dynamic [was: Re: [Modeling-users] Using modeling framework in long run]

[Mario R. <ma...@ru...>]

On Jul 19, 2004, at 9:00 PM, Sebastien Bigaret wrote:
> the framework does not anymore relies that heavily on code
> generation, but how could you know since this hasn't been publicly
> announced yet :/ ... (esp. because it's not fully documented)
>
> --> dynamic, on-the-fly creation of package is available in the last
>     release 0.9pre17; look for a file named doc/README.dynamic.txt,  
> also
>     available here:
> http://cvs.sourceforge.net/viewcvs.py/modeling/ProjectModeling/ 
> Modeling/doc/README.dynamic.txt?rev=1.1&view=auto

I have just played with this, just very little... what I'd like to know  
more about is why the 3 ways of using Modeling.dynamic? It is not clear  
to me... and:
- it seems more code complications, that someone must maintain ;(
- more documentation, that someone must write, and maintain ;(
- more documentation, that someone must understand ;(
- not pythonic... as "there is no clear and obvious way to do it"...

When you get the time, could you say a little more about the rationale  
for these 3 ways, and, if these ways are not explorative and temporary  
(will "standardize" on one way in the future...), what are the  
advantages of one way over another, and when would you use one and not  
the other?

> Using that feature allows you to bypass the modification of the needed
> code since dynamic generation will always use your model to dynamically
> create your classes.  Just a little note, Ernesto Revilla reported some
> problems regarding properties and inheritance, so you may not want to
> use properties right now; more details in Ernesto's original post here:
> https://sourceforge.net/mailarchive/forum.php? 
> thread_id=5035017&forum_id=10674

These problems apply only to the first way, or to all three?

>   Feel free to ask for more if some points remain obscure!

;-)

mario