Home » Archived » Visual Editor (VE) » Code generation options
| Code generation options [message #59056] |
Thu, 09 September 2004 15:21  |
Eclipse User |
|
|
|
Originally posted by: bandrews.none.com
Hi,
I was wondering what sort of code generation options are being planned.
I have not seen a Java visual designer yet that generates the code that I
want. I always have to go back and tweak it. The problems I have seen so
far with VE is that it uses fully qualified names for everything. I hate
that and it seems that all visual designers do it. Why is it not possible
to import the object, then just use the name like JButton instead of
javax.swing.JButton? Also, I have noticed there is a get method for each
GUI component? Maybe some people like this, but I don't. I would much
rather have the GUI components initialized in a single method.
My point is, without code generation options, this tool will be just like
every other tool out there. So are there plans for these options?
thanks,
B
|
|
|
| Re: Code generation options [message #59138 is a reply to message #59056] |
Thu, 09 September 2004 16:24  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
We are working on doing imports. We have imports done on many things,
but not yet all. Since our release is just around the corner we won't
get to all of these in this release. But very early in either a fixpack
or the next release we will have everything using imports instead of
fully-qualified.
We intend to have in the future a style that generates just one init
statement. We haven't gotton to it yet with all of the other things
needed like SWT, etc.
--
Thanks, Rich Kulp
|
|
|
| Re: Code generation options [message #59185 is a reply to message #59138] |
Thu, 09 September 2004 16:40 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.none.com
WONDERFUL! Thanks a lot!
Since you are a developer working on this project ( I assume ), would you
mind commenting on my last post in the "HTML/JSP WYSIWYG editor" thread? I
would appreicate it very much.
thanks,
B
Rich Kulp wrote:
> We are working on doing imports. We have imports done on many things,
> but not yet all. Since our release is just around the corner we won't
> get to all of these in this release. But very early in either a fixpack
> or the next release we will have everything using imports instead of
> fully-qualified.
> We intend to have in the future a style that generates just one init
> statement. We haven't gotton to it yet with all of the other things
> needed like SWT, etc.
|
|
|
| Re: Code generation options [message #59210 is a reply to message #59185] |
Thu, 09 September 2004 17:42 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
I doubt we will be doing something like that. At least in the near
future. We have a lot that needs to be done yet just for the java VE.
Also, I don't know HTML/JSP but I don't know if it is appropriate for
the VE style editor. The VE editor is best for object composition type
models, like java code, or UML. The VE edits models where you drop
things, set properties on them, and connect them together. HTML/JSP
WYSIWYG is more of a text/browser type editor and doesn't really fit
into the VE model.
If someone else wants to contribute such an editor based on the VE that
would be good, but the VE isn't ready yet for extensions like that. We
need to start making things API instead of everything internal.
--
Thanks, Rich Kulp
|
|
|
| Re: Code generation options [message #59233 is a reply to message #59210] |
Thu, 09 September 2004 17:58 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
"The VE edits models where you drop things, set properties on them, and
connect them together."
But HTML also has a model, yes? For example a button has properties like
font, name, size, etc. You listen to those changes in the model, update
the editor and update the code. Or update the code, update the model,
update the editor.
Am I being too simplistic?
thanks,
B
Rich Kulp wrote:
> I doubt we will be doing something like that. At least in the near
> future. We have a lot that needs to be done yet just for the java VE.
> Also, I don't know HTML/JSP but I don't know if it is appropriate for
> the VE style editor. The VE editor is best for object composition type
> models, like java code, or UML. The VE edits models where you drop
> things, set properties on them, and connect them together. HTML/JSP
> WYSIWYG is more of a text/browser type editor and doesn't really fit
> into the VE model.
> If someone else wants to contribute such an editor based on the VE that
> would be good, but the VE isn't ready yet for extensions like that. We
> need to start making things API instead of everything internal.
|
|
|
| Re: Code generation options [message #59281 is a reply to message #59233] |
Thu, 09 September 2004 19:38 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
No you are not being too simplistic. :-) It is mostly that I don't know
HTML/JSP. I don't know what a visual editor of such should even look
like. But I don't think HTML is really an object composition type model.
That is what works best in the visual editor, object composition. It may
be feasible, or it may not be.
--
Thanks, Rich Kulp
|
|
|
| Re: Code generation options [message #59306 is a reply to message #59281] |
Thu, 09 September 2004 19:57 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
Thanks for your replies! I guess I would have to look at the code to
really understand what you mean by "object composition type model." But
that's okay, I will take your word for it for now.
What about the AUIML Toolkit on alphaworks? It says it has an HTML visual
editor that is based on VE. If that's true, then apparently extending VE
to do HTML has already been done. Do you know anything about this? Is
there any chance that some parts of AUIML (like the HTML editor) would
eventually become a part of VE? Or maybe you cannot comment on such things?
thanks,
Barry
Rich Kulp wrote:
> No you are not being too simplistic. :-) It is mostly that I don't know
> HTML/JSP. I don't know what a visual editor of such should even look
> like. But I don't think HTML is really an object composition type model.
> That is what works best in the visual editor, object composition. It may
> be feasible, or it may not be.
|
|
|
| Re: Code generation options [message #59329 is a reply to message #59306] |
Thu, 09 September 2004 21:54 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
AUIML isn't an HTML editor per-se. The VE based portion doesn't edit
HTML. What it does is create xml for views, like Panels or Frames, that
are generic and not operating system specific. Then these XML's are
parsed by a factory on each type of display, such as from a Browser, and
turns them into the display specific type panel or frame. It does many
other things too, but that is the basics of the editor that is based
upon VE.
Maybe the AUIML folks will correct me on this. :-) I haven't had that
much to do with AUIML for a couple of years. I had helped them get
started with the VE, but they are quite proficient at it now and have
gone much beyond what I saw back then.
Think of UML when I say object composition. There are a bunch "things"
sitting on the surface, you click on a "thing" and you can set
properties of it. You can drop other "things" on a "thing" and it
becomes a child of the "thing". You can connect "things" together.
So in the Java VE land, you drop a JPanel (which is a "thing"), and then
you drop JButtons on it (which are "things").
So object composition means you have objects, your objects can contain
other objects, and you can have relationships between the objects.
--
Thanks, Rich Kulp
|
|
|
| Re: Code generation options [message #59380 is a reply to message #59329] |
Fri, 10 September 2004 13:33 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
"So object composition means you have objects, your objects can contain
other objects, and you can have relationships between the objects."
Got it! Thanks for clarifying the object composition for me! So yes, HTML
is not this way.
Thank you very much for your valuable information.
Barry
Rich Kulp wrote:
> AUIML isn't an HTML editor per-se. The VE based portion doesn't edit
> HTML. What it does is create xml for views, like Panels or Frames, that
> are generic and not operating system specific. Then these XML's are
> parsed by a factory on each type of display, such as from a Browser, and
> turns them into the display specific type panel or frame. It does many
> other things too, but that is the basics of the editor that is based
> upon VE.
> Maybe the AUIML folks will correct me on this. :-) I haven't had that
> much to do with AUIML for a couple of years. I had helped them get
> started with the VE, but they are quite proficient at it now and have
> gone much beyond what I saw back then.
> Think of UML when I say object composition. There are a bunch "things"
> sitting on the surface, you click on a "thing" and you can set
> properties of it. You can drop other "things" on a "thing" and it
> becomes a child of the "thing". You can connect "things" together.
> So in the Java VE land, you drop a JPanel (which is a "thing"), and then
> you drop JButtons on it (which are "things").
> So object composition means you have objects, your objects can contain
> other objects, and you can have relationships between the objects.
|
|
|
| Re: Code generation options [message #598244 is a reply to message #59056] |
Thu, 09 September 2004 16:24 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
We are working on doing imports. We have imports done on many things,
but not yet all. Since our release is just around the corner we won't
get to all of these in this release. But very early in either a fixpack
or the next release we will have everything using imports instead of
fully-qualified.
We intend to have in the future a style that generates just one init
statement. We haven't gotton to it yet with all of the other things
needed like SWT, etc.
--
Thanks, Rich Kulp
|
|
|
| Re: Code generation options [message #598255 is a reply to message #59138] |
Thu, 09 September 2004 16:40 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.none.com
WONDERFUL! Thanks a lot!
Since you are a developer working on this project ( I assume ), would you
mind commenting on my last post in the "HTML/JSP WYSIWYG editor" thread? I
would appreicate it very much.
thanks,
B
Rich Kulp wrote:
> We are working on doing imports. We have imports done on many things,
> but not yet all. Since our release is just around the corner we won't
> get to all of these in this release. But very early in either a fixpack
> or the next release we will have everything using imports instead of
> fully-qualified.
> We intend to have in the future a style that generates just one init
> statement. We haven't gotton to it yet with all of the other things
> needed like SWT, etc.
|
|
|
| Re: Code generation options [message #598264 is a reply to message #59185] |
Thu, 09 September 2004 17:42 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
I doubt we will be doing something like that. At least in the near
future. We have a lot that needs to be done yet just for the java VE.
Also, I don't know HTML/JSP but I don't know if it is appropriate for
the VE style editor. The VE editor is best for object composition type
models, like java code, or UML. The VE edits models where you drop
things, set properties on them, and connect them together. HTML/JSP
WYSIWYG is more of a text/browser type editor and doesn't really fit
into the VE model.
If someone else wants to contribute such an editor based on the VE that
would be good, but the VE isn't ready yet for extensions like that. We
need to start making things API instead of everything internal.
--
Thanks, Rich Kulp
|
|
|
| Re: Code generation options [message #598270 is a reply to message #59210] |
Thu, 09 September 2004 17:58 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
"The VE edits models where you drop things, set properties on them, and
connect them together."
But HTML also has a model, yes? For example a button has properties like
font, name, size, etc. You listen to those changes in the model, update
the editor and update the code. Or update the code, update the model,
update the editor.
Am I being too simplistic?
thanks,
B
Rich Kulp wrote:
> I doubt we will be doing something like that. At least in the near
> future. We have a lot that needs to be done yet just for the java VE.
> Also, I don't know HTML/JSP but I don't know if it is appropriate for
> the VE style editor. The VE editor is best for object composition type
> models, like java code, or UML. The VE edits models where you drop
> things, set properties on them, and connect them together. HTML/JSP
> WYSIWYG is more of a text/browser type editor and doesn't really fit
> into the VE model.
> If someone else wants to contribute such an editor based on the VE that
> would be good, but the VE isn't ready yet for extensions like that. We
> need to start making things API instead of everything internal.
|
|
|
| Re: Code generation options [message #598280 is a reply to message #59233] |
Thu, 09 September 2004 19:38 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
No you are not being too simplistic. :-) It is mostly that I don't know
HTML/JSP. I don't know what a visual editor of such should even look
like. But I don't think HTML is really an object composition type model.
That is what works best in the visual editor, object composition. It may
be feasible, or it may not be.
--
Thanks, Rich Kulp
|
|
|
| Re: Code generation options [message #598287 is a reply to message #59281] |
Thu, 09 September 2004 19:57 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
Thanks for your replies! I guess I would have to look at the code to
really understand what you mean by "object composition type model." But
that's okay, I will take your word for it for now.
What about the AUIML Toolkit on alphaworks? It says it has an HTML visual
editor that is based on VE. If that's true, then apparently extending VE
to do HTML has already been done. Do you know anything about this? Is
there any chance that some parts of AUIML (like the HTML editor) would
eventually become a part of VE? Or maybe you cannot comment on such things?
thanks,
Barry
Rich Kulp wrote:
> No you are not being too simplistic. :-) It is mostly that I don't know
> HTML/JSP. I don't know what a visual editor of such should even look
> like. But I don't think HTML is really an object composition type model.
> That is what works best in the visual editor, object composition. It may
> be feasible, or it may not be.
|
|
|
| Re: Code generation options [message #598297 is a reply to message #59306] |
Thu, 09 September 2004 21:54 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
AUIML isn't an HTML editor per-se. The VE based portion doesn't edit
HTML. What it does is create xml for views, like Panels or Frames, that
are generic and not operating system specific. Then these XML's are
parsed by a factory on each type of display, such as from a Browser, and
turns them into the display specific type panel or frame. It does many
other things too, but that is the basics of the editor that is based
upon VE.
Maybe the AUIML folks will correct me on this. :-) I haven't had that
much to do with AUIML for a couple of years. I had helped them get
started with the VE, but they are quite proficient at it now and have
gone much beyond what I saw back then.
Think of UML when I say object composition. There are a bunch "things"
sitting on the surface, you click on a "thing" and you can set
properties of it. You can drop other "things" on a "thing" and it
becomes a child of the "thing". You can connect "things" together.
So in the Java VE land, you drop a JPanel (which is a "thing"), and then
you drop JButtons on it (which are "things").
So object composition means you have objects, your objects can contain
other objects, and you can have relationships between the objects.
--
Thanks, Rich Kulp
|
|
|
| Re: Code generation options [message #598309 is a reply to message #59329] |
Fri, 10 September 2004 13:33 |
| Eclipse User |
|
|
|
Originally posted by: bandrews.NO_SPAM_bphnx.com
"So object composition means you have objects, your objects can contain
other objects, and you can have relationships between the objects."
Got it! Thanks for clarifying the object composition for me! So yes, HTML
is not this way.
Thank you very much for your valuable information.
Barry
Rich Kulp wrote:
> AUIML isn't an HTML editor per-se. The VE based portion doesn't edit
> HTML. What it does is create xml for views, like Panels or Frames, that
> are generic and not operating system specific. Then these XML's are
> parsed by a factory on each type of display, such as from a Browser, and
> turns them into the display specific type panel or frame. It does many
> other things too, but that is the basics of the editor that is based
> upon VE.
> Maybe the AUIML folks will correct me on this. :-) I haven't had that
> much to do with AUIML for a couple of years. I had helped them get
> started with the VE, but they are quite proficient at it now and have
> gone much beyond what I saw back then.
> Think of UML when I say object composition. There are a bunch "things"
> sitting on the surface, you click on a "thing" and you can set
> properties of it. You can drop other "things" on a "thing" and it
> becomes a child of the "thing". You can connect "things" together.
> So in the Java VE land, you drop a JPanel (which is a "thing"), and then
> you drop JButtons on it (which are "things").
> So object composition means you have objects, your objects can contain
> other objects, and you can have relationships between the objects.
|
|
|
Goto Forum:
Current Time: Sat Sep 28 02:24:14 GMT 2024
Powered by FUDForum. Page generated in 0.05868 seconds |
] 
Search
Help
Register
Login
Home
