Revision 18873
tags/tmp_build/frameworks/_fwAndami/.externalToolBuilders/Ant.launch | ||
---|---|---|
1 |
<?xml version="1.0" encoding="UTF-8"?> |
|
2 |
<launchConfiguration type="org.eclipse.ant.AntBuilderLaunchConfigurationType"> |
|
3 |
<booleanAttribute key="org.eclipse.debug.ui.ATTR_LAUNCH_IN_BACKGROUND" value="false"/> |
|
4 |
<booleanAttribute key="org.eclipse.ant.ui.DEFAULT_VM_INSTALL" value="false"/> |
|
5 |
<booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH" value="true"/> |
|
6 |
<stringAttribute key="org.eclipse.ui.externaltools.ATTR_RUN_BUILD_KINDS" value="full,incremental,auto,"/> |
|
7 |
<booleanAttribute key="org.eclipse.ant.ui.ATTR_TARGETS_UPDATED" value="true"/> |
|
8 |
<stringAttribute key="org.eclipse.ui.externaltools.ATTR_LOCATION" value="${workspace_loc:/_fwAndami/build.xml}"/> |
|
9 |
<booleanAttribute key="org.eclipse.ui.externaltools.ATTR_TRIGGERS_CONFIGURED" value="true"/> |
|
10 |
<booleanAttribute key="org.eclipse.debug.core.appendEnvironmentVariables" value="true"/> |
|
11 |
<stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER" value="org.eclipse.ant.ui.AntClasspathProvider"/> |
|
12 |
</launchConfiguration> |
|
0 | 13 |
tags/tmp_build/frameworks/_fwAndami/docs/Servicios para los plugins.txt | ||
---|---|---|
1 |
1 Ejecuci?n en segundo plano. |
|
2 |
|
|
3 |
Es conveniente que la interfaz est? siempre en funcionamiento, |
|
4 |
nunca bloqueada, aunque sea s?lo para mostrar al usuario que el |
|
5 |
programa est? procesando. Para ello hay que realizar las tareas |
|
6 |
que puedan tomar demasiado tiempo en un thread a parte. La |
|
7 |
clase PluginServices proporciona un m?todo est?tico |
|
8 |
backgroundExecution al cual se le pasa un objeto Runnable, que |
|
9 |
es ejecutado en segundo plano, dejando el thread de la interfaz |
|
10 |
libre para responder pero con sus eventos bloqueados con el fin |
|
11 |
de que la interfaz responda y se redibuje, pero se ignoren los |
|
12 |
eventos que produce el usuario mientras se procesa la petici?n |
|
0 | 13 |
tags/tmp_build/frameworks/_fwAndami/docs/funcionamiento class loader.txt | ||
---|---|---|
1 |
En Andami, el class loader de cada plugin delega primero en el classloader del sistemaes decir, que si se ejecuta desde eclipse buscar? por todos los jars que haya en el classpath del proyecto, y si se ejecuta desde la linea de comandos, buscar? en la variable de entorno CLASSPATH o en el argumento -classpath que se pase como par?metro a java. |
|
2 |
|
|
3 |
Si el class loader del sistema no satisface la b?squeda, se buscar? en los jars especificados por el config.xml del plugin que intenta cargar la clase y si no se encuentra en dichos jars, se buscar? en los jars de los plugins de los cuales depende el plugin que intenta cargar la clase. |
|
4 |
|
|
5 |
Por otra parte, FMap tiene un directorio de drivers en los que vas dejando los jars y autom?ticamente los procesa FMap. Sin embargo, FMap no conoce que es usado por Andami, y de hecho, FMap puede ser usado desde otros entornos, por lo que no usa directamente el class loader del plugin que tiene la librer?a fmap.jar en el config.xml. Usa su propio class loader, que est? definido en el proyecto driver-manager. Este class loader busca en los jars que hay en el mismo directorio del driver y de no encontrarla ?stos, delega en el classloader padre. El class loader padre, en el caso de gvSIG con Andami es el class loader del plugin que accede al driver. |
|
0 | 6 |
tags/tmp_build/frameworks/_fwAndami/docs/Andami developer guide.html | ||
---|---|---|
1 |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
|
2 |
<html> |
|
3 |
<head> |
|
4 |
<meta content="text/html; charset=ISO-8859-1" |
|
5 |
http-equiv="content-type"> |
|
6 |
<title>Andami developer guide</title> |
|
7 |
<link href="style.css" rel="stylesheet" type="text/css"> |
|
8 |
</head> |
|
9 |
<body> |
|
10 |
<table width="90%" border="0"> |
|
11 |
<tr> |
|
12 |
<td class="Nivel2"><a href="#Introduccion"><strong><font color="#FFFFFF">Introducción</font></strong></a></td> |
|
13 |
</tr> |
|
14 |
<tr> |
|
15 |
<td class="Nivel2"><a href="#Creacion_de_plugins"><font color="#FFFFFF"><strong>Creación |
|
16 |
de plugins</strong></font></a></td> |
|
17 |
</tr> |
|
18 |
<tr> |
|
19 |
<td class="Nivel2"><a href="#Funcionamiento_del_class_loader"><strong><font color="#FFFFFF">Funcionamiento |
|
20 |
del class loader</font></strong></a></td> |
|
21 |
</tr> |
|
22 |
<tr> |
|
23 |
<td class="Nivel2"><a href="#Servicios_a_los_plugins"><font color="#FFFFFF"><strong>Servicios |
|
24 |
a los plugins</strong></font></a></td> |
|
25 |
</tr> |
|
26 |
<tr> |
|
27 |
<td><strong> <a |
|
28 |
href="#Ejecucion_en_segundo_plano">Ejecución en segundo plano</a></strong></td> |
|
29 |
</tr> |
|
30 |
<tr> |
|
31 |
<td><strong> <a href="#Acceso_a_las_extensiones">Acceso |
|
32 |
a las extensiones</a></strong></td> |
|
33 |
</tr> |
|
34 |
<tr> |
|
35 |
<td class="urbanismo"><strong> <a href="#Persistencia_de_los_plugins">Persistencia |
|
36 |
de los plugins</a></strong></td> |
|
37 |
</tr> |
|
38 |
<tr> |
|
39 |
<td><strong> <a href="#popupmenus">Pop-up menus</a></strong></td> |
|
40 |
</tr> |
|
41 |
<tr> |
|
42 |
<td><strong> <a href="#Vistas">Vistas</a></strong></td> |
|
43 |
</tr> |
|
44 |
<tr> |
|
45 |
<td> <a href="#SingletonView">SingletonView's</a></td> |
|
46 |
</tr> |
|
47 |
</table> |
|
48 |
|
|
49 |
|
|
50 |
|
|
51 |
<p> <strong><font size="+1"><a name="Introduccion"></a>Introducción</font></strong></p> |
|
52 |
<p> Andami es un framework orientado a plugins construido sobre |
|
53 |
swing que permite la construcción de forma rápida y extensible |
|
54 |
de aplicaciones MDI (Multiple Document Interface). Tiene ya implementadas muchas |
|
55 |
de las funcionalidades requeridas para este tipo de aplicaciones tales como |
|
56 |
un menú Ventana, en la que van apareciendo las ventanas que se abren, |
|
57 |
soporte para el traducciones, configuración personalizada para cada usuario, |
|
58 |
actualizaciones automáticas, tanto del propio Andami como de los plugins, |
|
59 |
persistencia del tamaño y posición de la ventana, del idioma, |
|
60 |
distintos tipos de vista, con la finalidad de facilitar la programación |
|
61 |
de ventanas especiales, ... Todo esto además de tener ya solventados |
|
62 |
los problemas típicos de la programación de un entorno como éste |
|
63 |
que no son pocos.<br> |
|
64 |
<br> |
|
65 |
Además, Andami está diseñada de forma |
|
66 |
que la propia lógica MDI puede ser reemplazada. Si en lugar de una aplicación |
|
67 |
estilo arcView, se quiere que cada vista que se añada, se haga en una |
|
68 |
ventana de windows nueva (de las que aparecen en la barra de estado) o una vista |
|
69 |
como la de Eclipse, no hay más que desarrollar el plugin adecuado.<br> |
|
70 |
<br> |
|
71 |
Andami está diseñada para ser amistosa con |
|
72 |
el usuario y para ello incorpora la posibilidad de añadir tooltips y |
|
73 |
enabletexts a los botones. El tooltip es el texto que aparece cuando el ratón |
|
74 |
se detiene sobre un botón o menú. El enableText es el texto que |
|
75 |
aparece en el caso anterior cuando el botón está desactivado, |
|
76 |
permitiendo mostrar al usuario qué es lo que debe hacer para que dicho |
|
77 |
botón se active (o cualquier otro mensaje).<br> |
|
78 |
<br> |
|
79 |
Por último, Andami tiene una gestión de errores |
|
80 |
que agradará a cualquier programador, ya que en casos de errores graves, |
|
81 |
el propio framework avisa de dicho fallo y aconseja al usuario salvar los cambios |
|
82 |
y reiniciar el programa, a parte de que toda excepción no capturada por |
|
83 |
el usuario se redirige a un fichero de log configurable en el que se escribirá |
|
84 |
su traza.<br> |
|
85 |
</p> |
|
86 |
<p> <strong><font size="+1"><a name="Creacion_de_plugins"></a>Creación |
|
87 |
de plugins</font></strong></p> |
|
88 |
<p> Andami gira en torno al concepto de plugin. Andami mantiene |
|
89 |
un directorio como directorio de los plugins, que se puede cambiar en cualquier |
|
90 |
momento. Un plugin viene definido por la existencia de un subdirectorio dentro |
|
91 |
del directorio de los plugins, siendo el nombre del plugin el nombre de dicho |
|
92 |
directorio. Dentro de dicho directorio debe haber un fichero config.xml en el |
|
93 |
que se configuran los puntos de entrada y salida del plugin (menúes, |
|
94 |
barras de herramientas, etiquetas de la barra de estado, menúes contextuales), |
|
95 |
las librerías que va a usar, el paquete de traducciones, los plugins |
|
96 |
de los que depende, etc. El fichero plugin-config.xsd contiene el esquema que |
|
97 |
ha de seguir este fichero y están comentados todos los elementos. En |
|
98 |
el CorePlugin que viene con Adami se puede ver un ejemplo de config.xml.<br> |
|
99 |
<br> |
|
100 |
Las rutas de los directorios son siempre relativas al directorio |
|
101 |
del plugin y los textos de los menúes, tooltips y enabletext's son claves |
|
102 |
en el fichero de traducciones en caso de que haya y textos literales en caso |
|
103 |
de que no haya traducciones. El fichero de traducciones es un fichero de propiedades |
|
104 |
común: ver ResourceBundle en la API de Java.<br> |
|
105 |
<br> |
|
106 |
Dentro de los plugins aparece el concepto de extensión. |
|
107 |
Una extensión es instalada por los plugins mediante la implementación |
|
108 |
de la interfaz com.iver.andami.plugins.Extension y la instalación de |
|
109 |
unos controles geobernados por ésta en el fichero config.xml. Mediante |
|
110 |
esta implementación se le dice a Andami la condición que se debe |
|
111 |
cumplir para que los controles sean visibles o estén activos. Además |
|
112 |
se implementa la acción a llevar a cabo cuando se selecciona uno de los |
|
113 |
menúes o botones asociados a la extensión. Cabe resaltar que Andami |
|
114 |
crea una instancia de cada extensión configurada en config.xml, por lo |
|
115 |
que las clases que implementen la interfaz Extension deben de tener un constructor |
|
116 |
sin argumentos.<br> |
|
117 |
<br> |
|
118 |
En los tag 'extension' existe un atributo class-name en el |
|
119 |
que se especifica la clase que gobierna el punto de extensión que se |
|
120 |
está definiendo. Esta clase deberá implementar la interfaz com.iver.andami.plugins.Extension |
|
121 |
y será mediante ésta que gobernará los menúes y |
|
122 |
botones asociados a este punto de extensión<br> |
|
123 |
<br> |
|
124 |
Una problema común en este framework es no ver cómo |
|
125 |
se mantiene la información del proyecto concreto que se está desarrollando. |
|
126 |
El lugar adecuado es una de las extensiones instaladas. Por ejemplo en el caso |
|
127 |
de gvSIG está la extensión com.iver.cit.gvsig.ProjectExtension, |
|
128 |
en la cual hay un atributo Project que es la raíz del árbol jerárquico |
|
129 |
del cual penden las vistas, mapas, tablas, ... Además esta extensión |
|
130 |
tiene un método getProject que devuelve la referencia al proyecto, de |
|
131 |
manera que se puede acceder desde cualquier punto de la aplicación. Para |
|
132 |
ver el acceso a las instancias de las extensiones ver <a href="#Acceso_a_las_extensiones">acceso |
|
133 |
a las extensiones</a></p> |
|
134 |
<p><br> |
|
135 |
<font size="+1"><strong><a name="Funcionamiento_del_class_loader"></a>Funcionamiento |
|
136 |
del class loader</strong></font></p> |
|
137 |
<p> En Andami, el class loader de cada plugin delega primero en el classloader |
|
138 |
del sistemaes decir, que si se ejecuta desde eclipse buscará por todos |
|
139 |
los jars que haya en el classpath del proyecto, y si se ejecuta desde la linea |
|
140 |
de comandos, buscará en la variable de entorno CLASSPATH o en el argumento |
|
141 |
-classpath que se pase como parámetro a java.<br> |
|
142 |
<br> |
|
143 |
Si el class loader del sistema no satisface la búsqueda, se buscará |
|
144 |
en los jars del directorio especificado por el config.xml del plugin que intenta |
|
145 |
cargar la clase y si no se encuentra en dichos jars, se buscará en los |
|
146 |
jars de los plugins de los cuales depende el plugin que intenta cargar la clase.<br> |
|
147 |
<br> |
|
148 |
<strong><font size="+1"><a name="Servicios_a_los_plugins"></a>Servicios |
|
149 |
a los plugins</font></strong></p> |
|
150 |
<p><br> |
|
151 |
Andami ofrece a los plugins distintos servicios |
|
152 |
a través de la clase PluginServices en cuyo javadoc se puede obtener |
|
153 |
información sobre como usarlos. Existen unos servicios genéricos |
|
154 |
que vienen dados por métodos estáticos de dicha clase y luego |
|
155 |
está el método getPluginServices que obtiene una instancia de |
|
156 |
esta clase específica del plugin, mediante la cual puede acceder a servicios |
|
157 |
concretos de cada plugin, traducciones, persistencia, directorio del plugin, |
|
158 |
...<br> |
|
159 |
<br> |
|
160 |
<strong><a name="Ejecucion_en_segundo_plano"></a>Ejecución en segundo |
|
161 |
plano</strong><br> |
|
162 |
Es conveniente que la interfaz gráfica esté |
|
163 |
siempre en funcionamiento, nunca bloqueada, aunque sea sólo para mostrar |
|
164 |
al usuario que el programa está procesando. Para ello hay que realizar |
|
165 |
las tareas que puedan tomar demasiado tiempo en un thread a parte. La clase |
|
166 |
PluginServices proporciona un método estático backgroundExecution |
|
167 |
al cual se le pasa un objeto Runnable, que es ejecutado en segundo plano, dejando |
|
168 |
el thread de la interfaz libre para responder pero con sus eventos bloqueados |
|
169 |
con el fin de que la interfaz responda y se redibuje, pero se ignoren los eventos |
|
170 |
que produce el usuario mientras se procesa la petición<br> |
|
171 |
<br> |
|
172 |
<a name="Acceso_a_las_extensiones"></a><strong>Acceso a las extensiones</strong><br> |
|
173 |
Para acceder a la instancia de una extensión |
|
174 |
se puede usar simplemente el método de PluginServices getExtension(Class) |
|
175 |
a la cual habrá que pasar como parámetro la clase de la extensión |
|
176 |
a la que se quiere acceder. Dicho método retorna un objeto Extensión |
|
177 |
y por tanto habrá que hacer casting a la clase concreta de dicha extensión, |
|
178 |
habiendo obtenido así la referencia a la instancia de la extensión |
|
179 |
deseada.<br> |
|
180 |
A la hora de desarrollar habrá que tener en el build |
|
181 |
path del entorno de desarrollo que se use, el jar del plugin dentro del cual |
|
182 |
está la extensión que se quiere obtener, para poder pasarle como |
|
183 |
parámetro a getExtension(Class) la clase de la misma.<br> |
|
184 |
<br> |
|
185 |
<strong><a name="Persistencia_de_los_plugins"></a>Persistencia de |
|
186 |
los plugins</strong><br> |
|
187 |
Uno de los servicios que ofrece Andami a los |
|
188 |
plugins es la facilidad de guardar datos genéricos de los mismos en el |
|
189 |
directorio del usuario de manera que cada usuario mantiene su propia configuración |
|
190 |
de los plugins. Para ello, las instancias de PluginServices contienen una propiedad |
|
191 |
persistentXML que puede ser obtenida y asignada y que es de tipo XMLEntity, |
|
192 |
pudiendo añadir información de tipo básico (String, int, |
|
193 |
long, ...) a dicha instancia y siendo esta información persistente entre |
|
194 |
ejecuciones.<br> |
|
195 |
<br> |
|
196 |
<strong><a name="popupmenus"></a>Pop-up menus</strong><br> |
|
197 |
Otro servicio proporcionado por Andami es el de pop-up |
|
198 |
menu's extensibles. Mediante el XML se puede definir un pop-up menu con un nombre |
|
199 |
y unas entradas al igual que cualquier otro menú, con la única |
|
200 |
diferencia que para mostrar el popup menú habrá que registrar |
|
201 |
un listener de la siguiente manera:<br> |
|
202 |
</p> |
|
203 |
<div style="text-align: center;"> |
|
204 |
<pre><>public void addPopupMenuListener(String name, Component c, ActionListener listener)</><br></pre> |
|
205 |
</div> |
|
206 |
Lo cual hará que al pinchar con el |
|
207 |
botón derecho sobre el componente 'c' aparezca el menú |
|
208 |
'name' del fichero de configuración del plugin y al seleccionar |
|
209 |
cualquier entrada se ejecutará el ActionListener que se pasa |
|
210 |
como parámetro.<br> |
|
211 |
<br> |
|
212 |
Estos menúes son extensibles porque cualquier |
|
213 |
otro plugin puede añadir entradas a dicho menú en su |
|
214 |
propio fichero config.xml referenciando el menú al que quiere |
|
215 |
extender mediante el nombre del plugin más el nombre del |
|
216 |
menú. Un ejemplo. Tenemos un plugin llamado com.iver.cit.gvsig |
|
217 |
que instala un menú de la siguiente manera:<br> |
|
218 |
<pre> <popupMenu name="cascada"><br> <entry text="Cascada" <br> tooltip="cascada_tooltip" <br> enableText="cascada_enable" actionCommand="CASCADA"/><br> <entry text="Tile" <br> tooltip="tile_tooltip" <br> enableText="cascada_enable" actionCommand="CASCADA"/><br> </popupMenu><br></pre> |
|
219 |
y tenemos otro plugin que quiere añadir una entrada a dicho |
|
220 |
menú. Para ello deberá de incluir un fragmento similar a |
|
221 |
este en su fichero config.xml:<br> |
|
222 |
<pre> <popupMenu name="com.iver.cit.gvsig.cascada"><br> <entry text="Nueva entrada" actionCommand="NUEVA"/><br> </popupMenu><br></pre> |
|
223 |
y además deberá de registrarse como listener de la manera |
|
224 |
que se explicó anteriormente.<br> |
|
225 |
<br> |
|
226 |
<strong><a name="Vistas"></a>Vistas</strong><br> |
|
227 |
El servicio más importante que |
|
228 |
proporciona Andami es el de añadir vistas al marco principal. |
|
229 |
Podemos calsificar las vistas por varios criterios:<br> |
|
230 |
<ul> |
|
231 |
<li>Por su modalidad</li> |
|
232 |
<ul> |
|
233 |
<li>Modales</li> |
|
234 |
<li>No modales</li> |
|
235 |
</ul> |
|
236 |
</ul> |
|
237 |
<ul> |
|
238 |
<li>Por su contenido</li> |
|
239 |
<ul> |
|
240 |
<li>Singleton (Contenido identificable)</li> |
|
241 |
<li>Normales (Contenido no identificable)</li> |
|
242 |
</ul> |
|
243 |
</ul> |
|
244 |
Para crear una vista hay que hacer una clase que |
|
245 |
derive de JPanel en la que se pone toda la funcionalidad como si de un |
|
246 |
diálogo normal se tratara. Además esta clase ha de |
|
247 |
implementar la interfaz View la cual proporciona un método |
|
248 |
getViewInfo que es invocado una vez en la vida de la vista. Este objeto |
|
249 |
contiene las características que tendrá la vista: |
|
250 |
maximizable, resizable, title, ... y puede ser actualizado en cualquier |
|
251 |
momento, reflejándose estos cambios de manera automática |
|
252 |
en la interfaz de usuario. Una vez implementada la vista, hay que |
|
253 |
añadirla al manger MDI, que es el encargado de manejar toda la |
|
254 |
lógica relacionada con las vistas. Para obtener una referencia |
|
255 |
al manager MDI la clase PluginServices tiene un método |
|
256 |
getMDIManager, el cual a su vez tiene un método addView mediante |
|
257 |
el cual se puede añadir la vista.<br> |
|
258 |
<br> |
|
259 |
Si durante la ejecución se quiere cambiar |
|
260 |
alguna propiedad de la vista tal como el tamaño, la |
|
261 |
posición o el |
|
262 |
título, sólo hay que acceder al objeto ViewInfo de la |
|
263 |
misma y realizar los cambios de la manera deseada. El siguiente trozo |
|
264 |
de código cambia el título de una ventana (se supone que |
|
265 |
es ejecutado desde la clase que implementa View).<br> |
|
266 |
<pre> PluginServices.getMDIManager().getViewInfo(this).setTitle("Nuevo título");<br></pre> |
|
267 |
Puede ser necesario que algunas vistas realicen |
|
268 |
algún tipo de procesamiento al ser activadas pero esto no se |
|
269 |
sabe cuando ocurre ya que lo que se entrega al manager MDI es un |
|
270 |
JPanel. Para recibir los eventos sobre las vistas, además de |
|
271 |
implementar View hay que implementar ViewListener la cual |
|
272 |
proporcionará los métodos que serán invocados |
|
273 |
cuando sucedan los eventos oportunos en las vistas.<br> |
|
274 |
<br> |
|
275 |
<big><a name="SingletonView"></a>SingletonView<br> |
|
276 |
</big> Un tipo especial de vistas son las |
|
277 |
SingletonView. Su principal característica es que se les define |
|
278 |
el contenido de las mismas, de manera que cuando hay una SingletonView |
|
279 |
minimizada en el proyecto y se intenta añadir un JPanel con el |
|
280 |
mismo contenido, en lugar de aparecer otra ventana en el escritorio, lo |
|
281 |
que sucede es que la ventana que estaba minimizada se restaura a su |
|
282 |
posición anterior. Para esto, el método addView devuelve |
|
283 |
una referencia a la vista que se muestra, sea esta la que se |
|
284 |
está añadiendo o la que ya está añadida. |
|
285 |
Además, al cerrar dicha ventana se guardan las dimensiones y la |
|
286 |
posición de las mismas, de manera que al volverla a abrir se |
|
287 |
recuerdan estos datos.<br> |
|
288 |
</body> |
|
289 |
</html> |
|
0 | 290 |
tags/tmp_build/frameworks/_fwAndami/gvsig.sh | ||
---|---|---|
1 |
#!/bin/sh |
|
2 |
[ -x /usr/bin/dirname ] && cd `dirname $0` |
|
3 |
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH":../../libs/ |
|
4 |
java -Djava.library.path=/usr/lib:/home/cesar/libs -cp andami.jar:lib/beans.jar:./lib/castor-0.9.5.3-xml.jar:lib/commons-dbcp-1.0-dev-20020806.zip:lib/commons-codec-1.3.jar:lib/commons-collections-3.1.zip:lib/commons-pool-1.2.zip:/lib/crimson.jar:lib/gvsig-i18n.jar:./lib/javaws.jar:lib/JWizardComponent.jar:./lib/iver-utiles.jar:./lib/log4j-1.2.8.jar:lib/looks-2.0.2.jar:lib/tempFileManager.jar:./lib/xerces_2_5_0.jar:./lib/xml-apis.jar:./lib/kxml2.jar -Xmx500M com.iver.andami.Launcher gvSIG gvSIG/extensiones "$@" |
|
0 | 5 |
tags/tmp_build/frameworks/_fwAndami/build.xml | ||
---|---|---|
1 |
<project name="_fwAndami" default="create-jar" basedir="."> |
|
2 |
<!-- set global properties for this build --> |
|
3 |
<property name="src" location="src" /> |
|
4 |
<property name="build" location="bin" /> |
|
5 |
<property name="dist" location="dist" /> |
|
6 |
<property name="lib" location="lib" /> |
|
7 |
<property name="appDir" location="gvSIG" /> |
|
8 |
<property name="extensiones" location="${appDir}/extensiones" /> |
|
9 |
<property name="build-doc" value="build-doc"/> |
|
10 |
<property name="jarName" value="andami.jar"/> |
|
11 |
<property name="debug" value="off" /> |
|
12 |
<import file="compile-classpath.xml"/> |
|
13 |
<property name="webapps" location="c:\webservers\jakarta-tomcat-5.0.25\webapps\" /> |
|
14 |
<property name="webdir" location="web" /> |
|
15 |
<property name="keystore" location="keystore" /> |
|
16 |
<property name="schemas" location="schemas" /> |
|
17 |
<property name="JavaSourceVersion" value="1.4"/> |
|
18 |
<property name="JavaTargetVersion" value="1.4"/> |
|
19 |
|
|
20 |
<target name="init"> |
|
21 |
<!-- Create the time stamp --> |
|
22 |
<tstamp /> |
|
23 |
<echo> |
|
24 |
Compiling ${ant.project.name}... |
|
25 |
</echo> |
|
26 |
</target> |
|
27 |
|
|
28 |
<target name="batch-build" |
|
29 |
description="compile the sources, create the jar file for Andami framework" |
|
30 |
depends="init,compile,create-jar"> |
|
31 |
</target> |
|
32 |
|
|
33 |
<target name="compile" description="compile the source" > |
|
34 |
<!-- Compile the Java code from ${src} to ${build} --> |
|
35 |
<mkdir dir="${build}" /> |
|
36 |
<javac srcdir="${src}" |
|
37 |
destdir="${build}" |
|
38 |
source="${JavaSourceVersion}" |
|
39 |
target="${JavaTargetVersion}" |
|
40 |
debug="${debug}" |
|
41 |
encoding="${encoding}" |
|
42 |
debuglevel="${debuglevel}"> |
|
43 |
<classpath refid="_fwAndami.compile-classpath"/> |
|
44 |
</javac> |
|
45 |
<copy todir="${build}"> |
|
46 |
<fileset |
|
47 |
dir="${src}" |
|
48 |
excludes="**/*.java"/> |
|
49 |
</copy> |
|
50 |
</target> |
|
51 |
|
|
52 |
<!--Crea un jar con el codigo de andami--> |
|
53 |
<target name="create-jar" description="Crea el jar de la aplicacion"> |
|
54 |
<copy todir="${build}/com/iver/andami/"> |
|
55 |
<fileset dir="config" includes="*.properties" /> |
|
56 |
</copy> |
|
57 |
<mkdir dir="${appDir}" /> |
|
58 |
<jar destfile="${jarName}" basedir="${build}" /> |
|
59 |
</target> |
|
60 |
|
|
61 |
<target name="clean" description="delete binaries and jar files" > |
|
62 |
<!-- Delete the ${build} and ${dist} directory trees --> |
|
63 |
<delete dir="${build}"/> |
|
64 |
<delete dir="${dist}"/> |
|
65 |
<delete file="${jarName}"/> |
|
66 |
<delete dir="${appDir}"/> |
|
67 |
</target> |
|
68 |
|
|
69 |
<target name="build-doc" depends="" description="Genera un zip con la documentación"> |
|
70 |
<javadoc |
|
71 |
packagenames="com.iver.andami.*" |
|
72 |
sourcepath="src" |
|
73 |
defaultexcludes="yes" |
|
74 |
destdir="${build-doc}/andami-api" |
|
75 |
windowtitle="andami API"> |
|
76 |
</javadoc> |
|
77 |
</target> |
|
78 |
|
|
79 |
|
|
80 |
<!-- Genera las clases a partir de los esquemas --> |
|
81 |
<target name="generate-andami-config-classes"> |
|
82 |
|
|
83 |
<delete> |
|
84 |
<fileset dir="${src}" includes="com/iver/andami/config/generate/**" /> |
|
85 |
</delete> |
|
86 |
<java classname="org.exolab.castor.builder.SourceGenerator"> |
|
87 |
<classpath> |
|
88 |
<pathelement path="lib/castor-0.9.5.3-xml.jar" /> |
|
89 |
<pathelement path="lib/xerces_2_5_0.jar" /> |
|
90 |
</classpath> |
|
91 |
<arg value="-i" /> |
|
92 |
<arg value="${schemas}/andami-config.xsd" /> |
|
93 |
<arg value="-package" /> |
|
94 |
<arg value="com.iver.andami.config.generate" /> |
|
95 |
<arg value="-dest" /> |
|
96 |
<arg value="${src}" /> |
|
97 |
</java> |
|
98 |
</target> |
|
99 |
|
|
100 |
<!-- Genera las clases a partir de los esquemas --> |
|
101 |
<target name="generate-plugin-config"> |
|
102 |
<delete> |
|
103 |
<fileset dir="${src}" includes="com/iver/andami/plugins/config/generate/**" /> |
|
104 |
</delete> |
|
105 |
<java classname="org.exolab.castor.builder.SourceGenerator"> |
|
106 |
<classpath> |
|
107 |
<pathelement path="lib/castor-0.9.5.3-xml.jar" /> |
|
108 |
<pathelement path="lib/xerces_2_5_0.jar" /> |
|
109 |
</classpath> |
|
110 |
<arg value="-i" /> |
|
111 |
<arg value="${schemas}/plugin-config.xsd" /> |
|
112 |
<arg value="-package" /> |
|
113 |
<arg value="com.iver.andami.plugins.config.generate" /> |
|
114 |
<arg value="-dest" /> |
|
115 |
<arg value="${src}" /> |
|
116 |
</java> |
|
117 |
</target> |
|
118 |
|
|
119 |
<!-- Genera las clases a partir de los esquemas --> |
|
120 |
<target name="generate-plugin-persistence"> |
|
121 |
<delete> |
|
122 |
<fileset dir="${src}" includes="com/iver/andami/persistence/generate/**" /> |
|
123 |
</delete> |
|
124 |
<java classname="org.exolab.castor.builder.SourceGenerator"> |
|
125 |
<classpath> |
|
126 |
<pathelement path="lib/castor-0.9.5.3-xml.jar" /> |
|
127 |
<pathelement path="lib/xerces_2_5_0.jar" /> |
|
128 |
</classpath> |
|
129 |
<arg value="-i" /> |
|
130 |
<arg value="${schemas}/plugin-persistence.xsd" /> |
|
131 |
<arg value="-package" /> |
|
132 |
<arg value="com.iver.andami.persistence.generate" /> |
|
133 |
<arg value="-dest" /> |
|
134 |
<arg value="${src}" /> |
|
135 |
</java> |
|
136 |
|
|
137 |
</target> |
|
138 |
|
|
139 |
<!--Copia los jar que hay en el subdirectorio lib al directorio web--> |
|
140 |
<target name="move-jars" description="Pone todos los jar en el directorio web" depends="create-jar"> |
|
141 |
<copy todir="${webdir}"> |
|
142 |
<fileset dir="lib" includes="**/*" /> |
|
143 |
</copy> |
|
144 |
</target> |
|
145 |
|
|
146 |
<!--Comprime las extensiones en un zip y las mete en el directorio web--> |
|
147 |
<target name="extensiones" description="Copia el directorio de extensiones"> |
|
148 |
<zip zipfile="${webdir}/extensiones.zip"> |
|
149 |
<fileset dir="${extensiones}" includes="**/*" excludes="CVS" excludesfile=".cvsignore" /> |
|
150 |
</zip> |
|
151 |
</target> |
|
152 |
|
|
153 |
</project> |
|
0 | 154 |
tags/tmp_build/frameworks/_fwAndami/.classpath | ||
---|---|---|
1 |
<?xml version="1.0" encoding="UTF-8"?> |
|
2 |
<classpath> |
|
3 |
<classpathentry kind="src" path="src"/> |
|
4 |
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> |
|
5 |
<classpathentry kind="lib" path="lib/castor-0.9.5.3-xml.jar"/> |
|
6 |
<classpathentry kind="lib" path="lib/log4j-1.2.8.jar"/> |
|
7 |
<classpathentry kind="lib" path="lib/javaws.jar"/> |
|
8 |
<classpathentry kind="lib" path="lib/iver-utiles.jar" sourcepath="/libIverUtiles/src"/> |
|
9 |
<classpathentry kind="lib" path="lib/tempFileManager.jar"/> |
|
10 |
<classpathentry kind="lib" path="lib/xml-apis.jar"/> |
|
11 |
<classpathentry kind="lib" path="lib/crimson.jar"/> |
|
12 |
<classpathentry kind="lib" path="lib/xerces_2_5_0.jar"/> |
|
13 |
<classpathentry kind="lib" path="lib/commons-dbcp-1.0-dev-20020806.zip"/> |
|
14 |
<classpathentry kind="lib" path="lib/commons-pool-1.2.zip"/> |
|
15 |
<classpathentry kind="lib" path="lib/commons-collections-3.1.zip"/> |
|
16 |
<classpathentry kind="lib" path="lib/commons-codec-1.3.jar"/> |
|
17 |
<classpathentry kind="lib" path="lib/xmlrpc-2.0.1.jar"/> |
|
18 |
<classpathentry kind="lib" path="lib/beans.jar" sourcepath="/libUI/src"/> |
|
19 |
<classpathentry kind="lib" path="lib/gvsig-i18n.jar" sourcepath="/libInternationalization/src"/> |
|
20 |
<classpathentry kind="lib" path="lib/looks-2.0.2.jar"/> |
|
21 |
<classpathentry exported="true" kind="lib" path="lib/JWizardComponent.jar"/> |
|
22 |
<classpathentry kind="lib" path="lib/jcalendar.jar"/> |
|
23 |
<classpathentry kind="lib" path="lib/kxml2.jar"/> |
|
24 |
<classpathentry kind="lib" path="lib/jh.jar"/> |
|
25 |
<classpathentry kind="output" path="bin"/> |
|
26 |
</classpath> |
|
0 | 27 |
tags/tmp_build/frameworks/_fwAndami/gpl.txt | ||
---|---|---|
1 |
GNU GENERAL PUBLIC LICENSE |
|
2 |
Version 2, June 1991 |
|
3 |
|
|
4 |
Copyright (C) 1989, 1991 Free Software Foundation, Inc. |
|
5 |
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA |
|
6 |
Everyone is permitted to copy and distribute verbatim copies |
|
7 |
of this license document, but changing it is not allowed. |
|
8 |
|
|
9 |
Preamble |
|
10 |
|
|
11 |
The licenses for most software are designed to take away your |
|
12 |
freedom to share and change it. By contrast, the GNU General Public |
|
13 |
License is intended to guarantee your freedom to share and change free |
|
14 |
software--to make sure the software is free for all its users. This |
|
15 |
General Public License applies to most of the Free Software |
|
16 |
Foundation's software and to any other program whose authors commit to |
|
17 |
using it. (Some other Free Software Foundation software is covered by |
|
18 |
the GNU Library General Public License instead.) You can apply it to |
|
19 |
your programs, too. |
|
20 |
|
|
21 |
When we speak of free software, we are referring to freedom, not |
|
22 |
price. Our General Public Licenses are designed to make sure that you |
|
23 |
have the freedom to distribute copies of free software (and charge for |
|
24 |
this service if you wish), that you receive source code or can get it |
|
25 |
if you want it, that you can change the software or use pieces of it |
|
26 |
in new free programs; and that you know you can do these things. |
|
27 |
|
|
28 |
To protect your rights, we need to make restrictions that forbid |
|
29 |
anyone to deny you these rights or to ask you to surrender the rights. |
|
30 |
These restrictions translate to certain responsibilities for you if you |
|
31 |
distribute copies of the software, or if you modify it. |
|
32 |
|
|
33 |
For example, if you distribute copies of such a program, whether |
|
34 |
gratis or for a fee, you must give the recipients all the rights that |
|
35 |
you have. You must make sure that they, too, receive or can get the |
|
36 |
source code. And you must show them these terms so they know their |
|
37 |
rights. |
|
38 |
|
|
39 |
We protect your rights with two steps: (1) copyright the software, and |
|
40 |
(2) offer you this license which gives you legal permission to copy, |
|
41 |
distribute and/or modify the software. |
|
42 |
|
|
43 |
Also, for each author's protection and ours, we want to make certain |
|
44 |
that everyone understands that there is no warranty for this free |
|
45 |
software. If the software is modified by someone else and passed on, we |
|
46 |
want its recipients to know that what they have is not the original, so |
|
47 |
that any problems introduced by others will not reflect on the original |
|
48 |
authors' reputations. |
|
49 |
|
|
50 |
Finally, any free program is threatened constantly by software |
|
51 |
patents. We wish to avoid the danger that redistributors of a free |
|
52 |
program will individually obtain patent licenses, in effect making the |
|
53 |
program proprietary. To prevent this, we have made it clear that any |
|
54 |
patent must be licensed for everyone's free use or not licensed at all. |
|
55 |
|
|
56 |
The precise terms and conditions for copying, distribution and |
|
57 |
modification follow. |
|
58 |
|
|
59 |
GNU GENERAL PUBLIC LICENSE |
|
60 |
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION |
|
61 |
|
|
62 |
0. This License applies to any program or other work which contains |
|
63 |
a notice placed by the copyright holder saying it may be distributed |
|
64 |
under the terms of this General Public License. The "Program", below, |
|
65 |
refers to any such program or work, and a "work based on the Program" |
|
66 |
means either the Program or any derivative work under copyright law: |
|
67 |
that is to say, a work containing the Program or a portion of it, |
|
68 |
either verbatim or with modifications and/or translated into another |
|
69 |
language. (Hereinafter, translation is included without limitation in |
|
70 |
the term "modification".) Each licensee is addressed as "you". |
|
71 |
|
|
72 |
Activities other than copying, distribution and modification are not |
|
73 |
covered by this License; they are outside its scope. The act of |
|
74 |
running the Program is not restricted, and the output from the Program |
|
75 |
is covered only if its contents constitute a work based on the |
|
76 |
Program (independent of having been made by running the Program). |
|
77 |
Whether that is true depends on what the Program does. |
|
78 |
|
|
79 |
1. You may copy and distribute verbatim copies of the Program's |
|
80 |
source code as you receive it, in any medium, provided that you |
|
81 |
conspicuously and appropriately publish on each copy an appropriate |
|
82 |
copyright notice and disclaimer of warranty; keep intact all the |
|
83 |
notices that refer to this License and to the absence of any warranty; |
|
84 |
and give any other recipients of the Program a copy of this License |
|
85 |
along with the Program. |
|
86 |
|
|
87 |
You may charge a fee for the physical act of transferring a copy, and |
|
88 |
you may at your option offer warranty protection in exchange for a fee. |
|
89 |
|
|
90 |
2. You may modify your copy or copies of the Program or any portion |
|
91 |
of it, thus forming a work based on the Program, and copy and |
|
92 |
distribute such modifications or work under the terms of Section 1 |
|
93 |
above, provided that you also meet all of these conditions: |
|
94 |
|
|
95 |
a) You must cause the modified files to carry prominent notices |
|
96 |
stating that you changed the files and the date of any change. |
|
97 |
|
|
98 |
b) You must cause any work that you distribute or publish, that in |
|
99 |
whole or in part contains or is derived from the Program or any |
|
100 |
part thereof, to be licensed as a whole at no charge to all third |
|
101 |
parties under the terms of this License. |
|
102 |
|
|
103 |
c) If the modified program normally reads commands interactively |
|
104 |
when run, you must cause it, when started running for such |
|
105 |
interactive use in the most ordinary way, to print or display an |
|
106 |
announcement including an appropriate copyright notice and a |
|
107 |
notice that there is no warranty (or else, saying that you provide |
|
108 |
a warranty) and that users may redistribute the program under |
|
109 |
these conditions, and telling the user how to view a copy of this |
|
110 |
License. (Exception: if the Program itself is interactive but |
|
111 |
does not normally print such an announcement, your work based on |
|
112 |
the Program is not required to print an announcement.) |
|
113 |
|
|
114 |
These requirements apply to the modified work as a whole. If |
|
115 |
identifiable sections of that work are not derived from the Program, |
|
116 |
and can be reasonably considered independent and separate works in |
|
117 |
themselves, then this License, and its terms, do not apply to those |
|
118 |
sections when you distribute them as separate works. But when you |
|
119 |
distribute the same sections as part of a whole which is a work based |
|
120 |
on the Program, the distribution of the whole must be on the terms of |
|
121 |
this License, whose permissions for other licensees extend to the |
|
122 |
entire whole, and thus to each and every part regardless of who wrote it. |
|
123 |
|
|
124 |
Thus, it is not the intent of this section to claim rights or contest |
|
125 |
your rights to work written entirely by you; rather, the intent is to |
|
126 |
exercise the right to control the distribution of derivative or |
|
127 |
collective works based on the Program. |
|
128 |
|
|
129 |
In addition, mere aggregation of another work not based on the Program |
|
130 |
with the Program (or with a work based on the Program) on a volume of |
|
131 |
a storage or distribution medium does not bring the other work under |
|
132 |
the scope of this License. |
|
133 |
|
|
134 |
3. You may copy and distribute the Program (or a work based on it, |
|
135 |
under Section 2) in object code or executable form under the terms of |
|
136 |
Sections 1 and 2 above provided that you also do one of the following: |
|
137 |
|
|
138 |
a) Accompany it with the complete corresponding machine-readable |
|
139 |
source code, which must be distributed under the terms of Sections |
|
140 |
1 and 2 above on a medium customarily used for software interchange; or, |
|
141 |
|
|
142 |
b) Accompany it with a written offer, valid for at least three |
|
143 |
years, to give any third party, for a charge no more than your |
|
144 |
cost of physically performing source distribution, a complete |
|
145 |
machine-readable copy of the corresponding source code, to be |
|
146 |
distributed under the terms of Sections 1 and 2 above on a medium |
|
147 |
customarily used for software interchange; or, |
|
148 |
|
|
149 |
c) Accompany it with the information you received as to the offer |
|
150 |
to distribute corresponding source code. (This alternative is |
|
151 |
allowed only for noncommercial distribution and only if you |
|
152 |
received the program in object code or executable form with such |
|
153 |
an offer, in accord with Subsection b above.) |
|
154 |
|
|
155 |
The source code for a work means the preferred form of the work for |
|
156 |
making modifications to it. For an executable work, complete source |
|
157 |
code means all the source code for all modules it contains, plus any |
|
158 |
associated interface definition files, plus the scripts used to |
|
159 |
control compilation and installation of the executable. However, as a |
|
160 |
special exception, the source code distributed need not include |
|
161 |
anything that is normally distributed (in either source or binary |
|
162 |
form) with the major components (compiler, kernel, and so on) of the |
|
163 |
operating system on which the executable runs, unless that component |
|
164 |
itself accompanies the executable. |
|
165 |
|
|
166 |
If distribution of executable or object code is made by offering |
|
167 |
access to copy from a designated place, then offering equivalent |
|
168 |
access to copy the source code from the same place counts as |
|
169 |
distribution of the source code, even though third parties are not |
|
170 |
compelled to copy the source along with the object code. |
|
171 |
|
|
172 |
4. You may not copy, modify, sublicense, or distribute the Program |
|
173 |
except as expressly provided under this License. Any attempt |
|
174 |
otherwise to copy, modify, sublicense or distribute the Program is |
|
175 |
void, and will automatically terminate your rights under this License. |
|
176 |
However, parties who have received copies, or rights, from you under |
|
177 |
this License will not have their licenses terminated so long as such |
|
178 |
parties remain in full compliance. |
|
179 |
|
|
180 |
5. You are not required to accept this License, since you have not |
|
181 |
signed it. However, nothing else grants you permission to modify or |
|
182 |
distribute the Program or its derivative works. These actions are |
|
183 |
prohibited by law if you do not accept this License. Therefore, by |
|
184 |
modifying or distributing the Program (or any work based on the |
|
185 |
Program), you indicate your acceptance of this License to do so, and |
|
186 |
all its terms and conditions for copying, distributing or modifying |
|
187 |
the Program or works based on it. |
|
188 |
|
|
189 |
6. Each time you redistribute the Program (or any work based on the |
|
190 |
Program), the recipient automatically receives a license from the |
|
191 |
original licensor to copy, distribute or modify the Program subject to |
|
192 |
these terms and conditions. You may not impose any further |
|
193 |
restrictions on the recipients' exercise of the rights granted herein. |
|
194 |
You are not responsible for enforcing compliance by third parties to |
|
195 |
this License. |
|
196 |
|
|
197 |
7. If, as a consequence of a court judgment or allegation of patent |
|
198 |
infringement or for any other reason (not limited to patent issues), |
|
199 |
conditions are imposed on you (whether by court order, agreement or |
|
200 |
otherwise) that contradict the conditions of this License, they do not |
|
201 |
excuse you from the conditions of this License. If you cannot |
|
202 |
distribute so as to satisfy simultaneously your obligations under this |
|
203 |
License and any other pertinent obligations, then as a consequence you |
|
204 |
may not distribute the Program at all. For example, if a patent |
|
205 |
license would not permit royalty-free redistribution of the Program by |
|
206 |
all those who receive copies directly or indirectly through you, then |
|
207 |
the only way you could satisfy both it and this License would be to |
|
208 |
refrain entirely from distribution of the Program. |
|
209 |
|
|
210 |
If any portion of this section is held invalid or unenforceable under |
|
211 |
any particular circumstance, the balance of the section is intended to |
|
212 |
apply and the section as a whole is intended to apply in other |
|
213 |
circumstances. |
|
214 |
|
|
215 |
It is not the purpose of this section to induce you to infringe any |
|
216 |
patents or other property right claims or to contest validity of any |
|
217 |
such claims; this section has the sole purpose of protecting the |
|
218 |
integrity of the free software distribution system, which is |
|
219 |
implemented by public license practices. Many people have made |
|
220 |
generous contributions to the wide range of software distributed |
|
221 |
through that system in reliance on consistent application of that |
|
222 |
system; it is up to the author/donor to decide if he or she is willing |
|
223 |
to distribute software through any other system and a licensee cannot |
|
224 |
impose that choice. |
|
225 |
|
|
226 |
This section is intended to make thoroughly clear what is believed to |
|
227 |
be a consequence of the rest of this License. |
|
228 |
|
|
229 |
8. If the distribution and/or use of the Program is restricted in |
|
230 |
certain countries either by patents or by copyrighted interfaces, the |
|
231 |
original copyright holder who places the Program under this License |
|
232 |
may add an explicit geographical distribution limitation excluding |
|
233 |
those countries, so that distribution is permitted only in or among |
|
234 |
countries not thus excluded. In such case, this License incorporates |
|
235 |
the limitation as if written in the body of this License. |
|
236 |
|
|
237 |
9. The Free Software Foundation may publish revised and/or new versions |
|
238 |
of the General Public License from time to time. Such new versions will |
|
239 |
be similar in spirit to the present version, but may differ in detail to |
|
240 |
address new problems or concerns. |
|
241 |
|
|
242 |
Each version is given a distinguishing version number. If the Program |
|
243 |
specifies a version number of this License which applies to it and "any |
|
244 |
later version", you have the option of following the terms and conditions |
|
245 |
either of that version or of any later version published by the Free |
|
246 |
Software Foundation. If the Program does not specify a version number of |
|
247 |
this License, you may choose any version ever published by the Free Software |
|
248 |
Foundation. |
|
249 |
|
|
250 |
10. If you wish to incorporate parts of the Program into other free |
|
251 |
programs whose distribution conditions are different, write to the author |
|
252 |
to ask for permission. For software which is copyrighted by the Free |
|
253 |
Software Foundation, write to the Free Software Foundation; we sometimes |
|
254 |
make exceptions for this. Our decision will be guided by the two goals |
|
255 |
of preserving the free status of all derivatives of our free software and |
|
256 |
of promoting the sharing and reuse of software generally. |
|
257 |
|
|
258 |
NO WARRANTY |
|
259 |
|
|
260 |
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY |
|
261 |
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN |
|
262 |
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES |
|
263 |
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED |
|
264 |
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF |
|
265 |
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS |
|
266 |
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE |
|
267 |
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, |
|
268 |
REPAIR OR CORRECTION. |
|
269 |
|
|
270 |
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING |
|
271 |
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR |
|
272 |
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, |
|
273 |
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING |
|
274 |
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED |
|
275 |
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY |
|
276 |
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER |
|
277 |
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE |
|
278 |
POSSIBILITY OF SUCH DAMAGES. |
|
279 |
|
|
280 |
END OF TERMS AND CONDITIONS |
|
281 |
|
|
282 |
How to Apply These Terms to Your New Programs |
|
283 |
|
|
284 |
If you develop a new program, and you want it to be of the greatest |
|
285 |
possible use to the public, the best way to achieve this is to make it |
|
286 |
free software which everyone can redistribute and change under these terms. |
|
287 |
|
|
288 |
To do so, attach the following notices to the program. It is safest |
|
289 |
to attach them to the start of each source file to most effectively |
|
290 |
convey the exclusion of warranty; and each file should have at least |
|
291 |
the "copyright" line and a pointer to where the full notice is found. |
|
292 |
|
|
293 |
<one line to give the program's name and a brief idea of what it does.> |
|
294 |
Copyright (C) <year> <name of author> |
|
295 |
|
|
296 |
This program is free software; you can redistribute it and/or modify |
|
297 |
it under the terms of the GNU General Public License as published by |
|
298 |
the Free Software Foundation; either version 2 of the License, or |
|
299 |
(at your option) any later version. |
|
300 |
|
|
301 |
This program is distributed in the hope that it will be useful, |
|
302 |
but WITHOUT ANY WARRANTY; without even the implied warranty of |
|
303 |
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
|
304 |
GNU General Public License for more details. |
|
305 |
|
|
306 |
You should have received a copy of the GNU General Public License |
|
307 |
along with this program; if not, write to the Free Software |
|
308 |
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA |
|
309 |
|
|
310 |
|
|
311 |
Also add information on how to contact you by electronic and paper mail. |
|
312 |
|
|
313 |
If the program is interactive, make it output a short notice like this |
|
314 |
when it starts in an interactive mode: |
|
315 |
|
|
316 |
Gnomovision version 69, Copyright (C) year name of author |
|
317 |
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. |
|
318 |
This is free software, and you are welcome to redistribute it |
|
319 |
under certain conditions; type `show c' for details. |
|
320 |
|
|
321 |
The hypothetical commands `show w' and `show c' should show the appropriate |
|
322 |
parts of the General Public License. Of course, the commands you use may |
|
323 |
be called something other than `show w' and `show c'; they could even be |
|
324 |
mouse-clicks or menu items--whatever suits your program. |
|
325 |
|
|
326 |
You should also get your employer (if you work as a programmer) or your |
|
327 |
school, if any, to sign a "copyright disclaimer" for the program, if |
|
328 |
necessary. Here is a sample; alter the names: |
|
329 |
|
|
330 |
Yoyodyne, Inc., hereby disclaims all copyright interest in the program |
|
331 |
`Gnomovision' (which makes passes at compilers) written by James Hacker. |
|
332 |
|
|
333 |
<signature of Ty Coon>, 1 April 1989 |
|
334 |
Ty Coon, President of Vice |
|
335 |
|
|
336 |
This General Public License does not permit incorporating your program into |
|
337 |
proprietary programs. If your program is a subroutine library, you may |
|
338 |
consider it more useful to permit linking proprietary applications with the |
|
339 |
library. If this is what you want to do, use the GNU Library General |
|
340 |
Public License instead of this License. |
|
0 | 341 |
tags/tmp_build/frameworks/_fwAndami/theme/andami-theme.xml | ||
---|---|---|
1 |
<AndamiProperties> |
|
2 |
<ApplicationImages> |
|
3 |
<SplashImages> |
|
4 |
<!--Splash path="theme/logoIver.png" timer="1000"/--> |
|
5 |
<Splash path="theme/logo_es.png" timer="10000"/> |
|
6 |
</SplashImages> |
|
7 |
<!--BackgroundImage path="theme/logo_es.png"/--> |
|
8 |
<!--WallpaperType value="CENTERED"/--> |
|
9 |
<Icon path="theme/logoGVA.gif"/> |
|
10 |
</ApplicationImages> |
|
11 |
<ApplicationName value="gvSIG 1.1.2"/> |
|
12 |
</AndamiProperties> |
|
0 | 13 |
tags/tmp_build/frameworks/_fwAndami/theme/logo_es.png | ||
---|---|---|
1 |
?PNG |
|
2 |
|
|
3 |