[wx-dev] XTI

[Stefan Csomor]

Hi Francesco

I've inscribed to mentor this project, so that I can help with
background info and concepts that were inside. I'm going through all the
emails that were exchanged 4 years ago, on that topic, copy pasting
things that seem important for further work. I'll also go through the
mini sample we used for testing
 
> 2) It's not clear to me however what is a wxHandlerInfo. I could only
> find empty blocks about them:
> 
> wxBEGIN_HANDLERS_TABLE(wxGauge95)
> wxEND_HANDLERS_TABLE()
> 
> in the sources...

HANDLERS are event handlers, the methods that are able to handle a
certain event in YOUR ie the users-code classes. This helps a designer
application to offer the proper connectors for a certain exposed event
eg from a button.

WX_BEGIN_HANDLERS_TABLE(MyXTIFrame)
	WX_HANDLER( ButtonClickHandler , wxCommandEvent )
WX_END_HANDLERS_TABLE()

> 3) I'd say that wxxVariant (as you wrote in a comment) should be
> merged
> with wxVariant. Stefan, did you remember why you did not use
> wxVariant
> right from the beginning?
> To me it seems that it could be reimplemented in terms of
> wxVariant/wxVariantData...

it is using a templated approach, so while it could be merged with
wxVariant technically, I don't see how it could be implemented with it

> 
> 4) The persister/depersister classes seems untied from the wx-stream
> classes when instead they probably should... isn't it?

no, IMHO it is better to have a looser coupled scheme, where we could
offer a bridge to wxstreams of course

> 5) some classes have too-generic names: I propose to use the
> "wxClass"
> prefix for XTI classes exposed to the user. That plays well with the
> already existing wxClassInfo. It was proposed to use a namespace for
> them (since they already require templates to work), but I think that
> we
> should either use a "wx" namespace everywhere or nowhere. Since I
> don't
> think we're going to use "wx" namespace everywhere, then I'd say we
> shouldn't use a namespace for XTI neither.

I wouldn't like to add too long prefix, it is rather connected to the
'info' than to the 'class' in wxClassInfo, because it is meta
information. So "wxClass" doesn't seem to me the best fit.

Best,

Stefan