1. [WIN] parser from MakeDoc.exw [Derek]

Derek,

I'd like to make use of your version of MakeDoc to get a list of Win32Lib
routines, & other stuff, from Win32lib_full.ew, but I'm having a little
trouble.  Looks like you
may have done very nearly exactly what I need, but I can't quite see where
the data ends up so as to make use of it.

I'm trying to update a mod I made for Judith's editor, which allows for easy
pasting of all Euphoria and Win32Lib routines into the code editor from a
list of routines, in a default form showing each routines parameters.  The
mod includes a list of the names of all Win32Lib routines, what kind of
routine each is, the short description, and the html name (for jumping to
its help); when I did this previously, I modified the then current
"MakeDoc.exw" program to spit out those things into a file, in exactly the
form I wanted to put into the editor mod.

But my earlier "MakeDoc" mod doesn't seem to work with Win32Lib 0.55.1, so I
thought to try to modify its  "MakeDoc.exw" similarly, but it appears you
may have now written it so it practically does what I want, with the
constants,
   , kName        = 1     -- name of routine, first for sorting
   , kTopic       = 2     -- topic
   , kTag         = 3     -- html tag
   , kDesc        = 4     -- short info

Problem is, I can't figure out exactly where that data ends up so as to
selectively retrieve & use it.

Can you help?

Here's a sample of what my previous mod of the MakeDoc parser yielded:

-- Topics and Routines from Win32Lib,
-- Version:     0.50

global constant W32RoutinesCategories = {
    {"General (Attributes)"},
    {"Colors"},
    {"Dialogs"},
    {"Edit Control"},
    {"Event related"},
    {"Fonts"},
    {"Graphics"},
    {"Image Lists"},
    {"List Control"},
    {"ListView Control"},
    {"Low Level Routines"},
    {"MonthCalendar Control"},
    {"Mouse"},
    {"Printing"},
    {"RichEdit Control"},
    {"Scroll Control"},
    {"TreeView Control"},
    {"Types"},
    {"Utilities"},
    {"XPM (graphics)"}
}

--***************
constant AttributesStuff = {
    { "addToBand( id, band )", "Add a control to a RebarBand ",
"ADDTOBAND" },
    { "closeWindow( window )", "Close < window>. ", "CLOSEWINDOW" },
    { "create( class, title, parent, x, y, cx, cy, flags )", "Create an
object of type < class>.  ", "CREATE" },...

Thanks,
Dan Moyer

new topic     » topic index » view message » categorize

2. Re: [WIN] parser from MakeDoc.exw [Derek]

----- Original Message -----
From: <DanMoyer at PRODIGY.NET>
>
> I'd like to make use of your version of MakeDoc to get a list of Win32Lib
> routines, & other stuff, from Win32lib_full.ew, but I'm having a little
> trouble.  Looks like you
> may have done very nearly exactly what I need, but I can't quite see where
> the data ends up so as to make use of it.

Hi Dan,
MakeDoc has become quite useful, especially because its not win32lib
specific. David Cuny wrote the first version and I've added extra
capabilites to it, but its never been documented. Also, I'm currently adding
the ability to derive documentation from multiple files as if it was one
file.

I'll document the tool and submit it to the contributions list as an item in
itself.

------
Derek Parnell
Melbourne, Australia
"To finish a job quickly, go slower."

new topic     » goto parent     » topic index » view message » categorize

3. Re: [WIN] parser from MakeDoc.exw [Derek]

Derek,

Good idea, I look forward to it.  Thanks.

Dan

----- Original Message -----
From: "Derek Parnell" <ddparnell at bigpond.com>

>

>
> ----- Original Message -----
> From: <DanMoyer at PRODIGY.NET>
> >
> > I'd like to make use of your version of MakeDoc to get a list of
Win32Lib
> > routines, & other stuff, from Win32lib_full.ew, but I'm having a little
> > trouble.  Looks like you
> > may have done very nearly exactly what I need, but I can't quite see
where
> > the data ends up so as to make use of it.
>
> Hi Dan,
> MakeDoc has become quite useful, especially because its not win32lib
> specific. David Cuny wrote the first version and I've added extra
> capabilites to it, but its never been documented. Also, I'm currently
adding
> the ability to derive documentation from multiple files as if it was one
> file.
>
> I'll document the tool and submit it to the contributions list as an item
in
> itself.
>
> ------
> Derek Parnell
> Melbourne, Australia
> "To finish a job quickly, go slower."

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu