Hi Mike,
I've been a bit pressed on time in the last few weeks, So I didn't
have the time to try WOLips 2 before. After all, it always take half
a day to upgrade that stuff and I wasn't enthusiastic on 80MB of
other dependencies. But now I finally got around to trying it out.
Total, absolute congratulations for your work (and Ulrichs too, of
course, this does without saying:)! It's really, really, truly great!
After clicking around a bit, I found a few tiny little issues and
also have a few suggestions. I'm posting them here for discussion first:
- WOValidation:
- void action methods are not supported (public void foo() {}),
but are legal
- action bindings: content assist does not show only void and
WOActionResults methods
- "foo-bar" = "baz" is flagged as an error, but legal for WO
- foo-bar = "baz" is flagged as an error, but legal for WO
- the small error flags (right to the scrollbars) which give you
an overview of the file are missing
- I'm getting quite a few "The class bla is either missing or not
a subclass of WOElement" even
though the class is not missing and is a subclass of WOElement?
Not sure where this comes from.
This happens intra- and inter-project wise.
- hover tooltip for the error description is missing
- /*...*/ comments are not handled (everything after it is ignored)
- in general, the parser should recover after an error and not
bail out and ignore the rest. I have custom bindings like:
DeliverableDetail: WOSwitchComponent {
...
images=#deliverableImages;
}
and everything after that is ignored and thus flagged as an error.
- the WO .wod parser does not seem to mind if the last entry does
not have a ; only a }. You might want to make this a warning only.
- the .api seems to get cached: if you change it externally, the
old messages are still displayed. Only re-building the project helps.
- These should not quietly be eaten up, but flagged as errors:
org.objectstyle.wolips.core.resources.types.api.ApiModelException:
Failed to parse API file /Volumes/Home/Jobs/gaia/Base/components/
TextComponent.api.
- WODEditor
- a "Show in Package explorer" would be nice for the components
- a context command "Open with WOBuilder" would be nice
- when you select a component class name a "F3" "Open Component"
analogous to the Java shortcut would be nice
- the "Related" view is empty when you are on a component tab
- the API>"Validation" and API>"Display" are empty
- a "Quickfix->Remove" would be nice if an entry is in the .wod
but not in the HTML
- a "Text/Form" switch in the .api would be nice, as validation
can't be entered currently.
- saving is a bit confusing, when you make a change in the .wod
and the doc is marked as dirty, then click in the .html and press
save, the save doesn't happen
- Related view
- should offer alternative ways of opening (Text, WOBuilder,
WODEditor etc).
- General stuff
- the Code uses assert() which is available only in JDK 5... I
fixed that in CVS
- Profiling did not even start, I fixed that in CVS:
java.lang.NoClassDefFoundError: org/objectstyle/wolips/launching/ui/
CommonWOArgumentsTab
- Profiling takes an age to start up, even on small projects? I
assume that it's waiting on a network timeout. After that most stuff
works except for the AWT based view which kill Eclipse.
Again, great stuff!
Cheers, Anjo
This archive was generated by hypermail 2.0.0 : Thu Oct 13 2005 - 09:57:53 EDT