Hi All,
2009/10/24 Yarko Tymciurak <[email protected]>:
> On Fri, Oct 23, 2009 at 11:09 PM, mdipierro <[email protected]> wrote:
>>
>> It seems to me this would move us completely in the wrong direction.
>
> First, since you are not writing in context, I will guess you are talking
> about the concept that suiato presented of all [model, view, controller] in
> on class.
if you insist, replacing 'class' with 'module' in my previous writing
will become another way to doing it.
use of classes, however, is of course nothing wrong, though. thinking
of creating a system like gluon without classes would be a nightmare.
java without classes is unthinkable, of course. there're good reasons
to use them like encapsulation, inheritance, sanitary namespace,
portability, refactoring, etc.
> This concept as is, is simply not workable, as you can see from simple
> "units" analysis - models and controllers are Python code; views are /
> consist of html/template code (different base).
> I agree with massimo that it makes no sense to organize this particular way.
i added myP.view() because i casually thought {{... myP.view() ...}}
would works. but, i may be mistaken. in that case, the 'view' part'd
better be dropped. thought of returning myP.view() in myctrl.py (a
controller), but i'm not sure if it's a good way.
just saw mr.freeze's post which looks like showing a solution.
Cheers,
Teru
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
