Changes between Version 13 and Version 14 of DevelopGuide

Timestamp:

Sep 22, 2008, 8:00:47 AM (16 years ago)

Author:

Frédéric

Comment:

--

DevelopGuide

@@ -24 +24 @@
 Papywizard uses a MVC-like pattern, which keeps the model separated from the views. This allows to use any other toolkit if needed; I recently switched from Tkinter to PyGTK, to run papywizard on Nokia plateform. I hope, one day, to be able to run papywizard on QTopia-based devices, like Openmoko. But I first need to get such device ;o)
 
-Low-levels routines which control the hardware are also in their own package; I plan to made them even more modualr, to be used in an external project to control the head. For know, only Merlin/Orion head is supported, but it is very easy to implement other heads.
+Low-levels routines which control the hardware are also in their own package; I plan to made them even more modular, to be used in an external project to control the head. For know, only Merlin/Orion head is supported, but it is very easy to implement other heads.
 
 A word about the simulation (to come).
@@ -34 +34 @@
 ==== Custom presets ====
 
-The current (1.0) version does not allow user to add its own presets, at least not from the GUI. But it is not very difficult to modify the code to do that. Juste edit the {{{<install_dir>/papywizard/common/config.py}}} file (you may need to become root), and add the new preset(s) in the '''PRESET_INDEX''' and '''PRESET''' vars. The first one is used by the GUI to build the list of presets (in a Combo Box), and contains a double-entry dict. The integer is the position of the preset in the GUI list. The second var contains the presets themselves. Note that the names must match in the 3 locations!
+The current (1.0) version does not allow user to add its own presets, at least not from the GUI. But it is not very difficult to modify the code to do that. Just edit the:
+
+{{{<install_dir>/papywizard/common/config.py}}}
+
+file (you may need to become root), and add the new preset(s) in the '''PRESET_INDEX''' and '''PRESET''' vars. The first one is used by the GUI to build the list of presets (in a Combo Box), and contains a double-entry dict. The integer is the position of the preset in the GUI list. The second var contains the presets themselves. Note that the names must match in the 3 locations!
 
 A preset is just a python dict., where the key is its name (as listed in the GUI), and the value a list of tuple, where each tuple is the ''(yaw, pitch)'' position to shoot. Note that it is possible to use The {{{None}}} value as position; in this case, the given axis won't move, but rather stay at the previous position. This is mainly used for ''zenith'' and ''nadir'', where the ''yaw'' position does not matter. Example: