richter 00/07/16 10:46:26
Modified: embperl Changes.pod.1.html
Log:
Embperl Webpages - Changes
Revision Changes Path
1.160 +16 -3 modperl-site/embperl/Changes.pod.1.html
Index: Changes.pod.1.html
===================================================================
RCS file: /home/cvs/modperl-site/embperl/Changes.pod.1.html,v
retrieving revision 1.159
retrieving revision 1.160
diff -u -r1.159 -r1.160
--- Changes.pod.1.html 2000/07/08 17:10:02 1.159
+++ Changes.pod.1.html 2000/07/16 17:46:26 1.160
@@ -18,7 +18,7 @@
<blockquote>
[<a href="index.html">HOME</a>] [<a
href="Changes.pod.cont.html">CONTENT</a>] [<a
href="Changes.pod.cont.html">PREV (Revision History - Content)</a>] [<a
href="Changes.pod.2.html">NEXT (1.3b3 (BETA) 25.04.2000)</a>] <br><hr>
<P>
-Last Update: Sat Jul 8 19:10:29 2000 (MET)
+Last Update: Sun Jul 16 19:46:50 2000 (MET)
<P>
NOTE: This version is only available via <A HREF="CVS.pod.1.html#INTRO">"CVS"</A>
@@ -48,10 +48,23 @@
work when searching the correct file.
- If import parameter is given to Execute, Perl code is compiled, but
only [! !] blocks are executed (to allow sub definitions on import)
- - New debug flag dbgObjectSearch can be set to see which files
- EmbperlObject picksup and how it searches them.
- Space is converted to %20 instead of +, because that is more generic.
Suggested by Michael Blakely.
+ - EmbperlObject now automaticly defines all subs that are declared
+ inside the base template and inside the requested page, so it isn't
+ neccessary anymore to call Execute with import => 0 for them.
+ - Every Embperl Page now get passed a request object (which can be obtained
+ from $_[0]). The request object is a hash reference which is blessed
+ into the package HTML::Embperl::Req. Embperl itself don't uses the hash, so
+ you are free to populate it and pass data between different pages of one
request.
+ - EmbperlObject now setup the inherence so that
+ request page -ISA->
+ base template -ISA->
+ EMBPERL_OBJECT_HANDLER_CLASS (if defined) -ISA->
+ HTML::Embperl::Req
+ and the Embperl request object is blessed into the packages of the
+ requested page, so you can do methods calls to subs that are defined
+ inside the requested page.
</PRE>
<P>
<PRE>