HQK: Difference between revisions

From HaskellWiki
(creation of initial content)
 
m (link correction)
Line 1: Line 1:
HQK is an effort to provide Haskell bindings to large parts of the Qt and KDE libraries. As of October 2008, we are developing a generator which shall produce most of the binding code automatically. In addition, we have developed [http://softbase.org/hqk/doc/qoo.pdf a small Haskell module] for accessing object-oriented libraries in a convenient way. This module also supports parts of Qt’s signal-slot mechanism. In contrast to the original C++-based solution, type correctness of signal-slot connections is checked at compile time with our library.
HQK is an effort to provide Haskell bindings to large parts of the Qt and KDE libraries. As of October 2008, we are developing a generator which shall produce most of the binding code automatically. In addition, we have developed [http://softbase.org/hqk/qoo/ a small Haskell module] for accessing object-oriented libraries in a convenient way. This module also supports parts of Qt’s signal-slot mechanism. In contrast to the original C++-based solution, type correctness of signal-slot connections is checked at compile time with our library.


We plan to develop a HQK GUI backend for the Functional Reactive Programming library [[Grapefruit]], thereby making Grapefruit multi-platform.
We plan to develop a HQK GUI backend for the Functional Reactive Programming library [[Grapefruit]], thereby making Grapefruit multi-platform.

Revision as of 14:03, 7 October 2008

HQK is an effort to provide Haskell bindings to large parts of the Qt and KDE libraries. As of October 2008, we are developing a generator which shall produce most of the binding code automatically. In addition, we have developed a small Haskell module for accessing object-oriented libraries in a convenient way. This module also supports parts of Qt’s signal-slot mechanism. In contrast to the original C++-based solution, type correctness of signal-slot connections is checked at compile time with our library.

We plan to develop a HQK GUI backend for the Functional Reactive Programming library Grapefruit, thereby making Grapefruit multi-platform.