[wx-discuss] wxTNG: compatibility with wx2 API

[Kevin Ollivier]

Hi Stefan,

On Feb 18, 2006, at 7:31 AM, Stefan Csomor wrote:

> Hi
>
>>  Yes, you could do this with wxDC but try doing it with
>> wxWindow (which you don't just use as a local variable but
>> have to use as child/parent of other windows).
>
> it depends on the hooks we'd have between the bridges from wx2 to  
> 3, but
> surely wxWindow and subclasses is the centerpiece and would take quite
> some time.
>
>>
>> SC> >  But, in any case, this is not what I'm after. I want to have a
>> SC> > reasonably fully functional wx3 API soon. We need this
>> to show it
>> SC> > to others, to start advertising it (let's not be afraid of this
>> SC> > word), to propose it for inclusion in boost (if we feel
>> brave) or
>> SC> > next C++ standard (if we feel
>> SC> > crazy) and to attract more people, both users and
>> developers, to it.
>>
>>  You didn't reply to this but the above is really my main
>> concern with your proposal. You may have the best intentions
>> in the world but without being able to show a working wx3
>> program any time soon, we'd have a very hard time going
>> anywhere with it.
>
> The thing is that I don't see that pressure on timing, to have  
> something
> in 12 months that is well thought out and through and cleanly  
> structured
> would not be too late for me, and I'd think this would be  
> achievable if
> 3-4 people could work on it within the constraints that we are all are
> in.

A couple questions:

1) This is really a lot of work before we have a product others could  
use outside of the wx2 backend, so I'm wondering - exactly how much  
impact do you see this total re-write having? i.e. is this something  
you're mostly developing for your own needs/usage, or are you  
primarily concerned with increasing the adoption of wx by the  
developer community?

2) If the latter, why do you see this total re-write as having more  
impact than other possible initiatives for increasing our userbase? -  
e.g. development of better documentation, a much clearer starting  
path for beginners, modernization of existing APIs, and creation of  
some sort of RAD toolset for users.

Thanks,

Kevin

> Best,
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org
> For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: wx-discuss-unsubscribe at lists.wxwidgets.org
For additional commands, e-mail: wx-discuss-help at lists.wxwidgets.org