I really don't want to go to the new ScrollPanel in MGWT 2.0 and have to fix those same problems again ( which the beta version I tried last year made me think I would have to ). For instance, I had lots of problems in MGWT 1.2 with scroll panels, which I finally resolved. My bigger concern is that I know some things work differently now ( at least they did when I tried one of the beta MGWT 2.0 versions ), which means what worked in MGWT 1.2 might not work in MGWT 2.0. Don't get me wrong, an IDE like Eclipse helps immensely with this type of upgrade, largely because it clearly shows all the API changes and lets you fix one at a time. That said, I would also appreciate an upgrade guide immensely. Granted, this only makes it so that Eclipse knows to use a new version, and can clearly report any new bugs because of API changes. To the best of your knowledge, does the new final version of ScrollPanel ( 2.0.0 ) work pretty much the same as the old version ( 1.1.2 ), at least with regards to API and user experience?įirst of all, for those curious on some upgrade steps, see this discussion here, which uses Maven. One thing I am definitely going to do is setup a separate Eclipse project for MGWT 2.0 so I can have two applications side by side, using different versions of MGWT.Īlso, one of the biggest reasons I did not complete the migration was because, at least for the beta version I was using, something I fixed with my ScrollPanel usage in MGWT 1.1.2 did not work in MGWT 2.0.0. Eclipse makes some of these migration issues a little easier, but still tedious. But eventually I will have to bite the bullet and migrate, and a guide would be helpful. Eventually just went back to MGWT 1.1.2 because I knew it worked. The last time I tried to migrate my app, I ran into quite a few problems ( change in package structure, LayoutPanel going away, etc ). I am also wondering if/when there is going to be a migration guide? I could swear I saw one of the MGWT developers mention such a guide, so that is why I ask. Porting would be much easier, if you could keep old classes/methods with deprecate annotation and a comment how to replace them, instead of simple removing themīut independend from this problems m-gwt is great, thank you for the work.UiBinder-XML-Files get complicate with all xmlns entries, in the past a simple xmlns:mgwt="urn:import.client.widget" was enough.Whenever I enable ie6/7 Support with (sorry can't drop it at work), compile fails at MCheckBox. I compile mixed applications with desktop (pure gwt) and mobile (m-gwt) output depending on mgwt.formfactor.The 1.x Showcase provided the nice tablet feature to show navigation on the left in landscape mode and hide it in portrait mode, is there a way to bring this feature back to 2.x?.The Manifest-Handling seems not work anymore, I've found no PropertyProvider for the new properties mgwt.formfactor and nsity.KeyUpEvent and KeyPressEvent are no longer supported by MSearchBox, how can I update search result whenever the input changes.Keyboard navigationĮnable optional keyboard navigation by setting the prop key-nav. Make the toolbar span the maximum available width, by increasing spacing between the button groups, input groups and dropdowns, by setting the prop justify. Note, if you want smaller or larger buttons or controls, set the size prop directly on the, , and components. Similar to the example above, you'll likely need some utility classes though to space things properly. New Edit Undo Item 1 Item 2 Item 3 Save Cancel Usageįeel free to mix input groups and dropdowns with button groups in your toolbars.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |