Hi Eric, As a matter of fact right after e-mailing my last response, I figured it out. It now seems easy enough and I've gone ahead and implemented a VERY basic MVC model yet not fully-fledged ZF MVC. I setup a bootstrap and am currently funneling requests to scripts, then breaking off the code (on my own) into separate actions and OO classes. I feel very comfortable with this and am quite happy with the direction.
It was just that initial hump of understanding what was going on with the view and layout class that got be stumped, but it's coming along nicely. I'm actually quite excited with what I've come up with - it's *extremely* flexible now that I've got it setup properly. I would like to add however that I find an almost paradoxical notion in ZF. It's claimed that the parts can be split-off and re-used in any way to remain flexible, but in reality what I found in my initial testing/learning phase was that people just kept telling me that proper MVC was easier. The paradox is that there are claims that they can be used as standalone but ultimately you are driven to just using MVC - which for developers who are trying to take baby-steps into DRYing up their current sites, requires a complete re-code - which seems unavoidable. Basically it seems very biased towards MVC; perhaps a natural or even intended effect! Either way now I'm on a roll but before. I think the community would be better served by producing a manual for standalone use of each module. This would increase the frameworks use by allowing people to become familiar with the modules on their current projects (which are most likely NOT MVC). Basically, I'm hoping to push for better support for standalone use - that's all. David :-) On Mon, May 5, 2008 at 11:00 AM, Eric Marden <[EMAIL PROTECTED]> wrote: > > Yeah, well I guess I'm trying to break away from procedural while not > foraying 100% into MVC. > > In my opinion you are making this much harder on yourself than you need > to. Full Stack MVC is going to be easier with a framework, as the components > are designed to work together. Breaking parts of it out on its own almost > requires you to be MORE familiar with the MVC pattern than if you were just > go with the flow and figure out how it all works together. > > Also you may find it easier to make the jump from procedural to just > organizing your code in classes. Once you get the power of an Object > Oriented approach, then you can research design patterns and how to better > organizing your classes. > > YMMV, > > > -- > Eric Marden > > > > -- David Di Biase
