[Padre-dev] POD viewer and perltidy

Heiko Jansen heiko_jansen at web.de
Mon Nov 10 02:53:13 PST 2008


Hi all.

> -----Ursprüngliche Nachricht-----
> Von: "Gabor Szabo" <szabgab at gmail.com>
> Gesendet: 10.11.08 07:43:51
> An: "Padre development discussion list" <padre-dev at perlide.org>
> Betreff: Re: POD viewer and perltidy

> I'd rather move this to the mailing list so others can comment as well.

good move ;-)
 
> the POD viewer was an early experiment in adding, well pod viewer.
> Then I've heard that the CPANPLUS::Shell::Wx project also has a
> pod-viewer and I stopped developing this one in the hope that the other
> one will be split out from that module and can be reused without the
> need of the whole CPANPLUS stack.
> 
> Now I am not sure any more which path to follow. If you pick this up you
> can decide.

Had a short look at CPANPLUS::Shell::Wx some time ago and wasn't overly impressed.
But there were a few updates since then so I'll try again.
It does provide a mechanism to re-use the POD viewer from other Wx applications but I don't know about the internal dependencies.

> My idea was is to create an index of the documentation of perl and
> all the installed modules and let the user search.
> What was implemented so far is the indexing of module names in the sqlite
> database (though it was reported to be broken). the combo-box should be
> a place where you type in a name of the module and it will show you a limited
> list of modules filtered by what you typed so far. Like the Gmail To field.
> The limits can be set in Edit/Prefernces/ Min and Max number of modules.

Ah, ok. 
Regarding indexing of POD: Maybe there's something one could steal from CPAN::Mini::Webserver?
 
> I would like to be able to provide the following:
> when a user highlights $_ , Padre should be able to
> explain what $_ is and lead to the relevant documentation.
> I'd go as far as writing new and more simple documentation
> especially for beginners. That should be factored out to some other
> module and it should be multi-lingual so it can be reused by
> anyone else.
> 
> Padre should also notice if the $_ was actually part of $_[0] and explain the
> difference.

Sounds like a tough job...

> b) Look at the Perltidy Plugin and work on that please.

Will have a look. Once it's stable I'd suggest incorporating it directly into Padre, though.

> For project specific perltidy I think first we need to implement the
> idea of a project.

8-)

Heiko
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066



More information about the Padre-dev mailing list