Let us say you have a ui design where every-other day is styled a different
color and that we only have global styles available.
Now, the "correct" way to do this is for the user to add the styles to each
day of each month. The problem, of course, is that we as library designers
do not know how many months the application designer anticipates their user
trolling through, and for each day in each month in each year we will end up
accumulating global state.
Now recently, as a team, we have been moving to a model where we care a lot
less about memory efficiency, so we can use that argument to change the
design and remove the visible date mechanics.
Cheers,
Emily
On Tue, Dec 2, 2008 at 9:03 PM, Ray Ryan <[EMAIL PROTECTED]> wrote:
> I'm working through the big date picker review:
>
> http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thread/thread/486babc9bb0863a9
>
> I don't understand why we provide addGlobalStyleToDateand
> addStyleToVisibleDates, especially since the latter will explode in your
> face if you call it on an invisible date, except when it doesn't in web
> mode.
>
> Why don't we get rid of the visibleDate variants, and drop the "global"
> from the others?
>
> rjrjr
>
>
--
"There are only 10 types of people in the world: Those who understand
binary, and those who don't"
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
