- Subject: RE: fljed: question about menus
- From: SANGOI DINO <SANGOID@xxxxxxxxxxxxxxxxx>
- Date: Tue, 22 Feb 2005 17:41:32 +0100
> -----Original Message-----
> From: Marko Mahnic [mailto:marko.mahnic@xxxxxxxx]
> Sent: martedì 22 febbraio 2005 14.42
> Subject: fljed: question about menus
>
> Hello!
>
> I am working on the native FLTK menus for fljed. I have
> implemented the basic functions to build the menus with just
> one minor modification to the existing jedlib files
> (evalfile("popups.sl") in jedrc).
>
> My question is this: if I am able to make the fljed menus
> behave pretty much like the text-mode menus, should fljed use
> only the native menus or should it also have support for
> text-mode menus?
>
> One thing that would be hard (but not impossible) to
> implement in native menus is invoking menus from within a
> recorded keyboard macro.
My 2c are:
- If you can implement native menus with the same (programming) interface of
standard (text-mode) menus, go for it.
- Recorded macros may or may not be a big problem. I don't use macros that
much, if I have some repetitive task to do, I write a slang script :))
- As Guenter has already asked, compatibile configuration and interaction
with slang script is much more important: This is why I hate custom Windows
menus: those have a completely separated configuration and API.
- Keeping the old text mode menus should be easy: all the code is already
there.
IMHO, jed should call menu functions through pointers, like already does for
tt_* functions. This way different frontends can have a custom
implementation.
Ciao,
Dino
--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.
[2005 date index]
[2005 thread index]
[Thread Prev] [Thread Next]
[Date Prev] [Date Next]