Hi Pritpal, >> SO: win XP, harbour+mingw >> > > I know. I will concentrate on it once I will establish the parent/childs > relations for all the interface widgets. It is message loop which has gone > weired because not all the widgets are created through Xbp* class framework. > This tool is of hibrid mode using Xbp class framework with HBQT classes for > some widgets which are not available in Xbp. > > This is the reason I floated the idea of extending Xbase++ framework > which has not been accepted by the group by now. > > But I am feeling the pinch of this omission.
AFAIK the only one reaction came from me telling you _can_ extend it, just guard all the extensions with HBXBP_EXTENSION. This looks like a pretty simple thing to do (although it needs some paying attention of course), and not a huge price to pay to create extensions. Since I assume clean extensions come in the form of new classes or new methods/vars in existing Xbase++ compatibility classes, another solution is to mark all these class/ method/var names with distinctive prefix (hb_/hb). I'd advise against hidden extensions like new parameters to existing methods or change of behavior, since these are much difficult to handle, but if you need to do such thing, the HBXBP_EXTENSION trick would work as well. Any of above is even useful for yourself if you ever want to do any Xbase++ compatibility testing of hbxbp code. Two more thoughs: 1) Apart from this, IMO it would be a great plus if users could mix hbxbp and hbqt usage in one app, as I'm sure there will ever be someone who find hbxbp feature not enough for their apps, and wants to use some hbqt features directly (and don't have the freedom or will to extend hbxbp). I assume it's not always nice to extend base hbxbp classes for _every_ need that appears when coding hbide. 2) hbide could be a nice showcase to present elegant way of hbxbp programming and if/where needed a nice showcase of mixing hbxbp and hbqt the "proper" way. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
