9324
Commento:
|
10230
ready for #70
|
Le cancellazioni sono segnalate in questo modo. | Le aggiunte sono segnalate in questo modo. |
Linea 1: | Linea 1: |
#acl GruppoAdmin:admin,read,write,revert GruppoEditori:read,write,revert GruppoFcm:read,write,revert -All:read -Known:read [[Include(Fcm/Header)]] |
#acl GruppoAdmin:admin,read,write,revert GruppoOperatori:admin,read,write,revert GruppoEditori:read,write,revert GruppoFcm:read,write,revert palombo:admin,read,write,revert new.life:admin,read,write,revert paolettopn:admin,read,write,revert Known:read All:read |
Linea 4: | Linea 3: |
== HowTo6 == | <<Include(Fcm/Header)>> = Testo inglese = |
Linea 6: | Linea 6: |
=== Traduzione italiana === Aggiungere Screenlet |
LibreOffice Part 23: Base Form Enhancements with Macros |
Linea 9: | Linea 8: |
Scritto da Pasha T | by Elmer Perry |
Linea 11: | Linea 10: |
Gli Screenlet sono dei piccoli aggeggi che potete mettere sopra il vostro desktop per tenere d'occhio diverse cose, tra le quali la RAM, la CPU, l'uso del disco, data e ora, il meteo, e persino le ultime notizie. Non solo sono facili da usare, ma non danno fastidio e sono relativamente leggeri sul sistema. Qui ce ne occuperemo solo di due, gli altri li potete provare da soli. | For the previous four parts of this series, we have slowly built a database document using LibreOffice's Base module. We have a database with forms to enter our data, and queries and reports for extracting the data. We now have a usable document for recording our book library. However, our current design has one flaw we need to overcome. If we need to enter a new author or media type while we are in the books form, we have to close the book form and open one of the others. If we could enter new authors and media types directly from the books form, it would behave more like an application and make data entry even easier. We can accomplish this through a few short macros. The LibreOffice Basic language is very similar to other Basic languages, such as Visual Basic for Applications. To manipulate the underlying LibreOffice document, we access the Uno framework controlling the document. The Uno framework is quite complex, but I will explain, as best I can, the properties and objects we will use. The goal is not to teach you how to write LibreOffice macros, but how you can use them. Macro Security and Options |
Linea 13: | Linea 14: |
Per installare il programma degli Screenlet, andate sul terminale e digitate quanto segue: | While macros allow us to do cool things in our documents, they can also cause problems. Some people use macros to compromise other people's systems, therefore, we need to take a few minutes to talk about macro security. Whether you are running LibreOffice on Linux, Mac, or Windows, malicious code in a macro can compromise your data and possibly your entire system. |
Linea 15: | Linea 16: |
sudo apt-get install screenlets | Macro security in LibreOffice is simple. Tools > Options opens the Options dialog for LibreOffice. Under LibreOffice, select Security. Click on the Macro Security button to pop up the macro security options. You have four options. Never use the Low security option – it will run macros without asking you. I recommend the Medium security level. With this level, you are prompted whether to run the macros when you open a document containing macros. The High and Very High options require a certificate or folder you designate as trusted. While this is great, I believe nothing trumps the instincts of the user. You usually know whether you were expecting a document to contain macros. When in doubt, click No. Click OK to save your choice and OK to close the options dialog. Now, on to the fun stuff. The Macros |
Linea 17: | Linea 20: |
Comunque per coloro che preferiscono installare i programmi con Synaptic o con Aggiungi/Rimuovi, cercate semplicemente "screenlets" e installateli. Dopo aver fatto questo, andate su Applicazioni > Accessori > Screenlets. Troverete un assortimento di diversi screenlet già installati. Per usarne uno, cliccateci semplicemente sopra, poi cliccate Avvia/Ferma sulla sinistra e lo dovreste veder comparire sul desktop. Prendetevi un minuto per divertirvi muovendolo sullo schermo e così via. (Nota: se volete che uno screenlet si avvii all'avvio del computer, scegliete l'opzione "Avvia automaticamente al login" sulla sinistra). | We will write four macros for our database document. Three will deal with opening forms, and the last will update the list boxes for authors and media types. The general idea behind macros is to accomplish tasks that are not built into the program, or to simplify complex tasks. Our macros really accomplish both, as we will simplify the tasks of adding authors and media types and provide functionality not built into the program. Before we can begin to write our macros, we need a container to hold them. Macros are contained in a module. Modules can live in the program itself or within a document. Since our macros are specific to our database file, we will embed them in the document. Macros embedded in a document are available only when the document is loaded. Macros contained in the program are available as long as the program is running. Tools > Macros > Organize Macros > LibreOffice Basic. The LibreOffice Basic Macros dialog pops up. Select book.odb from the Macro from-list. Click the New button. A dialog pops up asking you for a name for the module. Name it FormCalls. Click OK. This brings up the LibreOffice macro editor. The macro comes with a default main subroutine. We will not use this subroutine. Highlight Sub main and End Sub and press the backspace key to delete them. Our first macro is a generalized subroutine for opening a form. A generalized subroutine is written for reuse. We will call this routine twice from other routines we write. Type this subroutine into the editor: {{{ Sub OpenAForm (FormName as String) Dim GetForm as Object GetForm = ThisDatabaseDocument.FormDocuments.GetByName(FormName) GetForm.Open End Sub }}} The first line of the subroutine is called the signature. The signature determines how the subroutine is called. A signature starts with the keyword Sub, which defines this call as a subroutine. Next, the name of the subroutine. In our case, OpenAForm is the name of the subroutine. Finally in the parenthesis, we have the arguments used when calling this subroutine. In our case, we have a variable named FormName which is a type String. In the second line of the subroutine, Dim is another keyword. Dim initializes a variable as a type, and, optionally, a value. We define a variable named GetForm as a type Object. The third line assigns a value to the variable GetForm through a chain of commands in the Uno framework. ThisDatabaseDocument refers to the currently open database document. In our case, book.odb. FormDocuments is a collection of all the forms in the document. Finally, GetByName retrieves a specific form object from the collection. Notice, we pass the variable FormName from the signature to this method. Once the call is complete, the variable GetForm is the object of the form name passed to the subroutine. The fourth line calls the Open method of the form. On the fifth line, we tell Basic this is the end of the subroutine with the command End Sub. We will call the OpenAform subroutine twice. Once to open the authors form, and once to open the media form. Add these two subroutines to your editor: {{{ Sub OpenAuthorsForm(oEv As Object) OpenAForm("Authors") End Sub |
Linea 19: | Linea 38: |
Potete trovarne molti di più online. | Sub OpenMediaForm(oEv As Object) OpenAForm("Media") End Sub }}} The signature on these two subroutines are a little different. Since we will call them from a control within a form, we need to pass the object making the call as an argument, even though we do not use it. The argument oEv is a reference to the object making the call. We will use this to our advantage later, in the last subroutine, but here we do it because it is required. These two subroutines are pretty simple. We just make a call to OpenAForm passing the name of the form we want to open, Authors or Media. The final subroutine deals with our problem of refreshing the data in the list boxes for authors and media when we add authors or media using the two subroutines above: {{{ Sub ListRefresh(oEv as Object) oEv.source.model.Refresh End Sub }}} Once again, since we will call this subroutine from a control, we need a reference to the control making the call. However, this time we will actually use the object. This subroutine makes a method call to the underlying model of the list box and refreshes the data in the list, thus updating our list of authors or media types. Save your module and close the Basic editor. |
Linea 21: | Linea 52: |
Screenlet | Making Connections to Macros |
Linea 23: | Linea 54: |
Il primo screenlet di cui ci occuperemo è chiamato Folderview Screenlet. Quelli di voi che hanno visto il nuovo desktop KDE4 e a cui è piaciuto l'applet Folderview vorranno usarlo. È semplicemente uno screenlet sulla scrivania che potete usare per accedere velocemente in qualche cartella della vostra /home (o dappertutto, peraltro). Guardate la schermata (a destra) per vederlo. Il secondo è chiamato Terminal Screenlet ed è semplicemente un terminale posizionato sulla scrivania per un rapido accesso. Guardate nuovamente la schermata in basso. | At this point, our macros do nothing. We need to connect them to objects in our form to activate them when needed. First, we will connect the open form subroutines to buttons in our form, and then we will connect the ListRefresh to the list boxes. In the database pane, click on Forms. Right-click the Books form and select edit. Add two push buttons to the form, one under the Authors table and another under the Media table. Right-click the button under the Authors table and select Control to bring up the buttons properties dialog. On the General tab, change the name to AddAuthors and the Label to Add Authors. On the Events tab, click the ellipses (…) button next to Execute Action – which brings up the Assign Action dialog. Click the Macro button to bring up the Macro Selector dialog. In the tree list under Library, select book.odb > Standard > FormCalls. Select OpenAuthorsForm from the Macro Name list and click OK. Click OK to close the Assign Action dialog. Close the buttons properties dialog. Do the same with the button under the Media table, only name it AddMedia, make the label Add Media Type, and assign the macro OpenMediaForm to the Execute Action event. Finally, we need to add the refresh subroutine to our list boxes. Right-click the Authors column in the authors table and select Column. On the Events tab, click the ellipse (…) button beside “When receiving focus”. In the Assign Action button, use the Macro button to assign the ListRefresh macro to the action. This will cause the list to update data from the Authors table when you click on a list box in the column. Do the same for the Media column in the media table. Save your changes to the Books form and close it. |
Linea 25: | Linea 61: |
"Gli screenlet sono piccole applicazioni (scritte in Pyton) che possono essere descritte come "la rappresentazione virtuale delle cose che sparse qua e là sulla vostra scrivania". Post-it, orologi, righelli... le possibilità sono infinite. | Testing Your Changes |
Linea 27: | Linea 63: |
Installare gli Screenlet | Any time we make changes to our forms, we will want to test them and make sure we got everything right, especially in cases where we have used macros. One simple typo could cause things to not work. Double-click the Books form to open it. Add a new book with an author and media type you have not added already. Click the Add Authors button to make sure it opens the form. Add some authors. Close the Authors form. Click on the authors dropdown list box and verify that the authors you added are there. Do the same test with the Add Media Type button and listbox. Final Thoughts and References |
Linea 29: | Linea 66: |
Cominceremo con installarli. Andate su www.gnome-look.org e, sulla sinistra, troverete una barra di ricerca. Per prima cosa cercate Folderview e il risultato dovrebbe condurvi alla sua pagina. Scaricatelo da lì e andate alla vostra cartella di download. Trascinate il file tar.gz all'inerno del gestore screenlet e lo installerà automaticamente. Ripetete lo stesso per il Terminal Screenlet e installatelo. In seguito avviateli e divertitevi. | Again, I would like to emphasize that writing macros in LibreOffice Basic is complex. Documentation is pretty sparse, but it is out there. If you are interested in taking up the challenge, here are some references to get you started: LibreOffice Basic Guide: http://wiki.documentfoundation.org/images/d/dd/BasicGuide_OOo3.2.0.odt Andrew Pitonyak's OpenOffice Macro Information: http://www.pitonyak.org/oo.php You can find the macros used in this How-To on pastebin.com at http://pastebin.com/MU2Ztizi Next time, we will move on to another part of the LibreOffice suite and explore the Math module. |
Linea 31: | Linea 72: |
Il prossimo passo è configurare le proprietà di questi screenlet. Cominceremo con Folderview. Cliccate con il tasto destro e scegliete proprietà. Vedrete tre schede: Informazioni, Temi, Opzioni. La scheda Temi è dove potete trovare i vari temi per lo screelet. In questo caso c'è solo quello di default. Quella successiva è la scheda Opzioni. Qui potete trovare le impostazioni attuali di questo screenlet. Potete esaminare le opzioni e scegliere ciò che vi serve. Per esempio seleziono "Fissa sulla scrivania" poiché voglio che questo screenlet sia su tutte le scrivanie (1,2,3 ecc). Seleziono anche "Blocca posizione" poiché tendo a muovere accidentalmente gli screenlet. La scheda successiva che vedrete è Folder. Qui potete configurare quante icone volete in questo screenlet e anche il percorso della cartella. Se volete, potete avere diversi screenlet Folderview sulla vostra scrivania per qualsiasi cartella a cui vogliate accedere: la vostra cartella home, i vostri download, i documenti ecc. Infine troverete la scheda Look. Qui potrete configurare l'aspetto dello screenlet, come il colore, l'opacità, spessore dei bordi e altro ancora. Provate le varie impostazioni fino a trovare qualcosa che vi piaccia. Ricordatevi solo che se volete che i vostri screenlet siano belli e volete l'opacità, assicuratevi che sia attivo o Compiz oppure Metacity compositing (personalmente preferisco Metacity compositing che è più leggero e non richiede schede grafiche sofisticate). In seguito potete giocherellare con il Terminal Screenlet e le sue proprietà. Dovreste perder tempo con le proprietà di qualsiasi screenlet per configurarlo come volete. Dopotutto Linux è libertà assoluta di scelta. | = Traduzione italiana = |
Linea 33: | Linea 74: |
Dunque divertitevi con gli screenlet e se ne volete di più, cliccate semplicemente su "get more screenlets" in fondo al Gestore Screenlet (come mostrato sopra a destra). ==== Note alla traduzione ==== |
== Note alla traduzione == |
Linea 38: | Linea 77: |
=== Revisione === Aggiungere Screenlet Scritto da Pasha T Gli Screenlet sono dei piccoli aggeggi che potete mettere sul vostro desktop per tenere d'occhio diverse cose, tra le quali la RAM, la CPU, l'uso del disco, data e ora, il meteo, e persino le ultime notizie. Non solo sono facili da usare, ma non danno fastidio e sono relativamente leggeri per il sistema. Ne esamineremo soltanto due, mentre i rimanenti li potete provare da soli. Per installare il programma degli Screenlet, andate sul terminale e digitate quanto segue: sudo apt-get install screenlets Tuttavia per coloro che preferiscono installare i programmi con Synaptic o con Aggiungi/Rimuovi, cercate semplicemente screenlets e installateli. Dopo aver fatto questo, andate su Applicazioni > Accessori > Screenlets. Troverete un assortimento di diversi screenlet già installati che potete usare. Per usarne uno, cliccateci semplicemente sopra, poi cliccate Avvia/Ferma in alto a sinistra e lo dovreste veder comparire sul desktop. Prendetevi un minuto per divertirvi muovendolo sullo schermo e così via. (Nota: se volete che uno screenlet si avvii all'avvio del computer, scegliete l'opzione "Avvia automaticamente al login" sulla sinistra). Potete trovarne molti altri online, in aggiunta a quelli forniti con il programma. Screenlet Il primo screenlet di cui ci occuperemo è chiamato Folderview Screenlet. Quelli di voi che hanno visto il nuovo desktop KDE4 e a cui è piaciuto l'applet Folderview vorranno usarlo. È semplicemente uno screenlet sulla scrivania che potete usare per accedere velocemente ad una certa cartella della vostra /home (o dappertutto, peraltro). Guardate la schermata (a destra) per vederlo. Il secondo è chiamato Terminal Screenlet ed è semplicemente questo, un terminale posizionato sulla scrivania per un rapido accesso. Guardate nuovamente la schermata in basso. "Gli screenlet sono piccole applicazioni (scritte in Pyton) che possono essere descritte come "la rappresentazione virtuale di oggetti che giacciono/che stanno sparse sulla vostra scrivania". Post-it, orologi, righelli... le possibilità sono infinite. Installare gli Screenlet Cominceremo prima di tutto con l'installarli. Andate su www.gnome-look.org e, sulla sinistra, troverete una barra di ricerca. Per prima cosa cercate Folderview e il risultato dovrebbe condurvi alla sua pagina. Scaricatelo da lì e andate alla vostra cartella di download. Trascinate il file tar.gz all'interno del gestore screenlet e lo installerà automaticamente. Ripetete la stessa cosa per il Terminal Screenlet e installatelo. Dopodiché avviateli e divertitevi. Il prossimo passo è configurare le proprietà di questi screenlet. Cominceremo con Folderview. Cliccate con il tasto destro e scegliete proprietà. Vedrete tre schede: Informazioni, Temi e Opzioni. La scheda Temi è dove potete trovare i vari temi per lo screelet. In questo caso c'è solo quello di default. Quella successiva è la scheda Opzioni. Qui potete trovare le impostazioni attuali di questo particolare screenlet. Potete esaminare le opzioni e scegliere ciò che vi serve. Per esempio io ho selezionato "Fissa sulla scrivania" poiché voglio che questo screenlet sia su tutte le mie scrivanie (1,2,3 ecc). Ho selezionato anche "Blocca posizione" poiché tendo a muovere accidentalmente gli screenlet. La scheda successiva che vedrete è Folder. Qui potete configurare quante icone volete in questo screenlet e anche il percorso della cartella. Se volete, potete avere diversi screenlet Folderview attivi sulla vostra scrivania per qualsiasi cartella cui vogliate accedere - la vostra cartella home, i vostri download, i documenti ecc. Infine troverete la scheda Look. Qui potrete configurare l'aspetto dello screenlet, come il colore, l'opacità, lo spessore dei bordi ed altro ancora. Provate le varie impostazioni fino a trovare qualcosa che vi piaccia. Ricordatevi solo che se volete che i vostri screenlet siano belli e volete l'opacità, assicuratevi che sia attivo o Compiz oppure Metacity compositing (personalmente preferisco Metacity compositing che è più leggero e non richiede schede grafiche sofisticate). A questo punto potete giocherellare con il Terminal Screenlet e le sue proprietà. Dovrete perdere un po' di tempo con le proprietà di qualche screenlet per configurarlo come volete. Dopotutto Linux è libertà assoluta di scelta. Dunque divertitevi con gli screenlet e se ne volete di più, cliccate semplicemente su "get more screenlets" in fondo al Gestore Screenlet (come mostrato sopra a destra). ==== Note alla revisione ==== |
= Revisione = |
Linea 72: | Linea 80: |
== Note alla revisione == | |
Linea 73: | Linea 82: |
=== Errata Corrige === | = Errata Corrige = |
Linea 78: | Linea 89: |
CategoryComunita | CategoryComunitaFcm |
Testo inglese
LibreOffice Part 23: Base Form Enhancements with Macros
by Elmer Perry
For the previous four parts of this series, we have slowly built a database document using LibreOffice's Base module. We have a database with forms to enter our data, and queries and reports for extracting the data. We now have a usable document for recording our book library. However, our current design has one flaw we need to overcome. If we need to enter a new author or media type while we are in the books form, we have to close the book form and open one of the others. If we could enter new authors and media types directly from the books form, it would behave more like an application and make data entry even easier. We can accomplish this through a few short macros. The LibreOffice Basic language is very similar to other Basic languages, such as Visual Basic for Applications. To manipulate the underlying LibreOffice document, we access the Uno framework controlling the document. The Uno framework is quite complex, but I will explain, as best I can, the properties and objects we will use. The goal is not to teach you how to write LibreOffice macros, but how you can use them. Macro Security and Options
While macros allow us to do cool things in our documents, they can also cause problems. Some people use macros to compromise other people's systems, therefore, we need to take a few minutes to talk about macro security. Whether you are running LibreOffice on Linux, Mac, or Windows, malicious code in a macro can compromise your data and possibly your entire system.
Macro security in LibreOffice is simple. Tools > Options opens the Options dialog for LibreOffice. Under LibreOffice, select Security. Click on the Macro Security button to pop up the macro security options. You have four options. Never use the Low security option – it will run macros without asking you. I recommend the Medium security level. With this level, you are prompted whether to run the macros when you open a document containing macros. The High and Very High options require a certificate or folder you designate as trusted. While this is great, I believe nothing trumps the instincts of the user. You usually know whether you were expecting a document to contain macros. When in doubt, click No. Click OK to save your choice and OK to close the options dialog. Now, on to the fun stuff. The Macros
We will write four macros for our database document. Three will deal with opening forms, and the last will update the list boxes for authors and media types. The general idea behind macros is to accomplish tasks that are not built into the program, or to simplify complex tasks. Our macros really accomplish both, as we will simplify the tasks of adding authors and media types and provide functionality not built into the program. Before we can begin to write our macros, we need a container to hold them. Macros are contained in a module. Modules can live in the program itself or within a document. Since our macros are specific to our database file, we will embed them in the document. Macros embedded in a document are available only when the document is loaded. Macros contained in the program are available as long as the program is running. Tools > Macros > Organize Macros > LibreOffice Basic. The LibreOffice Basic Macros dialog pops up. Select book.odb from the Macro from-list. Click the New button. A dialog pops up asking you for a name for the module. Name it FormCalls. Click OK. This brings up the LibreOffice macro editor. The macro comes with a default main subroutine. We will not use this subroutine. Highlight Sub main and End Sub and press the backspace key to delete them. Our first macro is a generalized subroutine for opening a form. A generalized subroutine is written for reuse. We will call this routine twice from other routines we write. Type this subroutine into the editor:
Sub OpenAForm (FormName as String) Dim GetForm as Object GetForm = ThisDatabaseDocument.FormDocuments.GetByName(FormName) GetForm.Open End Sub
The first line of the subroutine is called the signature. The signature determines how the subroutine is called. A signature starts with the keyword Sub, which defines this call as a subroutine. Next, the name of the subroutine. In our case, OpenAForm is the name of the subroutine. Finally in the parenthesis, we have the arguments used when calling this subroutine. In our case, we have a variable named FormName which is a type String. In the second line of the subroutine, Dim is another keyword. Dim initializes a variable as a type, and, optionally, a value. We define a variable named GetForm as a type Object. The third line assigns a value to the variable GetForm through a chain of commands in the Uno framework. ThisDatabaseDocument refers to the currently open database document. In our case, book.odb. FormDocuments is a collection of all the forms in the document. Finally, GetByName retrieves a specific form object from the collection. Notice, we pass the variable FormName from the signature to this method. Once the call is complete, the variable GetForm is the object of the form name passed to the subroutine. The fourth line calls the Open method of the form. On the fifth line, we tell Basic this is the end of the subroutine with the command End Sub. We will call the OpenAform subroutine twice. Once to open the authors form, and once to open the media form. Add these two subroutines to your editor:
Sub OpenAuthorsForm(oEv As Object) OpenAForm("Authors") End Sub Sub OpenMediaForm(oEv As Object) OpenAForm("Media") End Sub
The signature on these two subroutines are a little different. Since we will call them from a control within a form, we need to pass the object making the call as an argument, even though we do not use it. The argument oEv is a reference to the object making the call. We will use this to our advantage later, in the last subroutine, but here we do it because it is required. These two subroutines are pretty simple. We just make a call to OpenAForm passing the name of the form we want to open, Authors or Media. The final subroutine deals with our problem of refreshing the data in the list boxes for authors and media when we add authors or media using the two subroutines above:
Sub ListRefresh(oEv as Object) oEv.source.model.Refresh End Sub
Once again, since we will call this subroutine from a control, we need a reference to the control making the call. However, this time we will actually use the object. This subroutine makes a method call to the underlying model of the list box and refreshes the data in the list, thus updating our list of authors or media types. Save your module and close the Basic editor.
Making Connections to Macros
At this point, our macros do nothing. We need to connect them to objects in our form to activate them when needed. First, we will connect the open form subroutines to buttons in our form, and then we will connect the ListRefresh to the list boxes. In the database pane, click on Forms. Right-click the Books form and select edit. Add two push buttons to the form, one under the Authors table and another under the Media table. Right-click the button under the Authors table and select Control to bring up the buttons properties dialog. On the General tab, change the name to AddAuthors and the Label to Add Authors. On the Events tab, click the ellipses (…) button next to Execute Action – which brings up the Assign Action dialog. Click the Macro button to bring up the Macro Selector dialog. In the tree list under Library, select book.odb > Standard > FormCalls. Select OpenAuthorsForm from the Macro Name list and click OK. Click OK to close the Assign Action dialog. Close the buttons properties dialog. Do the same with the button under the Media table, only name it AddMedia, make the label Add Media Type, and assign the macro OpenMediaForm to the Execute Action event. Finally, we need to add the refresh subroutine to our list boxes. Right-click the Authors column in the authors table and select Column. On the Events tab, click the ellipse (…) button beside “When receiving focus”. In the Assign Action button, use the Macro button to assign the ListRefresh macro to the action. This will cause the list to update data from the Authors table when you click on a list box in the column. Do the same for the Media column in the media table. Save your changes to the Books form and close it.
Testing Your Changes
Any time we make changes to our forms, we will want to test them and make sure we got everything right, especially in cases where we have used macros. One simple typo could cause things to not work. Double-click the Books form to open it. Add a new book with an author and media type you have not added already. Click the Add Authors button to make sure it opens the form. Add some authors. Close the Authors form. Click on the authors dropdown list box and verify that the authors you added are there. Do the same test with the Add Media Type button and listbox. Final Thoughts and References
Again, I would like to emphasize that writing macros in LibreOffice Basic is complex. Documentation is pretty sparse, but it is out there. If you are interested in taking up the challenge, here are some references to get you started: LibreOffice Basic Guide: http://wiki.documentfoundation.org/images/d/dd/BasicGuide_OOo3.2.0.odt Andrew Pitonyak's OpenOffice Macro Information: http://www.pitonyak.org/oo.php You can find the macros used in this How-To on pastebin.com at http://pastebin.com/MU2Ztizi Next time, we will move on to another part of the LibreOffice suite and explore the Math module.
Traduzione italiana
Note alla traduzione
Revisione
Note alla revisione