Commits

Herbert Breunung  committed ee7d72c

re arrange doc texts

  • Participants
  • Parent commits a438d2c
  • Branches sp3

Comments (0)

Files changed (5)

File doc/.DS_Store

Binary file added.

File doc/Plan.txt

Empty file removed.

File doc/Sanddrum.pod

-=head1 Sandrum
-
-=head2 SYNOPSIS
-
-language of the Kephra command line
-
-=head2 Main Idea
-
-The best thing about vi is the way to control the editor with short comands,
-that get typed into a seperate line.
-For complex operations is this the fastest way to get thigs done.
-Thats because each latter can open a new context.
-This way you can stuff much more commands onto the keayboard.
-Also the the options of each command multiply the into the unimaginable,
-if you just think in terms of point and click or simple key combinations
-
-Why not Perl? All commands would be much longer/complicated.
-But its also possible. In a different command line just one tab away.
-
-=head2 Name
-
-Kephra, depicted as a scarab is a desert beatle. 
-For communication the beat the sand, making low frequency sound signals.
-
-
-=head2 Command Overview
-
-  .       -     repeat last action
-  /../    -     match / find
-  /../../ -     substitute
-  g/d     -     goto line number /d stands for number (regex syntax)
-  gb      -     goto [docs] beginning
-  ge      -     goto        end
-  gs/w    -     goto sub name = /w
-  gd.     -     goto doc nr (/d) or name(/w)
-  dw      -     delete word
-  dl      -     delete line
-  cw      -     copy word
-  cl      -     copy line
-  cs      -     copy selection
-  sa      -     select all
-  u       -     undo
-  r       -     redo

File lib/Kephra/Internals.pod

 =head2 Kephra::API
 
 The module Kephra::API is the best starting point to understand the inner workings.
-It's one design goal and purpose of this file, because it naturally gives an
-overview of the most important functions and values and there origin. From here
-you can step to the other major interfaces that are included there with C<use>
-in the first lines.
+That's actually one design goal and purpose of this file, because it gives an
+overview to the most important functions and values and there origin. From there
+you can step to the other major interfaces that are included with C<use> in the
+first lines.
 
 But more vitally it decouples many cross module calls and allows to change things
 under the hood during smaller release cycles. As long as the first version number
 
 =head1 Document
 
+=head2  Interdependency Of Core Modules
+
+=head2  Modules vs Objects
+
+=head2  Boot Stages
+
+Just using the fact that when modules are loded (after the fork)
+there main code (outside the sub) is run. At this time we create the
+basic command list and the definition which module gets which part of
+the global config (actual loading happens later).
+
+=head2  Worker Fork
+
+
 =cut
 
-__END__
-
-our @needed_at_first = qw/App API/;
-our @starttime_loaded_modules = qw/
-	App App::Util API Config Config::Default Config::File
-	Document DocumentStash CommandList Edit EventTable 
-	File KeyMap PluginRegistrar SanddrumInterpreter Works/;
-our @runtime_loaded_namespaces =
-	qw/App::Dialog Config::Default/;
-
-our @command_modules = 
-	qw/App App::Panel::Editor App::Panel::FileBrowser App::Panel::IOUnit
-	App::Panel::OrgPad App::Panel::ProjectManager App::Panel::SratchSheet
-	App::Panel::TextLab App::Panel::TreeLib
-	CommandList Config 
-	Edit File EventTable KeyMap PluginRegistrar SanddrumInterpreter/;
-our @oop_interfaces = 
-	qw/App::Editor App::Panel App::Splitter App::SidePanelController 
-	   App::Bar::Document Document/;

File lib/Kephra/Sanddrum.pod

+=head1 Sandrum
+
+=head2 SYNOPSIS
+
+language of the Kephra command line
+
+=head2 Main Idea
+
+The best thing about vi is the way to control the editor with short comands,
+that get typed into a seperate line.
+For complex operations is this the fastest way to get thigs done.
+Thats because each latter can open a new context.
+This way you can stuff much more commands onto the keayboard.
+Also the the options of each command multiply the into the unimaginable,
+if you just think in terms of point and click or simple key combinations
+
+Why not Perl? All commands would be much longer/complicated.
+But its also possible. In a different command line just one tab away.
+
+=head2 Name
+
+Kephra, depicted as a scarab is a desert beatle. 
+For communication the beat the sand, making low frequency sound signals.
+
+
+=head2 Command Overview
+
+  .       -     repeat last action
+  /../    -     match / find
+  /../../ -     substitute
+  g/d     -     goto line number /d stands for number (regex syntax)
+  gb      -     goto [docs] beginning
+  ge      -     goto        end
+  gs/w    -     goto sub name = /w
+  gd.     -     goto doc nr (/d) or name(/w)
+  dw      -     delete word
+  dl      -     delete line
+  cw      -     copy word
+  cl      -     copy line
+  cs      -     copy selection
+  sa      -     select all
+  u       -     undo
+  r       -     redo