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

   Vyššie na [Platon] / phpMyEdit / doc / sgml
Rozdiely pre phpMyEdit/doc/sgml/configuration.general.sgml medzi verziami 1.25 a 1.26


verzia 1.25, 2003/03/31 00:12:42
verzia 1.26, 2003/04/05 20:32:05



Riadok 1 




Riadok 1 




 <!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.24 2003/03/30 21:44:42 nepto Exp $ -->
 <!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.25 2003/03/31 00:12:42 nepto Exp $ -->


 
 


 <sect1 id="configuration.mysql-options">
 <sect1 id="configuration.mysql-options">


 <title id="configuration.mysql-options.title">Database connection</title>
 <title id="configuration.mysql-options.title">Database connection</title>




Riadok 436  $opts['filters'] = 'Table0.sessions_coun




Riadok 436  $opts['filters'] = 'Table0.sessions_coun




 </example>
 </example>


 
 


 </para>
 </para>


 
 <para>


 
 


 
 For future is planned initialization like the following one.


 
 


 
 <programlisting><![CDATA[


 
 $opts['filters'] = array(


 
         'col_name_1' => 'value_1',


 
         'col_name_2' => 'value_2'


 
 );


 
 ]]></programlisting>


 
 


 
 The main advantage of this approach will be that <varname>col_name_1</> and


 
 <varname>col_name_2</> fields are automatically considered as read-only on


 
 display record pages with pre-set <constant>value_1</>, <constant>value_2</>


 
 and without need to enter them manually.


 
 


 
 </para>


 </sect1>
 </sect1>


 
 


 <sect1 id="configuration.triggers">
 <sect1 id="configuration.triggers">




Riadok 707  advanced and experienced users using &na




Riadok 724  advanced and experienced users using &na




 projects. If you do not understand what does this thing do, feel free to skip
 projects. If you do not understand what does this thing do, feel free to skip


 it. You will surely do not need it.
 it. You will surely do not need it.


 
 


 
 <example><title>Persistent CGI variables</title>


 
 <programlisting><![CDATA[


 
 $opts['cgi']['persist'] = array(


 
                 'article_id' => $article_id,


 
                 'session_id' => $SESSION_ID


 
                 );


 
 ]]></programlisting></example>


 
 


 </para>
 </para>


 </sect1>
 </sect1>


 
 


 <sect1 id="configuration.css-classes-policy">
 <sect1 id="configuration.css">


 <title id="configuration.css-classes-policy.title">CSS classes policy</title>
 <title id="configuration.css.title">CSS classes policy</title>


 
 <para>


 
 


 
 CSS classes policy in &name; is one from the most complicated and complex


 
 features. The goal is to reach almost any possible classification of HTML


 
 elements with possibility to simplify classification to lower number of


 
 classes.


 
 


 
 </para>


 
 <para>


 
 


 
 The phpMyEdit CSS class schema is displayed here:


 
 


 
 <example><title>CSS class name schema</title>


 
 <programlisting><![CDATA[


 
 <prefix>-<element>-<page_type>-<position>-<dividor>-<postfix>


 
 ]]></programlisting></example>


 
 </para>


 
 <para>


 
 


 
 Particular parts are described here:


 
 


 
 <itemizedlist spacing=compact>


 
 <listitem><para>


 
 The <varname>prefix</> part is straighforward. Every &name; CSS class has user


 
 configurable prefix. It can be empty.


 
 </para></listitem>


 
 <listitem><para>


 
 The <varname>element</> represent the name or type of element.  The examples


 
 are <varname>form</>, <varname>row</>, <varname>value</>, <varname>input</>


 
 and others.


 
 </para></listitem>


 
 <listitem><para>


 
 For design distinguish between various types of pages there is


 
 <varname>page_type</> present. The possible values for this part are


 
 <varname>add</>, <varname>view</>, <varname>change</>, <varname>copy</>,


 
 <varname>delete</>.  This part is empty for table listing and table filtering


 
 pages.


 
 </para></listitem>


 
 <listitem><para>


 
 There are also some elements, which occurs on the top and on the bottom of


 
 page as well. For this matter there is <varname>position</> part present with


 
 possible values <varname>up</> and <varname>down</>.


 
 </para></listitem>


 
 <listitem><para>


 
 The <varname>dividor</> aim is to provide difference between even and odd


 
 table listing rows. This part, if present, is always numeric with values


 
 starting from <constant>0</>.


 
 </para></listitem>


 
 <listitem><para>


 
 At the end of CSS class name is <varname>postfix</> part located. This part is


 
 related to particular field. Every field can have its own postfix. See field's


 
 <xref linkend="configuration.fields.css" endterm="configuration.fields.css">


 
 for more information.


 
 </para></listitem>


 
 <listitem><para>


 
 The separator between parts is by default dash (<constant>-</>) and can be


 
 changed if desired.


 
 </para></listitem>


 
 </itemizedlist>


 
 


 
 </para>


 
 <para>


 
 


 
 CSS class names configuration is handle via <varname>$opts['css']</>


 
 associative array. Here follows possible configuration options related to this


 
 issue.


 
 


 
 </para>


 <para>
 <para>


 
 


 <simplelist type=horiz columns=2>
 <simplelist type=horiz columns=2>


 <member><varname>$opts['css']['prefix']</></>
 <member><varname>$opts['css']['prefix']</></>


 <member> &nbsp; prefix of every &name; CSS class ("pme" by default)</>
 <member> &nbsp; prefix of every &name; CSS class (<constant>pme</> by default)</>


 <member><varname>$opts['css']['page_type']</></>
 <member><varname>$opts['css']['page_type']</></>


 <member> &nbsp; if page type should occur in class name (disabled by default)</>
 <member> &nbsp; if page type should occur in class name (disabled by default)</>


 <member><varname>$opts['css']['position']</></>
 <member><varname>$opts['css']['position']</></>


 <member> &nbsp; if possition on the page should occur in class name (enabled by default)</>
 <member> &nbsp; if possition on the page should occur in class name (disabled by default)</>


 <member><varname>$opts['css']['dividor']</></>
 <member><varname>$opts['css']['dividor']</></>


 <member> &nbsp; how many list table rows should have own number before
 <member> &nbsp; how many list table rows should have own number before


 starting counting again from 0 (by default 2; value of -1 means every row has
 starting counting again from <constant>0</> (by default <constant>2</>; value


 its own number and value of 0 means disabled)</>
 of <constant>-1</> means every row has its own number and value of


 
 <constant>0</> means disabled)</>


 <member><varname>$opts['css']['separator']</></>
 <member><varname>$opts['css']['separator']</></>


 <member> &nbsp; separator between CSS class name elements ("-" (dash) by default)</>
 <member> &nbsp; separator between CSS class name elements (dash <constant>-</> by default)</>


 </simplelist>
 </simplelist>


 
 


 </para>
 </para>


 
 <para>


 
 


 
 For concrete names of CSS classes look into HTML source code of your generated


 
 page. In the following box are examples how CSS class names may looks like.


 
 However your CSS class names can differ according to your fields and


 
 configuration appropriatelly.


 
 


 
 <example><title>CSS class name examples</title>


 
 <programlisting><![CDATA[


 
 pme-navigation-up


 
 pme-row-0


 
 pme-cell-DateTime


 
 pme-cancel-view


 
 pme-input-change


 
 pme-key-ArticleID


 
 ]]></programlisting></example>


 
 


 
 </para>


 </sect1>
 </sect1>


 
 


 <!--
 <!--









Legend:


Odstranené z verzie1.25
 


zmenené riadky


 
Pridané vo verzii1.26


















Platon Group <platon@platon.sk> http://platon.sk/
  Vyššie na [Platon] / phpMyEdit / doc / sgml
-verzia 1.25, 2003/03/31 00:12:42
+verzia 1.26, 2003/04/05 20:32:05
 Riadok 1
 Riadok 1
 Riadok 1
- <!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.24 2003/03/30 21:44:42 nepto Exp $ -->
+ <!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.25 2003/03/31 00:12:42 nepto Exp $ -->
  <sect1 id="configuration.mysql-options">
  <title id="configuration.mysql-options.title">Database connection</title>
 Riadok 436  $opts['filters'] = 'Table0.sessions_coun
 Riadok 436  $opts['filters'] = 'Table0.sessions_coun
 Riadok 436  $opts['filters'] = 'Table0.sessions_coun
  </example>
  </para>
+ <para>
+ For future is planned initialization like the following one.
+ <programlisting><![CDATA[
+ $opts['filters'] = array(
+         'col_name_1' => 'value_1',
+         'col_name_2' => 'value_2'
+ );
+ ]]></programlisting>
+ The main advantage of this approach will be that <varname>col_name_1</> and
+ <varname>col_name_2</> fields are automatically considered as read-only on
+ display record pages with pre-set <constant>value_1</>, <constant>value_2</>
+ and without need to enter them manually.
+ </para>
  </sect1>
  <sect1 id="configuration.triggers">
-Riadok 707  advanced and experienced users using &na
+Riadok 724  advanced and experienced users using &na
 Riadok 707  advanced and experienced users using &na
 Riadok 724  advanced and experienced users using &na
  projects. If you do not understand what does this thing do, feel free to skip
  it. You will surely do not need it.
+ <example><title>Persistent CGI variables</title>
+ <programlisting><![CDATA[
+ $opts['cgi']['persist'] = array(
+                 'article_id' => $article_id,
+                 'session_id' => $SESSION_ID
+                 );
+ ]]></programlisting></example>
  </para>
  </sect1>
- <sect1 id="configuration.css-classes-policy">
+ <sect1 id="configuration.css">
- <title id="configuration.css-classes-policy.title">CSS classes policy</title>
+ <title id="configuration.css.title">CSS classes policy</title>
+ <para>
+ CSS classes policy in &name; is one from the most complicated and complex
+ features. The goal is to reach almost any possible classification of HTML
+ elements with possibility to simplify classification to lower number of
+ classes.
+ </para>
+ <para>
+ The phpMyEdit CSS class schema is displayed here:
+ <example><title>CSS class name schema</title>
+ <programlisting><![CDATA[
+ <prefix>-<element>-<page_type>-<position>-<dividor>-<postfix>
+ ]]></programlisting></example>
+ </para>
+ <para>
+ Particular parts are described here:
+ <itemizedlist spacing=compact>
+ <listitem><para>
+ The <varname>prefix</> part is straighforward. Every &name; CSS class has user
+ configurable prefix. It can be empty.
+ </para></listitem>
+ <listitem><para>
+ The <varname>element</> represent the name or type of element.  The examples
+ are <varname>form</>, <varname>row</>, <varname>value</>, <varname>input</>
+ and others.
+ </para></listitem>
+ <listitem><para>
+ For design distinguish between various types of pages there is
+ <varname>page_type</> present. The possible values for this part are
+ <varname>add</>, <varname>view</>, <varname>change</>, <varname>copy</>,
+ <varname>delete</>.  This part is empty for table listing and table filtering
+ pages.
+ </para></listitem>
+ <listitem><para>
+ There are also some elements, which occurs on the top and on the bottom of
+ page as well. For this matter there is <varname>position</> part present with
+ possible values <varname>up</> and <varname>down</>.
+ </para></listitem>
+ <listitem><para>
+ The <varname>dividor</> aim is to provide difference between even and odd
+ table listing rows. This part, if present, is always numeric with values
+ starting from <constant>0</>.
+ </para></listitem>
+ <listitem><para>
+ At the end of CSS class name is <varname>postfix</> part located. This part is
+ related to particular field. Every field can have its own postfix. See field's
+ <xref linkend="configuration.fields.css" endterm="configuration.fields.css">
+ for more information.
+ </para></listitem>
+ <listitem><para>
+ The separator between parts is by default dash (<constant>-</>) and can be
+ changed if desired.
+ </para></listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ CSS class names configuration is handle via <varname>$opts['css']</>
+ associative array. Here follows possible configuration options related to this
+ issue.
+ </para>
  <para>
  <simplelist type=horiz columns=2>
  <member><varname>$opts['css']['prefix']</></>
- <member> &nbsp; prefix of every &name; CSS class ("pme" by default)</>
+ <member> &nbsp; prefix of every &name; CSS class (<constant>pme</> by default)</>
  <member><varname>$opts['css']['page_type']</></>
  <member> &nbsp; if page type should occur in class name (disabled by default)</>
  <member><varname>$opts['css']['position']</></>
- <member> &nbsp; if possition on the page should occur in class name (enabled by default)</>
+ <member> &nbsp; if possition on the page should occur in class name (disabled by default)</>
  <member><varname>$opts['css']['dividor']</></>
  <member> &nbsp; how many list table rows should have own number before
- starting counting again from 0 (by default 2; value of -1 means every row has
+ starting counting again from <constant>0</> (by default <constant>2</>; value
- its own number and value of 0 means disabled)</>
+ of <constant>-1</> means every row has its own number and value of
+ <constant>0</> means disabled)</>
  <member><varname>$opts['css']['separator']</></>
- <member> &nbsp; separator between CSS class name elements ("-" (dash) by default)</>
+ <member> &nbsp; separator between CSS class name elements (dash <constant>-</> by default)</>
  </simplelist>
  </para>
+ <para>
+ For concrete names of CSS classes look into HTML source code of your generated
+ page. In the following box are examples how CSS class names may looks like.
+ However your CSS class names can differ according to your fields and
+ configuration appropriatelly.
+ <example><title>CSS class name examples</title>
+ <programlisting><![CDATA[
+ pme-navigation-up
+ pme-row-0
+ pme-cell-DateTime
+ pme-cancel-view
+ pme-input-change
+ pme-key-ArticleID
+ ]]></programlisting></example>
+ </para>
  </sect1>
  <!--
 Legend:


Odstranené z verzie1.25
 


zmenené riadky


 
Pridané vo verzii1.26
 Legend:


Odstranené z verzie1.25
 


zmenené riadky


 
Pridané vo verzii1.26
-Odstranené z verzie1.25
+Pridané vo verzii1.26


Copyright © 2002-2006 Platon Group Stránka používa redakčný systém Metafox	Na začiatok