Re: Ruby on Rails
| From: | Paul M Jones | Date: | Tue, 08 Feb 2005 13:54:10 +0000 |
| Subject: | Re: Ruby on Rails | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-36061@lists.php.net to get a copy of this message | ||
Nikolas 'Atrus' Coukouma wrote:
Daniel O'Connor wrote:<promotion target="pear" mode="self,shameless"> Yawp certainly is a nice way to get started, but it's not an end-all be-all. DB_Table for object-relation management and form generation (through HTML_QuickForm) is certainly nice to have, but it's not braindead-simple to set up. Of course, nothing in the real world is; I get the feeling that the ROR demo is, like all demos, inspiring and fun to watch, but that ROR won't handle real-world problems that way. One of the things preventing Yawp from going much further is that PEAR classes (being the products of disparate developers) are not built to work together implicitly from the start; e.g., the constructors are all different, there's no unified i18n strategy, etc. (One major exception to this is PEAR_Error; for all its flaws, it is one unifying factor that has proved quite successful.) None of this is bad, it just points to a different underlying philosophy that ROR. With that in mind, adding a PEAR class to Yawp is a difficult thing; Yawp has to support each one individually. </promotion> <promotion target="hive" mode="self,shameless"> Those are some of the reasons I've started Hive, blogged here:Questions: 1) What have I missed from Rails that we already have in the PHP world...I've played with YAWP a bit. It's not as cool as Ruby on Rails, but it's still nice and handy. http://phpyawp.com/ Other fun stuff is listed in the frameworks department http://dmoz.org/Computers/Programming/Languages/PHP/Scripts/Frameworks/2) Like it, hate it, let me know what you think... I've a developing itch to scratch :)
http://paul-m-jones.com/blog/index.php?p=105Each class in the library gets constructed the same way, optionally from a unified config file (PHP not XML). They are all built from the ground up to deal with each other effectively. I'm trying to implement unified i18n (localization) strategy, although output is left to end-user. Hive comes comes with basic sub-application components (a comment/trackback/flat-forum module right now, a bug-list module in the works, and planning to have a wiki-store module and a blog-module as well). Of course, Hive is only at 0.0.1dev1 with the first public release on Friday last. So I guess I'm saying that maybe Hive is a place to implement ROR ideas, seeing as it's just getting started. I'm not very MVC in practice, so aid in developing a front-controller would be appreciated. Maybe PEAR can take up some Hive ideas; goodness knows Hive has gotten plenty from PEAR, and both can be better for it. </promotion>