I am thinking of developing a Ext GWT "GXT" 3.0 module that I need to embed to a GXT 2.x web application. Is it a good strategy to load a GXT module in a iframe. I mean, so I can develop the new module using GXT 3 and still "embed" the module in a GXT 2.x based web application. The application is quite big, so I don't think that there will be anyone in the project team that will be able to adapt to 3.0 just yet.
It is possible to run them together in the same project thanks to them using a different namespace.
http://www.sencha.com/learn/running-ext-gwt-2-and-3-together/
Also if you plan to convert your older GXT2.x modules to GXT3 there is a legacy module to help with the transition. See :
http://www.sencha.com/forum/showthread.php?197973-How-to-use-the-Legacy-module&p=787639&viewfull=1#post787639
Related
I'm working on a product which is an RCP application based on Eclipse 3.x api. Now we are trying to move it to Eclipse 4.x. We are using some internal classes in our code. I've already read the tutorial provided by Vogella about migrating to Eclipse 4.x from 3.x, but I'm still not getting how to start.
We want to take advantage of the new Eclipse features, my main question is that we have good number of views, layouts in our old code, so what should be the approach I should follow. Also is there a way to create an application model from my older application using 3.x API.
I'm stuck and not getting how to proceed.
this really depends what you are trying to do. Do you just want to update your IDE? Or should the project be based on the e4 platform.
I recently updated a project from 3.x to the new IDE. This works very good, the compatibility layer does a good job and you are able to run the application with minimal changes. However if you do this, you cannot use the benefits of the e4 platform.
If you want to move your application to e4, thats more work to do. Mostly you will not want to touch all the old code, so there is a possiblity to have 3.x and e4 plugins run together in your application. Thats done with the e4 bridge and wrapper classes for old code. Most of the IDE views and editor are also still based on 3.x, so if you use them, the e4 bridge is also a good way to incorporate them.
Some information can be found here:
http://tomsondev.bestsolution.at/2011/06/10/how-to-apply-the-e4-programming-model-to-3-x/
http://eclipsesource.com/blogs/2012/06/18/migrating-from-eclipse-3-x-to-eclipse-4-e4/
Andy
I've read both the tutorial.But I am stucked and got too much confused as to where to start from. Basically 3 features are there
1. css styling of widgets(which i understood and did a bit of it)
2. to introduce dependency injection in my code
3. to put the application model
What approach I should follow?
This document helped me in deciding which strategy to adopt. http://www.eclipse.org/forums/index.php/fa/17403/ for migration.Indicates clearly which strategy you should adopt based on your existing code structure.Hope it helps
I'm working on project using GWT (with Vaadin) and I'm looking for a good, preferably, integrated flow chart library. The library can be commerical and preferrably is integrated with Vaadin.
Any recommendations?
I would go with mx-graph gwt wrapper with vaadin:
http://forum.jgraph.com/questions/4390/using-mxgraph-with-vaadin
http://jgraph.github.io/mxgraph/docs/manual.html#2.2.2.1
I am trying to move from java to scala . I am basically a web developer where i use zkoss, vaadin as my framework. Do scala has widget based framework.Fully ajax based? I haven't tried lift and play need some advice is that fully ajax based?
The Vaadin framework can be used with Scala. There is even a project called Scaladin to help you with that. Since you already know it, I suggest you try learning scala with that framework. After you have a good understand of scala you should have a better base for what framework to choose in case you want to leave Vaadin.
Here are some resources:
Scala and Vaadin HOWTO
Scaladin wiki
Develop Vaadin apps with Scala
Try Scala+GWT with one of web frameworks (Lift, Play and etc.)
I'm trying to work with GXT 3 widgets in the GWT designer, without success.
I successfully managed to use GXT 2.2 with the designer but when switched to GXT 3, it seems that resources and images are missing. this seems odd because there are no folders for resources and images in GXT 3. What's going on here?
I am using GXT 3.0 GPL and Eclipse Indigo 3.7
Check this related forum question: GWT Designer suport for GXT 3.0?
IMHO - It is very easy for Sencha to make money tweaking code a little bit to produce a next release and charge users for upgrade. Creating complex UI designer plug in for Ecliple / netbeans is not an easy money.
Overall: They are greedy and short-sighted.
Unfortunately, GXT team do not consider to support GWT designer for GXT 3.0. Google GWT Designer team also do not have any intention to support GXT 3.0 .. WYSWYG editor is just illusion for GXT 3.0 .. http://www.sencha.com/forum/showthread.php?170585-GWT-Designer-suport-for-GXT-3.0
GXT 3 is not compatible with the Google plugin For Eclipse, thus you won't be able to use the GWT Designer to manipulate GXT 3 widgets.
The Google plugin and GWT Designer are compatible only with GXT 2.2 and currently there are not active projects designated to provide support for GXT3, due to the GPE becoming an open-source. This is, in my opinion, a job for the sencha community.
Is it possible to develop an application in groovy using GWT components?
Luis
If you want to use Groovy on the server-side and GWT for the UI, that is certainly possible. You can use Grails (a Groovy web framework on the server), and the Grails GWT plugin to help you integrate GWT with this framework.
I don't think so, because the GWT compiler is basically a Java to JavaScript source compiler (it would be possible if the GWT compiler needed Java bytecode). You can use Groovy on the server side though.
Right now you cant use Groovy on the client side. One big reason is that Groovy relies a lot on introspection, and this is not available on GWT.
I have also wondered this, as it would be very nice. Vaadin essentially does this and you can use their plugin: http://grails.org/plugin/vaadin
Doing it this model, though, it is compiling components into Javascript and delivering from the server. But unlike GWT components, these are calling back to the server every time you touch the API (though of course with Vaadin you can use GWT components as well).