Boost logo

Boost :

From: Brock Peabody (brock.peabody_at_[hidden])
Date: 2003-07-30 16:18:18


> -----Original Message-----
> From: boost-bounces_at_[hidden]
[mailto:boost-bounces_at_[hidden]]
> On Behalf Of E. Gladyshev
> Sent: Wednesday, July 30, 2003 1:27 PM
> To: Boost mailing list
> Subject: RE: [boost] Re: GUI/GDI template library
>
> > If a decision is based on information that cannot be
> > known at
> > compile-time then you must make that decision at
> > run-time.
>
> How do you decide what information can and what cannot
> be know at compile-time. For instance if you want to
> use an external fullblown scripting definition of the
> GUI layout, almost no information is know at
> compile-time. I put my question another way, how much
> of POTENTIAL scripting functionality the library
> should provide?

I think that the scripting environment should be built on top of the
coding library. The 'basic' platform independent GUI library would
provide unlimited potential to be used as the foundation for a scripting
library.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk