On Jan 29, 10:49 am, [EMAIL PROTECTED] (David Cantrell) wrote: > On Mon, Jan 28, 2008 at 10:45:56AM -0800, [EMAIL PROTECTED] wrote: > > That seems to argue that I publish Mac::Pasteboard pretty much as is, > > then follow with Mac::Clipboard. It's lazy, but is it lazy _enough_? > > Would it expedite discussion if I put out a pre-release of the code? > > If so, how should it be done? Mail the tarball to people who ask? Post > > to the newsgroup? Submit to CPAN with a development version number? I > > can't guarantee the documentation to be limpid prose, but the code > > works. > > Release early, release often, that's what I do. > > I note, however, that there is already a Clipboard module that claims to > do the job on OS X. But the tests don't run properly on OS X. > > So *maybe* Mac::Clipboard isn't necessary. >
Yeah. But Clipboard under Mac OS X just shells out to pbcopy or pbpaste, as the case may be. And then only if you have IO::All installed (or at least, that's what I assume from the errors I get -- apparantly the author wasn't careful about what his or her dependencies were). I _do_ have subroutines called (suprise, suprise) pbcopy and pbpaste; but also an o-o interface that will do "get me the UTF16 text from pasteboard item 12345 on pasteboard 'my.very.own.pasteboard'." That's why I was raising the possibility of release, since if I did that, we'd all be (potentially, anyway) talking about the same code, instead of just each talking about our own ideas of it. Tom Wyant
