I appreciate the pointer, but I've read the documentation and it, frankly, sucks.
It's really dismaying that a company with the resources of Google is doing such a piss-poor job at delivering this toolkit. First of all, this simple thing should be trivial to solve - one line of code. The point of GAE is that it's supposed to be easy, right? Second, you shouldn't have to read 3 or 4 incomplete, poorly written, disjoint pieces of documentation to figure something out. It's not like this is a free service. Google really ought to ask themselves whether they want to do this and then look at the documentation Adobe, for example, provides for their tools. Even in Beta the Flex documentation and tools were orders of magnitude better than what Google provides. This is like, read the GAE "documentation", then read the django docs and figure out what does and does not apply, then read the docs for some python library, but we don't support it so you can't use it..... Then write your own version of the python library and maybe you can do this thing that would be one line of code in Django or Java or any good toolkit. Ok two lines of code if you count the import statements. On Jan 26, 4:05 am, ryan <[email protected]> wrote: > it's not a direct answer to your question, buthttp://timezones.appspot.com/ > has some relevant info and code snippets. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
