Index: trunk/doc/help.html =================================================================== --- trunk/doc/help.html (revision 20480) +++ trunk/doc/help.html (revision 20481) @@ -62,6 +62,11 @@ icons designer icons, other graphical elements for the GTK HID css designer CSS for the homepage (only design/style, no content). atest C/beginner program automated test cases + rosetta scripting port example scripts to your favorite language (more details) + fungw_pkg packaging packaging fungw for your favorite distro (more details) + script_pkg packaging packaging libmawk, funlisp, estutter for your favorite distro (more details) + actionw C action wrapper programming (more details) + Index: trunk/doc/help_details.html =================================================================== --- trunk/doc/help_details.html (nonexistent) +++ trunk/doc/help_details.html (revision 20481) @@ -0,0 +1,78 @@ + + + + pcb-rnd - help wanted + + + + + + + + + + +
Main + News + Doc & pool + Support + People + Events & timeline + pcb-rnd [pcb-rnd logo] +
+ + +

pcb-rnd - help wanted - details

+ +

porting example scripts

+

+The rosetta scripts start with an awk script, because awk is my favorite +language. When the awk version is tested out and the documentation +finalized, the script needs to be ported to different languages. The +porting is line-by-line, becuase we want to have all scripts do the same +and look the same, that's how it's easy to compare them. +

+If you have a favorite language, you could join porting example scripts to +that language. +

+Requirements: knowing your scripting language, system-wide fungw +installation, pcb-rnd from svn. + +

packaging fungw for your favorite distro

+

+At the moment fungw has no packaging coverage. Because we use fungw as the +action infrastructure, we have a minimal (no-script) version embedded in +src_3rd/ and scconfig already has the logics for choosing a system +installed version over the local version when avaialble. +

+To make system installs more wide-spread, we need OS packages, preferrably +official packages in as many systems as possible. Fungw is small: the core +lib and all existing engines (~ script language bindings) take up 4k sloc +total). The only challange is that we need to have a modular packaging: a +core package and one package per script language binding, to avoid the +core package depending on 6..8 scripting engines. +

+Requirements: knowing your favorite distro's packaging model + + +

packaging libmawk, funlisp, estutter

+

+These three scripting language libs are relatively small (funlisp is even +tiny), and unlike many popular languages they come with a nice, generic +API. Unfortunately they are not widely known so we lack OS packages. They +are generally easy to package. +

+Requirements: knowing your favorite distro's packaging model + +

action wrapper programming

+

+Most of our API in pcb-rnd are good, old-fashioned, raw C APIs. Which +means they are currently unaccessible to scripts. To make them accessible, +we need to write action wrappers. Such an action wrapper is usually +simple, as 90% of the time we want to expose the very same API, +parameter-to-parameter, in a coordinated effort. +

+Requirements: intermediate C knowledge, willing to learn the fungw API, +willing to use svn and IRC + +