in reply to How to structure LARGE Perl/Tk application?

See Re: Perl Tk - propagating events...and this result from my own similar re-engineering effort.

I wouldn't get too concerned about PBP stuff. I'd suggest sticking to basic OO and MVC; you may end up with code looking more like Java than Perl, but it will also probably be easier to maintain...and to eventually convert to AJAXy goodness, as I'm doing with most of my GUIs

  • Comment on Re: How to structure LARGE Perl/Tk application?

Replies are listed 'Best First'.
Re^2: How to structure LARGE Perl/Tk application?
by TGI (Parson) on Oct 01, 2008 at 22:10 UTC

    I've just been browsing your site. What's up with PSiCHE? It looks very interesting. Are the libraries available for download? Is the system usable for real work yet? Do you have some sample code? Insert inane question here?


    TGI says moo

      PSiCHE languishes.

      Mostly because Thread::Sociable languishes.

      Because I haven't won the lottery or inherited a large sum of money recently, and no one seems inclined to write checks sufficient to support the effort and resources required to complete it.

      Because the Perl(5) community seems content with fork and pipe.

      Which means I have to apply myself to other, more mundane, albeit profitable, pursuits, because its difficult to get a decent wifi signal from a refridgerator box on skid row.

      All of which is a damn shame. A recent thread on the Groovy lists pointed out a couple people presenting on concurrency models for Groovy. Based on concurrency stuff being added to Java, and soon, to Python. One such presentation is planned for codecamp. From which Perl appears to be completely absent.

      Which is (in part) why I'm spending more time reading Groovy books and maillists, than reading about/doing Perl these days.


      Perl Contrarian & SQL fanboy