Re: FF10, here we go again
Does the change cover the ESR version too? Cheers Marco On Feb 2, 7:03 am, Alan Leung acle...@google.com wrote: Currently under code review: http://gwt-code-reviews.appspot.com/1634803/ -Alan On Wed, Feb 1, 2012 at 10:06 AM, Adam a...@sevogle.com wrote: Well, hopefully their long term support of FF10, will allow it to be used for GWT dev for a while w/o all the hassle of updates all the time. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/4LKS7YD_0QsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Celltree - Add, Update, Remove Nodes
Here my third try: This way is recommended by gwt-commiter.
Please see following issue:
http://code.google.com/p/google-web-toolkit/issues/detail?id=7160
Current status:
* Adding is possible
* Removing is possible if not last child!
So, last open point, refresh the tree if last open child!
package com.test;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Map;
import com.google.gwt.cell.client.AbstractCell;
import com.google.gwt.core.client.EntryPoint;
import com.google.gwt.event.dom.client.ClickEvent;
import com.google.gwt.event.dom.client.ClickHandler;
import com.google.gwt.safehtml.shared.SafeHtmlBuilder;
import com.google.gwt.user.cellview.client.CellTree;
import com.google.gwt.user.client.ui.AbsolutePanel;
import com.google.gwt.user.client.ui.Button;
import com.google.gwt.user.client.ui.RootPanel;
import com.google.gwt.view.client.ListDataProvider;
import com.google.gwt.view.client.SingleSelectionModel;
import com.google.gwt.view.client.TreeViewModel;
public class MyCelltreeTest2 implements EntryPoint {
private AbsolutePanel absolutePanel;
private CellTree cellTree;
private Button btnAdd;
private Button btnRemove;
private MyTreeModel myTreeModel;
private SingleSelectionModelMyNode selectionModelCellTree =
null;
private MapMyNode, ListDataProviderMyNode mapDataProviders
= null;
private ListDataProviderMyNode rootDataProvider = null;
public void onModuleLoad() {
RootPanel rootPanel = RootPanel.get();
rootPanel.add(getAbsolutePanel(), 0, 0);
}
private AbsolutePanel getAbsolutePanel() {
if (absolutePanel == null) {
absolutePanel = new AbsolutePanel();
absolutePanel.setSize(612px, 482px);
absolutePanel.add(getCellTree(), 0, 0);
absolutePanel.add(getBtnAdd(), 265, 428);
absolutePanel.add(getBtnRemove(), 336, 428);
}
return absolutePanel;
}
private CellTree getCellTree() {
if (cellTree == null) {
myTreeModel = new MyTreeModel();
cellTree = new CellTree(myTreeModel, null);
cellTree.setSize(285px, 401px);
}
return cellTree;
}
private Button getBtnAdd() {
if (btnAdd == null) {
btnAdd = new Button(Add);
btnAdd.addClickHandler(new ClickHandler() {
public void onClick(ClickEvent event)
{
MyNode node =
selectionModelCellTree.getSelectedObject();
// if(node != null)
myTreeModel.add(node,
Bla);
}
});
}
return btnAdd;
}
private Button getBtnRemove() {
if (btnRemove == null) {
btnRemove = new Button(Remove);
btnRemove.addClickHandler(new ClickHandler() {
public void onClick(ClickEvent event)
{
MyNode node =
selectionModelCellTree.getSelectedObject();
// if(node != null)
myTreeModel.remove(node);
}
});
}
return btnRemove;
}
public class MyNode {
private String name;
private ArrayListMyNode childs; //nodes childrens
private MyNode parent; //track internal parent
public MyNode(String name) {
super();
parent = null;
this.name = name;
childs = new ArrayListMyNode();
}
public boolean hasChildrens() {
return childs.size()0;
}
public ArrayListMyNode getList() {
return childs;
}
public MyNode getParent() {
return parent;
}
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
}
public class MyTreeModel implements TreeViewModel {
public MyTreeModel() {
selectionModelCellTree = new
SingleSelectionModelMyNode();
mapDataProviders = new HashMapMyCelltreeTest2.MyNode,
ListDataProviderMyNode();
}
public void add(MyNode myparent, String name) {
MyNode child = new MyNode(name);
//root-node
if(myparent == null){
rootDataProvider.getList().add(child);
Activity Places - Remove Add of a widget for every new activity - Why?
Hello All:
I had a quick question regarding the implementation of Activity Places.
During the implementation of AP, specifically when working with the
activity, one overrides a method:
public void start(AcceptsOneWidget panel, EventBus eventBus) {
As seen above, the interface indicates that the container panel only takes
on widget or child. The consequence of this is that every time a new
activity is called, the child of the container panel is removed, the widget
to be added is also removed from any potential parent and then added to the
container panel.
Assuming I interpreted the code that handles this correctly, my question
is: Why the decision of adding/removing Vs having a Container Panel with a
Card Layout that takes widgets activating them when needed. In this case it
could be done in the activity start area.
I have tried to look around to see if somebody else asked this before and I
might even be missing the obvious, but I am particularly interested in the
rational behind the add/remove vs card layout approach here. I am thinking
it might be related to saving resources perhaps by having less elements
added to the DOM, but one would think there is a penalty also to pay when
adding/removing these views whenever a new place in the application is
reached.
Appreciate in advance any explanations/clarifications regarding this.
Thanks,
Alfredo
--
Alfredo Quiroga-Villamil
AOL/Yahoo/Gmail/MSN IM: lawwton
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
changing pages in GWT
Hello , i'm currently developing an exam project but i'm kind of started to GWT. So here's my question : I have a log in page which asks username and password to log in for students or teachers. After confirmation the informations of students or teachers, i would like to redirect user to his proper page (i mean change the log-in page to his proper page) , basicly i didn't understand how can i do that after clicking the CONFIRM button. Thanks for all help. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
New to GWT: Need Help
Hello
I try to write a little Application. I' ve the problem that I' don't
see all the hole page in the Browser. I've designed the page with the
UI Designer for Eclipse. There I see everything with the preview.
I only see the Toppanel (north), but not the SplitlayoutPanel (nor
the StackPanel or the Tree and also not the HTMLPanel) in the center!
When I debug the Source from my page in Chrome I see that the
Instructions for the widget in the panel are sent but I dont see them
on the screen.
Sorry for my english.
Someone knows what i'am doing worg?
Here is the code:
DesktopView.ui.xml:
!DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
ui:UiBinder xmlns:ui=urn:ui:com.google.gwt.uibinder
xmlns:g=urn:import:com.google.gwt.user.client.ui
xmlns:p1=urn:import:ch.asolution.pikett.client.ui
ui:style
/ui:style
g:DockLayoutPanel unit=EM
g:north size=5
p1:TopPanel ui:field=toppanel/
/g:north
g:center
g:SplitLayoutPanel
g:west size=150
g:StackLayoutPanel unit=EM
g:stack
g:header size=3Mitarbeiter/g:header
g:Tree animationEnabled=true
ui:field=mitarbeiterTree
g:TreeItem text=Mitarbeiter
bearbeiten state=true/
g:TreeItem text=Mitarbeiter
erstellen state=true/
g:TreeItem text=Mitarbeiter löschen
state=true/
/g:Tree
/g:stack
g:stack
g:header size=3Pikettplanung/g:header
g:Tree animationEnabled=true
ui:field=showTree
g:TreeItem text=Tagesansicht
state=true/
g:TreeItem text=Monatsansicht
state=true/
/g:Tree
/g:stack
/g:StackLayoutPanel
/g:west
g:center
g:HTMLPanel ui:field=detail/
/g:center
/g:SplitLayoutPanel
/g:center
/g:DockLayoutPanel
/ui:UiBinder
DestopView.java
package ch.asolution.pikett.client.ui;
import ch.asolution.pikett.client.presenter.DesktopPresenter;
import com.google.gwt.core.client.GWT;
import com.google.gwt.event.logical.shared.HasSelectionHandlers;
import com.google.gwt.uibinder.client.UiBinder;
import com.google.gwt.uibinder.client.UiField;
import com.google.gwt.user.client.ui.Composite;
import com.google.gwt.user.client.ui.DockLayoutPanel;
import com.google.gwt.user.client.ui.HasWidgets;
import com.google.gwt.user.client.ui.Tree;
import com.google.gwt.user.client.ui.TreeItem;
public class DesktopView extends Composite implements
DesktopPresenter.Display {
private static DesktopViewUiBinder uiBinder = GWT
.create(DesktopViewUiBinder.class);
@UiField
TopPanel toppanel;
@UiField
Tree mitarbeiterTree;
@UiField
Tree showTree;
@UiField
HasWidgets detail;
interface DesktopViewUiBinder extends
UiBinderDockLayoutPanel, DesktopView {
}
public DesktopView() {
DockLayoutPanel outer = uiBinder.createAndBindUi(this);
initWidget(outer);
}
@Override
public TopPanel getToppanel() {
return toppanel;
}
@Override
public HasWidgets getDetailPanel() {
return detail;
}
@Override
public HasSelectionHandlersTreeItem getMitarbeiter() {
return mitarbeiterTree;
}
@Override
public HasSelectionHandlersTreeItem getShow() {
return showTree;
}
}
DesktopPresenter.java
package ch.asolution.pikett.client.presenter;
import ch.asolution.pikett.client.ui.MitarbeiterView;
import ch.asolution.pikett.client.ui.TopPanel;
import ch.asolution.pikett.shared.User;
import com.google.gwt.event.logical.shared.HasSelectionHandlers;
import com.google.gwt.event.logical.shared.SelectionEvent;
import com.google.gwt.event.logical.shared.SelectionHandler;
import com.google.gwt.event.shared.HandlerManager;
import com.google.gwt.user.client.ui.HasWidgets;
import com.google.gwt.user.client.ui.TreeItem;
import com.google.gwt.user.client.ui.Widget;
public class DesktopPresenter implements Presenter {
public interface Display {
TopPanel getToppanel();
Re: Bug in CellTable.Resources when migrating to GWT 2.4
Thank you very much, Uninstalling the Google chrome frame does the trick, Unfortunately we need it :-( When do you expect to have a fix for this problem? Thanks Ayala -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
