Elegant handling of user experience when new GWT application is deployed.
Is there an elegant solution to handle when a new release is deployed while you are in the GWT app? E.g. we want the application to notice a new version of itself and automatically do a full page refresh? Ideas? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/yKvYd8guTZwJ. 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.
Re: GWT Cells - Unnecessary headache?
Using a scroll panel and flow panel then means we have to build all the other benefits of the CellTable ourselves. For example pagers, sorting, columns, data providers. All those things are great. I guess my question is. It would be great if there were two versions of the list widgets. A Cell version for high performance and a widget version for existing functionality. GCJ On Wednesday, 19 December 2012 09:54:45 UTC-8, Jens wrote: > > You should use Cell widgets when you expect to display a lot of data to > get the full performance benefit of using Cell widgets. If you only want to > display a few things in a list then simply use ScrollPanel + FlowPanel > along with some CSS and add your "list entry" widgets to it. > Sure CellTable/DataGrid have some nice features like column sorting that > are not available in other GWT table like widgets but that does not mean > that you should use CellTable/DataGrid for absolutely everything. > > -- J. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/mIqnwr1Ju8oJ. 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 Cells - Unnecessary headache?
I have been using the cell widgets for a while now and am having trouble understanding their purpose. I attended Google IO 2010 when they were introduced and thought great GWT has some list and table widgets now. But quickly realised that after using them that all your existing widgets need to be re-engineered to enable use in the lists. Now whilst for performance I can understand why this is necessary, but given that these lists will be used in a lot of typical given that most people show < 20 records at a time, or often a lot less, it seems like there is a lot of work just to use these widgets. Therefore I am raising the question in order to get feedback. With GWT 2.5 we have the UiRenderer which offers some interesting abstraction issues but still requires you to significantly re-write your existing widgets. Thoughts? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/NurrlEqVpkwJ. 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.
UiRenderer KeyUp and KeyDown Events (GWT 2.5)
*Problem: *Having issues getting KeyUp and KeyDown events to be called with
UiRenderer.
Using the syntax below they don't always get called:
@UiHandler({"inputTextBox"})
void onKeyUpEvent(KeyUpEvent event, Element parent, String name)
(from:
https://developers.google.com/web-toolkit/doc/latest/DevGuideUiBinder#Rendering_HTML_for_Cells)
Switching to overriding onEnterKeyPressed results in an incorrect parent
element? So when I call:
renderer.getInputTextBox(parent).getValue()
The item isn't found because the parent is wrong?
*Question: *Has anyone successfully used KeyUp/KeyDown in a UiRenderer
context and successfully caught the KeyCode being pressed?
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/AwnCAXjUXx0J.
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.
Grid Control Recomendations
Besides the awful SmartGWT and ExtGWT (My opinion). What other third party grids can you recommend? Feel free to recommend Javascript grids that have the potential for a GWT Wrapper to be created for them. Thanks G -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/5nmZbv5nFlIJ. 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.
How to handle dependencies in minor UI controls within the MVP framework.
I aim to have a discussion on best practices with regards to the MVP framework and minor UI Controls. Imagine a typical MVP entity in your application where the view element is made up of many interesting UI controls. Some UI Controls contain further UI controls as the application is re-factored to contain each element in its own logical class. I have taken the presenter component to mean that all logical operations of the application should take place in the presenter so therefore any events that occur in the sub-sub UI controls should be wired back up to the presenter. I have a problem with this type of working in that imagine a click event, the parent UI has to handle that, then that is passed to another parent and then finally to the presenter where the click event is analysed and acted upon. I would much prefer a scenario where a, say for example, a navigationHelper dependency is injected into a view control that requires it, thereby it can be acted on immediately without having to wire up through the UIs to the presenter. I wonder if anyone had any thoughts on this as to the best practices in this scenario. Or should all controls in the application be created in the MVP style so that each object no matter how insignificant always has a presenter associated with it? Any thoughts are much appreciated! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/6wmFoJvvot4J. 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.
Re: GWT UIBinder content assist lag
This is happening to me as well. Osx-Eclipse-Helios -- 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.
Re: CrossSiteIframeLinker (xsiframe) ready for prime time?
I was wondering whether the xsiframe linker was ready? I have a debugging issue I would like to examine with IE and it doesn't appear to work in GWT 2.1. Any news on whether it is working for GWT 2.2? Cheers Gene -- 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.
Nested Views in MVP
Hi,
I have been reading the excellent article at:
http://code.google.com/webtoolkit/doc/latest/DevGuideMvpActivitiesAndPlaces.html
And love the new built in objects that facilitate the MVP design
paradigm. My initial thought is great but how does this system cope
with Nested Views or Dock Panel style layouts where various elements
can be clicked and the widget that changes isn't necessarily always
the center one?
Looking at the example code given for HelloMVP it looks like when you
go to a new Place when the Activity is started by calling the start
method a widget is passed in that is the containerWidget or host for
that presenter:
@Override
public void start(AcceptsOneWidget containerWidget, EventBus
eventBus) {
GoodbyeView goodbyeView = clientFactory.getGoodbyeView();
goodbyeView.setName(name);
containerWidget.setWidget(goodbyeView.asWidget());
}
Looking at the setup code from the onModuleLoad, a root SimplePanel is
added to the activity manager:
activityManager.setDisplay(appWidget);
This widget is then passed to the start method each time a new place
is revealed. Thus causing a screen refresh? each time a new place is
revealed.
How would you handle a scenario that has a Left hand menu (like gmail)
and a main container. Where clicking options in the LHS initiates a
new widget to be displayed in the center. Using the current logic it
looks like the whole screen is refreshed to show the newly selected
menu option and the center widget. Perhaps it does, and perhaps this
is ok, but it sounds hacky.
For example it would be nice if clicking a center widget not only
indicated what place to reveal but where that place/widget should be
revealed?
I am sure this scenario is very common and it may have a lot to do
with my naivety with this new methodology. If anyone has any
pointers, opinions or examples on this it would be greatly
appreciated.
Cheers
Gene
--
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-tool...@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.
