The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

Changes for version 0.3

  • start to implement session management (demo11, F10 key, start of Text::Editor::Easy objects destruction)

Documentation

An editor written using Text::Editor::Easy module.

Modules

A perl module to edit perl code with syntax highlighting and more.
The module that manages everything that is displayed.
Thread communication mecanism of "Text::Editor::Easy" module.
Object oriented interface to cursor data (managed by "Text::Editor::Easy::Abstract")
Global common data shared by all threads.
Object oriented interface to displays (managed by "Text::Editor::Easy::Abstract"). A display is a screen line. With wrap mode, you can have several displays for a single line on a file.
Management of the data that is edited.
Link between "Text::Editor::Easy::Abstract" and a terminal. Does not actually work.
Link between "Text::Editor::Easy::Abstract" and "Gtk". Does not actually work.
Link between "Text::Editor::Easy::Abstract" and "Tk".
Key functions using object-oriented interface of "Text::Editor::Easy".
Object oriented interface to a file line (managed by "Text::Editor::Easy::Abstract" and "Text::Editor::Easy::File_manager").
Manage various user events on "Text::Editor::Easy" objects.
Execution of macro panel instructions in the "Editor.pl" program.
Redirection of prints coming from the macro panel of the "Editor.pl" program (insertion in a "Text::Editor::Easy" object).
STDOUT and SDTERR redirection when launching a new application from "Editor.pl" program.
Bad named module (initially searching text) : used to answer to user modification in the Eval tab of the Editor.pl program.
Tab simulation with just a Text::Editor::Easy object.
Object oriented interface to screen data (managed by "Text::Editor::Easy::Abstract").
Perl highlighting (will always be limited, perl is too dynamic...). Contexts are still not yet managed.
-
Print management (every print is traced : which thread writes it, what was the thread called for, stack call is also saved). The consequence is that a print should be considered as a long operation. The benefit is that every print is a little more than a print.