MSc. Human Movement Science, #programmer #sports #health #openbigdata #node.js and #graph-theory, developer @ http://www.nodejitsu.com, co-founder observe.it
Thanks for the feedback, Swaagle. The purpose of the file previewing is not for the uploader, but is instead for the people you share it with (who do not yet know the contents of the file). I didn't do a good job of explaining that unfortunately.
:) then I can definitely see its purposes! innovation updated!
Hi Martijn, thank you! Yes, we agree with you, it is not a solved problem. Maybe it is more a shift in learning focus: instead of syntax errors the learner will focus on logic and problem related questions. Indeed, many blocks create complexity to visualize the whole code. We are interested in investigating ways to reduce this complexity, maybe using abstract structures (groups, zoom-in/out interface, ...). Maybe NoFlo guys can give some shots on that. Anyway, your feedback and acceptance was so important to us! Thank you!
Thanks. You're right it could and should be easier!
Sorry to hear that. Can I ask what API URL you were using? I'd like to test.
We only wait 20 seconds because line graphs with 1 data point are pretty uninteresting. Our samples are set to 10000ms refresh so 20 seconds get us 3 points resulting in a better presentation.
Swaagle, took a look in our logs. You were trying to check uptime on an HTML page. THis is specifically for checking api's that serve JSON.
Thanks for the feedback, yeah things get all sorts of real with the actual feeds turned on! Keep an eye out :)
Hi Swaagie, thanks for your comments. We definitely agree that we need to put more time into the interface (only so much you can do in 48 hours), but we want to stress that the integration of github into our service was very deliberate.
One of our main goals was to provide a system for the collaborative development of online tutorials. As a scientist myself I'd rather work on document editing within github (rather than emailing around word documents as we usually do) - frankly, software developers are miles ahead of the game when it comes to working together, there's a lot that we in academia and research can learn from them.
So one of the things we are really trying to demonstrate with tut is that gitub doesn't just have to be for code. The version control, the commenting, the tagging, the creation of issues, all of these are just as important in the development of educational materials as they are in the development of software.
So certainly, the interface and flow could use some work (and we will get on that after the contest is over), but one thing that won't change is the use of github as a means to host the tutorials, because it really is a great tool for that. Thanks again for your comments and taking the time to check out tut.
Actually you got a very good point there, added 2 stars for design. I'm coming from an academic background myself as well and I often wondered why people don't use github to do collaborative scientific writing.
Thanks for your feedback, you are right Grwp is more focused on anonymous kind of conversations like job interviews, random assembled groups in online games or school, etc,
Thank for your feedback, however we actually think that what makes our application unique is that you don't need a rooster of friends as you do in Hangouts.
We imagine use cases were you don't want to add someone to your contacts list in order to talk with them, for example when you are conducting a large number of interviews, or while playing games online with people you recently met.
Regarding Hangouts and social integration, we also believe that another strength of Grwp is that you and the people you are taking to don't need any type of account to use it. You can't expect everyone to have a Gmail account ;)
background subtraction is something that I would like to work once NKO ends :)
ah k :) definitely still a cool project