Re: Win32Lib Doc, jump-to-links errors--extra space between routine name & (
Derek,
Ok, will do, but it could be a while, we'll see. And that fix does seem
trivial even to me, so I'll probably do it too :)
Dan
----- Original Message -----
From: "Derek Parnell" <ddparnell at bigpond.com>
To: "EUforum" <EUforum at topica.com>
Subject: Re: Win32Lib Doc, jump-to-links errors--extra space between routine
name & (
>
> That sounds fine. Send it to me when you are ready and I'll fix the parser
> to recognise ...
>
> func xxx ()
> and
> func xxx()
>
> as the same thing.
>
> ------------
> cheers,
> Derek
>
> ----- Original Message -----
> From: "Dan Moyer" <DANIELMOYER at prodigy.net>
> To: "EUforum" <EUforum at topica.com>
> Sent: Thursday, August 15, 2002 4:10 PM
> Subject: Re: Win32Lib Doc, jump-to-links errors--extra space between
routine
> name & (
>
>
> > Derek,
> >
> > What I'm doing is just making it make a bunch of separate htm files, &
> > trying to make all the links in all those files (which were originally
> just
> > links to names in the single file) be stated correctly to jump to the
> > correct individual file & then to the name in that file.
> >
> > I have made it create lots of separate files, (eg, alphabetic files for
> > routines; Table of Contents; Index; Topics, etc.), and make correct
links
> > for all the Topics in the Table of Contents, and for all the items and
> links
> > in the item descriptions in the Index, but a lot remains.
> >
> > This may be less than what you have in mind for it?
> >
> > What exactly do you mean by "fixing the parser"? I'm struggling to just
> do
> > the making correct links to the individual files :)
> >
> > Dan
> >
> > ----- Original Message -----
> > From: "Derek Parnell" <ddparnell at bigpond.com>
> > To: "EUforum" <EUforum at topica.com>
> > Sent: Tuesday, August 13, 2002 12:16 AM
> > Subject: Re: Win32Lib Doc, jump-to-links errors--extra space between
> routine
> > name & (
> >
> >
> > > Thanks. This is near the top of my TODO list. The top item is to
remove
> > the
> > > one remaining bug(yeah, sure!) with the resource subsystem, then to
work
> > on
> > > MakeDoc. If you want to do that instead, please go ahead. However, you
> > > really should have a go at fixing the parser.
> > >
> > > I've been out of action for the last two weeks. I'm back on board
> > tomorrow.
> > >
> > > ----- Original Message -----
> > > From: "Dan Moyer" <DANIELMOYER at prodigy.net>
> > > To: "EUforum" <EUforum at topica.com>
> > > Sent: Tuesday, August 13, 2002 3:24 PM
> > > Subject: Win32Lib Doc, jump-to-links errors--extra space between
routine
> > > name & (
> > >
> > >
> > > > Derek,
> > > >
> > > > I'm modifying MakeDoc to make lots of little htm files instead of
one
> > big,
> > > > like Euphoria docs ('cause on my system the single large one takes
> > forever
> > > > to jump between links), and discovered that a few functions &
> procedures
> > > in
> > > > Win32Lib don't quite follow the format expected by MakeDoc & louse
it
> up
> > a
> > > > little (by making html names and href that aren't exactly the same).
> > > >
> > > > The result is that clicking on some items in the doc results in no
> jump
> > to
> > > > the link. The problem is nothing more than that some functions &
> > > procedures
> > > > have a space between the routine name & the first parenthesis, for
> > > example,
> > > > --/func classDefaults (integer class, sequence pData), instead of
> > > > --/func classDefaults(integer class, sequence pData).
> > > >
> > > > The MakeDoc parser looks for the first parenthesis to construct the
> link
> > > > name, but I guess does something else to make the href link, because
> > with
> > > > the space, the name & the link end up different, without the extra
> space
> > > > they work right.
> > > >
> > > > Here's a list of some like that which I found:
> > > > classDefaults
> > > > setAppName
> > > > setLVInsert
> > > > addLVItem
> > > > getTVParent
> > > > addTVItem
> > > > getTabItem
> > > > expandTV
> > > > setWindowScrollRange
> > > >
> > > > I started to fix this in the parser, but it's easier to fix in the
> > source
> > > > doc :)
> > > >
> > > > Dan Moyer
> > > >
> > > >
>
>
>
|
Not Categorized, Please Help
|
|
