It looks like you've already decided to nail one foot to the floor. If you
can't share common code w/ the client, you'll have to make due with
providing a least common denominator format (the server will pre-digest the
data for the client) and use RPC to transfer the data.

On Wed, Sep 29, 2010 at 7:36 AM, Dan <[email protected]> wrote:

> Hello everyone,
>
> currently I am working in a Project, which may use GWT to realize a
> GUI. Right now i am evaluating wich advantages and disadvantages GWT
> has in stock for us. Within that research i stumbled across a few
> Problems which i need some opinions on from other people.
>
> The project itself is split into two Java-projects, one of which
> contains the GWT-GUI, the other one offers the infrastructure behind
> the GUI, which will be shared amongst several other projects too.
> Therefore, modifying the shared project should not be an option.
>
> Now, I created a Widget for the GWT-GUI, which is able to visualize a
> certain complex datastructure from the shared project. The problem I
> have is the fact that the Widget makes it necessary to have the
> datastructure compiled into JavaScript, since the Widget is part of
> client side code. If i now break my rule of not modifying the shared
> project, i can declare the shared project as a GWT-Module, and have
> the datastructure in question compiled into JavaScript by GWT.
>
> However, the datastructure has dependencies to most of the shared
> project, so i would have to let GWT compile most of that shared
> project, making the JavaScript file which is handed over to the client
> enormously large. Moreover, the datastructure depends on classes in a
> third-party .jar file, which i can not easily make a GWT-Module.
>
> My question about these circumstances is: Is there any elegant way to
> make the datastructure compilable to JavaScript, WITHOUT having the
> whole shared project compiled, especially the external jar must not be
> compiled. Or is there any other way to visualize that datastructure
> without exposing it to the client-side of GWT?
>
> Any suggestions on this topic will be appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<google-web-toolkit%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

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

Reply via email to