We get a fair number of visits, I think. For a rarely-maintained, grassrootsy, non-commercial site. Not a lot. We had under 400 visits the last month, according to Google Analytics, though most visits last over 2 minutes, and at least half our visitors are repeat visitors.
I have to assume folks are making use of JazzRecord in some way, and that they’re visiting to refer to the documentation. I don’t see any other explanation. I’d really like to get to know the users, and find out if we can do anything to improve JazzRecord short-tern and long-term.
Long-term, for instance, I’d like to move our documentation into the source code repo and simply reference/style that nicer on the Web site. I’d also like to provide better docs and add a few more features, like the ability to add indexes in a model’s declaration. I’m still considering the implications of async support eventually, though I certainly don’t have time to support this idea at the moment. We’d still like to translate the docs into other languages, but we need volunteers.
Short-term, I’d like to add some new adapters to the codebase. I’d like to support any new runtimes that may have cropped up lately. Node.js and similar are definitely on the list. Does anyone use Jaxer still? Is there an environment you’d like to see supported? So long as SQLite or a compatible dialect of SQL is supported, and so long as a *synchronous* API of some kind exists, JazzRecord can be added with very little effort.
Please, take a moment and comment, here or on Twitter. Let us know how you use JR and what you’d like to see in the future.
7 Comments
Hi I’m very interested in using JazzRecord with Adobe AIR, I’m currently using Doctrine ORM on the server side, and I need active record to maintain the db on the AIR client.
I’d love to see some more code examples in the docs and perhapse an example of generating models from an existing DB or YAML?
I am also interested in helping you document JazzRecord as I implement it in this project, please contact me at convenience.
re: http://www.jazzrecord.org/browser_demo
it’s producing:
Errno::ENOENT in SiteController#browser_demo
and, it’s displaying the full stack trace (assuming all requests are local?)
apart from that, this looks like a really cool project, and i’m about to get started playing around with it!
I check back to see if there are any bugs being fixed that I should know about, any performance improvements, etc.
Wow, sorry to be getting back to you so late! I didn’t realize anyone had been commenting on the blog.
I’m not sure where the link you reference came from, but the correct URL for testing in Gears in-browser is http://www.jazzrecord.org/demo.
Thanks for the kind words and I hope it’s useful to you! If you have any questions please comment on Twitter or email me at thynctank at thynctank dot com.
Hi Mike, apologies for not getting back sooner. (MUCH sooner)
I hope you’ve been able to make use of JR and the docs have been of use. Please do contact me at thynctank at thynctank dot com if you are still interested in using JR at all in the future and/or you would like help understanding any code examples or would like to contribute to docs, code etc.
Thanks again!
There are definitely bugs and changes that have made it into the stable branch on github, which has been the preferred means of getting JR for a while now. This site has out of date code. Apologies for that, we’ll be scrapping this site as means for distributing the code shortly.
Please check http://github.com/thynctank/jazzrecord/tree/0.8 for current stable branch and http://github.com/thynctank/jazzrecord for ongoing development.
Thanks for the interest in JR, and please contact us via Twitter (@jazzrecord http://twitter.com/jazzrecord) or email me directly at thynctank at thynctank dot com.
I’m feeling a bit guilty, as I’ve been promising to clean up the site for ages, and have been sleeping on it. Unfortunately, my poor job of webmastering has not well reflected the continued maintenance and progress of this project!
The website shall be fixed up within the next few days. I will post a blog on here once complete!