On Thu, May 24, 2012 at 12:42 AM, Norman Shelley <[email protected]> wrote:
>
> I have not found anything that indicates what the actual GWT Java
> source/revision were used to create each of the current pyjs GWT python
> objects.

unfortunately, none such mapping exists :-(  some kind of ala carte
from the 1.5-1.7? range IIRC.

>  The documentation just says: /library/gwt/libs tracking original gwt
> sources, without improvements

ah, that was ripped out some time ago by ... which document was that
in?  if you could open a quick ticket that would be fantastic ... or
just remove it and ill pull your branch on github ;-)

> It would be very nice to know the exact source revision and the URL to the
> source code that was used to create the related pjys GWT python object
> (traceability is a great feature).

couldn't agree more.

> This would make it easier to look at the actual GWT bug tracking issues to
> determine if necessary bugs have been fixed that have not been incorporated
> into the pjys GWT object
> Nice to understand what GWT version the pjys version is actually at - nice
> when reading Google's GWT documentation. People currently looking into pjys
> have no idea what version of GWT they will be starting at.
> Nice starting point in an attempt down the road to semi-automate
> daily/weekly/monthly/... tracking and updating of pyjs GWT objects to the
> current Java GWT objects.

there have been many changes custom to pyjs that make the mapping task
next to impossible. my thought at the moment is to "freeze" the
"pyjamas" library as-is, and call it round one, this way people don't
need to change their apps.  this doesn't mean it won't be updated or
improved, but it will never progress beyond GWT 1.x.  for 2.x, we will
find a way to maintain a mostly pure translation, with pyjs changes
layered on top.

this will be a part of ongoing work to break the UI libraries out of
the main distribution; i want to make it clear that 3rd party
implementations/frameworks are both possible *and* encouraged ... GWT
is just one path of many.

-- 

C Anthony

Reply via email to