Re: C++ & Hydrant

[Alain Magloire]

> 
> "Alain Magloire" <address@hidden> writes:
> 
> > And I would even go on step further with the front-end by decoupling
> > the windowing system, so one could use curses, gtk+, ...
> > depending on the need.
> 
> Aaargh! I started a library for that purpose some time ago, but it is
> far, far, *FAR* from finished. I think the last thing it was doing was

In C++ ?
If you browse sourceforge, freshmeat or whatever you have that's
hype today.  You'll find tons of free software, some are good
very good and many are bad ... very bad.

<rant on>
One of my pet peeve is to see the lack of decoupling
from of the  engine.  A prime example of this is Tcl/Tk
Tk even in the higher levels use X functions calls.  So the
what the Window and Mac port author did is to have an emulation
X layer.  There was no layer in Tk to protect the highest layer,
porting Tk on other windowing system is a nightmare, especially
if your windowing system is completly foreign to what X is.

Same goes for many Email browsers found on freshmeat etc ...
Every new mailbox format is a challenge this not that bad since
the email browser is close tied to the underlying engine.

But having a "plugin" API that isolate the different level of
the program is benificial and maybe a good thing even if you
have to bloat the code a little.  Having a tight little mail
browser really couple/bind together is great too but maintaining it
when you have a moving target ... is difficult at best.

</rant off>

> basic input and output with curses, gtk+ bindings weren't even
> close. If anyone is interested, it's in the module gnuts on
> subversions.

That certainly could be a starting code for hydrant to decouple
the gui rendering.
Again is in C++ ? Are you considering C++ ?

-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!