<!DOCTYPE display PUBLIC "-//Liferay//DTD Display 4.0.0//EN" "http://www.liferay.com/dtd/liferay-display_4_0_0.dtd">
<display>
- <category name="IT Mill Toolkit">
+ <category name="Vaadin">
<portlet id="PortletDemoPortlet" />
<portlet id="SimpleReserverPortlet" />
<portlet id="SelectDemoPortlet" />
xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd">
<portlet>
<portlet-name>PortletDemoPortlet</portlet-name>
- <display-name>IT Mill Toolkit PortletDemo</display-name>
+ <display-name>Vaadin PortletDemo</display-name>
<portlet-class>com.vaadin.terminal.gwt.server.ApplicationPortlet</portlet-class>
<init-param>
<name>application</name>
</portlet>
<portlet>
<portlet-name>SimpleReserverPortlet</portlet-name>
- <display-name>IT Mill Toolkit SimpleReserver</display-name>
+ <display-name>Vaadin SimpleReserver</display-name>
<portlet-class>com.vaadin.terminal.gwt.server.ApplicationPortlet</portlet-class>
<init-param>
<name>application</name>
</portlet>
<portlet>
<portlet-name>FeatureBrowserPortlet</portlet-name>
- <display-name>IT Mill Toolkit FeatureBrowser</display-name>
+ <display-name>Vaadin FeatureBrowser</display-name>
<portlet-class>com.vaadin.terminal.gwt.server.ApplicationPortlet</portlet-class>
<init-param>
<name>application</name>
</portlet>
<portlet>
<portlet-name>ChatServletPortlet</portlet-name>
- <display-name>IT Mill Toolkit ChatServlet</display-name>
+ <display-name>Vaadin ChatServlet</display-name>
<portlet-class>com.vaadin.terminal.gwt.server.ApplicationPortlet</portlet-class>
<init-param>
<name>application</name>
</portlet>
<portlet>
<portlet-name>BrowserDemoPortlet</portlet-name>
- <display-name>IT Mill Toolkit BrowserDemo</display-name>
+ <display-name>Vaadin BrowserDemo</display-name>
<portlet-class>com.vaadin.terminal.gwt.server.ApplicationPortlet</portlet-class>
<init-param>
<name>application</name>
\r
\r
<web-app>\r
- <display-name>IT Mill Toolkit</display-name>\r
- <description>IT Mill Toolkit examples</description>\r
+ <display-name>Vaadin</display-name>\r
+ <description>Vaadin examples</description>\r
\r
<context-param>\r
<param-name>productionMode</param-name>\r
<param-value>false</param-value>\r
- <description>IT Mill Toolkit production mode</description>\r
+ <description>Vaadin production mode</description>\r
</context-param>\r
<!-- Permit use of IT Mill Testing Tools for this servlet continer -->
<context-param>
</context-param>
<servlet>
- <servlet-name>ITMillToolkitApplicationRunner</servlet-name>
+ <servlet-name>VaadinApplicationRunner</servlet-name>
<servlet-class>com.vaadin.terminal.gwt.server.ApplicationRunnerServlet</servlet-class>
</servlet>
</servlet>
<servlet-mapping>
- <servlet-name>ITMillToolkitApplicationRunner</servlet-name>
+ <servlet-name>VaadinApplicationRunner</servlet-name>
<url-pattern>/run/*</url-pattern>
</servlet-mapping>\r
\r
<body>
<iframe id="__gwt_historyFrame" style="width:0;height:0;border:0;overflow:hidden" src="javascript:false"></iframe>
- <p>Multiple toolkits per html file test page</p>
+ <p>Multiple Vaadin applications per html file test page</p>
<div id="fb" style="height:400px;border:2px solid red;margin:0"></div>
<div id="calc" style="border:2px solid green;margin:0"></div>
* <p>
* The <code>QueryContainer</code> is the specialized form of Container which is
* Ordered and Indexed. This is used to represent the contents of relational
- * database tables accessed through the JDBC Connection in the Toolkit Table.
+ * database tables accessed through the JDBC Connection in the Vaadin Table.
* This creates Items based on the queryStatement provided to the container.
* </p>
*
}
- log("Toolkit application servlet version: " + cnf.getServletVersion());
+ log("Vaadin application servlet version: " + cnf.getServletVersion());
log("Widget set is built on version: " + VERSION);
log("Application version: " + cnf.getApplicationVersion());
main.removeAllComponents();
main
.addComponent(new Label(
- "In Toolkit 5 we introduce new componens. Previously we"
+ "In Toolkit 5 we introduce new components. Previously we"
+ " usually used setStyle or some other methods on possibly "
+ "multiple steps to configure component for ones needs. These new "
+ "server side components are mostly just classes that in constructor "
* Proof of concept how to create a decent login screen that works with browsers
* PW managers. (Browsers don't autofill generated login forms)
*
- * TODO generalize js to work inside iframes (if toolkit is inside iframe)
+ * TODO generalize js to work inside iframes (if a Vaadin application is inside
+ * iframe)
*
* TODO extract login form to a external template.
*
* </p>
* <p>
* Since <code>DateField</code> extends <code>AbstractField</code> it implements
- * the {@link com.vaadin.data.Buffered}interface. A
- * <code>DateField</code> is in write-through mode by default, so
- * {@link com.vaadin.ui.AbstractField#setWriteThrough(boolean)}must be
- * called to enable buffering.
+ * the {@link com.vaadin.data.Buffered}interface. A <code>DateField</code> is in
+ * write-through mode by default, so
+ * {@link com.vaadin.ui.AbstractField#setWriteThrough(boolean)}must be called to
+ * enable buffering.
* </p>
*
* @author IT Mill Ltd.
* This can be overridden to handle conversions or to throw an exception, or
* to fire an event.
*
- * The default behavior is likely to change in the next major version of the
- * toolkit - a Property.ConversionException will be thrown.
+ * The default behavior is likely to change in the next major version of
+ * Vaadin - a Property.ConversionException will be thrown.
*
* @param dateString
* @return parsed Date
*
* By default it is encouraged to used default formatting defined by Locale,
* but due some JVM bugs it is sometimes necessary to use this method to
- * override formatting. See Toolkit issue #2200.
+ * override formatting. See Vaadin issue #2200.
*
* @param dateFormat
* the dateFormat to set
projects / vaadin-framework.git / commitdiff