| Re: [e4-dev] MWizard and MDialog |
So, having specific dialogs in the model seems to be a good idea, but not generic ‘dialog’ as it is done today… A general dialog asking confirmation or some information can be opened easily in an handler, and there is no objects hierarchy to manage. This is not its place in model. I tried the new implementation with a dialog and a wizard and everything has been opened at startup ! Absolutely useless. The other solution could be to stop to change application model every month and to keep the old extension point mechanism which is quiet powerful. For the moment I manage pure E4 preferences using a plugin which defines a generic handler to open the dialog, and an extension point similar to the definition in E3. This plugin is available on my github and I will probably propose to include it in E4 if there are no other solutions proposed to manage this concept. In this case, properties and wizards could be managed in the same way… Of course this plugin manage only preferences using JFace and not javafx… and it is not the ‘good’ solution. What is your opinion about it ? Le 28 mars 2014 à 18:40, Wim Jongman <wim.jongman@xxxxxxxxx> a écrit :
|