Query about list_dialog()

[Thorsten Haude]

Hi,

* A.V.Kuznetsov wrote (2007-01-10 14:01):
>Such an approach have advantages: only single dialog_macro() can be maintained
>and developed in future, all improvements of dialog interface (like size of
>dialogs-window and its output position in buffer-window) will be automatically 
>applied to all dialogs.

I agree that the macro language should offer more in terms of Motif
windows, but I'm not so sure about stacking it like this. As long as
full widget handling (ie. including layout management) is not possible
in macros, we should keep with offering pre-made dialogs of certain
types.

An alternative might be something like Motif's work area. We would
keep the current set of dialog, but add a parameter workarea to each
of them. We would then offer composite widgets similar to dialogs
which could be out into these work areas. The dialog's result would
contain an extra parameter containing the work area's result.

You could thus create a string dialog with a list field:
    widget = list_widget(lMessage, list)
    result = string_dialog(sMessage, widget, "OK", "Cancel")

    string = result.string
    button = result.button
    line = result.widget.line


What's really missing are callbacks however.


Thorsten
-- 
Wise men make proverbs, but fools repeat them.
    - Samuel Palmer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.nedit.org/pipermail/discuss/attachments/20070110/96e6c847/attachment-0001.bin