My two cents

I would like to see EJB support and Aspects be plugins instead of being
integrated features. The core IDE should stay as lean and mean as possible.
If I don't use EJBs or Aspects in my project then I don't want those plugins
to load.

To be useful, the GUI builder must support Java beans for custom and third
party components. Also I would like to see a way to delegate events to
procedures inside the binding class.

The GUI builder looks pretty good, I like the fact that it doesn't produce
a class full of ugly unmaintainable code like tools such as netbeans,
however it would be nice to have the option to generate source that can be
tweaked. Don't lose the byte code manipulation though, it's an innovative
approach to the GUI builder problem.


10 comments
Comment actions Permalink

Rob Abbe wrote:

To be useful, the GUI builder must support Java beans for custom and third
party components. Also I would like to see a way to delegate events to
procedures inside the binding class.


UI designer does support third party components. It relays on JavaBeans
spec to introspect the properties. The only problem now is that it's not
possible to edit component palette, but we are working on this feature
and it will be available soon.

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

0
Comment actions Permalink

"Rob Abbe" <rabbe@captovation.com> wrote in message
news:bf661l$a0p$1@is.intellij.net...

I would like to see EJB support and Aspects be plugins instead of being
integrated features. The core IDE should stay as lean and mean as

possible.

If I don't use EJBs or Aspects in my project then I don't want those

plugins

to load.


What benefits are you hoping to get from not loading the EJB and Aspects
plugins?

Just curious...


0
Comment actions Permalink

As it stands now, there is a compilation step that says something like
"Weaving Aspects into app". This step takes a second or two.

--
Jordan Zimmerman
http://www.jordanzimmerman.com


0
Comment actions Permalink

"Erik Hanson" <ehanson@comsys.com> wrote in > What benefits are you hoping
to get from not loading the EJB and Aspects

plugins?


I would hope the IDE would consume less memory and load faster if my project
did not use EJB's or Aspects and those plugins were not loaded.

Also, there is a little less ui clutter, in that an aspect button would not
be present (nit picky I know).

Personally, I feel Aspects are of limited value. An opinion shared by more
than just myself. If EJB and Aspects were plugins, everyone wins.

What would be the harm in making them plugins? The pros outweigh the cons
from what I can tell.



0
Comment actions Permalink

That's great news. I've been waiting for Idea to support a GUI builder for
a long time. I love the fact that you made it a plugin.


"Vladimir Kondratyev" <vova@intellij.net> wrote in message
news:bf687h$hg6$1@is.intellij.net...

Rob Abbe wrote:

To be useful, the GUI builder must support Java beans for custom and

third

party components. Also I would like to see a way to delegate events to
procedures inside the binding class.

>

UI designer does support third party components. It relays on JavaBeans
spec to introspect the properties. The only problem now is that it's not
possible to edit component palette, but we are working on this feature
and it will be available soon.

>

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

>


0
Comment actions Permalink

"Rob Abbe" <rabbe@mn.rr.com> wrote in message
news:bf7li5$q45$1@is.intellij.net...

"Erik Hanson" <ehanson@comsys.com> wrote in

What benefits are you hoping
to get from not loading the EJB and Aspects
plugins?

>

I would hope the IDE would consume less memory and load faster if my

project

did not use EJB's or Aspects and those plugins were not loaded.


I was just curious to see if performance was indeed the reason.

I personally don't have memory or performance issues with IDEA; I'm
wondering if that's why I've never wished for features to be converted to
plugins. (Well, that and the fact that IDEA loves to delete my plugins so I
end up only using a couple really important ones. But in this case since I
also don't use EJB or Aspects, I don't care if they are plugins.)

Do a lot of people out there have memory and performance issues with IDEA?
(Even when I did development on an old laptop, my main problem was the small
screen, not the 433 MHz CPU or 256 MB of RAM.)


0
Comment actions Permalink

Never had any memory or performance problems. My opinion is that JetBrains should not hesitate to enhance IntelliJ with a useful feature because it might not work on some older machines. As long as everything goes smooth on a computer equipped with 512 mb memory, I am fine.

Hardware, especially memory, is not that expensive nowadays, and IntelliJ is one of the cheapest Java IDEs on the market, not counting the free open source products of course.

Regards
Thomas Gülden
Munich, Germany

0
Comment actions Permalink

UI designer does support third party components. It relays on JavaBeans
spec to introspect the properties.


Will the appropriate setters be hard-coded when generating the class
file, so even primitiv obfuscators will be possible to rename them?

Tom

0
Comment actions Permalink

Thomas Singer wrote:
>>UI designer does support third party components. It relays on JavaBeans
>>spec to introspect the properties.


Will the appropriate setters be hard-coded when generating the class
file, so even primitiv obfuscators will be possible to rename them?

Tom


All setters are hardcoded. You can try to decompile generated class file
to see what happend. Of course obfuscation should be possible.

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

0
Comment actions Permalink

Don't lose the byte code manipulation though, it's an innovative approach to the GUI builder problem.

.. what problem does it solve?

0

Please sign in to leave a comment.