Re: [wxperl-users] Basic WXPerl questions

[Joe Y. <jyo...@jo...>]

Hi Edward,

I'm pretty sure you can make only a couple changes to your current app and
add GUI support quite easily.

If you haven't already downloaded the samples, I'd do that now and take a
look at the sample/controls.pl file.

In there Mattia builds a text control, sets it as the log and then sends
output to it....really simple.

Look at wxLogTextCtrl, wxTextCtrl, and read the log overview in the help
files.

I think your hardest/longest activity will be building the classes for the
GUI rather than making the changes on output to the log control.

hth,
JY
----- Original Message ----- 
From: "Edward Wildgoose" <Edward.Wildgoose@FRMHedge.com>
To: <wxp...@li...>
Sent: Wednesday, July 23, 2003 12:38 PM
Subject: [wxperl-users] Basic WXPerl questions


I currently have an application which basically is a long running app which
just spits out periodic output to stdout (status messages every now and
again)

I would like to put a simple GUI around this so that it looks a bit more
professional, not really much more than a text box for the status messages
though, and a couple of labels to show current status, and perhaps a couple
of buttons.

The app needs to run on Linux and Win32, and I have been evaluating TK, but
run into some pretty serious limitations with it's handling of reading data
using fileevent on win32

Suppose I wanted to put a wrapper around this app with wxperl could I do
something as simple as running my current app, grabbing stdout and feeding
it into the text box on screen?  What would be some pseudo code to achieve
that, and what kind of wx controls do I need to look at?  (Basically I don't
want to be using an on idle thread and watching a perl filehandle).  I could
convert the underlying app to spit output to a socket if this made it easier
to use wxsocketclient?

In the long term if wxperl works out, then I would like to convert the app
to a proper wx app, which will basically mean that the guts of my current
app (big IO::select which listens for incoming tcp connections and starts
various server code in response) to use wxsocketserver.  Are there any
caveats to watch out for with this in the current implementation of wxperl?
Does everything work properly under windows and linux right now, or are
there any funny limitations?  For example will it mean that I can toss out
all the nasty code  which works around non-blocking sockets on windows
machines...?

Thanks for any pointers

Ed W



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
wxperl-users mailing list
wxp...@li...
https://lists.sourceforge.net/lists/listinfo/wxperl-users