| VE 1.0 Plans [message #20196] |
Fri, 20 February 2004 02:42  |
Eclipse User |
|
|
|
Hello,
Is there a plan document for the 1.0 version of VE?
Francesc Rosés
|
|
|
|
|
|
|
| Re: VE 1.0 Plans [message #21346 is a reply to message #21325] |
Fri, 27 February 2004 09:29  |
| Eclipse User |
|
|
|
I'd recommend reading my article "Effective Layout Management" to avoid
using BarfBag. You can get a much cleaner/maintainable design this
way...
See
http://developer.java.sun.com/developer/onlineTraining/GUI/A WTLayoutMgr
Note that when I wrote it BoxLayout didn't exist. The parts of the
example that use BarfBag can be very easily done with a nested BoxLayout
(off the top of my head):
Panel [BoxLayout(X_AXIS)]
h-strut
FileDisplay
h-strut
Panel [BoxLayout(Y_AXIS)]
v-glue
Button("-->")
v-strut
Button("<--")
v-glue
h-strut
FileDisplay
h-strut
That simple design replaces a 6-component BarfBag, which requires 66
constraint settings...
I gave a talk at JavaOne based on the article, and you can get the
slides at
http://www.javadude.com/articles/javaone/Effective%20Layout%
20Management.zip
These slides talk about the BoxLayout design a bit.
SpringLayout may make things even easier, though I haven't played with
it yet.
If you're using BoxLayout, take a look at my BoxBeans, which can be used
in visual builder tools to help adjust components to stretch/shrink
appropriately. (http://javadude.com/tools). I haven't tried them in VE,
though, but they should work.
Of course I wouldn't recommend wholesale redesign for all of your
existing screens, but you could slowly rework them to reduce your
dependency on BarfBag.
Later,
-- Scott
In article <c1muem$eh3$1@eclipse.org>, andreas.wuertz@information-
factory.com says...
> How about better support for GridBagLayouts?
>
> For me and my thousands of dialogs/panels, this is by far the most-used
> Layout. In VisualAge you drag components within the layout to put them into
> different cells. This does not seem to work in VE. Actually it makes working
> with VE quite painful. Any plans on that?
>
> Cheers and thanks for the good work
|
|
|
| Re: VE 1.0 Plans [message #21354 is a reply to message #21346] |
Fri, 27 February 2004 09:54 |
| Eclipse User |
|
|
|
Thanks for the info, but it doesn't really help me, because:
- I have over 1000 dialogs/panels that I cannot/do not want to completely
redesign, but have to maintain from time to time (i.e once every year)
- I am not sure if nesting panels just for layout purposes should be the way
to go (of course, sometimes it is inevitable)
- BoxLayouts do not exist in Java1, but we are still supporting MacOS 9
- I really love GridBagLayouts - under VisualAge, they are quite easy to use
:-)
Cheers
Andy
"Scott Stanchfield" <scott@javadude.com> schrieb im Newsbeitrag
news:MPG.1aa91e70637e134298969f@news.eclipse.org...
> I'd recommend reading my article "Effective Layout Management" to avoid
> using BarfBag. You can get a much cleaner/maintainable design this
> way...
>
> See
> http://developer.java.sun.com/developer/onlineTraining/GUI/A WTLayoutMgr
>
> Note that when I wrote it BoxLayout didn't exist. The parts of the
> example that use BarfBag can be very easily done with a nested BoxLayout
> (off the top of my head):
>
> Panel [BoxLayout(X_AXIS)]
> h-strut
> FileDisplay
> h-strut
> Panel [BoxLayout(Y_AXIS)]
> v-glue
> Button("-->")
> v-strut
> Button("<--")
> v-glue
> h-strut
> FileDisplay
> h-strut
>
> That simple design replaces a 6-component BarfBag, which requires 66
> constraint settings...
>
> I gave a talk at JavaOne based on the article, and you can get the
> slides at
>
> http://www.javadude.com/articles/javaone/Effective%20Layout%
> 20Management.zip
>
> These slides talk about the BoxLayout design a bit.
>
> SpringLayout may make things even easier, though I haven't played with
> it yet.
>
> If you're using BoxLayout, take a look at my BoxBeans, which can be used
> in visual builder tools to help adjust components to stretch/shrink
> appropriately. (http://javadude.com/tools). I haven't tried them in VE,
> though, but they should work.
>
> Of course I wouldn't recommend wholesale redesign for all of your
> existing screens, but you could slowly rework them to reduce your
> dependency on BarfBag.
>
> Later,
> -- Scott
>
>
> In article <c1muem$eh3$1@eclipse.org>, andreas.wuertz@information-
> factory.com says...
> > How about better support for GridBagLayouts?
> >
> > For me and my thousands of dialogs/panels, this is by far the most-used
> > Layout. In VisualAge you drag components within the layout to put them
into
> > different cells. This does not seem to work in VE. Actually it makes
working
> > with VE quite painful. Any plans on that?
> >
> > Cheers and thanks for the good work
|
|
|
| Re: VE 1.0 Plans [message #21386 is a reply to message #21354] |
Fri, 27 February 2004 16:40 |
| Eclipse User |
|
|
|
That's cool. Just keep these ideas in mind when designing new screens or
making significant changes to old screens. Much simpler.
Of course eventually VE will have better BarfBag support, as will
Penumbra when I release it (don't ask when -- don't know yet).
Later,
-- Scott
In article <c1nlg6$ejh$1@eclipse.org>, andreas.wuertz@information-
factory.com says...
> Thanks for the info, but it doesn't really help me, because:
>
> - I have over 1000 dialogs/panels that I cannot/do not want to completely
> redesign, but have to maintain from time to time (i.e once every year)
> - I am not sure if nesting panels just for layout purposes should be the way
> to go (of course, sometimes it is inevitable)
> - BoxLayouts do not exist in Java1, but we are still supporting MacOS 9
> - I really love GridBagLayouts - under VisualAge, they are quite easy to use
> :-)
>
> Cheers
> Andy
>
> "Scott Stanchfield" <scott@javadude.com> schrieb im Newsbeitrag
> news:MPG.1aa91e70637e134298969f@news.eclipse.org...
> > I'd recommend reading my article "Effective Layout Management" to avoid
> > using BarfBag. [...]
|
|
|
|
|
|
|
|
|
|
| Re: Create SWT Re: VE 1.0 Plans [message #23267 is a reply to message #23260] |
Sat, 06 March 2004 10:30 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Right now you have to include "SWT Container" from the java build page
Add library button. That is the only way we currently recognize SWT.
Just adding SWT.jar to the build path doesn't work for VE.
--
Thanks, Rich Kulp
|
|
|
|
|
| Re: VE 1.0 Plans [message #582335 is a reply to message #20235] |
Tue, 24 February 2004 09:05 |
| Eclipse User |
|
|
|
Francesc Rosés wrote:
> Hello,
>
> I observe the major efforts are in the SWT area. We can't
> expect enhancements in the tool behavior nor the Swing support?
> For example, the word "performance" don't appears, but I observed
> better performance in the 1.0 integration builds...
>
> Francesc
>
> Jeff Myers wrote:
>
>
>>The Visual Editor's 1.0.0 Line Item Objectives (i.e. plan) is available
>>here:
>>
>
> http://dev.eclipse.org/viewcvs/indextools.cgi/%7Echeckout%7E /vep-home/WebContent/docs/v1.0.0/line-items/index.htm
>
>
>> - Jeff
>
>
>>Francesc Rosés wrote:
>>
>>>Hello,
>>>
>>> Is there a plan document for the 1.0 version of VE?
>>>
>>> Francesc Rosés
>>>
>
>
>
There are three major goals for v1.0.0:
1. Start with SWT support (as noted above)
2. Improve performance.
o Reduce code path
o Reduce the need for a reload from scratch
o Perform most of the bottom up updates in the background.
We have made some advances on the 1st bullet, but have much to go on.
We have not started on the last two bullets.
3. v3 Eclipse
|
|
|
| Re: VE 1.0 Plans [message #582634 is a reply to message #20668] |
Fri, 27 February 2004 03:20 |
| Eclipse User |
|
|
|
How about better support for GridBagLayouts?
For me and my thousands of dialogs/panels, this is by far the most-used
Layout. In VisualAge you drag components within the layout to put them into
different cells. This does not seem to work in VE. Actually it makes working
with VE quite painful. Any plans on that?
Cheers and thanks for the good work
Andy
"Gili Mendel" <mendelgili@netscape.net> schrieb im Newsbeitrag
news:c1flgt$8gk$1@eclipse.org...
> Francesc Ros
|
|
|
| Re: VE 1.0 Plans [message #582679 is a reply to message #21325] |
Fri, 27 February 2004 09:29 |
| Eclipse User |
|
|
|
I'd recommend reading my article "Effective Layout Management" to avoid
using BarfBag. You can get a much cleaner/maintainable design this
way...
See
http://developer.java.sun.com/developer/onlineTraining/GUI/A WTLayoutMgr
Note that when I wrote it BoxLayout didn't exist. The parts of the
example that use BarfBag can be very easily done with a nested BoxLayout
(off the top of my head):
Panel [BoxLayout(X_AXIS)]
h-strut
FileDisplay
h-strut
Panel [BoxLayout(Y_AXIS)]
v-glue
Button("-->")
v-strut
Button("<--")
v-glue
h-strut
FileDisplay
h-strut
That simple design replaces a 6-component BarfBag, which requires 66
constraint settings...
I gave a talk at JavaOne based on the article, and you can get the
slides at
http://www.javadude.com/articles/javaone/Effective%20Layout%
20Management.zip
These slides talk about the BoxLayout design a bit.
SpringLayout may make things even easier, though I haven't played with
it yet.
If you're using BoxLayout, take a look at my BoxBeans, which can be used
in visual builder tools to help adjust components to stretch/shrink
appropriately. (http://javadude.com/tools). I haven't tried them in VE,
though, but they should work.
Of course I wouldn't recommend wholesale redesign for all of your
existing screens, but you could slowly rework them to reduce your
dependency on BarfBag.
Later,
-- Scott
In article <c1muem$eh3$1@eclipse.org>, andreas.wuertz@information-
factory.com says...
> How about better support for GridBagLayouts?
>
> For me and my thousands of dialogs/panels, this is by far the most-used
> Layout. In VisualAge you drag components within the layout to put them into
> different cells. This does not seem to work in VE. Actually it makes working
> with VE quite painful. Any plans on that?
>
> Cheers and thanks for the good work
|
|
|
| Re: VE 1.0 Plans [message #582696 is a reply to message #21346] |
Fri, 27 February 2004 09:54 |
| Eclipse User |
|
|
|
Thanks for the info, but it doesn't really help me, because:
- I have over 1000 dialogs/panels that I cannot/do not want to completely
redesign, but have to maintain from time to time (i.e once every year)
- I am not sure if nesting panels just for layout purposes should be the way
to go (of course, sometimes it is inevitable)
- BoxLayouts do not exist in Java1, but we are still supporting MacOS 9
- I really love GridBagLayouts - under VisualAge, they are quite easy to use
:-)
Cheers
Andy
"Scott Stanchfield" <scott@javadude.com> schrieb im Newsbeitrag
news:MPG.1aa91e70637e134298969f@news.eclipse.org...
> I'd recommend reading my article "Effective Layout Management" to avoid
> using BarfBag. You can get a much cleaner/maintainable design this
> way...
>
> See
> http://developer.java.sun.com/developer/onlineTraining/GUI/A WTLayoutMgr
>
> Note that when I wrote it BoxLayout didn't exist. The parts of the
> example that use BarfBag can be very easily done with a nested BoxLayout
> (off the top of my head):
>
> Panel [BoxLayout(X_AXIS)]
> h-strut
> FileDisplay
> h-strut
> Panel [BoxLayout(Y_AXIS)]
> v-glue
> Button("-->")
> v-strut
> Button("<--")
> v-glue
> h-strut
> FileDisplay
> h-strut
>
> That simple design replaces a 6-component BarfBag, which requires 66
> constraint settings...
>
> I gave a talk at JavaOne based on the article, and you can get the
> slides at
>
> http://www.javadude.com/articles/javaone/Effective%20Layout%
> 20Management.zip
>
> These slides talk about the BoxLayout design a bit.
>
> SpringLayout may make things even easier, though I haven't played with
> it yet.
>
> If you're using BoxLayout, take a look at my BoxBeans, which can be used
> in visual builder tools to help adjust components to stretch/shrink
> appropriately. (http://javadude.com/tools). I haven't tried them in VE,
> though, but they should work.
>
> Of course I wouldn't recommend wholesale redesign for all of your
> existing screens, but you could slowly rework them to reduce your
> dependency on BarfBag.
>
> Later,
> -- Scott
>
>
> In article <c1muem$eh3$1@eclipse.org>, andreas.wuertz@information-
> factory.com says...
> > How about better support for GridBagLayouts?
> >
> > For me and my thousands of dialogs/panels, this is by far the most-used
> > Layout. In VisualAge you drag components within the layout to put them
into
> > different cells. This does not seem to work in VE. Actually it makes
working
> > with VE quite painful. Any plans on that?
> >
> > Cheers and thanks for the good work
|
|
|
| Re: VE 1.0 Plans [message #582752 is a reply to message #21354] |
Fri, 27 February 2004 16:40 |
| Eclipse User |
|
|
|
That's cool. Just keep these ideas in mind when designing new screens or
making significant changes to old screens. Much simpler.
Of course eventually VE will have better BarfBag support, as will
Penumbra when I release it (don't ask when -- don't know yet).
Later,
-- Scott
In article <c1nlg6$ejh$1@eclipse.org>, andreas.wuertz@information-
factory.com says...
> Thanks for the info, but it doesn't really help me, because:
>
> - I have over 1000 dialogs/panels that I cannot/do not want to completely
> redesign, but have to maintain from time to time (i.e once every year)
> - I am not sure if nesting panels just for layout purposes should be the way
> to go (of course, sometimes it is inevitable)
> - BoxLayouts do not exist in Java1, but we are still supporting MacOS 9
> - I really love GridBagLayouts - under VisualAge, they are quite easy to use
> :-)
>
> Cheers
> Andy
>
> "Scott Stanchfield" <scott@javadude.com> schrieb im Newsbeitrag
> news:MPG.1aa91e70637e134298969f@news.eclipse.org...
> > I'd recommend reading my article "Effective Layout Management" to avoid
> > using BarfBag. [...]
|
|
|
| Re: VE 1.0 Plans [message #582938 is a reply to message #21325] |
Mon, 01 March 2004 09:34 |
| Eclipse User |
|
|
|
Andreas Würtz wrote:
> How about better support for GridBagLayouts?
>
> For me and my thousands of dialogs/panels, this is by far the most-used
> Layout. In VisualAge you drag components within the layout to put them into
> different cells. This does not seem to work in VE. Actually it makes working
> with VE quite painful. Any plans on that?
>
> Cheers and thanks for the good work
>
> Andy
>
Visual support for GridBag is available in the Visual Editor for Java
(in the WebSphere Studio products) and was not moved to VE because of
pending patents in this area.
As time go by, I would hope to see such basic necessities move into open
source.
|
|
|
|
| Re: VE 1.0 Plans [message #583128 is a reply to message #21797] |
Wed, 03 March 2004 09:04 |
| Eclipse User |
|
|
|
Andreas Würtz wrote:
> Thanks for the info.
>
> Does that mean it is going to take ages for the visual support to be
> integrated? Or are they already in the process of solving those patent
> problems?
>
> Cheers
> Andy
>
>
I wish I could give you a direct answer, but I can not. ... every
problem can be viewed as in the process of getting solved ;-). The
problem is that in most cases it is impossible to determine with
certainty how long will that process take.
|
|
|
| Re: VE 1.0 Plans [message #583262 is a reply to message #21933] |
Wed, 03 March 2004 19:48 |
| Eclipse User |
|
|
|
Anyone know the status of VE 1.0, it is a Swing only or will release
after the SWT designer finish?
Gili Mendel wrote:
> Andreas Würtz wrote:
>
>> Thanks for the info.
>>
>> Does that mean it is going to take ages for the visual support to be
>> integrated? Or are they already in the process of solving those patent
>> problems?
>>
>> Cheers
>> Andy
>>
>>
>
>
> I wish I could give you a direct answer, but I can not. ... every
> problem can be viewed as in the process of getting solved ;-). The
> problem is that in most cases it is impossible to determine with
> certainty how long will that process take.
>
|
|
|
| Re: VE 1.0 Plans [message #583321 is a reply to message #22240] |
Thu, 04 March 2004 09:12 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
SWT is being worked on at this time. It will be available when 1.0.0 if
finally released. The current integration driver has some small support
(can only drop a shell, but there are problems with it).
--
Thanks, Rich Kulp
|
|
|
| Create SWT Re: VE 1.0 Plans [message #583630 is a reply to message #22485] |
Sat, 06 March 2004 06:44 |
| Eclipse User |
|
|
|
I added swt library to a project that have vep 1.0, and when I create
new visual class, I cannot create a swt form, but Swing form
can you help>?
Rich Kulp wrote:
> SWT is being worked on at this time. It will be available when 1.0.0 if
> finally released. The current integration driver has some small support
> (can only drop a shell, but there are problems with it).
>
|
|
|
| Re: Create SWT Re: VE 1.0 Plans [message #583646 is a reply to message #23257] |
Sat, 06 March 2004 10:21 |
| Eclipse User |
|
|
|
The Visual Class Wizard hasn't been changed yet to create an SWT class.
Simply choose to extend Object from the Visual Class Wizard, and the
SWT palette will show up if you have the SWT library included in the
project.
- Jeff
Frans Thamura wrote:
> I added swt library to a project that have vep 1.0, and when I create
> new visual class, I cannot create a swt form, but Swing form
>
> can you help>?
>
>
> Rich Kulp wrote:
>
>> SWT is being worked on at this time. It will be available when 1.0.0
>> if finally released. The current integration driver has some small
>> support (can only drop a shell, but there are problems with it).
>>
|
|
|
| Re: Create SWT Re: VE 1.0 Plans [message #583659 is a reply to message #23260] |
Sat, 06 March 2004 10:30 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Right now you have to include "SWT Container" from the java build page
Add library button. That is the only way we currently recognize SWT.
Just adding SWT.jar to the build path doesn't work for VE.
--
Thanks, Rich Kulp
|
|
|
Home