[Catalyst] Article on web frameworks ommits Catalyst

John Napiorkowski jjn1056 at yahoo.com
Tue Jan 2 16:39:31 GMT 2007


--- Matt S Trout <dbix-class at trout.me.uk> wrote:

> 
> On 2 Jan 2007, at 14:33, John Napiorkowski wrote:
> 
> >
> > --- Kieren Diment <diment at gmail.com> wrote:
> >
> >> Hey,
> >>
> >> There's an article, "Web Framework Manifesto"
> here:
> >>
> >
>
http://blog.lostlake.org/index.php?/archives/16-Web-Framework-
> 
> > Manifesto.html
> >>
> >> I've written a comment in the article suggesting
> >> that this is a pretty major
> >> ommission and that he might want to evaluate
> >> Catalyst and do an update.  The
> >> author seems coherent and reasonably knowledgable
> to
> >> me, so how bout it
> >> guys?  Maybe you should let him know his mistake
> >> too?
> >
> > This is actually quite an interesting thoughtdump
> on
> > what we'd like in a web development framework. 
> Some
> > of the things mentioned, such as a great
> dispatching
> > system, straightforward ORM support and easy to
> extend
> > APIS (Plugins, customized Controllers, Views or
> > Models) we have.  However some of the things
> mentioned
> > I don't see as current strong points of Catalyst,
> such
> > as the idea of web pages being highly
> componentized
> > and capable of managing their own state.  This
> could
> > just be my ignorance though.
> >
> 
> I don't really think that belongs in Catalyst base;
> I'm implementing  
> highly componentised UI development with automatic
> state management  
> in Reaction and I'm not finding doing so "on top" of
> Catalyst any  
> harder than it'd be to hack it into the core.

There wouldn't happen to be any examples of that
floating around that would be okay to share?  I've
spent a lot of time reading the Reaction source so I
think I have the basic idea, but the example CRUD
application doesn't really click for me in terms of
how I could use this to build a componentised webpage,
since it's only a few pages.  I mean I see how the
forms get composed of the different peices but for me
there isn't a critical mass of documentation/examples
in this for me to be able to use  it and to contribute
meaningfully.  This is something I'd definitely like
to contribute to if possible since user interface has
been main development focus for a long time.  Just
right now before I can contribute I am sure I'd need
50 questions answered and lots of hand holding that I
know nobody has time for.  I am sure there are a bunch
of other catalyst developers that would be eager to
join in as well if only we could get past the initial
conceptual curve.

thanks,
John

> 
> > The article is big on continuations.  Catalyst has
> a
> > plugin for this but I'm not sure many people know
> what
> > to do with it or what the advantages could be.  To
> be
> > honest I'm not someone that could answer that
> > question.
> 
> Web development is effectively stateless - or at
> least HTTP is. I  
> tend to find continuation usage is almost invariably
> an XY problem -  
> i.e. if you need continuations to implement your
> design, you should  
> probably rethink it.
> 
> -- 
> Matt S Trout, Technical Director, Shadowcat Systems
> Ltd.
> Offering custom development, consultancy and support
> contracts for  
> Catalyst,
> DBIx::Class and BAST. Contact mst (at)
> shadowcatsystems.co.uk for  
> details.
> + Help us build a better perl ORM: http://dbix- 
> class.shadowcatsystems.co.uk/ +
> 
> 
> 
> _______________________________________________
> List: Catalyst at lists.rawmode.org
> Listinfo:
> http://lists.rawmode.org/mailman/listinfo/catalyst
> Searchable archive:
>
http://www.mail-archive.com/catalyst@lists.rawmode.org/
> 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 



More information about the Catalyst mailing list