Hello Meir & all, I do like the concept of a ³traps & pitfalls² section for each discussion topic when available. The difficulty I had was how to accommodate these in the design document. I think for now, whenever a specific trap or pitfall is posted to the group, I¹ll document it in the ³Additional Comments² column.
As for your question on whether the wxPerl book idea is a dynamic environment, absolutely yes. Anyone can post suggestions or comments and I will certainly pay close attention to them. Whether an idea should be incorporated into the book or not, will hopefully be decided by the wider wxPerl community. Thanks for your thoughts. Cheers, Ron. On 21/01/16 12:53 AM, "Meir Guttman" <mguttm...@gmail.com> wrote: > Dear Ron, > > Unfortunately I have next-to-nothing experience in wx and wxPerl, although I > have some stale GUI experience doing Tk programming in Perl almost six years > ago. The only example I do have is while installing it, as can be seen here > <http://stackoverflow.com/questions/28584660/installing-alienwxwidgets-into-a- > windows-7-strawberry-perl-box-failed> . The gotcha here is:"don't use > CPAN-Minus, use CPAN!. > > Other examples of "gotchas" in other modules can be found here > <http://www.nntp.perl.org/group/perl.dbi.users/2014/07/msg36989.html> (use > "server prepare" attr.) and here > <http://stackoverflow.com/questions/30276611/declaring-a-perl-array-and-assign > ing-it-values-by-an-array-slice> (don't try it). > > But anyway, this is going to be a dynamic environment, right? And if you are > going to allow and provide (moderated) talk-back, people will contribute > these. Example can be found in MySQL docs > <http://dev.mysql.com/doc/refman/5.6/en/comments.html> . > > Regards, > Meir > > -- Meir > > On Wed, Jan 20, 2016 at 4:30 PM, Ron Grunwald <ron...@yahoo.com.au> wrote: >> Hello Meir & everyone, >> >> First of all, thank you for your suggestions, Meir. >> >> On point 1, yes, that¹s a much better title. I¹ll change it in the design >> document. >> >> On point 2, I partially agree with you. I think the concept of a first >> complete wxPerl program has merit in the introductory part because it gives >> the reader an immediate overview of what wxPerl code looks like. I also >> really like Steve¹s comments about explaining the fundamental components like >> OnInit, Show and MainLoop. >> >> Still on point 2, you mentioned how to combine basic widgets to form a >> complete application. I think that¹s a good idea and I¹ll take that onboard. >> However, it wouldn¹t be suitable to write about it in the introductory part >> in my view. >> >> On point 3, are there any specific examples that you¹re thinking of? >> >> Many thanks. >> >> Cheers, >> Ron. >> >> On 19/01/16 10:51 PM, "Meir Guttman" <mguttm...@gmail.com >> <http://mguttm...@gmail.com> > wrote: >> >>> Hi Folks! >>> >>> A few remarks: >>> 1. Shouldn't the name be ³Part I - Introduction to GUI programming with >>> wxPerl²? >>> 2. The equivalent of "Hello World", other than making sure the installation >>> is OK, does very little to knowing how to write a real-world GUI >>> application. Therefore, examples must be quite elaborate because in my very >>> little experience with wxPerl, the problem was not with the buttons, the >>> check boxes and the radio selection. It was how to combine them. >>> 3. I would like to see a "Gotchas" as the last chapter, of every part, >>> regarding the topics in it. I am sure that many people are falling to the >>> same holes, and without help, it will take them too long to crawl out of >>> them... >>> That's my two bits... >>> >>> Meir >>> >>> -- Meir >>> >>> On Tue, Jan 19, 2016 at 4:17 PM, Ron Grunwald <ron...@yahoo.com.au >>> <http://ron...@yahoo.com.au> > wrote: >>>> Good evening everyone, >>>> >>>> As I¹m adding to the design document, I find myself thinking more and more >>>> about Part I Introduction to wxPerl and GUI programming. I expect this >>>> part of the book to be quite long. I think it may also become the most >>>> important part of the book as it¹s here where potential newcomers will >>>> decide whether its worth their time and effort to further pursue learning >>>> about wxPerl. >>>> >>>> To that effect I would like to turn to the members of this list. Imagine >>>> that you have no idea what wxPerl is all about, but you have heard others >>>> talk about it. What would you like to see in an introduction section that >>>> would hold your interest and want you to keep reading more? >>>> >>>> Steve has already mentioned installation of wxPerl. This will certainly be >>>> included in Part I and deserves a thorough and concise writing effort. I >>>> would also like to see a chapter entitled ³A simple wxPerl program². The >>>> wxPython book has an exquisite example on page 35 in the PDF document. I¹ve >>>> attached the page for your reference. >>>> >>>> Finally, in relation to my use of the term ³geometry management², yes it >>>> refers to ³layout². I¹m just used to the former term from my programming >>>> days with X/Motif and Perl/Tk. >>>> >>>> I really would be very interested to hear about your views on what to >>>> include in ³Part I - Introduction to wxPerl and GUI programming². >>>> >>>> Cheers, >>>> >>>> Ron. >>>> >>>> >>>> On 18/01/16 11:19 PM, "Steve Cookson - gmail" <steveco.1...@gmail.com >>>> <http://steveco.1...@gmail.com> <http://steveco.1...@gmail.com> > wrote: >>>> >>>>> Hi Ron, >>>>> >>>>> Thanks for this. >>>>> >>>>> >>>>> On 17/01/16 12:53, Ron Grunwald wrote: >>>>> >>>>> >>>>>> >>>>>> 1. Introduction to GUI programming and wxPerl >>>>>> 2. The wxPerl widgets (currently worked on in the design doc.) >>>>>> 3. Geometry management in wxPerl (to be worked on next in the design >>>>>> doc.) >>>>>> 4. Event handling in wxPerl >>>>>> 5. Advanced Topics >>>>>> 6. >>>>>> >>>>>> >>>>> Is Geometry Management the same as layout? If so I had to do a double >>>>> take to work out what it meant. >>>>> >>>>> Maybe we should also have something about platforms and installation, >>>>> which is always a joy! It could be an appendix if you wanted, so that the >>>>> flow of the chapters was not disrupted. >>>>> >>>>> Regards >>>>> >>>>> Steve. >>>>> >>> >>> > >
