Was looking at how EXIN-240 was implemented in ReportProblemWizard and I
noticed some things that raised some questions. Would be good to hear
the answer to them ;)
1) Custom Preferences?
I noticed org.jboss.tools.common.model.ui.reporting.ReportPreference
was used - what are these Preference things ? It looks similar to
Eclipse Preferences but I have a feeling that is not the case...what are
they and why are the "path" hardcoded to "Struts Studio" ?
Why aren't these just normal eclipse properties ?
Where are they stored ?
How can the user toggle them ?
2) ATT_ATTACH_REDHAT_LOG and ATT_ATTACH_ECLIPSE_LOG
What is REDHAT_LOG ?
Why aren't these attributes used for anything ?
Attaching the eclipse log would be an relavant option.
3) What is AbstractQueryWizard ? The dialog extends it but what does it
help with ?
4) The layout looks weird on linux - the right side of all the text
fields are chopped of (the dialog is to narrow) - note commenting out
the hard coded getPreferredSize did not help, it just made it worse.
5) what is XAttributeSupport ?
> But does it have to load *everything* ?
Meta model loads initially only declarations.
Preferences model is loaded completely, but it does not necessarily
loads struts and jsf plugins (I need check it).
It certainly can be improved by separating
into parts which will be loaded only on request to respective plugins.
> what do you mean by UI Strings ?
Labels for input fields, titles for dialogs etc.
For instance .meta defines an action, and if it neads a dialog,
.properties bind to that action dialog title.
Another example, .meta defines object attribute, and
.properties bind to it human friendly name to be used
in dialogs and forms.
Hi Denis and Mikhael,
Any chance that you guys could give a quick description of trying out
the new features in the seam project wizard and hibernate diagram viewer
? Currently I can't seem to make it run so would like to get a few
tips/hints on what I need to do to make it work.
Just noticed this one in commits:
No longer launches twiddle as its own process.
and the code is now using classloaders inside the eclipse process to get
the launch going.
I know this is tempting to do (I did it myself in hibernate tools) BUT I
wan't to remove it again simply because it very easily result in leaks.
e.g. the current code does not use a finally block to clean up its
classloader (p.s. it also seem to use hardcoded paths to the jbossas
Was the twiddle launch really a heavy thing or ?