Difference between revisions of "DevelopmentPlan"

From OOModels
Jump to navigationJump to search
Line 26: Line 26:
| download servlet
| download servlet
| gets all necessary parameters from download page<br>translates paremeters to istreams via ''oomodels reader''<br>calls ''main converter''
| gets all necessary parameters from download page<br>translates paremeters to istreams via ''oomodels reader''<br>calls ''main converter''
|  
| created oomodels.jar with servlet infrastructure
|  
| 1
|  
| [[Contact:Person/net/leue/andreas|al]]
|-
|-
| oomodels reader
| oomodels reader

Revision as of 14:12, 24 June 2008

Task Description State Priority Contributor
Concept make design of software for oomodels this table here
a Unit Test Case is available
1 al
download page (jsp) page which is the target of all the download links in the wiki
searches for all conversion pages
provides a list of possible target formats
each entry has a "download xyz format" button
calls download servlet with respective parameters
optionally tries sequences of conversion with one (or two) central formats
mediawiki indices several lists and indices (like all artefacts within a certain domain) should be generated automatically - the "Category" mechanism is already a good start - so one or a few good extensions would be valuable
download servlet gets all necessary parameters from download page
translates paremeters to istreams via oomodels reader
calls main converter
created oomodels.jar with servlet infrastructure 1 al
oomodels reader accesses oomodels via http
finds code section in page
extracts code section, recodes escapes, removes anchor tags etc.
provides code as java io stream
java converter interface something like
public interface org.oomodels.tools.Converter ...
public IStream convert(String converter_id, IStream code, ??? arguments...)
arguments might be: IStream's, name, type and encoding of IStreams's (Strings)
1
main converter a dispatcher, which is a singelton with the converter interface
redirects according to converter registry
converter registry redirects to a list of registered converters
(a registered converter is one with an entry in the wiki)
matching is according to regexps
generator converter converter, which uses sphenon generator for transformation
xslt converter converter, which uses xslt for transformation
soap client converter converter, which redirects to a soap interface for conversion
soap server converter soap server, which calls the converter interface
eclipse plugin plugin core, with extension points for local converters
step one: given a page url from oomodels and a target format, the oneline
(or preferred local) converter is called
and the result inserted in project
step 2: browsing of oomodels content within ide and a lot more convenience stuff
step 3: workflow engine integration (sphenon processor u.a.), model transformations integration (sphenon oov u.a.)
eclipse oomodels cache in project and all included projects, in a folder "oomodels", the same structure as online can be reproduced
e.g. oomodels/Type/org/oomodels/wiki...
the cache can be maintained automatically or
manually overridded (working completely independent of oomodels.org)
eclipse oomodels reader like oomodels reader, but looks locally in oomodels folders before
eclipse oomodels converter registry like converter registry, but looks in extensions before