Re: [kyoryoku] Qtonium]

[Toni Alatalo]

Ryan McDougall kirjoitti:

>> >> others, so here it is as a separate project: Qtonium (the name obviously
>> >> being inspired by Awesomium and Berkelium ;)
>> >>
>>

Yay!

This is exactly the way: let's make reusable components in the different
projects. We have a c++ written prim mesher (port) at least to offer :p

And compatible APIs so that we can use the same components in many of
the applications. Luckily many APIs are also given to us largely, like
when using Qt and Python.


>> >> with good performance. Other details: Mouse clicks work, but seem to be very
>> >> slightly 'off' in their position. Key presses are sent but currently don't
>> >> work for some reason. Tested on Linux, but should work on any platform.
>> >>
>>

Btw, we have working in-world / on-object-as-texture interactive qt
canvases in Naali trunk, as of last week. IIRC mouse clicks etc work ok.
And have been using qt webviews on 2d surfaces since the beginning
basically, for login ui.


>> >> Code is triple-licensed under: Apache 2.0, GPL 3+, AGPL3+.
>> >> - kripken
>> >>
>>
> >
> > Excellent! We should totally pick this up!
> >
>

Seconded. I didn't take a closer look yet, but am certainly curious how this
will end up.

BTW the Qt integration we are using is PythonQt, which is different from
PyQt and PySide. I haven't yet looked into the interoperabilities of
those, but the APIs are of course now very far off (the basic diff is
that PythonQt is bsd-like, for embedding in c++ qt apps, whereas PyQt
(gpl) and PySide (new bsd-like rewrite of PyQt by Nokia) are for making
full qt applications in Python (instead of using c++ necessarily).

It seems that Qtonium is PyQt, so perhaps the time to study
interoperability comes soon. It might be also possible to use PyQt in
Naali when GPL is suitable, we haven't tested that (have just used PyQt
for separate apps, like when developing the webdav inventory module that
is in use in Naali via PythonQt now).


> > Cheers
>

~Toni

[Toni Alatalo]

Toni Alatalo kirjoitti:

> BTW the Qt integration we are using is PythonQt, which is different from
> PyQt and PySide. I haven't yet looked into the interoperabilities of
> those, but the APIs are of course now very far off (the basic diff is
>

Graah, sorry for proofreading only after had posted in haste: tried to
say *not* very far off, thinking that it is the same qt underneath
anyways. And given the duck typing in py it's usually easy enough to
hack code to work in a different env than what it was written in.

> ~Toni
>

Same, apologizing.