On 11 Dez., 17:05, Gaspard Buma <
a...@gaspardbuma.org> wrote:
> Hi Peter,
>
> I saw this binding very briefly. I am still considering how to encode the
> views (defined on the "server" side but running on the "client"). The
> current options are:
Hi Gaspard,
what do you mean with "defined on server side". As I understand your
architecture, client and server are running in its own process on
maybe
different machines communicating via zeromq. And you wanna make the
server something like a webservice with a special kind of client,
which
is only for viewing the content generated by the server? This sound
very
complicated to me, or is the content of the view not that complex?
> 1. json: easy to "merge" (update some parts of the interface by sending
> partial dictionaries)
Having Lua you don't need JS to package some data.
> 2. qml: native support by Qt made for UI
Have you looked into the QML doc? For me it looks like it is not
usable
for desktop GUIs because you have to define all elements by your own.
I even coudn't find a simple hello world example with a pushbutton.
> 3. lqt: avoids having yet another language, would need to be made "safe" (we
> do not want to run arbitrary code on the client) but that should be pretty
> easy.
As mentiond above, why not coding the views in C++ with help of Qt's
designer?
> For the communication layer between instances and between the server and
> clients, I want to use Lua so there will be at least some lua code running
> in Mimas anyway so that's another incentive on using lqt. My only worry is
> that I need the GUI to be in place really fast and I do not want to spend
> time on Lua bindings on the GUI side (already a lot to do in Rubyk core).
>
> I did not realize at first that you were one of the authors of lqt. If you
> think lqt is a good choice to build the visual elements (or even all of
> Mimas), I'll use this because I like the idea of using Lua for everything.
> My main concern right now is time: I have a show in June and everything must
> work long before this date so I will choose whatever saves me time !
Then I would code the GUI in C++, it's a proven way to produce stable
GUIs in
short times. lqt is maybe interesting for extending existing
functionality.
BTW, recently I read a book about music and mathematics,
and I assume you will also like it:
http://www.maths.abdn.ac.uk/~bensondj/html/maths-music.html
Cheers,
Peter