[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jwt-dev] AW: JWT - jBPM - Bull meeting 20081121 - notes
|
>>I will ask to Rodrigue to get in touch with you on this topic through the
mailing list as Florian suggested...
Great, as Marc already suggested on another topic, all these requirements
should not only be captured via email but best also on a bug entry in
bugzilla. So, please try mainly to start the discussion via mailing list and
let the others know about the bug number (which they should be notified
automatically nonetheless if configured correctly) and then leave the
discussion mainly on the bug entry.
Concerning bugzilla: yes, it also includes bugs as well as feature requests.
Concerning the JWT roadmap: hmm, if we can include all the aspect related
things in a milestone then we could have the 0.6 release for vendors which
would include all the requirements that you guys need. What do you think
about that? Let's discuss it in a minute.
Thanks in advance,
Florian
-----Message d'origine-----
De : Christian Saad [mailto:christian.saad@xxxxxxxxxxxxxxxxxxxxxxxxxx]
Envoyé : mardi 25 novembre 2008 14:15
À : 'Miguel Valdes Faura'; 'Marc Dutoo'; 'Koen Aers'
Cc : 'Florian Lautenbacher'; 'Tom Baeyens'; 'Tom Baeyens'; 'Mickael Istria';
pierre.vigneras@xxxxxxxx Objet : AW: JWT - jBPM - Bull meeting 20081121 -
notes
Hi Miguel,
could you provide us with just a quick lineup of your requirements regarding
the palette since I'm currently planning on how to redo the view system and
therefore am very interested which demands for customization could or could
not be satisfied by views.
Things currently planned/under consideration for views are:
* Include: View ID, Translations of the View Name and a View Icon (basically
as is now but in a more consistent manner)
* Use XML format instead of serialized objects
* Include: Support for custom figures (already present, but I'd like to put
this in plugin.xml to make it easily configurable)
* Include: Support for renaming model elements and their properties
* Put standard views (business/technical) in external plugin
* Rewrite internal handling since it has become quite bloated over time
* Option to hide elements from the standard palette
* New view editor
Thanks,
Chris
