Changes between Version 2 and Version 3 of ZOO_GSoC_Idea

Timestamp:

Mar 17, 2016, 11:04:52 AM (8 years ago)

Author:

djay

Comment:

--

ZOO_GSoC_Idea

@@ -20 +20 @@
 The first goal of this GSoC project is to '''create WPS Services based on each of the available pyModis scripts'''. Those services should provide the ongoing status of the execution during the execution to make the client able to know the current state of the service and its evolution.
 
-The ZOO-Project provides the ZOO-Client, a JavaScript API, which is already able to automatically generate HTML forms for every available service. Examples of such an automatic HTML forms creation are available in the following demonstration UI: [http://zoo-project.org/examples/saga-example.html 1] and [http://zoo-project.org/examples/otb-example.html 2].
+The ZOO-Project provides the ZOO-Client, a !JavaScript API, which is already able to automatically generate HTML forms for every available service. Examples of such an automatic HTML forms creation are available in the following demonstration UI: [http://zoo-project.org/examples/saga-example.html 1] and [http://zoo-project.org/examples/otb-example.html 2].
 
 The second goal of this GSoC project is to '''create User Interfaces to interact with the pyModis WPS services''' by taking advantages of the existing ZOO-Client and its templating system.
@@ -42 +42 @@
 
 The ZOO-Project is a solid WPS server able to handle services implemented in various different programming languages. The Java bindings have never been tested in advanced configurations and complex data types.
-The JGrasstools project is a modular processing library and its highly annotated nature makes it possible to adapt quite easily to other toolboxes. One example has been the adaptation to the Geotools Process API. The JGrasstools project, as well as other java based projects (as JTS and even GeoTools) would benefit a lot from the possibility to be used within a WPS environment. The proposal is to bring the Java binding to a mature level and validate them by integrating the JGrasstools libraries. This will allow them to work inside the ZOO-Project and serve its modules under the WPS standard.
+The JGrasstools project is a modular processing library and its highly annotated nature makes it possible to adapt quite easily to other toolboxes. One example has been the adaptation to the Geotools Process API. The JGrasstools project, as well as other java based projects (as JTS and even !GeoTools) would benefit a lot from the possibility to be used within a WPS environment. The proposal is to bring the Java binding to a mature level and validate them by integrating the JGrasstools libraries. This will allow them to work inside the ZOO-Project and serve its modules under the WPS standard.
 
 === Mentors ===
@@ -51 +51 @@
 * Andrea Antonello as co-mentor
 
-== Moving the ZOO-Kernel JavaScript support from SpiderMonkey to V8 ==
+== Moving the ZOO-Kernel !JavaScript support from !SpiderMonkey to V8 ==
 
-When the ZOO-Project decided to implement the JavaScript in 2009, SpiderMonkey was a well-known technology. Nevertheless, time has changed and now the Google V8 implementation is now becoming more and more popular over the year. 
+When the ZOO-Project decided to implement the !JavaScript in 2009, !SpiderMonkey was a well-known technology. Nevertheless, time has changed and now the Google V8 implementation is now becoming more and more popular over the year. 
 
-The goal of this GSoC project is to '''provide an optional V8 support for the ZOO-Kernel'''. The main goal is to provide a similar implementation  to the one already available. So to say, the goal is to provide an implementation which can support the exact same ZOO-Services already existing and implemented using the JavaScript language with the V8 engine in place of the SpiderMonkey current implementation.
+The goal of this GSoC project is to '''provide an optional V8 support for the ZOO-Kernel'''. The main goal is to provide a similar implementation  to the one already available. So to say, the goal is to provide an implementation which can support the exact same ZOO-Services already existing and implemented using the !JavaScript language with the V8 engine in place of the current !SpiderMonkey implementation.
 
-For this purpose, the implementation should be able to load the following JavaScripts files: [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-api/js/ZOO-api.js ZOO-API] and [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-api/js/ZOO-proj4js.js ZOO-prj4js]. The [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L150 C functions exposed to the JavaScript language] should also be available, they are: [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L34 alert], [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L849 ZOOTranslate], [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L870 ZOORequest], [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L955 ZOOUpdateStatus] and [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L59 importScripts].
+For this purpose, the implementation should be able to load the following !JavaScripts files: [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-api/js/ZOO-api.js ZOO-API] and [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-api/js/ZOO-proj4js.js ZOO-prj4js]. The [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L150 C functions exposed to the JavaScript language] should also be available, they are: [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L34 alert], [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L849 ZOOTranslate], [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L870 ZOORequest], [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L955 ZOOUpdateStatus] and [http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/service_internal_js.c#L59 importScripts].
 
 === Mentors ===