Definition of Designer Capable Class

[robnauticus]

Hello Eric (and everyone else),

Just wanted to ask a question about the new Designer version. I am using a clean Eclipse 3.4 with GWT 1.6.4 & 1.7 now with all the plugins and the newest designer 7.
I imported my project into a new workspace via SVN to experiment with it. I have owned the Designer product for almost a year but had to move back to the standard project structure for compatibility reasons.
So I converted my project again to a Designer project but I cannot design any of my classes.

I have two questions about this behavior,
how can I tell what qualifies a class as "design-able"?
what is the best approach for an existing project/class to maximize ease of using the designer once a fairly complex set of widgets has been created?

I have seen a few topics now on IsDesignTime(), is that still viable in the new versions? Is it smart enough to allow my classes to be design-able if I implement this?

I have an abstract widget that extends a Composite that is the basis for all of my visual classes. There is nothing in any of my visual classes that would call a RPC or require anything other than some parameters during construction. I remember the old version of the Designer did not like classes without a default constructor, I even tried to make one but could stilll not get into Designer.

Thanks, I am looking forward to trying the new version out asap!!!

Rob

[Eric Clayberg]

So I converted my project again to a Designer project but I cannot design any of my classes.

What do you mean by you "cannot design any of my classes"? Without an actual description of the problem / exception / symptom, I don't have much to go on.

how can I tell what qualifies a class as "design-able"?

For GWT, it would be any EntryPoint, Composite, DialogBox or PopupPanel subclass.

I have seen a few topics now on IsDesignTime(), is that still viable in the new versions?

Sure, but unless you are encountering an exception triggered in your own code caused by accessing runtime only services, isDesignTime() is likely not to make any difference. Simply adding that method will do precisely nothing.

[robnauticus]

In response to first quote:

What do you mean by you "cannot design any of my classes"? Without an actual description of the problem / exception / symptom, I don't have much to go on.

The Designer mode is unavailable, as in I cannot see the Source/Design Tabs to switch to Designer mode. I have no errors anywhere. Is there a maximum depth or complexity limitation that the designer cannot traverse through the code structure? Should I try stubbing off my code to simplify things for the designer?

Then second:

For GWT, it would be any EntryPoint, Composite, DialogBox or PopupPanel subclass.

All of my Composite-based classes exhibit the same behavior as stated above since the all extend the same Composite. If I create a new Composite through the menu (GWT->Composite) I can design that just fine. So the program is activated and working once it recognizes a compatible type. I can post up some code if it would help. Here are the basics...

My base class for all of my widgets:

Code: Select all

public abstract class GrooveDialogWidget extends Composite implements Service_IWindowManaged {...}


Then an example of a class I would like to design

Code: Select all

public class Design_Notification_Message_OK extends GrooveDialogWidget {...}


Thanks Eric, love the product btw!

[Eric Clayberg]

The Designer mode is unavailable, as in I cannot see the Source/Design Tabs to switch to Designer mode.

It sounds like you just need to use the GWT Designer (WindowBuilder) Editor rather than the standard Java Editor. See...

http://download.instantiations.com/D2WB ... indow.html

[robnauticus]

So simple! Thanks!!! Must have missed the obvious.

Take Care,
Rob

[Eric Clayberg]

Glad that worked for you.