I have only used PDL::Prima::Simple's most simple features so far. I
was hoping that some of the PDL::Graphics::* modules authors would
want to chip in, add a line or two if they like, modify something, or
add a code snippet if they want. But anyone can do this, really, the
code is on Github.

I don't know how it gets included (or not) in the main branch though.

On 1 May 2013 16:24, Clifford Sobchuk <[email protected]> wrote:
> Hi Pierre, I was referring to the links to the videos won't work if the 
> person is offline, or for some other reason cannot access the internet site. 
> I was thinking that there might be some simple code snippets that could be 
> added to show what a specific plot in each package would look like. I 
> understand that the target was to provide a quick overview of the packages 
> and which one to choose. If the target was to include the overview in to the 
> book, then links to the specific module examples would suffice. In that vein 
> I tested the  links on the page and several don't work to the meta-cpan site.
> The ones that don't work are:
> PDL::Book
> PDL::Graphics
> I couldn't find either of them on meta-cpan at all. I don't know why the Book 
> is not found on meta-cpan.
>
> Thanks, Cliff.
> -----Original Message-----
> From: Pierre M [mailto:[email protected]]
> Sent: May 01, 2013 6:35 AM
> To: Clifford Sobchuk
> Cc: [email protected]
> Subject: Re: [Perldl] i made a PDL::Graphics doc page to compare all 
> PDL::Graphics modules - what do you think about it?
>
> There's still a few TODO statements in the middle. Especially about the 
> PDL::Graphics::Simple module, there's things that need to be checked or 
> corrected.
>
> I didn't understand your point about adding code snippets to show how to 
> create a plot with each module.
> My current opinion is that this page is just for guiding people towards one 
> solution or the other. Then they'll figure out how to create a plot. If 
> that's not easy to figure out, then it's the module's documentation that 
> lacks clarity, and it should be improved.
> Giving example in this summary feels like duplication. And is not really 
> going to help people choose a module. But I might just be wrong
> (^c^) Can you re-explain why it could be good, Cliff?
>
> On 30 April 2013 22:09, Clifford Sobchuk <[email protected]> 
> wrote:
>> Looks good. I didn't see anything that needed to be cleaned up as a first 
>> cut. It might be useful to embed several code snippets to show how each 
>> module creates a plot. The only reason I say this is for a hard copy or 
>> offline use of PDL there is still documentation that surrounds it.
>>
>> Thanks, Cliff
>>
>> -----Original Message-----
>> From: Pierre M [mailto:[email protected]]
>> Sent: April 27, 2013 10:45 AM
>> To: [email protected]
>> Subject: [Perldl] i made a PDL::Graphics doc page to compare all 
>> PDL::Graphics modules - what do you think about it?
>>
>> Hi all,
>> i've created PDL::Graphics, a documentation page which presents a short 
>> comparative review of the various PDL::Graphics modules. The aim is to help 
>> beginners find easily which PDL::Graphics module is better adapted to their 
>> needs.
>>
>> It's here :
>> http://htmlpreview.github.com/?https://github.com/mascip/pdl/blob/doc-
>> graphics/Basic/Pod/Graphics.html
>>
>> I've finally learned to use GitHub, so i created a doc-graphics branch here:
>> https://github.com/mascip/pdl/tree/doc-graphics
>> You will find the Graphics.pod (and Graphics.html) files in Basic/Pod/
>>
>> Please tell me what you think, correct me where i wrote wrong stuff, and 
>> don't hesitate to participate or even take over: lots of you are better 
>> suited than me for this job, as i have only used Prima::Simple, and just a 
>> little bit.
>>
>> Pierre "mascip"
>>
>> _______________________________________________
>> Perldl mailing list
>> [email protected]
>> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to