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 21754 - Wrong design of jelly.Explorer - requirement for new component in jellytools
Summary: Wrong design of jelly.Explorer - requirement for new component in jellytools
Status: CLOSED FIXED
Alias: None
Product: qa
Classification: Unclassified
Component: Jellytools (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@qa
URL:
Keywords:
Depends on:
Blocks: 21756
  Show dependency tree
 
Reported: 2002-03-20 16:57 UTC by Lukas Hasik
Modified: 2002-08-07 08:35 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Hasik 2002-03-20 16:57:04 UTC 
What is Explorer ? 
A frame with a JTree inside, right ? You can push popup on JTree, expand,
collapse it and that's all.
Well I'm missing such component in Jello, Jam or whatever. 

IMHO if there was such component then design of Explorer have to be changed.
IMHO jelly.Explorer should extend this new component. I understand that
jelly.Explorer is written to work just with Explorer in NB but what about the
others Explorer like frame in NB ? See Explorer from here, Customize Workspaces
... these frames looks just like really simple Explorer(and they are ;).


Why I need it ?
I'd like to work with such frames containing just jtree. ;)
I really need for my tests....
Comment 1 Jiri Skrivanek 2002-03-21 08:43:19 UTC 
Well, if I understand, you are looking for better support of nodes in
jellytools.
There is already such support. You can handle node in Customize
Workspaces frame for example this way:

        JamFrame wrksp = new JamFrame("Explorer [Workspaces]");
        FrameNode node = new FrameNode(wrksp, "Workspaces");
        node = node.getChild("Running");
        node.expand();
        node.getActions().copy();
        node.properties();

Implemented approach has some drawbacks and that is why we are
thinking about node support improvements.
I am changing to TASK P3.
Comment 2 Jiri Skrivanek 2002-08-07 08:27:36 UTC 
This task is solved by jelly2. There are new operators
ExplorerOperator, RepositoryTabOperator and nodes.
Comment 3 Jiri Skrivanek 2002-08-07 08:35:45 UTC 
Closing because reporter of this is out of office for a long time.