Now that the interest for this kind of library has been shown (or not,
whatever) could the interested parties please coordinate their efforts
using other means than boost mailing list? IIUC this list is for issues
with existing code (problems, usage patterns etc) and for submissions
that have some
"E. Gladyshev" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> --- Bohdan <[EMAIL PROTECTED]> wrote:
>
> > 2. Finally your lib may become non-template ( i mean
> > cpp files) ...
>
> If it becomes not-template, I'll stop working on it
> :). cpp files are allowed for the layer 1 cod
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> On Behalf Of E. Gladyshev
> Sent: Thursday, August 07, 2003 10:33 AM
> To: Boost mailing list
> Subject: Re: [boost] Re: Re: GUI/GDI template library
[...]
> Not exactly, STL has some i
--- Bohdan <[EMAIL PROTECTED]> wrote:
>
> Under 'non-template' I mean that it is not
> header-only
> library. Generaly term 'template library' is used
> for
> Pure template-inline library which contains only
> headers,
> but not cpp.
> Ex: spirit is template library, but boost::regex is
> not.
N
> Now that the interest for this kind of library has been shown (or not,
> whatever) could the interested parties please coordinate
> their efforts using other means than boost mailing list?
> IIUC
> this list is for issues with existing code (problems, usage
> patterns etc) and for submissions
--- Drazen DOTLIC <[EMAIL PROTECTED]> wrote:
> Now that the interest for this kind of library has
> been shown (or not,
> whatever) could the interested parties please
> coordinate their efforts
> using other means than boost mailing list? IIUC this
> list is for issues
> with existing code (probl
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> On Behalf Of John Torjo
> Sent: Monday, August 04, 2003 2:34 AM
> To: Boost mailing list
> Subject: Re: [boost] Re: Re: GUI/GDI template library
>
[...]
>
> Forgive me for not agreeing
> > 1. i'm 99% sure that plain
> > resource language or even XML is much cleaner than c++ bindings-
> > templates-operators mess.
>
> Templates aren't always beautiful, but this library is targeted towards
> C++ programmers who should be familiar with them. We've had the STL for
> ov
E. Gladyshev wrote:
> --- Rainer Deyke <[EMAIL PROTECTED]> wrote:
>> For a GUI library to be useful to me, it would need
>> to support custom
>> physical GUI layers. I would then write my own
> [...]
>> full-screen multimedia. I
>> realize that my needs are unusual, and boost::gui
>> may be unabl
>From: "Edward Diener" <[EMAIL PROTECTED]>
> Add to this the fact that nearly every C++ programmer already works with a
> framework library depending on his implementation of choice. On Windows
> alone I know of WTL, ATL, MFC, OWL, VCL, wxWindows, QT, and no doubt
others
> about which I have no kn
--- Rene Rivera <[EMAIL PROTECTED]>
wrote:
> [2003-08-01] E. Gladyshev wrote:
>
> >> Are you aware that the pImpl idiom is used for
> many
> >> different things
> >
> >It defenitly has its place but not in modern C++.
>
> Could you do us the courtesy of indicating who you
> are quoting when you
[2003-08-01] E. Gladyshev wrote:
>> Are you aware that the pImpl idiom is used for many
>> different things
>
>It defenitly has its place but not in modern C++.
Could you do us the courtesy of indicating who you are quoting when you post
to the list. It's very hard to follow otherwise. Not to me
> Are you aware that the pImpl idiom is used for many
> different things
It defenitly has its place but not in modern C++.
> or have
> you just decided its not modern C++ at all because
> you don't use it for the
> things you want to do ?
In my opinion modern C++ is more oriented toward
program
E. Gladyshev wrote:
>> Not quite. pImpl is really bad when you have
>> multiple interacting
>> concrete types. I think you'll find yourself doing
>> a lot of
>> polymorphic_downcast<>s.
>
> Another good point against the pImpl idiom. I'd
> suggest to overwrite some of the boost libaries that
> u
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> On Behalf Of Gregory Colvin
> Sent: Tuesday, July 29, 2003 4:25 PM
> To: Boost mailing list
> Subject: Re: [boost] Re: Re: GUI/GDI template library
>
[...]
>
> Yes, you might. But I
On Tuesday, Jul 29, 2003, at 16:02 America/Denver, Brock Peabody wrote:
On Behalf Of Gregory Colvin
[...]
For this kind of localization loading the localized resources at
runtime
is essential. Regenerating C++ code and rebuilding the application is
not an option.
Why would it be necessary to rel
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> On Behalf Of Gregory Colvin
> Sent: Tuesday, July 29, 2003 3:39 PM
> To: Boost mailing list
> Subject: Re: [boost] Re: Re: GUI/GDI template library
[...]
> For this kind of localization
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> On Behalf Of Bohdan
> Sent: Tuesday, July 29, 2003 4:10 PM
> To: [EMAIL PROTECTED]
> Subject: [boost] Re: Re: GUI/GDI template library
>
[...]
> 1. i'm 99% sure that plain
>
On Tuesday, Jul 29, 2003, at 16:24 America/Denver, Bohdan wrote:
"Brock Peabody" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
On Tuesday, Jul 29, 2003, at 12:25 America/Denver, Brock Peabody
wrote:
...
I don't think custom resource files would be any easier to edit that
inline C++ c
"Brock Peabody" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> > On Behalf Of Gregory Colvin
> > Sent: Tuesday, July 29, 2003 1:15 PM
> > To: Boost mailing list
> > Subject: Re: [boost] Re: GU
"Brock Peabody" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> > 1. Resouce files can be easily edited by hand, contrary to
> "inline"
> > GUI-building code.
>
> I don't think custom resource files would be any easier to edit that
> inline C++ code. I think they woul
"Brock Peabody" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> > 1. Resouce files can be easily edited by hand, contrary to
> "inline"
> > GUI-building code.
>
> I don't think custom resource files would be any easier to edit that
> inline C++ code. I think they woul
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> On Behalf Of Bronek Kozicki
> Sent: Tuesday, July 29, 2003 3:40 AM
> To: Boost mailing list
> Subject: Re: [boost] Re: Re: GUI/GDI template library
>
> E. Gladyshev <[EMAIL PROTECT
E. Gladyshev <[EMAIL PROTECTED]> wrote:
> GUI objects generate events. What is the best design
> for it? Should the events handlers be executed
I do not know what is best design, but here's what I think about it:
- each "window" (or almost each - may it be widget, edit box, dialog,
data view, or
E. Gladyshev <[EMAIL PROTECTED]> wrote:
> ** Option 1 (compile-time structure)
> typedef std::list< boost::entry std::string> > listbox;
I like it. More compile time information > better type safety, and more
space for user "plugins" (ie. template parameters) or future standard
library enhancemen
> typedef std::list< boost::container boost::gui::fast_signals> >
> mylistbox;
As for the signals.
GUI objects generate events. What is the best design
for it? Should the events handlers be executed
asynchronously in the context of some internal thread
or should they be something like a message
> I personnally prefer seeing something similar to:
>
> typedef std::list< boost::entry std::string> > listbox;
>
I think the basic issue here is this.
Should we expose the gui structure as a set of direct
STL data types or should we define separate GUI data
types that will behave like the STL
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> On Behalf Of Philippe A. Bouchard
> Sent: Monday, July 28, 2003 6:08 AM
> To: [EMAIL PROTECTED]
> Subject: [boost] Re: Re: GUI/GDI template library
>
[...]
> By the way, this should
Philippe A. Bouchard wrote:
[...]
> Because you have more control over individual listbox' entries. Take for
> example MS Excel. It is a spread sheet (list< list< entry std::string> > >) with different popups on each entry, depending on its
> data type and other user-defined conditions.
In fac
Bronek Kozicki wrote:
[...]
> Uh. I would not recommend inheriting from STL. I think that template
> policies would be rather more appropriate solution:
Agreed.
> typedef boost::gui::list,
> boost::gui::win32::listbox, boost::gui::fast_signals> mylistbox;
I personnally prefer seeing something
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Edward Diener
Sent: Friday, July 25, 2003 7:17 PM
To: [EMAIL PROTECTED]
Subject: [boost] Re: Re: GUI/GDI template library
> I am not trying to discourage you on working on such a project but
> Your notes made me think of a consistent
> reperesentation of state machines in terms of C++
> templates. It should be generic enough to be used in
> all sorts of things.
>
yes. andreas (huber) has something in the pipeline. its a
non-trivial thing though (the topic and the library). i
suspect
Hi,
On Saturday 26 July 2003 04:27, E. Gladyshev wrote:
> It was not exactly my experience. The ammount of code
> just to manage the GUI states and data transfer
> between GUI structures and internal application
> reperesentations is huge.
I agree with this, but I don't think that an STL like i
[...]
> I am not trying to discourage you on working on such
> a project but the
Thanks for your comments.
Don't worry, this is why I posted it here, to hear
what other people think.
[...]
> works for Windows, Linux,
> Unix flavors, MacIntosh, VMS, OS2, and whatever else
> OSs Boost supports.
Th
E. Gladyshev wrote:
>> Microsoft has a Windows Template Library, WTL, for
>> Windows specifically,
>> which is template-based but which they barely
>> support for their VC++ users.
>
> The main point of the proposed library is not a
> wrapper. WTL is just a Win32 wrapper.
> The main idea is to sim
35 matches
Mail list logo
