[Catalyst] Catalyst::Controller::Rose::Simple = CatalystX::RoseIntegrator

Hello list, Following the preceding discussion, I scheduled Catalyst::Controller::Rose::Simple for deletion on CPAN and uploaded the same module under the name CatalystX::RoseIntegrator. Please wait the time required for it to show up. I gave it version 0.02 because of this and a

Re: [Catalyst] Catalyst::Controller::Rose::Simple

Matt S Trout a écrit : I think you should just rewrite the damn thing to use Controller::Rose. That seems like a much better idea to me since Peter Karman's code is already pretty stable and provides most of the things you need. Like what? Just provide a different interface on top.

Re: [Catalyst] Catalyst::Controller::Rose::Simple

Peter Karman a écrit : Alexandre Jousset wrote on 9/20/07 11:41 AM: I'm sure I haven't your experience but for me (and also for Peter Karman, C::C::Rose author), the suffix ::Simple (suggested by him) means Take all that [what already exists, i.e. Catalyst and Rose] and make it simpler

[Catalyst] Catalyst::Controller::Rose::Simple

Hello list, I just uploaded on CPAN the module : http://search.cpan.org/dist/Catalyst-Controller-Rose-Simple/ that makes use of Rose::* easier ith Catalyst. It is version 0.01, so use with care and development environment use only. I know, documentation and tests are

Re: [Catalyst] Catalyst::Controller::Rose::Simple

Hello Matt, Matt S Trout wrote: Feel free to ask me any question you want. Why haven't you submitted patches to the existing C-C-Rose? Any module called '-Simple' usually means there was an existing module that worked but I'm too lazy to patch it - please justify why that

[Catalyst] RDBO/RHTMLO integration with Catalyst - work in progress

Sorry for the repost, the address for the RDBO list was wrong. -- Hello lists, Since I haven't seen any work like this before (if I'm wrong please give me pointers!) I started to write a Catalyst Controller

[Catalyst] RDBO/RHTMLO integration with Catalyst - work in progress

Hello lists, Since I haven't seen any work like this before (if I'm wrong please give me pointers!) I started to write a Catalyst Controller called Catalyst::Controller::RHTMLO to integrate RHTMLO (and a few bits of RDBO) to Catalyst the same way Catalyst::Controller::FormBuilder do.

[Catalyst] Re: [RHTMLO] RDBO/RHTMLO integration with Catalyst - work in progress

Peter Karman a écrit : check out Catalyst::Controller::Rose on cpan. It has a different philosophy than what you've described. But if you find features missing that you think would make it more useful, please send me patches/tests/docs etc. You might consider writing a new

Re: [Catalyst] Re: [RHTMLO] RDBO/RHTMLO integration with Catalyst - work in progress

Peter Karman a écrit : I'm still studying them to be sure what is the right thing to do... But any advice is welcome... C::C::Rose takes the thin controller/fat model approach. Look at the example app in the t/examples dir to see one implementation. Done. I prefer to follow the

Re: [Catalyst] Ask Catalyst: What are your prefered DB and HTML abstraction layers ?

Matt S Trout a écrit : [...] (1) Will it be more work to get your RHTMLO-DBIC integration going than it would be to port to RDBO and get RHTMLO-RDBO integration going? For the moment there is not a lot of code, so it could be easy to port the application to Rose. (2) Do you need any of

[Catalyst] Ask Catalyst: What are your prefered DB and HTML abstraction layers ?

Hello list, I started a project using Catalyst with DBIx::Class and FormBuilder. This is far from a CRUD application. In fact it is a Slashdot-like application. I've heard about Rose and I'm planning to move from FormBuilder to Rose::HTML::Object that seems better designed. My

Re: [Catalyst] Session unexpectedly expiring

Hi, Jeff Chimene wrote: More breadcrumbs. The directory is getting created, but session_data isn't getting created. I have similar problem... The symptom is that the directory is created with the wrong user (root). Each time I reboot the server I have to manually « chown

[Catalyst] What to use ? HTML::Widget ? Data::FormValidator ? etc...

Hello dear list, I'm currently in the early stage of writing a Catalyst application (in fact redesigning a non-Catalyst one) and I'm wondering what plugins to use. I've already written Catalyst applications successfully but for this one I've decided those constraints : -

Re: [Catalyst] What to use ? HTML::Widget ? Data::FormValidator ? etc...

Jonathan Rockway wrote: Alexandre Jousset wrote: - Use TT as view - Use a form validator - Not necessarily use a widget creation plugin - I18n - Reuse the most possible code / templates and be very modular Catalyst::Controller::FormBuilder does all that. It also auto