gxt

I need a Column in which it was possible to put a Widget. I have this: import com.google.gwt.cell.client.AbstractCell; import com.google.gwt.safehtml.shared.SafeHtmlBuilder; import com.google.gwt.user.client.ui.Widget; public class WidgetGridCell extends AbstractCell<Widget> { Widget widget; public WidgetGridCell(Widget widget) { this.widget = widget; } @Override public void render(Context paramContext, Widget param, SafeHtmlBuilder pb) { } } But I do not know how to include the widget in HTML P.S. Or not Widget, only GWT Button will suit me. See here for a number of examples of AbstractCell

I created an EditorGrid using GXT 2.2.3.In that grid,one column is with the TextField as Editor.My code is as below: ColumnConfig checkinTimecolumn=new ColumnConfig(); checkinTimecolumn.setId("checkinTime"); checkinTimecolumn.setHeader("Check In Time"); checkinTimecolumn.setWidth(80); checkinTimecolumn.setMenuDisabled(true); checkinTimecolumn.setSortable(false); checkinTimecolumn.setStyle("width:100%;"); checkinTimecolumn.setStyle("padding-right:3px;"); final TextField<String> checkintime = new TextField<String>(); checkintime.setAllowBlank(true); checkintime.setWidth(15); checkintime

When starting a new application, what are the things that you weight out in order to decide whether to go with ExtGWT or ExtJS? For a programmer that knows both Javascript and Java, what is best to choose? Are there still performance issues with ExtGWT compared to ExtJS - back in 2008 people said that ExtGWT is slow for adding a large number of DOM nodes compared to ExtJS but they enjoyed the debugging support ExtGWT provided while in ExtJS debugging is hard and painful How do you find development in ExtGWT compared to ExtJS? Is the compile time of an ExtGWT app an issue - I saw it takes about

since the 2.6.0 release of GWT which dropped support of ie6 browser my current project which also uses GXT is failing to compile with the following error: Loading inherited module 'com.sencha.gxt.ui.GXT' Loading inherited module 'com.sencha.gxt.data.Data' Loading inherited module 'com.sencha.gxt.core.Core' [ERROR] The value ie6 was not previously defined. [ERROR] Line 96: Unexpected exception while processing element 'set-property' i tried to set <set-property name="gxt.user.agent" value="safari3, safari4, safari5, chrome, air, gecko1_8, gecko1_9"/> and the <extend-property name="user.agent" .

I get the following exception when I try deploying my webApp on weblogic12: weblogic.application.ModuleException: java.lang.IllegalAccessError: tried to access method com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap; from class org.jboss.weld.logging.WeldMessageConveyor at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) at weblogic.application.internal.flow.ModuleStateDriver$3

Support GXT 3 responsitive design out of the box or is there another way to get a good mobile application with GXT running. I know about Sencha Touch but I don't want to develop two standalone apps.. Regards, Markus 2015-01-22 update without mentioning a date, but looks promising: sencha.com: Taking a Look at Sencha GXT and GWT it seems in summer 2014 (around now :-)) we should get this natively with GXT 4.0 from Sencha: http://www.sencha.com/blog/gxt-roadmap-update/ full tablet support (touch gestures, smooth scrolling, drag and drop, and more...) But it seems with touch4j ( http://emitrom

How can frozen columns be implemented in GXT 3.x (from Sencha)? Ext-JS, another product from Sencha seems to implement this, but I can't see where the Java based GXT implement the same thing: http://dev.sencha.com/deploy/ext-4.0.0/examples/grid/locking-grid.html The basic idea is that you need two different scrolling containers, one with the fixed column(s), one with the scrolling columns. Each of these need to be in a distinct viewport, so the standard Grid/GridView doesn't work well with this - they make assumptions about how scrolling should behave, so simply subclassing one or both is