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.
Summary: | Wrong design of jelly.Explorer - requirement for new component in jellytools | ||
---|---|---|---|
Product: | qa | Reporter: | Lukas Hasik <lhasik> |
Component: | Jellytools | Assignee: | issues@qa <issues> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | mmirilovic |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | TASK | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 21756 |
Description
Lukas Hasik
2002-03-20 16:57:04 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. This task is solved by jelly2. There are new operators ExplorerOperator, RepositoryTabOperator and nodes. Closing because reporter of this is out of office for a long time. |