Re: [mlview-list] Transition to libxml++ ?

[Dodji Seketeli <dodji seketeli org>]

Hello Bruno,

Well, I think we will be needing to switch to a document object model
that is more C++-ish (i.e: one that has better type safety etc).
But, switching to libxml++ is not necessarily the best option.

I would rather go the route of porting the current MlViewXMLDocument to
an mlview::XMLDocument class where the later and the former have the
very same methods (okay, signals would be then based on libsigc++).

This would be pretty much the same as what we did in porting
MlViewAppContext to mlview::AppContext or MlViewApp to mlview::App
for example.

The rationale of this choice is that the current MlViewXMLDocument
mostly has all the functionalities we need and keeping the same methods
will ease the porting of the application over the new class.

So if you feel the guts of undertaking that task, man you have my
blessing :-) I just can't cheer you enough :-)

Best wishes,

 Dodji.

On Fri, Jul 29, 2005 at 05:47:52PM +0200, Nicolas Centa wrote:
> Bruno Dusausoy <bdusauso beeznest net> writes:
> 
> > Hi,
> >
> > In the process of transition from C to C++, will the project use 
> > libxml++ instead of libxml ?
> 
>   Hello,
> 
>   I think we don't need to use libxml++ : we already have our own 
> wrappers to libxml2 because of our very specific needs (like events,
> etc.). libxml++ would be one more dependancy. 
> 
> Nicolas Centa
> _______________________________________________
> Mlview-list mailing list
> Mlview-list gnome org
> http://mail.gnome.org/mailman/listinfo/mlview-list