>
> You aren't making a very solid case. Writing a new Proxy class for models
> doesn't seem cleaner than using autoload, for example.
>
Yes it is cleaner, because you have to do every include manually - in the
Helper or in an extra file, like header files in C/C++. Also, the coding in
the controllers is cleaner, too.
Bill Karwin wrote:
>
> You're making the same mistake I see in nearly every programming proposal
> I read -- you've identified the solution before you've defined the
> problem, and now you're aimlessly trying to invent a reason for the
> solution you've designed.
>
I know what you mean. Maybe you're right. I defined problems before, but it
seems there are more problems. My diagrams are something like brainstorming,
to talk about it, not a full ready-to -go implementation ;)
Bill Karwin wrote:
>
> If you want to create a Proxy mechanism for the sake of practice, or if
> you just want to play, then that's fine. There's nothing wrong with
> experimentation, it's a good way of learning.
>
> However, I would point out that learning how to write a technical proposal
> is just as important a skill for professional software engineering as
> learning programming languages, design patterns, or other technology.
>
Well, i am a studied software engineer, but learning is something i will do
my whole life long...
--
View this message in context: http://www.nabble.com/Integration-of-Models-tp18985795p18989956.html
Sent from the Zend MVC mailing list archive at Nabble.com.
没有评论:
发表评论