/**
* <p>
* Base class required for all Vaadin applications. This class provides all the
- * basic services required by the toolkit. These services allow external
- * discovery and manipulation of the user, {@link com.vaadin.ui.Window windows}
- * and themes, and starting and stopping the application.
+ * basic services required by Vaadin. These services allow external discovery
+ * and manipulation of the user, {@link com.vaadin.ui.Window windows} and
+ * themes, and starting and stopping the application.
* </p>
*
* <p>
/**
* Gets the previous user of the application.
*
- * @return the previous Toolkit user, if user has not changed ever on
+ * @return the previous Vaadin user, if user has not changed ever on
* application it returns <code>null</code>
*/
public Object getPreviousUser() {
<body bgcolor="white">
<p>Provides several fully functional Vaadin example applications. These
-highlight certain aspects of the toolkit and how it can be
+highlight certain aspects of the Vaadin and how it can be
used to produce simple, elegant yet powerful user interface driven
applications.</p>
super(
"Dates",
"Dates",
- "The DateField component can be used to produce various date and time input fields with different resolutions. The date and time format used with this component is reported to the Toolkit by the browser.",
+ "The DateField component can be used to produce various date and time input fields with different resolutions. The date and time format used with this component is reported to Vaadin by the browser.",
new Feature[] {
//
new DatePopup(), //
}
} else {
- $wnd.alert("Toolkit app failed to initialize: " + this.id);
+ $wnd.alert("Vaadin app failed to initialize: " + this.id);
}
}-*/;
/**
* GWT's HasFocus is way too overkill for just receiving focus in simple
- * components. Toolkit uses this interface in addition to GWT's HasFocus to pass
+ * components. Vaadin uses this interface in addition to GWT's HasFocus to pass
* focus requests from server to actual ui widgets in browsers.
*
* So in to make your server side focusable component receive focus on client
/**
* Sends message to server that this action has been fired. Messages are
- * "standard" Toolkit messages whose value is comma separated pair of
+ * "standard" Vaadin messages whose value is comma separated pair of
* targetKey (row, treeNod ...) and actions id.
*
* Variablename is always "action".
/*
*
- * We need a hack make popup act as a child of VPopupView in toolkits
+ * We need a hack make popup act as a child of VPopupView in Vaadin's
* component tree, but work in default GWT manner when closing or
* opening.
*
import com.vaadin.terminal.gwt.client.BrowserInfo;
/**
- * In Toolkit UI this Overlay should always be used for all elements that
+ * In Vaadin UI this Overlay should always be used for all elements that
* temporary float over other components like context menus etc. This is to deal
* stacking order correctly with VWindow objects.
*/
/*
* Two types of Widgets can be focused, either implementing
- * GWT HasFocus of a thinner Toolkit specific Focusable
+ * GWT HasFocus of a thinner Vaadin specific Focusable
* interface.
*/
if (toBeFocused instanceof HasFocus) {
return;
}
- // Send initial AJAX page that kickstarts Toolkit application
+ // Send initial AJAX page that kickstarts a Vaadin application
writeAjaxPage(request, response, window, themeName, application);
} catch (final SessionExpired e) {
// supported, but the hack is make it possible to use linux and
// hosted mode browser for debugging. Note that due this hack,
// debugging gwt code in portals with linux will be problematic if
- // there are multiple toolkit portlets visible at the same time.
+ // there are multiple Vaadin portlets visible at the same time.
// TODO remove this when hosted mode on linux gets newer gecko
page.write("<iframe tabIndex=\"-1\" id=\"__gwt_historyFrame\" "
* <ul>
* <li>context=vaadin</li>
* <li>Runner servlet=run</li>
- * <li>Toolkit application=com.vaadin.demo.Calc</li>
+ * <li>Vaadin application=com.vaadin.demo.Calc</li>
* </ul>
*
* @param request
/**
* This example demonstrates custom layout. All components created here are
* placed using custom.html file. Custom layouts may be created with any web
- * designer tool such as Dreamweaver. To place Toolkit components into html
- * page, use divs with location tag as an identifier for Toolkit components, see
- * html page (themes/example/layout/custom.html) and source code below. Body
- * panel contents are changed when menu items are clicked. Contents are HTML
- * pages located at themes/example/layout directory.
+ * designer tool such as Dreamweaver. To place Vaadin components into html page,
+ * use divs with location tag as an identifier for Vaadin components, see html
+ * page (themes/example/layout/custom.html) and source code below. Body panel
+ * contents are changed when menu items are clicked. Contents are HTML pages
+ * located at themes/example/layout directory.
*
* @author IT Mill Ltd.
* @since 4.0.0
import com.vaadin.ui.Window;
/**
- * This example demonstrates layouts. Layouts are populated with sample Toolkit
+ * This example demonstrates layouts. Layouts are populated with sample Vaadin
* UI components.
*
* @author IT Mill Ltd.
private final Label result;
- private static final String DESCRIPTION = "Hyphothesis: Toolkit 4 has major architechtural problem when adding "
+ private static final String DESCRIPTION = "Hypothesis: Toolkit 4 has major architechtural problem when adding "
+ "small incrementall updates to a container which has either a lot or "
+ "some very slow components in it. Toolkit 5 has 'subtree caching' and a"
+ " small amount of logic in containers, so CommunicationManager can assure"
/**
* This example shows how Table, Select and Tree UI components can use
- * Containers. QueryContainer is used to bind SQL table rows into Toolkit UI
+ * Containers. QueryContainer is used to bind SQL table rows into Vaadin UI
* components. Table has few example actions added. Also embedding XHTML through
* Label components is used. Demonstrates: how to create
* <code>com.vaadin.data.Container</code> and set it as datasource to UI
* components <code>com.vaadin.ui.Component.Tree</code>, how to receive
- * ExpandEvent and implement
- * <code>com.vaadin.ui.Tree.ExpandListener</code>, how to use
- * <code>com.vaadin.event.Action</code>.
+ * ExpandEvent and implement <code>com.vaadin.ui.Tree.ExpandListener</code>, how
+ * to use <code>com.vaadin.event.Action</code>.
*
* @author IT Mill Ltd.
* @since 4.0.0
*
*/
-public class QueryContainerDemo extends com.vaadin.Application
- implements Action.Handler {
+public class QueryContainerDemo extends com.vaadin.Application implements
+ Action.Handler {
private static final String ACTION_DESCRIPTION = "Try right mouse button to initiate "
+ "actions menu.<br />Note: on Opera you use meta key "
table.addActionHandler(this);
table.setDescription(ACTION_DESCRIPTION);
- // populate Toolkit table component with test SQL table rows
+ // populate Vaadin table component with test SQL table rows
try {
final QueryContainer qc = new QueryContainer(
"SELECT * FROM employee", sampleDatabase.getConnection());
select.setCaption("All distinct units from employee table.");
select.setItemCaptionPropertyId("UNIT");
- // populate Toolkit select component with test SQL table rows
+ // populate Vaadin select component with test SQL table rows
try {
final QueryContainer qc = new QueryContainer(
"SELECT DISTINCT UNIT FROM employee", sampleDatabase
+ "actions menu. Note: on Opera you use meta key "
+ "and left mouse button.");
- // Populate Toolkit Tree using select component as data source
+ // Populate Vaadin Tree using select component as data source
tree.setContainerDataSource(select.getContainerDataSource());
}
import com.vaadin.ui.Window;
/**
- * This example demonstrates layouts. Layouts are populated with sample Toolkit
+ * This example demonstrates layouts. Layouts are populated with sample Vaadin
* UI components.
*
* @author IT Mill Ltd.
import com.vaadin.ui.Tree.ExpandEvent;
/**
- * Browsable file explorer using Toolkit Tree component. Demonstrates: how to
- * add items hierarchially into
- * <code>com.vaadin.ui.Component.Tree</code>, how to receive ExpandEvent
- * and implement <code>com.vaadin.ui.Tree.ExpandListener</code>.
+ * Browsable file explorer using Vaadin Tree component. Demonstrates: how to add
+ * items hierarchically into <code>com.vaadin.ui.Component.Tree</code>, how to
+ * receive ExpandEvent and implement
+ * <code>com.vaadin.ui.Tree.ExpandListener</code>.
*
* @since 4.0.0
*
import com.vaadin.ui.Component.Listener;
/**
- * Browsable file explorer using Toolkit Tree component. Demonstrates: how to
- * use <code>com.vaadin.ui.Component.Tree</code> datasource container,
- * how to create <code>com.vaadin.data.util.FilesystemContainer</code>,
- * how to read <code>com.vaadin.ui.Component.Event</code> objects, how
- * to receive and handle any event by implementing
- * <code>com.vaadin.ui.Component.Listener</code>.
+ * Browsable file explorer using Vaadin Tree component. Demonstrates: how to use
+ * <code>com.vaadin.ui.Component.Tree</code> datasource container, how to create
+ * <code>com.vaadin.data.util.FilesystemContainer</code>, how to read
+ * <code>com.vaadin.ui.Component.Event</code> objects, how to receive and handle
+ * any event by implementing <code>com.vaadin.ui.Component.Listener</code>.
*
* @since 4.0.0
*
*/
-public class TreeFilesystemContainer extends com.vaadin.Application
- implements Listener {
+public class TreeFilesystemContainer extends com.vaadin.Application implements
+ Listener {
// Filesystem explorer panel and it's components
private final Panel explorerPanel = new Panel("Filesystem explorer");
import com.vaadin.ui.Select;
import com.vaadin.ui.Window;
-public class UsingObjectsInSelect extends com.vaadin.Application
- implements ValueChangeListener {
+public class UsingObjectsInSelect extends com.vaadin.Application implements
+ ValueChangeListener {
private final Select select = new Select();
private final Label selectedTask = new Label("Selected task",
}
/**
- * Sample class which is bind in Toolkit components
+ * Sample class which is bound to Vaadin components
*
*/
public class Task {
// TODO Add browser agent string
private final String description = WELCOME_TEXT_LOWER
- + "<br /><br />Vaadin Toolkit version: "
- + ApplicationServlet.VERSION;
+ + "<br /><br />Vaadin version: " + ApplicationServlet.VERSION;
public IntroWelcome() {
super();
\r
@Override\r
protected String getDescription() {\r
- return "Toolkit should not choke on deep component trees. 15 levels should be minimum to survive.";\r
+ return "Vaadin should not choke on deep component trees. 15 levels should be minimum to survive.";\r
}\r
\r
@Override\r
layout = lo;\r
}\r
layout.addComponent(new Label(\r
- "FF did it! Toolkit, Mozilla and you win! Dare to try again?"));\r
+ "FF did it! Vaadin, Mozilla and you win! Dare to try again?"));\r
root.setLayout(r);\r
}\r
\r
*
* TODO theme
*
- * TODO refine docs, make LoginBox a standard toolkit component
+ * TODO refine docs, make LoginBox a standard Vaadin component
*
* TODO article
*
+ "<body onload='setTarget();'>"
+ "Iframe generated by LoginBox. PW managers can autofill form. Form handled by LoginBox "
+ "that will fire LoginEvents. Will post into another iframe, from where the script "
- + "will find toolkit client that will be force synced. <form id='loginf' target='logintarget'>"
+ + "will find Vaadin client that will be force synced. <form id='loginf' target='logintarget'>"
+ "Username : <input type='text' name='username'>"
+ "Password : <input type='password' name='password'>"
+ "<input type='submit' value='login'>" + "</form>"
* <p>
* A container component with freely designed layout and style. The layout
* consists of items with textually represented locations. Each item contains
- * one sub-component, which can be any Toolkit component, such as a layout. The
+ * one sub-component, which can be any Vaadin component, such as a layout. The
* adapter and theme are responsible for rendering the layout with a given style
* by placing the items in the defined locations.
* </p>
import com.vaadin.terminal.gwt.server.AbstractApplicationServlet;
/**
- * LoginForm is a Toolkit component to handle common problem among Ajax
+ * LoginForm is a Vaadin component to handle common problem among Ajax
* applications: browsers password managers don't fill dynamically created forms
* like all those UI elements created by Vaadin.
* <p>
*
* <p>
* This method should not be invoked directly. Instead the
- * {@link com.vaadin.Application#addWindow(Window)} method should be
- * used to add the window to an application and
- * {@link com.vaadin.Application#removeWindow(Window)} method for
- * removing the window from the applicion. These methods call this method
- * implicitly.
+ * {@link com.vaadin.Application#addWindow(Window)} method should be used to
+ * add the window to an application and
+ * {@link com.vaadin.Application#removeWindow(Window)} method for removing
+ * the window from the applicion. These methods call this method implicitly.
* </p>
*
* <p>
* in client too. Not the one that is rendered last (the case we'd get if
* implemented in Focusable only).
*
- * To focus component from Toolkit application, use Focusable.focus(). See
+ * To focus component from Vaadin application, use Focusable.focus(). See
* {@link Focusable}.
*
* @param focusable
projects / vaadin-framework.git / commitdiff