Re: Segregating wxperl from App Code

On Sat, 3 Apr 2004 09:04:08 +0200 (CEST),  wrote:


>I just 'finished' my first Wx project and while writing it I finally did
>what I should have done a lot earlier: OOP (Object Oriented Programming).
>I rewrote most of the project as classes and ended up with a lot cleaner
>code.
>
>As a side-effect it made what you want to do (making CLI & GUI versions)
>easy. All of the code that used Wx was in the main file and it was easy to
>strip all of that and end up with a daemon-only version without end-user
>interaction just network interface. An object always knows how to find
>it's own methods (routines) so you won't have any of those scope problems.
>
>So maybe you should try this chapter as well:
>
>http://learn.perl.org/library/beginning_perl/3145_Chap11.pdf
>

Sounds like a mini-faq "Writing Application Code for WxPerl" might be
a good idea, any volunteers?

zzapper (vim, cygwin, wiki & zsh)
--

vim -c ":%s/^/WhfgTNabgureRIvzSUnpxre/|:%s/[R-T]/ /Ig|:normal ggVGg?"

http://www.vim.org/tips/tip.php?tip_id=305  Best of Vim Tips



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click