Hi, I've only been using Catalyst since Feb. but I think some of the trends I've noticed have been:
-- DBIx::Class becoming a defacto ORM standard. -- More discussion of HTML::Widget for form input and validation, and discussion of Dojo as possible a good Javascript toolkit to use. I think in the future we'll see html::Widget and dojo in more catalyst applications. At least in mine :) I think the stuff in "Task::Catalyst" is still considered core modules to use and build applications. Most people seem to prefer template toolkit for templating, for example. Some of the plugins are not getting as much play as before, such as FillInForm, since they have performance and security implications. I think Catalyst is a lot like Perl itself, very open but after a time certain best practices are starting to emerge based on the community interaction. So there is still plenty of time for you to have an impact. You should try to follow what's going on in the documentation for the next release, since I'm getting the feeling there will be a lot of documentation related updates. I also think you might get more responses here if you ask more detailed techy questions about your application and goals. Is there something in particular that is worrying you? When I first jumped into Catalyst I also had a feeling people where talking about things several jumps ahead of what I was doing. I know also there is supposed to be a bunch of Catalyst related developer blogs around, and I think you could probably search for that thread in this list. That might also help you. good luck -john --- Joe Landman <[EMAIL PROTECTED]> wrote: > Hi folks: > > This is more of an update-my-understanding > question. I started > playing with Catalyst about 9 months ago, and > quickly moved development > over to it. Our last update was 5.61. > > What we are doing requires a number of simple > things. Handle logins > and authentication against a database, restrict > access to pages based > upon roles/permissions in the database, as well as > timed expiration of > sessions, and storing session state on the server if > possible. > > Catalyst had bits to do this some months ago, and > we started working > with them. But it has evolved so rapidly since then > that we are > concerned we are not using up-to-date > code/plugins/tech. > > Is there a set of currently suggest plugins, and > sample code that we > should be looking at? Pointers/RTFM welcome with > pointer to the FM or > FD which are relevant for this. Thanks! > > Joe > > > > _______________________________________________ > List: [email protected] > Listinfo: > http://lists.rawmode.org/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
