starting to look at indexing...

[Aaron J. Seigo]

i'll jump in randomly here.. scott'll correct me where i'm off ;-)

On Sunday 07 November 2004 07:07, Gregory Newby wrote:
> > *) KLink::Link will be a triplet containing a source node (for text a
> > KLink::Word) a target node (in the simple case a file) and optionally a
> > KLink::Anchor (which says how to index into target)
>
> I'm vague on the use of Anchor.  Is this a document type?

no.. it's a data-specific way to mark WHERE in a set of data the link points 
to, much like the "name" value  in an HTML <a> tag. this might be a time for 
an audio file (e.g. seconds into a song) or a word/paragraph index for a word 
processor document. this allows linking INTO data and not just AT data (where 
i'm using "data" to refer to a superset of "file" and "document")

> that this will be a limitation.  Unless we're getting beyond
> the individual desktop level, it's not that likely.  

the plan is to eventually network-enable this, yes. so it will be more than 
the local desktop; it may be all the desktops in an entire enterprise.

> Great!  Is there a source code repository we'll be using?

KDE's CVS, right now it's in the klink directory of the kdenonbeta CVS module.

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/klink/attachments/20041107/ab55df66/attachment.pgp