yade-dev team mailing list archive

[Václav S(milauer <eudoxos@xxxxxxxx>]

> Apparently Vaclav went crazy about changes in the core without a
> month-long discussion about his plans on the mailing list ;-P
>
> So now it's his job to fix this mess. 
>
> Vaclav, I think that the simplest option for you is to restore
> old Qt3GUI, and give another name to your brand-new experimental
> always-crashing PythonQt3GUI. (the names are up to you)
>   
It is not always-crashing, I think. I know there are glitches, but there
are actually 3 things that happen, but are conceptually separate.

1. decoupling simulation from the controller, that is, retain the
controller functionality while allowing asynchronous changes of
simulation parameters - from within the simulation, from console.

2. making the qt3 gui more friendly (I think, at least - for example
taking less space on the screen) and the code cleaner. Why have dynamic
menus, if we really have just a few fixed set of things that you do? And
so on. I know qt3 gui is deprecated etc, but so is yade serialization,
so are old class names etc. And we still use them and will use them for
some time.

3. Running python console together with qt3; it doesn't affect QtGUI
except for about 5 lines. This will not, obviously, happen if you
compile without EMBED_PYTHON. Perhaps I should add an option? (so that
the console is disabled by default and people don't blame python for
crashes I caused by the two points above ;-) )

I think the the ui is quite stabilized now (buzz me if not) and I am
sorry for the difficult transition.

Vaclav
_______________________________________________
yade-dev mailing list
yade-dev@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-dev