Contestant on Rock 'em, Sock 'em, Node bots.
Definitely jump on later and we'll play. Always glad to hear from a fellow Divekicker!
if you see that I was only an only contestant and the competition was 48 hours ... I think it's pretty good, it is far from perfect, but it does what it promises
Thanks for voting and for the feedback! I appreciate it.
Answering your questions:
The documentation is generated by analyzing .js files and looking for jsdoc (http://en.wikipedia.org/wiki/JSDoc) style comments. JSDoc is very similar to JavaDoc and is considered the standard for documenting .js code;
The project is meant to be a prototype and doesn't have caching or any other feature that you might find in a finished product;
There's a huge difference between documentation generated from jsdoc style comments and a README.md -- first, the README.md documents the concept of the package (or repo) while generate docs reference the whole API.
Now, looking at your repos and trying to understand why the generated docs are poor in comparison to the given example:
bond (https://github.com/EndangeredMassa/bond): only one .js file found, and it was generated by CoffeeScript. Also, there's no documentation whatsoever in any of the .coffee files or the generated .js
quack (https://github.com/EndangeredMassa/quack): there are no .js files in that repo so the tool is useless
facile.js (https://github.com/EndangeredMassa/facile.js): again, only one .js file and it was generated by CoffeeScript. No documentation whatsoever was found on the .js itself or on the .coffee files
To summarize, hookdoc attempts to render documentation based on jsdoc comments that are found in code. If there are no jsdoc style comments, the generator won't be able to work properly.
I hope you have the time to give some more feedback if you read this reply.
Makes sense! I didn't realize it was looking for those comments.
Thanks for the feedback! We definitely wanted to do a better job with a "walkthrough", but ran out of time. Any ideas on what you'd like to see there?
For the "one file at a time" - what exactly do you mean? Just want to make sure we can work on fixing it.
Thank You very much.
Thats a great idea. Thanks! Also, gitdo automatically creates github issues and stays in sync. So it should fit in nicely with anyone's workflow.
Hey Sean, these are great questions. We're hoping that Tidbit can completely replace ad revenue. Looking forward, there's a ton of interesting optimizations we can do. First and foremost we want to integrate WebGL and run computations on the GPU. Beyond that, there are even different cryptocurrencies with less mining overhead like Litecoin that we could swap in.
With respect to sustainability, our clients get paid for work done for the mining pool, not exact bitcoins mined. This should mitigate losses to network difficulty. Hopefully Bitcoin is around long enough to experience such difficulty! :)
Hey there, thanks for the feedback. As we move forward, we will indeed make the quizzes available on the site itself so you can take them when you want (only so much you can do in 48 hours, thouhg).
However, we debuted tut with the SMS feature for a very deliberate reason. The purpose of the SMS quizzes is to distribute the testing over time - so you wouldn't be going in between computer and phone. You'd study, mark the tutorial as read, and then tut would send you quiz questions at semi-random intervals (so you never know where you'll be, hence relying on phone tech). Check out our science docs on the main page for the full rationale behind this, but the short story is, you tend to retain more information from that form of testing, rather than being quizzed all at once at the end of studying.
Thanks again for your comments, and yeah, we're going to keep going after the competition finishes. This is just the beginning for tut.
I did reset as you asked, we have problem with auto reseting map.
Unfortunately, chrome queues the WebSocket messages unless it's in the foreground. That's what we mean may 'Active Conections'. Try opening 2 tabs side by side and see if it's better.
I'm glad you will like, but that cat has a little chubby. haha..
Most modern web browsers don't make it easy to use RSS/atom feeds without 3rd party addons -- our API is intended to make it easy to write those addons -- a lot like like IMAP works for email, actually.
Another reason is that when you subscribe to a feed that's already in the system (by another user), you get full history right away from our cache. Sadly we didn't get time to implement full text search in the API.
We were planning on using Twitter and Twilio to solve this problem, but we ran out of time.
Thanks for the feedback buddy! We know that we cannot compete with other solutions in this area(like G-maps) but our idea is not to do what all these other solutions are doing. Can you imagine a place where Google traffic is not supported(there are lot), You'll be helpless. But this solution is based on the crowd. Which means if you are in a traffic in city A and I'm headed that way i know there's a traffic ahead. Its all about people helping people. As a web app its a cross platform compatible solution.
Thanks for you vote. Anyway the bot section is not for real people ^^
sorry. i misunderstood English .... now refreshed something but English ......
thanks comment ☆
Thanks. In the future, we will continue to work on that, and explore more in the GIT side. e.g. showing the difference of the workspace and git repo in real time, and showing different GIT commits..etc :)
hey Sean, our site is back again, thanks for reviewing ;)
Hrm. There appear to either be no seeded personalities. When I create a profile, I only see my own profile in the Browser Profiles. And, I can click Meet/Pass on my own profile, which does nothing.
From what I can see, this doesn't do anything so far.