[gwt-contrib] Re: UIBinder and the new Layout system
Brett, You should be able to use the already-checked-in LayoutPanel to do anything you could have done with AbsolutePanel before. And it should be the case that you can get rid of all of your manual resize code (that's the intention, anyway). Also, if you run into any problems embedding other widgets (like the aforementioned FlexTable or FormPanle), please let me know as well. Thanks, joel. On Thu, Aug 20, 2009 at 1:06 AM, brett.wooldridge brett.wooldri...@gmail.com wrote: Joel, Will be happy to test new layouts and review API. Unfortunately, I don't use Dock, Stack, or Split in my app. I do use Absolute. And because of an interior scrolling area that fills the client, a sprinkling of resize code (after beating my head against CSS for a few days). I do use FormPanel and FlexTable, but I would expect both of those to be minimally affected or not affected by your layout as they are somewhat micro-level layouts not needing resize/reflow behaviors. -Brett On Aug 18, 12:32 am, Joel Webber j...@google.com wrote: The situation as I see it is this. The old layout system has two huge problems:1. Some widgets (e.g., StackPanel) *cannot* be made to work as expected in standards mode, because of changes to table rendering behavior. 2. It's not really a system, in the sense that it can be highly unpredictable. I am quite convinced it is impossible to fix these issues in any fundamental way, without taking an entirely different approach. See the design doc ( http://code.google.com/p/google-web-toolkit/wiki/LayoutDesign) for my justification of this particular approach. In particular, I think it's worth noting that while Google Wave uses different actual code (they wrote their implementation before I did, but they didn't have to support IE6, which drastically simplified the problem), it's philosophically the same thing. This works quite well for them. As for reimplementing widgets like StackPanel, I mention in the design-doc that several such widgets will need to be replaced, and I'm working on that right now. The APIs won't be identical, because they need a bit more explicit size information in some cases, but I don't believe it will be too much trouble (I'm rewriting some of the samples to be sure). I'm hoping to have initial implementations of Dock, Stack, and Split widgets checked in over the next couple of days. If you could try using them and give me API and behavior feedback, that would be really helpful. Thanks, joel. On Sat, Aug 15, 2009 at 2:13 PM, brett.wooldridge brett.wooldri...@gmail.com wrote: Cool. Then another question about the future of the new layout system. Is the current thinking that eventually it *will* replace all of the older panels? I mean, is there buy-in at Google that that is a desired track for this project. Or will the new layout system remain parallel to the original? Also, is it possible to re-write StackPanel etc. to be compatible with the new system so that people have a migration? I don't personally care about migration, because I'm starting nearly from scratch, but I don't want to adopt a side-car layout system that doesn't have a track into the mainline of GWT. Thanks for your answers and your efforts. If there is anything I can do to help, let me know, I will be glad to pitch in a hand with some layouts or UIBinder parsers etc. if you are willing to give direction. Brett On Aug 15, 12:44 am, Joel Webber j...@google.com wrote: Brett, I am going to be writing adding custom parsers for the new layout panels sometime soon. And the new layout system will be de facto in the sense that I'm updating all the samples to use it (and possibly adding another sample). We obviously won't be removing the old widgets (e.g., StackPanel) that won't play nice in standards mode until a later release, so we don't break anyone's existing projects. Cheers, joel. On Fri, Aug 14, 2009 at 11:17 AM, brett.wooldridge brett.wooldri...@gmail.com wrote: I have been tracking the process of the UIBinder and the new pure CSS- based layout system being driven by Joel at google. I assume these two will play nicely together in 2.0? Or will custom parsers be needed to use UIBinder with the new layout system? Sounds like the UIBinder parsers API won't be ready for public consumption in the first release. Lastly, will the new layout system be the *defacto* layout system in 2.0? Please say yes. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: UIBinder and the new Layout system
Joel, Will be happy to test new layouts and review API. Unfortunately, I don't use Dock, Stack, or Split in my app. I do use Absolute. And because of an interior scrolling area that fills the client, a sprinkling of resize code (after beating my head against CSS for a few days). I do use FormPanel and FlexTable, but I would expect both of those to be minimally affected or not affected by your layout as they are somewhat micro-level layouts not needing resize/reflow behaviors. -Brett On Aug 18, 12:32 am, Joel Webber j...@google.com wrote: The situation as I see it is this. The old layout system has two huge problems:1. Some widgets (e.g., StackPanel) *cannot* be made to work as expected in standards mode, because of changes to table rendering behavior. 2. It's not really a system, in the sense that it can be highly unpredictable. I am quite convinced it is impossible to fix these issues in any fundamental way, without taking an entirely different approach. See the design doc (http://code.google.com/p/google-web-toolkit/wiki/LayoutDesign) for my justification of this particular approach. In particular, I think it's worth noting that while Google Wave uses different actual code (they wrote their implementation before I did, but they didn't have to support IE6, which drastically simplified the problem), it's philosophically the same thing. This works quite well for them. As for reimplementing widgets like StackPanel, I mention in the design-doc that several such widgets will need to be replaced, and I'm working on that right now. The APIs won't be identical, because they need a bit more explicit size information in some cases, but I don't believe it will be too much trouble (I'm rewriting some of the samples to be sure). I'm hoping to have initial implementations of Dock, Stack, and Split widgets checked in over the next couple of days. If you could try using them and give me API and behavior feedback, that would be really helpful. Thanks, joel. On Sat, Aug 15, 2009 at 2:13 PM, brett.wooldridge brett.wooldri...@gmail.com wrote: Cool. Then another question about the future of the new layout system. Is the current thinking that eventually it *will* replace all of the older panels? I mean, is there buy-in at Google that that is a desired track for this project. Or will the new layout system remain parallel to the original? Also, is it possible to re-write StackPanel etc. to be compatible with the new system so that people have a migration? I don't personally care about migration, because I'm starting nearly from scratch, but I don't want to adopt a side-car layout system that doesn't have a track into the mainline of GWT. Thanks for your answers and your efforts. If there is anything I can do to help, let me know, I will be glad to pitch in a hand with some layouts or UIBinder parsers etc. if you are willing to give direction. Brett On Aug 15, 12:44 am, Joel Webber j...@google.com wrote: Brett, I am going to be writing adding custom parsers for the new layout panels sometime soon. And the new layout system will be de facto in the sense that I'm updating all the samples to use it (and possibly adding another sample). We obviously won't be removing the old widgets (e.g., StackPanel) that won't play nice in standards mode until a later release, so we don't break anyone's existing projects. Cheers, joel. On Fri, Aug 14, 2009 at 11:17 AM, brett.wooldridge brett.wooldri...@gmail.com wrote: I have been tracking the process of the UIBinder and the new pure CSS- based layout system being driven by Joel at google. I assume these two will play nicely together in 2.0? Or will custom parsers be needed to use UIBinder with the new layout system? Sounds like the UIBinder parsers API won't be ready for public consumption in the first release. Lastly, will the new layout system be the *defacto* layout system in 2.0? Please say yes. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: UIBinder and the new Layout system
The situation as I see it is this. The old layout system has two huge problems:1. Some widgets (e.g., StackPanel) *cannot* be made to work as expected in standards mode, because of changes to table rendering behavior. 2. It's not really a system, in the sense that it can be highly unpredictable. I am quite convinced it is impossible to fix these issues in any fundamental way, without taking an entirely different approach. See the design doc ( http://code.google.com/p/google-web-toolkit/wiki/LayoutDesign) for my justification of this particular approach. In particular, I think it's worth noting that while Google Wave uses different actual code (they wrote their implementation before I did, but they didn't have to support IE6, which drastically simplified the problem), it's philosophically the same thing. This works quite well for them. As for reimplementing widgets like StackPanel, I mention in the design-doc that several such widgets will need to be replaced, and I'm working on that right now. The APIs won't be identical, because they need a bit more explicit size information in some cases, but I don't believe it will be too much trouble (I'm rewriting some of the samples to be sure). I'm hoping to have initial implementations of Dock, Stack, and Split widgets checked in over the next couple of days. If you could try using them and give me API and behavior feedback, that would be really helpful. Thanks, joel. On Sat, Aug 15, 2009 at 2:13 PM, brett.wooldridge brett.wooldri...@gmail.com wrote: Cool. Then another question about the future of the new layout system. Is the current thinking that eventually it *will* replace all of the older panels? I mean, is there buy-in at Google that that is a desired track for this project. Or will the new layout system remain parallel to the original? Also, is it possible to re-write StackPanel etc. to be compatible with the new system so that people have a migration? I don't personally care about migration, because I'm starting nearly from scratch, but I don't want to adopt a side-car layout system that doesn't have a track into the mainline of GWT. Thanks for your answers and your efforts. If there is anything I can do to help, let me know, I will be glad to pitch in a hand with some layouts or UIBinder parsers etc. if you are willing to give direction. Brett On Aug 15, 12:44 am, Joel Webber j...@google.com wrote: Brett, I am going to be writing adding custom parsers for the new layout panels sometime soon. And the new layout system will be de facto in the sense that I'm updating all the samples to use it (and possibly adding another sample). We obviously won't be removing the old widgets (e.g., StackPanel) that won't play nice in standards mode until a later release, so we don't break anyone's existing projects. Cheers, joel. On Fri, Aug 14, 2009 at 11:17 AM, brett.wooldridge brett.wooldri...@gmail.com wrote: I have been tracking the process of the UIBinder and the new pure CSS- based layout system being driven by Joel at google. I assume these two will play nicely together in 2.0? Or will custom parsers be needed to use UIBinder with the new layout system? Sounds like the UIBinder parsers API won't be ready for public consumption in the first release. Lastly, will the new layout system be the *defacto* layout system in 2.0? Please say yes. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: UIBinder and the new Layout system
Cool. Then another question about the future of the new layout system. Is the current thinking that eventually it *will* replace all of the older panels? I mean, is there buy-in at Google that that is a desired track for this project. Or will the new layout system remain parallel to the original? Also, is it possible to re-write StackPanel etc. to be compatible with the new system so that people have a migration? I don't personally care about migration, because I'm starting nearly from scratch, but I don't want to adopt a side-car layout system that doesn't have a track into the mainline of GWT. Thanks for your answers and your efforts. If there is anything I can do to help, let me know, I will be glad to pitch in a hand with some layouts or UIBinder parsers etc. if you are willing to give direction. Brett On Aug 15, 12:44 am, Joel Webber j...@google.com wrote: Brett, I am going to be writing adding custom parsers for the new layout panels sometime soon. And the new layout system will be de facto in the sense that I'm updating all the samples to use it (and possibly adding another sample). We obviously won't be removing the old widgets (e.g., StackPanel) that won't play nice in standards mode until a later release, so we don't break anyone's existing projects. Cheers, joel. On Fri, Aug 14, 2009 at 11:17 AM, brett.wooldridge brett.wooldri...@gmail.com wrote: I have been tracking the process of the UIBinder and the new pure CSS- based layout system being driven by Joel at google. I assume these two will play nicely together in 2.0? Or will custom parsers be needed to use UIBinder with the new layout system? Sounds like the UIBinder parsers API won't be ready for public consumption in the first release. Lastly, will the new layout system be the *defacto* layout system in 2.0? Please say yes. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: UIBinder and the new Layout system
Brett, I am going to be writing adding custom parsers for the new layout panels sometime soon. And the new layout system will be de facto in the sense that I'm updating all the samples to use it (and possibly adding another sample). We obviously won't be removing the old widgets (e.g., StackPanel) that won't play nice in standards mode until a later release, so we don't break anyone's existing projects. Cheers, joel. On Fri, Aug 14, 2009 at 11:17 AM, brett.wooldridge brett.wooldri...@gmail.com wrote: I have been tracking the process of the UIBinder and the new pure CSS- based layout system being driven by Joel at google. I assume these two will play nicely together in 2.0? Or will custom parsers be needed to use UIBinder with the new layout system? Sounds like the UIBinder parsers API won't be ready for public consumption in the first release. Lastly, will the new layout system be the *defacto* layout system in 2.0? Please say yes. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
