« BasicPrinciples » : différence entre les versions

De GENOPUS
Aller à la navigation Aller à la recherche
Aucun résumé des modifications
Aucun résumé des modifications
Ligne 1 : Ligne 1 :
<font color=#556B2F>'''GENOPUS'''</font> widgets correspond to [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] objects (for example <font color=#4169E1>GPAbsoluteDate</font> for <font color=#4169E1>AbsoluteDate</font>, <font color=#4169E1>GPOrbit</font> for <font color=#4169E1>Orbit</font> …).
<font color=#556B2F>'''GENOPUS'''</font> widgets correspond to [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] objects (for example[{{PathCurrentJavaDoc}}/fr/cnes/genopus/time/GPAbsoluteDate.html GPAbsoluteDate] for <font color=#4169E1>AbsoluteDate</font>, [{{PathCurrentJavaDoc}}/fr/cnes/genopus/orbits/GPOrbit.html GPOrbit] for <font color=#4169E1>Orbit</font> …).
All these widgets are coded in <font color=#FF8C00>Java</font> using [[https://logiciels.cnes.fr/en/node/76?type=desc GENIUS]]  functionalities for <font color=#4169E1>display</font> but also <font color=#4169E1>read/write</font>: it means that they will propose the possibility to store them via an <font color=#FF8C00 title="Extensible Markup Language">XML</font> file.
All these widgets are coded in <font color=#FF8C00>Java</font> using [[https://logiciels.cnes.fr/en/node/76?type=desc GENIUS]]  functionalities for <font color=#4169E1>display</font> but also <font color=#4169E1>read/write</font>: it means that they will propose the possibility to store them via an <font color=#FF8C00 title="Extensible Markup Language">XML</font> file.



Version du 7 septembre 2017 à 10:30

GENOPUS widgets correspond to [PATRIUS] objects (for exampleGPAbsoluteDate for AbsoluteDate, GPOrbit for Orbit …). All these widgets are coded in Java using [GENIUS] functionalities for display but also read/write: it means that they will propose the possibility to store them via an XML file.

Initialization

A main requirement for most of the GENOPUS widgets is the fact that they can be initialized:

  1. With no argument, meaning that all internal values have “by default” values
  2. With the corresponding [PATRIUS] object

Getting PATRIUS objects

Another main requirement is the fact that most of GENOPUS widgets own a getPatriusObject() method allowing getting the corresponding [PATRIUS] object.

Some non graphical objects

Some classes are not widgets but more computation flight dynamics ones. Most of the time, their name start with “Custom”. In fact, they correspond to temporary classes that could be included in [PATRIUS] library but which are not available at the time being or available but with lacking methods (getters for example). Each time an equivalent class will be available with [PATRIUS] , the next GENOPUS version will link with it and the old “Custom” equivalent class will become obsolete.