[texworks] Script: Questions about the API
Stefan Löffler
st.loeffler at gmail.com
Tue Apr 20 07:13:32 CEST 2010
Hi,
Am 2010-04-19 03:11, schrieb Jonathan Kew:
> As for allowing scripts to present richer UI than the few simple dialogs that are currently available, there is an alternative approach we could explore. This is to use Qt's user interface classes, so that Qt Designer can be used to create a .ui file defining the interface (just like TW's own "native" windows and dialogs). Because all the Qt GUI code is already present in the application, this would add very little "bloat"; we'd just need a thin layer of "glue" code connecting the UI loader and widgets to scripts, rather than pulling in an entire multi-megabyte Web browser engine in order to present a dialog box.
>
> I'd welcome other people's thoughts on this, too.
>
For comparison, I've posted a patch for using QUILoader, .ui files, and
the Qt Designer in general
(http://code.google.com/p/texworks/issues/detail?id=221#c13).
Note that - curiously enough - I just found out that you can embed a
QWebView in the .ui file and it works (for me). This may be related to
the shared Qt build I use on Linux and may not work in the monolithic
official builds, but it's worth a try (and worth to monitor the size of
Tw.exe closely).
This also showed that there still is a bug in Lua - see
http://code.google.com/p/texworks/issues/detail?id=335#c3 for a fix.
-Stefan
More information about the texworks
mailing list