I''ve used a number of portals both java and .net based and I found the basic concept very appealing. I''d very much like to see a Rails portal framework with ''railets''. I think this could really enhance the sharability of Rails apps. _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Xavier Toth wrote:> I''ve used a number of portals both java and .net based and I found the > basic concept very appealing. I''d very much like to see a Rails portal > framework with ''railets''. I think this could really enhance the > sharability of Rails apps.What''s your definition of ''railets''? Pluggable components? -- Alex
I''m thinking more about pluggable applications (blog, wiki, photo gallery, wheather, address book, chat, calender, ...). The portal would support dynamic configuration of itself you know drag and drop apps. I actaully like what dotnetnuke does with an admin app where you can select what they call modules from a list stored in a database and position them on a portal page. On 9/22/05, Alex Young <alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org> wrote:> > Xavier Toth wrote: > > I''ve used a number of portals both java and .net based and I found the > > basic concept very appealing. I''d very much like to see a Rails portal > > framework with ''railets''. I think this could really enhance the > > sharability of Rails apps. > > What''s your definition of ''railets''? Pluggable components? > > -- > Alex >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Sounds like that might work as modules within a CMS system built on top of Rails, rather than something in Rails itself... although maybe helpers, migrations and fixtures could be packaged in a standard ''plugin'' format to make that easier? Xavier Toth wrote:> I''m thinking more about pluggable applications (blog, wiki, photo > gallery, wheather, address book, chat, calender, ...). The portal would > support dynamic configuration of itself you know drag and drop apps. I > actaully like what dotnetnuke does with an admin app where you can > select what they call modules from a list stored in a database and > position them on a portal page. > > On 9/22/05, *Alex Young* <alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org > <mailto:alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org>> wrote: > > Xavier Toth wrote: > > I''ve used a number of portals both java and .net based and I found the > > basic concept very appealing. I''d very much like to see a Rails portal > > framework with ''railets''. I think this could really enhance the > > sharability of Rails apps. > > What''s your definition of ''railets''? Pluggable components? > > -- > Alex > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails-- Alex
Definitely this would be something built with Rails more than into Rails. Yeah I''m going to look around and see what''s going on with CMS and Rails. On 9/22/05, Alex Young <alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org> wrote:> > Sounds like that might work as modules within a CMS system built on top > of Rails, rather than something in Rails itself... although maybe > helpers, migrations and fixtures could be packaged in a standard > ''plugin'' format to make that easier? > > Xavier Toth wrote: > > I''m thinking more about pluggable applications (blog, wiki, photo > > gallery, wheather, address book, chat, calender, ...). The portal would > > support dynamic configuration of itself you know drag and drop apps. I > > actaully like what dotnetnuke does with an admin app where you can > > select what they call modules from a list stored in a database and > > position them on a portal page. > > > > On 9/22/05, *Alex Young* <alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org > > <mailto:alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org>> wrote: > > > > Xavier Toth wrote: > > > I''ve used a number of portals both java and .net based and I found the > > > basic concept very appealing. I''d very much like to see a Rails portal > > > framework with ''railets''. I think this could really enhance the > > > sharability of Rails apps. > > > > What''s your definition of ''railets''? Pluggable components? > > > > -- > > Alex > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > -- > Alex >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
The Java Specification for Portlets is actually quite good.
Is anyone familiar with the state of Rails CMSs? Is there one that stands out or has the most momentum? On 9/22/05, Mike Pence <mike.pence-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > The Java Specification for Portlets is actually quite good. >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
In the end I''m really more interested in portal like functionality (yeah JSR 168 ish) but I haven''t seen anything like this in the Rails world. On 9/22/05, Xavier Toth <txtoth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Is anyone familiar with the state of Rails CMSs? Is there one that stands > out or has the most momentum? > > On 9/22/05, Mike Pence < mike.pence-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > The Java Specification for Portlets is actually quite good. > > > >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
A lot of people are interesting in using a CMS, but no one wants to write one. However, MuraveyWeb is available: http://rubyforge.org/projects/muravey-tools . No idea what the status is, but http://allwaysspain.com/ is an example site using it. There was also the shortlived RailFrog movement: http://www.railfrog.com/ -- rick http://techno-weenie.net
Xavier Toth wrote:> Is anyone familiar with the state of Rails CMSs? Is there one that > stands out or has the most momentum? > > On 9/22/05, *Mike Pence* < mike.pence-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org > <mailto:mike.pence-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>> wrote: > > The Java Specification for Portlets is actually quite good.Ah-ha! A light has dawned. It would appear that I have some reading to do. -- Alex
This CMS/portal functionality is an obvious extension point for Rails just waiting for someone to tackle it. Other areas I see already are: -- A more robust ActiveRecord, able to use views (or stored procs) for data sources and stored procs for data updating. -- A rich-client view framework, so that view-side components can be manipulated view PME (Properties, Methods and Events), like JSF but without the XML ugliness, with AJAX-style updating built-in and automatic I''m sure those that feel an IDE is not the Ruby-way will absolutely hate the idea of visual design tools, but imagine a tool with the power of Ruby and the ease of use of Delphi. That would be pretty compelling. Mike Pence On 9/22/05, Rick Olson <technoweenie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> A lot of people are interesting in using a CMS, but no one wants to write one. > > However, MuraveyWeb is available: > http://rubyforge.org/projects/muravey-tools . No idea what the status > is, but http://allwaysspain.com/ is an example site using it. > > There was also the shortlived RailFrog movement: http://www.railfrog.com/ > > > -- > rick > http://techno-weenie.net > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
On 9/22/05, Rick Olson <technoweenie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > A lot of people are interesting in using a CMS, but no one wants to write > one. > > However, MuraveyWeb is available: > http://rubyforge.org/projects/muravey-tools . No idea what the status > is, but http://allwaysspain.com/ is an example site using it. > > There was also the shortlived RailFrog movement: http://www.railfrog.com/Uhh, railfrog isn''t dead, we''re currently working on collecting User Stories. If you are interested in helping out, subscribe to the dev list - http://lists.railfrog.com/mailman/listinfo/railfrog-dev -warner --> rick > http://techno-weenie.net > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
I think a good starting point would be to have a common authentication / authorization (user roles) scheme for railets. I''ve seen a lot of php applets that have to support the various schemes for individual CMS. It''s just not a DRY solution. Even non CMS apps would benefit greatly from this. The java portlets spec is probably a great starting point. I''ll check it out this weekend. -esstone
Certainly security and role based access control would be good services for a portal to supply. Also I used the term railets because I was thinking of portlets. However I hope railets could be more independent of the portal in their interactions because of the way Rails works than portlet are currently. Keep in mind that when JSR 168 was written AJAX wasn''t the buzz that it is today. On 9/22/05, Eric Stone <esstone-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > I think a good starting point would be to have a common authentication > / authorization (user roles) scheme for railets. I''ve seen a lot of > php applets that have to support the various schemes for individual > CMS. It''s just not a DRY solution. Even non CMS apps would benefit > greatly from this. > > The java portlets spec is probably a great starting point. I''ll check > it out this weekend. > > -esstone > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On 9/22/05, Mike Pence <mike.pence-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > This CMS/portal functionality is an obvious extension point for Rails > just waiting for someone to tackle it. Other areas I see already are: > > -- A more robust ActiveRecord, able to use views (or stored procs) for > data sources and stored procs for data updating. > -- A rich-client view framework, so that view-side components can be > manipulated view PME (Properties, Methods and Events), like JSF but > without the XML ugliness, with AJAX-style updating built-in and > automatic > > I''m sure those that feel an IDE is not the Ruby-way will absolutely > hate the idea of visual design tools, but imagine a tool with the > power of Ruby and the ease of use of Delphi. That would be pretty > compelling. > > Mike Pence >Actually, I saw someone using IntelliJ the other day, and if there was a tool like that for Ruby/RoR, I would leave Emacs in a heartbeat. -- http://www.approachingnormal.com _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
In article <e316da805092213284d9e9572-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>, esstone- Re5JQEeQqe8AvxtiuMwx3w-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org says...> > I think a good starting point would be to have a common authentication > / authorization (user roles) scheme for railets.Oo! Oo! I know! ActiveRBAC! (Which I''m about to try for the first time...) -- Jay Levitt | Wellesley, MA | I feel calm. I feel ready. I can only Faster: jay at jay dot fm | conclude that''s because I don''t have a http://www.jay.fm | full grasp of the situation. - Mark Adler
Honestly, I would love to have a component along the lines of Acegi (a pluggable java component for Spring). http://acegisecurity.sourceforge.net/ The ability to easily define authentication/authorization, various authentication backends, advanced password encoding, etc. -dave
Rails can already do this, they''re called components. Admittedly, there are a few hickups with this at the moment, but they can be ironed out. I''ve got a working blog component using this method at the moment, instances of which can be deployed at many points on my site. I''ll release it to the community shortly, but I figure I should at least add RSS support for it so that people don''t laugh at it''s lack of feature set. :) Still, if anyone wants to see the source now (and they are a fellow developer, not someone looking for a quick fix solution), please drop me a line. Craig Xavier Toth wrote:> I''m thinking more about pluggable applications (blog, wiki, photo > gallery, wheather, address book, chat, calender, ...). The portal > would support dynamic configuration of itself you know drag and drop > apps. I actaully like what dotnetnuke does with an admin app where you > can select what they call modules from a list stored in a database and > position them on a portal page. > > On 9/22/05, *Alex Young* <alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org > <mailto:alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org>> wrote: > > Xavier Toth wrote: > > I''ve used a number of portals both java and .net based and I > found the > > basic concept very appealing. I''d very much like to see a Rails > portal > > framework with ''railets''. I think this could really enhance the > > sharability of Rails apps. > > What''s your definition of ''railets''? Pluggable components? > > -- > Alex > > >------------------------------------------------------------------------ > >_______________________________________________ >Rails mailing list >Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >http://lists.rubyonrails.org/mailman/listinfo/rails > >
Components are a fantastic part of rails, and I expect many very cool components to be generated in the upcoming months . But say you embed a blog-summary component in the sidebar of your frontpage. A few months later you want to blog about work, so you add a white-list for who can view specific posts. It''s quick to roll your own authorization scheme for your component (or app), but it might not match up with the authorization scheme for a friend''s Amazon Wishlist component. It''d be a shame to have 314 different implementations of this floating around - I really don''t want to maintain multiple user->role->function maps. Check out the user-management code for Gallery - it''s all "if (drupal)...elsif(nuke)..elsif(wordpress)..." etc because the CMSs use different models. Ick! I really hope the Rails community standardizes itself around one authorization scheme for components. Please contemplate this if you''re developing a component. -eric ps. Someone earlier mentioned ActiveRBAC, thank you! This looks promising - Can''t wait to check it out. https://activerbac.turingstudio.com/trac http://csrc.nist.gov/rbac/ On 9/22/05, Craig Ambrose <craig-sZi9aYDroxztFRKb8DbDFhCuuivNXqWP@public.gmane.org> wrote:> > Rails can already do this, they''re called components. Admittedly, there > are a few hickups with this at the moment, but they can be ironed out. > I''ve got a working blog component using this method at the moment, > instances of which can be deployed at many points on my site. I''ll > release it to the community shortly, but I figure I should at least add > RSS support for it so that people don''t laugh at it''s lack of feature > set. :) Still, if anyone wants to see the source now (and they are a > fellow developer, not someone looking for a quick fix solution), please > drop me a line. > > Craig > > Xavier Toth wrote: > > > I''m thinking more about pluggable applications (blog, wiki, photo > > gallery, wheather, address book, chat, calender, ...). The portal > > would support dynamic configuration of itself you know drag and drop > > apps. I actaully like what dotnetnuke does with an admin app where you > > can select what they call modules from a list stored in a database and > > position them on a portal page. > > > > On 9/22/05, *Alex Young* <alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org > > <mailto:alex-qV/boFbD8Meu8LGVeLuP/g@public.gmane.org>> wrote: > > > > Xavier Toth wrote: > > > I''ve used a number of portals both java and .net based and I > > found the > > > basic concept very appealing. I''d very much like to see a Rails > > portal > > > framework with ''railets''. I think this could really enhance the > > > sharability of Rails apps. > > > > What''s your definition of ''railets''? Pluggable components? > > > > -- > > Alex > > > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >Rails mailing list > >Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > >http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
Hi Eric, My approach to that was not to put any authorisation code in the component. Instead, there are a couple of ''magic'' parameters which I pass in when the component is called (I call it from a controller, not a view). One of them is "can_administer?", although this could be extended if there are more that two possible access states to the component. If we can agree on the types of access to the component (ie: write, publish, edit, read), then we can leave the idea of users and authentication up to the application which calls the component. Craig Eric Stone wrote:>Components are a fantastic part of rails, and I expect many very cool >components to be generated in the upcoming months . But say you embed >a blog-summary component in the sidebar of your frontpage. A few >months later you want to blog about work, so you add a white-list for >who can view specific posts. It''s quick to roll your own >authorization scheme for your component (or app), but it might not >match up with the authorization scheme for a friend''s Amazon Wishlist >component. It''d be a shame to have 314 different implementations of >this floating around - I really don''t want to maintain multiple >user->role->function maps. Check out the user-management code for >Gallery - it''s all "if (drupal)...elsif(nuke)..elsif(wordpress)..." >etc because the CMSs use different models. Ick! > >I really hope the Rails community standardizes itself around one >authorization scheme for components. Please contemplate this if >you''re developing a component. > >-eric > >ps. Someone earlier mentioned ActiveRBAC, thank you! This looks >promising - Can''t wait to check it out. > >https://activerbac.turingstudio.com/trac >http://csrc.nist.gov/rbac/ > > >
On 9/22/05, Eric Stone <esstone-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Components are a fantastic part of rails, and I expect many very cool > components to be generated in the upcoming months . But say you embed > a blog-summary component in the sidebar of your frontpage. A few > months later you want to blog about work, so you add a white-list for > who can view specific posts. It''s quick to roll your own > authorization scheme for your component (or app), but it might not > match up with the authorization scheme for a friend''s Amazon Wishlist > component. It''d be a shame to have 314 different implementations of > this floating around - I really don''t want to maintain multiple > user->role->function maps. Check out the user-management code for > Gallery - it''s all "if (drupal)...elsif(nuke)..elsif(wordpress)..." > etc because the CMSs use different models. Ick! > > I really hope the Rails community standardizes itself around one > authorization scheme for components. Please contemplate this if > you''re developing a component. > > -eric >I wrote a little rails component that took a different approach. Instead of trying to specify some abstract authentication scheme, I completely left it out. I then reopen the class and make a before_filter call in whatever app is using the component. I have the component integrated into two completely different rails apps and it seems to work well. -- rick http://techno-weenie.net