diff options
Diffstat (limited to 'files/it/archive/mozilla')
23 files changed, 0 insertions, 2099 deletions
diff --git a/files/it/archive/mozilla/index.html b/files/it/archive/mozilla/index.html deleted file mode 100644 index 0acec76e6d..0000000000 --- a/files/it/archive/mozilla/index.html +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Archived Mozilla and build documentation -slug: Archive/Mozilla -tags: - - NeedsTranslation - - TopicStub -translation_of: Archive/Mozilla ---- -<p>These articles are archived, obsolete documents about Mozilla, Gecko, and the process of building Mozilla projects.</p> -<p>{{SubpagesWithSummaries}}</p> diff --git a/files/it/archive/mozilla/persona/.well-known-browserid/index.html b/files/it/archive/mozilla/persona/.well-known-browserid/index.html deleted file mode 100644 index 66614c5b3d..0000000000 --- a/files/it/archive/mozilla/persona/.well-known-browserid/index.html +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: .well-known-browserid -slug: Archive/Mozilla/Persona/.well-known-browserid -translation_of: Archive/Mozilla/Persona/.well-known-browserid ---- -<p>Domains advertise their ability to act as Persona Identity Providers (IdPs) by publishing a support document at <code>/.well-known/browserid</code>. This JSON-formatted document must be served over HTTPS with the content type <code>application/json</code>.</p> -<p>This document may either specify how to provision and authenticate users, or may delegate its authority to another Identity Provider.</p> -<p><strong>Note:</strong> you should also consult the <a class="link-https" href="https://github.com/mozilla/id-specs/blob/prod/browserid/index.md">BrowserID Protocol Specification</a> as the authoritative technical reference.</p> -<h2 id="Basic_Support">Basic Support</h2> -<p>A domain which directly acts an an IdP must provide three values in its support document:</p> -<ul> - <li><code>public-key</code>: The public part of the domain's cryptographic key.</li> - <li><code>authentication</code>: The domain's page for asking users to log in.</li> - <li><code>provisioning</code>: The domain's page for certifying its users' identities.</li> -</ul> -<p id="Example_.2F.well-known.2Fbrowserid_file.3A"><strong>Example /.well-known/browserid file:</strong></p> -<pre class="brush:js;">{ - "public-key": { - "algorithm": "RS", - "n": "82818905405105134410187227495885391609221288015566078542117409373192106382993306537273677557482085204736975067567111831005921322991127165013340443563713385983456311886801211241492470711576322130577278575529202840052753612576061450560588102139907846854501252327551303482213505265853706269864950437458242988327", - "e": "65537" - }, - "authentication": "/browserid/sign_in.html", - "provisioning": "/browserid/provision.html" -}</pre> -<h2 id="Delegated_Support">Delegated Support</h2> -<p>HTTP redirects and other means of "moving" a /.well-known/browserid file are not permitted. If an IdP would like to delegate to another domain for authentication and provisioning, it may publish a support document which only contains an <code>authority</code> entry.</p> -<p id="Example_.2F.well-known.2Fbrowserid.3A"><strong>Example /.well-known/browserid:</strong></p> -<pre class="brush:js;">{ - "authority": "subdomain.example.com" -} -</pre> -<p>Then <code>subdomain.example.com</code> would host its own support document, as per the example above.</p> -<p>The <code>authority</code> field is specified as a hostname plus, optionally, a port. It may not contain a path. So <code>"example.com</code>", "<code>subdomain.example.com"</code>, and "<code>subdomain.example.com:8080</code>" are all valid, but "<code>subdomain.example.com/login</code>" is not.</p> -<p>A domain may delegate to any other domain, so long as the other domain publishes a <code>/.well-known/browserid</code> document.</p> -<h2 id="Checklist">Checklist</h2> -<ul> - <li>The document is formatted as valid JSON</li> - <li>The document is served over SSL</li> - <li>The document is served with a content type of "<code>application/json</code>"</li> - <li>The document is hosted on the domain exactly matching that in the email addresses assigned to users. For example: <code>example.com</code>, not <code>www.example.com</code>.</li> - <li>If delegating to another Identity Provider, the <code>authority</code> value is specified only as a hostname and, optionally, a port.</li> -</ul> -<p>Many of these can be tested automatically with the <a class="link-https" href="https://github.com/mozilla/browserid/blob/dev/scripts/check_primary_support" title="https://github.com/mozilla/browserid/blob/dev/scripts/check_primary_support">check_primary_support script from the Persona</a> codebase<strong>.</strong></p> diff --git a/files/it/archive/mozilla/persona/compatibilità_con_i_browser/index.html b/files/it/archive/mozilla/persona/compatibilità_con_i_browser/index.html deleted file mode 100644 index 33af33db7c..0000000000 --- a/files/it/archive/mozilla/persona/compatibilità_con_i_browser/index.html +++ /dev/null @@ -1,86 +0,0 @@ ---- -title: Browser compatibility -slug: Archive/Mozilla/Persona/Compatibilità_con_i_Browser -translation_of: Archive/Mozilla/Persona/Browser_compatibility ---- -<h2 id="Browser_supportati">Browser supportati</h2> -<p>Persona è sviluppato, testato e supportato dai seguenti browser. Grazie alla libreria JavaScript multipiattaforma di Persona, gli utenti non hanno bisogno di componenti aggiuntivi per usare il sistema.</p> -<table> - <tbody> - <tr> - <th colspan="3" scope="row" style="text-align: center; background-color: #d3d7cf;"><strong>Browser Desktop</strong></th> - </tr> - <tr> - <th scope="row"><strong>Internet Explorer</strong></th> - <td colspan="2" rowspan="1" style="background-color: #8ae234;">8.0<sup>*</sup>, 9.0<sup>†</sup>, 10.0<sup>*</sup><sup>*</sup> (vedi <a href="https://developer.mozilla.org/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22" title="https://developer.mozilla.org/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22">Modalità Compatibilità</a> più sotto)</td> - </tr> - <tr> - <th scope="row"><strong>Firefox</strong></th> - <td colspan="2" style="background-color: #8ae234;">Versione Stabile Corrente, Beta, Aurora, Nightly, e Extended Support Releases<br> - Versione Stabile Precedente</td> - </tr> - <tr> - <th scope="row"><strong>Chrome</strong></th> - <td colspan="2" style="background-color: #8ae234;">Ultima Versione Stabile</td> - </tr> - <tr> - <th scope="row"><strong>Safari</strong></th> - <td colspan="2" style="background-color: #8ae234;">Ultima Versione Stabile</td> - </tr> - <tr> - <th scope="row"><strong>Opera</strong></th> - <td colspan="2" style="background-color: #8ae234;">Ultima Versione Stabile<sup>‡</sup></td> - </tr> - <tr> - <th colspan="3" scope="row" style="text-align: center; background-color: #d3d7cf;"><strong>Browser iOS</strong></th> - </tr> - <tr> - <th scope="row"><strong>Safari Mobile</strong></th> - <td colspan="2" rowspan="1" style="background-color: #8ae234;">iOS 5.x — 6.x</td> - </tr> - <tr> - <th colspan="3" scope="row" style="text-align: center; background-color: #d3d7cf;"><strong>Browser Android</strong></th> - </tr> - <tr> - <th scope="row"><strong>Browser Predefinito</strong></th> - <td colspan="2" rowspan="1" style="background-color: #8ae234;">2.2 — 4.x</td> - </tr> - <tr> - <th scope="row"><strong>Firefox</strong></th> - <td colspan="2" style="background-color: #8ae234;">Versione Stabile Corrente, Beta, Aurora, Nightly<br> - Versione Stabile Precedente</td> - </tr> - <tr> - <th scope="row"><strong>Chrome</strong></th> - <td colspan="2" style="background-color: #8ae234;">Ultima Versione Stabile</td> - </tr> - </tbody> -</table> -<p><sup>*</sup>: Per Windows XP. <sup>†</sup>: Per Windows Vista e Windows 7. <sup>*</sup><sup>*</sup>Windows 8.<sup> </sup><sup>‡</sup>: Tempo permettendo.</p> -<h2 id="Browser_non_supportati">Browser non supportati</h2> -<ul> - <li>Internet Explorer versioni 6.0 e 7.0 non è supportato. Agli utenti verrà chiesto di aggiornare il proprio browser. Vedi anche la sezione <a href="https://developer.mozilla.org/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22" title="https://developer.mozilla.org/docs/persona/Browser_compatibility#Internet_Explorer_.22Compatibility_Mode.22">Modalità Compatibilità</a> più sotto.</li> - <li>Google Chrome Frame non è supportato e non è funzionante. Il supporto potrebbe essere aggiunto successivamente (<a href="https://github.com/mozilla/browserid/issues/796" title="https://github.com/mozilla/browserid/issues/796">Issue #796</a>).</li> - <li>Browser di terze parti su iOS non sono supportati e non sono funzionanti. Il supporto potrebbe essere aggiunto successivamente (<a href="https://github.com/mozilla/browserid/issues/2034" title="https://github.com/mozilla/browserid/issues/2034">Issue #2034</a>).</li> -</ul> -<h2 id="Modalità_compatibilità_di_Internet_Explorer">"Modalità compatibilità" di Internet Explorer</h2> -<p>Dalla versione 8.0 in poi, Internet Explorer supporta la cosiddetta Modalità Compatibilità, nella quale il browser può emulare una versione del browser precedente alla 8.0 nel renderizzare una pagina. Questa funzionalità può essere controllata in tre modi</p> -<ol> - <li>come impostazione locale del browser</li> - <li>basandosi sulla presenza e il valore della dichiarazione <a href="https://developer.mozilla.org/docs/Quirks_Mode_and_Standards_Mode" title="https://developer.mozilla.org/docs/Quirks_Mode_and_Standards_Mode">DOCTYPE</a> nella pagina</li> - <li>come istruzione inviata dal sito stesso, utilizzando l'intestazione <a href="http://msdn.microsoft.com/library/cc288325%28v=vs.85%29.aspx" title="http://msdn.microsoft.com/library/cc288325%28v=vs.85%29.aspx">"X-UA-Compatible"</a> come intestazione HTTP o tramite l'uso del tag <a href="https://developer.mozilla.org/docs/HTML/Element/meta" title="https://developer.mozilla.org/docs/HTML/Element/meta"><code><meta></code></a> nella pagina. Questo metodo bypassa gli altri due.</li> -</ol> -<p>Poiché le versioni di Internet Explorer precedenti alla 8.0 non sono supportate da Persona, qualsiasi versione di Internet Explorer configurata per emulare versioni pre-8.0 non funzioneranno con Persona. Il problema solitamente si verifica per una di queste ragioni:</p> -<ul> - <li>il sito sta utilizzando "X-UA-Compatible" per indicare esplicitamente al browser di emulare una versione pre-8.0 version</li> - <li>nelle pagine del sito il DOCTYPE non è dichiarato, non si trova nella prima riga della pagina, o imposta il browser in quirks mode, e il sito non ha il settaggio "X-UA-Compatible" per IE versione 8.0 o successiva</li> - <li>il browser è configurato localmente per utilizzare una Modalità Compatibilità per una versione pre-8.0 e il sito non sta bypassando queste impostazioni utilizzando "X-UA-Compatible" per indicare una versione di IE pari o superiore alla 8.0.</li> -</ul> -<p>Per ulteriori informazioni, vedere <a href="https://blogs.msdn.com/b/askie/archive/2009/03/23/understanding-compatibility-modes-in-internet-explorer-8.aspx?Redirected=true" title="https://blogs.msdn.com/b/askie/archive/2009/03/23/understanding-compatibility-modes-in-internet-explorer-8.aspx?Redirected=true">"Comprendere le Modalità Compatibilità in Internet Explorer 8"</a> e <a href="http://hsivonen.iki.fi/doctype/index.html#ie8" title="http://hsivonen.iki.fi/doctype/index.html#ie8">"Complicazioni su IE8 e IE9"</a>.</p> -<h2 id="Altri_Browser">Altri Browser</h2> -<p>Anche se non esplicitamente supportato, qualunque browser includa sia {{ domxref("window.postMessage()") }} che {{ domxref("Storage", "localStorage") }} dovrebbe funzionare. Queste API sono disponibli in tutti i principali browser da Marzo 2010.</p> -<h2 id="Problemi_noti">Problemi noti</h2> -<ul> - <li>I browser devono accettare i cookie di terze parti per funzionare appieno (<a href="https://github.com/mozilla/browserid/issues/1352" title="https://github.com/mozilla/browserid/issues/1352">Issue #1352</a>).</li> - <li>Gli utenti di Android 2.x senza un browser di default potrebbero non riuscire ad effettuare il login (<a href="https://github.com/mozilla/browserid/issues/1854" title="https://github.com/mozilla/browserid/issues/1854">Issue #1854</a>).</li> -</ul> diff --git a/files/it/archive/mozilla/persona/index.html b/files/it/archive/mozilla/persona/index.html deleted file mode 100644 index ae58667799..0000000000 --- a/files/it/archive/mozilla/persona/index.html +++ /dev/null @@ -1,175 +0,0 @@ ---- -title: Persona -slug: Archive/Mozilla/Persona -translation_of: Archive/Mozilla/Persona ---- -<div class="boxed translate-display"> -<div class="summary"><a href="https://plus.google.com/111906898111013941029/posts?pid=5965858120233436114&oid=111906898111013941029"><img alt="" src="https://plus.google.com/111906898111013941029/posts?pid=5965858120233436114&oid=111906898111013941029"></a>Sistema di autenticazione singola semplice e attento alla privacy: permetti ai tuoi utenti di autenticarsi sul tuo sito con il proprio indirizzo email e liberati dalla gestione delle password.</div> - -<div class="column-container"> -<p><span class="seoSummary"><a href="https://login.persona.org/">Mozilla Persona</a> è un sistema di login per il Web utilizzabile con qualsiasi browser, facile da usare e da integrare. Funziona su <a href="https://developer.mozilla.org/it/docs/persona/Browser_compatibility">tutti i principali browser</a> e puoi <a href="https://developer.mozilla.org/it/docs/Persona/Quick_Setup">iniziare a usarlo subito</a>.</span></p> - -<p>Perché dovresti usare Persona sul tuo sito?</p> - -<ol> - <li><strong>Persona elimina completamente le password per i singoli siti,</strong> liberando l'utente dalla necessità di creare, gestire e tenere al sicuro le password.</li> - <li><strong>Persona è facile da usare.</strong> In solo due clic, un utente Persona può autenticarsi su un nuovo sito, come <a href="http://voo.st">Voost</a>, aggirando gli ostacoli associati alla creazione di un account.</li> - <li><strong>Persona è facile da implementare</strong><strong>. </strong>Gli sviluppatori possono aggiungere Persona sul proprio sito in mezza giornata.</li> - <li><strong>Non c'è alcun vincolo</strong>. Gli sviluppatori ottengono da tutti i loro utenti un indirizzo verificato, mentre gli utenti possono utilizzare qualsiasi indirizzo email con Persona.</li> -</ol> - -<p>Inoltre, Persona può solo migliorare: è sviluppato su un <strong>protocollo aperto e decentralizzato,</strong> che è progettato per permettere <strong>un'integrazione diretta all'interno dei browser</strong> e il <strong>supporto nativo da parte dei provider di posta</strong><strong>. </strong>I siti che implementano Persona oggi, otterranno automaticamente questi miglioramenti, senza bisogno di modificare il proprio codice.</p> -</div> - -<hr> -<div class="column-container"> -<h2 id="Usare_Persona_sul_proprio_sito">Usare Persona sul proprio sito</h2> - - -<div class="column-third"> -<h3 id="Per_iniziare">Per iniziare</h3> - -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Why_Persona">Perché Persona?</a></dt> - <dd>Che cosa ha di speciale persona rispetto ad altri sistemi di identificazione e autenticazione.</dd> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Quick_Setup">Preparazione veloce</a></dt> - <dd>Una guida passo passo che insegna come aggiungere Persona al proprio sito web.</dd> -</dl> - -<h3 id="Riferimento_delle_API">Riferimento delle API</h3> - -<dl> - <dt><a href="https://developer.mozilla.org/it/Persona/The_navigator.id_API">La API navigator.id</a></dt> - <dd>L'API del browser.</dd> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Remote_Verification_API">Riferimento dell'API di verifica</a></dt> - <dd>L'API di verifica remota.</dd> -</dl> -</div> - -<div class="column-third"> -<h3 id="Guide">Guide</h3> - -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Security_Considerations">Considerazioni sulla sicurezza</a></dt> - <dd>Pratiche e tecniche per assicurarsi che il proprio deploy di Persona sia sicuro.</dd> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Browser_compatibility">Compatibilità con i browser</a></dt> - <dd>Scopri esattamente quali browser supportano Persona.</dd> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Internationalization">Internazionalizzazione</a></dt> - <dd>Scopri come Persona gestisce lingue diverse.</dd> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/The_implementor_s_guide">Guida dell'implementatore</a></dt> - <dd>Suggerimenti dai siti che hanno già aggiunto il supporto a Persona.</dd> -</dl> -</div> - -<div class="column-third"> -<h3 id="Risorse">Risorse</h3> - -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Libraries_and_plugins">Librerie e plugin</a></dt> - <dd>Trova librerie semplici da aggiungere per il tuo linguaggio di programmazione, framework web, blog o content management system preferito.</dd> - <dt><a class="link-https" href="https://github.com/mozilla/browserid-cookbook">Ricette per Persona</a></dt> - <dd>Codice sorgente di esempio per i siti che usano Persona. Include esempi per C# (MVC3), PHP, Node.js e altri.</dd> - <dt><a href="https://developer.mozilla.org/it/docs/persona/marchio">Linee guida per l'interfaccia utente</a></dt> - <dd>Come presentare l'autenticazione con Persona ai propri utenti.</dd> -</dl> -</div> -</div> - -<hr> -<h2 id="Diventare_un_Identity_Provider">Diventare un Identity Provider</h2> - -<p>Se sei un provider di email o un servizio di provider di identificazione, controlla i link qui sotto per scoprire come diventare un Identity Provider di Persona.</p> - -<div class="column-container"> -<div class="column-third"> -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Identity_Provider_Overview">Panoramica di Identity Provider</a></dt> - <dd>Una visione di alto livello su Persona Identity Providers.</dd> -</dl> -</div> - -<div class="column-third"> -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Implementing_a_Persona_IdP">Implementare un Identity Provider</a></dt> - <dd>Una guida minuziosa ai dettagli tecnici su come diventare un Identity Provider.</dd> -</dl> -</div> - -<div class="column-third"> -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/.well-known-browserid">.well-known/browserid</a></dt> - <dd>Una panoramica sul file <code>.well-known/browserid</code>, che gli Identity Provider utilizzano per indicare il proprio supporto al protocollo.</dd> -</dl> -</div> -</div> - -<hr> -<h2 id="Il_progetto_Persona">Il progetto Persona</h2> - -<div class="column-container"> -<div class="column-third"> -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Glossary">Glossario</a></dt> - <dd>Definizioni sulla terminologia di BrowserID e Persona.</dd> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/FAQ">FAQ</a></dt> - <dd>Risposte alle domande più comuni.</dd> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Protocol_Overview">Visione di insieme del protocollo</a></dt> - <dd>Una visione di insieme tecnica a medio livello del protocollo BrowserID sottostante.</dd> -</dl> -</div> - -<div class="column-third"> -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/persona/Crypto">Crittografia</a></dt> - <dd>Informazioni riguardo i concetti crittografici che sono alla base di Persona e BrowserID.</dd> - <dt><a class="link-https" href="https://github.com/mozilla/id-specs/blob/prod/browserid/index.md">Specifiche</a></dt> - <dd>Qui si trovano i dettagli più tecnici.</dd> -</dl> -</div> - -<div class="column-third"> -<dl> - <dt><a href="https://developer.mozilla.org/it/docs/Persona/Bootstrapping_Persona">Il sito di Persona</a></dt> - <dd>Per far funzionare Persona stiamo ospitando tre servizi su <a class="link-https" href="https://login.persona.org" rel="freelink">https://login.persona.org</a>: un Identity Provider per quando gli altri non funzionano, un implementazione delle API {{domxref("navigator.id")}}, e un servizio di veifica.</dd> - <dt><a href="https://github.com/mozilla/browserid">Il codice sorgente di Persona</a></dt> - <dd>Il codice sorgete di persona è su GitHub. Le pull request sono le benvenute!</dd> -</dl> -</div> -</div> - -<h2 id="Subnav">Subnav</h2> - -<ol> - <li><a href="https://developer.mozilla.org/it/docs/Persona#">Usare persona su un sito</a> - - <ol> - <li><a href="https://developer.mozilla.org/it/Persona/Why_Persona" title="Why Persona?">Perché usare Persona?</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Quick_setup" title="Quick Start">Per cominciare</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/The_implementor_s_guide" title="Implementor's Guide">Consigli per implementare Persona</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Security_Considerations" title="Security Considerations">Considerazioni sulla sicurezza</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Browser_compatibility" title="Browser compatibility">Compatibilità con i browser</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Internationalization" title="Internationalization">Internazionalizzazione</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/The_navigator.id_API" title="The navigator.id API">L'API navigator.id</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Remote_Verification_API" title="Remote Verification API">L'API di verifica remota</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Libraries_and_plugins" title="Libraries and plugins">Librerie e plugin</a></li> - <li><a href="https://developer.mozilla.org/it/docs/persona/marchio" title="User interface guidelines">Linee guida per l'interfaccia utente</a></li> - </ol> - </li> - <li><a href="https://developer.mozilla.org/it/docs/Persona#">Diventare un Identity Provider</a> - <ol> - <li><a href="https://developer.mozilla.org/it/Persona/Identity_Provider_Overview" title="IdP Overview">Visione di insieme di Identity Provider</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Implementing_a_Persona_IdP" title="Implementing an IdP">Implementare un Identity Provider</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/.well-known-browserid" title=".well-known-browserid format">Formato .well-known-browserid</a></li> - </ol> - </li> - <li><a href="https://developer.mozilla.org/it/docs/Persona#">Il progetto Persona</a> - <ol> - <li><a href="https://developer.mozilla.org/it/Persona/Glossary" title="Glossary">Glossario</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/FAQ" title="FAQ">FAQ</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Bootstrapping_Persona" title="Persona hosted services">Servizi ospitati di Persona</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Protocol_Overview" title="Protocol overview">Visione di insieme del protocollo</a></li> - <li><a href="https://developer.mozilla.org/it/Persona/Crypto" title="Crypto">Crittografia</a></li> - </ol> - </li> -</ol> -</div> diff --git a/files/it/archive/mozilla/persona/internationalization/index.html b/files/it/archive/mozilla/persona/internationalization/index.html deleted file mode 100644 index 29ebccf30a..0000000000 --- a/files/it/archive/mozilla/persona/internationalization/index.html +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Internazionalizzazione -slug: Archive/Mozilla/Persona/Internationalization -translation_of: Archive/Mozilla/Persona/Internationalization ---- -<h2 id="What's_localized_in_Persona">What's localized in Persona</h2> -<p>In the future, the user interface for signing into sites with Persona will be directly integrated into the browser, and thus localized along with the browser's own localization. For browsers without integrated support, Persona's user interface consists of a series of dialogs served from <a href="https://login.persona.org" title="https://login.persona.org">login.persona.org</a>. These dialogs are translated by a team of community volunteers, and more than 45 locales are currently <a href="https://github.com/mozilla/browserid/blob/dev/config/l10n-prod.json" title="https://github.com/mozilla/browserid/blob/dev/config/l10n-prod.json">enabled in production</a>.</p> -<h2 id="How_Persona_chooses_localizations">How Persona chooses localizations</h2> -<p>The Persona service selects a language using the <code>Accept-Language</code> header sent alongside the browser's requests. The algorithm used to map an <code>Accept-Language</code> header to a language is the same as that used by <code>mozilla.org</code>:</p> -<ol> - <li>For each language tag in the <code>Accept-Language</code> header: - <ul> - <li>check if we have an exact match for the language identified by the language tag</li> - <li>check if we have an exact match for the language identified by the first part of the language tag</li> - </ul> - </li> - <li>If a match can't be made using rule (1), fall back to en-US. However, en or en-US is almost always the last accept-lang header sent by most browsers.</li> -</ol> -<p>For example, the table below lists the language selected for various <code>Accept-Language</code> headers, if the following locales were supported: <code>en-US, es, es-MX</code>:</p> -<table> - <thead> - <tr> - <th scope="col"><strong>Accept-Language Header</strong></th> - <th scope="col"><strong>Selected language</strong></th> - </tr> - </thead> - <tbody> - <tr> - <td><code>es-AR,es;q=0.8,en-us;q=0.5</code></td> - <td><code>es</code></td> - </tr> - <tr> - <td><code>es-MX,es;q=0.8,en-us;q=0.5</code></td> - <td><code>es-MX</code></td> - </tr> - <tr> - <td><code>e</code><code>s-es,en-us;q=0.5</code></td> - <td><code>en-US</code></td> - </tr> - <tr> - <td><code>e</code><code>s-es</code></td> - <td><code>en-US</code></td> - </tr> - </tbody> -</table> -<p>There is currently no way for a website to force the dialogs to appear in another language. This is because the Persona UI is logically (and in future native implementations will actually be) part of the browser UI, so its language should be consistent with the language selected for the browser.</p> -<h2 id="How_you_can_help">How you can help</h2> -<p>Persona uses Mozilla Verbatim to help volunteers create new translations. If you want to help out, read about <a href="https://developer.mozilla.org/en-US/docs/Localizing_with_Verbatim" title="https://developer.mozilla.org/en-US/docs/Localizing_with_Verbatim">getting started with Verbatim</a> and check out the <a href="https://localize.mozilla.org/projects/browserid/" title="https://localize.mozilla.org/projects/browserid/">"BrowserID" project</a> on Verbatim.</p> -<p> </p> diff --git a/files/it/archive/mozilla/persona/libraries_and_plugins/index.html b/files/it/archive/mozilla/persona/libraries_and_plugins/index.html deleted file mode 100644 index 2e11654b68..0000000000 --- a/files/it/archive/mozilla/persona/libraries_and_plugins/index.html +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: Librerie e plugin -slug: Archive/Mozilla/Persona/Libraries_and_plugins -translation_of: Archive/Mozilla/Persona/Libraries_and_plugins ---- -<p>Want to use Persona on your website or blog? Implementing Persona from scratch <a href="/en-US/docs/Persona/Quick_Setup" title="/en-US/docs/Persona/Quick_Setup">is easy</a>, but the plugins and libraries listed here might get you going faster!<br> - <br> - This page lists three types of libraries:<br> - <br> - 1. <strong>Plugins</strong> that integrate Persona with existing frameworks and content management systems<br> - 2. <strong>Utility libraries</strong> that are useful when building new plugins or integrating Persona into a site from scratch<br> - 3. <strong>Everything else</strong> related to Persona, including libraries for turning your domain into a Persona Identity Provider<br> - <br> - This is a community-maintained list. If you've created a library or plugin, please add it to this page.</p> -<div class="note"> - This page is currently being revised and some plugins may be out of date. Please review plugins before using them.</div> -<h2 id="Plugins">Plugins</h2> -<h3 id="Clojure">Clojure</h3> -<ul> - <li>Noir: <a href="https://github.com/tmarble/nongrata" title="https://github.com/tmarble/nongrata">https://github.com/tmarble/nongrata</a></li> - <li>ring / cemerick.friend / cljs: <a href="https://github.com/osbert/persona-kit" title="https://github.com/osbert/persona-kit">https://github.com/osbert/persona-kit</a></li> -</ul> -<h3 id="Cold_Fusion">Cold Fusion</h3> -<ul> - <li>CFML: <a href="https://github.com/gregmoser/cfpersona" title="https://github.com/gregmoser/cfpersona">https://github.com/gregmoser/cfpersona</a></li> -</ul> -<h3 id="Haskell">Haskell</h3> -<ul> - <li>Yesod: <a href="https://github.com/yesodweb/authenticate" title="https://github.com/yesodweb/authenticate">https://github.com/yesodweb/authenticate</a></li> -</ul> -<h3 id="Java">Java</h3> -<ul> - <li>Spring: <a href="https://github.com/webdetails/SpringSecurityBrowserID" title="https://github.com/webdetails/SpringSecurityBrowserID">https://github.com/webdetails/SpringSecurityBrowserID</a></li> - <li>Lutece: <a href="http://dev.lutece.paris.fr/plugins/module-mylutece-persona/" title="https://dev.lutece.paris.fr/plugins/module-mylutece-persona/">http://dev.lutece.paris.fr/plugins/module-mylutece-persona/</a></li> -</ul> -<h3 id="JavaScript">JavaScript</h3> -<ul> - <li>Mootools: <a href="http://mootools.net/forge/p/browserid" title="http://mootools.net/forge/p/browserid">http://mootools.net/forge/p/browserid</a></li> - <li>jQuery: <a href="https://github.com/altryne/browserID-jQuery" title="https://github.com/altryne/browserID-jQuery">https://github.com/altryne/browserID-jQuery</a></li> - <li>Meteor: <a href="https://github.com/vladikoff/meteor-accounts-persona" title="https://github.com/vladikoff/meteor-accounts-persona">https://github.com/vladikoff/meteor-accounts-persona</a></li> -</ul> -<h3 id="Node.js">Node.js</h3> -<ul> - <li>Express: <a href="https://github.com/jbuck/express-persona" title="https://github.com/jbuck/express-persona">https://github.com/jbuck/express-persona</a></li> - <li>Express / Jungles: <a href="https://npmjs.org/package/jungles-auth-persona" title="https://npmjs.org/package/jungles-auth-persona">https://npmjs.org/package/jungles-auth-persona</a></li> - <li>Passport: <a href="https://github.com/jaredhanson/passport-browserid" title="https://github.com/jaredhanson/passport-browserid">https://github.com/jaredhanson/passport-browserid</a></li> - <li>Express / connect - connect-auth: <a href="https://github.com/ciaranj/connect-auth" title="https://github.com/ciaranj/connect-auth">https://github.com/ciaranj/connect-auth</a></li> - <li>Persona + LevelDB session storage: <a href="https://github.com/maxogden/doorknob" title="/en-US/docs/">https://github.com/maxogden/doorknob</a></li> -</ul> -<h3 id="PHP">PHP</h3> -<ul> - <li>CakePHP: <a href="https://github.com/overflow636/ofbid" title="https://github.com/overflow636/ofbid">https://github.com/overflow636/ofbid</a> and <a href="https://github.com/markomarkovic/cakephp-plugin-persona" title="https://github.com/markomarkovic/cakephp-plugin-persona">https://github.com/markomarkovic/cakephp-plugin-persona</a></li> - <li>DokuWiki: <a href="https://github.com/Rudloff/dokuwiki-browserid" title="https://github.com/Rudloff/dokuwiki-browserid">https://github.com/Rudloff/dokuwiki-browserid</a></li> - <li>Dotclear: <a href="http://plugins.dotaddict.org/dc2/details/browserID" title="http://plugins.dotaddict.org/dc2/details/browserID">http://plugins.dotaddict.org/dc2/details/browserID</a></li> - <li>Drupal: <a href="https://drupal.org/project/persona" title="https://drupal.org/project/persona">https://drupal.org/project/persona</a></li> - <li>Elgg: <a href="http://community.elgg.org/plugins/1154520/1.0/persona" title="/en-US/docs/">http://community.elgg.org/plugins/1154520/1.0/persona</a></li> - <li>Mediawiki: <a href="http://www.mediawiki.org/wiki/Extension:Persona">http://www.mediawiki.org/wiki/Extension:Persona</a></li> - <li>Joomla: <a href="http://extensions.joomla.org/extensions/access-a-security/authentication-cloud-based/18567" title="http://extensions.joomla.org/extensions/access-a-security/authentication-cloud-based/18567">http://extensions.joomla.org/extensions/access-a-security/authentication-cloud-based/18567</a></li> - <li>Midgard MVC: <a href="https://github.com/midgardproject/midgardmvc_core/blob/master/services/authentication/browserid.php" title="https://github.com/midgardproject/midgardmvc_core/blob/master/services/authentication/browserid.php">https://github.com/midgardproject/midgardmvc_core/blob/master/services/authentication/browserid.php</a></li> - <li>MyBB: <a href="https://github.com/Rudloff/mybb-browserid" title="https://github.com/Rudloff/mybb-browserid">https://github.com/Rudloff/mybb-browserid</a></li> - <li>SPIP: <a href="http://www.spip-contrib.net/BrowserID" title="http://www.spip-contrib.net/BrowserID">http://www.spip-contrib.net/BrowserID</a></li> - <li>Symfony2: <a href="https://github.com/Proxiweb/PersonaBundle" title="https://github.com/Proxiweb/PersonaBundle">https://github.com/Proxiweb/PersonaBundle</a>, <a href="https://github.com/bitgrave/BGPersonaBundle" title="https://github.com/bitgrave/BGPersonaBundle">https://github.com/bitgrave/BGPersonaBundle</a>, <a href="https://packagist.org/packages/champs-libres/persona-user-bundle">https://packagist.org/packages/champs-libres/persona-user-bundle</a></li> - <li>Tiki: <a href="http://dev.tiki.org/Mozilla+Persona" title="http://dev.tiki.org/Mozilla+Persona">http://dev.tiki.org/Mozilla+Persona</a></li> - <li>WordPress / bbPress 2: <a href="http://wordpress.org/extend/plugins/browserid/" title="http://wordpress.org/extend/plugins/browserid/">http://wordpress.org/extend/plugins/browserid/</a></li> - <li>Yii framework: <a href="https://github.com/KryDos/persona-yii">https://github.com/KryDos/persona-yii</a></li> -</ul> -<h3 id="Python">Python</h3> -<ul> - <li>CherryPy: <a href="https://bitbucket.org/jaraco/jaraco.persona">https://bitbucket.org/jaraco/jaraco.persona</a></li> - <li>Django: <a href="https://github.com/mozilla/django-browserid" title="https://github.com/mozilla/django-browserid">https://github.com/mozilla/django-browserid</a> (see <a href="http://godjango.com/11-browser-id/" title="http://godjango.com/11-browser-id/">screencast</a>)</li> - <li>Django Social Auth: <a href="https://github.com/omab/django-social-auth/blob/master/social_auth/backends/browserid.py" title="https://github.com/omab/django-social-auth/blob/master/social_auth/backends/browserid.py">https://github.com/omab/django-social-auth/blob/master/social_auth/backends/browserid.py</a></li> - <li>Django 1.5 and Python 3: <a href="https://github.com/mozillaperu/MozTanta-Persona" title="/en-US/docs/">https://github.com/mozillaperu/MozTanta-Persona</a></li> - <li>Flask: <a href="http://pypi.python.org/pypi/Flask-BrowserID" title="http://pypi.python.org/pypi/Flask-BrowserID">http://pypi.python.org/pypi/Flask-BrowserID</a></li> - <li>Google App Engine: <a href="https://github.com/psawaya/BrowserID-GAE" title="https://github.com/psawaya/BrowserID-GAE">https://github.com/psawaya/BrowserID-GAE</a></li> - <li>Pyramid: <a href="http://www.rfk.id.au/blog/entry/painless-auth-pyramid-browserid/" title="http://www.rfk.id.au/blog/entry/painless-auth-pyramid-browserid/">http://www.rfk.id.au/blog/entry/painless-auth-pyramid-browserid/</a></li> - <li>Pyramid: <a href="https://github.com/madjar/pyramid_persona/" title="https://github.com/madjar/pyramid_persona/">https://github.com/madjar/pyramid_persona/</a> (see <a href="http://compiletoi.net/quick-authentication-on-pyramid-with-persona.html" title="http://compiletoi.net/quick-authentication-on-pyramid-with-persona.html">blog post</a>)</li> - <li>Repoze: <a href="https://github.com/mozilla-services/repoze.who.plugins.browserid" title="https://github.com/mozilla-services/repoze.who.plugins.browserid">https://github.com/mozilla-services/repoze.who.plugins.browserid</a></li> - <li>Tornado: <a href="http://www.peterbe.com/plog/integrate-browserid-in-a-tornado-web-app" title="http://www.peterbe.com/plog/integrate-browserid-in-a-tornado-web-app">http://www.peterbe.com/plog/integrate-browserid-in-a-tornado-web-app</a></li> - <li>Twisted: <a href="https://github.com/warner/browserid-cred" title="https://github.com/warner/browserid-cred">https://github.com/warner/browserid-cred</a></li> - <li>web.py: <a href="https://github.com/oscarfroberg/browserid-webpy" title="https://github.com/oscarfroberg/browserid-webpy">https://github.com/oscarfroberg/browserid-webpy</a></li> - <li>WSGI: <a href="https://github.com/ianb/wsgibrowserid" title="https://github.com/ianb/wsgibrowserid">https://github.com/ianb/wsgibrowserid</a></li> -</ul> -<h3 id="Ruby">Ruby</h3> -<ul> - <li>Devise: <a href="https://rubygems.org/gems/devise-browserid" title="https://rubygems.org/gems/devise-browserid">https://rubygems.org/gems/devise-browserid</a></li> - <li>Devise: <a href="https://github.com/denschub/devise_browserid_authenticatable" title="https://github.com/denschub/devise_browserid_authenticatable">https://github.com/denschub/devise_browserid_authenticatable</a></li> - <li>OmniAuth: <a href="https://github.com/intridea/omniauth-browserid" title="https://github.com/intridea/omniauth-browserid">https://github.com/intridea/omniauth-browserid</a></li> - <li>Rails: <a href="http://rubygems.org/gems/browserid-rails" title="http://rubygems.org/gems/browserid-rails">http://rubygems.org/gems/browserid-rails</a></li> - <li>Sinatra: <a href="http://rubygems.org/gems/sinatra-browserid" title="http://rubygems.org/gems/sinatra-browserid">http://rubygems.org/gems/sinatra-browserid</a></li> - <li>Warden / Rack: <a href="https://rubygems.org/gems/warden-browserid" title="/en-US/en-US/docs/">https://rubygems.org/gems/warden-browserid</a></li> -</ul> -<h3 id="Perl">Perl</h3> -<ul> - <li>Plack: <a href="https://metacpan.org/release/Plack-Middleware-Auth-BrowserID">https://metacpan.org/release/Plack-Middleware-Auth-BrowserID</a></li> -</ul> -<h3 id="Erlang">Erlang</h3> -<ul> - <li>CouchDB: <a href="https://github.com/iriscouch/browserid_couchdb" title="https://github.com/iriscouch/browserid_couchdb">https://github.com/iriscouch/browserid_couchdb</a></li> -</ul> -<h3 id="Miscellaneous">Miscellaneous</h3> -<ul> - <li>Apache: <a href="https://github.com/mozilla/mod_authnz_persona" title="/Link_Type_Article_Title_Lookup_/_Link_Text_Attachments_URL">https://github.com/mozilla/mod_authnz_persona</a></li> - <li>Cyrus SASL: <a href="https://github.com/ozten/sasl-browserid" title="https://github.com/ozten/sasl-browserid">https://github.com/ozten/sasl-browserid</a></li> - <li>PhoneGap: <a href="https://github.com/couchbaselabs/cordova-browserid" title="https://github.com/couchbaselabs/cordova-browserid">https://github.com/couchbaselabs/cordova-browserid</a></li> -</ul> -<p>Didn't see your language or framework listed? <a href="http://identity.mozilla.com/post/31008721633/" title="http://identity.mozilla.com/post/31008721633/">LoginRadius</a>, a hosted authentication widget, offers Persona integration for a wide variety of platforms.</p> -<h2 id="Verification_Libraries">Verification Libraries</h2> -<h3 id="Go">Go</h3> -<ul> - <li>persona: <a href="https://github.com/sauerbraten/persona">https://github.com/sauerbraten/persona</a></li> -</ul> -<h3 id="Java_2" style="line-height: 20px;">Java</h3> -<ul> - <li><span style="color: rgb(102, 102, 102); font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 16.363636016845703px; line-height: 20px;">Simple Java BrowserID Verifier</span>: <a href="https://github.com/user454322/browserid-verifier/">https://github.com/user454322/browserid-verifier</a></li> -</ul> -<h3 id="Node.js_2">Node.js</h3> -<ul> - <li>browserid-verify: <a href="https://npmjs.org/package/browserid-verify">https://npmjs.org/package/browserid-verify</a></li> -</ul> -<h3 id="Perl_2">Perl</h3> -<ul> - <li>Net::BrowserID::Verify: <a href="http://search.cpan.org/perldoc?Net%3A%3ABrowserID%3A%3AVerify">http://search.cpan.org/perldoc?Net::BrowserID::Verify</a></li> -</ul> -<h3 id="PHP_2">PHP</h3> -<ul> - <li>auth-browserid: <a href="https://github.com/fmarier/auth-browserid">https://github.com/fmarier/auth-browserid</a></li> -</ul> -<h3 id="Ruby_2">Ruby</h3> -<ul> - <li>browserid-verify: <a href="https://rubygems.org/gems/browserid-verify">https://rubygems.org/gems/browserid-verify</a></li> -</ul> -<h2 id="Utility_Libraries">Utility Libraries</h2> -<h3 id="C">C</h3> -<ul> - <li><a href="https://github.com/PADL/gss_browserid" title="https://github.com/PADL/gss_browserid">https://github.com/PADL/gss_browserid</a> (libbrowserid component)</li> -</ul> -<h3 id="Go_2">Go</h3> -<ul> - <li><a href="https://github.com/elathan/gobrowserid" title="https://github.com/elathan/gobrowserid">https://github.com/elathan/gobrowserid</a></li> -</ul> -<h3 id="Haskell_2">Haskell</h3> -<ul> - <li><a href="http://hackage.haskell.org/package/authenticate" title="http://hackage.haskell.org/package/authenticate">http://hackage.haskell.org/package/authenticate</a></li> -</ul> -<h3 id=".Net">.Net</h3> -<ul> - <li><a href="https://github.com/cvrajeesh/NBrowserID" title="https://github.com/cvrajeesh/NBrowserID">https://github.com/cvrajeesh/NBrowserID</a></li> - <li><a href="http://www.codeguru.com/csharp/.net/net_asp/using-browserid-authentication-in-asp.net-web-sites.htm" title="http://www.codeguru.com/csharp/.net/net_asp/using-browserid-authentication-in-asp.net-web-sites.htm">http://www.codeguru.com/csharp/.net/net_asp/using-browserid-authentication-in-asp.net-web-sites.htm</a></li> - <li><a href="https://github.com/fernandozamoraj/BrowserIdDemoWithMVC3" title="https://github.com/fernandozamoraj/BrowserIdDemoWithMVC3">https://github.com/fernandozamoraj/BrowserIdDemoWithMVC3</a> (see <a href="http://fernandozamorajimenez.blogspot.com/2012/04/integrating-browserid-with-mvc3.html" title="http://fernandozamorajimenez.blogspot.com/2012/04/integrating-browserid-with-mvc3.html">blog post</a>)</li> - <li><a href="https://github.com/sergiotapia/ASP.Net-MVC3-Persona-Demo" title="https://github.com/sergiotapia/ASP.Net-MVC3-Persona-Demo">https://github.com/sergiotapia/ASP.Net-MVC3-Persona-Demo</a></li> - <li><a href="https://www.nuget.org/packages/Persona">https://www.nuget.org/packages/Persona</a> (MVC3, 4, & 5; integrates with ASP.NET authentication)</li> -</ul> -<h3 id="Node.js_3">Node.js</h3> -<ul> - <li><a href="https://github.com/substack/persona-id" title="https://github.com/substack/persona-id">https://github.com/substack/persona-id</a></li> - <li><a href="https://github.com/lloyd/node-browserid" title="https://github.com/lloyd/node-browserid">https://github.com/lloyd/node-browserid</a></li> -</ul> -<h3 id="PHP_3">PHP</h3> -<ul> - <li><a href="https://github.com/Falco20019/php-browseridlib" title="https://github.com/Falco20019/php-browseridlib">https://github.com/Falco20019/php-browseridlib</a></li> - <li><a href="https://github.com/raymondjavaxx/php5-browserid" title="https://github.com/raymondjavaxx/php5-browserid">https://github.com/raymondjavaxx/php5-browserid</a></li> -</ul> -<h3 id="Python_2">Python</h3> -<ul> - <li><a href="https://github.com/mozilla/PyBrowserID" title="https://github.com/mozilla/PyBrowserID">https://github.com/mozilla/PyBrowserID</a></li> -</ul> -<h3 id="UrWeb">Ur/Web</h3> -<ul> - <li><a href="https://github.com/doublec/urweb-persona">https://github.com/doublec/urweb-persona</a></li> -</ul> -<h2 id="Everything_Else">Everything Else</h2> -<h3 id="Perl_3">Perl</h3> -<ul> - <li>Perl/CGI IdP: <a href="https://github.com/benkard/mulkyid" title="https://github.com/benkard/mulkyid">https://github.com/benkard/mulkyid</a></li> -</ul> -<h3 id="Python_3">Python</h3> -<ul> - <li>WSGI IdP: <a href="https://bitbucket.org/djc/persona-totp" title="https://bitbucket.org/djc/persona-totp">https://bitbucket.org/djc/persona-totp</a></li> -</ul> -<h3 id="Ruby_3">Ruby</h3> -<ul> - <li>Rack IdP: <a href="https://rubygems.org/gems/browserid-provider" title="https://rubygems.org/gems/browserid-provider">https://rubygems.org/gems/browserid-provider</a> (see <a href="https://rin.no/category/browserid-2/" title="https://rin.no/category/browserid-2/">blog post</a>)</li> -</ul> -<h3 id="PHP_4">PHP</h3> -<ul> - <li>Symfony2 IdP: <a href="https://github.com/gigablah/GBPersonaProviderBundle" title="https://github.com/gigablah/persona-provider-bundle">https://github.com/gigablah/GBPersonaProviderBundle</a></li> -</ul> -<h3 id="Racket">Racket</h3> -<ul> - <li>web-server module: <a href="https://github.com/cosmez/racket-persona">https://github.com/cosmez/racket-persona</a></li> -</ul> -<h3 id="Orchard_CMS" style="line-height: 20px;">Orchard CMS</h3> -<ul> - <li>Mozilla persona sign in module: <a href="https://github.com/grapto/Contrib.Persona">https://github.com/grapto/Contrib.Persona</a></li> -</ul> diff --git a/files/it/archive/mozilla/persona/marchio/index.html b/files/it/archive/mozilla/persona/marchio/index.html deleted file mode 100644 index e7ac828695..0000000000 --- a/files/it/archive/mozilla/persona/marchio/index.html +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: Personalizzazione dei bottoni -slug: Archive/Mozilla/Persona/marchio -translation_of: Archive/Mozilla/Persona/User_interface_guidelines ---- -<h2 id="I_bottoni_per_l'accesso_con_Persona">I bottoni per l'accesso con Persona</h2> -<h3 id="Immagini">Immagini</h3> -<p>I bottoni "Accesso con Persona" sono disponibili in tre colorazioni:</p> -<p>Scarica (.psd)</p> -<h3 id="Versioni_basate_su_CSS">Versioni basate su CSS</h3> -<p><a href="http://sawyerhollenshead.com/" title="http://sawyerhollenshead.com/">Sawyer Hollenshead</a> ha creato un set eccellente di bottoni basati su CSS. <a href="http://dev.sawyerhollenshead.com/mozilla/buttons/buttons.html" title="http://dev.sawyerhollenshead.com/mozilla/buttons/buttons.html">Demo</a> / Scarica (.zip)</p> -<h2 id="Ulteriori_informazioni">Ulteriori informazioni</h2> -<p>Puoi trovare ulteriori informazioni sul visual design di Persona alla pagina <a href="http://people.mozilla.org/~smartell/persona/" title="http://people.mozilla.org/~smartell/persona/">style primer di Sean Martell </a>(disponibile solo in Inglese).</p> diff --git a/files/it/archive/mozilla/persona/quick_setup/index.html b/files/it/archive/mozilla/persona/quick_setup/index.html deleted file mode 100644 index 076e004ca1..0000000000 --- a/files/it/archive/mozilla/persona/quick_setup/index.html +++ /dev/null @@ -1,273 +0,0 @@ ---- -title: Setup veloce -slug: Archive/Mozilla/Persona/Quick_Setup -translation_of: Archive/Mozilla/Persona/Quick_Setup ---- -<p>Aggiungere il sistema di login Persona al tuo sito richiede solo cinque passaggi:</p> - -<ol> - <li>Includere la libreria JavaScript di Persona nelle tue pagine.</li> - <li>Aggiungere i bottoni di “login” e “logout”.</li> - <li>Watch for login and logout actions.</li> - <li>Verificare le credenziali dell'utente.</li> - <li>Rivedere le best practices.</li> -</ol> - -<p>Dovresti riuscire a implementarlo e farlo funzionare in un solo pomeriggio, ma innanzitutto: se hai intenzione di usare Persona sul tuo sito, <em>per piacere</em> prendi un momento per sottoscrivere la mailing list <a href="https://mail.mozilla.org/listinfo/persona-notices">Persona notices</a>. Genera un traffico estremamente basso, viene solo usata per annunciare cambiamenti o questioni di sicurezza che potrebbero avere un impatto negativo sul tuo sito.</p> - -<h2 id="Step_1_Includi_la_libreria_di_Persona">Step 1: Includi la libreria di Persona</h2> - -<p>Persona é progettato per essere indipendente dal browser e funzionare bene su <a href="https://developer.mozilla.org/docs/persona/Browser_compatibility">tutti i maggiori browser per desktop e mobile</a>.</p> - -<p>Ci aspettiamo che in futuro i browser supporteranno nativamente Persona, ma nel frattempo forniamo una libreria JavaScript che implementa completamente l'interfaccia utente e la parte client-side del protocollo. Includendo questa libreria, i tuoi utenti saranno in grado di registrarsi con Persona anche se il loro browser non lo supporta nativamente.</p> - -<p>Questa libreria è caricata nella tua pagina, Persona funziona necessita di ({{ domxref("navigator.id.watch()", "watch()") }}, {{ domxref("navigator.id.request()", "request()") }}, and {{ domxref("navigator.id.logout()", "logout()") }}) sarà disponibile al mondo navigator.id object.</p> - -<p>Includere la libreria JavaScript di Persona, tu puoi mettere questo script tag in fondo al <code>body</code> della pagina:</p> - -<pre class="brush: html;"><script src="https://login.persona.org/include.js"></script> -</pre> - -<p><strong>Devi</strong> includere questo script in ogni pagina dove gli utenti utilizzeranno Persona {{ domxref("navigator.id") }}. Ciò perchè Persona è ancora in svilippo, tu non dovresti auto accogliere il file <code>include.js</code></p> - -<h2 id="Step_2_Aggiungere_il_bottone_di_login_e_di_logout">Step 2: Aggiungere il bottone di login e di logout</h2> - -<p>Because Persona is designed as a DOM API, you must call functions when a user clicks a login or logout button on your site. To open the Persona dialog and prompt the user to log in, you should invoke {{ domxref("navigator.id.request()") }}. For logout, invoke {{ domxref("navigator.id.logout()") }}. Note, the call to {{ domxref("navigator.id.logout()", "logout()") }} <em>must</em> be made in the click handler of the logout button.</p> - -<p>For example:</p> - -<pre class="brush: js;">var signinLink = document.getElementById('signin'); -if (signinLink) { - signinLink.onclick = function() { navigator.id.request(); }; -} - -var signoutLink = document.getElementById('signout'); -if (signoutLink) { - signoutLink.onclick = function() { navigator.id.logout(); }; -} -</pre> - -<p>What should those buttons look like? Check out our <a href="https://developer.mozilla.org/docs/persona/branding">Branding Resources</a> page for premade images and CSS-based buttons!</p> - -<h2 id="Step_3_Watch_for_login_and_logout_actions">Step 3: Watch for login and logout actions</h2> - -<p>For Persona to function, you need to tell it what to do when a user logs in or out. This is done by calling the {{ domxref("navigator.id.watch()") }} function and supplying three parameters:</p> - -<ol> - <li> - <p>The email address of the user currently logged into your site from this computer, or <code>null</code> if no one is logged in. For example, you might examine the browser's cookies to determine who is signed in.</p> - </li> - <li> - <p>A function to invoke when an <code>onlogin</code> action is triggered. This function is passed a single parameter, an “identity assertion,” which must be verified.</p> - </li> - <li> - <p>A function to invoke when an <code>onlogout</code> action is triggered. This function is not passed any parameters.</p> - </li> -</ol> - -<div class="note style-wrap"> -<p><strong>Note:</strong> You must always include both <code>onlogin</code> and <code>onlogout</code> when you call {{ domxref("navigator.id.watch()") }}.</p> -</div> - -<p>For example, if you currently think Bob is logged into your site, you might do this:</p> - -<pre class="brush: js;">var currentUser = 'bob@example.com'; - -navigator.id.watch({ - loggedInUser: currentUser, - onlogin: function(assertion) { - // A user has logged in! Here you need to: - // 1. Send the assertion to your backend for verification and to create a session. - // 2. Update your UI. - $.ajax({ /* <-- This example uses jQuery, but you can use whatever you'd like */ - type: 'POST', - url: '/auth/login', // This is a URL on your website. - data: {assertion: assertion}, - success: function(res, status, xhr) { window.location.reload(); }, - error: function(xhr, status, err) { alert("Login failure: " + err); } - }); - }, - onlogout: function() { - // A user has logged out! Here you need to: - // Tear down the user's session by redirecting the user or making a call to your backend. - // Also, make sure loggedInUser will get set to null on the next page load. - // (That's a literal JavaScript null. Not false, 0, or undefined. null.) - $.ajax({ - type: 'POST', - url: '/auth/logout', // This is a URL on your website. - success: function(res, status, xhr) { window.location.reload(); }, - error: function(xhr, status, err) { alert("Logout failure: " + err); } - }); - } -}); -</pre> - -<p>In this example, both <code>onlogin</code> and <code>onlogout</code> are implemented by making an asynchronous <code>POST</code> request to your site’s backend. The backend then logs the user in or out, usually by setting or deleting information in a session cookie. Then, if everything checks out, the page reloads to take into account the new login state.</p> - -<p>You can, of course, use AJAX to implement this without reloading or redirecting, but that’s beyond the scope of this tutorial.</p> - -<p>Here is another example, this time not using jQuery.</p> - -<pre class="brush: js;">function simpleXhrSentinel(xhr) { - return function() { - if (xhr.readyState == 4) { - if (xhr.status == 200) - // reload page to reflect new login state - window.location.reload(); - else - alert("XMLHttpRequest error: " + xhr.status); } } } - -function verifyAssertion(assertion) { - // Your backend must return HTTP status code 200 to indicate successful - // verification of user's email address and it must arrange for the binding - // of currentUser to said address when the page is reloaded - var xhr = new XMLHttpRequest(); - xhr.open("POST", "/xhr/sign-in", true); - // see http://www.openjs.com/articles/ajax_xmlhttp_using_post.php - var param = "assert="+assertion; - xhr.setRequestHeader("Content-type", "application/x-www-form-urlencoded"); - xhr.setRequestHeader("Content-length", param.length); - xhr.setRequestHeader("Connection", "close"); - xhr.send(param); // for verification by your backend - - xhr.onreadystatechange = simpleXhrSentinel(xhr); } - -function signoutUser() { - // Your backend must return HTTP status code 200 to indicate successful - // sign out (usually the resetting of one or more session variables) and - // it must arrange for the binding of currentUser to 'null' when the page - // is reloaded - var xhr = new XMLHttpRequest(); - xhr.open("GET", "/xhr/sign-out", true); - xhr.send(null); - xhr.onreadystatechange = simpleXhrSentinel(xhr); } - -// Go! -navigator.id.watch( { - loggedInUser: currentUser, - onlogin: verifyAssertion, - onlogout: signoutUser } ); -</pre> - -<p>You <strong>must</strong> call <code>navigator.id.watch()</code> on every page with a login or logout button. To support Persona enhancements like automatic login and global logout for your users, you <strong>should</strong> call this function on every page of your site.</p> - -<p>Persona will compare the email address you've passed into <code>loggedInUser</code> with its own knowledge of whether a user is currently logged in, and who they are. If these don't match, it may automatically invoke <code>onlogin</code> or <code>onlogout</code> on page load.</p> - -<p> </p> - -<h2 id="Step_4_Verify_the_user’s_credentials">Step 4: Verify the user’s credentials</h2> - -<p>Instead of passwords, Persona uses “identity assertions,” which are kind of like single-use, single-site passwords combined with the user’s email address. When a user wants to log in, your <code>onlogin</code> callback will be invoked with an assertion from that user. Before you can log them in, you must verify that the assertion is valid.</p> - -<p>It’s <em>extremely important</em> that you verify the assertion on your server, and not in JavaScript running on the user’s browser, since that would be easy to forge. The example above handed off the assertion to the site’s backend by using jQuery’s <code>$.ajax()</code> helper to <code>POST</code> it to <code>/auth/login</code>.</p> - -<p>Once your server has an assertion, how do you verify it? The easiest way is to use a helper service provided by Mozilla. Simply <code>POST</code> the assertion to <code>https://verifier.login.persona.org/verify</code> with two parameters:</p> - -<ol> - <li><code>assertion</code>: The identity assertion provided by the user.</li> - <li><code>audience</code>: The hostname and port of your website. You must hardcode this value in your backend; do not derive it from any data supplied by the user.</li> -</ol> - -<p>For example, if you’re <code>example.com</code>, you can use the command line to test an assertion with:</p> - -<pre class="brush: bash;">$ curl -d "assertion=<ASSERTION>&audience=https://example.com:443" "https://verifier.login.persona.org/verify" -</pre> - -<p>If it’s valid, you’ll get a JSON response like this:</p> - -<pre class="brush: js;">{ - "status": "okay", - "email": "bob@eyedee.me", - "audience": "https://example.com:443", - "expires": 1308859352261, - "issuer": "eyedee.me" -} -</pre> - -<p>You can learn more about the verification service by reading <a href="https://developer.mozilla.org/en-US/docs/BrowserID/Remote_Verification_API">The Verification Service API</a>. An example <code>/api/login</code> implementation, using <a href="http://python.org/">Python</a>, the <a href="http://flask.pocoo.org/">Flask</a> web framework, and the <a href="http://python-requests.org">Requests</a> HTTP library might look like this:</p> - -<pre class="brush: python;">@app.route('/auth/login', methods=['POST']) -def login(): - # The request has to have an assertion for us to verify - if 'assertion' not in request.form: - abort(400) - - # Send the assertion to Mozilla's verifier service. - data = {'assertion': request.form['assertion'], 'audience': 'https://example.com:443'} - resp = requests.post('https://verifier.login.persona.org/verify', data=data, verify=True) - - # Did the verifier respond? - if resp.ok: - # Parse the response - verification_data = json.loads(resp.content) - - # Check if the assertion was valid - if verification_data['status'] == 'okay': - # Log the user in by setting a secure session cookie - session.update({'email': verification_data['email']}) - return resp.content - - # Oops, something failed. Abort. - abort(500) -</pre> - -<p>For an example on how to use Persona in a C# ASP.Net MVC3 application, <a href="https://github.com/sergiotapia/ASP.Net-MVC3-Persona-Demo" title="https://github.com/sergiotapia/ASP.Net-MVC3-Persona-Demo">visit this application demo</a> or see the Controller code below:</p> - -<p> </p> - -<pre class="brush:java;">public class AuthController : Controller -{ - [HttpPost] - public ActionResult Login(string assertion) - { - if (assertion == null) - { - // The 'assertion' key of the API wasn't POSTED. Redirect, - // or whatever you'd like, to try again. - return RedirectToAction("Index", "Home"); - } - - using (var web = new WebClient()) - { - // Build the data we're going to POST. - var data = new NameValueCollection(); - data["assertion"] = assertion; - data["audience"] = "https://example.com:443"; // Use your website's URL here. - - - // POST the data to the Persona provider (in this case Mozilla) - var response = web.UploadValues("https://verifier.login.persona.org/verify", "POST", data); - var buffer = Encoding.Convert(Encoding.GetEncoding("iso-8859-1"), Encoding.UTF8, response); - - - // Convert the response to JSON. - var tempString = Encoding.UTF8.GetString(buffer, 0, response.Length); - var reader = new JsonReader(); - dynamic output = reader.Read(tempString); - - if (output.status == "okay") - { - string email = output.email; // Since this is dynamic, convert it to string. - FormsAuthentication.SetAuthCookie(email, true); - return RedirectToAction("Index", "Home"); - } - - // Could not log in, do something else. - return RedirectToAction("Index", "Home"); - } - } -}</pre> - -<p>The session management is probably very similar to your existing login system. The first big change is in verifying the user’s identity by checking an assertion instead of checking a password. The other big change is ensuring that the user’s email address is available for use as the <code>loggedInEmail</code> parameter to {{ domxref("navigator.id.watch()") }}.</p> - -<p>Logout is simple: you just need to remove the user’s session cookie.</p> - -<h2 id="Step_5_Review_best_practices">Step 5: Review best practices</h2> - -<p>Once everything works and you’ve successfully logged into and out of your site, you should take a moment to review <a href="https://developer.mozilla.org/docs/BrowserID/Security_Considerations">best practices</a> for using Persona safely and securely.</p> - -<p>If you're making a production-ready site, you may want to write integration tests that simulate logging a user in and out of your site using Persona. To facilitate this action in Selenium, consider using the <a href="https://github.com/mozilla/bidpom" title="https://github.com/mozilla/bidpom">bidpom</a> library. The sites <a href="https://mockmyid.com/" title="https://mockmyid.com/">mockmyid.com</a> and <a href="http://personatestuser.org" title="http://personatestuser.org">personatestuser.org</a> may also be helpful.</p> - -<p>Lastly, don’t forget to sign up for the <a href="https://mail.mozilla.org/listinfo/persona-notices">Persona notices</a> mailing list so you’re notified of any security issues or backwards incompatible changes to the Persona API. The list is extremely low traffic: it’s only used to announce changes which may adversely impact your site.</p> - -<p> </p> diff --git a/files/it/archive/mozilla/persona/remote_verification_api/index.html b/files/it/archive/mozilla/persona/remote_verification_api/index.html deleted file mode 100644 index 05a0e1e7b5..0000000000 --- a/files/it/archive/mozilla/persona/remote_verification_api/index.html +++ /dev/null @@ -1,171 +0,0 @@ ---- -title: API di verifica remota -slug: Archive/Mozilla/Persona/Remote_Verification_API -translation_of: Archive/Mozilla/Persona/Remote_Verification_API ---- -<h2 id="Summary" name="Summary">Summary</h2> -<p>When a user tries to log into a website, their browser generates a data structure called an <em>assertion</em>, which is essentially a cryptographically signed email address. The browser sends this assertion to the web site, which must verify that the assertion is valid before logging the user in.</p> -<p>Assertions can be verified locally, or with an API hosted at <span class="link-https"><code>https://verifier.login.persona.org/verify</code></span>. This page describes how to use the API.</p> -<h2 id="Methods" name="Methods">Method</h2> -<p>HTTP POST request to <code>https://verifier.login.persona.org/verify</code>.</p> -<h3 id="Parameters" name="Parameters">Parameters</h3> -<dl> - <dt> - <code>assertion</code></dt> - <dd> - The assertion supplied by the user. Available as the first parameter passed to the <code>onlogin</code> function in {{ domxref("navigator.id.watch()") }}.</dd> - <dt> - <code>audience</code></dt> - <dd> - The protocol, domain name, and port of your site. For example, "<code>https://example.com:443</code>".</dd> -</dl> -<h3 id="Return_values" name="Return_values">Return values</h3> -<p>The call returns a JSON structure containing a <code>status</code> element, which may be either "okay" or "failure". Depending on the value of <code>status</code>, the structure contains additional elements listed below.</p> -<h4 id="okay" name="okay">"okay"</h4> -<p>The assertion is valid.</p> -<p>In this case the JSON structure contains the following additional elements:</p> -<table class="standard-table" style="width: 80%;"> - <tbody> - <tr> - <td>"<code>email</code>"</td> - <td>The address contained in the assertion, for the intended person being logged in.</td> - </tr> - <tr> - <td>"<code>audience</code>"</td> - <td>The audience value contained in the assertion. Expected to be your own website URL.</td> - </tr> - <tr> - <td>"<code>expires</code>"</td> - <td>The date the assertion expires, expressed as the <a href="/en/JavaScript/Reference/Global_Objects/Date/valueOf" title="en/JavaScript/Reference/Global_Objects/Date/valueOf">primitive value of a Date object</a>: that is, the number of milliseconds since midnight 01 January, 1970 UTC.</td> - </tr> - <tr> - <td>"<code>issuer</code>"</td> - <td>The hostname of the identity provider that issued the assertion.</td> - </tr> - </tbody> -</table> -<h4 id="failure" name="failure">"failure"</h4> -<p>The assertion is invalid. In this case the JSON structure contains one additional element:</p> -<table class="compact-table"> - <tbody> - <tr> - <td><code>"reason"</code></td> - <td>A string explaining why verification failed.</td> - </tr> - </tbody> -</table> -<h2 id="Examples" name="Examples">Examples</h2> -<h3 id="node.js" name="node.js">node.js</h3> -<p>This example uses a node.js server using express.js</p> -<pre class="brush: js">var express = require("express"), - app = express.createServer(), - https = require("https"), - querystring = require("querystring"); -/* ... */ - -// The audience must match what your browser's address bar shows, -// including protocol, hostname, and port -var audience = "http://localhost:8888"; - -app.post("/authenticate", function(req, res) { - var vreq = https.request({ - host: "verifier.login.persona.org", - path: "/verify", - method: "POST" - }, function(vres) { - var body = ""; - vres.on('data', function(chunk) { body+=chunk; } ) - .on('end', function() { - try { - var verifierResp = JSON.parse(body); - var valid = verifierResp && verifierResp.status === "okay"; - var email = valid ? verifierResp.email : null; - req.session.email = email; - if (valid) { - console.log("assertion verified successfully for email:", email); - res.json(email); - } else { - console.log("failed to verify assertion:", verifierResp.reason); - res.send(verifierResp.reason, 403); - } - } catch(e) { - console.log("non-JSON response from verifier"); - // bogus response from verifier! - res.send("bogus response from verifier!", 403); - - } - }); - }); - - vreq.setHeader('Content-Type', 'application/x-www-form-urlencoded'); - - var data = querystring.stringify({ - assertion: req.body.assertion, - audience: audience - }); - - vreq.setHeader('Content-Length', data.length); - vreq.write(data); - vreq.end(); - - console.log("verifying assertion!"); -}); - -</pre> -<p>via <a class="link-https" href="https://github.com/lloyd/myfavoritebeer.org/blob/06255b960e1f9078bc935c1c7af0662f33c88818/server/main.js#L112">Lloyd Hilaiel</a></p> -<h3 id="PHP" name="PHP">PHP</h3> -<pre class="brush: php">$url = 'https://verifier.login.persona.org/verify'; -$assert = filter_input( - INPUT_POST, - 'assertion', - FILTER_UNSAFE_RAW, - FILTER_FLAG_STRIP_LOW|FILTER_FLAG_STRIP_HIGH -); -//Use the $_POST superglobal array for PHP < 5.2 and write your own filter -$params = 'assertion=' . urlencode($assert) . '&audience=' . - urlencode('http://example.com:80'); -$ch = curl_init(); -$options = array( - CURLOPT_URL => $url, - CURLOPT_RETURNTRANSFER => TRUE, - CURLOPT_POST => 2, - //CURLOPT_SSL_VERIFYPEER => true, //This currently blocks connection to 'https://verifier.login.persona.org/verify' - CURLOPT_SSL_VERIFYPEER => 0, - - CURLOPT_SSL_VERIFYHOST => 2, - CURLOPT_POSTFIELDS => $params -); -curl_setopt_array($ch, $options); -$result = curl_exec($ch); -curl_close($ch); -echo $result;</pre> -<p>Via <a class="link-https" href="https://github.com/codepo8/BrowserID-login-with-PHP/blob/184fdb74c8a554461c262875859968154d09288e/verify.php">Christian Heilmann</a></p> -<h3 id="Java" name="Java" style="line-height: 20px;">Java</h3> -<pre class="brush: java">@Override -protected void doPost(final HttpServletRequest req, - final HttpServletResponse resp) throws ServletException, - IOException { - - final String audience = req.getServerName(); - final String assertion = req.getParameter("assertion"); - final Verifier verifier = new Verifier(); - final BrowserIDResponse personaResponse = verifier.verify(assertion,audience); - final Status status = personaResponse.getStatus(); - - if (status == Status.OK) { - /* Authentication with Persona was successful */ - String email = personaResponse.getEmail(); - log.info("{} has sucessfully signed in", email); - HttpSession session = req.getSession(true); - session.setAttribute("email", email); - - } else { - /* Authentication with Persona failed */ - log.info("Sign in failed..."); - - } -} -</pre> -<p>Via <a class="link-https" href="https://github.com/user454322/browserid-verifier">Javier</a></p> -<p> </p> -<p>Note: If you send the assertion and audience parameters as a JSON-object, they <strong>must not</strong> be URL-encoded. If they are sent as regular HTTP POST parameters, as in the example above, they <strong>must</strong> be URL-encoded.</p> diff --git a/files/it/archive/mozilla/persona/security_considerations/index.html b/files/it/archive/mozilla/persona/security_considerations/index.html deleted file mode 100644 index 7d13904b45..0000000000 --- a/files/it/archive/mozilla/persona/security_considerations/index.html +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Considerazioni sulla sicurezza -slug: Archive/Mozilla/Persona/Security_Considerations -translation_of: Archive/Mozilla/Persona/Security_Considerations ---- -<p>When you add Persona support to your website, Persona takes on as much of the security burden as it can. However, some aspects of security can only be handled by your website. They're listed below.</p> -<h2 id="Essential_practices" name="Essential_practices">Essential practices</h2> -<h3 id="Verify_assertions_on_your_server" name="Verify_assertions_on_your_server">Verify assertions on your server</h3> -<p>When using Persona, identity assertions are passed into the <code>onlogin</code> function passed to {{ domxref("navigator.id.watch()") }}. You should <em>always</em> pass the assertion to your server for verification, and only your server should decide to grant the user additional permissions based on the verification result:</p> -<pre class="brush:js;">// Inside navigator.id.watch({ ... -onlogin: function(assertion) { - // A user wants to log in! Here you need to: - // 1. Send the assertion to your backend for verification and to create a session. - // 2. Update your UI. -}, -</pre> -<p>If you try to verify the assertion using the JavaScript executing in the user's browser, then a malicious user will be able to impersonate a legitimate user of your site by locally injecting code and subverting your JavaScript. This is possible because you're not fully in control of the user's browser, where the code executes.</p> -<p>Again, you should <em>always</em> pass the assertion to your server for verification. Even if you're using the remote verification API.</p> -<h3 id="Explicitly_specify_the_audience_parameter" name="Explicitly_specify_the_audience_parameter">Explicitly specify the audience parameter</h3> -<p>To verify an assertion, you may issue a POST request to<code> https://verifier.login.persona.org/verify</code>. The request includes a parameter called <code>audience</code>:</p> -<pre><code>assertion=<ASSERTION>&audience=https://mysite.com:443"</code></pre> -<p>The <code>audience</code> parameter is required. You should always specify the audience explicitly in your code, or in your code's configuration. Specifically:</p> -<ul> - <li>Do not trust the Host header sent by the user's browser.</li> - <li>Do not trust an explicit parameter sent by the user's browser, but generated by your JavaScript using, e.g. <code>document.location</code>.</li> -</ul> -<p>If you trust the user's browser to tell you the audience, then it becomes possible for a malicious web site to reuse assertions for <em>its</em> web site to log into <em>your</em> web site.</p> -<h3 id="Verify_SSL_certificates" name="Verify_SSL_certificates">Verify SSL certificates</h3> -<p>To verify an assertion, you may issue a POST request to <code>https://verifier.login.persona.org/verify</code>. You must ensure that your HTTPS request verifies the certificate sent from the server against a trusted root certificate. If you don't, then an attacker could pose as <code>verifier.login.persona.org</code> and issue false verifications.</p> -<p>Check that the library you are using to make the request verifies certificates correctly, and that you are initializing it with the appropriate root certificate(s).</p> -<p>For example, Python 2.7's standard <a class="external" href="http://docs.python.org/release/2.7.3/library/urllib2.html#urllib2.urlopen" title="http://docs.python.org/release/2.7.3/library/urllib2.html#urllib2.urlopen">urllib2 module</a> does not validate server certificates. Instead, we recommend using the "<a class="external" href="http://pypi.python.org/pypi/requests">requests</a>" or "<a class="external" href="http://pypi.python.org/pypi/urllib3" title="http://pypi.python.org/pypi/urllib3">urllib3</a>" modules in Python 2.x, or the standard <code>http.client.HTTPSConnection</code> class in Python 3.x. For Perl, ensure that you are using at least version 6.0 of <code>libwww-perl</code>. Depending on the language, library, and operating system that you're using, you may need to supply either a list of trusted CA roots or the single CA used by <code>verifier.login.persona.org</code>.</p> -<h3 id="Implement_CSRF_protection" name="Implement_CSRF_protection">Implement CSRF protection</h3> -<p>In a CSRF (Cross-Site Request Forgery) login attack, an attacker uses a cross-site request forgery to log the user into a web site using the attacker's credentials.</p> -<p>For example: a user visits a malicious web site containing a <code>form</code> element. The form's <code>action</code> attribute is set to an HTTP POST request to <a class="external" href="http://www.google.com/login" title="http://www.google.com/login">http://www.google.com/login</a>, supplying the attacker's username and password. When the user submits the form, the request is sent to Google, the login succeeds and the Google server sets a cookie in the user's browser. Now the user's unknowingly logged into the attacker's Google account.</p> -<p>The attack can be used to gather sensitive information about the user. For example, Google's <a class="link-https" href="https://www.google.com/history/">Web History</a> feature logs all the user's Google search terms. If a user is logged into the attacker's Google account and the attacker has Web History enabled, then the user is giving the attacker all this information.</p> -<p>CSRF login attacks, and potential defenses against them, are documented more fully in <a class="external" href="http://www.adambarth.com/papers/2008/barth-jackson-mitchell-b.pdf">Robust Defenses for Cross-Site Request Forgery</a> (PDF). They're not specific to Persona: most login mechanisms are potentially vulnerable to them.</p> -<p>There are a variety of techniques which can be used to protect a site from CSRF login attacks, which are documented more fully in the study above.</p> -<p>One approach is to create a secret identifier in the server, shared with the browser, and require the browser to supply it when making login requests. For example:</p> -<ol> - <li>As soon as the user lands on your site, before they try to log in, create a session for them on the server. Store the session ID in a browser cookie.</li> - <li>On the server, generate a random string of at least 10 alphanumeric characters. A randomly generated UUID is a good option. This is the CSRF token. Store it in the session.</li> - <li>Deliver the CSRF token to the browser by either embedding it in JavaScript or HTML as a hidden form variable.</li> - <li>Ensure that the AJAX submission or form POST includes the CSRF token.</li> - <li>On the server side, before accepting an assertion, check that the submitted CSRF token matches the session-stored CSRF token.</li> -</ol> -<h2 id="Enhancements" name="Enhancements">Enhancements</h2> -<h3 id="Content_Security_Policy_(CSP)" name="Content_Security_Policy_(CSP)">Content Security Policy (CSP)</h3> -<p><a href="/en-US/docs/Security/CSP" title="Security/CSP">Content Security Policy</a> (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware.</p> -<p>If you use CSP on your site, you may need to tweak your policy to enable Persona. Depending on your policy, you may need to:</p> -<ul> - <li>Remove inline <code>javascript:</code> URIs and replace them with code loaded from an additional script file. The file can look up elements based on their ID, and then attach to the element by setting {{ domxref("element.onclick", "onclick") }} or calling {{ domxref("element.addEventListener()", "addEventListener()") }}.</li> - <li>Allow <code>https://login.persona.org</code> as both a <code>script-src</code> and <code>frame-src</code> so that your site can load the remote <code>include.js</code> file and that file can communicate with the fallback Persona implementation.</li> -</ul> -<p>An example Apache configuration might include:</p> -<pre><span class="diff-content"><span class="idiff">Header set X-Content-Security-Policy: "default-src 'self'; frame-src 'self' https://login.persona.org ; script-src 'self' https://login.persona.org"</span></span></pre> diff --git a/files/it/archive/mozilla/persona/the_implementor_s_guide/index.html b/files/it/archive/mozilla/persona/the_implementor_s_guide/index.html deleted file mode 100644 index 2bd12dcc0b..0000000000 --- a/files/it/archive/mozilla/persona/the_implementor_s_guide/index.html +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: The implementor's guide -slug: Archive/Mozilla/Persona/The_implementor_s_guide -tags: - - NeedsTranslation - - Persona - - TopicStub -translation_of: Archive/Mozilla/Persona/The_implementor_s_guide ---- -<p>The <a href="/en-US/docs/Persona/Quick_setup" title="/en-US/docs/Persona/Quick_setup">Quick setup guide</a> should be enough to get you started, but when building a full production site you'll probably need features that aren't covered in that guide. In this page we've collected features that are commonly needed by sign-in systems, and explained the best-practice way to implement them with Persona.</p> -<div class="section"> - <dl> - <dt> - <a href="/en-US/docs/Persona/The_implementor_s_guide/Call_logout%28%29_after_a_failed_login" title="BrowserID/Why_BrowserID">Call logout() after a failed login</a></dt> - <dd> - Always call logout() if you reject an assertion, to avoid a mismatch between your idea of the current user and Persona's idea, which can lead to an endless loop of failed logins.</dd> - </dl> - <dl> - <dt> - <a href="/en-US/docs/Persona/The_implementor_s_guide/Adding_extra_email_addresses_with_Persona" title="BrowserID/Quick setup">Adding extra email addresses with Persona</a></dt> - <dd> - How to let your users add secondary email addresses using Persona.</dd> - </dl> - <dl> - <dt> - <a href="/en-US/docs/Persona/The_implementor_s_guide/Enabling_users_to_change_their_email_address" title="BrowserID/Quick setup">Enabling users to change their email address</a></dt> - <dd> - How to let your users change their email address using Persona.</dd> - </dl> - <dl> - <dt> - <a href="/en-US/docs/Persona/The_implementor_s_guide/Problems_integrating_with_CRSF_protection" title="BrowserID/Quick setup">Problems integrating with CSRF protection</a></dt> - <dd> - A problem caused by the interaction between a common mechanism for CSRF (Cross Site Request Forgery) protection and Persona's Observer API.</dd> - </dl> - <dl> - <dt> - <a href="/en-US/docs/Persona/The_implementor_s_guide/Supporting_users_without_JavaScript" title="BrowserID/Quick setup">Supporting users who don't have JavaScript</a></dt> - <dd> - Persona requires JavaScript. This page has some tips for supporting users who have JavaScript disabled.</dd> - </dl> - <dl> - </dl> - <dl> - <dt> - <a href="/en-US/docs/Persona/The_implementor_s_guide/Call_request()_only_from_a_click_handler" title="BrowserID/Quick setup">Call request() or get() only from a key handler or in response to a keypress</a></dt> - <dd> - Because Persona uses popup windows, you must call request() or get() only in response to a click or a key press, not some other event.</dd> - </dl> - <dl> - <dt> - <a href="/en-US/docs/Persona/The_implementor_s_guide/Testing" title="BrowserID/Quick setup">Testing your system</a></dt> - <dd> - Some pointers for simulating users logging in and out of your website.</dd> - </dl> -</div> -<p> </p> diff --git a/files/it/archive/mozilla/persona/the_implementor_s_guide/testing/index.html b/files/it/archive/mozilla/persona/the_implementor_s_guide/testing/index.html deleted file mode 100644 index 4ace111864..0000000000 --- a/files/it/archive/mozilla/persona/the_implementor_s_guide/testing/index.html +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Testing -slug: Archive/Mozilla/Persona/The_implementor_s_guide/Testing -translation_of: Archive/Mozilla/Persona/The_implementor_s_guide/Testing ---- -<p>If you're making a production system you will need to write integration tests that simulate logging a user in and out of your site using Persona.</p> -<p>If you're using <a href="http://docs.seleniumhq.org/" title="http://docs.seleniumhq.org/">Selenium</a> for testing, consider using the <a href="https://github.com/mozilla/bidpom" title="https://github.com/mozilla/bidpom">bidpom</a> library. The sites <a href="https://mockmyid.com/" title="https://mockmyid.com/">mockmyid.com</a> and <a href="http://personatestuser.org" title="http://personatestuser.org">personatestuser.org</a> may also be helpful.</p> -<p>You may also want to consider <a href="http://toolness.github.io/stubbyid/" title="http://toolness.github.io/stubbyid/">stubbyid</a>.</p> diff --git a/files/it/archive/mozilla/persona/the_navigator.id_api/index.html b/files/it/archive/mozilla/persona/the_navigator.id_api/index.html deleted file mode 100644 index 7ab75d0f93..0000000000 --- a/files/it/archive/mozilla/persona/the_navigator.id_api/index.html +++ /dev/null @@ -1,148 +0,0 @@ ---- -title: La API navigator.id -slug: Archive/Mozilla/Persona/The_navigator.id_API -translation_of: Archive/Mozilla/Persona/The_navigator.id_API ---- -<div class="note">For full details about the <code>navigator.id</code> API, refer to its <a href="/en-US/docs/Web/API/navigator.id">reference pages</a>.</div> - -<p>With Persona, a website asks the user to provide an "assertion", which is a digitally signed email address. By verifying the signature, the site can be assured that the user really does control the address in question. The site can then use this email address as an identifier for that user.</p> - -<p>To ask for an assertion, the website uses a JavaScript API defined by the <code>id</code> object, which is a member of the global <a href="/en-US/docs/Web/API/Navigator"><code>navigator</code></a> object.</p> - -<p>In future we expect the <code>id</code> object to be built into the browser, but at the moment it isn't, so sites using Persona need to include the polyfill library hosted at <a class="external link-https" href="https://login.persona.org/include.js" title="https://login.persona.org/include.js">https://login.persona.org/include.js</a> in their pages. After that, they can work as if <code>id</code> is just a built-in member of <code>navigator</code>.</p> - -<p>There are two current versions of the API: the "Callback API", and the newer "Observer API".</p> - -<h2 id="The_Callback_API">The Callback API</h2> - -<p>The <a href="/en-US/docs/Web/API/navigator.id#CallbackMethods">Callback API</a> consists of a single function, <a href="/en-US/docs/Web/API/navigator.id.get"><code>get()</code></a>. It takes two arguments:</p> - -<ul> - <li>a callback function that will be called back with a signed assertion if the user successfully authenticates to their Identity Provider</li> - <li>an options object that mostly customizes the dialog presented to users: allowing a website to link to its privacy policy, to set background color or include an icon, for example</li> -</ul> - -<p>You call <code>get()</code>, and in the callback you send the assertion to the server to <a href="/en-US/docs/Mozilla/Persona/Remote_Verification_API">verify the assertion</a>. If verification succeeds, you can log the user in:</p> - -<pre class="brush: js">var signin = document.getElementById('sign-in'); -signin.addEventListener("click", getAssertion, false); - -// get an assertion -function getAssertion() { - navigator.id.get(verifyAssertion, { - backgroundColor: "#606B72", - siteName: "My Example Site" - }); -} - -// send the assertion to the server for verification -function verifyAssertion(assertion) { - var xhr = new XMLHttpRequest(); - xhr.open("POST", "/verify", true); - var param = "assertion="+assertion; - xhr.setRequestHeader("Content-type", "application/x-www-form-urlencoded"); - xhr.setRequestHeader("Content-length", param.length); - xhr.setRequestHeader("Connection", "close"); - xhr.send(param); - xhr.onload = handleVerificationResponse(xhr); -}</pre> - -<h2 id="The_Observer_API">The Observer API</h2> - -<p>The <a href="/en-US/docs/Web/API/navigator.id#ObserverMethods">Observer API</a> consists of three functions: <a href="/en-US/docs/Web/API/navigator.id.request"><code>request()</code></a>, <a href="/en-US/docs/Web/API/navigator.id.watch"><code>watch()</code></a>, and <a href="/en-US/docs/Web/API/navigator.id.logout"><code>logout()</code></a>.</p> - -<p>You call <code>request()</code> to ask for a signed assertion, as you do using <code>get()</code> in the old API. But <code>request()</code> doesn't take a callback parameter: instead, you call another function <code>watch()</code>, with which you register callbacks for <code>onlogin</code> and <code>onlogout</code> events. Persona calls these callbacks when a user logs in or out respectively. Like the callback to <code>get()</code>, the <code>onlogin</code> callback gets a signed assertion for you to verify.</p> - -<p>You call <code>logout()</code> when a user logs out of your site, so Persona can update its state.</p> - -<p>The main difference between this API and the Callback API is that the Callback API doesn't maintain any state: it doesn't have any idea which user is currently logged into Persona in general or any site in particular. Each website is responsible for its own session management.</p> - -<p>By contrast the Observer API implements session management: the browser keeps track of which user it thinks is logged into a particular site and can trigger the <code>onlogin</code> and <code>onlogout</code> callbacks when its idea of the state changes. Because of this, you need to ensure that your website's state and Persona's state are kept in synch, and this tends to make the Observer API more complex to use.</p> - -<p>Here's an example showing the Observer API:</p> - -<pre class="brush: js">var signin = document.getElementById('sign-in'); -var signout = document.getElementById('sign-out'); - -signin.addEventListener("click", function() { - navigator.id.request(); -}, false); - -signout.addEventListener("click", function() { - navigator.id.logout(); -}, false); - -function handleUserResponse(xhr) { - return function() { - if (xhr.status == 200) { - if (xhr.responseText == "no user") { - logoutUser(); - } - else { - loginUser(xhr.responseText); - } - navigator.id.watch({ - loggedInUser: currentUser, - onlogin: function(assertion) { - verifyAssertion(assertion); - }, - onlogout: function() { - logoutUser(); - } - }); - } - else { - navigator.id.logout(); - alert("XMLHttpRequest error: " + xhr.status); - } - } -} - -function checkCurrentUser() { - var xhr = new XMLHttpRequest(); - xhr.open("GET", "/currentuser", true); - xhr.send(); - xhr.onload = handleUserResponse(xhr); -} - -checkCurrentUser(); - -function loginUser(loggedInUser) { - // update your UI to show that the user is logged in -} - -function logoutUser() { - // update your UI to show that the user is logged out -} - -function handleVerificationResponse(xhr) { - // if successfully verified, log the user in -} - -function verifyAssertion(assertion) { - var xhr = new XMLHttpRequest(); - xhr.open("POST", "/verify", true); - var param = "assertion="+assertion; - xhr.setRequestHeader("Content-type", "application/x-www-form-urlencoded"); - xhr.setRequestHeader("Content-length", param.length); - xhr.setRequestHeader("Connection", "close"); - xhr.send(param); - xhr.onload = handleVerificationResponse(xhr); -} -</pre> - -<p>This code adds listeners which call <code>request()</code> and <code>logout()</code> when the user clicks "Sign in" and "Sign out" respectively. It then checks whether the server thinks someone is logged in already, and updates its UI if it thinks someone is. The code then calls <code>watch()</code> to start listening for login and logout events. When Persona triggers <code>onlogout</code> the code updates its state to log the user out, and when Persona triggers <code>onlogin</code> the code sends the assertion to the server for verification.</p> - -<p>Although the Observer API is more complex to use, it provides two extra features: <em>seamless first-time sign-in</em>, and <em>global logout</em>.</p> - -<h3 id="Seamless_first-time_sign-in">Seamless first-time sign-in</h3> - -<p>The first time a user signs in using Persona, they may need to create a Persona account. This will happen if they haven't used Persona before and if their email provider does not support Persona. In this case they will be invited to create an account using the <a href="https://developer.mozilla.org/en-US/docs/Persona/Bootstrapping_Persona">fallback provider</a> operated by Mozilla, which will ask them to prove ownership of their email address. After creating an account, if the original website uses the Callback API, the user <em>will not</em> be automatically redirected to the website and signed in: they will have to navigate back to it.</p> - -<p>If the website uses the Observer API, then once the user finishes creating their account with the fallback provider, they will be immediately redirected to the site, the <code>watch()</code> API will call the <code>onlogin</code> listener, and the user will be signed in.</p> - -<h3 id="Global_logout">Global logout</h3> - -<p>With the Observer API, the website listens to the <code>onlogout</code> event. If the user signs out of Persona by visiting <a href="https://login.persona.org/">https://login.persona.org/</a> and signing out there, then the Observer API triggers this event for all websites that are listening. In response, the site should log the user out.</p> - -<p>This means that if the user doesn't always trust the other people that may access their computer, they can sign out in one place, and this will be propagated to all sites that use the Observer API. </p> diff --git a/files/it/archive/mozilla/persona/why_persona/index.html b/files/it/archive/mozilla/persona/why_persona/index.html deleted file mode 100644 index b2f606d85b..0000000000 --- a/files/it/archive/mozilla/persona/why_persona/index.html +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Perché Persona per Mozilla? -slug: Archive/Mozilla/Persona/Why_Persona -translation_of: Archive/Mozilla/Persona/Why_Persona ---- -<div dir="ltr" style="margin-left: 40px;"> - Persona is an openly distributed, cross-browser identity system providing a solution to the traditional password model. It addresses the usability deficiencies that plague other privacy-related systems such as OpenID, without resorting to a centralized infrastructure such as Facebook Connect.<span id="result_box" lang="en"><span class="hps"> </span></span></div> -<div dir="ltr" style="margin-left: 40px;"> - </div> -<div dir="ltr" style="margin-left: 40px;"> - <span lang="en"><span class="hps">The current approach for establishing and managing </span><span class="hps">user names</span> <span class="hps">and passwords is tedious, inefficient, and unsecure. </span>U<span class="hps">sers must create and remember complex passwords for each site and service. Sites then must securely encrypt and store passwords to prevent the leaking of sensitive information. The prevention and negation of security leaks is the primary reason for the use of Persona, but the flexibility of its systems outclasses most standard identity security systems.</span></span></div> -<div dir="ltr" style="margin-left: 40px;"> - </div> -<div class="summary"> - <div dir="ltr" style="margin-left: 40px;"> - <strong>Note:</strong> For more detailed information about Persona a<strong>nd its functions </strong>see <a href="https://support.mozilla.org/en-US/kb/what-is-persona-and-how-does-it-work">What is Persona and how does it work?</a></div> -</div> -<h2 id="Persona_eliminates_the_need_for_per-site_passwords">Persona eliminates the need for per-site passwords</h2> -<p style="margin-left: 40px;">Persona utilizes a safe, two-click system built on top of public-key cryptography for logging in to websites. The user's browser generates a cryptographic affirmation of identity that expires after a few minutes and is only valid on one site. By avoiding passwords, users do not need to worry about remembering several distinct passwords and need no longer be concerned with unsecure access to their password.<span id="result_box" lang="en"><span class="hps"> This quick and easy sign-in process eliminates the current inefficiencies of traditional account registration and allows users to quickly establish accounts on websites.</span></span></p> -<h2 id="Persona_uses_email_addresses_as_identities">Persona uses email addresses as identities</h2> -<div id="gt-src-tools"> - <div id="gt-src-tools-l"> - <div id="gt-input-tool" style="display: inline-block;"> - <div id="itamenu" style="margin-left: 40px;"> - Persona's system relies on email addresses as their key component because of email's inherent versatile and private nature. The pre-existing infrastructure works very well from not only a design perspective but an ideal perspective of openly maintained and safe transfer of identity across the Internet.</div> - </div> - </div> -</div> -<h3 id="sect1"> </h3> -<h3 id="Benefits_for_the_user"><span class="short_text" id="result_box" lang="en"><span class="hps">Benefits for</span> <span class="hps">the user</span></span></h3> -<ul style="margin-left: 40px;"> - <li>Users already know their email addresses. They don't have to learn a new and potentially confusing system, like OpenID.</li> - <li><span id="result_box" lang="en"><span class="hps">The</span> <span class="hps">email addresses</span> <span class="hps">carefully</span> <span class="hps">capture the</span> <span class="hps">idea of</span> <span id="result_box" lang="es"><span class="hps"><code>someone@some-context</code></span></span>. This <span class="hps">makes it easier for</span> <span class="hps">users to keep their</span> <span class="hps">identities</span> <span id="result_box" lang="es"><code>@work</code>, <code>@home</code>, or <code>@school </code></span><span>separate.</span> <span class="hps">This differs from</span> <span class="hps">the trend of</span> linking together many accounts <span class="hps">through real</span> <span class="hps">identity,</span> single-account <span class="hps">policies</span> <span class="hps">on social networks like Google+ and Facebook.</span></span></li> - <li><span id="result_box" lang="en"><span class="hps">Email can</span> <span class="hps atn">be self-</span><span>organized</span> <span class="hps">or delegated to</span> <span class="hps">other providers</span><span>,</span> <span class="hps">giving users</span> <span class="hps">control of their</span> <span class="hps">identity.</span></span> This ability is greatly diminished when one must consolidate many accounts into one identity. </li> -</ul> -<div class="almost_half_cell" id="gt-res-content"> - <h3 dir="ltr" id="Advantages_for_developers" style="zoom: 1;"><span class="short_text" id="result_box" lang="en"><span class="hps">Advantages</span> <span class="hps">for developers</span></span></h3> -</div> -<ul style="margin-left: 40px;"> - <li><span id="result_box" lang="en"><span class="hps">Email addresses</span> let <span class="hps">developers </span><span class="hps">communicate directly with </span><span class="hps">users.</span> </span></li> - <li> - <div class="almost_half_cell" id="gt-res-content"> - <div dir="ltr" style="zoom: 1;"> - <span id="result_box" lang="es"><span id="result_box" lang="en"><span class="hps">Persona provides email addresses to websites</span><span class="hps"> automatically</span> <span class="hps">when a user</span> <span class="hps">logs in, </span><span class="hps">eliminating the need for</span> <span class="hps">additional</span> <span class="hps atn">post-</span><span>signup</span> <span class="hps">forms.</span> </span></span></div> - </div> - </li> - <li> - <div class="almost_half_cell" id="gt-res-content"> - <div dir="ltr" style="zoom: 1;"> - <span id="result_box" lang="es"><span id="result_box" lang="en"><span class="hps">Many login systems</span> <span class="hps">treat</span> <span class="hps">email</span> <span class="hps">addresses</span> <span class="hps">as</span> <span class="hps">unique keys, </span><span class="hps">so there is no</span> <span class="hps">lock-in</span> <span class="hps">to</span> <span class="hps">Persona and</span> it <span class="hps">can be integrated</span> <span class="hps">with</span> <span class="hps">existing access</span> <span class="hps">systems</span><span>.</span></span></span><span lang="es"><span lang="en"><span class="hps"> Any user who has an</span></span></span><span lang="es"><span lang="en"><span class="hps"> email address can access content almost immediately</span></span></span><span id="result_box" lang="es"><span id="result_box" lang="en">.</span></span></div> - </div> - </li> -</ul> -<div class="almost_half_cell" id="gt-res-content"> - <h2 dir="ltr" id="How_Persona_is_different_from_other_providers_of_single_sign-on" style="zoom: 1;"><span id="result_box" lang="es"><span class="hps"><span id="result_box" lang="en"><span class="hps">How</span> <span class="hps">Persona</span> <span class="hps">is different</span> <span class="hps">from other providers of</span> <span class="hps">single sign</span><span>-on</span></span></span></span></h2> -</div> -<p style="margin-left: 40px;"><span id="result_box" lang="es"><span id="result_box" lang="en">Persona<span class="hps"> protects</span> <span class="hps">privacy, provides the user with</span><span class="hps"> control,</span> <span class="hps">and embellishes</span><span class="hps"> choice</span> <span class="hps">in a way that</span> <span class="hps">other security providers can't. Many</span> <span class="hps">social networks like</span> <span class="hps">Facebook</span> <span class="hps">and</span> <span class="hps">Google+</span> <span class="hps">require users to</span> <span class="hps">use their</span> <span class="hps">real names, accept their policies,</span> <span class="hps">and</span> <span class="hps">limit users to only</span> <span class="hps">one account.</span> P<span class="hps">ersona</span> <span class="hps">allows users to</span> <span class="hps">keep their work</span><span>, school, and social identities separate b</span></span></span><span style="line-height: 1.5;">y using email addresses as a unique identifier rather than real names.</span> Because of this anonymity you are guaranteed an extra layer of identity and network protection that most social networks do not have.</p> -<p style="margin-left: 40px;"><span lang="en"><span class="hps">Persona</span> <span class="hps">also takes</span> <span class="hps">a new approach</span> <span class="hps">to protecting</span> <span class="hps">user privacy</span> <span class="hps">by placing </span><span class="hps">the user's browser</span> <span class="hps">in the center</span> <span class="hps">of the authentication process. T</span><span>he browser</span> <span class="hps">obtains</span> <span class="hps">credentials</span> <span class="hps">provided by the</span> <span class="hps">user's email</span><span>,</span> <span class="hps">then presents these credentials to a website</span><span class="hps">.</span> <span class="hps">The</span> <span class="hps">email provider</span> <span class="hps">cannot</span> <span class="hps">track the</span> <span class="hps">user,</span> <span class="hps">but sites</span> <span class="hps">can still have</span> <span class="hps">confidence in the identity</span> <span class="hps">of the user by</span> <span class="hps">cryptographically</span> <span class="hps">verifying the</span> <span class="hps">credentials.</span> <span class="hps">Most</span> <span class="hps">other systems,</span> <span class="hps">even</span> <span class="hps">distributed</span> systems <span class="hps">like</span> <span class="hps">OpenID</span><span>,</span> <span class="hps">require</span> <span class="hps">sites</span> <span class="hps">to connect to central networks</span> <span class="hps">before allowing</span> <span class="hps">a user to</span> <span class="hps">log in.</span></span></p> -<p style="margin-left: 40px;">The efficiency of Persona allows an advanced relationship between developers and users. Mozilla is leading the way in open and free web development, and Persona supports Mozilla's design philosophy through its easy-to-use interface and user protection features.</p> diff --git a/files/it/archive/mozilla/xbl/index.html b/files/it/archive/mozilla/xbl/index.html deleted file mode 100644 index d47f050234..0000000000 --- a/files/it/archive/mozilla/xbl/index.html +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: XBL -slug: Archive/Mozilla/XBL -tags: - - Tutte_le_categorie - - XBL -translation_of: Archive/Mozilla/XBL ---- -<p> -</p><p><b>XML Binding Language</b> (<b>XBL</b>, a volte chiamato anche Extensible Bindings Language) è un linguaggio per descrivere i binding che possono essere associati ad elementi di altri documenti. L'elemento al quale il binding è associato, chiamato <i>bound element</i>, acquisisce il nuovo comportamento specificato dal binding. -</p><p>I binding possono contenere gestori di eventi che sono registrati per il bound element, un'implementazione di nuovi metodi e proprietà che divengono accessibili dal bound element e del contenuto anonimo che viene inserito sotto il bound element. -</p><p>La maggior parte dei widget <a href="it/XUL">XUL</a> sono almeno parzialmente implementati utilizzando XBL. E' inoltre possibile costruire widget riutilizzabili partendo da <a href="it/XUL">XUL</a>, <a href="it/HTML">HTML</a>, <a href="it/SVG">SVG</a> e altri linguaggi utilizzando XBL. -</p> -<h3 id="Specifiche"> Specifiche </h3> -<p>XBL 1.0 è specificato in <a href="it/XBL_1.0_Reference">XBL 1.0 Reference</a>. Purtroppo, l'attuale implementazione in Mozilla è differente dalle specifiche e non vi è alcun documento conosciuto che descriva tali differenze. E' sperabile che la Reference venga aggiornata per descrivere l'implementazione di Mozilla. -</p><p>XBL 1.0 è una tecnologia specifica di Mozilla e non uno standard W3C. Tuttavia, si sta lavorando su almeno due standard: sXBL e XBL 2.0. -</p> -<ul><li> W3C <a class="external" href="http://w3.org/TR/sXBL/">sXBL</a> (attualmente una bozza) sta per <i>SVG's XML Binding Language</i>. Includerà un sottoinsieme delle funzionalità di XBL 2.0 di cui si necessita per SVG. Nello stile è simile all'XBL di Mozilla, ma vi sono alcune differenze più o meno sottili. Per esempio, i nomi degli elementi sono diversi. Inoltre in sXBL manchino alcune funzionalità di XBL, come l'ereditarietà dei binding e la definizione di metodi e proprietà per i bound element. -</li><li> <a class="external" href="http://www.mozilla.org/projects/xbl/xbl2.html">XBL 2.0</a> è in fase di sviluppo ed è stato pensato per risolvere i problemi trovati in XBL 1.0 e per permettere l'implementazione in un più vasto rango di web browser. -</li></ul> -<p>Alcune differenze tra sXBL e XBL2 sono elencate in <a class="external" href="http://annevankesteren.nl/2005/11/xbl">un articolo di Anne van Kesteren</a> (EN). -</p> -<h3 id="Vedi_anche"> Vedi anche </h3> -<ul><li> <a href="it/Introduzione_a_XBL">Introduzione a XBL</a> da. <a href="it/Tutorial_XUL">Tutorial XUL</a>. -</li><li> <a class="external" href="http://mb.eschew.org/15.php">Il capitolo su XBL</a> di <a class="external" href="http://mb.eschew.org/">"Rapid Application Development with Mozilla"</a> (EN) -</li></ul> -{{ languages( { "en": "en/XBL", "fr": "fr/XBL", "pl": "pl/XBL", "pt": "pt/XBL" } ) }} diff --git a/files/it/archive/mozilla/xul/index.html b/files/it/archive/mozilla/xul/index.html deleted file mode 100644 index 5de9e8752f..0000000000 --- a/files/it/archive/mozilla/xul/index.html +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: XUL -slug: Archive/Mozilla/XUL -tags: - - Tutte_le_categorie - - XUL -translation_of: Archive/Mozilla/XUL ---- -<p> </p> - -<div class="callout-box"><strong><a href="/it/Tutorial_XUL" title="it/Tutorial_XUL">Tutorial XUL</a></strong><br> -Un tutorial guidato che aiuta i principianti a iniziare a programmare in XUL, originariamente pubblicato in XULPlanet.</div> - -<div><strong>XUL</strong> (XML User Interface Language) è un linguaggio di Mozilla basato su <a href="/it/XML" title="it/XML">XML</a> che permette di creare applicazioni multipiattaforma, ricche di funzionalità, che possono funzionare connesse a Internet oppure no. Queste applicazioni possono essere facilmente personalizzate con testi alternativi, elementi grafici, e layout, in modo che possano essere facilmente personalizzate o localizzate. Gli sviluppatori web che già conoscono l'HTML dinamico (<a href="/it/DHTML" title="it/DHTML">DHTML</a>) possono imparare XUL e iniziare a sviluppare rapidamente. Aprendo la pagina <a class="external" href="http://www.hevanet.com/acorbin/xul/top.xul">XUL Periodic Table</a> con Firefox o un qualsiasi altro browser basato su <a href="/it/Gecko" title="it/Gecko">Gecko</a> si vedranno alcuni esempi dimostrativi di XUL.</div> - -<table class="topicpage-table"> - <tbody> - <tr> - <td> - <h4 id="Documentazione" name="Documentazione"><a href="/it/Documentazione" title="it/Documentazione">Documentazione</a></h4> - - <dl> - <dt><a class="external" href="https://developer.mozilla.org/it/docs/Mozilla/Tech/XUL/XUL_Reference">Reference sugli elementi XUL</a></dt> - <dd><small>Si veda anche la documentazione MDC su <a href="/it/Sistema_di_Preferenze" title="it/Sistema_di_Preferenze">Sistema di Preferenze</a> e <a href="/it/Richlistbox" title="it/Richlistbox">richlistbox</a>.</small></dd> - </dl> - - <dl> - <dt><a href="https://developer.mozilla.org/it/docs/The_Joy_of_XUL" title="it/La_gioia_di_XUL">La gioia di XUL</a></dt> - <dd><small>Descrive le funzionalità e i componenti principali di XUL.</small></dd> - </dl> - - <dl> - <dt><a href="/it/Adattare_le_applicazioni_XUL_per_Firefox_1.5" title="it/Adattare_le_applicazioni_XUL_per_Firefox_1.5">Adattare le applicazioni XUL per Firefox 1.5</a></dt> - <dd><small>Una lista di cambiamenti in <a href="/it/Firefox_1.5" title="it/Firefox_1.5">Firefox 1.5</a> che interessano gli sviluppatori.</small></dd> - </dl> - - <dl> - <dt><a href="/it/Guida_ai_Template_XUL" title="it/Guida_ai_Template_XUL">Guida ai Template XUL</a></dt> - <dd><small>Una guida dettagliata sui Template di XUL, che servono essenzialmente a generare contenuti da una fonte dati.</small></dd> - </dl> - </td> - <td> - <h4 id="Strumenti" name="Strumenti">Strumenti</h4> - - <ul> - <li><a class="external" href="http://ted.mielczarek.org/code/mozilla/extensiondev/">L'estensione Extension developer</a> (che comprende un editor XUL)</li> - <li><a class="external" href="http://www.extensionsmirror.nl/index.php?showtopic=751">La barra laterale XULRef</a></li> - <li><a href="/it/DOM_Inspector" title="it/DOM_Inspector">DOM Inspector</a></li> - </ul> - - <h4 id="Argomenti_correlati" name="Argomenti_correlati">Argomenti correlati</h4> - - <dl> - <dd><a href="/it/JavaScript" title="it/JavaScript">JavaScript</a>, <a href="/it/XBL" title="it/XBL">XBL</a>, <a href="/it/CSS" title="it/CSS">CSS</a>, <a href="/it/RDF" title="it/RDF">RDF</a>, <a href="/it/Estensioni" title="it/Estensioni">Estensioni</a>, <a href="/it/XULRunner" title="it/XULRunner">XULRunner</a></dd> - </dl> - </td> - </tr> - </tbody> -</table> - -<p><span class="comment">Interwiki Language Links</span></p> - -<p>{{ languages( { "en": "en/XUL", "es": "es/XUL", "fr": "fr/XUL", "ja": "ja/XUL", "pl": "pl/XUL", "pt": "pt/XUL" } ) }}</p> diff --git a/files/it/archive/mozilla/xul/tutorial/index.html b/files/it/archive/mozilla/xul/tutorial/index.html deleted file mode 100644 index 30a8c31e2c..0000000000 --- a/files/it/archive/mozilla/xul/tutorial/index.html +++ /dev/null @@ -1,170 +0,0 @@ ---- -title: Guida a XUL -slug: Archive/Mozilla/XUL/Tutorial -tags: - - Guide - - XUL - - XUL_guida -translation_of: Archive/Mozilla/XUL/Tutorial ---- -<p>Questo tutorial descrive <a href="/en-US/docs/XUL" title="/en-US/docs/XUL">XUL</a>, the <a href="/en-US/docs/XML" title="/en-US/docs/XML">XML</a> Il linguaggio di interfaccia utente. Questo linguaggio è stato creato per le applicazioni Mozilla e viene utilizzato per descrivere l' interfaccia utente.</p> - -<h2 id="Introduction" name="Introduction">Introduzione</h2> - -<ul> - <li><a href="/it/docs/XUL/Tutorial/Introduction" title="/en-US/docs/XUL/Tutorial/Introduction">Introduzione</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/XUL_Structure" title="/en-US/docs/XUL/Tutorial/XUL_Structure">Struttura XUL</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/The_Chrome_URL" title="/en-US/docs/XUL/Tutorial/The_Chrome_URL">Chrome URL</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Manifest_Files" title="/en-US/docs/XUL/Tutorial/Manifest_Files">Files di Manifesto</a></li> -</ul> - -<h2 id="Simple_Elements" name="Simple_Elements">Elementi basilari</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Creating_a_Window" title="/en-US/docs/XUL/Tutorial/Creating_a_Window">Creazione di una finestra</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_Buttons" title="/en-US/docs/XUL/Tutorial/Adding_Buttons">Aggiunta di pulsanti</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_Labels_and_Images" title="/en-US/docs/XUL/Tutorial/Adding_Labels_and_Images">Aggiunta di etichette e di Immagini</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Input_Controls" title="/en-US/docs/XUL/Tutorial/Input_Controls">Campi input</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Numeric_Controls" title="/en-US/docs/XUL/Tutorial/Numeric_Controls">Campi interi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/List_Controls" title="/en-US/docs/XUL/Tutorial/List_Controls">Liste</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Progress_Meters" title="/en-US/docs/XUL/Tutorial/Progress_Meters">Barre di progresso</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_HTML_Elements" title="/en-US/docs/XUL/Tutorial/Adding_HTML_Elements">Aggiunta di elementi HTML</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Using_Spacers" title="/en-US/docs/XUL/Tutorial/Using_Spacers">Aggiunta di spaziatori</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/More_Button_Features" title="/en-US/docs/XUL/Tutorial/More_Button_Features">Altre funzionalità dei pulsanti</a></li> -</ul> - -<h2 id="The_Box_Model" name="The_Box_Model">Il Modello a scatola</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/The_Box_Model" title="/en-US/docs/XUL/Tutorial/The_Box_Model">Il Modello a scatola</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Element_Positioning" title="/en-US/docs/XUL/Tutorial/Element_Positioning">Posizionamento degli elementi </a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Box_Model_Details" title="/en-US/docs/XUL/Tutorial/Box_Model_Details">Dettagli del Modello a scatola</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Groupboxes" title="/en-US/docs/XUL/Tutorial/Groupboxes">I vari Groupbox</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_More_Elements" title="/en-US/docs/XUL/Tutorial/Adding_More_Elements">Aggiunta di altri elementi</a></li> -</ul> - -<h2 id="More_Layout_Elements" name="More_Layout_Elements">Altri elementi di Layout</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Stacks_and_Decks" title="/en-US/docs/XUL/Tutorial/Stacks_and_Decks">Pile e Mazzi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Stack_Positioning" title="/en-US/docs/XUL/Tutorial/Stack_Positioning">Posizionamento Pile</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Tabboxes" title="/en-US/docs/XUL/Tutorial/Tabboxes">Tab multipli</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Grids" title="/en-US/docs/XUL/Tutorial/Grids">Griglie</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Content_Panels" title="/en-US/docs/XUL/Tutorial/Content_Panels">Contenuti esterni</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Splitters" title="/en-US/docs/XUL/Tutorial/Splitters">Separatori</a></li> -</ul> - -<h2 id="Toolbars_and_Menus" name="Toolbars_and_Menus">Barre degli strumenti e Menù</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Toolbars" title="/en-US/docs/XUL/Tutorial/Toolbars">Barre degli strumenti</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Simple_Menu_Bars" title="/en-US/docs/XUL/Tutorial/Simple_Menu_Bars">Semplici barre di menù</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/More_Menu_Features" title="/en-US/docs/XUL/Tutorial/More_Menu_Features">Altre funzionalità dei menù</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Popup_Menus" title="/en-US/docs/XUL/Tutorial/Popup_Menus">Menù a comparsa</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Scrolling_Menus" title="/en-US/docs/XUL/Tutorial/Scrolling_Menus">Menù di scorrimento</a></li> -</ul> - -<h2 id="Events_and_Scripts" name="Events_and_Scripts">Eventi e Script</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_Event_Handlers" title="/en-US/docs/XUL/Tutorial/Adding_Event_Handlers">Aggiunta di Gestori degli eventi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/More_Event_Handlers" title="/en-US/docs/XUL/Tutorial/More_Event_Handlers">Altri gestori degli eventi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Keyboard_Shortcuts" title="/en-US/docs/XUL/Tutorial/Keyboard_Shortcuts">Scorciatoie da Tastiera</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Focus_and_Selection" title="/en-US/docs/XUL/Tutorial/Focus_and_Selection">Focus e Selezione</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Commands" title="/en-US/docs/XUL/Tutorial/Commands">Comandi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Updating_Commands" title="/en-US/docs/XUL/Tutorial/Updating_Commands">Aggiorna i Comandi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Broadcasters_and_Observers" title="/en-US/docs/XUL/Tutorial/Broadcasters_and_Observers">Emettitori e Osservatori</a></li> -</ul> - -<h2 id="Document_Object_Model" name="Document_Object_Model">Modello ad oggetti del documento</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Document_Object_Model" title="/en-US/docs/XUL/Tutorial/Document_Object_Model">Modello ad oggetti del documento</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Modifying_a_XUL_Interface" title="/en-US/docs/XUL/Tutorial/Modifying_a_XUL_Interface">Modificare un interfaccia XUL</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Manipulating_Lists" title="/en-US/docs/XUL/Tutorial/Manipulating_Lists">ManIpolare liste</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Box_Objects" title="/en-US/docs/XUL/Tutorial/Box_Objects">Scatole a oggetti</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/XPCOM_Interfaces" title="/en-US/docs/XUL/Tutorial/XPCOM_Interfaces">XPCOM Interfacce</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/XPCOM_Examples" title="/en-US/docs/XUL/Tutorial/XPCOM_Examples">XPCOM Esempi</a></li> -</ul> - -<h2 id="Trees" name="Trees">Alberi</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Trees" title="/en-US/docs/XUL/Tutorial/Trees">Alberi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/More_Tree_Features" title="/en-US/docs/XUL/Tutorial/More_Tree_Features">Altre funzionalità degli Alberi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Tree_Selection" title="/en-US/docs/XUL/Tutorial/Tree_Selection">Selezione dall' Albero</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Custom_Tree_Views" title="/en-US/docs/XUL/Tutorial/Custom_Tree_Views">Vista dell' albero personalizzata</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Tree_View_Details" title="/en-US/docs/XUL/Tutorial/Tree_View_Details">Dettagli della vista dell' Albero</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Tree_Box_Objects" title="/en-US/docs/XUL/Tutorial/Tree_Box_Objects">Albero ad oggetti</a></li> -</ul> - -<h2 id="RDF_and_Templates" name="RDF_and_Templates">RDF e Modelli</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Introduction_to_RDF" title="/en-US/docs/XUL/Tutorial/Introduction_to_RDF">Introduzione all' RDF</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Templates" title="/en-US/docs/XUL/Tutorial/Templates">Modelli</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Trees_and_Templates" title="/en-US/docs/XUL/Tutorial/Trees_and_Templates">Alberi e Modelli</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/RDF_Datasources" title="/en-US/docs/XUL/Tutorial/RDF_Datasources">RDF sorgenti di dati</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Advanced_Rules" title="/en-US/docs/XUL/Tutorial/Advanced_Rules">Regole avanzate</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Persistent_Data" title="/en-US/docs/XUL/Tutorial/Persistent_Data">Dati persistenti</a></li> -</ul> - -<h2 id="Skins_and_Locales" name="Skins_and_Locales">Temi e Località</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_Style_Sheets" title="/en-US/docs/XUL/Tutorial/Adding_Style_Sheets">Aggiunt a di fogli di stile</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Styling_a_Tree" title="/en-US/docs/XUL/Tutorial/Styling_a_Tree">Aggiunta di stile ad un Albero</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Modifying_the_Default_Skin" title="/en-US/docs/XUL/Tutorial/Modifying_the_Default_Skin">Modifica il tema di default</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Creating_a_Skin" title="/en-US/docs/XUL/Tutorial/Creating_a_Skin">Crea un tema</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Localization" title="/en-US/docs/XUL/Tutorial/Localization">Localizzazione</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Property_Files" title="/en-US/docs/XUL/Tutorial/Property_Files">File di proprietà</a></li> -</ul> - -<h2 id="Bindings" name="Bindings">Collegamenti</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Introduction_to_XBL" title="/en-US/docs/XUL/Tutorial/Introduction_to_XBL">Introduzione a XBL</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Anonymous_Content" title="/en-US/docs/XUL/Tutorial/Anonymous_Content">Contenuti anonimi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/XBL_Attribute_Inheritance" title="/en-US/docs/XUL/Tutorial/XBL_Attribute_Inheritance">XBL ereditarietà degli attributi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_Properties_to_XBL-defined_Elements" title="/en-US/docs/XUL/Tutorial/Adding_Properties_to_XBL-defined_Elements">Aggiunta di proprietà</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_Methods_to_XBL-defined_Elements" title="/en-US/docs/XUL/Tutorial/Adding_Methods_to_XBL-defined_Elements">Aggiunta di metodi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Adding_Event_Handlers_to_XBL-defined_Elements" title="/en-US/docs/XUL/Tutorial/Adding_Event_Handlers_to_XBL-defined_Elements">Aggiunta di gestori di eventi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/XBL_Inheritance" title="/en-US/docs/XUL/Tutorial/XBL_Inheritance">XBL ereditarietà</a></li> - <li><a href="/en-US/docs/Mozilla/Tech/XUL/Tutorial/Using_XBL_from_stylesheets">Creazione di contenuti riusabili usando CSS e XBL</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/XBL_Example" title="/en-US/docs/XUL/Tutorial/XBL_Example">XBL Esempi</a></li> -</ul> - -<h2 id="Specialized_Window_Types" name="Specialized_Window_Types">Tipi di finestre specializzate</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Features_of_a_Window" title="/en-US/docs/XUL/Tutorial/Features_of_a_Window">Funzionalità di una finestra</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Creating_Dialogs" title="/en-US/docs/XUL/Tutorial/Creating_Dialogs">Creazione di dialoghi</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Open_and_Save_Dialogs" title="/en-US/docs/XUL/Tutorial/Open_and_Save_Dialogs">Dialoghi di apertura e salvataggio</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Creating_a_Wizard" title="/en-US/docs/XUL/Tutorial/Creating_a_Wizard">Creazione di Guida</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/More_Wizards" title="/en-US/docs/XUL/Tutorial/More_Wizards">Più guide</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Overlays" title="/en-US/docs/XUL/Tutorial/Overlays">Livelli</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Cross_Package_Overlays" title="/en-US/docs/XUL/Tutorial/Cross_Package_Overlays">Livelli tra package</a></li> -</ul> - -<h2 id="Installation" name="Installation">Installazione</h2> - -<ul> - <li><a href="/en-US/docs/XUL/Tutorial/Creating_an_Installer" title="/en-US/docs/XUL/Tutorial/Creating_an_Installer">Creazione di un installer</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Install_Scripts" title="/en-US/docs/XUL/Tutorial/Install_Scripts">Aggiunta di scripts</a></li> - <li><a href="/en-US/docs/XUL/Tutorial/Additional_Install_Features" title="/en-US/docs/XUL/Tutorial/Additional_Install_Features">Ulteriori funzionalità di Installazione</a></li> -</ul> - -<div class="note"> -<p>Questa guida XUL è stata originariamente creata da <a class="external" href="http://www.xulplanet.com/ndeakin/">Neil Deakin</a>. Lui ha cortesemente dato a noi il permesso di usarla come parte di <a href="/en-US/docs/Project:About" title="Project:About">MDN</a>.</p> -</div> - -<div class="originaldocinfo"> -<h2 id="Original_Document_Information" name="Original_Document_Information">Informazioni sul documento originale</h2> - -<ul> - <li>Autore: <a class="external" href="http://www.xulplanet.com/ndeakin/">Neil Deakin</a></li> - <li>Informazione di Copyright: © 1999-2005 XULPlanet.com</li> -</ul> -</div> - -<p> </p> diff --git a/files/it/archive/mozilla/xulrunner/a_cosa_serve_xulrunner/index.html b/files/it/archive/mozilla/xulrunner/a_cosa_serve_xulrunner/index.html deleted file mode 100644 index 6ad5d00746..0000000000 --- a/files/it/archive/mozilla/xulrunner/a_cosa_serve_xulrunner/index.html +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: A cosa serve XULRunner -slug: Archive/Mozilla/XULRunner/A_cosa_serve_XULRunner -translation_of: Archive/Mozilla/XULRunner/What_XULRunner_Provides ---- -<p> </p> -<p>L'obbiettivo di <a href="/it/XULRunner" title="it/XULRunner">XULRunner</a> è fornire una soluzione per il rilascio di applicazioni <a href="/it/XUL" title="it/XUL">XUL</a> (in particolare Firefox e Thunderbird) e fornire un meccanismo per incorporare parti di programma. Le seguenti funzionalità sono già state implementate o sono pianificate:</p> -<p> </p> -<h3 id="Funzionalit.C3.A0_di_Gecko" name="Funzionalit.C3.A0_di_Gecko">Funzionalità di Gecko</h3> -<ul> - <li><a href="/it/XPCOM" title="it/XPCOM">XPCOM</a></li> - <li>Funzionalità di rete</li> - <li>Il motore di rendering <a href="/it/Gecko" title="it/Gecko">Gecko</a></li> - <li>Supporto alle modifiche e alle transazioni <a href="/it/DOM" title="it/DOM">DOM</a> (senza interfaccia utente)</li> - <li>Crittografia</li> - <li><a href="/it/XBL" title="it/XBL">XBL</a> (XBL2 in futuro)</li> - <li><a href="/it/XUL" title="it/XUL">XUL</a></li> - <li><a href="/it/SVG" title="it/SVG">SVG</a></li> - <li><a href="/it/XSLT" title="it/XSLT">XSLT</a></li> - <li><a href="/it/XML_Extras" title="it/XML_Extras">XML Extras</a> (<code><a href="/it/XMLHttpRequest" title="it/XMLHttpRequest">XMLHttpRequest</a></code>, <code><a href="/it/DOMParser" title="it/DOMParser">DOMParser</a></code>, etc.)</li> - <li>Web Services (SOAP)</li> - <li>Supporto all'aggiornamento automatico <em>(ancora incompleto)</em></li> - <li>Barra di ricerca nel documento</li> - <li>Cronologia</li> - <li>Supporto per l'accessibilità</li> - <li>Servizi IPC per la comunicazione tra applicazioni basate su Gecko <em>(ancora incompleto)</em></li> - <li>Interfacce storage/sqlite <em>(per ora, non è attivo per default)</em></li> -</ul> -<h3 id="Funzionalit.C3.A0_dell.27interfaccia_utente" name="Funzionalit.C3.A0_dell.27interfaccia_utente">Funzionalità dell'interfaccia utente</h3> -<p>I seguenti elementi dell'interfaccia utente sono forniti da XULRunner, ma possono essere sovrascritti dai programmi quando necessario:</p> -<ul> - <li>Le API e l'interfaccia utente per installare, disinstallare e aggiornare le applicazioni XUL. Si veda {{ interwiki('wikimo', 'XUL:Installation_Story', 'wikimo:XUL:Installation Story') }} (EN).</li> - <li>Extension Manager</li> - <li>File picker (utilizza il filepicker nativo del sistema)</li> - <li>Barra di ricerca</li> - <li>Finestre di dialogo e interfaccia utente dell'Help</li> - <li>Interfaccia utente per la sicurezza (SSL, etc)</li> -</ul> -<h3 id="Incorporare_le_API" name="Incorporare_le_API">Incorporare le API</h3> -<p>Le API seguenti sono contenute in XULRunner:</p> -<ul> - <li>Cross-platform embedding (XRE_InitEmbedding)</li> - <li><a href="/it/JavaXPCOM" title="it/JavaXPCOM">JavaXPCOM</a></li> - <li><a href="/it/PyXPCOM" title="it/PyXPCOM">PyXPCOM</a> <em>(incompleto)</em></li> - <li>gtkmozembed (solo su Linux) <em>(incompleto)</em></li> - <li>Widget NSView (solo su MacOS X) <em>(incompleto)</em></li> - <li>Controlli ActiveX (solo su Windows) <em>(incompleto)</em></li> -</ul> -<h3 id="La_lista_dei_.22forse.22" name="La_lista_dei_.22forse.22">La lista dei "forse"</h3> -<p>Le seguenti funzionalità sono state discusse e potrebbero essere incluse in XULRunner per il tempo lo permette e le dimensioni del codice saranno accettabili:</p> -<ul> - <li>LDAP</li> - <li>Controllo ortografico (con o senza i dizionari), si veda il <a class="link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=285977">bug 285977</a></li> - <li>Supporto di base per la migrazione dei profili (estendibile dalle specifiche applicazioni)</li> -</ul> -<h3 id="Cosa_rimane_fuori" name="Cosa_rimane_fuori">Cosa rimane fuori</h3> -<p>XULRunner non fornisce:</p> -<ul> - <li>Interfaccia utente per i bookmark e la cronologia (deve essere creata con l'applicazione)</li> - <li><a href="/it/XForms" title="it/XForms">XForms</a> (sarà disponibile con un'estensione)</li> -</ul> -<p><span class="comment">Interwiki Language Links</span></p> -<p>{{ languages( { "en": "en/XULRunner/What_XULRunner_Provides", "ja": "ja/XULRunner/What_XULRunner_Provides" } ) }}</p> diff --git a/files/it/archive/mozilla/xulrunner/applicazioni_basate_su_xulrunner/index.html b/files/it/archive/mozilla/xulrunner/applicazioni_basate_su_xulrunner/index.html deleted file mode 100644 index fddf5aef0f..0000000000 --- a/files/it/archive/mozilla/xulrunner/applicazioni_basate_su_xulrunner/index.html +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Applicazioni basate su XULRunner -slug: Archive/Mozilla/XULRunner/Applicazioni_basate_su_XULRunner -tags: - - XULRunner -translation_of: Archive/Mozilla/XULRunner/Hall_of_Fame ---- -<p> -</p><p>In questa pagina tentiamo di tenere traccia di tutte le applicazioni esistenti basate su <a href="it/XULRunner">XULRunner</a>. -</p> -<ul><li> <a href="http://chatzilla.rdmsoft.com/xulrunner/" class="external">ChatZilla</a> -<ul><li> Una versione standalone del client IRC ChatZilla. -</li></ul> -</li><li> <a href="http://daim.project.free.fr/" class="external">DAIM</a> -<ul><li> Uno strumento per costruire analisi di immagini, creato partendo da una libreria professionale -</li></ul> -</li><li> <a href="http://www.getdemocracy.com/" class="external">Democracy Player</a> -<ul><li> Browser e player per TV -</li></ul> -</li><li> <a href="http://exch.mozdev.org/" class="external">Exch</a> -<ul><li> Uno strumento finanziario che utilizza dati aggiornati reperibili su <a href="http://finance.yahoo.com/currency" class=" external" rel="freelink">http://finance.yahoo.com/currency</a>. Esiste come estensione di Firefox e come programma XUL standalone. -</li></ul> -</li><li> <a href="http://www.jakinbidea.com/?page_id=39" class="external">GencatRss</a> -<ul><li> Un gestore di RSS. -</li></ul> -</li><li> <a href="http://services.google.com/adwordseditor/index.html" class="external">Google AdWords Editor</a> -<ul><li> Un'applicazione per gestire il proprio account su Google. -</li></ul> -</li><li> <a href="http://www.epigoon.com/wiki/index.php/Mozchat" class="external">Mozchat</a> -<ul><li> Un client Jabber. -</li></ul> -</li><li> <a href="http://www.songbirdnest.com/" class="external">Songbird</a> -<ul><li> Un player musicale. -</li></ul> -</li><li> <a href="http://www.treebuilder.de/default.asp?file=257091.xml" class="external">SVGclock</a> -<ul><li> Un orologio basato su SVG. -</li></ul> -</li><li> <a href="http://blogs.acceleration.net/ryan/articles/2018.aspx" class="external">TaskPool</a> -<ul><li> Una piccola applicazione che aiuta a tenere traccia delle cose da fare nel tempo. E' possibile aggiungere dei compiti, attivarli, disattivarli e scandisce i secondi. -</li></ul> -</li><li> <a href="http://www.openwengo.org" class="external">WengoPhone</a> -<ul><li> Un Messenger nonchè client IM/VoIP, basato su SIP/XMPP. -</li></ul> -</li></ul> -{{ languages( { "en": "en/XULRunner_Hall_of_Fame", "fr": "fr/Floril\u00e8ge_des_applications_XULrunner" } ) }} diff --git a/files/it/archive/mozilla/xulrunner/getting_started_with_xulrunner/index.html b/files/it/archive/mozilla/xulrunner/getting_started_with_xulrunner/index.html deleted file mode 100644 index 0a9c732401..0000000000 --- a/files/it/archive/mozilla/xulrunner/getting_started_with_xulrunner/index.html +++ /dev/null @@ -1,271 +0,0 @@ ---- -title: Primi passi con XULRunner -slug: Archive/Mozilla/XULRunner/Getting_started_with_XULRunner -translation_of: Archive/Mozilla/XULRunner/Getting_started_with_XULRunner ---- -<p>{{ Next("Windows and menus in XULRunner") }}</p> - -<p>Questo articolo è stato rivisto e riscritto da Luigi Sentina. La mission di questo è quella di mostrare con un semplice esempio come sia facile costruire applicazioni dektop e molto altro ancora con la tecnologia messa a disposizione da XULrunner. L'articolo originale un pò "datato" (dato che faceva riferimento ad una vecchia versione di XULRunner) è stato rivisto sulla base dell'esempio originale (dato che non realmente testato per qualsiasi informazione potete contattarmi a info@luigisentina.com) Nell'esempio verrà creata la classica applicazione "Ciao Mondo" utilizzando la versione "<strong style="line-height: 1.5;">runtime" (vedere sotto).</strong></p> - -<p><span style="line-height: 1.5;">L'alternativa è la versione SDK ma ci vogliono conoscenze del linguaccio C++ e affini! Per correttezza vi rimando il link originale se qualcuno dovesse essere interessato: </span><a href="/en-US/docs/Creating_XULRunner_Apps_with_the_Mozilla_Build_System" style="line-height: 1.5;" title="/en-US/docs/Creating_XULRunner_Apps_with_the_Mozilla_Build_System">Creating XULRunner Apps with the Mozilla Build System</a><span style="line-height: 1.5;">.</span></p> - -<h2 id="Step_1:_Download_XULRunner" name="Step_1:_Download_XULRunner">Step 1: Download XULRunner</h2> - -<p>Puoi trovare il download di <a href="/en-US/docs/XULRunner" title="/en-US/docs/XULRunner">XULRunner</a> nella pagina principale di MDC. <span style="font-size: 14px; line-height: 1.5;">Dal momento che non stiamo creando componenti XPCOM binari, Dobbiamo scaricare il pacchetto di <strong>runtime</strong> XULRunner, non l'SDK.</span></p> - -<p>Il download di XULRunner per Windows prevede un file zip da scompattare in una determianta "posizione" all'interno della nostra applicazione. Quindi non c'e nessun programma da installare. Il vantaggio è propio questo, non avendo un installer rende possibile creare applicazioni "stand-alone"<span style="font-size: 14px; line-height: 1.5;"> ovvero quelle applicazioni che funzionano in maniera autonoma e svincolata da altri oggetti o software. Inoltre il fatto che non si "agganci" al sistema Windows non rischiamo di creare alcun conflitto da una possibile installazione o disintallazione di XULRunner.</span></p> - -<p>La versione MAC è distribuita nel formato compresso tar.bz2. Come per Windows estraggo il contenuto direttamente nella mia applicazione anche se in molte guide vi diranno di installarlo nel percorso locale: <code>/Library/Frameworks</code>.</p> - -<p>In Ubuntu desktop e le sue varianti (Xubuntu, Kubuntu, ...), dalla versione 11.10 (Oneiric Ocelot), XULRunner non è più mantenuto e non esiste nel repository di Ubuntu. Pertanto, è necessario compilare XULRunner manualmente o scaricare una versione binaria dal server FTP di Mozilla. Un modo per raggiungere questo obiettivo è quello di eseguire il seguente script ogni volta che si desidera installare una nuova versione:</p> - -<div class="note"><code>FIREFOX_VERSION=`grep -Po "\d{2}\.\d+" /usr/lib/firefox/platform.ini`<br> -ARCH=`uname -p`<br> -XURL=https://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/$FIREFOX_VERSION/runtimes/xulrunner-$FIREFOX_VERSION.en-US.linux-$ARCH.tar.bz2<br> -cd /opt<br> -sudo sh -c "wget -O- $XURL | tar -xj"<br> -sudo ln -s /opt/xulrunner/xulrunner /usr/bin/xulrunner<br> -sudo ln -s /opt/xulrunner/xpcshell /usr/bin/xpcshell </code></div> - -<p>Per comodità si potrebbe anche salvare questo script in un file. Nota: Se si utilizza Firefox costruire dal repository Ubuntuzilla e sostituire / usr / lib / firefox / platform.ini con / opt / firefox / platform.ini.</p> - -<h2 id="Step_2:__Install_XULRunner" name="Step_2:__Install_XULRunner">Step 2: Installazione di XULRunner</h2> - -<p>Su Windows, scompattare temporanemaente il file zip in una cartella qualsiasi. Come vedremo più avani per creare un applicazione esiste una gerarchia per le applicazioni basata su XULRunner. Quindi in seguito verrà spostata o copiata nella posizione finale.</p> - -<p>Su Mac, estrarre il contenuto del archivio tar.bz2 , e copiarne (temporaneamente) il contenuto nella directory: <code>/Library/Frameworks</code> directory, o se preferite anche in un altra posizione.</p> - -<p>Su Linux, è sufficiente scompattare l'archivio, se si utilizza XULRunner pre-release.</p> - -<div class="note"> -<p>In alternativa, se hai scaricato l'archivio compresso di XULRunner e vuoi installare sul vostro sistema potete farlo eseguendo</p> - -<p><code>xulrunner --register-global</code></p> - -<p>come amministratore per registrare XULRunner per tutti gli utenti della macchina.<br> - <br> - Per registrare XULRunner per una singolo utente</p> - -<p><code>xulrunner --register-user</code></p> -</div> - -<div class="note"> -<p>In tutti i sistemi puoi decomprimere il file omni.ja in qualche directory cambiare l'estensione del file in ".zip" e quindi utilizzare lo strumento di decompressione del file system normale per aprirlo. I contenuti di omni.ja sono disponibili per le applicazioni XULRunner e utili risorse per costruire facilmente incredibili applicazioni!</p> -</div> - -<h2 id="Step_3:_Create_the_application_folder_structure" name="Step_3:_Create_the_application_folder_structure">Step 3: Creare la struttura delle cartelle</h2> - -<p>Per capire la struttura di un' applicazione XULRunner procederemo con il classico esempio "Ciao mondo".</p> - -<p>Su Windows ho creato una nuova cartella nel percorso <code>c:\program files\miaapp </code><br> - La struttura "gerarchica" di un applicazione su tutti i sistemi operativi è la seguente:</p> - -<pre>+ miaapp/ -| -+-+ chrome/ -| | -| +-+ content/ -| | | -| | +-- main.xul -| | | -| | +-- main.js -| | -| +-- chrome.manifest -| -+-+ defaults/ -| | -| +-+ preferences/ -| | -| +-- prefs.js -| -+-- application.ini -| -+-- chrome.manifest -</pre> - -<p>Nell'esempio si noti che ci sono 5 file nella struttura di cartelle: Application.ini, chrome.manifest (2), prefs.js e main.xul. Il file / chrome / chrome.manifest è facoltativo, ma potrebbe essere utile per la retrocompatibilità. Vedere la nota che segue.</p> - -<div class="note"> -<p>Per maggiori dettagli sulla struttura di fasci installabili in generale, consultare:: <a href="/en-US/docs/Bundles" title="/en-US/docs/Bundles">Structure of an installable bundle</a>.</p> -</div> - -<div class="note"><strong>Nota:</strong> Nelle prime release di XULRunner il file chrome.manifest risiedeva nella root principale come mostrato nella gerarchia sopra. Nelle versioni precedenti è stato spostato nella cartella chrome. Tuttavia per avere una retrocompatibilità lasceremo entrambe i file dove nel primo (root) avrà il link al secondo file dentro chrome e quindi al suo interno comparirà solamente il path: manifest chrome/chrome.manifest. Il contenuto del secondo è spiegato più sotto. </div> - -<h2 id="Step_4:_Set_up_application.ini" name="Step_4:_Set_up_application.ini">I file nell'applicazione di esempio<br> - <br> - Step 4: <code>Il file application.ini</code></h2> - -<p>Il file <code><a href="/en-US/docs/XUL_Application_Packaging" title="/en-US/docs/XUL_Application_Packaging">application.ini</a> è il punto di ingresso per la nostra applicazione. </code>In questo file è sono specificate alcuni parametri di configurazione per la piattaforma XULrunner usata. <span style="font-size: 14px; line-height: 1.5;">Sotto per il nostro esempio</span></p> - -<pre>[App] -Vendor=XULTest -Name=miaapp -Version=1.0 -BuildID=20100901 -ID=xulapp@xultest.org - -[Gecko] -MinVersion=16.0 -MaxVersion=22.0 -</pre> - -<div class="note"><strong>Nota:</strong> <code>MinVersion</code> e <code>MaxVersion</code> sono fondamentali per il funzionamento indicano il "range" della versione XULRunner della nostra applicazione. Al momento della stesura di questo testo l'ultima versione disponibile è la 22. (MaxVersion:22.0). </div> - -<div class="note"><strong>Nota</strong>: Il nome della nostra applicazione deve avere un minimo di 3 caratteri tutti minuscoli</div> - -<h2 id="Step_5:_Set_up_the_chrome_manifest" name="Step_5:_Set_up_the_chrome_manifest">Step 5: I file chrome.manifest</h2> - -<p>Il file <a href="/en-US/docs/Chrome_Registration" title="/en-US/docs/Chrome_Registration">chrome manifest</a> è usato da XULRunner per specificare gli URI (percorsi) per le risorse utilizzate. Queste possono essere file JAR o file non compressi o cartelle. Nel nostro esempio utilizziamo cartelle non compresse. Questo è il contenuto del nostro file nella directory <strong>c<code>hrome/chrome.manifest</code>:</strong> <span style="font-size: 14px; line-height: 1.5;">(da non confondere con quello nella root principale)</span></p> - -<pre class="eval"> content miaapp content/ -</pre> - -<p>Come gia spiegato nello Step 3, il file <code>chrome.manifest</code> <strong>nella root princiapale</strong> conterrà solamente il path che punta al "reale" <code>chrome.manifest.</code>Il contenuto pertanto (ripeto) sarà:</p> - -<pre>manifest chrome/chrome.manifest</pre> - -<h2 id="Step_6:_Set_up_preferences" name="Step_6:_Set_up_preferences">Step 6: Il file prefs.js</h2> - -<p>Il file <a href="/en-US/docs/Mozilla/Preferences/A_brief_guide_to_Mozilla_preferences" title="/en-US/docs/Mozilla/Preferences/A_brief_guide_to_Mozilla_preferences">prefs.js</a> può contenere molte proprietà a seconde del tipo di applicazione che state creando (per farvi un idea digitate sul browser Firefox about:config e premete il pulsante "farò attenzione"). Nel nostro esempio usiamo una configurazione minima, la più importante che non può mancare è la prima riga. Questa infatti setta la prima pagina (finestra) XUL che verrà aperta quando lanceremo la nostra applicazione (nell' esempio main.xul).<br> - Queso è il contenuto:</p> - -<pre class="eval">pref("toolkit.defaultChromeURI", "<span class="external">chrome://myapp/content/main.xul</span>"); - -/* debugging prefs, disable these before you deploy your application! */ -pref("browser.dom.window.dump.enabled", true); -pref("javascript.options.showInConsole", true); -pref("javascript.options.strict", true); -pref("nglayout.debug.disable_xul_cache", true); -pref("nglayout.debug.disable_xul_fastload", true); -</pre> - -<div class="note"> -<p>Le varie prefs sono descritte nel dettagli qui: <a href="/en-US/docs/XULRunner/Specifying_Startup_Chrome_Window" title="/en-US/docs/XULRunner/Specifying_Startup_Chrome_Window">XULRunner:Specifying Startup Chrome Window</a>.</p> - -<p>Per quelle di Debug qui: <a href="/en-US/docs/Debugging_a_XULRunner_Application" title="/en-US/docs/Debugging_a_XULRunner_Application">Debugging a XULRunner Application</a></p> -</div> - -<h2 id="Step_7:_Create_some_XUL" name="Step_7:_Create_some_XUL">Step 7: Il file main.xul</h2> - -<p>Faccio un premessa, il nome "main.xul" non è obbligatorio la pagina può chiamarsi come meglio credete l'importante è che vi ricordiate di cambiare il nome anche nel file prefs.js allo step 6. Creeremo una semplice <a href="/en-US/docs/XUL/window" title="/en-US/docs/XUL/window">XUL window</a>, (finestra xul) con il minimo indispensabile per il nostro esmpio "Ciao Mondo". Ecco come si presenta il nostro file <span style="font-size: 14px; line-height: 1.5;">main.xul:</span></p> - -<pre><?xml version="1.0"?> - -<?xml-stylesheet href="chrome://global/skin/" type="text/css"?> - -<window id="main" title="My App" width="300" height="300" xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"> - - <script type="application/javascript" src="chrome://myapp/content/main.js"/> - - <caption label="Ciao Mondo"/> - <separator/> - <button label="More >>" oncommand="showMore();"/> - <separator/> - <description id="more-text" hidden="true">E' solamente un semplie esempio ma con l'esperienza potrete creare delel vere e proprie applicazioni professionali!</description> - -</window> -</pre> - -<div class="note"><strong>Nota:</strong> Assicurarsi che no vi siano spazi bianchi all'inizio del filee XML/XUL</div> - -<p>come potete notare viene incluso nel file xul il relativo file .Js (è buona norma chiamarli nello stesso modo). Nel "button" viene richiamata attraverso il "command" (che equivale al classico "onclick") la funzione <strong>shoMore(); </strong>che ovviamente sarà all'interno del file javascript. Si possono includere molti file .Js a seconde delle esigenze!<br> - </p> - -<h2 id="Step_7:_Create_some_XUL" name="Step_7:_Create_some_XUL" style="line-height: 22.79199981689453px;">Il file main.js</h2> - -<p>ecco l'unica funzione all'interno del nostro file main.js:</p> - -<pre>function showMore() { - document.getElementById("more-text").hidden = false; -} -</pre> - -<div class="note"> -<p>Per maggiori informazioni su potete vedere qui: <a href="/en-US/docs/XUL" title="/en-US/docs/XUL">XUL</a></p> - -<p>Per implementare html ai file XUL vedere qui <a href="/en-US/docs/XUL/Tutorial/Adding_HTML_Elements" title="/en-US/docs/XUL/Tutorial/Adding_HTML_Elements">Adding HTML Elements</a>.</p> -</div> - -<h2 id="Step_8:_Run_the_application" name="Step_8:_Run_the_application">Step 8: Eseguire l' applicazione</h2> - -<p>Finalmente vediamo come eseguire la nostra applicazione.</p> - -<h3 id="Windows">Windows</h3> - -<p>Apriamo una finestra di prompt, e proviamo ad eseguire questo comando:</p> - -<pre class="eval">c:\miaapp\xulrunner\xulrunner.exe c:\miaapp\application.ini -</pre> - -<p>Se avete creato l'applicazione sulla cartella programmi potete usare</p> - -<pre><span style="font-family: courier new,andale mono,monospace; line-height: normal;">%ProgramFiles%\</span><span style="line-height: normal;">miaapp\xulrunner\xulrunner.exe </span><span style="line-height: normal;">%ProgramFiles%</span><span style="line-height: normal;">\miaapp\application.ini</span> -</pre> - -<p><span style="font-size: 14px; line-height: 1.572;">per la cartella "Program File (x86)" nei sistemi a 64 bit usare questo: </span></p> - -<pre><span style="font-family: courier new,andale mono,monospace; line-height: normal;">%ProgramFiles(x86)</span></pre> - -<div class="note"> -<p><span style="font-size: 14px; line-height: 1.572;"><strong>Nota</strong>: </span><span style="line-height: 22px;"> Puoi anche creare un vero e proprio file di installer per distribuire la tua creazione per maggiori dettagli vedere</span><span style="font-size: 14px; line-height: 1.572;"> <a href="/it-IT/docs/XUL_Application_Packaging" title="/en-US/docs/XUL_Application_Packaging">Creare un Installer per Applicazioni XUL</a>.</span></p> -</div> - -<h3 id="Mac">Mac</h3> - -<p>On the Mac, before you can run a XULRunner application with everything intact, you must install it using the <code>--install-app</code> xulrunner commandline flag. Installing the application creates an OS X application bundle:</p> - -<pre class="eval"> /Library/Frameworks/XUL.framework/xulrunner-bin --install-app /<path>/<to>/myapp.zip -</pre> - -<p>Once installed, you can run the application:</p> - -<pre class="eval"> /Library/Frameworks/XUL.framework/xulrunner-bin "/Applications/Finkle/TestApp.app/Contents/Resources/application.ini" -</pre> - -<p>You may run it without installing (but with the menu bar and dock icon missing) in OS X by typing:</p> - -<pre>/Library/Frameworks/XUL.framework/xulrunner-bin "/<full path>/TestApp/application.ini" -</pre> - -<div class="note"> -<p>Note: The full path is required or a "Error: couldn't parse application.ini."-message will be returned.</p> -</div> - -<p>This might also be simplified using a very simple shell script (i call mine "run.sh"):</p> - -<pre>#!/bin/sh -/Library/Frameworks/XUL.framework/xulrunner-bin `pwd`/application.ini -</pre> - -<h3 id="Linux">Linux</h3> - -<p>On Ubuntu, you can run the application from a terminal. First change into the <code>\myapp</code> folder, then start the application by:</p> - -<pre class="eval"> xulrunner application.ini -</pre> - -<p>You should now see a window that looks something like this. This particular screenshot is from Ubuntu 10.</p> - -<p><img alt="myapp-screenshot.png" class="default internal" src="/@api/deki/files/4679/=myapp-screenshot.png"></p> - -<h3 id="Alternative:_Use_Firefox3_-app_to_run_XUL_apps" name="Alternative:_Use_Firefox3_-app_to_run_XUL_apps">Alternative: Run XUL apps with Firefox</h3> - -<p>With Firefox 3 and later, you can tell the Firefox executable to run a XUL application from the command line. The XUL application will run instead of the Firefox browser that normally starts. This is similar to starting a XUL app using XULRunner. See <a href="/en/XULRunner_tips#Using_Firefox_to_run_XULRunner_applications" title="en/XULRunner_tips#Using_Firefox_to_run_XULRunner_applications">Using Firefox to run XULRunner applications</a>. This does not work if Firefox itself was installed as a XUL app - you need to use the installed XULRunner directly.</p> - -<h2 id="Further_Reading">Further Reading:</h2> - -<p>There are many things you can do with XULRunner. Before you get too far into things you might want to read the <a href="/en-US/docs/XULRunner_tips" title="/en-US/docs/XULRunner_tips">XULRunner tips</a> article. Also, throughout this tutorial you've been introduced to various bits of the <a href="/en-US/docs/Toolkit_API" title="/en-US/docs/Toolkit_API">Toolkit API</a> and it may help you to get familiar with it. Once you've got an application that's ready for the world you'll love our article titled <a href="/en-US/docs/XULRunner/Deploying_XULRunner_1.8" title="/en-US/docs/XULRunner/Deploying_XULRunner_1.8">Deploying XULRunner</a>.</p> - -<p>For now, click the "next" link to learn about windows and menus in XULRunner!</p> - -<p>{{ Next("Windows and menus in XULRunner") }}</p> - -<div class="originaldocinfo"> -<h2 id="Original_Document_Information" name="Original_Document_Information">Original Document Information</h2> - -<ul> - <li>Author: Mark Finkle, October 2, 2006</li> -</ul> -</div> - -<p>{{ languages( { "ja": "ja/Getting_started_with_XULRunner", "ko": "ko/Getting_started_with_XULRunner" } ) }}</p> diff --git a/files/it/archive/mozilla/xulrunner/index.html b/files/it/archive/mozilla/xulrunner/index.html deleted file mode 100644 index ecb6ce492f..0000000000 --- a/files/it/archive/mozilla/xulrunner/index.html +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: XULRunner -slug: Archive/Mozilla/XULRunner -translation_of: Archive/Mozilla/XULRunner ---- -<p> </p> -<p><strong>XULRunner</strong> è un pacchetto di runtime Mozilla che può essere utilizzato per l'avvio di applicazioni <a href="/it/XUL" title="it/XUL">XUL</a> + <a href="/it/XPCOM" title="it/XPCOM">XPCOM</a>, anche ricche come Firefox e Thunderbird. Fornisce il meccanismo per installare, aggiornare e disinstallare tali applicazioni. XULRunner fornisce inoltre <a href="/it/Libxul" title="it/Libxul">libxul</a>, una soluzione che permette di incorporare le tecnologie Mozilla in altri programmi.</p> -<table class="topicpage-table"> <tbody> <tr> <td> <h4 id="Versioni">Versioni</h4> <div class="note"> <p>XULRunner 1.8.0.4 è una <em>developer preview</em> stabile, basata sullo stesso codice di base di Firefox 1.5.0.4. E' disponibile per <a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.0.4/win32/en-US/xulrunner-1.8.0.4.en-US.win32.zip">Windows</a>, <a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.0.4/mac/en-US/xulrunner-1.8.0.4.en-US.mac.dmg">Mac OS X</a> e <a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.0.4/linux-i686/en-US/xulrunner-1.8.0.4.en-US.linux-i686.tar.gz">Linux</a>, in inglese. Si vedano le <a href="/it/Note_di_rilascio_di_XULRunner_1.8.0.4" title="it/Note_di_rilascio_di_XULRunner_1.8.0.4">note di rilascio</a> per ulteriori dettagli sull'installazione, la disinstallazione e altro.</p> </div> <h4 id="Panoramica">Panoramica</h4> <ul> <li>{{ interwiki('wikimo', 'XULRunner:Roadmap', 'Development Roadmap') }} (EN)</li> <li><a href="/it/XULRunner/A_cosa_serve_XULRunner" title="it/XULRunner/A_cosa_serve_XULRunner">A cosa serve XULRunner</a></li> <li><a href="/it/XULRunner_FAQ" title="it/XULRunner_FAQ">XULRunner FAQ</a></li> <li>Nightly builds: <a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-mozilla1.8.0/">stable-1.8.0branch</a> <a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-trunk/">unstable-trunk</a></li> </ul> <h4 id="Documentazione">Documentazione</h4> <dl> <dt><a href="/it/Applicazioni_di_esempio" title="it/Applicazioni_di_esempio">Applicazioni di esempio</a></dt> <dd>Semplici applicazioni che è possibile copiare.</dd> </dl> <dl> <dt><a class="external" href="http://blogs.acceleration.net/ryan/archive/2005/05/06/1073.aspx">A XULRunner Tutorial</a> (EN)</dt> <dd><small>Una breve introduzione a XULRunner.</small></dd> </dl> <dl> <dt><a href="/it/XULRunner/Rilasciare_applicazioni_con_XULRunner_1.8" title="it/XULRunner/Rilasciare_applicazioni_con_XULRunner_1.8">Rilasciare applicazioni con XULRunner 1.8</a></dt> <dd><small>Spiega come utilizzare XULRunner 1.8 per sviluppare e rilasciare applicazioni XUL standalone in ambiente di produzione.</small></dd> </dl> <dl> <dt><a href="/it/Applicazioni_basate_su_XULRunner" title="it/Applicazioni_basate_su_XULRunner">Applicazioni basate su XULRunner</a></dt> <dd><small>Tutte le applicazioni disponibili basate su XULRunner.</small></dd> </dl> </td> <td> <h4 id="Argomenti_correlati">Argomenti correlati</h4> <ul> <li><a href="/it/XUL" title="it/XUL">XUL</a></li> <li><a href="/it/XPCOM" title="it/XPCOM">XPCOM</a></li> </ul> </td> </tr> </tbody> -</table> -<p> </p> -<p>{{ languages( { "ca": "ca/XULRunner", "en": "en/XULRunner", "es": "es/XULRunner", "fr": "fr/XULRunner", "zh-cn": "cn/XULRunner", "ja": "ja/XULRunner", "pl": "pl/XULRunner" } ) }}</p> diff --git a/files/it/archive/mozilla/xulrunner/note_di_rilascio_di_xulrunner_1.8.0.4/index.html b/files/it/archive/mozilla/xulrunner/note_di_rilascio_di_xulrunner_1.8.0.4/index.html deleted file mode 100644 index f2557a0040..0000000000 --- a/files/it/archive/mozilla/xulrunner/note_di_rilascio_di_xulrunner_1.8.0.4/index.html +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Note di rilascio di XULRunner 1.8.0.4 -slug: Archive/Mozilla/XULRunner/Note_di_rilascio_di_XULRunner_1.8.0.4 -translation_of: Archive/Mozilla/XULRunner/1.8.0.4 ---- -<p>XULRunner 1.8.0.4 è una <i>versione di anteprima stabile</i> del framework Mozilla <a href="it/XULRunner">XULRunner</a>. Essa rimpiazza la versione 1.8.0.1; tutti gli utenti dovrebbero aggiornarla. La nuova versione fornisce gli strumenti per lanciare applicazioni XUL standalone ed incorporare le API che possono essere utilizzate per visualizzare le pagine web in applicazioni nativa o in applicazioni Java. -</p> -<h3 id="Requisiti_di_sistema" name="Requisiti_di_sistema"> Requisiti di sistema </h3> -<p>Prima dell'installazione, assicurarsi che il computer risponda ai <a class="external" href="http://www.mozilla.com/firefox/system-requirements.html">requisiti di sistema</a>. I requisiti minimi sono identici a quelli di Firefox. -</p> -<h3 id="Installare_XULRunner" name="Installare_XULRunner"> Installare XULRunner </h3> -<p>Mozilla fornisce XULRunner per Windows, Mac OS X e Linux, al momento solo in inglese: -</p> -<ul><li> <a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.0.4/win32/en-US/xulrunner-1.8.0.4.en-US.win32.zip">Scarica XULRunner per Windows</a> -</li><li> <a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.0.4/mac/en-US/xulrunner-1.8.0.4.en-US.mac.dmg">Scarica XULRunner per Mac OS X</a> -</li><li> <a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.0.4/linux-i686/en-US/xulrunner-1.8.0.4.en-US.linux-i686.tar.gz">Scarica XULRunner per Linux</a> -</li></ul> -<h4 id="Windows" name="Windows"> Windows </h4> -<ul><li> Decomprimere il file ZIP in una nuova directory utilizzando un programma di compressione (Mozilla consiglia <a class="external" href="http://www.7zip.org/">7zip</a>). Si consiglia di utilizzare la seguente directory: <tt>C:\Program Files\Mozilla XULRunner\1.8.0.4</tt> -</li><li> Per registrare XULRunner nel sistema, aprire il prompt dei comandi ed eseguire il comando <tt>xulrunner.exe --register-global</tt> (per registrarlo per tutti gli utenti), oppure il comando <tt>xulrunner.exe --register-user</tt> (per registrarlo solo per l'utente corrente) -</li></ul> -<h4 id="Mac_OS_X" name="Mac_OS_X"> Mac OS X </h4> -<ul><li> Aprire il file .pkg e seguire le istruzioni del programma di installazione -</li></ul> -<h4 id="Linux" name="Linux"> Linux </h4> -<ul><li> Decomprimere il tarball in nuova nuova directory con il comando <tt>tar -xzf xulrunner-1.8.0.4.en-US.linux-i686.tar.gz</tt>. Si consiglia la seguente directory: <tt>/opt/xulrunner/1.8.0.4</tt> -</li><li> Registrare XULRunner nel sistema con il comando <tt>xulrunner --register-global</tt> (per instrallarlo per tutti gli utenti, ma occorrono i privilegi di root), oppure <tt>xulrunner --register-user</tt> (per installarlo solo per l'utente corrente) -</li></ul> -<p><br> -</p> -<h3 id="Disinstallare_XULRunner" name="Disinstallare_XULRunner"> Disinstallare XULRunner </h3> -<h4 id="Windows.2FLinux" name="Windows.2FLinux"> Windows/Linux </h4> -<ul><li> Dal prompt di MS-DOS o dalla shell di Linux, eseguire <tt>xulrunner --unregister-global</tt> oppure <tt>xulrunner --unregister-user</tt> (a seconda di quale comando si è utilizzato per installarlo) -</li><li> Rimuovere la directory di XULRunner -</li></ul> -<h4 id="Mac_OS_X_2" name="Mac_OS_X_2"> Mac OS X </h4> -<p>Se si hanno più versioni di XULRunner installate sul sistema, non è possibile disinstallarne soltanto una. -</p> -<ul><li> Per rimuovere <b>tutte</b> le versioni di XULRunner installate, rimuovere la directory <tt>/Library/Frameworks/XUL.framework</tt> -</li></ul> -<h3 id="Installare_applicazioni_XUL" name="Installare_applicazioni_XUL"> Installare applicazioni XUL </h3> -<p>Le applicazioni XUL si possono ottenere da diverse fonti e sono tipicamente compresse in un archizio ZIP con l'estensione <tt>.xulapp</tt> o <tt>.xpi</tt>. -</p> -<ul><li> Salvare l'archivio sul desktop o in qualche altra directory comoda -</li></ul> -<h4 id="Windows_2" name="Windows_2"> Windows </h4> -<p>Eseguire il seguente comando da Avvio -> Esegui o dal prompt dei comandi: -"C:\Program Files\Mozilla XULRunner\1.8.0.4\xulrunner\xulrunner.exe" --install-app "C:\Documents and Settings\<var>UTENTE</var>\Desktop\<var>NOME_APPLICAZIONE</var>.xpi" -</p><p>L'applicazione verrà installata in <tt>C:\Program Files\<var>NOME_VENDITORE</var>\<var>NOME_APPLICAZIONE</var></tt> -</p> -<h4 id="Mac_OS_X_3" name="Mac_OS_X_3"> Mac OS X </h4> -<p>Eseguire il seguente comando dal Terminale: -</p> -<pre class="eval">/Library/Frameworks/XUL.framework/xulrunner-bin --install-app ~/Desktop/<var>NOME_APPLICAZIONE</var>.xpi -</pre> -<p>L'applicazione verrà installata in <tt>/Applications/<var>NOME_VENDITORE</var>/<var>NOME_APPLICAZIONE</var></tt> -</p> -<h4 id="Linux_2" name="Linux_2"> Linux </h4> -<p>Eseguire il seguente comando dalla shell: -</p> -<pre class="eval">/opt/xulrunner/1.8.0.4/xulrunner/xulrunner --install-app ~/Desktop/<var>NOME_APPLICAZIONE</var>.xpi -</pre> -<p>L'applicazione verrà installata in <tt>/usr/lib/<var>NOME_VENDITORE</var>/<var>NOME_APPLICAZIONE</var></tt> -</p> -<h3 id="Problemi_conosciuti" name="Problemi_conosciuti"> Problemi conosciuti </h3> -<ul><li> I firewall potrebbero identificare tutte le applicazioni XUL come un'unica applicazione -</li><li> Su Microsoft Windows XP, tutte le applicazioni XUL potrebbero essere raggruppate insieme nella barra delle applicazioni -</li></ul> -<h3 id="Frequently_Asked_Questions" name="Frequently_Asked_Questions"> Frequently Asked Questions </h3> -<p></p><dl> -<dt>Perchè installare XULRunner è così complicato? Perchè non c'è un facile programma di installazione? -</dt><dd>Perchè nessuno lo ha ancora creato! Questa versione è un'anteprima per sviluppatori: ulteriori funzionalità per l'installazione e il rilascio di XULRunner e delle applicazioni basate su di esso saranno disponibili in versioni future. -<p></p></dd><dt>Sto scrivendo un'applicazione XUL, come posso rilasciarla? -</dt><dd>Per ora Mozilla consiglia che XULRunner venga rilasciato privatamente insieme ad ogni applicazione. Si veda <a href="it/XULRunner/Rilasciare_applicazioni_con_XULRunner_1.8">Rilasciare applicazioni con XULRunner 1.8</a> per ulteriori informazioni. -<p></p></dd><dt>Dove sono i sorgenti? -</dt><dd><a class="external" href="http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.0.4/source/xulrunner-1.8.0.4-source.tar.bz2">Qui.</a> -<p></p></dd><dt>Credo di aver trovato un bug, come posso segnalarlo? -</dt><dd><a class="link-https" href="https://bugzilla.mozilla.org/">bugzilla.mozilla.org</a> viene utilizzato per tenere traccia dei bug di tutti i prodotti Mozilla. Per favore, prima di segnalare un nuovo bug controlla se è già stato segnalato da qualcun altro. -<p></p></dd><dt>Come posso aiutarvi? -</dt><dd>Se vuoi aiutare gli sviluppatori di XULRunner ma non sai da dove iniziare, visita la pagina della <a href="it/XULRunner/Community">XULRunner:Community</a> e poni domande sui newsgroup o sul canale IRC. -<p></p></dd></dl> -{{ languages( { "en": "en/XULRunner_1.8.0.4_Release_Notes", "fr": "fr/Notes_de_versions_de_XULRunner_1.8.0.4", "ja": "ja/XULRunner_1.8.0.4_Release_Notes" } ) }} diff --git a/files/it/archive/mozilla/xulrunner/xulrunner_faq/index.html b/files/it/archive/mozilla/xulrunner/xulrunner_faq/index.html deleted file mode 100644 index 6602428faa..0000000000 --- a/files/it/archive/mozilla/xulrunner/xulrunner_faq/index.html +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: XULRunner FAQ -slug: Archive/Mozilla/XULRunner/XULRunner_FAQ -tags: - - XULRunner -translation_of: Archive/Mozilla/XULRunner/FAQ ---- -<p> -</p><p>Questa pagina ha lo scopo di rispondere alle domande più frequenti e correggere gli errori più comuni riguardo a <a href="it/XULRunner">XULRunner</a>. -</p><p></p><dl> -<dt>XULRunner è un browser? -</dt><dd>No. Si può utilizzare XULRunner per creare un browser (come <a href="http://benjamin.smedbergs.us/xulrunner/" class="external">mybrowser example</a> o Firefox), ma non esiste "il browser XULRunner". -<p></p></dd><dt>XULRunner è uno strumento di sviluppo? -</dt><dd>Non esattamente; XULRunner è una tecnologia internet runtime. Può essere utilizzato per creare strumenti di sviluppo (l'<a href="http://www.alphaworks.ibm.com/tech/ajaxtk" class="external">AJAX Toolkit Framework</a>, per esempio). In futuro ci sarà un XULRunner Developer Kit che conterrà vari strumenti di sviluppo. -<p></p></dd><dt>XULRunner assomiglia a linguaggi di programmazione come Java o .NET (o Python o...)? -</dt><dd>L'obiettivo di XULRunner è facilitare lo sviluppo e il rilascio di applicazioni internet. Non è concepito per essere un ambiente runtime completo; per questo XULRunner richiede poca memoria e una più semplice strategia di rilascio rispetto a un runtime completo. -<p></p></dd><dt>Se utilizzo XULRunner devo scrivere le mie applicazioni in XUL? -</dt><dd>No! Puoi scrivere le tue applicazioni in un qualunque linguaggio supportato dalla piattaforma web Mozilla, compresi HTML, XHTML, SVG, o XUL. -<p></p></dd><dt>Ma allora perchè si chiama XULRunner, invece di HTMLRunner o qualche altro nome simile? -</dt><dd>Il nome non è definitivo. E' possibile proporre nomi alternativi a Benjamin Smedberg. -<p></p></dd><dt>Quando Firefox si baserà su XULRunner? -</dt><dd>Si veda la <a href="http://wiki.mozilla.org/XULRunner:Roadmap" class="external">XULRunner roadmap</a>. Attualmente è previsto per Firefox 3 (XULRunner 1.9), verso la fine del 2007. -<p></p></dd></dl> -{{ languages( { "en": "en/XULRunner_FAQ", "fr": "fr/FAQ_de_XULRunner", "ja": "ja/XULRunner_FAQ" } ) }} |