 |
Home | Changes | Index | Search | Go
SwingLabs Application Framework Ideas Whiteboard
This page is to collect ideas for an "application framework" for SwingLabs.
Please writeup your comments/ideas/thoughts/requests by editing this page. Include your SwingLabs signature with your submissions. For your own comments, separate your entries from others with a horizontal rule; if you want to add a comment to someone else's ideas, write your comments in italics and add your signature. Add a heading at the top of your "section" so it will be included in the TOC.
If there are other projects that offer the feature(s) you are referring to, list them. You might also remark what you like or don't like about how those features exist in other frameworks or tools. Feel free to create sub-pages for extended discussions on a feature.
Use-cases are welcome--let everybody know what you are trying to accomplish, and how this feature would help.
If you like a feature, but have no comments to add, you can add your signature with a "+1" comment, or with a "-1" comment to indicate you're not in favor of it.
List of ideas:
Plugin Architecture
Support application plugins as NetBeans, Eclipse, jEdit do
A plugin like architecture would be nice (Something like the Eclipse RCP ?). This would give me standard extension points, so I won't have to write the same Menu bar, tool bar and status bar again and again. This would require me to structure my code as per plugin specs but will make reuse and maintenance of code easier IMO -- radzloco
A plugin architecture built on small, self contained parts that can be reused independently would be nice. Using an available OSGi framework would be a good starting point - it works for Eclipse -- Main.zuluimpi - 20 May 2005
Sounds good to me. I have created and proposed some Application framework/architecture already in 1999! I just found SwingLabs during a conference (JavaPolis?) where some guys from Sun presented it. And heard about some of NetBean?'s components supposed to be included into Swing and the JDK (6,...) also.
I would be happy to contribute some of my ideas and (where it fits in) also code and components to that -- Werner Keil, Creative Arts & Technologies - December 2005
Use existing code
rambles by josh
I'd like to see reusable list, table, and tree renderers for common things.
I'd like to see a great package of pre-fab icons
A way to organize my actions and keep them straigh
a validation framework
a binding framework
some really good example applications
a tutorial that takes me through building an entire application.
a spreadsheet component
Action management
As of .7, the container of Actions is an element called 'rootPane', and it allows for 0 or 1 toolbars and menus.
I would like to see a more abstract element be the container of actions, so that I can create an ActionContainerFactory? from a single XML document.
I would extend the ActionContainerFactory? with APIs like :
JToolBar? createToolBar(Object id)
JMenuBar? createMenuBar(Object id)
rambles by cupofjoe
Isn't this JSR 296 now?
https://tframe.dev.java.net/
Mediator framework with a simple way to register any component or action to the mediator. TFrame does this now and is one of the few things it does worth mentioning.
Has a large collection of actions/icons all built on the Sun 2nd Edition Look and Feel guide. They delegate their actions to the mediator to hook your implementation code into. Icons are very old. 
Requires you to inherit from TFrame. Have a Mediator class and it forces an order of construction.
The whole thing works without you having to do any bean or deal with custom events/listeners. "Tea Frame" has all of the cafine but no beans required. Since I wrote it I had to keep it simple. 
|