>
> I only realized now that we are depending on the ProgressBar
> in incubator... so if I read this right it might get scrapped from GWT :-
It depends on whether we can implement it without using a ResizeTimer in a
way that makes sense. Really, the only problem with ProgressBar is
positioning t
Hi,
I only realized now that we are depending on the ProgressBar in
incubator... so if I read this right it might get scrapped from GWT :-
S.
David
On Jan 12, 7:04 pm, John LaBanca wrote:
> Incubator Users -
>
> The Google Web Toolkit Incubator project began as a proving grounds for new
> widge
Daniel,
Last time I looked at HTML5 audio support in browsers (in the context of
putting it in to gwt-voices) it was fairly lacking. It's probably a good
time to revisit that though. I'd love to get better native support for audio
since the current state of affairs (i.e. everything before HTML5) l
[+fred, just to make sure he sees this]
On Mon, Feb 1, 2010 at 11:26 AM, dflorey wrote:
> See:
>
>
> http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/4f5fb0cbd007fa25/e6a70c6a26a444cd?lnk=gst&q=compatibility+animations#e6a70c6a26a444cd
>
> On 1 Feb., 17:23, dfl
See:
http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/4f5fb0cbd007fa25/e6a70c6a26a444cd?lnk=gst&q=compatibility+animations#e6a70c6a26a444cd
On 1 Feb., 17:23, dflorey wrote:
> What about Fred Sauer's gwt voices project?
> AFAK it has an elegant approach how to p
What about Fred Sauer's gwt voices project?
AFAK it has an elegant approach how to provide flash based fallback if
certain capabilities are not supported by the browser itself.
On 1 Feb., 14:25, Joel Webber wrote:
> To be clear, we do recognize the importance of starting to support HTML5
> const
To be clear, we do recognize the importance of starting to support HTML5
constructs that don't work on all browsers, though we need to find a clear
way to indicate to developers that a particular library or widget won't work
in some cases. None of us have ever worked through all the nuances of how
As you'll see in the first note in this thread, Incubator is closing down.
Having your work in its own project is exactly the right thing to do. If it
becomes an appropriate addition for GWT proper, we'll eagerly help you
integrate it. In the meantime, the community can use it and shape it without
I've developed "gwt-html5-media", which implements all the common
functionality described in the "Media Element" section of the HTML5
spec, including the specific functionality for Video and Audio tags,
including all of the events and settings. I could use some help
testing and improving it and per
Any plans for touch interfaces?
Ability to replace mouse events with touch events or new DomImpl with
touch events.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Both nightly build and developer snapshots would be even better, best
of both worlds.
Developer snapshots provide the best way for hardcore developers to
sync their communication on the development progress.
Nightly builds are easy to setup and provide users an easy way to see
if a particular bug
"developer snapshot" releases would be really nice.
We build infrequently from trunk and we currently guess what might be
a good version to grab our internal snapshot from. Having a developer
snapshot would help us when we are looking to grab the "latest"
version for our internal use.
Chris
Hmm, a nightly build sounds like a cool idea, I wouldn't mind seeing that as
well.
--
Arthur Kalmenson
On Thu, Jan 21, 2010 at 3:28 AM, David wrote:
> Hi,
>
> It would be nice that the GWT team would release some development
> builds once in a while. That would be very usefull at the point whe
Hi,
It would be nice that the GWT team would release some development
builds once in a while. That would be very usefull at the point where
new things are added to the trunk. This way you can get a lot more
input from the community, since it makes it much easier to use a more
experimental version
Thank you John for your explanation. Now I understand the reason why
you are shutting down the incubator. What I am suggesting is that
developers should have a place where they can see what new features
(libraries,...) are being developed and not to stumble upon this new
features by chance (like I
Libraries and widgets that we want to incubate will be moved into separate
projects. Instead of downloading one incubator jar, you'll be able to (have
to) download each project individually. Like Ray said, we're going to
commit most new features directly to trunk, but we may still want to
incubat
Then, how about a list of new features in the trunk since the last
release. That way developers would know if they should become involved
in the nontrivial (but not too hard) task of compiling GWT from
source. I take the last comment back if such a list exists. I could
not find it.
Regards.
On J
On Wed, Jan 20, 2010 at 6:52 AM, monkeyboy wrote:
> Hello John.
>
> I'm glad to see that PagingScrollTable will make it to the GWT trunk.
> Even now it is a useful widget but I can't wait to see the final
> version. I would like to ask a few questions. I am sorry to hear that
> the incubator will
Hello John.
I'm glad to see that PagingScrollTable will make it to the GWT trunk.
Even now it is a useful widget but I can't wait to see the final
version. I would like to ask a few questions. I am sorry to hear that
the incubator will be shut down. I was wandering what (if anything)
will replace
I just created a new page on the wiki where we can share our
design-in-progress and get feedback:
http://code.google.com/p/google-web-toolkit/wiki/DataBackedWidgetsDesign
We've barely started discussing the requirements, let alone the design, so
we have nothing to report at the moment, but hopeful
It would be cool to have a shared google doc for the table design.
I've added some ideas of simple annotation based table creation to my
treetable branch:
http://code.google.com/p/google-web-toolkit-incubator/wiki/TreeTable
On Jan 13, 1:28 am, jay wrote:
> One request, especially around the tabl
One request, especially around the table work
Please use this forum generously--ask questions about APIs and bounce
ideas around publicly so that we have ample opportunity to chime in
(and fewer excuses if the delivered solution doesn't work for us).
Thanks!
jay
On Jan 12, 10:04 am, Jo
22 matches
Mail list logo
