[Padre-dev] opening an arbitrary pod file

[Gabor Szabo]

After some fighting with PERL5LIB I managed to install KinoSearch-0.163
that required Lingua-Stem-Snowball-0.952,    Snowball?

I don't have much understanding in indexing and searching so I don't
know if this is a
good tool or not.

As of another dependency, I don't mind it - our plan was always to
pull half of CPAN in :-) -
but I am quite sure our memory footprint will have another blow with this.

So I wonder what others says?

Gabor

On Mon, Jan 12, 2009 at 9:11 AM, Andrew Bramble
<bramble.andrew at gmail.com> wrote:
> One of the parts still undone in Wx::DocBrowser is a chooser allowing
> the user to pick from a group of provider schemes like 'pod://' ,
> 'perldoc://' , 'man://' . Wx::DocBrowser is also doing something a bit
> strange with HTML_LINK_CLICKED events from it's notebook children so
> internal document links don't work.
>
> Certainly a good index is a big missing part. How do you feel about
> pulling in a dep on something like KinoSearch to provide the index ?
>
> Doc Providers I would hope to see in padre core ;
>
> perldoc (aka perlop , perlipc etc - the non module docs) - not working
> correctly on Win32 right now ?!?
>
> Pod (from installed modules , optionally from CPAN where no installed
> module found) - see 'module_to_path' in DocBrowser::Pod , stolen
> shamelessly from the venerable Pod::Frame (RIP)
>
> 'SystemDocs'  being *roff unix man pages or your platform equivalent
> (started this, trickier than I imagined)
>
> Wx & WxWidgets (I notice the dev plugin addresses this to a degree, it
> would be even nicer to find/build wx docs against the installed
> version)
>
>
>
> On Mon, Jan 12, 2009 at 5:30 PM, Gabor Szabo <szabgab at gmail.com> wrote:
>> Besides viewing the docs of perl 5 I'd like to be able to see a
>> searchable version
>> of the Parrot documentation - currently scattered around several
>> directories in the
>> svn checkout of Parrot and the Perl 6 documentation.
>> Obviously I'd like to be able to index and search them separately.
>>
>> Gabor
>>
>> On Mon, Jan 12, 2009 at 1:05 AM, Andrew Bramble
>> <bramble.andrew at gmail.com> wrote:
>>> Poorly handled at best right now.
>>>
>>> I'd suggest opening them in the editor and using Help -> Current Document
>>>
>>> I still don't think DocBrowser is smart enough. Nor the POD2HTML
>>> renderer it uses. What bothers me the most ? The direction it is going
>>> in as that of an honest to goodness browser, and there are several of
>>> those available (I've heard).
>>>
>>>
>>> On Mon, Jan 12, 2009 at 8:48 AM, Gabor Szabo <szabgab at gmail.com> wrote:
>>>> I have several pod files in some directories on my hard disk
>>>>
>>>> /path/to/docs/a.pod
>>>> /path/to/other/docs/b.pod
>>>>
>>>> how can I open them with the PodBrowser ?
>>>>
>>>> 'perldoc:/path/to/other/docs/b.pod'
>>>> does not seem to work.
>>>>
>>>> How can I create a pod file with links to these files?
>>>> L</path/to/docs/a.pod> created a link but when I clicked on it I got
>>>>
>>>> Could not find documentation for
>>>> perldoc:/path/to/docs/a.pod
>>>>
>>>>
>>>> Gabor