On Mon, Jan 16, 2012 at 1:42 PM, Joel Berger <[email protected]>wrote:
> You can use the > File::ShareDir<https://metacpan.org/module/File::ShareDir>framework to > distribute and locate the data files, you'll need the EU::MM > port called > File::ShareDir::Install<https://metacpan.org/module/File::ShareDir::Install>. > Then the PDL::SampleData module will call File::ShareDir to find the > installed folder location, it can the rfits and return the piddle. > > I'll mock something up. > > Cheers, > Joel > This sounds like the right approach to me. It adds a CPAN dependency, but I care little about such things. Other porters, however, may object, so we'll need to discuss this on the Porters list. Let us know when you have something David > On Mon, Jan 16, 2012 at 6:51 AM, David Mertens <[email protected]> > wrote: > > And by the way, that's a particularly dumb way to do it. Sorry. I didn't > > look at it until after sending it. > > > > The best way would be to have some PDL::Data (or more properly named) > > module, which could then examine %INC. I have working code at work that I > > can send if others want to see it. > > > > David > > > > On Mon, Jan 16, 2012 at 6:48 AM, David Mertens <[email protected] > > > > wrote: > >> > >> Sorry, forgot to include attachment. > >> > >> David > >> > >> > >> On Mon, Jan 16, 2012 at 6:47 AM, David Mertens < > [email protected]> > >> wrote: > >>> > >>> > >>> > >>> On Mon, Jan 16, 2012 at 6:28 AM, zentara <[email protected]> > wrote: > >>>> > >>>> On Sun, 15 Jan 2012 17:48:42 -0500 > >>>> chm <[email protected]> wrote: > >>>> > >>>> > >>>> >I'll aim to get a reworked TriD chapter by next > >>>> >weekend and then the writeup on the PDL shell(s). > >>>> > >>>> Hi, > >>>> > >>>> Mark Baker, [email protected] > >>>> wants to make a separate TriD Recipes pod. > >>>> > >>>> So what would be a good full name for the pod? > >>>> TriD::Recipes? > >>>> > >>>> I'm wondering, for the reason you mention below. > >>>> > >>>> >Also, maybe we should standardize on a location > >>>> >for the images (maybe a separate subdirectory > >>>> >and naming scheme like img/subdir where subdir > >>>> >is all lowercase version of the POD source file > >>>> >name---to help systems that can't or won't > >>>> >differentiate between case in filenames...). > >>>> > > >>>> >Cheers, > >>>> >Chris > >>>> > >>>> So if we have a pod called TriD::Recipes, I would then > >>>> put, and refer to images, stored in > >>>> imgs/trid::recipes/img01.png, etc, etc? > >>>> > >>>> Also, what about including animated gifs and > >>>> possibly small videos, for the TriD examples? > >>>> Can those be embedded in the html sections? > >>>> > >>>> 0m, > >>>> zentara > >>> > >>> > >>> I don't want to get too far off topic, since this is supposed to be > about > >>> the Book, but I don't know that we have ever decided on where we want > to put > >>> data. Furthermore, even if we distribute data with PDL, we don't have > an > >>> easy way to get at it. As such, I think (1) we should choose a specific > >>> place to put image data and (2) we should create a module for > accessing that > >>> data. To give an idea of how this module might look, I've attached a > module > >>> I used in a talk I gave about PDL that simplified the access of M51 > for me. > >>> > >>> Getting back to the topic, we cannot do #2 for 2.4.10 since said module > >>> wouldn't be allowed (we're in code freeze). We *can* discuss and agree > on a > >>> location where we put images and other data for 2.4.10, and for 2.4.11 > we > >>> can create a module or set of modules for accessing that data. > >>> > >>> I'm not sure where we should put images, but I expect > >>> that imgs/trid::recipes/img01.png won't work for Windows, but a minor > >>> variant might: imgs/trid-recipes/img01.png. Where would these images be > >>> installed? I suggest PDL::Data, i.e. > >>> site_perl/<perl-version>/<OS-version>/PDL/Data/TriD/Recipes/img01.png, > which > >>> is basically where MakeMake will put it if we tell it to create a > >>> PDL::Data::TriD::Recipes directory. > >>> > >>> David > >>> > >>> -- > >>> Sent via my carrier pigeon. > >> > >> > >> > >> > >> -- > >> Sent via my carrier pigeon. > > > > > > > > > > -- > > Sent via my carrier pigeon. > > > > _______________________________________________ > > Perldl mailing list > > [email protected] > > http://mailman.jach.hawaii.edu/mailman/listinfo/perldl > > > > -- Sent via my carrier pigeon.
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
