5 comments
Comment actions Permalink

please vote for this feature if you see it the same way i see it: it's better to insert the source code into a class(.java-file) than manipulate the bytecode of a class(.class-file)!!! for this reason, we need a button which returns you the source code from a uiDesigner .form-file and you can manually add it into your java-file.

0
Comment actions Permalink

Michael Seele wrote:

please vote for this feature if you see it the same way i see it: it's better to insert the source code into a class(.java-file) than manipulate the bytecode of a class(.class-file)!!! for this reason, we need a button which returns you the source code from a uiDesigner .form-file and you can manually add it into your java-file.


Michael, be sure we'll do something with this request, because a lot of
people want to see source code. My personal opinion is that source code
for UI is a garbage which we always forced to seen because Java doesn't
have convenient tools for UI construction. UI source code is a
historical rudiment. Perhaps it has happened due to "political" reasons:
Java never was positioned for desktop developmenet and UI side is
historically very weak in Java. Most probabale we tweak current approach
and allow user do see UI mess of constraints, component constructors and
primitive setters. IMHO thinking about UI like a resource is the best
approach. Each language should allow easely solve particulars tasks.
Java is a general purposes language so it's evident that Java is not
very suitable for description of resources.

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

0
Comment actions Permalink

I see two possible approaches:

1. GUI is constructed at runtime on-the-fly from XML form description. In this case the class, to which the form is bound, only needs to call framework method. This method will parse form description, create GUI components, lay them out and set their properties.

2. (What we currently have) Some code is generated at design time from XML form description. In current implementation this code is generated in binary form and inserted into binary class file.

My personal preference is to have both approaches implemented and available for use. But for the second approach I would also prefer to have an option to insert generated code into source file instead of tweaking binary code. With code folding I can always collapse generated code.

0
Comment actions Permalink

IMHO it's ok to insert the byte-code in runtime. but you should have another chance to use the uiDesigner. when you can click on a button which returns the java source code into a JTextField where you can manually copy it into your file it's ok. the best solution is how http://www.swt-designer.com/ does it(demo: http://www.swt-designer.com/demos/demo1.html ). you can change between the code- and the design-window...

0
Comment actions Permalink

Sergei S. Ivanov wrote:

I see two possible approaches:

1. GUI is constructed at runtime on-the-fly from XML form description. In this case the class, to which the form is bound, only needs to call framework method. This method will parse form description, create GUI components, lay them out and set their properties.


This approach is not acceptable because it breaks ofbuscation.

With best regards,
Vladimir Kondratyev
_____________________
JetBrains

0

Please sign in to leave a comment.