Hi David,
here in Lisbon/Portugal, which has the same timezone as London
(currently UTC+1), the datefield example also works fine!
João Ventura
Em 02-04-2012 22:03, David Ripplinger escreveu:
Thank you all for the info.
I've discovered that the bug is time-zone dependent. I asked my
brothers (one in Utah, another in Alabama) to test it, and they have
the same behavior as I do (in Massachusetts). Luke lives in the UK
(working). Peter, where roughly do you live?
I then switched the time on my computer to London's time zone and
retried the web page. It works then.
If anyone has any ideas off the top of their heads why the time zone
is affecting it, let me know. I'll keep looking into it, and use the
debugging capability if I don't find the solution right away.
I would like to try Pyjamas desktop to get familiar with its debugging
capabilities, but I feel kind of dumb I haven't been able to get it to
run on my computer yet. Do you just have the "import pyjd" before any
other imports, and then make sure the pyjd.run command is executed,
like in the examples? Then, do I just simply run my python code for
the main controller (e.g. client.py or DateField.py), or am I supposed
to pass in that file as an argument to something else? I tried it that
way, but it complains that there is no module named comtypes. If this
does not have a trivial answer, I can move it into a separate
discussion thread.
David
On Mon, Apr 2, 2012 at 15:57, Peter Bittner <[email protected]
<mailto:[email protected]>> wrote:
David,
>> Furthermore, I find it odd that the example on
>> pyjs.org/examples <http://pyjs.org/examples> is producing a
different result depending on whether I am
>> accessing the web page or someone else is. I have tried it in
Chrome and
>> Firefox with the same results. As a side note, when I tried it
in IE, it
The Calendar example works fine for me too for both, the version
online on pyjs.org/examples <http://pyjs.org/examples> and the
latest git locally on my machine.
I've tested with Chrome 16, FF 11, and Opera 11 - all on Ubuntu Linux.
>> I will keep looking into it and see if I can get some debug
stuff to work.
>> Where do I get this new logging module?
The FAQ question on logging (aka "debug output") is not updated yet on
pyjs.org <http://pyjs.org>, but it in the repository already: (see
bottom of the
following page)
http://pyjs.org/pygit/#file=doc/pyjs_site/public/faq/answers/i_want_to_throw_some_debug_output_onto_the_screen_how_do_i_best_do_that.html&id=a3dae43bcd48c152068e7095499709e5928a61b3&mimetype=text-html
<http://pyjs.org/pygit/#file=doc/pyjs_site/public/faq/answers/i_want_to_throw_some_debug_output_onto_the_screen_how_do_i_best_do_that.html&id=a3dae43bcd48c152068e7095499709e5928a61b3&mimetype=text-html>
In brief: 2 possibilities
a) quick and easy: (= AppendLogger, i.e. output on the web page)
from pyjamas import log
...
log.debug("bla bla bla")
log.info <http://log.info>("variable %s also there", myvar)
b) full-featured: (= identical feature set of Python's logging module)
from pyjamas import logging
...
logging.debug("bla bla bla") # Python style; prints to stderr
log = logging.getAlertLogger() # try also Append / Console /
PrintLogger
log.info <http://log.info>("bla bla bla")
debug, info, warning, error are the log levels. The default log level
is set to "debug", so everything is printed.
Have fun,
Peter
