"Randall" <[EMAIL PROTECTED]> writes: > I think I found the post you are referring to. It says there is a bug > in Safari that prevents the calendar from working properly. Couldn't > we modify the calendar or do a browser check and revert back to a less > functional calendar when the better one is not supported?
This would make both calendars a requirement when just one would suffice. I believe that Kevin's proposal of making a separate egg just to make it easily available is enough -- or putting some link and explaining why is there such alternative... With regards to Kevin's concerns with LGPL and "linking", TG works perfectly without this code and it is a standalone piece of code that can be used the same way inside and outside of TG (except if it is included in some widget...), so I don't believe it will be a problem. BUT... :-) -- Jorge Godoy <[EMAIL PROTECTED]>
