Re: GWT pluggable GUIs

2011-06-14 Thread lemaiol
Hi Jaroslav,

Are you still interested on this topic? Maybe have a look at:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/42062c7f6cf8989b/e29d37a5f737d34e?lnk=gst&q=pluggable#e29d37a5f737d34e
and give feedback.

cheers,
Berto

On May 5, 10:51 am, Jaroslav Urban  wrote:
> Hello,
>
> I'm investigating the possibility to use GWT in our project. One of
> the requirements is the ability for extensible GUIs and possibly
> domain classes. I have the impression that it's not really possible
> (e.g. 
> seehttp://stackoverflow.com/questions/814647/is-it-possible-to-create-dy...).
>
> Let me explain our use case in more detail - basically we'd like our
> application to be extensible similarly to Eclipse platform. So the
> application would define a set of extension points that can be
> extended by plugins. One specific example - the application works with
> configurable entities that are configured via properties. The
> properties are typed (e.g. "file path" property has the type
> "fileURL") and each type can have a specific editing GUI (file
> selection dialog in case of the file path). We need the ability of
> plugins to describe such configurable entities, and define new types
> of the properties with possibly new editing GUIs. From the point of
> view of the plugin it would register something like "complexType" type
> with its editing GUI provided by "ComplexTypeEditor" class.
>
> In effect the application would consist of a set of plugins - we don't
> necessarily need the plugins to be loadable at run-time (restart of
> the application might be OK). My impression is this is not possible
> because the GWT compiler takes all modules of the application and
> creates one big JavaScript (for each permutation). This would mean
> that kind-of plugin-ability would be possible only at compile time -
> the resulting application cannot be freely composed of plugins.
>
> Best regards,
> Jaroslav Urban

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.



GWT pluggable GUIs

2011-05-05 Thread Jaroslav Urban
Hello,

I'm investigating the possibility to use GWT in our project. One of
the requirements is the ability for extensible GUIs and possibly
domain classes. I have the impression that it's not really possible
(e.g. see
http://stackoverflow.com/questions/814647/is-it-possible-to-create-dynamically-pluggable-gwt-widgets-portlets-in-separate-w).

Let me explain our use case in more detail - basically we'd like our
application to be extensible similarly to Eclipse platform. So the
application would define a set of extension points that can be
extended by plugins. One specific example - the application works with
configurable entities that are configured via properties. The
properties are typed (e.g. "file path" property has the type
"fileURL") and each type can have a specific editing GUI (file
selection dialog in case of the file path). We need the ability of
plugins to describe such configurable entities, and define new types
of the properties with possibly new editing GUIs. From the point of
view of the plugin it would register something like "complexType" type
with its editing GUI provided by "ComplexTypeEditor" class.

In effect the application would consist of a set of plugins - we don't
necessarily need the plugins to be loadable at run-time (restart of
the application might be OK). My impression is this is not possible
because the GWT compiler takes all modules of the application and
creates one big JavaScript (for each permutation). This would mean
that kind-of plugin-ability would be possible only at compile time -
the resulting application cannot be freely composed of plugins.

Best regards,
Jaroslav Urban

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.