[Phpgroupware-cvs] CVS: sitemgr/doc sitemgr.html,1.2,1.3 sitemgr.lyx,1.2,1.3 sitemgr.pdf,1.2,1.3 sitemgr.sgml,1.2,1.3

[Michael Totschnig <address@hidden>]

Update of /cvsroot/phpgroupware/sitemgr/doc
In directory subversions:/tmp/cvs-serv21316/doc

Modified Files:
        sitemgr.html sitemgr.lyx sitemgr.pdf sitemgr.sgml 
Log Message:
set_block must use a reference to the block argument


Index: sitemgr.html
===================================================================
RCS file: /cvsroot/phpgroupware/sitemgr/doc/sitemgr.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** sitemgr.html        6 Jun 2003 18:38:49 -0000       1.2
--- sitemgr.html        9 Jun 2003 20:20:22 -0000       1.3
***************
*** 1043,1050 ****
  ></DD
  ><DT
! >set_block($block,$produce=False)</DT
  ><DD
  ><P
! >This function is called by the content manager (with $produce=False) and by 
the page generation (with $produce=True) for each content block, so that the 
module knows everything about the block it has to edit or generate (above all 
its context and its arguments). If your module overrides this function, it 
should always call the parent class' set_block function first with 
parent::set_block($block). If you want to configure your module with respect to 
the block, you can do this here. This is also the place where your module 
should add the transformers it needs for generating output. For example:
     </P
  ></DD
--- 1043,1050 ----
  ></DD
  ><DT
! >set_block(&#38;$block,$produce=False)</DT
  ><DD
  ><P
! >This function is called by the content manager (with $produce=False) and by 
the page generation (with $produce=True) for each content block, so that the 
module knows everything about the block it has to edit or generate (above all 
its context and its arguments). If your module overrides this function, it 
should always call the parent class' set_block function first with 
parent::set_block($block,$produce). If you want to configure your module with 
respect to the block, you can do this here. This is also the place where your 
module should add the transformers it needs for generating output. For example:
     </P
  ></DD
***************
*** 1059,1065 ****
  ><PRE
  CLASS="PROGRAMLISTING"
! >function set_block($block) 
  { 
!     parent::set_block($block);
      if ($produce)
      {
--- 1059,1065 ----
  ><PRE
  CLASS="PROGRAMLISTING"
! >function set_block(&#38;$block,$produce=False)
  { 
!     parent::set_block($block,$produce)
      if ($produce)
      {

Index: sitemgr.lyx
===================================================================
RCS file: /cvsroot/phpgroupware/sitemgr/doc/sitemgr.lyx,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** sitemgr.lyx 1 Jun 2003 01:00:39 -0000       1.2
--- sitemgr.lyx 9 Jun 2003 20:20:22 -0000       1.3
***************
*** 1303,1312 ****
  \layout Description
  
! set_block($block,$produce=False) This function is called by the content
   manager (with $produce=False) and by the page generation (with $produce=True)
   for each content block, so that the module knows everything about the block
   it has to edit or generate (above all its context and its arguments).
   If your module overrides this function, it should always call the parent
!  class' set_block function first with parent::set_block($block).
   If you want to configure your module with respect to the block, you can
   do this here.
--- 1303,1312 ----
  \layout Description
  
! set_block(&$block,$produce=False) This function is called by the content
   manager (with $produce=False) and by the page generation (with $produce=True)
   for each content block, so that the module knows everything about the block
   it has to edit or generate (above all its context and its arguments).
   If your module overrides this function, it should always call the parent
!  class' set_block function first with parent::set_block($block,$produce).
   If you want to configure your module with respect to the block, you can
   do this here.
***************
*** 1316,1320 ****
  \layout Code
  
! function set_block($block) 
  \layout Code
  
--- 1316,1320 ----
  \layout Code
  
! function set_block(&$block,$produce=False)
  \layout Code
  
***************
*** 1322,1326 ****
  \layout Code
  
!     parent::set_block($block);
  \layout Code
  
--- 1322,1326 ----
  \layout Code
  
!     parent::set_block($block,$produce)
  \layout Code
  

Index: sitemgr.pdf
===================================================================
RCS file: /cvsroot/phpgroupware/sitemgr/doc/sitemgr.pdf,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
Binary files /tmp/cvsmR99Gd and /tmp/cvsCcXlKi differ

Index: sitemgr.sgml
===================================================================
RCS file: /cvsroot/phpgroupware/sitemgr/doc/sitemgr.sgml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** sitemgr.sgml        6 Jun 2003 18:38:49 -0000       1.2
--- sitemgr.sgml        9 Jun 2003 20:20:22 -0000       1.3
***************
*** 1024,1029 ****
     <varlistentry>
     <term>
! set_block(&dollar;block,&dollar;produce=False)
! </term><listitem><para>This function is called by the content manager (with 
&dollar;produce=False) and by the page generation (with &dollar;produce=True) 
for each content block, so that the module knows everything about the block it 
has to edit or generate (above all its context and its arguments). If your 
module overrides this function, it should always call the parent class' 
set_block function first with parent::set_block(&dollar;block). If you want to 
configure your module with respect to the block, you can do this here. This is 
also the place where your module should add the transformers it needs for 
generating output. For example:
     </para>
  
--- 1024,1029 ----
     <varlistentry>
     <term>
! set_block(&amp;&dollar;block,&dollar;produce=False)
! </term><listitem><para>This function is called by the content manager (with 
&dollar;produce=False) and by the page generation (with &dollar;produce=True) 
for each content block, so that the module knows everything about the block it 
has to edit or generate (above all its context and its arguments). If your 
module overrides this function, it should always call the parent class' 
set_block function first with parent::set_block(&dollar;block,&dollar;produce). 
If you want to configure your module with respect to the block, you can do this 
here. This is also the place where your module should add the transformers it 
needs for generating output. For example:
     </para>
  
***************
*** 1034,1040 ****
    </variablelist>
    <programlisting>
! <![CDATA[function set_block($block) 
  ]]><![CDATA[{ 
! ]]><![CDATA[    parent::set_block($block);
  ]]><![CDATA[    if ($produce)
  ]]><![CDATA[    {
--- 1034,1040 ----
    </variablelist>
    <programlisting>
! <![CDATA[function set_block(&$block,$produce=False)
  ]]><![CDATA[{ 
! ]]><![CDATA[    parent::set_block($block,$produce)
  ]]><![CDATA[    if ($produce)
  ]]><![CDATA[    {