QML - new window / gui / coding for Leo?

[Terry Brown]

This thread will need Ville to set it on the right track, I barely know
the names of the technologies, but Qt has been advancing with, quoting
from their site:

Qt Quick

The Qt UI Creation Kit lets you create rich, touch-enabled UIs and
apps...quickly.

* QML - CSS & JavaScript like language, same code base for UI
designers & developers

* Supported by Qt Creator IDE for rapid prototyping and development

* Qt Quick UI runtime - Direct access to native APIs, performance
boost with C++

I think the first bullet is most relevant to Leo. Could we embed this
kind of environment in Leo? Can it be integrated effectively with the
current GUI?

That route might make adding task specific GUIs in Leo quick and easy.

Cheers -Terry

[Edward K. Ream]

On Fri, Sep 16, 2011 at 9:14 AM, Terry Brown <terry_...@yahoo.com> wrote:
> This thread will need Ville to set it on the right track, I barely know
> the names of the technologies, but Qt has been advancing with, quoting
> from their site:
>
>  Qt Quick

I assume that this is a kind of support for iphone-like features.
They will be part of Windows 8 as well:
http://www.youtube.com/watch?v=p92QfWOw88I

It's not clear how Leo could use this technology.

Edward

[Terry Brown]

Not for the touch part (although Leo on a tablet would be fun), but as
a way of quickly creating task specific GUIs, "forms" if you like, for
accessing / interacting with the data in a Leo outline. I'm assuming
that QML is higher level / less coding the regular PyQt programming,
but I don't know that, not having tried it.

Cheers -Terry

[Ville M. Vainio]

On Fri, Sep 16, 2011 at 6:01 PM, Terry Brown <terry_...@yahoo.com> wrote:

> Not for the touch part (although Leo on a tablet would be fun), but as
> a way of quickly creating task specific GUIs, "forms" if you like, for
> accessing / interacting with the data in a Leo outline.  I'm assuming
> that QML is higher level / less coding the regular PyQt programming,
> but I don't know that, not having tried it.

QML is actually lower level than QWidgets / "regular" PyQt
programming. Key selling point of QML is that the UI's are more free
form, "custom" and much faster than QWidget UI's (in Qt5, QML maps
quite naturally to OpenGL, making it fly on mobile phone/tablet
hardware).

QML would be natural for graphcanvas / tabula / other "custom" ui
plugins, but it doesn't yet have text editor as powerful as QTextEdit,
not tree widget as powerful as QTreeWidget / QTreeView.

I expect QML to be first used in mobile version of Leo (I have one
actually, that I will publish "at later date" ;-). For desktop, QML is
not yet as attractive as the "old stuff".

>
> Cheers -Terry
>
> --
> You received this message because you are subscribed to the Google Groups "leo-editor" group.
> To post to this group, send email to leo-e...@googlegroups.com.
> To unsubscribe from this group, send email to leo-editor+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
>
>

[ilkosta]

Only for knoledge, there is also an interesenting possibility in WT (http://www.webtoolkit.eu/wt), a QT-like (often identical api) web framework.
WT that is c++ have bindings in ruby and a mantained reimplementation in java.
I think that the web-interface is the right direction, but although I like this kind of framework,  i think that the route of widget-like framework (like wt) is worse than other web-mv* solutions.