[Nitro] The future of Nitro, Og and Raw
george.moschovitis at gmail.com
Thu Oct 23 12:18:40 EDT 2008
nice to see a post on this list after all this time ;-)
I have no problem with your proposal, it's OK by me.
Btw, in the last few months I have created a brand new web (or should I say
REST) framework for my own use. It's completely different to the old Nitro
(and frameworks like Rails/Merb). I am trying to make it as simple and
standards compliant as possible. The plan is to eventually write some docs
and release it as open source, but we 'll see about that. At the moment the
server side logic is written in Ruby, but I am thinking about switching to
have so far ;-) ;-)
An early version of this framework powers my new blog: www.gmosx.com, check
On Thu, Oct 23, 2008 at 6:10 PM, chris <prpht9 at gmail.com> wrote:
> Not sure who all is still listening but I have something to say.
> As Dan North said a while back. Nitro is quite feature full and could
> really use some time to settle in with some bug fixes and a really solid
> release. I may end up taking a stab at this. Once I got some fixes into
> the Nitro and Raw dependancies and require statements. A simple "nitro
> hello;cd hello;nitro" works out of the box. I also converted the entire
> projects to "newgem" projects ( no offense intended ). The rake build tasks
> in there are excellent and "rake local_deploy" works perfectly. I have not
> touched Og, it seems to be pretty solid already. (side note: I think Og
> could stand on it's own two feet as well but if you want me to hold onto it
> for a while I will)
> Fixed Nitro and Raw gemspec dependancies
> Fixed missing "require 'raw/controller'" in raw.rb
> Replaced lib/facets.rb with a gemspec dependancy
> Converted Nitro to a newgem project to capitalize on the rake tasks and
> rubyforge integration
> Converted Raw to a newgem project to capitalize on the rake tasks and
> rubyforge integration
> I think I found some bugs in the admin part, which in my opinion is key to
> getting a new user's feet wet with nitro and og. I'd like to fix those.
> Massive build up of examples in the rdocs
> Move good examples to the prototype site produced by "nitro project_name"
> Include more details in the actual prototype site code and startup files
> like app.rb and config/debug.rb
> I do not plan to move away from using the current unit testing. However I
> will create new tests using rspec and rbehave. They are not mutually
> Get "rake docs" working
> Get "rake website_generate" working
> With your permission, Trans and George I'm talking to you, I'll put some
> more effort into this and see what I can come up with. None of my changes
> will mess with the api, my entire goal is stability and usability. After
> presenting my initial work to you guys, we can decide where you want to go
> from there.
> Before I forget, Robert Mela, if your out there. I'd love to get a hold
> of your cheatsheets for inclusion in the actual rdocs. Looks like your site
> has been reclaimed by the domain goblins.
> Hope to hear from you,
> Chris Scheper
> Nitro-general mailing list
> Nitro-general at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nitro-general