Re: [Modeling-users] Pythonic, and non-XML, Model description

[Sebastien B. <sbi...@us...>]

        Hi,

  A quick notes about that:

> > Can you please take a look at the attached 2 files;
> > PyModel.py -- defines the classes (signatures for) for, and documen=
ts
> > the rules for, a PyModel instance
> > sample_PyModel.py -- re-expresses the StoreEmployees model
>=20
> One thing that is a big win for Modeling is the ability to import a X=
ML
> model.  We make our models with Data Designer
> (http://www.danny.cz/datadesigner.en.html) and convert the XML to a f=
ormat
> that Modeling can easily crunch.  The performance boost of the python
> model is a big win but the ability to import, convert, compile, ... a=
 XML
> model should be kept.
>=20
> I mean, we'd like to see it in future releases.=20

As Mario already said, there's nothing to worry about. Moreover, this i=
s a
very valuable information that you gave us ; I did not succeed in linki=
ng
the db schema designer yet /: (I get a bunch of warnings about wx stuff
being undefined references) but the screenshots make me think it might =
me a
modeler really worth a try. It might be the modeler I'm looking for.

  Would you mind sharing your conversion scripts from db-designer to
  xml-modeling? I'm thinking of adding a few notes on this tool in the
  framework's documentation, and having the conversion script would be
  really handy.

I also agree with Mario saying that two (or more!) different models can
co-exist with no problem. That said it is possible that a python model,=
 if
defined, will be preferred for run-time initialization (loading the mod=
el)
since it is likely to load far quicker than parsing the xml... Whatever
the changes, you can count on a bridge between the model formats.

  Last: Mario, I have not found the time yet to study your proposal but=
 I
  will for sure.

        Cheers,

-- S=E9bastien.