-It would be good to make the refdoc samples self-contained, that isavoid the dependency on the slop block (which is not yet annotated in
SVN). I think using codebase in the snippets sitemap instead ofslopbase would enable that. The goal is to make refdoc testable as isfrom SVN, the only
Thanks for the ideas...they may have given me a solution. I'm still
not familiar enough with XSLT to really think with it or in it, but
such ideas can give me a spark. I'll be more specific about the
problem and lay out my quick idea for a solution. Then everyone can
ridicule my hole-ridden
over in advance for it and any help/advice
they may offer.
Thanks,
Robert Graham
Bertrand,
Of course the SlopGenerator is a dead simple component, others might
need much more documentation, but I hope this shows my idea more
precisely. Sorry about not communicating this better before.
I think that you had already gotten this across, I'm just not entirely
sure how to
Bertrand,
Okay. I wasn't sure if a solution like this would be acceptable. It
accepts HTTP GET variables including pageLength (# of hits displayed
per page). I'll go with that for now.
Robert
On 8/8/05, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
Hi Robert,
Le 7 août 05, à 23:30, Robert
the necessary URLs and puts them together.
Any ideas are appreciated.
Robert Graham
I'm not sure why it wouldn't work, but here is a fresh version that
worked for me...
Robert
On 8/4/05, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
Hi Robert,
Le 4 août 05, à 06:03, Robert Graham a écrit :
A new patch for SLOP using the newer style of things...
I tried to apply your
A new patch for SLOP using the newer style of things developed from
the thread about Neutral Document format. I kept the old comments in
there to give the project a more thorough testing. The README hasn't
changed, just look through the patch or affected files. I'll be
posting a new version of
ok - my view was a more high-level one than classes and methods, which
are adequately covered by the javadocs. These are certainly useful
though, but see the proposed use-cases below for a more
component-oriented view.
Okay, this was something I wasn't sure about, but I thought it might
be
an idea. I'd like input and will write up an
email about that specifically to follow tonight.
Cheers,
Robert Graham
doktor-slop-patch.patch
Description: Binary data
Doktor Patch README
Description: Binary data
comments, ideas, or discussion is welcomed.
Thanks for reading.
Cheers,
Robert Graham
I would prefer to send out a tarball, but all I have access to right
now is zip so I've been forced to include several files, a
readme, and the patch file of course. I believe this is all you need,
but make sure to check out the readme before trying anything new.
Robert
patch.patch
Description:
for whatever reason, until I
deleted the old index folder and restarted Tomcat. I'm not totally
sure what caused things to work, but I know that those are the only
new things I did.
While I've solved the problem of creating the right index, I'm still
not sure the solution wil work for refdoc.
Robert Graham
You might want to look at the generated index using a Lucene utility,
Luke for example, it's an index viewer and querier with a GUI. Don't
have the URL here as I'm offline right now, but you'll find it.
Can do. I've been helped out some by an article I found:
1. Extract snippets from the various types of source files: XML, java,
text
I feel that this is mostly complete, but I'm open to new suggestions.
2. Convert these snippets to an XML form that is easily indexable with
Lucene, generating Lucene fields for all important pieces of
On 7/18/05, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
Le 18 juil. 05, à 16:40, Robert Graham a écrit :
...And I seem to be tending away from the Lucene block and toward
Lucene
itself or at least the 1.4.3 jar that comes with Cocoon. Is that an
unwanted design decision
On 7/18/05, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
Le 18 juil. 05, à 19:14, Robert Graham a écrit :
...I've seen it in some examples(XMLSearch), but I'm afraid that I
haven't seen enough of the crawler t understand how to utilize it..
If you start cocoon and go to
http://localhost
Hello all,
I've been digging through the Lucene project and Lucene block docs,
but can't seem to get what I want to work or find much that references
it. So I've got a few more dumb questions to ask.
What I'm trying to do is get a crawler to walk through all the links
that the current refdoc
Hi All,
This is mostly a question for the mentors on the project, but ideas
are welcome. I posted to dev mostly to have it backed up.
I've been through the prototype code and I've even gotten a couple of
the TODO's taken care of (specifically the matching multiple key-value
pairs and most of a
I'm a little confused as to how the wildcard matchers work here:
With a given URI snippets/samples/subdir/dummy-sitemap.xweb
{global.codebase} = ../annotated-code
That folder contains the files referenced by the pipeline.
map:match pattern=*/**.*
map:generate type=slop
I grabbed the trunk off of SVN and the whiteboard and tried to build
this, but it failed trying to build the javadocs and I'm not sure why.
I thought someone might be able to enlighten me.I've got 2.1 running
on the same setup and have no trouble building it. I've edited it for
simplicity as best
Hi all,
I'm Robert, another of the GSoC kind. I'm working on the Cocoon refdoc
project this summer and am really just getting rolling in the last
week or so. Right now I'm doing my homework on Cocoon and it's pieces.
Bertrand mentioned:
Getting up to speed with Cocoon, XSLT and the integration
22 matches
Mail list logo
