[Padre-dev] Some Padre problems

[Ahmad Zawawi]

On Tue, Jul 14, 2009 at 9:10 AM, Gabor Szabo<szabgab at gmail.com> wrote:
> Hi Richard,
>
> thanks for your e-mail.
>
> I am also forwarding it to the padre-dev list with a few comments so
> we can improve things.
>
> 2009/7/13 Richard Hainsworth <richard at rusrating.ru>:
>> Dear Gabor,
>>
>> Thanks for your help last night on #perl6.
>>
>> I have  to use padre for quite some time. Got frustrated with various
>> things, but came back to it after seeing work being done on grok.
>>
>> Some problems recently:
>> a) I tried doing syntax highlighting with a
>> proto sub infix:<myoperator>(@vec, at mat) { ... };
>>
>> It gobbled up cpu resources and I had to kill it.
>
> I guess this is an STD.pm issue but I am sure azawawi will be able to look
> into the problem.
>

Sorry for the late response. I am have been busy lately with life's
routine chores.

Try closing Padre and opening the file again. Sometimes Padre runs
Perl 5 syntax highlighters with Perl 6's. When you run the STD
highlighter for the first time, it generates a cached lex folder and
this takes some CPU cycles, but it makes it a bit faster on subsequent
runs. To find out which Padre tasks are running, double click on the
hour glass at the bottom status bar and in the output pane you'll get
a dump of what tasks are currently running.

If things do not work out, you can have a corrupt STD lex cache, and
you can clean it up via the Perl 6 menu and then re-open the file
again.

As for the highlighting problem, STD currently colors a routine
declarator as red but using Rakudo/PGE highlighter you can get better
results (use preferences to select another highlighter).

By the way, what operating system are you using at the moment to run Padre?

>
>> b) I could not get a perl6 script to run (as explained on #perl6) and there
>> is nothing I could find about the necessary environment settings.
>>
>> Perhaps, it would be possible to add a section on Perl6 in the main help
>> document. Just a hint about RAKUDO_DIR would have been useful.
>
> Based on our discussion on #perl6 I see some confusion that we have to clear up.
> 1) The Parrot plugin is not needed for running Perl 6 code on Rakudo,
> its docs should indicate this
> 2) IMHO the Perl 6 plugin should look for the perl6 executable in
> several places (including the $RAKUDO_DIR)
>    but should not attempt to run perl 6 code if it did not find a
> perl 6 executable. It should report it as an error.
> 3) We should have clear instructions on how to get started with Perl 6
> using Padre both in the Perl 6 plugin
>    and on our web site.
>
>

I Agree. And maybe having a pre-built snapshot of rakudo for the
user's operating system.

>>
>> But Padre does look much better now, and I have been wanting to use it for a
>> while.
>

I am glad to hear that. Rest assured Padre will become better by July
26th (Padre's 1-year birthday). I think I can push Perl 6 refactoring
tools along with a better STD highlighter by then.  Customizable
highlighters per Perl 6 construct are also on my TODO list.

Regards,
Ahmad M. Zawawi