Re: [javaCompiler-users] NetBeans and JSwing Layout Support and JMF Support
Status: Beta
Brought to you by:
soapy
From: Marco T. <mt...@gm...> - 2006-09-21 18:00:30
|
Joe Osborne wrote: >> Joe Osborne wrote: >>> Hello Mark > > Sorry about that Marco. > I work on my program until the sun comes up and things > look a bit hazy on the screen by that time. ;) No problem... > <snip> > > Here is the compilation output: > - compiling sources for Java 1.5 preprocessing > > C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\JavaCompilerTempa2jenm.out\MainWindow\MainList.java:24: > cannot find symbol > symbol : class ProgressMonitor > location: package swingwtx.swing > import swingwtx.swing.ProgressMonitor; > > There are 16 of these for various classes. > I take it these are the classes that I am using that > swingWT doesn't have equivalents for in it's library. swingWT mapps AWT/Swing to SWT. But not everything is mapped... http://javacompiler.mtsystems.ch/frame_faq.html, second question > So this is where I need help. > > This is what I am guessing I have to do: > 1-Get these classes as java source codes. > 2-Get the swingWT as source. > 3-Put the classes somewhere in the swingWT directory > hierarchy. (src folder) > 4-Add something to the swingWT main class so they are > seen. > 5-Compile them to a jar. > 6-Compile the jar to an object file. > 7-Replace the original swingWT object and jar files > with the ones I modified. > > Is this what I have to do? No. You have to get the swingWT source and add all classes/methods you still need. Internally you will work with SWT, but you simulate the AWT/Swing API to outside. Change directly to SWT... It's easier... >> I downloaded JMF and tried a little: >> - It needs sun classes that are not yet in gcj. You >> could add them manually. > > Where do I put them? > Do I need to make changes to any of the gcj files to > take acount of the files I add? No. Put them in a jar and add the jar to your project in JavaCompiler. This will work with most of the classes... >> - The player window uses AWT or Swing, so I guess it >> will be hard to get >> that working with swingWT. But you could try... > > Fortunately I am not using the player window. > I just create an instance of the player bean object. Even better... Marco |