Here are my thoughts on a possible format so far:
- Archive file (.tar.gz, .zip, .other_archiver) containing
- Plugin file (plugin.pl)
- Plugin Info/Doc file (plugin.xml)
- (Optional) Pre-Install script (pre-install.pl)
- (Optional) Post-Install script (post-install.pl)
- Any extra files (plugin.pm, etc.)
- Single Perl Plugin file (plugin.pl) containing:
- Plugin Code
- Plugin Info/Docs (in POD format)
We can support one, the other, or even both. At the moment, I don't know how easy or hard it is to pull out the POD docs from a Perl script, but I don't imagine it could be too difficult.
Any thoughts, questions, concerns?
; "Feed Stats Widget")
; "Google Referrer")
; "MediaConsumer Template Output")
; "MediaConsumer List Items")
; "MediaConsumer Edit Item")
; "mt-qotd.png")
; "Vox-qotd.png")
re munging POD - don't do it yourself :-)
Check the CPAN for Pod::Parser for all purpose POD munging and Pod::SAX for generating XML from POD, e.g.
# xml -> disk
my $w = XML::SAX::Writer->new(Output=>$fh);
# xml -> xml
my $f = XML::Filter::POD2MT->new(Handler=>$w);
# pod -> xml
my $p = Pod::SAX->new(Handler=>$f);
$p->parse_file("/path/to/pod");
Pod::Simple makes POD hacking, well simple! :)
http://search.cpan.org/author/SBURKE/Pod-Simple-0.96/
If you are looking at a format to use, PAR looks very tempting:
http://search.cpan.org/author/AUTRIJUS/PAR-0.66/
Gavin.
Help me please....
Can you give me, one's example proposal project. "Proposal project matematika research.