Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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

    • 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