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 123348 - Merge "Find in UML Model" with "Find in Projects"
Summary: Merge "Find in UML Model" with "Find in Projects"
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: General (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@uml
Keywords: UI
Depends on:
Reported: 2007-12-04 13:31 UTC by jrojcek
Modified: 2008-08-13 15:46 UTC (History)
5 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description jrojcek 2007-12-04 13:31:50 UTC
Problem description and solution:

With the NB 6.0 pack consolidation into a single coherent piece we've achieved a pretty good simplicity and consistency of main menus. That is true also for 
the IDE with all packs installed. There's still a few things missing. One of them is special menu items for Find/Replace in UML model. Those actions are very 
similar to the Find/Replace in Project and as such should be merged together.


Note that even though I'm filing this issue as part of the 6.1 planning, the real intention is to address this issue in one of the upcoming releases.
Comment 1 George Vasick 2008-04-03 17:19:32 UTC
Comments from Trey:

In order for us to make it work, we need to have an API from the Find/Replace in Project authors.  The action can not do
a simple test replace, because our model is in memory.  Also we would need to send events to the correct listeners when
a model element changes so that it can update on the diagram.  For example if you change the name of a class, we have to
update the attributes that are of changed type.  Since the attribute simply references type, it will not get updated
until it gets an event.
Comment 2 jrojcek 2008-04-07 13:00:52 UTC
Ccing Tomas who's team develops the "Find in Projects" action.
Comment 3 Tomas Pavek 2008-04-07 17:27:48 UTC
There are both UI and technical things to clarify. From the UI point of view, should both "Find" and "Find in Project" 
actions be reused? I see no problem with "Find" as it is applied to actual selection - so if it is UML project, it can 
show its own dialog and perform its own search. "Find in Projects" searches through all opened projects - which is a 
bit tricky to define in terms of how the UML search should get involved (only if all opened projects are UML? or)...

Marian Petras can do the technical evaluation. I'd say hooking into Find action should not be difficult.
Comment 4 jrojcek 2008-04-14 14:16:49 UTC
This issue is only about merging "Find in UML Model" and "Find in Projects" actions. "Find" action should be a separate issue.

There should be just a single dialog and single action called Find in Projects. If the user types in "JPanel" the Results window should show all files, uml model 
elements and any other object from open projects containing the word JPanel. Maybe the find dialog should have UML specific options. That's TBD. That was 
the intention of the original request.
Comment 5 Marian Petras 2008-04-18 17:24:29 UTC
For your information, dialog "Find in UML Model" in badly broken when running on JDK 6 (at least on Linux) - it is
actually unusable! When running on JDK 1.5, it works but it does strange layout changes during resizing.
[32-bit Linux (Ubuntu 7.10), quad-core Intel processor]
Comment 6 Marian Petras 2008-04-18 17:27:17 UTC
The strange issues I described in my previous comment were in NB 6.1 RC2 (Build 200804170002).
Comment 7 Marian Petras 2008-04-18 17:46:28 UTC
The following are major differences between the two dialogs I have found so far:

  - "find in UML" does not search files so it is nonsense to display the file name patterns field
  - "find in UML" only searches UML models and not actually projects
  - "find in UML" uses a table view for displaying search results and the table has six UML-specific columns

Other differences that I think are not that serious:

  - "find in UML" uses special UML-related options
       ("This is an XPath Expression", "Also Search Alias", "Search in Elements/Descriptions")
  - "find in UML" uses a different approach to the selection of search scope