While I'm actively working on a rewrite of the Task Manager and
threading code, it's being done in a branch and will be moderately
destructive when it lands.

That said, once it lands a ton of background/threading improvements
and fixes that are currently imposing hard to solve should then be
easy, and hopefully progress will resume.

Adam K

On 27 April 2010 18:31, Adam Kennedy <adamkennedybac...@gmail.com> wrote:
> I would say that at least a third of the entire Padre core
> distribution (in lines of code terms) has been written on Win32.
>
> That's not to say there aren't a ton of bugs, just that if you see a
> problem on Windows it is definitely a bug and not something caused
> merely by lack of attention. File tickets against anything you
> encounter.
>
> While the deep internals and all the basic functionality should be
> pretty reliable, in some cases one particular feature that isn't
> commonly used (printing might be a good example) might not have been
> testing on Win32.
>
> Again, file tickets and they should get fixed.
>
> Tests that exercise those features are even better, because CPAN
> Testers will complain indefinitely into the future.
>
> Of course, test scripts for printing would be rather annoying...
> (especially if they printed something)
>
> Adam K
>
> On 25 April 2010 02:09, chm <devel.chm...@gmail.com> wrote:
>> I just updated to v0.60 (win32/strawberry) and
>> verified that the REPL plugin still crashes
>> Padre: if you load the plugin with the manager,
>> enter $a = 1; in the REPL Evaluate widget... BOOM!
>>
>> * Are there any Padre developers working on win32?
>>
>> * Do you see the same result or is this something
>>   screwy in my installation/configuration?
>>
>> * Also, I did load a single perl source file.  When
>>   I selected File->Print the system printer widget
>>   came up but when I hit the Print button, Padre
>>   locked up completely.  (At least when the REPL
>>   kills Padre I don't have to manually kill the
>>   process.  :-)
>>
>> Apologies for the "stick my head up from the rabbit
>> hole" posting but I'm currently working to get all
>> the core PDL functionality to work on win32 perls.
>> Once that is working, I would like to see PDL
>> working with Padre.  Previous list discussions
>> with Gabor Szabo with PDL developers suggested
>> two directions for PDL+Padre work:
>>
>> * Integrate the perldl shell on-line help into the
>>   Padre help capabilities
>>
>> * Make a Padre::Plugin::Perldl interface based
>>   on the current Padre::Plugin::REPL.
>>
>> I'm open to suggestions for inching forward with
>> the win32 Padre problems.  The fundamental problem
>> may be that there are not any win32 Padre developers
>> so that platform will continue to lag until some
>> appear.
>>
>> Padre looks very nice and I look forward to using
>> and developing for it once it works on my platforms
>> of necessity (win32 and cygwin).
>>
>> I'll post again with PDL on win32 status as things
>> happen.  Please let me know if there is any Padre
>> progress on the same front.
>>
>> Thanks much,
>> Chris Marshall
>> PDL Developer / future Padre Developer...
>> _______________________________________________
>> Padre-dev mailing list
>> Padre-dev@perlide.org
>> http://mail.perlide.org/mailman/listinfo/padre-dev
>>
>
_______________________________________________
Padre-dev mailing list
Padre-dev@perlide.org
http://mail.perlide.org/mailman/listinfo/padre-dev

Reply via email to