Re: [wxperl-users] porting a perl/tk application to perl/wx

[Bob H. <cat...@ya...>]

>I think it was pointed out that you needed to read
the documentation.

I'll stop you here. If you read all my comments, as
you seem to have, then you know that I have been
asking for documentation, but had none, because there
is none (proper). Today, I asked for how to bypass the
perl-gui programming at once via XRC. I do not care
about gui programming. I hate it. I do not know wxPerl
programming. I hate its API, it is not consistent with
PERL's philosophy, and I am not going to learn its
guts just because you love it. All I care about is to
get the real job done with no need to bother with gui
programming.

On the docs, I have a 700+ pages book on wxWidgets
(Cross-Platform GUI Programming with wxWidgets, P.Hall
2006) which is for c++ and python, not for perl.
wxPerl is different; it might mirror wxPython on the
API, but is not identical to wxPython, and I am not
going to learn python plus 700+pages just because the
wxPerl community cannot bother writing the PODs and a
single tutorial that does the job. Now, you might like
things as they are, because all you do is to program
gui 9-5, but I do not. All I want from wxPerl is to
cut through its own gui programming. I do not want to
see gui code in my own code in the first place. I want
a clear cut between form and function, and a minimal
interface between them.

I am not sure about how many people are actually using
wxPerl, but the fact that there is no proper
documentation, and all the efforts (from both
wxWidgets and wxGlade) are towards c++ and python,
speak aloud about how much wxPerl is lying behind,
both in terms of support and in terms of number of
users. I think I know why, at this point. If you want
to go forward in this direction, I am not going to
stop you. I just do not care. I care about having
wxPerl reading and using an XRC file directly. I know
that there are people who know how to do it. There is
no documentation around, so I am asking for what
little could be gathered in this mailing list. All the
rest is either old ideas, or new ones that I am giving
away. If the developers want to implement the ideas,
it is up to them. My resolution is that either I get
the docs on how to use an XRC, or I will stick with
Tk, which works wonders anyway (if you know how to use
it) and is cross-platform too.

The best idea is the XRC interpreter in c++, which
would cut out a large part of the problems and
development efforts with both wxPerl and wxPython, and
wxGlade. However, I understand that the developers
might be reluctant to let go, expecially after having
spent years to do implement an idea that is now
obsolete. It is hard to let go, but the old does clear
of the way, eventually.

Bob



 
____________________________________________________________________________________
Food fight? Enjoy some healthy debate 
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367