Looks like Ogitor is looking at Tundra as an inspiration for ideas

[Peter C.]

I just happened to be on the Ogitor forums, and I happened across a recent thread where they are looking at Naali (well, Tundra) for ideas. I figured you guys may want to know about it. I already chimed in with a bit of feedback based on personal analysis of my researching implementing Ogitor as a plugin for Tundra (TL;DR version, I really didn't like how the plugins and the like were completely tied to Qt as a GUI given the history of looking for other GUIs for RealXtend, not to mention my tendency to aim for modularity). It might be nice to chime in over there.

http://forum.ogitor.org/viewtopic.php?f=3&t=1122

Cheers,
Peter

[Jonne Nauha]

Yeah I went a dropped them a line. Looks interesting if they would like to utilize Tundra in their next rewrite!

Best regards,
Jonne Nauha
Meshmoon developer at Adminotech Ltd.

www.meshmoon.com

--
--
http://groups.google.com/group/realxtend-dev
http://wiki.realxtend.org
http://dev.realxtend.org
---
You received this message because you are subscribed to the Google Groups "realXtend-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to realxtend-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Peter C.]

Yeah, I just posted a reply to your response. I wasn't aware of the fact
that 5.1 added Android support, so that beef with Qt got ruled out. I
did notice however what you said about scripting and I have a question.
As per issue 623: https://github.com/realXtend/naali/issues/623 I
thought that Qt's signal and slot implementation didn't play nice with
scripting implementations other than QtScript. I thought that was part
of the reason why Angelscript support got the No-Go.

[Lasse Öörni]

I would not say AngelScript is no-go with Qt, but implementing Qt signal-slot support will be quite some amount of work, and it's on hold due to limited manpower. It would require a similar middle-man implementation as the QScriptEngine does. Using a more straightforward signal-slot library has the potential to make the integration easier, but wiring arbitrary C++ signals to call arbitrary script functions will always be somewhat involved.

- Lasse

[Ali Kämäräinen]

Yes, AngelScript support is most definitely something we want to have in Tundra. Same goes for non-QtScript JavaScript support. 

On Mon, Apr 15, 2013 at 9:53 AM, Lasse Öörni <lasse...@ludocraft.com> wrote:

I would not say AngelScript is no-go with Qt, but implementing Qt signal-slot support will be quite some amount of work, and it's on hold due to limited manpower. It would require a similar middle-man implementation as the QScriptEngine does. Using a more straightforward signal-slot library has the potential to make the integration easier, but wiring arbitrary C++ signals to call arbitrary script functions will always be somewhat involved.

- Lasse