🚀 go-pugleaf

Jeroen:

It's not that simple as you don't have all the source (where it dives
into dataset, etc.).

One other cause for that particular method is that I don't think
package renamer is aware of the exceptions to the renaming in JFC. 
For example, almost everything moved to javax, but L&F stuff didn't
(and some was moved to a different deliverable).  So, if you rename
from com.sun.* to javax.swing.*, all your UI L&F code gets the new
name which is the wrong name in the new hierarchy.  I'm not sure how
well it handles other ambiguities created by javax based on your
imports.  For example, if you have an import java.util.* and a
java.awt.* and a reference to a List object in the code, you have an
automatic ambiguity in your code after the rename.

-Rich

Jeroen Zwartepoorte wrote:
> 
> Hi,
> 
> Can i recompile the dbSwing source (after running PackageRenamer to
> convert the "import com.sun.java.swing.*;" to "import javax.swing.*")
> and then distribute that with my jdk1.2 application?
> 
> Right now, when i try to use dbSwing components with jdk1.2 it
> complaints that it can't find the com.sun.java.swing package.
> 
> Do we have to recompile it ourselves? Or will Inprise come with an
> update soon?
> 
> Jeroen Zwartepoorte
> Jeroen@xs4all.nl

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=