Chris Nandor wrote: >My idea is to put the name of the doc in the menu. Currently in Shuck the >menu item might be "Data structures". In my version the menu item says >"Data structures (perldata)". Would that suit you? Yes it's clearer R J Kimball wrote: >How about rewriting the menus so they look like this? > >perlre (Regular Expressions) >perldata (Data Types) >perlop (Operators and Precedence) Ditto as above *takes a deep breath*perhaps (starts digging a foxhole) might I suggest insted of having a seperate POD for where Mac may differ from DOS/VMS/Unix (ie that system() doesn't work unless you have toolserver etc, or comand line switches that don't work) why not put this information into the relevant points of the Docs thus making forays into PODs a lot less window intensive and less time consuming? if it's down to the fact the greater Perl community won't like the docs being /hacked | cobbled together | messed about with | broken/ then I suggest calling them something else (it worked for The Artist Who Was Formerly Known As Prince) and covertly distrubuting them :). Seriously though there are issues we should deal with, instead of thinking of MacPerl as perl on the Mac (read evolved Unix glue language on a Mac) we should be thinking about what it has become SINCE it was ported, it shares a heritage but much in the way bears and dogs do - common ancestors different beasts - so is the bear manual workable as the dog manual and vice versa? Can you try to grok a bear while reading the lables on a dog food tin? It's left as an exercise for the reader to figure out if Unix is the bear or the dog in the anology :) # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org