window builder work with new Eclipse "Helios" (3.6) ?

[TEMP USER]

hello,

i tried downloading the new version of Eclipse to check it out, but it seems that it cannot download&install window builder, at least not via the update URL of window builder.
can they work together?
website for downloading:
http://download.eclipse.org/eclipse/dow ... /index.php
i've found it via the eclipse blog:
http://eclipsesource.com/blogs/

[Eric Clayberg]

can they work together?

They work fine together on our end.

It would help if you were more specific about what you mean by "cannot download&install".

[TEMP USER]

well, the website of window builder says it's up to 3.5 :
http://www.instantiations.com/windowbui ... .html?id=1
so i used the link of update to 3.5:
http://download.instantiations.com/D2WB ... pdate/3.5/
now that i've checked it out again, it seems to work fine.odd.
however, it seems that the new version shows a lot of warnings about the code of window builder , and also warned me that the code was created for an older version of Eclipse. screenshot: http://yfrog.com/1220100210095638p
the warnings are of:"Class is a raw type. " , "HashMap is a raw type." , "Iterator is a raw type.", "Map is a raw type." .

[Eric Clayberg]

The 3.5 update site will work fine with 3.6. There is also a corresponding ".../3.6" update site available although we won't officially support 3.6 until it is released.

You can suppress the version warning if you like using the checkbox in that dialog.

I'm not sure what the context is of the other warnings you mention.

[TEMP USER]

the warnings are about code that window builder has written for creating the GUI at one of my programs. they are all exist only on the file of window builder and not on the one i've worked on.
anyway, i've used the @suppresswarning (or however it's written) so now they are gone.

[Eric Clayberg]

I'm not sure which file you are referring to, but the most likely cause for that would be having had your project set to JDK 1.4 compatibility when that file was created and then setting your file to JDK 1.5 compatibility or above later.

[TEMP USER]

i doubt it. there are works that i've used version 1.5 of JDK , but they didn't have any use of SWT . plus, the warnings appeared only after i installed the new Eclipse.
the version that is used in the "problematic" program is 1.6 .
here's a sample code of the file "SWTResourceManager.java" that window builder created:

Code: Select all

/**
   * Dispose of all the cached {@link Color}'s.
   */
  @SuppressWarnings("rawtypes")
  public static void disposeColors()
    {
    for(Iterator I=m_colorMap.values().iterator();I.hasNext();)
      ((Color)I.next()).dispose();
    m_colorMap.clear();
    }

if i remove the @SuppressWarnings("rawtypes") part, i get :
"Iterator is a raw type. References to generic type Iterator<E> should be parameterized"

[Eric Clayberg]

SWT Designer includes two versions of the SWTResourceManager class - one for use with JDK 1.4 and one for JDK 1.5 and above. The version that is created in your project depends on the JDK version in effect at that point in time.

The JDK 1.5/1.6 version of that method looks like this...

Code: Select all

   /**
    * Dispose of all the cached {@link Color}'s.
    */
   public static void disposeColors() {
      for (Color color : m_colorMap.values()) {
         color.dispose();
      }
      m_colorMap.clear();
   }

As you can see, it even uses JDK 1.5 syntax. If you create a new SWT project using JDK 1.6 and a new SWT app window class and then play around with fonts and colors, you should see the JDK 1.5/1.6 version of that class created for you.

[TEMP USER]

i cannot create a new project for this project. i might delete something important from it. can't window builder be compatible with its previous created files and modify them when needed?
here's the file that window builder created:
http://rapidshare.com/files/350109302/S ... nager.java

it doesn't make sense that only this project was made in version 1.5 (or 1.4), since it's not that old(and i don't think i had 1.5 when i had window builder, or even heard of it yet) , plus it's the only one that has those warnings.

[Eric Clayberg]

i cannot create a new project for this project.

Read what I wrote again. I did not suggest doing that. I am not suggesting doing anything with your current project at all.

can't window builder be compatible with its previous created files

It is compatible with its previously created files. In this case the previously created code still compiles and works just fine.

modify them when needed?

It does do exactly that. In this case, it has no need to modify that file and doesn't even have a reason to look at that file again until you do something in the design view that uses a font or color resource. If you were to actually change a font or color in the design view, it would check whether the resource manager file matches the latest version, and, if it doesn't, it would then replace the file (with the JDK 1.5 version in this case). Until you actually modify anything in the design view that uses one of those managed resources, it has no reason to change that file because it compiles and runs just fine.

here's the file that window builder created:
http://rapidshare.com/files/350109302/S ... nager.java

Sorry, but that service wouldn't let me download anything. Based on the snippet you posted earlier, that is the JDK 1.4 version of the file. That version would only be created for a JDK 1.4 project. We have tested it again on our end and confirmed that it is working correctly and as expected.

it doesn't make sense that only this project was made in version 1.5 (or 1.4)

I wasn't there when you created the project, so I can't comment. I would encourage you to try my earlier suggestion of creating a brand new SWT project using JDK 1.6 and seeing what version of the resource manager is created in that case.

[TEMP USER]

i can't find the answer in what you've written: what can i do instead of creating the whole project again?
about the "modify when needed" , i meant that new versions will take care of modifying the code so that just like earlier, it won't have any new warnings and errors.
since those warnings are new, it might have something to do with the new eclipse version, or that i just never noticed them.

[Eric Clayberg]

what can i do instead of creating the whole project again?

As suggested earlier, you can do either of the following:

1) Edit a font or color property for any widget in your current project. Once you do this, it would check whether the resource manager file matches the latest version, and, if it doesn't, it would then replace the file (with the JDK 1.5 version in this case).

2) Create a new JDK 1.5/1.6 project with a new UI class, add a widget, and change its font or color. That will cause the JDK 1.5/1.6 version of the resource manager to be generated which you can then copy to your old project.

about the "modify when needed" , i meant that new versions will take care of modifying the code so that just like earlier, it won't have any new warnings and errors.

That is exactly what it will do, if you do #1 above. Until you actually modify anything in the design view that uses one of those managed resources, it has no reason to change that file because it compiles and runs just fine.

[TEMP USER]

thanks!
method #1 seems to work like magic!
so nice. it didn't even take so long.

[Eric Clayberg]

Glad that worked for you.