On Mon, Mar 5, 2012 at 2:52 AM, Ahmad Zawawi <ahmad.zaw...@gmail.com> wrote: > I know this is a somewhat late response. I am not totally familiar > with PDL. What kind of support do we need for PDL in Padre (e.g. > Padre::Plugin::PDL). > > Could you explain what needs to be done? > - PDL keywords highlighting
Yes, this would help users see what routines are actual PDL methods or subs. > - Padre help integration Yes. PDL has a pdldoc command and 'help' and 'apropos' commands in the interactive shells. It would make sense if this could be integrated with Padre support. > - Snippets? I don't know what this means. > - Run PDL scripts? Yes. > - Debug PDL scripts? Yes. This would also include using PDL from an interactive command line REPL type stuff. There is an existing PDL shell (pdl2) based on Devel::REPL that was inspired by the Padre REPL shell with the hopes of smoothing the integration with Padre. > - Syntax check PDL scripts? Yes. A key feature here would be to support PDL::NiceSlice syntax for multidimensional indexing/slicing operations. To start with, just colorizing the niceslice operations to indicate where they are would help show the "special" constructs. E.g., if $a is a shape [2,4,3] pdl, then to select the the 2nd [2,4] slice from $a, the syntax is: $a(:,:,(1)) or $a->(:,:,(1)) See docs for PDL::NiceSlice for more details. Where I could see this going would be a tool to visualize and edit/refactor slicing operations which are the essence of PDL vector operations. See Conway's Life iteration update in 3 lines of PDL code, here http://pdl.perl.org/?docs=Threading&title=PDL::Threading A slice-builder tool would allow one to construct these operations more easily since it could track the dimensionality and perhaps even auto-insert dimension reordering, etc, to make things work. > - Show in Outline PDL elements. I'm not sure what this means. > P.S. I am willing to allocate FuN time on this one if i can understand > what needs to be done first :) I'm cc-ing the perldl mailing list in case other users and developers have ideas for this or even direct experience using Padre and PDL already. Also, having tutorial/introductory documentation on how to develop for Padre (task API, help specs,...) that would allow new developers to contribute to Padre + PDL integration would be a *huge* help. Having a stable, documented, explained and explainable Padre would really help here. Thanks, Chris > Regards, > Ahmad M. Zawawi > > 2012/2/6 chm <devel.chm...@gmail.com>: >> Hey Gabor- >> >> We've just released PDL-2.4.10 along with the >> first draft of the PDL Book. PDL seems to be >> getting close to being a fully portable release >> across all major perl platforms: windows, >> unix-en, and macosx. >> >> I've seen some recent announcements that Padre >> may be starting to stabilize with a 1.0 release. >> >> If that is the case, maybe it would be possible >> to take another look at using Padre with PDL in >> the coming year. With the rapid evolution of >> Padre recently, it has not been possible to >> investigate further as part of PDL development. >> >> Cheers, >> Chris >> >> On 2/6/2012 2:48 PM, Gabor Szabo wrote: >>> On Mon, Feb 6, 2012 at 8:03 PM, kmx<k...@atlas.cz> wrote: >>>> >>>>> Any reason why "Strawberry Perl 5.14 preview release" is not the >>>>> default stable? >>>> >>>> http://strawberryperl.com/package/kmx/p5.14.2.1-RC/ was prepared (by me) >>>> in release quality (well tested, digitally signed, many bugs fixed) >>>> >>>> Ask Alias why he did not uploaded these ZIPs/MSIs to proper place (where >>>> I was not given an access) - note that the files are dated 22-Nov-2011, >>>> which is the date when I have notified him (+ couple of times after that) >>> >>> Hmm, I thought it had some issues or that at least it was not signed. >>> >>> I'll try to ask Adam what's the problem and in the meantime I'll try >>> to install Padre in it >>> starting with the 32 bit msi file as I only have a 32 bit Windows. >>> >>> regards >>> Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
