[pmwiki-users] ZAP and "fun with forms"

[Dr Fred C]

Ben Stallings wrote:
> Dan wrote:
>   
>> I'm wondering if Pm, or any current ZAP users have input on the
>> direction ZAP should pursue?
>>     
>
> Having just caught up on this thread, I tend to agree with Crisses that 
> (paraphrasing here) you should wait to accommodate this new 
> forms-processing until it's part of the core and has stabilized and been 
> documented.  For my part, I'll also update DataQuery and DataPlates at 
> that time (and not before), so that DataQuery will generate basic forms 
> using the core functionality and DataPlates will embellish the forms 
> with Acme/ZAP for additional functionality.
>
> The one area where I think you (Dan) and Hans need to be sure to get 
> your two cents in is to make sure that your recipes will have a 
> clear-cut way to alter and/or prevent normal form processing when 
> necessary. ...
    As one who's managed rapidly evolving software systems of a similar 
nature to pmwiki, IMHO, the ZAP project needs have some sort of milepost 
like documentation system about what direction it's going to help guide 
development to complete existing mileposts before proceeds onto another 
evolutionary branches.  It seems to have enough going for it to become a 
solid contributor to pmwiki's utility.  In my experience, ZAP having 
documentation of this sort helps in several fashions.

   1. Developing new features to well expressed, logical (internal)
      documentation helps direct code development to be of the same
      quality, especially if more than one programmer is working on the
      project.
   2. Quality documentation that attempts to explain new code
      development frequently exposes fallacious illogical code that
      shouldn't be allowed to see the light of day.  Hence, it makes
      sense to first develop to documentation, not visa versa.
   3. Development toward documentation tends to come in organized steps,
      rather than scattered pulses of code development in this or that
      direction which may require significant (unacceptable) rewrites of
      earlier enduser projects. 

    Pmwiki has PITS, which covers features, bugs, cookbooks, and more.  
Perhaps Zap should have ZITS... :)   , with the goal of promoting more 
blemish free development towards usable utilitarian ACME like goals.  :-o

Just a thought...

-- 

Always, Dr Fred C
drfredc at drfredc.com