Gareth Kirwan wrote: >> Personally, I'd try to refactor the site so that you don't have this >> problem. Maybe there's another layout you could use to avoid this? I >> don't know... >> > > /app/$index/action could be replaced by /app/action/$index, > but i wanted to do more things later that would run off of this. > > I guess you could consider that maybe I'm using mason a bit too > controllerisly. > Catalyst might be the right way to go for this kind of thing, > since pathparts closely relate to what we're doing here. > > However I still like the feature, and am using it more liberally each week. > > Heh, I agree that it's much better to have URLs that read really cleanly like that, and that's how I write things when using Catalyst.
Using Catalyst with Mason is fun, because you have two seperate 'inheritance' chains. In Catalyst, you map a URL to an action, and pick a mason component, and then Mason will have its own chain of components based on that. This means that you can layout your mason components however it is easiest given the wrapping chain you want, and not worry about how it maps to a URL. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
