Opensource.Platon.SK CVS: phpMyEdit/doc/sgml/extensions.sgml - diff

   Up to  [Platon] / phpMyEdit / doc / sgml
Diff for phpMyEdit/doc/sgml/extensions.sgml between version 1.10 and 1.11


version 1.10, 2003/05/01 21:38:10
version 1.11, 2003/05/12 22:23:36



Line 1 




Line 1 




 <!-- $Platon: phpMyEdit/doc/sgml/extensions.sgml,v 1.9 2003/04/07 00:53:28 nepto Exp $ -->
 <!-- $Platon: phpMyEdit/doc/sgml/extensions.sgml,v 1.10 2003/05/01 21:38:10 nepto Exp $ -->


 
 


 <chapter id="extensions">
 <chapter id="extensions">


 <title id="extensions.title">Extensions</title>
 <title id="extensions.title">Extensions</title>




Line 104  triggers.




Line 104  triggers.




 <para>
 <para>


 
 


 To use this extension you have to include
 To use this extension you have to include


 <filename>extensions/&name;-slide.class.php</filename> file instead of common
 <filename>extensions/&name;-slide.class.php</filename> file and call


 &name; class file.
 <varname>new &name;_slide($opts)</varname> instead of common &name; class


 
 file.


 
 


 </para>
 </para>


 </sect1>
 </sect1>




Line 145  cookies are used for described kind of m




Line 146  cookies are used for described kind of m




 <para>
 <para>


 
 


 To use this extension simply include
 To use this extension simply include


 <filename>extensions/&name;-report.class.php</filename> file instead of common
 <filename>extensions/&name;-report.class.php</filename> file and call


 &name; class file. Extension specific configuration parameters currently do not
 <varname>new &name;_report($opts)</varname> instead of common &name; class


 exist, thus all table columns are allowed to be selected in final report. This
 file. Extension specific configuration parameters currently do not exist, thus


 will surely change in future, because table could have columns that need to be
 all table columns are allowed to be selected in final report. This will surely


 
 change in future, because table could have columns that need to be


 unselectable for final report (such as password column or similar).
 unselectable for final report (such as password column or similar).


 
 


 </para>
 </para>


 </sect1>
 </sect1>


 
 


 
 <sect1 id="extensions.htmlarea">


 
 <title id="extensions.htmlarea.title">&name;-htmlarea</title>


 
 <para>


 
 


 
 &name;-report extension provides support for htmlArea. htmlArea is a free


 
 WYSIWYG editor replacement for &lt;textarea&gt; fields.  For full source code


 
 and documentation, visit <ulink


 
 url="http://www.interactivetools.com/">http://www.interactivetools.com/</ulink>


 
 website.


 
 


 
 </para>


 
 <para>


 
 


 
 htmlArea requires Microsoft Internet Explorer 5.5 or better on Windows to run.


 
 This is because it makes use of some advanced features of IE5.5 that aren't


 
 available in other browsers yet. It is backwards compatible with other


 
 browsers, though. They will get a regular textarea field instead of a WYSIWYG


 
 editor.


 
 


 
 </para>


 
 <para>


 
 


 
 The extension requires a properly installed htmlArea script as it is described


 
 on the metioned website. This extension enables WYSIWYG editing of a textarea


 
 field. In order to use it, you should:


 
 


 
 <orderedlist>


 
 


 
 <listitem>


 
 <para>


 
 


 
 Load htmlArea script in the &lt;head&gt;...&lt;/head&gt; section of


 
 your &name; calling program as described in the htmlArea manual.


 
 


 
 </para>


 
 </listitem>


 
 


 
 <listitem>


 
 <para>


 
 


 
 Call to <filename>&name;-htmlarea.class.php</> instead of


 
 <filename>&name;.class.php</>.


 
 


 
 <example><title>htmlArea extension enabling</title>


 
 <programlisting>


 
 require_once 'extensions/&name;-htmlarea.class.php';


 
 new &name;-htmlarea($opts);


 
 </programlisting>


 
 </example>


 
 


 
 </para>


 
 </listitem>


 
 


 
 <listitem>


 
 <para>


 
 


 
 Add <varname>'html'=>true</> parameter to the textarea field


 
 definition in your &name; calling program.


 
 


 
 <example><title>htmlArea field enabling</title>


 
 <programlisting><![CDATA[


 
 $opts['fdd']['body'] = array(


 
         'name'     => 'Content',


 
         'select'   => 'T',


 
         'options'  => 'ACPVD',


 
         'required' => true,


 
         'textarea' => array(


 
                 'html' => true,


 
                 'rows' => 11,


 
                 'cols' => 81)


 
 );


 
 ]]></programlisting>


 
 </example>


 
 


 
 </para>


 
 </listitem>


 
 </orderedlist>


 
 


 
 </para>


 
 <para>


 
 


 
 This extension is contribution of Ezudin Kurtowich


 
 <email>ekurtovic@ieee.org</email> from Sarajevo.


 
 


 
 </para>


 
 </sect1>


 
 


 </chapter>
 </chapter>


 
 









Legend:


Removed from v.1.10
 


changed lines


 
Added in v.1.11


















Platon Group <platon@platon.org> http://platon.org/
  Up to  [Platon] / phpMyEdit / doc / sgml
-version 1.10, 2003/05/01 21:38:10
+version 1.11, 2003/05/12 22:23:36
 Line 1
 Line 1
 Line 1
- <!-- $Platon: phpMyEdit/doc/sgml/extensions.sgml,v 1.9 2003/04/07 00:53:28 nepto Exp $ -->
+ <!-- $Platon: phpMyEdit/doc/sgml/extensions.sgml,v 1.10 2003/05/01 21:38:10 nepto Exp $ -->
  <chapter id="extensions">
  <title id="extensions.title">Extensions</title>
 Line 104  triggers.
 Line 104  triggers.
 Line 104  triggers.
  <para>
  To use this extension you have to include
- <filename>extensions/&name;-slide.class.php</filename> file instead of common
+ <filename>extensions/&name;-slide.class.php</filename> file and call
- &name; class file.
+ <varname>new &name;_slide($opts)</varname> instead of common &name; class
+ file.
  </para>
  </sect1>
-Line 145  cookies are used for described kind of m
+Line 146  cookies are used for described kind of m
 Line 145  cookies are used for described kind of m
 Line 146  cookies are used for described kind of m
  <para>
  To use this extension simply include
- <filename>extensions/&name;-report.class.php</filename> file instead of common
+ <filename>extensions/&name;-report.class.php</filename> file and call
- &name; class file. Extension specific configuration parameters currently do not
+ <varname>new &name;_report($opts)</varname> instead of common &name; class
- exist, thus all table columns are allowed to be selected in final report. This
+ file. Extension specific configuration parameters currently do not exist, thus
- will surely change in future, because table could have columns that need to be
+ all table columns are allowed to be selected in final report. This will surely
+ change in future, because table could have columns that need to be
  unselectable for final report (such as password column or similar).
  </para>
  </sect1>
+ <sect1 id="extensions.htmlarea">
+ <title id="extensions.htmlarea.title">&name;-htmlarea</title>
+ <para>
+ &name;-report extension provides support for htmlArea. htmlArea is a free
+ WYSIWYG editor replacement for &lt;textarea&gt; fields.  For full source code
+ and documentation, visit <ulink
+ url="http://www.interactivetools.com/">http://www.interactivetools.com/</ulink>
+ website.
+ </para>
+ <para>
+ htmlArea requires Microsoft Internet Explorer 5.5 or better on Windows to run.
+ This is because it makes use of some advanced features of IE5.5 that aren't
+ available in other browsers yet. It is backwards compatible with other
+ browsers, though. They will get a regular textarea field instead of a WYSIWYG
+ editor.
+ </para>
+ <para>
+ The extension requires a properly installed htmlArea script as it is described
+ on the metioned website. This extension enables WYSIWYG editing of a textarea
+ field. In order to use it, you should:
+ <orderedlist>
+ <listitem>
+ <para>
+ Load htmlArea script in the &lt;head&gt;...&lt;/head&gt; section of
+ your &name; calling program as described in the htmlArea manual.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Call to <filename>&name;-htmlarea.class.php</> instead of
+ <filename>&name;.class.php</>.
+ <example><title>htmlArea extension enabling</title>
+ <programlisting>
+ require_once 'extensions/&name;-htmlarea.class.php';
+ new &name;-htmlarea($opts);
+ </programlisting>
+ </example>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add <varname>'html'=>true</> parameter to the textarea field
+ definition in your &name; calling program.
+ <example><title>htmlArea field enabling</title>
+ <programlisting><![CDATA[
+ $opts['fdd']['body'] = array(
+         'name'     => 'Content',
+         'select'   => 'T',
+         'options'  => 'ACPVD',
+         'required' => true,
+         'textarea' => array(
+                 'html' => true,
+                 'rows' => 11,
+                 'cols' => 81)
+ );
+ ]]></programlisting>
+ </example>
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>
+ This extension is contribution of Ezudin Kurtowich
+ <email>ekurtovic@ieee.org</email> from Sarajevo.
+ </para>
+ </sect1>
  </chapter>
 Legend:


Removed from v.1.10
 


changed lines


 
Added in v.1.11
 Legend:


Removed from v.1.10
 


changed lines


 
Added in v.1.11
-Removed from v.1.10
+Added in v.1.11


Copyright © 2002-2006 Platon Group Site powered by Metafox CMS	Go to Top