Also on IRC if anyone has questions.
Currently working on making the Arc app read directly from SQL.
I'll post a #devski update later tonight.
EDIT: alright, I'm calling it. I got SQL loading in the main app working, but it's slow, I don't know why. Hoping it's fixable. I'll post a #devski update shortly.
I know right? I'm intensely curious in it and have been reading a few articles but I do not see how to get from (+ 1 1) to a site like Hubski. I'm coming from a Java/PHP/Ruby background so it's really difficult for me to visualise what the code actually looks like, and unfortunately seems I'm late to this party. So here, an article about The Strange Appeal of Live-Coding.
For the hubski internal API, I mostly used the docs and this. If you prefer to learn by example (like me), I'd actually recommend the hubski internal API I've been working on. It's a pretty good small example of how to do URL dispatch, JSON, and basic serving. I think I took out the x-expression stuff though. Definitely look into x-expressions. They're flipping awesome.
Mm, I saw about that and have seen some about it (actually I was reading about Pollen and started delving in from there). My problem now is time, I would love to learn some functional programming and see if I will be able to teach it in class, but I think I'll likely be shoe-horned into just using Python or C# or some-such so it's a cost/benefit problem where at the moment the cost seems too high.
Yeah definitely, it's on my list but my issue is I keep finding new and exciting things to add like Haskell or the many many JS frameworks etc. It's tough to figure out which ones would actually be of use to me, and certainly I don't think any will be of use for the classroom as I think we'll be pressed for time (and this is teenagers who aren't exactly going to be excited for programming in the first place :) )
Well, I'm more back-end. This is really insomniasexx's department. I tend to agree, it does seem a bit small for unindented paragraphs. But I'm not a typographer. I'll bring it up. You could always jump on the API bandwagon.gonna need a new cause.
Ohhhh this is what you meant by the paragraph spacing. forwardslash this is for you! There are two separate issues (correct me if I am wrong, flag) - one is that the paragraphs go away when you edit a post. And two: a single line space doesn't register as a new paragraph (I think there is a reason for this one though...)
Please please please just make what we type in the little box be exactly what shows up on the screen after submission if at all possible. WHY doesn't hitting enter make a new line? EDIT: Surely I am not the only one who thinks about this way too much,
Lol. Okay - I looked it up. It's a thing with Markdown (which is not something we created, just hacked to use in Arc) http://meta.stackexchange.com/questions/26011/should-the-markdown-renderer-treat-a-single-line-break-as-br You indeed are not the only one: A markup should not break elementary common sense rules in order to provide other elevated functionality. The fact users use two carriage returns to create paragraphs [...] is irrelevant. The markup internal rules stipulate that [...] text formatting can break break because the lack of two carriage returns. That's fair enough. But text doesn't lose readability if instead of a new paragraph, every carriage return introduces a line break on the resulting text. Take a look at the user edit box here: [image that is now gone so use flag's image above] Is there anything in there that is not clear in terms of formatting? He doesn't use carriage returns and yet his line-break formatting style makes that particular text easy to read and appealing to the eye. The markup however made a mess of it. So, the markup actively ruined the user text. This cannot be. For the sake of some special formatting elements, like list detection the markup aggressively demands two carriage returns to break a line and doesn't accept the idea of a new-line break, unless the user explicitly forces it with the BR tag. The line that divides easy-of-use and formatting tyranny can be very thin. On this case it was crossed over. The text the user writes on his text box should have been formatted with single line-breaks. The end result would have been readable text, just like the user intended.Hitting the carriage return key on a keyboard should give the user a new line in the output. This is simply typographical common sense.
I think we need to just see if there is a way to read a single line break from what is delivered when you press "submit" and turn it into a <br /> (or a <p></p>). We actually don't use <br /> tags for line breaks. cc: forwardslash
I'm seeing some 'failed to upgrade connection' messages in the connection log. That means someone tried to connect, but their browser doesn't support Websockets. If you go to that URL and get a blank screen, it's probably because your browser doesn't support Websockets. Probably because it's old. Sorry, not much I can do to fix it.