Re: Dependeny on javax.swing

2009/12/28 Daniel Dekany <[email protected]>:
>> javax.swing.tree.*, that'd be a start. As I said, something similar
> So can that be worked around in FreeMarker (and of so, with how much

I have two concern for work around javax.swing.tree.* package reference.
1. Backword compatibility, we don't want break the stable release
stream in 2.3.X. Even NORMAL freemarker usecase won't be involved with
the swing.

2. The simple/safe way to get away from javax.swing.tree.* is to
duplicate the used classes/interface insides freemarker such as
freemarker.core.tree. It may have copyright concern to the source
code.

P.S. There are only 4 direct reference in freemarker 2.3.15, so not a
big deal to just copy them to freemarker :)
./freemarker/template/Template.java:57:      import javax.swing.tree.TreePath;
./freemarker/core/FreeMarkerTree.java:56:   import javax.swing.JTree;
./freemarker/core/FreeMarkerTree.java:57:   import
javax.swing.tree.DefaultTreeModel;
./freemarker/core/TemplateElement.java:57: import javax.swing.tree.TreeNode;

-Guo

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev