use Perl

• Another idea on context, for menus and buttons (Score:2)

  by bart (450)

  Here's another thing that I don't remember actually having seen on an editor yet — or at least, on a free or cheap editor — I don't actually know if Kephra does: let the tool buttons and menu entries depend on the type of file.

  It removes clutter if you don't show any menu entries that don't make sense on this type of file.

  For example, if you have the Java compiler (javac) defined as a tool, it makes no sense to show it as an option for a Perl script. And vice versa: show perl only as a tool for
  • Re:Another idea on context, for menus and buttons (Score:1)

    by sir_lichtkind (5541) on 2009.12.10 8:10 (#71366) Homepage Journal

    yes its the next logical step. the technical basis for that is there and it doesn't sound that challenging to me. Now menu items deactivate (turn into a shadow) if the enable call say no (aka 0 aka '' :) ) and this calls are checked before the menu popup. because on windows this event is fired on any menu popup of the main menu, i currently thinking about to change the enabling and toggle items if the content changing event was triggered. its not a too large change because currently the Kephra::Menu lib can do a lot of dynamic and flexible stuff. just hiding items is a nice idea i just have to test it on a small prototype but it doesnt make that much sense now, because there arent that much things that get disabled.
    
    the other thing you wrote about are menus for special syntax modes. padre already does it and kephra will also have it after 0.5. we currently build some features that are pretty basic and urgently needed in Kephra. but after that i have planned to introduce syntax modes, that go beyong highlighting. its about what comment chars belong to that language and what tools and so on and then you will get such dynamic menu. its all already working in my head. you just have to download it and run the brain2perl.pl. :)

    Reply to This

    Parent