If it works for you then by all means go with it. From my own perspective,
though, one based on my own experiences, I've found it best to adhere to
tried and true OO principles. There are always exceptions of course and
doing something in a prescribed manner without questioning the logic of
doing it that way is dangerous in its own right. However, discounting the
wisdom of sound principles is equally dangerous IMO.

One of the things I really love about developing an application is the
iterative process of going back, over and over again, over what I've
implemented and how I've implemented it and doing constant code reviews. I
am my harshest critic :)

Jeff

On Sun, Nov 28, 2010 at 12:36 PM, Rein Petersen <rein.peter...@gmail.com>wrote:

> Thanks Jeff,
>
> You're right - the way you have described is the way I should do it. But
> something bothers me about not being able to model relationships and state
> using inheritance. When I think about the problem domain, I really do want
> to model it the way I have described. I have achieved it on the client, in
> javascript, using __proto__ (you can hear the gasps of disgust) and it works
> great although undocumented and not permitted, in general, for that reason.
>
> When I was looking at the composition of the polymodel, it became clear
> that I could probably manipulate it's 'class' field to change it's type (at
> serialization to the db), without actually changing the type (in my case
> python). Afterwards, the next deserialization results in the new type.
>
> I know it breaks the rules but I actually haven't seen any rules that
> expressly say that I cannot change an object's type - in python or
> javascript or in OOP - maybe I just haven't done enough reading.
>
>
> Rein
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appeng...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
*Jeff Schwartz*

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to