The GWT team is happy to announce the availability of Google Web Toolkit 1.6 Milestone 2! Binary distributions are available for download directly from the GWT Google Code project.
If you have already tried GWT 1.6 Milestone 1, you may not notice much difference in Milestone 2. Changes have mostly been general polish and various small bug fixes. For the nitty-gritty details of the changes since the previous milestone, see the attached source control commit logs. You can also watch the GWT bug tracker for the most up-to-date list of resolved issues ( http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...). As for doc, the javadoc that comes bundled with the distribution should be up-to-date, but the online Developer Guide ( http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) is still being tweaked.
We anticipate that GWT 1.6 M2 will be the last milestone build for this version. After a few more bugs fixes and a bit more doc, we expect it to be followed soon by a release candidate build. In the meanwhile, please report bugs to the GWT issue tracker ( http://code.google.com/p/google-web-toolkit/issues/list) after doing a quick search to see if your issue has already been reported. If you encounter a bug in 1.6 M2 that you think qualifies as a showstopper, we would greatly appreciate it if you'd also reply on this thread to alert the engineering team.
As always, remember that GWT milestone builds like this are use-at-your-own-risk. Don't be surprised if it takes a bit of trial and error to get everything to work, and we don't recommend it for production use quite yet.
I doubt it is considered a showstopper. No-one took any notice when I mentioned it for 1.5 and 1.6.0, but it severely limits what I would like to be able to do. There are a number of widgets which cannot be used anywhere inside DisclosurePanels and StackPanels and probably other things.
For example: add a SplitPanel to a DisclosurePanel and in IE the split is set at 0 but can be moved, in FF/Safari/Chrome and, I think, Opera, it is at 0 and cannot be moved
There are a number of other combinations like this. Here's some example code:
public class Main implements EntryPoint { public void onModuleLoad() { DisclosurePanel d = new DisclosurePanel("Click To Open"); RootPanel.get().add(d); HorizontalSplitPanel s = new HorizontalSplitPanel(); d.add(s); s.setLeftWidget(new Label("Left")); s.setRightWidget(new Label("Right")); s.setSize("200px", "100px"); s.setSplitPosition("100px"); }
id's in HTMLPanels have to be unique within an application for every HTMLPanel every time you use it. so, for example, if you go to a database and get some HTML returned, say <div id=name>Fred</div>
then
getElementById("name").getInnerHTML()
will return 'Fred'
But from then on, every getElementById("name").getInnerHTML() will return 'Fred', even if you create a new instance of the same class, even if you create an instance of a completely different class
I reported this behaviour for version 1.4 for RootPanel back in 2007 (issue#1937). Nothing has happened about it but I was recommended to use HTMLPanel. This has now become ususable, too.
Is it worth adding a new issue, or will the v1.4 issue cover it?
Hi Ian,
Thanks for bringing this back up on the radar. I've updated Issue #1937 so
that the team can take another look at the issue and consider it for
inclusion for 1.6. Given that the HTMLPanel solution no longer works, this
should probably be fixed for 1.6. The issue log should be seeing some action
soon, so keep an eye out for that.
On Mon, Mar 2, 2009 at 5:22 PM, Ian Bambury <ianbamb...@gmail.com> wrote:
> id's in HTMLPanels have to be unique within an application for every
> HTMLPanel every time you use it. so, for example, if you go to a database
> and get some HTML returned, say
> <div id=name>Fred</div>
> then
> getElementById("name").getInnerHTML()
> will return 'Fred'
> But from then on, every getElementById("name").getInnerHTML() will return
> 'Fred', even if you create a new instance of the same class, even if you
> create an instance of a completely different class
> I reported this behaviour for version 1.4 for RootPanel back in 2007
> (issue#1937). Nothing has happened about it but I was recommended to use
> HTMLPanel. This has now become ususable, too.
> Is it worth adding a new issue, or will the v1.4 issue cover it?
Agreed, this doesn't sound like a showstopper, but still should be
investigated for a fix in a future release if not in 1.6.
I couldn't find this issue reported on the Issue Tracker. Feel free to add
this to the tracker - the details provided in the message below should be
enough for the issue report itself. I'll add it myself in case you don't get
a chance to get to it later today.
On Mon, Mar 2, 2009 at 4:39 PM, Ian Bambury <ianbamb...@gmail.com> wrote:
> I doubt it is considered a showstopper. No-one took any notice when I
> mentioned it for 1.5 and 1.6.0, but it severely limits what I would like to
> be able to do.
> There are a number of widgets which cannot be used anywhere inside
> DisclosurePanels and StackPanels and probably other things.
> For example: add a SplitPanel to a DisclosurePanel and in IE the split is
> set at 0 but can be moved, in FF/Safari/Chrome and, I think, Opera, it is at
> 0 and cannot be moved
> There are a number of other combinations like this. Here's some example
> code:
> public class Main implements EntryPoint
> {
> public void onModuleLoad()
> {
> DisclosurePanel d = new DisclosurePanel("Click To Open");
> RootPanel.get().add(d);
> HorizontalSplitPanel s = new HorizontalSplitPanel();
> d.add(s);
> s.setLeftWidget(new Label("Left"));
> s.setRightWidget(new Label("Right"));
> s.setSize("200px", "100px");
> s.setSplitPosition("100px");
> }
> }
Just installed M2 and took a look around. I must say I like it - feels
more natural to me. For a new project I wanted to start in 1.6, I
didn't want to migrate in the middle and update all the deprecated
stuff.
Haven't put it through its paces yet. But first thing - I have control
of web.xml :)
> Just installed M2 and took a look around. I must say I like it - feels
> more natural to me. For a new project I wanted to start in 1.6, I
> didn't want to migrate in the middle and update all the deprecated
> stuff.
> Haven't put it through its paces yet. But first thing - I have control
> of web.xml :)
> Specifically, which version of the Servlet API does it support ? I
> hope 2.4 is supported.
> On Mar 5, 8:24 am, Riyaz Mansoor <riyaz.mans...@gmail.com> wrote:
> > Just installed M2 and took a look around. I must say I like it - feels
> > more natural to me. For a new project I wanted to start in 1.6, I
> > didn't want to migrate in the middle and update all the deprecated
> > stuff.
> > Haven't put it through its paces yet. But first thing - I have control
> > of web.xml :)
On Thu, Feb 26, 2009 at 4:45 AM, Bruce Johnson <br...@google.com> wrote:
> The GWT team is happy to announce the availability of Google Web Toolkit
> 1.6 Milestone 2! Binary distributions are available for download directly
> from the GWT Google Code project.
> If you have already tried GWT 1.6 Milestone 1, you may not notice much
> difference in Milestone 2. Changes have mostly been general polish and
> various small bug fixes. For the nitty-gritty details of the changes since
> the previous milestone, see the attached source control commit logs. You can
> also watch the GWT bug tracker for the most up-to-date list of resolved
> issues (
> http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...).
> As for doc, the javadoc that comes bundled with the distribution should be
> up-to-date, but the online Developer Guide (
> http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) is still
> being tweaked.
> We anticipate that GWT 1.6 M2 will be the last milestone build for this
> version. After a few more bugs fixes and a bit more doc, we expect it to be
> followed soon by a release candidate build. In the meanwhile, please report
> bugs to the GWT issue tracker (
> http://code.google.com/p/google-web-toolkit/issues/list) after doing a
> quick search to see if your issue has already been reported. If you
> encounter a bug in 1.6 M2 that you think qualifies as a showstopper, we
> would greatly appreciate it if you'd also reply on this thread to alert the
> engineering team.
> As always, remember that GWT milestone builds like this are
> use-at-your-own-risk. Don't be surprised if it takes a bit of trial and
> error to get everything to work, and we don't recommend it for production
> use quite yet.
> On Thu, Feb 26, 2009 at 4:45 AM, Bruce Johnson <br...@google.com> wrote:
>> The GWT team is happy to announce the availability of Google Web Toolkit
>> 1.6 Milestone 2! Binary distributions are available for download directly
>> from the GWT Google Code project.
>> If you have already tried GWT 1.6 Milestone 1, you may not notice much
>> difference in Milestone 2. Changes have mostly been general polish and
>> various small bug fixes. For the nitty-gritty details of the changes since
>> the previous milestone, see the attached source control commit logs. You can
>> also watch the GWT bug tracker for the most up-to-date list of resolved
>> issues (
>> http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...).
>> As for doc, the javadoc that comes bundled with the distribution should be
>> up-to-date, but the online Developer Guide (
>> http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) is still
>> being tweaked.
>> We anticipate that GWT 1.6 M2 will be the last milestone build for this
>> version. After a few more bugs fixes and a bit more doc, we expect it to be
>> followed soon by a release candidate build. In the meanwhile, please report
>> bugs to the GWT issue tracker (
>> http://code.google.com/p/google-web-toolkit/issues/list) after doing a
>> quick search to see if your issue has already been reported. If you
>> encounter a bug in 1.6 M2 that you think qualifies as a showstopper, we
>> would greatly appreciate it if you'd also reply on this thread to alert the
>> engineering team.
>> As always, remember that GWT milestone builds like this are
>> use-at-your-own-risk. Don't be surprised if it takes a bit of trial and
>> error to get everything to work, and we don't recommend it for production
>> use quite yet.
Hi Hez,
As Vitali mentioned, marking these downloads as deprecated is our way of
keeping them from view on the main download page. The milestone builds
aren't fit for production, so we want to make sure no one mistakenly
downloads a milestone build for work that they're planning to put into
production.
> On Thu, Feb 26, 2009 at 4:45 AM, Bruce Johnson <br...@google.com> wrote:
>> The GWT team is happy to announce the availability of Google Web Toolkit
>> 1.6 Milestone 2! Binary distributions are available for download directly
>> from the GWT Google Code project.
>> If you have already tried GWT 1.6 Milestone 1, you may not notice much
>> difference in Milestone 2. Changes have mostly been general polish and
>> various small bug fixes. For the nitty-gritty details of the changes since
>> the previous milestone, see the attached source control commit logs. You can
>> also watch the GWT bug tracker for the most up-to-date list of resolved
>> issues (
>> http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=statu...).
>> As for doc, the javadoc that comes bundled with the distribution should be
>> up-to-date, but the online Developer Guide (
>> http://code.google.com/docreader/#p=google-web-toolkit-doc-1-6) is still
>> being tweaked.
>> We anticipate that GWT 1.6 M2 will be the last milestone build for this
>> version. After a few more bugs fixes and a bit more doc, we expect it to be
>> followed soon by a release candidate build. In the meanwhile, please report
>> bugs to the GWT issue tracker (
>> http://code.google.com/p/google-web-toolkit/issues/list) after doing a
>> quick search to see if your issue has already been reported. If you
>> encounter a bug in 1.6 M2 that you think qualifies as a showstopper, we
>> would greatly appreciate it if you'd also reply on this thread to alert the
>> engineering team.
>> As always, remember that GWT milestone builds like this are
>> use-at-your-own-risk. Don't be surprised if it takes a bit of trial and
>> error to get everything to work, and we don't recommend it for production
>> use quite yet.
Hi All
I have an issue, I want to drag and drop the panel, It can be
horizontal or vertical or any other panel so that i can change it
property(like change its size), but it is not supporting for the
panels it is supporting for simple widgets like label,button,text box
and able to change it property also.
I try to do but facing issue.
Example:
AbsolutePanel ab=new AbsolutePanel();
Label LHP = new Label("HorizontalPanel");
LHP.addClickHandler(new ClickHandler(){
public void onClick(ClickEvent event) {
HorizontalPanel newHP = new HorizontalPanel();
newHP.setSize("50", "50"); // on click panel size must be
fixed,user can change it size
newHP.setBorderWidth(2); // broder
ab.add(newHP); // adding panel to absolutePanel
dragController.makeDraggable(newHP);
// This listner is called when a panel is clicked
newHP.addMouseDownHandler(new MouseDownHandler(){
public void onMouseDown(MouseDownEvent event) {
// TODO Auto-generated method stub
Label proplab=new Label("Property Pallet");
}
});
Here addMouseDownHandler it is not supporting please any one can help
me in this regard.
> Hi All
> I have an issue, I want to drag and drop the panel, It can be
> horizontal or vertical or any other panel so that i can change it
> property(like change its size), but it is not supporting for the
> panels it is supporting for simple widgets like label,button,text box
> and able to change it property also.
> I try to do but facing issue.
> Example:
> AbsolutePanel ab=new AbsolutePanel();
> Label LHP = new Label("HorizontalPanel");
> LHP.addClickHandler(new ClickHandler(){
> public void onClick(ClickEvent event) {
> HorizontalPanel newHP = new HorizontalPanel();
> newHP.setSize("50", "50"); // on click panel size must be
> fixed,user can change it size
> newHP.setBorderWidth(2); // broder
> ab.add(newHP); // adding panel to absolutePanel
> dragController.makeDraggable(newHP);
> // This listner is called when a panel is clicked
> newHP.addMouseDownHandler(newMouseDownHandler(){
> public void onMouseDown(MouseDownEvent event) {
> // TODO Auto-generated method stub
> Label proplab=new Label("Property Pallet");
> }
> });
> Here addMouseDownHandler it is not supporting please any one can help
> me in this regard.
