Hi Aure,
Nice looking system - I''m having a problem with the mail component
though - I added a ticket in ruby forge:
http://rubyforge.org/tracker/index.php?func=detail&aid=2530&group_id=949&atid=3722
However previous experience tells me rubyforge doesn''t always alert
project admins to new tickets, so I thought I''d post here.
Many thanks.
CHEERS> SAM
Aurelius Prochazka wrote:
> Hi,
>
> I took up Rails this summer and I''ve been developing a few web
sites
> with it. I extended the capabilities of the Login Generator and
> Salted Hash Login Generator to include groups management and a
> management user interface. I wanted to give back to the community so
> I created a generator called "ARCS" standing for A Rails
Community
> System which is available at http://rubyforge.org/projects/arcs/ and
> http://arcs.rubyforge.org/
>
> I was really enjoying programming in Ruby On Rails up until the point
> where I had to package my code for distribution. I find the
> generator format to lacking in several ways.
>
> a) I really like the directory structure of Rails (esp. when using
> Textmate for editing) and I think it''s pretty silly to flatten the
> structure and put all the files in one templates directory as is the
> case in most generators. You can have subdirectories in the
> templates directory, so I sort of recreate a rails like structure
> underneath templates, which is okay.
>
> b) Once you''ve moved to a generator based system, any time you
make a
> change and want to test, you have to run the generator, taking much
> of the joy out of developing and immediately seeing your results.
> If you make changes to the code output by the generator then you have
> to change all of your <% to <%% format which is a pain as well.
>
> I dealt with some of the problems in a) and b) and wrote about them here
> http://aurelius.com/articles/2005/09/12/creating-rails-generators
> but still...
>
> c) Even when you package up everything in a generator, it seems like
> you still are left with a lot of instructions for the program
> installing the software. The step-by-step installation guides for
> the Salted Hash Login Generator or my ARCS system are pretty
> involved. The programmer has to change his application.rb file, his
> environment.rb file, and routes.rb for any kind of complex system.
>
> Rather than creating generators, Tobias Luetke has opted to
> distribute his reasonably complex software like Typo and Hieraki by
> packaging it with a complete rails directory structure. So, since I
> think ARCS will also end up being fairly complex, perhaps I should do
> that as well?
>
> This is my first post to the list, so I''d like to introduce
myself.
> I am one of the co-founders of ArsDigita, a company that made the
> ArsDigita Community System which has morphed into OpenACS (http://
> www.openacs.org/). I''m actually not a big fan of how heavy OpenACS
> has become, here''s my opinion on Rails vs. OpenACS (and vs. Zope):
> http://aurelius.com/framework_comparison
>
> Anyway, I believe Ruby On Rails needs a really good system for
> distributing and installing 3rd party code. Maybe, DHH, it hasn''t
> been on the forefront of your thoughts yet because I''m sure
you''d
> come up with a brilliant and simple solution! Otherwise, I''m
feeling
> a nagging tug towards Django which has user and groups, a management
> interface, and python style module packaging out of the box.
>
> Aure
>
>
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>