thanks,
i just use wxperl and my techniques are maybe considered
dirty by others, bcause im not a huge fan of the oop
style matia proposes in the examples. im shure you can take some
style inspiration from there.
but as i teached wxperl it begins with very simple things
like do explizit return value. some methods rely on a return value.
dont take a return value from another sub for that. its hard to debug
when something goes wrong
for beginners its oftern easier to create the GUI by vlick and point and use
wxformbuilder, create XRC and load that later by the program to get a gui.
its also a nice abstraction layer customers can play with.
there are some other little things like this but mainly its about what to but
in which class/module to manage complexity.
or i use lttle funcs like
sub gbpos { Wx::GBPosition->new(@_) }
sub gbspan { Wx::GBSpan->new(@_) }
to get a gridbagssizers->add vommands in one line
im shure other have here different ideas.
Am 13.07.2010 18:49, schrieb Eric J. Roode:
> Hello All,
>
> I would like to tap into the accumulated wisdom of the WxPerl sages
> and write an article on what coding techniques would be considered
> "Best Practices" in WxPerl programming.
>
> This is probably a subjective (and maybe contentious?) subject, so
> hopefully there will be some good discussion here about this. Feel free
> to chime in with what you have learned makes the development process go
> easier, helps you to reduce bugs, organize your code, etc. I will gather
> the comments posted here, condense them down, and post the result to the
> WxPerl wiki.
