Where possible I would like to make our work available to non
Padre users as well.
Certain parts of Padre were moved to PPIx::EditorTools earlier.
In the last two days I moved the code of the Outline building
and the code of the standard PPI Syntax highlighter as well.
Now I'd like to move the Context Sensitive Help to Code::Explain,
the new module I started to write a while ago. Once I manage
to move the core of the help system, it can be used by any
other editor as well (e.g. vim).
I am building a web front-end as well to talk to Code::Explain
and I already hooked Code::Explain up to Hyppolit so IRC
channels will also be able to use the same backend.
Initially it will be for Perl 5. Then soon for Perl 6 and it
can be expanded to other languages as well.
I hope this way we might bring some more contributors
these parts of Padre.
It makes it also a lot easier to test these parts on their own.
So I need to change Padre::Document::Perl::Help and move
most of it to Code::Explain.
As I can see Padre::Document::Perl::Help uses two additional
files:
perlopquick.pod comes now with Padre and I think it is also part
of the standard perl documentation starting from 5.13.x
I would like to move it to Code::Explain::Perl5
The other one is wxwidgets.pod that comes with Padre::Plugin::WxWidgets.
Azawawi, do I recall correctly that the reason this is in a plugin
is some licensing issue? Does the plugin have any other purpose?
If that's it then I'd like to rename it to something like
Code::Explain::Perl5::WxWidgets and move the code that parses
it to the same package.
Have I missed something?
I started to write Code::Explain in Github with the hope that it
can attract more contributors there than within the Padre repository.
What do you think, shall I keep working there or shall I move
it to the Padre SVN repo?
regards
Gabor
--
Gabor Szabo
http://szabgab.com/
_______________________________________________
Padre-dev mailing list
Padre-dev@perlide.org
http://mail.perlide.org/mailman/listinfo/padre-dev
