Comments on: We’ve been baking! http://blog.juvely.com/2007/02/12/weve-been-baking/ Two 19 year old students documenting the process of developing a web app! Wed, 19 Nov 2008 10:30:03 +0000 http://wordpress.org/?v=2.6.3 By: Luca http://blog.juvely.com/2007/02/12/weve-been-baking/#comment-18 Luca Wed, 21 Feb 2007 16:01:54 +0000 http://blog.juvely.com/2007/02/12/weve-been-baking/#comment-18 Thanks for your comment Tuomas! I started writing my own framework to begin with based upon a tutorial I found (I am afraid I don't have the URL, but I am sure a Google search will bring up plenty). It was actually quite a lot easier than I thought it would be - to start with - but things gradually got more and more complicated. I found Cake while looking for ideas of how I could do things in my own framework, but when I found Cake I thought I would give it a try. Another thing that made me go with another framework rather than my own was that we don't have to really worry about bugs that could appear in the code, as Cake is being developed by and used by (hence tested by) many people bugs will quickly appear and hopefully quickly dissapear. If we used a system we built ourself it would be up to us to find bugs and eradicate them, which would lead to less time working with Juvely. There are definately plus sides to writing your own MVC framework (and a lot of fun to be had along the way), but if you are developing an application I would say give it a miss as there are plenty of other frameworks out there that can be used - if you really can't find one that suits your needs or have an idea of how to do it better then go for it! Luca Thanks for your comment Tuomas!

I started writing my own framework to begin with based upon a tutorial I found (I am afraid I don’t have the URL, but I am sure a Google search will bring up plenty). It was actually quite a lot easier than I thought it would be - to start with - but things gradually got more and more complicated. I found Cake while looking for ideas of how I could do things in my own framework, but when I found Cake I thought I would give it a try.

Another thing that made me go with another framework rather than my own was that we don’t have to really worry about bugs that could appear in the code, as Cake is being developed by and used by (hence tested by) many people bugs will quickly appear and hopefully quickly dissapear. If we used a system we built ourself it would be up to us to find bugs and eradicate them, which would lead to less time working with Juvely.

There are definately plus sides to writing your own MVC framework (and a lot of fun to be had along the way), but if you are developing an application I would say give it a miss as there are plenty of other frameworks out there that can be used - if you really can’t find one that suits your needs or have an idea of how to do it better then go for it!

Luca

]]> By: Tuomas http://blog.juvely.com/2007/02/12/weve-been-baking/#comment-17 Tuomas Wed, 21 Feb 2007 07:24:44 +0000 http://blog.juvely.com/2007/02/12/weve-been-baking/#comment-17 Hi, How's the framework research is going on? I've been checking various php frameworks that are similar to Ruby on Rails (since I don't want to spend my time configuring mongrel & apache clusters) and then I kinda accidentally wrote my own simple MVC framework. It's nothing fancy, but it has ActiveRecord implementation and some other useful stuff. You might want to try to write your own framework first, it might be fun and when you run into problems & bugs, you know all the inner-workings of your application's framework and you know how to deal with them. But the downside is, more you spend time on framework, the less you spend time with your application... Here is another MVC framework, Akelos (http://www.akelos.org) "Akelos Framework, PHP on Rails". I haven't tried it, since it lacks documentation. I hope they fix it soon, I think it has potential. Hi,

How’s the framework research is going on? I’ve been checking various php frameworks that are similar to Ruby on Rails (since I don’t want to spend my time configuring mongrel & apache clusters) and then I kinda accidentally wrote my own simple MVC framework. It’s nothing fancy, but it has ActiveRecord implementation and some other useful stuff.

You might want to try to write your own framework first, it might be fun and when you run into problems & bugs, you know all the inner-workings of your application’s framework and you know how to deal with them. But the downside is, more you spend time on framework, the less you spend time with your application…

Here is another MVC framework, Akelos (http://www.akelos.org) “Akelos Framework, PHP on Rails”. I haven’t tried it, since it lacks documentation. I hope they fix it soon, I think it has potential.

]]>