Sounds really cool.
That being said, you said "RFC"...so... :-)
> This approach ties the column width to the view, not to the Column
> itself, so users can use different widths for mobile and desktop
> views.
Personally, I'd rather just do:
column.setWidth(20, Unit.PX);
Than the ColumnsWidths abstraction.
...besides, in canonical GWT MVP, wouldn't you do something like:
interface XxxView { HasData<T> table(); }
class MobileView {
void foo() {
columnA.setWidth(20, Unit.PX);
}
}
class DesktopView {
void foo() {
columnA.setWidth(200, Unit.PX);
}
}
...are you really going to want to share widths across desktop/web? Or,
even if you do, should that be something your presenter worries about?
I suppose if the widths relative--but even if the widths are relative,
it still seems like that is a code reuse concern between the views, and
not something the presenter should be concerned about.
(Look at that, Column is even an abstract class, so you can add setWidth
without a breaking change. ;-) )
- Stephen
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
