> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Rainer Deyke > Sent: Wednesday, August 06, 2003 12:32 PM > To: [EMAIL PROTECTED] > Subject: [boost] Re: GUI/GDI template library > > Brock Peabody wrote: > > Method 1 - common underlying representation method > > > > layer 1 - target GUI API > > > > layer 2 - low level GUI API interface wrapper. There is one > > implementation of this wrapper that compiles for all target platforms, > > using standard cross-platform development methods. This layer may be > > private to boost (in namespace detail). > > > > layer 3 - high level boost GUI API. This is the public interface to > > our > > GUI 'domain specific sublanguage'. It is implemented on top of layer > > 2. > > Like I said before, I would need to use a custom layer 1. This means that > I > also have to write a custom layer 2 under both methods. If boost::gui is > to > be useful for me at all, it has to provide layer 3, and the interface > between layers 2 and 3 has to be public.
If layer 2 is platform independent there is no reason not to make it public, other than to promote the use of the higher level abstractions at layer 3. > > Oh, and I really want the ability to select layers 1 and 2 at runtime, in > a > single place in my code, on a per top-level window basis. Let's just try to get it working first. I don't doubt that we could do this but is it worth the cost in increased complexity to both the implementation _and_ the interface? _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
