|
From: | Massimiliano Gubinelli |
Subject: | Re: TeXmacs NextStep backend |
Date: | Thu, 14 Mar 2013 01:41:20 +0100 |
Hi, On Mar 14, 2013, at 1:29 AM, Gregory Casamento <address@hidden> wrote:
Nice feature, I didn't know it was possible. However TeXmacs cannot use XIB files since all the GUI elements are generated programmatically from the scheme code. TeXmacs is inspired by Emacs and all the features of the user interface can be reprogrammed on the fly without recompiling. For example menus and toolbars are described by scheme code and we are also developing a full set of widgets which can be used by the user to write his own plugins. An example is the following piece of code (tm-widget (widget4) (centered (resize "200px" "50px" (scrollable (choice (display* answer "\n") '("First" "Second" "Third" "Fourth" "Fifth" "Sixth") "Third"))) ====== (resize "200px" "150px" (choices (display* answer "\n") '("First" "Second" "Third" "Fourth" "Fifth" "Sixth") '("Third" "Fifth"))))) which produces a widget with some fields. To implement this kind of logic we really need auto layout features. Qt has them and things work quite nicely there. I was a bit worried about having to reimplement all that for AppKit but now I found Renaissance and it seems really what I was looking for. Note that we do not aim to being able to produce full blown applications from scheme, just to have simple dialogs (like preferences panes or toolbars) which the users can reprogram at will without having to understand much of the underlying system and in quite natural ways. Massimilano
|
[Prev in Thread] | Current Thread | [Next in Thread] |