On Sat, Jan 17, 2009 at 1:50 AM, Yigal Chripun <yigal100@gmail.com> wrote:

>>> Question: since D2 now uses the same runtime as tango and that includes the (same) GC, do we still need the wrapper, for D2 code?
>>
>> What do you mean by wrapper? Or you mean extern C++ capabilites of D2? I tried them, and they seem really poor. Besides nobody who I was asking knows when D2 finally stabilise and goes out of beta, tango for example isn't going to be ported to D2 in nearest future.
>
> I was refering to Bill's WeakRef class. In the above quote you can see that he said: "WeakRef Yigal was referring to is just a handy wrapper class for the same GC callback that std.signals uses.  Plus it's compatible with both Phobos and Tango."

The need for the "handy" part doesn't go away.  Just the need for the "compatible" part.

--bb

Katrina Niolet wrote:
> This is exactly correct. Even D2 currently lacks the introspection
> capabilities provided by moc. In addition to providing the code for
> signals/solts moc also provides for things like getting a list of
> enums in a class, converting enum values to and from string
> (technically moc doesn't do this conversion, it just makes it
> possible), a string list of object properties and their types, you
> can even add new signals and slots dynamically at run time (which may
> not even be members of the class that you are declaring them to be a
> slot of). Qt's signal/slot implementation is also thread safe
> (connecting a signal from one thread to a slot in another I mean),
> and provides several options for how a slot actually gets called by a
> signal (directly, via the event loop, etc). This level of
> "dynamic-ness" is what makes bindings to Qt possible in the first
> place.
> [...]
> P.S. You may have guessed this already, but I'm one of the developers
> working on QtD ;-)

I don't know Qt, so if you could do a writeup on exactly what D2 needs to support Qt, that would be most helpful.

On Fri, Jan 16, 2009 at 11:42 AM, Sergey Kovrov <kovrov+digitalmars@gmail.com> wrote:
> That makes me think Qt might be using GDI (DrawEdge, DrawFocusRect, etc.) or Themes API to draw widgets that looks native. But surely they use their own "widget logic".

Actually, you are right, they use the theme API. I was under the wrong impression, so they must be doing something right :).

Take care,
Daniel

Walter Bright Wrote:

> I don't know Qt, so if you could do a writeup on exactly what D2 needs to support Qt, that would be most helpful.

Yep, will do! Give me a few days on this please, I want to make sure I get everything in there.