I'm not one of the "heavy coders" of Padre, but I'm sure that many
people here will be happy to see your last note.
Thanks for "spreading the word" - this is wonderful.

Regarding the packaging of Padre with Strawberry,
Well... I think that this is necessary for MS-Windows, but not for Linux / BSD.
This is the reason - I guess - for making the "MSI" package that
installs Strawberry+Padre on  MS-Windows.
IMHO -  the simplest way for Padre on MS-Windows is to install this
package - and then upgrade Padre inside the Strawberry environment,
using CPAN.
This is what I do on the MS-Windows PC that I have at work.

On my home laptop and PC I have Linux (currently Ubuntu and ArchLinux).
Usually - Linux (and *BSD) already come with Perl.
So no need for Strawberry Perl in a usual Linux / *BSD.

And... in fact using Strawberry Perl on MS-Windows is very good for
developers (I really love it) but it's not a "must".
Padre can be installed on MS-Windows - also with ActiveState Perl.

On my work PC I have two Padre installations - one on ActiveState Perl
environment, and other one on Strawberry Perl environment. Both live
together.

But I use the one from Strawberry.



On Fri, Apr 22, 2011 at 6:11 PM, Charlie Gonzalez <itchar...@gmail.com> wrote:
>
> Oren,
>
> You are correct. I forgot to mention that I spoke about the fact that I had 
> to do a memory upgrade from 1 gig to 2 gigs and that I had a few memory 
> issues while installing Strawberry Perl and Padre on my netbook with 1 gig 
> ram.  I used this example to argue the fact that Padre and Strawberry Perl 
> needs to be packaged with the latest version of Padre to avoid time consumed 
> on installing both.
>
> PC with greater processing power than a netbook are ideal candidates for 
> installing Padre.
>
> I am considering to work on a User Manual for Padre but I need to spend some 
> time looking at the docs that are available to formulate a list of questions 
> before I begin.
>
> FYI my presentation has inspired many of my coworkers to install and consider 
> working with Padre. Thanks again for building such a wonderful IDE for Perl.
>
> Charlie G
>
> On Fri, Apr 22, 2011 at 6:09 AM, Oren Maurer <meor...@gmail.com> wrote:
>>
>> Hi Charlie
>> The presentation looks very nice!
>> Really!
>> Just a small comment regarding the time that of installing Padre on 
>> MS-Windows:
>> I guess that first of all it's a question of memory and CPU.
>> AFAIK - the Asus EEE PCs are designed to be lightweight and small laptops - 
>> also in memory... mainly for running Web browser and Office.
>> Compiling on it will surely take longer then on larger laptop.
>> And - as far as I know - installing Padre directly from CPAN does require 
>> compilation (of Wx).
>>
>> On Thu, Apr 21, 2011 at 10:31 AM, Zeno Gantner <zeno.gant...@gmail.com> 
>> wrote:
>>>
>>> Hello Charlie,
>>>
>>> On Wed, Apr 20, 2011 at 11:53 PM, Charlie Gonzalez <itchar...@gmail.com> 
>>> wrote:
>>> > I have conducted a presentation in  regards to my user experience of 
>>> > Padre.
>>> > This presentation was done in the NY Perl Seminar Group yesterday and  
>>> > below
>>> > is a url to the slides. (CC'ed in this email is Jim Keenan the moderator 
>>> > of
>>> > NY Perl Seminar Group).
>>> >
>>> > http://www.slideshare.net/CharlieGonzalez2/padre-user-experience
>>> >
>>> > This presentation was mainly focused on the user perspective of the Padre
>>> > application. A demo of Padre was also done at the end of the presentation.
>>>
>>> Thank you very much for presenting Padre, and also for sharing the
>>> slides with us.
>>>
>>> > I want to inquire about any present efforts on producing  a training book 
>>> > on
>>> > how to use Padre. Is there an effort to do this and if so how can one
>>> > contribute?
>>>
>>> Currently, all Padre documentation is in the form of POD in the Padre
>>> source files, plus some content on the wiki and in blog posts.
>>> Very recently, there has been some effort to document Padre's features
>>> in detail in the wiki: http://padre.perlide.org/trac/wiki/Features
>>>
>>> So no, there is currently no user manual in the form of a book.
>>> If you want, you can start one - the feature list would of course be a
>>> good starting point.
>>> I would be willing to contribute, but I am hesitant to lead the thing
>>> because my free time for Padre is currently quite limited.
>>>
>>> If you have questions, don't hesitate to ask them here in the list or on 
>>> IRC.
>>>
>>> As said, sharing your experience is very valuable to us.
>>> For instance, I did not know that installing a current Padre takes 1.5
>>> hours on Windows!
>>> This is actually quite sad, we should definitely do something about this.
>>>
>>> Best regards,
>>>  Zeno
>>> --
>>> MyMediaLite Recommender System Library: http://ismll.de/mymedialite
>>> _______________________________________________
>>> Padre-dev mailing list
>>> Padre-dev@perlide.org
>>> http://mail.perlide.org/mailman/listinfo/padre-dev
>>
>>
>>
>> --
>> ________________________________
>> Oren  Maurer
>> http://oren.maurer.org.il
>> http://meorero.wordpress.com
>>  _______________________________
>>  #  =======================|
>>  #  Please avoid sending me Word |
>>  #   or PowerPoint attachments      |
>>  #  =======================|
>>  # See: http://www.gnu.org/philosophy/no-word-attachments.html
>>
>> _______________________________________________
>> 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
>



--
________________________________
Oren  Maurer
http://oren.maurer.org.il
http://meorero.wordpress.com
 _______________________________
 #  =======================|
 #  Please avoid sending me Word |
 #   or PowerPoint attachments      |
 #  =======================|
 # See: http://www.gnu.org/philosophy/no-word-attachments.html
_______________________________________________
Padre-dev mailing list
Padre-dev@perlide.org
http://mail.perlide.org/mailman/listinfo/padre-dev

Reply via email to