Moving from JBuilder to Eclipse [message #86119] |
Fri, 08 April 2005 15:00 |
Eclipse User |
|
|
|
Originally posted by: francisc.brs.ca
Must be a popular question, but i just can't find the info...
Our current product was developed using JBuilder and we're checking how
to jump to Eclipse. The only problem is all the bunch of GUI generated
by JBuiler wich is really ugly when we open the files Swing files in VE.
Does anyone has a link or something where i could find the info?
Thanks
|
|
|
|
Re: Moving from JBuilder to Eclipse [message #86610 is a reply to message #86562] |
Mon, 11 April 2005 14:37 |
Eclipse User |
|
|
|
Originally posted by: francisc.brs.ca
Problem is we only use standard Swing components and layouts.
When opening a file in VE, that was done with JBuilder, we see the
components scattered around. All the frames are extending JFrame.
That, for some reason, VE don't like.
I tried creating classes directly with VE, extending JFrame, not
encapsulating, and i get the same result. You see the frame's head at
the top of the editor, and the components scattered but looks like list...
So, i'm not sure if the jbInit() the problem. The way i see it, VE just
doesn't like us to extend for JFrame (or others). The only it seems to
work properly is to encapsulate.
Maybe i'm wrong about that to.
Gili Mendel wrote:
> Francis Cote wrote:
>
>> Must be a popular question, but i just can't find the info...
>>
>> Our current product was developed using JBuilder and we're checking
>> how to jump to Eclipse. The only problem is all the bunch of GUI
>> generated by JBuiler wich is really ugly when we open the files Swing
>> files in VE.
>>
>> Does anyone has a link or something where i could find the info?
>>
>> Thanks
>
>
> You may be having some of the issues noted in the following:
>
> http://dev.eclipse.org/newslists/news.eclipse.tools.ve/msg02 743.html
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=82734
>
> If you have other issues, it will be great if you can include a snippet
> of code that causes these problems.
|
|
|
Re: Moving from JBuilder to Eclipse [message #86624 is a reply to message #86610] |
Mon, 11 April 2005 14:46 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Please append an example of .java file in error. That will tell us if it
is the coding pattern or if it is some other error.
--
Thanks,
Rich Kulp
|
|
|
Re: Moving from JBuilder to Eclipse [message #86666 is a reply to message #86624] |
Mon, 11 April 2005 15:34 |
Eclipse User |
|
|
|
Originally posted by: francisc.brs.ca
This is a multi-part message in MIME format.
--------------090002070307020203000402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Rich Kulp wrote:
> Please append an example of .java file in error. That will tell us if it
> is the coding pattern or if it is some other error.
>
>
First, i'm trying to convince my co workers to switch to Eclipse. This
file is from a Swing application in wich i have no implications. But i
need to find a way for that programmer to be able to continue his Swing
development for me to convince him... My boss is pressuring me to do so.
Obviously i don't send the whole project for legal reasons.
But, like i wrote in my previous email, i have seen the problem even
creating a class straight from VE. It seems to dislike extending
JFrames. Encapsulation works fine. But there are too many Swing related
files created with JBuiler, and they won't be happy if they have to
re-write the whole thing...
Thanks
--------------090002070307020203000402
Content-Type: text/plain;
name="MainMenu.java"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline;
filename="MainMenu.java"
package ca.caddy.caddyweb;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import javax.swing.border.*;
import ca.caddy.caddyweb.util.*;
import java.util.ArrayList;
import java.util.Collection;
import ca.caddy.caddyweb.fw.DataBean;
import ca.caddy.caddyweb.fw.DataBeanFactory;
import ca.caddy.caddyweb.general.client.DataBeanFactory1;
import ca.caddy.caddyweb.general.client.PermissionBean;
/*import ca.caddy.caddyweb.handicap.edit.teemarker.TeeMarkerEditIntFr ame;
import ca.caddy.caddyweb.handicap.edit.handicapclass.HandicapClassE dit;
import ca.caddy.caddyweb.handicap.edit.handicapclubcourse.*;
import ca.caddy.caddyweb.handicap.edit.membergames.MemberGameHystor yEdit;*/
import ca.caddy.caddyweb.reports.CaddyReportsIntFrame;
import ca.caddy.caddyweb.reports.CaddyReportsMaintenance;
import ca.caddy.caddyweb.edit.tournament.TournamentEditIntFrame;
import java.util.ResourceBundle;
import java.lang.reflect.*;
import ca.caddy.caddyweb.reservation.client.TeeSheetBean;
import ca.caddy.caddyweb.tools.*;
import ca.caddy.caddyweb.search.CaddySearchMainIntFrame;
import ca.caddy.caddyweb.edit.search.CaddySearchMemberPanel;
import ca.caddy.caddyweb.reservation.client.MemberClubBean;
import ca.caddy.caddyweb.status.ClientStatusDialog;
import ca.caddy.caddyweb.widgets.*;
import ca.caddy.caddyweb.edit.cart.*;
import ca.caddy.caddyweb.edit.category.*;
import ca.caddy.caddyweb.edit.club.*;
import ca.caddy.caddyweb.edit.course.*;
import ca.caddy.caddyweb.edit.crossover.*;
import ca.caddy.caddyweb.edit.draw.*;
import ca.caddy.caddyweb.edit.holiday.*;
import ca.caddy.caddyweb.edit.locker.*;
import ca.caddy.caddyweb.edit.member.*;
import ca.caddy.caddyweb.edit.member.memberimport.*;
import ca.caddy.caddyweb.edit.membertype.*;
import ca.caddy.caddyweb.edit.ninehole.*;
import ca.caddy.caddyweb.edit.refsheet.*;
import ca.caddy.caddyweb.edit.role.*;
import ca.caddy.caddyweb.edit.teesheettemplate.*;
import ca.caddy.caddyweb.edit.typetable.*;
import ca.caddy.caddyweb.edit.user.*;
import ca.caddy.caddyweb.edit.properties.club.*;
import ca.caddy.caddyweb.exception.*;
import ca.caddy.caddyweb.gridgenerator.*;
import ca.caddy.caddyweb.rnr.*;
import ca.caddy.caddyweb.pos.client.GreenFeeTableBean;
/**
* <p>Title: Main Caddy window</p>
* <p>Description: The CaddyWeb Main Menu</p>
* <p>Copyright: Copyright (c) 2002</p>
* <p>Company: Caddy Systems</p>
* @author Marc-Andr
|
|
|
|
Re: Moving from JBuilder to Eclipse [message #86912 is a reply to message #86884] |
Tue, 12 April 2005 15:53 |
Eclipse User |
|
|
|
Originally posted by: francisc.brs.ca
Thanks. I'll had to the bugs soon.
I'll try that solution for one file and see what happens.
Gili Mendel wrote:
> There are two issues with the pattern in the file above. It is
> something we should fix.
>
> 1. is https://bugs.eclipse.org/bugs/show_bug.cgi?id=48552
>
> VE currently will not parse some thing like
> this.getContentPane().setLayout(borderLayout1);
>
> As a workaround, you can select the "this.getContentPane()",
> ContextMenu->Refactor->Extract Local Variable
> It will create the following expression
> Container contentPane = this.getContentPane();
>
> Replace it with
> Container contentPane = new JPanel();
> this.setContentPane(contentPane);
>
> 2. is https://bugs.eclipse.org/bugs/show_bug.cgi?id=91138
>
> VE will not model a border interface by default. You can force it to
> model it by either:
> changing decleration like these:
> private Border border1;
> to
>
> private Border ivjborder1;
> or
> private Border border1; // @jve:decl-index=0
>
> Adding ivj in front of the decleration, or the @jve: comment will force
> the modeling of a border interface.
>
> You can add yourself to these bugs if you want to. The more interest
> there is for a particular bug, the higher it gets prioritized.
|
|
|
|
Re: Moving from JBuilder to Eclipse [message #607107 is a reply to message #86562] |
Mon, 11 April 2005 14:37 |
Eclipse User |
|
|
|
Originally posted by: francisc.brs.ca
Problem is we only use standard Swing components and layouts.
When opening a file in VE, that was done with JBuilder, we see the
components scattered around. All the frames are extending JFrame.
That, for some reason, VE don't like.
I tried creating classes directly with VE, extending JFrame, not
encapsulating, and i get the same result. You see the frame's head at
the top of the editor, and the components scattered but looks like list...
So, i'm not sure if the jbInit() the problem. The way i see it, VE just
doesn't like us to extend for JFrame (or others). The only it seems to
work properly is to encapsulate.
Maybe i'm wrong about that to.
Gili Mendel wrote:
> Francis Cote wrote:
>
>> Must be a popular question, but i just can't find the info...
>>
>> Our current product was developed using JBuilder and we're checking
>> how to jump to Eclipse. The only problem is all the bunch of GUI
>> generated by JBuiler wich is really ugly when we open the files Swing
>> files in VE.
>>
>> Does anyone has a link or something where i could find the info?
>>
>> Thanks
>
>
> You may be having some of the issues noted in the following:
>
> http://dev.eclipse.org/newslists/news.eclipse.tools.ve/msg02 743.html
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=82734
>
> If you have other issues, it will be great if you can include a snippet
> of code that causes these problems.
|
|
|
|
Re: Moving from JBuilder to Eclipse [message #607111 is a reply to message #86624] |
Mon, 11 April 2005 15:34 |
Eclipse User |
|
|
|
Originally posted by: francisc.brs.ca
This is a multi-part message in MIME format.
--------------090002070307020203000402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Rich Kulp wrote:
> Please append an example of .java file in error. That will tell us if it
> is the coding pattern or if it is some other error.
>
>
First, i'm trying to convince my co workers to switch to Eclipse. This
file is from a Swing application in wich i have no implications. But i
need to find a way for that programmer to be able to continue his Swing
development for me to convince him... My boss is pressuring me to do so.
Obviously i don't send the whole project for legal reasons.
But, like i wrote in my previous email, i have seen the problem even
creating a class straight from VE. It seems to dislike extending
JFrames. Encapsulation works fine. But there are too many Swing related
files created with JBuiler, and they won't be happy if they have to
re-write the whole thing...
Thanks
--------------090002070307020203000402
Content-Type: text/plain;
name="MainMenu.java"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline;
filename="MainMenu.java"
package ca.caddy.caddyweb;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import javax.swing.border.*;
import ca.caddy.caddyweb.util.*;
import java.util.ArrayList;
import java.util.Collection;
import ca.caddy.caddyweb.fw.DataBean;
import ca.caddy.caddyweb.fw.DataBeanFactory;
import ca.caddy.caddyweb.general.client.DataBeanFactory1;
import ca.caddy.caddyweb.general.client.PermissionBean;
/*import ca.caddy.caddyweb.handicap.edit.teemarker.TeeMarkerEditIntFr ame;
import ca.caddy.caddyweb.handicap.edit.handicapclass.HandicapClassE dit;
import ca.caddy.caddyweb.handicap.edit.handicapclubcourse.*;
import ca.caddy.caddyweb.handicap.edit.membergames.MemberGameHystor yEdit;*/
import ca.caddy.caddyweb.reports.CaddyReportsIntFrame;
import ca.caddy.caddyweb.reports.CaddyReportsMaintenance;
import ca.caddy.caddyweb.edit.tournament.TournamentEditIntFrame;
import java.util.ResourceBundle;
import java.lang.reflect.*;
import ca.caddy.caddyweb.reservation.client.TeeSheetBean;
import ca.caddy.caddyweb.tools.*;
import ca.caddy.caddyweb.search.CaddySearchMainIntFrame;
import ca.caddy.caddyweb.edit.search.CaddySearchMemberPanel;
import ca.caddy.caddyweb.reservation.client.MemberClubBean;
import ca.caddy.caddyweb.status.ClientStatusDialog;
import ca.caddy.caddyweb.widgets.*;
import ca.caddy.caddyweb.edit.cart.*;
import ca.caddy.caddyweb.edit.category.*;
import ca.caddy.caddyweb.edit.club.*;
import ca.caddy.caddyweb.edit.course.*;
import ca.caddy.caddyweb.edit.crossover.*;
import ca.caddy.caddyweb.edit.draw.*;
import ca.caddy.caddyweb.edit.holiday.*;
import ca.caddy.caddyweb.edit.locker.*;
import ca.caddy.caddyweb.edit.member.*;
import ca.caddy.caddyweb.edit.member.memberimport.*;
import ca.caddy.caddyweb.edit.membertype.*;
import ca.caddy.caddyweb.edit.ninehole.*;
import ca.caddy.caddyweb.edit.refsheet.*;
import ca.caddy.caddyweb.edit.role.*;
import ca.caddy.caddyweb.edit.teesheettemplate.*;
import ca.caddy.caddyweb.edit.typetable.*;
import ca.caddy.caddyweb.edit.user.*;
import ca.caddy.caddyweb.edit.properties.club.*;
import ca.caddy.caddyweb.exception.*;
import ca.caddy.caddyweb.gridgenerator.*;
import ca.caddy.caddyweb.rnr.*;
import ca.caddy.caddyweb.pos.client.GreenFeeTableBean;
/**
* <p>Title: Main Caddy window</p>
* <p>Description: The CaddyWeb Main Menu</p>
* <p>Copyright: Copyright (c) 2002</p>
* <p>Company: Caddy Systems</p>
* @author Marc-Andr
|
|
|
|
Re: Moving from JBuilder to Eclipse [message #607126 is a reply to message #86884] |
Tue, 12 April 2005 15:53 |
Eclipse User |
|
|
|
Originally posted by: francisc.brs.ca
Thanks. I'll had to the bugs soon.
I'll try that solution for one file and see what happens.
Gili Mendel wrote:
> There are two issues with the pattern in the file above. It is
> something we should fix.
>
> 1. is https://bugs.eclipse.org/bugs/show_bug.cgi?id=48552
>
> VE currently will not parse some thing like
> this.getContentPane().setLayout(borderLayout1);
>
> As a workaround, you can select the "this.getContentPane()",
> ContextMenu->Refactor->Extract Local Variable
> It will create the following expression
> Container contentPane = this.getContentPane();
>
> Replace it with
> Container contentPane = new JPanel();
> this.setContentPane(contentPane);
>
> 2. is https://bugs.eclipse.org/bugs/show_bug.cgi?id=91138
>
> VE will not model a border interface by default. You can force it to
> model it by either:
> changing decleration like these:
> private Border border1;
> to
>
> private Border ivjborder1;
> or
> private Border border1; // @jve:decl-index=0
>
> Adding ivj in front of the decleration, or the @jve: comment will force
> the modeling of a border interface.
>
> You can add yourself to these bugs if you want to. The more interest
> there is for a particular bug, the higher it gets prioritized.
|
|
|
Powered by
FUDForum. Page generated in 0.04613 seconds