I am interested in the XRC question myself. I was looking at the 'complicated' recipe to convert. How different are the files? It occurs to me, that an XSLT filter is called for. After all that is what XSLT is built to do :wink:
I've got another question, why not use an XRC based schema? I would 'see' two way to accomplish that. To embed the XRC as embedded XML in a wxSmith layout. Or, to keep two files. One the XRC and the other a 'wxSmith helper' file.
used for resource without separate xrc file) only use different name of root node and adds few extra properties / nodes. Simple text editor should be enough
Having looked at the wxSmith layout and made the conversion to XRC a few times now, why don't you just use the XRC by default anyway! That would make for a cleaner design. As if the wxSmith encapsulated the XRC. At them moment it looks as if we have a bit of a hybrid.
> one major thing i fight with is usually that it seems to allowe
> only the common classes like wxTreeCtrl and stuff.
Fortunately for you, this is not true anymore :) The syntax is quite
simple:CodeHTH,<object class="wxTreeCtrl" subclass="MyTreeCtrl">
...
</object>
MyTreeCtrl must be registered in wx's RTTI system:
class MyTreeCtrl: public wxTreeCtrl
{
DECLARE_DYNAMIC_CLASS(MyTreeCtrl)
}
...
IMPLEMENT_DYNAMIC_CLASS(MyTreeCtrl, wxTreeCtrl)
Vaclav
Byo: How about making derivative classes that do the initialization like you want it?
From http://lists.wxwidgets.org/pipermail/wx-users/2002-September/024391.html :
I imagine that if you also define xrc handlers for objects like wxTimer, maybe that could do the trick :)