I don't think mcclim would use the widgets provided by qt, so it doesn't need to interface with the object model provided by commonqt. You would just need a way to output things on screen, render fonts and receive input events. Can do that more efficiently with a simple c++ wrapper.
On Tue, Jan 7, 2020 at 12:46 PM Orm Finnendahl orm.finnendahl@selma.hfmdk-frankfurt.de wrote:
Hi,
if QT was regarded as an option, CommonQt would probably be the more obvious choice for a CLIM Backend to avoid multiple layers of abstraction. In addition CommonQt (and Qtools) currently is stuck with Qt4 and I'm not aware there are any efforts to port it to Qt5.
-- Orm
Am Montag, den 06. Januar 2020 um 22:53:35 Uhr (+0100) schrieb Daniel Kochmański:
Hey,
mike thomas writes:
Hi there
I'm not a member of this list - couldn't find how to subscribe - so apologies for directly sending.
you may subscribe here: https://mailman.common-lisp.net/listinfo/mcclim-devel
I just have two questions:
Has consideration been given to basing a back-end on QTools?
No, QTools never came up as a proposed backend. We did consider cross-platform libraries as backends though. I think that the most likely SDL backend will be implemented at some point of time.
Does it have
potential to do the job, or is it better to work directly through native OS capabilities.
I would be surprised if it couldn't do a job. I don't know this library but it seems to be a layer on top of CommonQt which is pretty complete to my knowledge.
Cheers
Mike Thomas
Best regards, Daniel
-- Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland TurtleWare - Daniel Kochmański | www.turtleware.eu
"Be the change that you wish to see in the world." - Mahatma Gandhi