Re: gEDA-dev: Google summer of code

[Igor2 <igor2-at-NOSPAMinno_dot_bme_dot_hu>]

On Sat, 3 Mar 2007, DJ Delorie wrote:

>
>> The only thing I need to be able to continue with the script HID is GUI
>> functionality in both GUI HIDs so that commands created by scripts could
>> be accessed trough hierarchical menus. I guess if an experienced dev
>> (DJ?) would design the API and add the necessary things in the HID
>> structure, the rest could be done by those students.
>
>If the scripts are just actions, you can register them as such and the
>user can put them in their pcb-menu.res.  This already works.
>
>I've been thinking of expanding the "exporter" API to include
>"importers" and "wizards" (things that just act on the current board).
>This isn't much different than plain actions, except that there would
>be a place in the menu tree where they'd show up automatically.

What I mean is not just to initiate an action, but to be able to present a
simple dialog box to set up the parameters. Is that possible with
pcb-menu.res? With exporters, it is (and it already works from scripts).

My favorite example is tiling: the user has the script plugin
installed and a tile.tcl (or tile.php or tile.py, etc) would be copied in
his scripts directory. When he runs PCB, on the script plugin
initialization these scripts are loaded and initialized. The script can
register hids (currently only exporter hid). The tiling script would
register a wizard hid so a new submenu would show up in the wizrds
menu. When the user would select it, a dialog box would pop up with
settings like
 - how many columns/rows he would like to have or to fill up
   the board size
 - what's the spacing between the tiles
 - should each tile have a small boarder (I find this useful for toner
   transfer)




_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev