This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 88321 - Reusable/Extensible "Find" UI / infrastructure
Summary: Reusable/Extensible "Find" UI / infrastructure
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Vladimir Yaroslavskiy
URL: http://xdesign-tools.czech.sun.com:80...
Keywords:
Depends on:
Blocks: 87850 89926
  Show dependency tree
 
Reported: 2006-10-31 13:39 UTC by Michael Frisino
Modified: 2008-03-12 09:07 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Frisino 2006-10-31 13:39:58 UTC
In 5.5., the XSD and WSDL editors both make use of a similar Design view UI for
"Find". This UI is nice and we wish to do similar for BPEL Design view. However,
rather than copying sources and hacking them, or re-writing essentially much of
the same work, it seems this may be an opportunity for XML modules to provide
some reusable infrastructure and maybe UI that can be used/extended by
specialized XML language editors like BPEL.

At the very least we wish to standardize the UI. If nothing else, this RFE
should result in an HIE standard for this Find feature 
- the L&F of the UI controls.
- the L&F of the find results.

Maximally, this RFE will result in some reusable code. For instance, could we
follow the pattern already established by Refactoring system? That is one
example where NetBeans successfully propagates the reuse of a standard UI. Could
we do something similar?

There may be some limitations to what can be standard and what needs to be
specialized. For instance, the presentation of results may need to be
specialized because the highlighting approach taken by one design view may not
be the right thing for the highligthing used by another view. So I think the
result presentation may be very design view specific.

Assigning to Vladimir, to converse with XML team on expediting this.
Comment 1 Jiri Kopsa 2006-11-01 20:15:12 UTC
Just adding a test URL ... you may replace it later on with whatever you want.
Comment 2 Jiri Kopsa 2006-11-03 16:20:52 UTC
Adding "gavotte" status whiteboard (for testing of gavotte features query).
Comment 3 Vladimir Yaroslavskiy 2006-12-04 15:55:07 UTC
fixed.
Comment 4 Vladimir Yaroslavskiy 2007-02-16 14:26:44 UTC
Internal design, verified and closed.
Comment 5 Vladimir Yaroslavskiy 2007-02-16 14:27:40 UTC
Internal design: verified and closed.