[news.eclipse.tools.ve] Re: Jlabel border

[Pierre Abel <abel@xxxxxxxxxxx>]

Gili and Shri,
Thanks for the quick answer...

Gili Mendel wrote:

> > Now my question:
> > Is there a way to remove the JLabel border that is displayed in the 
> > editor ?
> > I understand that this fake border is displayed to know how many 
> > spaces the JLabel uses, but it would be very nice if you can remove 
> > it to have a real WYSIWYG view of your component.. Currently I'm 
> > using VE to do some high level prototyping and I need a good visual 
> > feedback without the need of running the program each time.
>
> That is a good point; we have been struggling with what/when to put 
> borders around things.
> We plan to make borders as an option in the future.
yes an option would be nice!

> > Ps: some feedback from my experience
> > 1-> I've got problems installing VE because the JVM that was assigned 
> > to my project was 1.3.1 . I've read the requirements (JVM version 
> > >1.4.2) but I thought it was only for the JVM that was used by 
> > eclipse program...
>
>
> We have not tested with 1.3.1 based project - its a bug 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=105805
> ... note that Sun has started the End Of Line (EOL) process for 1.3.1.
The point was that it was not clear in the requirements specified in the 
download page that it is your project that need the JVM 1.4.2  (and not  
only eclipse ). Now it seems really lofic to me since there is code 
generation but at that time i didn't figure out! My problem  was just 
because my default JVM was 1.3.1 (because I work sometimes with projects 
that have been only validated with 1.3.1)...but really don't worry I 
think it's a minor problem

> > 2--> a minor usability feature: when creating a jlabel, it could be 
> > nice to have the jlabel directly in editing text mode (since most of 
> > the times, when you create a jlabel, immediately after you set the 
> > jlabel's text)
>
> That's a good idea.  It may make sense to make it as an option on the 
> (optional) instance name dialog that comes up on the drop.  That way 
> we are not forcing one to enter text after the drop.

yes, and you can generalize to all components that have a text field 
(like checkboxes...)

Pierre