PRADO is the php equivolent to save asp.net. I think that it has some potential for specific developers, especially as a gui gets built to harness the ease of use that type of approach gives developers. But the overhead for going back to the server for each action is something I rarely see as a good thing unless you are doing intranet sites. There are ways to optimize as in asp.net with disabling viewstate but in the long run I see most scripting languages going this way.
Sometimes i find it easy to develop my own framework than using other's.
First i don't have to study that framework.
Second, sometimes these frameworks are a kill for an application
Third, as a developer i find it better to create and use my own frameworks and when i have enough information then to use other frameworks. Because then i'll know what's going on.
its same as learning HTML on dreaweaver, which completes it for you and fter the newbies don't know what to do.
Pear is great, but problem comes in when have to install it. i have seen many people (including me) just getting lost in process of installing Pear. becasuse to use one package you got to install whole Pear thingy.
and sorry clenard, i din't see the link. i think i need coffee.
^ it's alright... i agree with you for the most part - but some frameworks just make life easier in the long run... Prado is a good example - not sure how to explain it - it's just REALLY good Framework if you play with it... but yeah - much like Dreamweaver - it doesn't help newbies out too much.
Al - def. take a look... they're trying to show that PHP can take on languages such as Java and .NET with those kinds of projects - and doing a d@mn good job :)
Frameworks are great. I will concede the fact that for enterprise level solutions you need something that is not home grown.
My whole issue with what some of what PRADO does is that for the view it wants to handle all server object's (textbox etc) actions at the server. And to keep state it needs to pass all the selected values for all those server objects on each return visit and it is A LOT of additional bandwidth for high traffic sites. I know there are work arounds and I admit I'm no expert, just issues I have with asp.net as well
BTW for .net UIP is a great framework, but that is a discussion for a seperate forum ;)
hey AL... I haven't been here for a while due to family things - but I agree with Prado and the view handling... now they've finally put AJAX into the Framework (although it's not as smooth as say.... RoR) and hopefully soon things will be much better! :)
PRADO looks very interesting. I haven't seen it before, but I'm going to keep an eye on it and maybe even try it out with a few simple apps. Thanks for the info!
I have developed my own framework over the years, but it's difficult and cumbersome to keep a huge, complex set of classes and rules updated and secure all alone! Although, I'm using my framework and variants of it in a large number of sites - from complex intranet apps to high volume web sites - so it's not exactly something I'll be letting go of anytime soon. :)
I usually steer clear of PEAR; not that it's a bad thing, but requiring PEAR on the server and all packages updated just gives me a bad rub. While my classes are nowhere near JAVA-like strictness and lab quality OOP methodology, they are fast, safe, and dead easy to implement.
I've actually thought about GPL'ing my template class to foster interest and improve it. I fear the direction it might take, though, as well as the fact that I'm using it in a number of systems and is part of a valuable asset for my company.
Who knows though, if there was enough interest for a single file, simplicity of implementation oriented template class (think rFastTemplate) I would begin to consider it a bit more seriously. :)