cvs: phpdoc-it /chapters tutorial.xml

From: Date: Thu, 23 Jan 2003 16:30:45 +0000
Subject: cvs: phpdoc-it /chapters tutorial.xml
Groups: php.doc.it 
Request: Send a blank email to doc-it+get-183@lists.php.net to get a copy of this message
cortesi Thu Jan 23 11:30:45 2003 EDT Added files: /phpdoc-it/chapters tutorial.xml Log: partly translated

Index: phpdoc-it/chapters/tutorial.xml +++ phpdoc-it/chapters/tutorial.xml <?xml version="1.0" encoding="iso-8859-1"?> <!-- EN-Revision: 1.10 Maintainer: cortesi Status: translating --> <chapter id="tutorial"> <title>Una semplice introduzione</title> <para> Di seguito, in una breve e semplice introduzione, vorremmo mostrare alcuni esempi di uso del PHP. Essi sono relativi soltanto alla creazione dinamica di pagine web usando PHP, anche se PHP non ha funzionalità limitate esclusivamente alla creazione delle sole pagine web. Fare riferimento alla sezione intitolata <link linkend="intro-whatcando">Cosa può fare PHP</link> per avere ulteriori informazioni. </para> <para> Pagine web create con PHP vengono trattate cone normali pagine HTML e possono essere create e modifichate nello stesso modo in cui si creano normali pagine HTML. </para> <sect1 id="tutorial.requirements"> <title>Di cosa ho bisogno?</title> <para> In questa introduzione assumiamo che si abbia già a disposizione di un server con supporto per il PHP e che tutti i file con estensione <filename>.php</filename> vengano interpretati correttamente dal PHP. Su molti server questa è l'estensione predefinita per i file PHP, ma è opportuno chiedere al proprio amministratore del server per esserne sicuri. Se si dispone di un server con supporto per il PHP, allora non serve fare null'altro. &Egrave; sufficiente creare i file <filename>.php</filename> e metterli nella directory del proprio server web, a questo punto sarà il server ad occuparsi di eseguirle magicamente per voi. Non c'è necessità di compilare nulla e nemmeno di installare strumenti aggiuntivi. Si pensi ai file PHP come a semplici file HTML che hanno però in aggiunta una nuova famiglia di magici tag che permettono di fare molte cose in più. </para> </sect1> <sect1 id="tutorial.firstpage"> <title>La prima pagina PHP</title> <para> Creare un file con nome <filename>ciao.php</filename> nella directory del web server che abbia il seguente contenuto: </para> <para> <example> <title>Il nostro primo script PHP: <filename>ciao.php</filename></title> <programlisting role="php"> <![CDATA[ <html> <head> <title>Test PHP</title> </head> <body> <?php echo "Ciao Mondo<p>"; ?> </body> </html> ]]> </programlisting> <para> L'output di questo script sarà: <screen role="html"> <![CDATA[ <html> <head> <title>Test PHP</title> </head> <body> Ciao Mondo<p> </body> </html> ]]> </screen> </para> </example> </para> <para> Si noti che questo file non è come uno script CGI. Il file non necessita in alcun modo di essere eseguibile o speciale in alcuna maniera. Si pensi ad esso come ad un normale file HTML nel quale sono contenuti uno speciale set di tag che permettono di eseguire una moltitudine di cose interessanti. </para> <para> Questo programma era molto semplice e sicuramente non era necessario fare ricorso a PHP per creare una pagina come quella. Tutto ciò che essa fa è di visualizzare: <literal>Ciao Mondo</literal> usando la funzione <function>echo</function> di PHP. </para> <para> Se si è provato questo esempio e non ha dato alcun output, o è apparso un pop-up che chiedeva se di scaricare la pagina, o se è apparso il file come testo, è probabile che il server su cui si stanno effettuando le prove non ha abilitato PHP. Provare a chiedere al proprio amministratore di sistema di abilitarlo per voi usando il capitolo del manuale dedicato all'<link linkend="installation">Installazione</link>. Se si vogliono sviluppare in locale script PHP, fare riferimento alla sezione <ulink url="&url.php.downloads;">download</ulink>. Si può sviluppare senza problemi sul proprio Sistema Operativo in locale, è bene installare anche un web server. </para> <para> L'obbiettivo dell'esempio è quello di mostrare il formato speciale dei tag PHP. In questo esempio abbiamo usato <literal>&lt;?php</literal> per indicare l'inizio di un tag PHP. Quindi abbiamo scritto la funzione PHP e abbiamo lasciato la modalità PHP usando il tag di chiusura, <literal>?&gt;</literal>. All'interno di un file HTML si può entrare ed uscire dalla modalità PHP quante volte si desidera. </para> <note> <title>Nota riguardo gli editor di testo</title> <para> Esistomo molti editor di testo e Integrated Development Environment (IDE) che possono essere usati per creare, modificare e gestire file PHP. Una lista parziale di questi strumenti è disponibile qui: <ulink url="&url.phpeditorlist;">PHP Editor's List</ulink>. Se si desidera suggerire un nuo programma, visitare la pagina sopra e chiedere al curatore di aggiungerlo alla lista. </para> </note> <note> <title>Nota riguardo i Word Processor</title> <para> Word processor quali StarOffice Writer, Microsoft Word e Abiword non sono una buona scelta per modificare i file PHP. </para> <para> Se si vogliono provare comunque per scrivere questo script di test, ci si deve assicurare di salvare il file come SOLO TESTO, altrimenti PHP non sarà in grado di leggerlo e quindi non riuscirà ad eseguire lo script. </para> </note> <note> <title>Nota riguardo Blocco Note di Windows</title> <para> Se si scrive codice usando l'applicazione di Windows Blocco Note, occorre assicurarsi che i file vengano salvati con estensione .php. (Blocco Note aggiunge automaticamente l'estensione .txt ai file, a meno che non si intraprenda uno dei passi descritti di seguito.) </para> <para> Quando si salva il file e viene chiesto il nome da assegnargli, scrivere il nome fra virgolette (ad esempio: "ciao.php"). </para> <para> Alternativamente, si può cliccare sul menu a tendina 'Documenti di Testo' nella finestra di salvataggio e cambiare l'impostazione in "Tutti i File". A quel punto si può inserire il nome del file, senza usare le virgolette. </para> </note> </sect1> <sect1 id="tutorial.useful"> <title>Something Useful</title> <para> Let's do something a bit more useful now. We are going to check what sort of browser the person viewing the page is using. In order to do that we check the user agent string that the browser sends as part of its HTTP request. This information is stored in a <link linkend="language.variables">variable</link>. Variables always start with a dollar-sign in PHP. The variable we are interested in right now is <varname>$_SERVER["HTTP_USER_AGENT"]</varname>. </para> <note> <title>PHP Autoglobals Note</title> <para> <link linkend="reserved.variables.server">$_SERVER</link> is a special reserved PHP variable that contains all web server information. It's known as an Autoglobal (or Superglobal). See the related manual page on <link linkend="language.variables.superglobals">Autoglobals</link> for more information. These special variables were introduced in PHP <ulink url="&url.php.release4.1.0;">4.1.0</ulink>. Before this time, we used the older <varname>$HTTP_*_VARS</varname> arrays instead, such as <varname>$HTTP_SERVER_VARS</varname>. Although deprecated, these older variables still exist. (See also the note on <link linkend="tutorial.oldcode">old code</link>.) </para> </note> <para> To display this variable, we can simply do: </para> <para> <example> <title>Printing a variable (Array element)</title> <programlisting role="php"> <![CDATA[ <?php echo $_SERVER["HTTP_USER_AGENT"]; ?> ]]> </programlisting> <para> A sample output of this script may be: <screen role="html"> Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) </screen> </para> </example> </para> <para> There are many <link linkend="language.types">types</link> of variables available in PHP. In the above example we printed an <link linkend="language.types.array">Array</link> element. Arrays can be very useful. </para> <para> <varname>$_SERVER</varname> is just one variable that's automatically made available to you by PHP. A list can be seen in the <link linkend="reserved.variables">Reserved Variables</link> section of the manual or you can get a complete list of them by creating a file that looks like this: </para> <para> <example> <title>Show all predefined variables with <function>phpinfo</function></title> <programlisting role="php"> <![CDATA[ <?php phpinfo(); ?> ]]> </programlisting> </example> </para> <para> If you load up this file in your browser you will see a page full of information about PHP along with a list of all the variables available to you. </para> <para> You can put multiple PHP statements inside a PHP tag and create little blocks of code that do more than just a single echo. For example, if we wanted to check for Internet Explorer we could do something like this: </para> <para> <example> <title>Example using <link linkend="control-structures">control structures</link> and <link linkend="functions">functions</link></title> <programlisting role="php"> <![CDATA[ <?php if (strstr($_SERVER["HTTP_USER_AGENT"], "MSIE")) { echo "You are using Internet Explorer<br />"; } ?> ]]> </programlisting> <para> A sample output of this script may be: <screen role="html"> <![CDATA[ You are using Internet Explorer<br /> ]]> </screen> </para> </example> </para> <para> Here we introduce a couple of new concepts. We have an <link linkend="control-structures.if">if</link> statement. If you are familiar with the basic syntax used by the C language this should look logical to you. If you don't know enough C or some other language where the syntax used above is used, you should probably pick up any introductory PHP book and read the first couple of chapters, or read the <link linkend="langref">Language Reference</link> part of the manual. You can find a list of PHP books at <ulink url="&url.php.books;">&url.php.books;</ulink>. </para> <para> The second concept we introduced was the <function>strstr</function> function call. <function>strstr</function> is a function built into PHP which searches a string for another string. In this case we are looking for <literal>"MSIE"</literal> inside <varname>$_SERVER["HTTP_USER_AGENT"]</varname>. If the string is found, the function returns &true; and if it isn't, it returns &false;. If it returns &true;, the <link linkend="control-structures.if">if</link> statement evaluates to &true; and the code within its {braces} is executed. Otherwise, it's not. Feel free to create similar examples, with <link linkend="control-structures.if">if</link>, <link linkend="control-structures.else">else</link>, and other functions such as <function>strtoupper</function> and <function>strlen</function>. Each related manual page contains examples too. </para> <para> We can take this a step further and show how you can jump in and out of PHP mode even in the middle of a PHP block: </para> <para> <example> <title>Mixing both HTML and PHP modes</title> <programlisting role="php"> <![CDATA[ <?php if (strstr($_SERVER["HTTP_USER_AGENT"], "MSIE")) { ?> <h3>strstr must have returned true</h3> <center><b>You are using Internet Explorer</b></center> <?php } else { ?> <h3>strstr must have returned false</h3> <center><b>You are not using Internet Explorer</b></center> <?php } ?> ]]> </programlisting> <para> A sample output of this script may be: <screen role="html"> <![CDATA[ <h3>strstr must have returned true</h3> <center><b>You are using Internet Explorer</b></center> ]]> </screen> </para> </example> </para> <para> Instead of using a PHP echo statement to output something, we jumped out of PHP mode and just sent straight HTML. The important and powerful point to note here is that the logical flow of the script remains intact. Only one of the HTML blocks will end up getting sent to the viewer depending on if <function>strstr</function> returned &true; or &false; In other words, if the string <literal>MSIE</literal> was found or not. </para> </sect1> <sect1 id="tutorial.forms"> <title>Dealing with Forms</title> <para> One of the most powerful features of PHP is the way it handles HTML forms. The basic concept that is important to understand is that any form element in a form will automatically be available to your PHP scripts. Please read the manual section on <link linkend="language.variables.external">Variables from outside of PHP</link> for more information and examples on using forms with PHP. Here's an example HTML form: </para> <para> <example> <title>A simple HTML form</title> <programlisting role="html"> <![CDATA[ <form action="action.php" method="POST"> Your name: <input type="text" name="name" /> Your age: <input type="text" name="age" /> <input type="submit"> </form> ]]> </programlisting> </example> </para> <para> There is nothing special about this form. It is a straight HTML form with no special tags of any kind. When the user fills in this form and hits the submit button, the <filename>action.php</filename> page is called. In this file you would have something like this: </para> <para> <example> <title>Printing data from our form</title> <programlisting role="php"> <![CDATA[ Hi <?php echo $_POST["name"]; ?>. You are <?php echo $_POST["age"]; ?> years old. ]]> </programlisting> <para> A sample output of this script may be: <screen role="html"> <![CDATA[ Hi Joe. You are 22 years old. ]]> </screen> </para> </example> </para> <para> It should be obvious what this does. There is nothing more to it. The <varname>$_POST["name"]</varname> and <varname>$_POST["age"]</varname> variables are automatically set for you by PHP. Earlier we used the <varname>$_SERVER</varname> autoglobal, now above we just introduced the <link linkend="reserved.variables.post">$_POST</link> autoglobal which contains all POST data. Notice how the <emphasis>method</emphasis> of our form is POST. If we used the method <emphasis>GET</emphasis> then our form information would live in the <link linkend="reserved.variables.get">$_GET</link> autoglobal instead. You may also use the <link linkend="reserved.variables.request">$_REQUEST</link> autoglobal if you don't care the source of your request data. It contains a mix of GET, POST, COOKIE and FILE data. See also the <function>import_request_variables</function> function. </para> </sect1> <sect1 id="tutorial.oldcode"> <title>Using old code with new versions of PHP</title> <para> Now that PHP has grown to be a popular scripting language, there are more resources out there that have listings of code you can reuse in your own scripts. For the most part the developers of the PHP language have tried to be backwards compatible, so a script written for an older version should run (ideally) without changes in a newer version of PHP, in practice some changes will usually be needed. </para> <para> Two of the most important recent changes that affect old code are: <itemizedlist> <listitem> <simpara> The deprecation of the old <varname>$HTTP_*_VARS</varname> arrays (which need to be indicated as global when used inside a function or method). The following <link linkend="language.variables.superglobals">autoglobal arrays</link> were introduced in PHP <ulink url="&url.php.release4.1.0;">4.1.0</ulink>. They are: <varname>$_GET</varname>, <varname>$_POST</varname>, <varname>$_COOKIE</varname>, <varname>$_SERVER</varname>, <varname>$_ENV</varname>, <varname>$_REQUEST</varname>, and <varname>$_SESSION</varname>. The older <varname>$HTTP_*_VARS</varname> arrays, such as $HTTP_POST_VARS, still exist and have since PHP 3. </simpara> </listitem> <listitem> <simpara> External variables are no longer registered in the global scope by default. In other words, as of PHP <ulink url="&url.php.release4.2.0;">4.2.0</ulink> the PHP directive <link linkend="ini.register-globals">register_globals</link> is <emphasis>off</emphasis> by default in &php.ini;. The preferred method of accessing these values is via the autoglobal arrays mentioned above. Older scripts, books, and tutorials may rely on this directive being on. If on, for example, one could use <varname>$id</varname> from the URL <literal>http://www.example.com/foo.php?id=42</literal>. Whether on or off, <varname>$_GET['id']</varname> is available. </simpara> </listitem> </itemizedlist> For more details on these changes, see the section on <link linkend="language.variables.predefined">predefined variables</link> and links therein. </para> </sect1> <sect1 id="tutorial.whatsnext"> <title>What's next?</title> <para> With what you know now you should be able to understand most of the manual and also the various example scripts available in the example archives. You can also find other examples on the php.net websites in the links section: <ulink url="&url.php.links;">&url.php.links;</ulink>. </para> </sect1> </chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml sgml-omittag:t sgml-shorttag:t sgml-minimize-attributes:nil sgml-always-quote-attributes:t sgml-indent-step:1 sgml-indent-data:t indent-tabs-mode:nil sgml-parent-document:nil sgml-default-dtd-file:"../../manual.ced" sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 -->
« previous php.doc.it (#183) next »