--- title: Client-Side Module Entry-Point order: 2 layout: page --- [[clientsideapp.entrypoint]] = Client-Side Module Entry-Point A client-side application requires an __entry-point__ where the execution starts, much like the [methodname]#init()# method in server-side Vaadin UIs. Consider the following application: [source, java] ---- package com.example.myapp.client; 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.user.client.ui.RootPanel; import com.vaadin.ui.VButton; public class MyEntryPoint implements EntryPoint { @Override public void onModuleLoad() { // Create a button widget Button button = new Button(); button.setText("Click me!"); button.addClickHandler(new ClickHandler() { @Override public void onClick(ClickEvent event) { mywidget.setText("Hello, world!"); } }); RootPanel.get().add(button); } } ---- Before compiling, the entry-point needs to be defined in a module descriptor, as described in the next section. [[clientsideapp.entrypoint.descriptor]] == Module Descriptor The entry-point of a client-side application is defined, along with any other configuration, in a client-side module descriptor, described in <<../clientside/clientside-module#clientside.module,"Client-Side Module Descriptor">>. The descriptor is an XML file with suffix [filename]#.gwt.xml#. [source, xml] ---- ---- You might rather want to inherit the [classname]#com.google.gwt.user.User# to get just the basic GWT widgets, and not the Vaadin-specific widgets and classes, most of which are unusable in pure client-side applications. You can put static resources, such as images or CSS stylesheets, in a [filename]#public# folder (not a Java package) under the folder of the descriptor file. When the module is compiled, the resources are copied to the output folder. Normally in pure client-side application development, it is easier to load them in the HTML host file or in a [classname]#ClientBundle# (see GWT documentation), but these methods are not compatible with server-side component integration, if you use the resources for that purpose as well. y user interface library: https://github.com/jquery/jquery-uiwww-data
aboutsummaryrefslogtreecommitdiffstats
path: root/ui/i18n/datepicker-it-CH.js
blob: 9895da4cc32150ba22ae6e232c2c2dbac397c77d (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

/* Italian initialisation for the jQuery UI date picker plugin. */
/* Written by Antonello Pasella (antonello.pasella@gmail.com). */
( function( factory ) {
	if ( typeof define === "function" && define.amd ) {

		// AMD. Register as an anonymous module.
		define( [ "../widgets/datepicker" ], factory );
	} else {

		// Browser globals
		factory( jQuery.datepicker );
	}
}( function( datepicker ) {

datepicker.regional[ "it-CH" ] = {
	closeText: "Chiudi",
	prevText: "&#x3C;Prec",
	nextText: "Succ&#x3E;",
	currentText: "Oggi",
	monthNames: [ "Gennaio","Febbraio","Marzo","Aprile","Maggio","Giugno",
		"Luglio","Agosto","Settembre","Ottobre","Novembre","Dicembre" ],
	monthNamesShort: [ "Gen","Feb","Mar","Apr","Mag","Giu",
		"Lug","Ago","Set","Ott","Nov","Dic" ],
	dayNames: [ "Domenica","Lunedì","Martedì","Mercoledì","Giovedì","Venerdì","Sabato" ],
	dayNamesShort: [ "Dom","Lun","Mar","Mer","Gio","Ven","Sab" ],
	dayNamesMin: [ "Do","Lu","Ma","Me","Gi","Ve","Sa" ],
	weekHeader: "Sm",
	dateFormat: "dd.mm.yy",
	firstDay: 1,
	isRTL: false,
	showMonthAfterYear: false,
	yearSuffix: "" };
datepicker.setDefaults( datepicker.regional[ "it-CH" ] );

return datepicker.regional[ "it-CH" ];

} ) );