Re: wgnuplot

[Nigel N. <nn...@gm...>]

[My reply only went to Ethan.  Reposting to list.]

On Sun, Oct 12, 2008 at 7:00 PM, I replied...

Hello Ethan!

On Sun, Oct 12, 2008 at 5:20 PM, Ethan A Merritt
<merritt@u.washington.edu> wrote:
> On Saturday 11 October 2008, Nigel Nunn wrote:
>> Hi wgnuplotters,
>>
>> The old wgnuplot code maps very easily onto wxWidgets.
>
> I'm lost.  What do you mean "maps onto"?


We can replace the Win32 code with wx code.  One of the original
intentions for wx was to replace a cruddy MFC. This means upgrading
Win32 gui code is easy.

> We already support wxWidgets on MSWin, so far as I know.

It looks like the wx version is attempting to drive a wx gui from a
console app.  I may have misunderstood this design. As a stand alone
solution, this may work, but a more natural approach may be to have a
gui wx app driving the gnuplot library code.  This allows us to expose
gnuplot as a library of plotting routines.  Our simulation environment
can then drive gnuplot, as we do wtih Vtk.


>> After October 25 I will start reworking the current wgnuplot to handle
>> plotting duties inside our wxVtk simulation environment.  If anyone
>> has comments or suggestions (to help make this useful to a wider
>> group) please send them in.
>
> You should probably look at the work Michael Goffioul is doing.
> I don't understand this MSWin stuff, but I gather he's re-working the
> communication paths for wgnuplot to do away with any need for a
> separate pipe-handling program (pgnuplot).
>
>        Ethan

thanks for the suggestion!
Nigel