Will it be possible to use other UI API for building UI using UI builder, say SWT? Let me rephrase: does IntelliJ plan to support SWT, maybe in later versions of Aurora?
Definitely not in Aurora. BTW is it possible to incorporate SWT components into swing-based program?
I do not have much experience with Java GUI, so I don't know, I think that it is not possible now. On the other hand, there are talks on Eclipse forum to provide SWT user code working on Swing, and Swing user code working on SWT thin layer. The purpose to run SWT code on Swing is to be able to provide "run everywhere" ability if SWT native library is not available for particular platform (but imho now it covers most used ones, like Windows, OS X, Linux, AIX, Solaris). The purpose of running Swing apps on SWT is to increase perfomance and provide native look & feel.
So, my understanding is that currently one cannot mix SWT and Swing in one container, but Eclipse group is going to change this. I, with my Win API background, like SWT approach. It allows to write fast apps with native look.
Do you really think, this is usable? What if you have 50 different purpose panels that you use in your application? Do I have to add all 50 panels? What happens, when they are renamed? Or Moved to another package?
Do you really think, this is usable? What if you have 50 different purpose panels that you use in your application? Do I have to add all 50 panels? What happens, when they are renamed? Or Moved to another package?
Good point. There should be an "Add User-Defined Component" button which asks for a class name each time you add it to the form. And, of course, all of this should be tied in with the refactorings.
This e-mail and any attachments may be confidential and/or legally privileged. If you have received this email and you are not a named addressee, please inform the sender at Digital Steps Ltd by phone on +44 (0)1483 469 480 or by reply email and then delete the email from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this email. Although Digital Steps Ltd routinely screens for viruses, addressees should check this email and any attachments for viruses. Digital Steps Ltd makes no representation or warranty as to the absence of viruses in this email or any attachments.
Good point. There should be an "Add User-Defined Component" button which asks for a class name each time you add it to the form. And, of course,
all
of this should be tied in with the refactorings.
Other idea : when you click on a JLabel, there should be a drop-down list with all the subclasses of JLabel that are present in your project and libraries. And the same behaviour for all other derivatives of JComponent obviously. That way, you could use any custom component, without bothering to add all the components you wish to use.
Forgot following: What about components, that cannot be instantiated with an empty constructor? What about components, that are created by a factory (e.g. MyPanel.createInstance())?
Forgot following: What about components, that cannot be instantiated with an empty constructor? What about components, that are created by a factory (e.g. MyPanel.createInstance())?
Well, yes, my idea does not cover all the cases... So your solution would be the layout of placeholders, not components, I know.
For the Swing standard components, things are ok. But with custom ones, there's an issue. My rough guess would be simply to show a standard JButton if your own component is a subclass of JButton. And for the creation of your custom component, it's always your task to do so in the bound class. So that's not really an issue, it's up to you to do the job. Your component would be listed among the JLabels, but the creation part is yours.
This would be in violation of the bean spec. If I remember correctly bean needs to have a default ctor and everything should be wireable through setter and addXXXListener. But something tells me that you do not care about Visual Bean assembly since you do it in code. Default ctor was definitively a word around for gui builders.
Forgot following: What about components, that cannot be instantiated with an empty constructor? What about components, that are created by a factory (e.g. MyPanel.createInstance())?
If you want to deal with layout only, you don't. If you want to have the builder also deal with form creation you most likely need it. Let's see if and how they are going to deal with event handling. BTW if you do not pass any parameter to your factory method I do not see any difference with a default ctor.
Definitely not in Aurora. BTW is it possible to incorporate SWT components
into swing-based program?
--
--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"
"Michael Jouravlev" <mikus@mail.ru> wrote in message
news:bccs2l$lvb$1@is.intellij.net...
later
>
>
will it be possible to use own components with the UIdesigner?
"Valentin Kipiatkov" <valentin@intellij.com> wrote in message
news:bcd5mb$76c$1@is.intellij.net...
I do not have much experience with Java GUI, so I don't know, I think that
it is not possible now. On the other hand, there are talks on Eclipse forum
to provide SWT user code working on Swing, and Swing user code working on
SWT thin layer. The purpose to run SWT code on Swing is to be able to
provide "run everywhere" ability if SWT native library is not available for
particular platform (but imho now it covers most used ones, like Windows, OS
X, Linux, AIX, Solaris). The purpose of running Swing apps on SWT is to
increase perfomance and provide native look & feel.
So, my understanding is that currently one cannot mix SWT and Swing in one
container, but Eclipse group is going to change this. I, with my Win API
background, like SWT approach. It allows to write fast apps with native
look.
"Michael Seele" <mseele@guh-software.de> wrote in message
news:22268359.1055939681638.JavaMail.itn@is.intellij.net...
Yes, you will be able to add your own components to component palette.
--
Best regards,
Dmitry Peshehonov
JetBrains, Inc, http://www.intellij.com
Do you really think, this is usable? What if you have 50 different
purpose panels that you use in your application? Do I have to add all
50 panels? What happens, when they are renamed? Or Moved to another
package?
Tom
Thomas Singer wrote:
Good point. There should be an "Add User-Defined Component" button which
asks for a class name each time you add it to the form. And, of course, all
of this should be tied in with the refactorings.
Vil.
--
Vilya Harvey, Consultant
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/
DisclaimerThis e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.
all
Other idea : when you click on a JLabel, there should be a drop-down list
with all the subclasses of JLabel that are present in your project and
libraries. And the same behaviour for all other derivatives of JComponent
obviously.
That way, you could use any custom component, without bothering to add all
the components you wish to use.
Guillaume Laforge
Forgot following: What about components, that cannot be instantiated
with an empty constructor? What about components, that are created by
a factory (e.g. MyPanel.createInstance())?
Tom
Well, yes, my idea does not cover all the cases...
So your solution would be the layout of placeholders, not components, I
know.
For the Swing standard components, things are ok.
But with custom ones, there's an issue.
My rough guess would be simply to show a standard JButton if your own
component is a subclass of JButton.
And for the creation of your custom component, it's always your task to do
so in the bound class.
So that's not really an issue, it's up to you to do the job.
Your component would be listed among the JLabels, but the creation part is
yours.
Guillaume Laforge
This would be in violation of the bean spec. If I remember correctly bean
needs to have a default ctor and everything should be wireable through
setter and addXXXListener.
But something tells me that you do not care about Visual Bean assembly since
you do it in code. Default ctor was definitively a word around for gui
builders.
Jacques
"Thomas Singer" <thomas.singer@NOregnisSPAM.de> wrote in message
news:vgj5fvk0qbfn93hjo2rf8t8tng0jo8ob65@4ax.com...
>
>This would be in violation of the bean spec.
Who said, that the components need to be beans?
Tom
They are working on a project to redefine slowness??? Ouch.
>
If you want to deal with layout only, you don't. If you want to have the
builder also deal with form creation you most likely need it. Let's see if
and how they are going to deal with event handling.
BTW if you do not pass any parameter to your factory method I do not see any
difference with a default ctor.
Jacques