|
Posted by Sam Holden on July 23, 2004, 12:36 pm
Please log in for more thread options
I would like to upload a module I've written to CPAN. I've got a PAUSE
account, but I need to work out a module name.
It's an interface to the Wily text editor's message interface, since
I suspect not many people have heard of wily if you care about it
have a look at:
http://www.cs.yorku.ca/~oz/wily/
The module allows a perl script to connect to a running a wily and use
the messaging interface, creating windows, opening files, intercepting
commands, and so on.
Currently the module is named 'Wily' with a handful of Wily::* packages.
For CPAN it should probably not be a top level namespace. But I can't
find an existing top level namespace in which it fits. In fact I can't
even find a section it fits in.
Any advice would be appreciated.
It's *very* tempting to stick it in Acme:: , since Wily is a work-alike
of the plan9 editor called 'acme'. But that's subverting the acme
namespace...
--
Sam Holden
|
|
Posted by Jim Keenan on July 25, 2004, 8:15 pm
Please log in for more thread options
> I would like to upload a module I've written to CPAN. I've got a PAUSE
> account, but I need to work out a module name.
>
> It's an interface to the Wily text editor's message interface, since
> I suspect not many people have heard of wily if you care about it
> have a look at:
>
If it's a text editor, why not Text::Wily?
It would seem to fit nicely on this search.cpan.org page:
http://search.cpan.org/modlist/String_Language_Text_Processing/Text
jimk
|
|
Posted by Sam Holden on July 26, 2004, 6:44 am
Please log in for more thread options >> I would like to upload a module I've written to CPAN. I've got a PAUSE
>> account, but I need to work out a module name.
>>
>> It's an interface to the Wily text editor's message interface, since
>> I suspect not many people have heard of wily if you care about it
>> have a look at:
>>
> If it's a text editor, why not Text::Wily?
>
> It would seem to fit nicely on this search.cpan.org page:
> http://search.cpan.org/modlist/String_Language_Text_Processing/Text
Because it doesn't deal with text itself. It implements a message based protocol
to talk to the text editor and command it to do things like open a file in
a window, execute a command, search for some text in a window. And can also
receive events - the user searched for this text in this window, the user
executed this command in this window, the user typed this text, etc.
So the module doesn't actually work with text itself. The sort of things that
have been written with it (or with other language variants of it) are:
* A terminal - ie. running a process whose IO goes via a wily text window.
* A mail client - using wily to compose and view messages
I use the following for $EDITOR (when wily is running), for example, the
module name will probably change of course:
---wedit---
#!/usr/bin/perl
use warnings;
use strict;
use Cwd 'abs_path';
use Wily;
use Wily::Message;
die "Usage: $0 filenamen" unless @ARGV;
my $wily = Wily->new();
my $win = $wily->win(abs_path($ARGV[0]), 1);
$win->set_callback(Wily::Message::WEdestroy, sub );
$win->attach(Wily::Message::WEdestroy);
$wily->event_loop();
---wedit---
That has nothing to do with manipulating text, as all the modules in
Text::* seem to.
Though, I guess it's close enough, and certainly preferable to a top level
name.
--
Sam Holden
|
|
Posted by Jim Keenan on July 27, 2004, 7:06 am
Please log in for more thread options > >> I would like to upload a module I've written to CPAN. I've got a PAUSE
> >> account, but I need to work out a module name.
> >>
> >> It's an interface to the Wily text editor's message interface, since
> >> I suspect not many people have heard of wily if you care about it
> >> have a look at:
> >>
> > If it's a text editor, why not Text::Wily?
> >
> > It would seem to fit nicely on this search.cpan.org page:
> > http://search.cpan.org/modlist/String_Language_Text_Processing/Text
>
> Because it doesn't deal with text itself. It implements a message based
protocol
> to talk to the text editor and command it to do things like open a file in
> a window, execute a command, search for some text in a window. And can also
> receive events - the user searched for this text in this window, the user
> executed this command in this window, the user typed this text, etc.
>
> So the module doesn't actually work with text itself.
[snip]>
> That has nothing to do with manipulating text, as all the modules in
> Text::* seem to.
>
> Though, I guess it's close enough, and certainly preferable to a top level
> name.
While in general it's not a good idea to open up a new TLNS, it's
certainly not unprecedented, particularly with interfaces to
commercial programs (see:
http://search.cpan.org/modlist/Commercial_Software_Interfaces).
Should non-commercial programs take the same approach? That's a
question I would pose at module-authors@perl.org, and, since that's
where the people who have the most invested in Perl modules gather to
hash things out, I recommend you extend this discussion there.
Jim Keenan
|
| Similar Threads | Posted | | URI::URL query vs equery | February 1, 2005, 9:30 am |
| Query about Spreadsheet::WriteExcel | September 10, 2004, 3:54 pm |
| TL1 module namespace | May 12, 2005, 1:13 pm |
| A module looking for a namespace | March 4, 2005, 11:15 pm |
| New module namespace | May 17, 2006, 8:38 pm |
| Google API using SOAP Lite doesn't like '&' in query | June 29, 2005, 2:06 pm |
| Namespace for new module: HTML::Template::HTX? | May 13, 2005, 7:17 pm |
| Module namespace: Tie::Flatfile::Array | February 25, 2007, 11:55 pm |
| Namespace for Z-machine parse/translate module | July 29, 2004, 10:02 am |
| Choosing a good namespace for a module to upload to CPAN | July 14, 2004, 1:46 pm |
|
XML Sitemap