From a065e04d529da1d847b5062a12c46d916408bf32 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 8 Dec 2020 21:46:22 -0500 Subject: update based on https://github.com/mdn/yari/issues/2028 --- files/pt-pt/_wikihistory.json | 5229 -------------------- .../index.html | 130 - .../add-ons/extensoes_bootstrapped/index.html | 352 -- files/pt-pt/archive/add-ons/index.html | 11 - .../index.html | 375 -- .../index.html | 286 -- .../apps/ferramentas_e_frameworks/index.html | 45 - files/pt-pt/archive/apps/index.html | 14 - .../pt-pt/archive/b2g_os/api/camera_api/index.html | 38 - .../b2g_os/api/camera_api/introducao/index.html | 178 - files/pt-pt/archive/b2g_os/api/index.html | 156 - .../building_apps_for_firefox_os/index.html | 361 -- .../manifesto/index.html | 926 ---- .../archive/b2g_os/firefox_os_apps/index.html | 140 - .../localiza\303\247\303\243o/index.html" | 101 - .../index.html" | 690 --- files/pt-pt/archive/b2g_os/index.html | 241 - .../archive/b2g_os/phone_guide/flame/index.html | 305 -- files/pt-pt/archive/b2g_os/phone_guide/index.html | 53 - files/pt-pt/archive/b2g_os/simulator/index.html | 118 - .../index.html" | 283 -- files/pt-pt/archive/css3/index.html | 1090 ---- files/pt-pt/archive/devtools_api_social/index.html | 213 - files/pt-pt/archive/firefox_os/index.html | 11 - files/pt-pt/archive/index.html | 25 - files/pt-pt/archive/mdn/index.html | 20 - .../conteudo_mdn_em_webplatform.org/index.html | 19 - .../archive/meta_docs/escrever_conteudo/index.html | 58 - files/pt-pt/archive/meta_docs/index.html | 12 - files/pt-pt/archive/meta_docs/trello/index.html | 101 - .../pt-pt/archive/mozilla/drag_and_drop/index.html | 142 - files/pt-pt/archive/mozilla/index.html | 10 - .../pt-pt/archive/mozilla/uris_and_urls/index.html | 122 - files/pt-pt/archive/mozilla/xbl/index.html | 36 - .../archive/mozilla/xul/comunidade/index.html | 6 - files/pt-pt/archive/mozilla/xul/image/index.html | 154 - files/pt-pt/archive/mozilla/xul/index.html | 83 - .../archive/mozilla/xul/namespaces/index.html | 153 - .../archive/mozilla/xul/outros_recursos/index.html | 6 - files/pt-pt/archive/mozilla/xul/scale/index.html | 235 - .../adicionar_etiquetas_e_imagens/index.html | 102 - .../tutorial/ficheiros_de_propriedade/index.html | 115 - .../pt-pt/archive/mozilla/xul/tutorial/index.html | 142 - .../modificar_o_tema_predefinido/index.html | 70 - .../mozilla/xul/tutorial/xbl_bindings/index.html | 215 - files/pt-pt/archive/normas_web/index.html | 151 - .../o_detetor_plugin_hang_detector/index.html | 46 - .../como_o_rss_trabalha/index.html" | 18 - .../archive/rss/como_come\303\247ar/index.html" | 57 - .../o_que_\303\251_rss/index.html" | 242 - .../porque_usar_rss/index.html" | 22 - .../rss/como_come\303\247ar/sindicar/index.html" | 99 - files/pt-pt/archive/rss/index.html | 47 - .../archive/rss/vers\303\243o/0.90/index.html" | 79 - "files/pt-pt/archive/rss/vers\303\243o/index.html" | 107 - files/pt-pt/archive/themes/index.html | 11 - .../index.html | 123 - files/pt-pt/chrome.manifest/index.html | 107 - .../creating_a_skin_for_seamonkey_2.x/index.html | 19 - files/pt-pt/criando_um_patch/index.html | 33 - .../contents.rdf/index.html | 46 - .../iniciando/index.html | 83 - .../install.rdf/index.html | 49 - .../uuid/index.html | 13 - .../pt-pt/empacotando_extens\303\265es/index.html" | 29 - files/pt-pt/empacotando_temas/index.html | 100 - files/pt-pt/eventos_arrastar_e_soltar/index.html | 33 - files/pt-pt/extras_xml/index.html | 116 - files/pt-pt/gecko/index.html | 106 - .../gecko_dom_reference/introduction/index.html | 319 -- files/pt-pt/gecko_sdk/index.html | 18 - files/pt-pt/install.rdf/index.html | 255 - .../melhorias_das_css_no_firefox_3/index.html | 42 - files/pt-pt/mozilla/add-ons/amo/index.html | 9 - .../add-ons/amo/policy/em_destaque/index.html | 85 - files/pt-pt/mozilla/add-ons/amo/policy/index.html | 19 - .../add-ons/amo/policy/revis\303\265es/index.html" | 160 - .../index.html" | 518 -- .../pt-pt/mozilla/add-ons/distribuicao/index.html | 78 - .../linhas_diretrizes_para_extras/index.html | 8 - files/pt-pt/mozilla/add-ons/sdk/index.html | 97 - .../add-ons/themes/conceitos_tema/index.html | 230 - files/pt-pt/mozilla/add-ons/themes/index.html | 49 - .../creating_a_skin_for_firefox/index.html | 33 - .../mozilla/add-ons/themes/obsolete/index.html | 10 - files/pt-pt/mozilla/add-ons/thunderbird/index.html | 135 - .../mozilla/calendar/calendar_versions/index.html | 1037 ---- files/pt-pt/mozilla/calendar/index.html | 80 - .../criacao_barra_lateral_firefox/index.html | 40 - .../index.html" | 95 - .../edi\303\247\303\243o_programador/index.html" | 36 - .../mozilla/firefox/multiple_profiles/index.html | 244 - .../cross_process_object_wrappers/index.html | 157 - .../depuracao_de_frame_scripts/index.html | 56 - .../gestor_de_mensagens/index.html | 74 - .../multiprocess_firefox/glossario/index.html | 36 - .../firefox/multiprocess_firefox/index.html | 79 - .../limitacoes_de_chrome_scripts/index.html | 215 - .../limitacoes_de_frame_scripts/index.html | 103 - .../quais_os_uris_que_carregam_e_onde/index.html | 62 - .../resumo_t\303\251cnico/index.html" | 164 - files/pt-pt/mozilla/firefox_for_android/index.html | 77 - .../index.html | 97 - .../index.html | 77 - files/pt-pt/mozilla/ligar/index.html | 117 - .../index.html" | 282 -- .../configuracao_inicial/index.html" | 81 - .../fase_da_traducao/index.html" | 120 - .../fase_de_lancamento/index.html" | 177 - .../fase_pr/index.html" | 212 - .../index.html" | 41 - files/pt-pt/mozilla/localization/index.html | 23 - files/pt-pt/mozilla/localization/index/index.html | 9 - .../localization/localizacao_e_plurais/index.html | 384 -- .../localizar_com_mercurial/index.html | 256 - .../index.html" | 138 - files/pt-pt/mozilla/mercurial/basicos/index.html | 61 - files/pt-pt/mozilla/mercurial/index.html | 41 - .../mercurial/instaacao_mercurial/index.html | 151 - .../pt-pt/mozilla/o0coes_linha_comandos/index.html | 486 -- .../performance/about_colon_memory/index.html | 187 - .../index.html | 53 - files/pt-pt/mozilla/performance/index.html | 145 - .../perfilar_com_o_profiler_integrado/index.html | 356 -- files/pt-pt/mozilla/persona/index.html | 153 - files/pt-pt/mozilla/phishing/index.html | 50 - files/pt-pt/mozilla/projects/emscripten/index.html | 42 - files/pt-pt/mozilla/projects/index.html | 14 - files/pt-pt/mozilla/projects/mailnews/index.html | 42 - files/pt-pt/mozilla/projects/rhino/index.html | 24 - .../thunderbird/localizacao_thunderbird/index.html | 100 - files/pt-pt/mozilla/tech/index.html | 14 - files/pt-pt/mozilla/tech/places/index.html | 75 - .../mozilla/tech/xpcom/armazenamento/index.html | 372 -- .../index.html" | 222 - files/pt-pt/mozilla/tech/xpcom/guide/index.html | 21 - files/pt-pt/mozilla/tech/xpcom/index.html | 52 - .../tech/xpcom/reference/glue_classes/index.html | 13 - .../pt-pt/mozilla/tech/xpcom/reference/index.html | 27 - .../tech/xul/attribute/textbox.type/index.html | 5 - .../autoconfiguration/fileformat/como/index.html | 243 - .../fileformat/definicao/index.html | 6 - .../autoconfiguration/fileformat/index.html | 10 - .../configuracao_autom\303\241tica/index.html" | 162 - files/pt-pt/mozilla/thunderbird/index.html | 69 - .../mozilla/thunderbird/lancamentos/index.html | 19 - .../index.html | 397 -- .../index.html" | 552 --- .../pt-pt/new_compatibility_tables_beta/index.html | 24 - files/pt-pt/ns_addref/index.html | 21 - files/pt-pt/ns_error/index.html | 15 - files/pt-pt/ns_if_addref/index.html | 21 - files/pt-pt/ns_if_release/index.html | 27 - files/pt-pt/ns_postcondition/index.html | 20 - files/pt-pt/ns_precondition/index.html | 20 - files/pt-pt/ns_release/index.html | 21 - files/pt-pt/ns_warning/index.html | 15 - files/pt-pt/nsiidleservice/index.html | 68 - files/pt-pt/plugins/index.html | 63 - files/pt-pt/rdf/index.html | 63 - files/pt-pt/social_api/index.html | 97 - .../configura\303\247\303\265es/index.html" | 59 - files/pt-pt/tools/scratchpad/index.html | 126 - files/pt-pt/tools/webide/index.html | 41 - files/pt-pt/web/css/azimuth/index.html | 72 - .../css/como_come\303\247ar/dados_xml/index.html" | 239 - .../interfaces_de_usu\303\241rio_xul/index.html" | 336 -- .../javascript/novidades_no_javascript/index.html | 80 - .../novidades_no_javascript_1.8/index.html | 136 - files/pt-pt/xpcom_interface_reference/index.html | 17 - files/pt-pt/xul/attribute/index.html | 5 - files/pt-pt/xul/attribute/textbox.type/index.html | 21 - files/pt-pt/zonas/index.html | 53 - 173 files changed, 27366 deletions(-) delete mode 100644 files/pt-pt/_wikihistory.json delete mode 100644 files/pt-pt/archive/add-ons/communication_between_html_and_your_extension/index.html delete mode 100644 files/pt-pt/archive/add-ons/extensoes_bootstrapped/index.html delete mode 100644 files/pt-pt/archive/add-ons/index.html delete mode 100644 files/pt-pt/archive/add-ons/interaction_between_privileged_and_non-privileged_pages/index.html delete mode 100644 files/pt-pt/archive/add-ons/trabalhar_com_multiprocessos_firefox/index.html delete mode 100644 files/pt-pt/archive/apps/ferramentas_e_frameworks/index.html delete mode 100644 files/pt-pt/archive/apps/index.html delete mode 100644 files/pt-pt/archive/b2g_os/api/camera_api/index.html delete mode 100644 files/pt-pt/archive/b2g_os/api/camera_api/introducao/index.html delete mode 100644 files/pt-pt/archive/b2g_os/api/index.html delete mode 100644 files/pt-pt/archive/b2g_os/firefox_os_apps/building_apps_for_firefox_os/index.html delete mode 100644 files/pt-pt/archive/b2g_os/firefox_os_apps/building_apps_for_firefox_os/manifesto/index.html delete mode 100644 files/pt-pt/archive/b2g_os/firefox_os_apps/index.html delete mode 100644 "files/pt-pt/archive/b2g_os/firefox_os_apps/localiza\303\247\303\243o/index.html" delete mode 100644 "files/pt-pt/archive/b2g_os/firefox_os_apps/permissoes_de_aplica\303\247\303\243o/index.html" delete mode 100644 files/pt-pt/archive/b2g_os/index.html delete mode 100644 files/pt-pt/archive/b2g_os/phone_guide/flame/index.html delete mode 100644 files/pt-pt/archive/b2g_os/phone_guide/index.html delete mode 100644 files/pt-pt/archive/b2g_os/simulator/index.html delete mode 100644 "files/pt-pt/archive/b2g_os/utilizar_o_gestor_de_aplicac\303\265es/index.html" delete mode 100644 files/pt-pt/archive/css3/index.html delete mode 100644 files/pt-pt/archive/devtools_api_social/index.html delete mode 100644 files/pt-pt/archive/firefox_os/index.html delete mode 100644 files/pt-pt/archive/index.html delete mode 100644 files/pt-pt/archive/mdn/index.html delete mode 100644 files/pt-pt/archive/meta_docs/conteudo_mdn_em_webplatform.org/index.html delete mode 100644 files/pt-pt/archive/meta_docs/escrever_conteudo/index.html delete mode 100644 files/pt-pt/archive/meta_docs/index.html delete mode 100644 files/pt-pt/archive/meta_docs/trello/index.html delete mode 100644 files/pt-pt/archive/mozilla/drag_and_drop/index.html delete mode 100644 files/pt-pt/archive/mozilla/index.html delete mode 100644 files/pt-pt/archive/mozilla/uris_and_urls/index.html delete mode 100644 files/pt-pt/archive/mozilla/xbl/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/comunidade/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/image/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/namespaces/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/outros_recursos/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/scale/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/tutorial/adicionar_etiquetas_e_imagens/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/tutorial/ficheiros_de_propriedade/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/tutorial/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/tutorial/modificar_o_tema_predefinido/index.html delete mode 100644 files/pt-pt/archive/mozilla/xul/tutorial/xbl_bindings/index.html delete mode 100644 files/pt-pt/archive/normas_web/index.html delete mode 100644 files/pt-pt/archive/plugins/out_of_process_plugins/o_detetor_plugin_hang_detector/index.html delete mode 100644 "files/pt-pt/archive/rss/como_come\303\247ar/como_o_rss_trabalha/index.html" delete mode 100644 "files/pt-pt/archive/rss/como_come\303\247ar/index.html" delete mode 100644 "files/pt-pt/archive/rss/como_come\303\247ar/o_que_\303\251_rss/index.html" delete mode 100644 "files/pt-pt/archive/rss/como_come\303\247ar/porque_usar_rss/index.html" delete mode 100644 "files/pt-pt/archive/rss/como_come\303\247ar/sindicar/index.html" delete mode 100644 files/pt-pt/archive/rss/index.html delete mode 100644 "files/pt-pt/archive/rss/vers\303\243o/0.90/index.html" delete mode 100644 "files/pt-pt/archive/rss/vers\303\243o/index.html" delete mode 100644 files/pt-pt/archive/themes/index.html delete mode 100644 files/pt-pt/archive/utilizar_normas_web_nas_suas_paginas_da_web/index.html delete mode 100644 files/pt-pt/chrome.manifest/index.html delete mode 100644 files/pt-pt/creating_a_skin_for_seamonkey_2.x/index.html delete mode 100644 files/pt-pt/criando_um_patch/index.html delete mode 100644 files/pt-pt/criando_um_visual_para_o_firefox/contents.rdf/index.html delete mode 100644 files/pt-pt/criando_um_visual_para_o_firefox/iniciando/index.html delete mode 100644 files/pt-pt/criando_um_visual_para_o_firefox/install.rdf/index.html delete mode 100644 files/pt-pt/criando_um_visual_para_o_firefox/uuid/index.html delete mode 100644 "files/pt-pt/empacotando_extens\303\265es/index.html" delete mode 100644 files/pt-pt/empacotando_temas/index.html delete mode 100644 files/pt-pt/eventos_arrastar_e_soltar/index.html delete mode 100644 files/pt-pt/extras_xml/index.html delete mode 100644 files/pt-pt/gecko/index.html delete mode 100644 files/pt-pt/gecko_dom_reference/introduction/index.html delete mode 100644 files/pt-pt/gecko_sdk/index.html delete mode 100644 files/pt-pt/install.rdf/index.html delete mode 100644 files/pt-pt/melhorias_das_css_no_firefox_3/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/amo/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/amo/policy/em_destaque/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/amo/policy/index.html delete mode 100644 "files/pt-pt/mozilla/add-ons/amo/policy/revis\303\265es/index.html" delete mode 100644 "files/pt-pt/mozilla/add-ons/cri\303\247\303\243o_de_extens\303\265es_firefox_com_sistema_mozilla/index.html" delete mode 100644 files/pt-pt/mozilla/add-ons/distribuicao/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/linhas_diretrizes_para_extras/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/sdk/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/themes/conceitos_tema/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/themes/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/themes/obsolete/creating_a_skin_for_firefox/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/themes/obsolete/index.html delete mode 100644 files/pt-pt/mozilla/add-ons/thunderbird/index.html delete mode 100644 files/pt-pt/mozilla/calendar/calendar_versions/index.html delete mode 100644 files/pt-pt/mozilla/calendar/index.html delete mode 100644 files/pt-pt/mozilla/criacao_barra_lateral_firefox/index.html delete mode 100644 "files/pt-pt/mozilla/cria\303\247\303\243o_de_um_complemento_de_dicion\303\241rio_de_verifica\303\247\303\243o_ortogr\303\241fica/index.html" delete mode 100644 "files/pt-pt/mozilla/firefox/edi\303\247\303\243o_programador/index.html" delete mode 100644 files/pt-pt/mozilla/firefox/multiple_profiles/index.html delete mode 100644 files/pt-pt/mozilla/firefox/multiprocess_firefox/cross_process_object_wrappers/index.html delete mode 100644 files/pt-pt/mozilla/firefox/multiprocess_firefox/depuracao_de_frame_scripts/index.html delete mode 100644 files/pt-pt/mozilla/firefox/multiprocess_firefox/gestor_de_mensagens/index.html delete mode 100644 files/pt-pt/mozilla/firefox/multiprocess_firefox/glossario/index.html delete mode 100644 files/pt-pt/mozilla/firefox/multiprocess_firefox/index.html delete mode 100644 files/pt-pt/mozilla/firefox/multiprocess_firefox/limitacoes_de_chrome_scripts/index.html delete mode 100644 files/pt-pt/mozilla/firefox/multiprocess_firefox/limitacoes_de_frame_scripts/index.html delete mode 100644 files/pt-pt/mozilla/firefox/multiprocess_firefox/quais_os_uris_que_carregam_e_onde/index.html delete mode 100644 "files/pt-pt/mozilla/firefox/multiprocess_firefox/resumo_t\303\251cnico/index.html" delete mode 100644 files/pt-pt/mozilla/firefox_for_android/index.html delete mode 100644 files/pt-pt/mozilla/how_to_get_a_stacktrace_for_a_bug_report/index.html delete mode 100644 files/pt-pt/mozilla/implementacao_do_pontoon_num_projeto_da_mozilla/index.html delete mode 100644 files/pt-pt/mozilla/ligar/index.html delete mode 100644 "files/pt-pt/mozilla/localization/aplica\303\247\303\243o_tradu\303\247\303\243o_com_mercurial/index.html" delete mode 100644 "files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/configuracao_inicial/index.html" delete mode 100644 "files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_da_traducao/index.html" delete mode 100644 "files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_de_lancamento/index.html" delete mode 100644 "files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_pr/index.html" delete mode 100644 "files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/index.html" delete mode 100644 files/pt-pt/mozilla/localization/index.html delete mode 100644 files/pt-pt/mozilla/localization/index/index.html delete mode 100644 files/pt-pt/mozilla/localization/localizacao_e_plurais/index.html delete mode 100644 files/pt-pt/mozilla/localization/localizar_com_mercurial/index.html delete mode 100644 "files/pt-pt/mozilla/localization/localiza\303\247\303\243o_com_pontoon/index.html" delete mode 100644 files/pt-pt/mozilla/mercurial/basicos/index.html delete mode 100644 files/pt-pt/mozilla/mercurial/index.html delete mode 100644 files/pt-pt/mozilla/mercurial/instaacao_mercurial/index.html delete mode 100644 files/pt-pt/mozilla/o0coes_linha_comandos/index.html delete mode 100644 files/pt-pt/mozilla/performance/about_colon_memory/index.html delete mode 100644 files/pt-pt/mozilla/performance/comunicacao_de_um_problema_de_desempenho/index.html delete mode 100644 files/pt-pt/mozilla/performance/index.html delete mode 100644 files/pt-pt/mozilla/performance/perfilar_com_o_profiler_integrado/index.html delete mode 100644 files/pt-pt/mozilla/persona/index.html delete mode 100644 files/pt-pt/mozilla/phishing/index.html delete mode 100644 files/pt-pt/mozilla/projects/emscripten/index.html delete mode 100644 files/pt-pt/mozilla/projects/index.html delete mode 100644 files/pt-pt/mozilla/projects/mailnews/index.html delete mode 100644 files/pt-pt/mozilla/projects/rhino/index.html delete mode 100644 files/pt-pt/mozilla/projects/thunderbird/localizacao_thunderbird/index.html delete mode 100644 files/pt-pt/mozilla/tech/index.html delete mode 100644 files/pt-pt/mozilla/tech/places/index.html delete mode 100644 files/pt-pt/mozilla/tech/xpcom/armazenamento/index.html delete mode 100644 "files/pt-pt/mozilla/tech/xpcom/guide/altera\303\247\303\265es_xpcom_gecko_2.0/index.html" delete mode 100644 files/pt-pt/mozilla/tech/xpcom/guide/index.html delete mode 100644 files/pt-pt/mozilla/tech/xpcom/index.html delete mode 100644 files/pt-pt/mozilla/tech/xpcom/reference/glue_classes/index.html delete mode 100644 files/pt-pt/mozilla/tech/xpcom/reference/index.html delete mode 100644 files/pt-pt/mozilla/tech/xul/attribute/textbox.type/index.html delete mode 100644 files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/como/index.html delete mode 100644 files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/definicao/index.html delete mode 100644 files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/index.html delete mode 100644 "files/pt-pt/mozilla/thunderbird/configuracao_autom\303\241tica/index.html" delete mode 100644 files/pt-pt/mozilla/thunderbird/index.html delete mode 100644 files/pt-pt/mozilla/thunderbird/lancamentos/index.html delete mode 100644 files/pt-pt/mozilla/trabalhar_com_janelas_no_codigo_chrome/index.html delete mode 100644 "files/pt-pt/mozilla/utiliza\303\247\303\243o_cxx_no_c\303\263digo_da_mozilla/index.html" delete mode 100644 files/pt-pt/new_compatibility_tables_beta/index.html delete mode 100644 files/pt-pt/ns_addref/index.html delete mode 100644 files/pt-pt/ns_error/index.html delete mode 100644 files/pt-pt/ns_if_addref/index.html delete mode 100644 files/pt-pt/ns_if_release/index.html delete mode 100644 files/pt-pt/ns_postcondition/index.html delete mode 100644 files/pt-pt/ns_precondition/index.html delete mode 100644 files/pt-pt/ns_release/index.html delete mode 100644 files/pt-pt/ns_warning/index.html delete mode 100644 files/pt-pt/nsiidleservice/index.html delete mode 100644 files/pt-pt/plugins/index.html delete mode 100644 files/pt-pt/rdf/index.html delete mode 100644 files/pt-pt/social_api/index.html delete mode 100644 "files/pt-pt/tools/debugger/configura\303\247\303\265es/index.html" delete mode 100644 files/pt-pt/tools/scratchpad/index.html delete mode 100644 files/pt-pt/tools/webide/index.html delete mode 100644 files/pt-pt/web/css/azimuth/index.html delete mode 100644 "files/pt-pt/web/css/como_come\303\247ar/dados_xml/index.html" delete mode 100644 "files/pt-pt/web/css/como_come\303\247ar/interfaces_de_usu\303\241rio_xul/index.html" delete mode 100644 files/pt-pt/web/javascript/novidades_no_javascript/index.html delete mode 100644 files/pt-pt/web/javascript/novidades_no_javascript/novidades_no_javascript_1.8/index.html delete mode 100644 files/pt-pt/xpcom_interface_reference/index.html delete mode 100644 files/pt-pt/xul/attribute/index.html delete mode 100644 files/pt-pt/xul/attribute/textbox.type/index.html delete mode 100644 files/pt-pt/zonas/index.html (limited to 'files/pt-pt') diff --git a/files/pt-pt/_wikihistory.json b/files/pt-pt/_wikihistory.json deleted file mode 100644 index 00fda8305e..0000000000 --- a/files/pt-pt/_wikihistory.json +++ /dev/null @@ -1,5229 +0,0 @@ -{ - "Acentuação_para_conteúdos_carregados_por_AJAX": { - "modified": "2019-03-23T23:50:32.509Z", - "contributors": [ - "Leandro Mercês Xavier", - "JulioGreff", - "Micox", - "Douglas", - "Pfsergio1968" - ] - }, - "Atualizando_extensões_para_o_Firefox_3": { - "modified": "2019-12-13T20:33:32.517Z", - "contributors": [ - "wbamberg", - "fscholz", - "SphinxKnight", - "Anonymous", - "teoli", - "Sheppy", - "Leandro Mercês Xavier", - "Verruckt" - ] - }, - "Atualizando_extensões_para_o_Firefox_3.5": { - "modified": "2019-03-24T00:00:34.452Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Componentes": { - "modified": "2019-03-23T23:40:02.292Z", - "contributors": [ - "SphinxKnight", - "GrandeBuzina" - ] - }, - "Configurando_um_servidor_de_atualização": { - "modified": "2019-01-16T14:51:09.548Z", - "contributors": [ - "Leandro Mercês Xavier" - ] - }, - "Construir_uma_Extensão": { - "modified": "2019-03-24T00:04:05.919Z", - "contributors": [ - "teoli", - "fscholz", - "Rhuanbarros", - "Rsjuliao", - "Horyuu1", - "Leandro Mercês Xavier", - "Dudaott", - "Ecocam", - "Toyux", - "Verruckt", - "Luis Henrique Sousa", - "Mr.leal", - "Joker pt", - "Brunnolou", - "Bermonruf" - ] - }, - "Controles_XUL": { - "modified": "2019-03-24T00:03:56.894Z", - "contributors": [ - "fscholz", - "Luis Henrique Sousa", - "Verruckt" - ] - }, - "Criando_plugins_OpenSearch_para_o_Firefox": { - "modified": "2019-03-24T00:00:54.849Z", - "contributors": [ - "tregagnon", - "Verruckt", - "Rodrigoknascimento" - ] - }, - "Criando_um_visual_para_o_Firefox": { - "modified": "2019-03-23T23:51:38.630Z", - "contributors": [ - "SphinxKnight", - "Milona87", - "Thestrongergod", - "Verruckt", - "Camaleaun" - ] - }, - "Criar_uma_pele_para_o_Firefox": { - "modified": "2019-01-16T16:12:28.704Z", - "contributors": [ - "MarceloGhelman", - "Leandro Mercês Xavier", - "Amrlima" - ] - }, - "DHTML": { - "modified": "2019-01-16T16:23:46.538Z", - "contributors": [ - "SphinxKnight", - "RuiMaciel" - ] - }, - "DOM/DOM_Reference": { - "modified": "2019-03-23T23:25:55.220Z", - "contributors": [ - "Anonymous", - "Brettz9" - ] - }, - "DOM/Selection": { - "modified": "2019-03-24T00:02:03.808Z", - "contributors": [ - "SphinxKnight", - "danielwebsistemas" - ] - }, - "DOM/Storage": { - "modified": "2019-03-24T00:00:51.877Z", - "contributors": [ - "khalid32", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "DOM/document.alinkColor": { - "modified": "2019-03-24T00:04:44.971Z", - "contributors": [ - "teoli", - "italo" - ] - }, - "DOM/document.bgColor": { - "modified": "2019-03-24T00:04:41.203Z", - "contributors": [ - "teoli", - "italo" - ] - }, - "DOM/document.cookie": { - "modified": "2019-03-19T14:20:57.798Z", - "contributors": [ - "lucasrenod", - "SphinxKnight", - "gadelhas", - "teoli", - "italo" - ] - }, - "DOM/document.getElementsByClassName": { - "modified": "2019-12-02T03:58:42.536Z", - "contributors": [ - "jestevespereira", - "khalid32", - "teoli", - "Leandro Mercês Xavier", - "Verruckt" - ] - }, - "DOM/element": { - "modified": "2020-10-15T21:16:02.585Z", - "contributors": [ - "Anonymous", - "MauroBonucci", - "khalid32", - "Leandro Mercês Xavier", - "Davis.peixoto", - "Codigo13" - ] - }, - "DOM/element.appendChild": { - "modified": "2019-03-23T23:43:33.351Z", - "contributors": [ - "khalid32", - "teoli", - "Leandro Mercês Xavier", - "Wingedx" - ] - }, - "DOM/element.clientLeft": { - "modified": "2019-03-23T23:49:26.792Z", - "contributors": [ - "khalid32", - "teoli", - "Leandro Mercês Xavier", - "Verruckt" - ] - }, - "DOM/element.clientTop": { - "modified": "2019-03-23T23:49:30.994Z", - "contributors": [ - "AshfaqHossain", - "teoli", - "Leandro Mercês Xavier", - "Verruckt" - ] - }, - "DOM/element.cloneNode": { - "modified": "2019-09-30T14:07:35.240Z", - "contributors": [ - "semisse", - "SphinxKnight", - "guerreirogabriel", - "Diogok", - "Glauco.basilio", - "Codigo13", - "Leandro Mercês Xavier" - ] - }, - "DOM/element.insertBefore": { - "modified": "2019-03-23T23:46:00.401Z", - "contributors": [ - "jsx", - "Codigo13" - ] - }, - "DOM_Inspector": { - "modified": "2020-07-16T22:36:24.733Z", - "contributors": [ - "wbamberg", - "SphinxKnight", - "Anonymous", - "teoli", - "Verruckt" - ] - }, - "DOM_Inspector/Introduction_to_DOM_Inspector": { - "modified": "2020-07-16T22:36:26.057Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Desenhando_texto_usando_canvas": { - "modified": "2019-03-23T23:59:25.399Z", - "contributors": [ - "Wladimir_Palant", - "maicon", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "FAQ_Extensões": { - "modified": "2019-01-16T14:39:04.547Z", - "contributors": [ - "fscholz", - "Luis Henrique Sousa", - "Toyux", - "Verruckt", - "Calebeaires" - ] - }, - "Firefox_1.5_para_Desenvolvedores": { - "modified": "2019-03-24T00:02:26.260Z", - "contributors": [ - "wbamberg", - "SphinxKnight", - "fscholz", - "Takenbot", - "Leandro Mercês Xavier" - ] - }, - "Firefox_2_para_desenvolvedores": { - "modified": "2019-03-24T00:02:35.537Z", - "contributors": [ - "wbamberg", - "SphinxKnight", - "fscholz", - "Leandro Mercês Xavier", - "Kayalemao" - ] - }, - "Firefox_3.5_para_desenvolvedores": { - "modified": "2019-03-24T00:00:50.782Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Firefox_3.6_para_desenvolvedores": { - "modified": "2019-12-13T20:33:40.975Z", - "contributors": [ - "wbamberg", - "SphinxKnight", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Firefox_3_para_desenvolvedores": { - "modified": "2019-01-16T14:32:08.166Z", - "contributors": [ - "teoli", - "fscholz", - "Verruckt", - "Fernandopsilveira", - "Leandro Mercês Xavier" - ] - }, - "Firefox_4_para_desenvolvedores": { - "modified": "2019-11-21T00:43:18.363Z", - "contributors": [ - "wbamberg", - "Sebastianz", - "Prinz_Rana", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Firefox_5_para_desenvolvedores": { - "modified": "2019-03-24T00:09:30.352Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Firefox_6_para_desenvolvedores": { - "modified": "2019-11-21T00:43:07.958Z", - "contributors": [ - "wbamberg", - "Anonymous", - "teoli", - "Verruckt" - ] - }, - "Games/Tutorials/2D_breakout_game_Phaser": { - "modified": "2019-03-18T21:30:42.706Z", - "contributors": [ - "wbamberg", - "chrisdavidmills" - ] - }, - "Glossary/API": { - "modified": "2019-03-23T22:32:07.433Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário": { - "modified": "2020-10-07T11:13:28.151Z", - "contributors": [ - "peterbe", - "joaonunomota", - "SphinxKnight", - "Anonymous", - "wbamberg" - ] - }, - "Glossário/404": { - "modified": "2020-06-25T18:13:41.660Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/502": { - "modified": "2020-06-25T18:28:46.890Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/AJAX": { - "modified": "2020-06-09T08:11:59.760Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/API": { - "modified": "2020-10-25T11:15:06.759Z", - "contributors": [ - "Zamalor", - "joaonunomota", - "Anonymous" - ] - }, - "Glossário/ARIA": { - "modified": "2020-06-11T20:31:33.120Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Acessibilidade": { - "modified": "2019-03-18T21:47:01.702Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Argumento": { - "modified": "2019-03-18T21:17:57.812Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Assinatura": { - "modified": "2019-03-23T22:12:54.952Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/BigInt": { - "modified": "2020-06-12T14:16:25.328Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/CIA": { - "modified": "2020-06-11T20:33:04.482Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/CRLF": { - "modified": "2020-06-12T13:10:14.562Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/CRUD": { - "modified": "2020-06-11T20:38:17.457Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Cabeçalho_de_entidade": { - "modified": "2020-07-25T18:10:04.388Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Cache": { - "modified": "2020-06-07T12:38:40.205Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Compilar": { - "modified": "2019-03-23T22:01:24.745Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Compressao_GZip": { - "modified": "2019-03-18T21:46:58.480Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/DOM": { - "modified": "2019-10-08T09:31:32.173Z", - "contributors": [ - "Anonymous", - "GoToLoop" - ] - }, - "Glossário/ECMA": { - "modified": "2019-03-23T22:30:19.413Z", - "contributors": [ - "GoToLoop" - ] - }, - "Glossário/Eixo_principal": { - "modified": "2019-04-08T06:57:09.138Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Glossário/Eixo_transversal": { - "modified": "2019-04-08T06:58:12.600Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Glossário/Elemento": { - "modified": "2019-03-18T21:18:07.800Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Etiqueta": { - "modified": "2019-03-23T22:01:42.150Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Extensoes_da_Web": { - "modified": "2019-03-18T21:37:24.767Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Favicon": { - "modified": "2020-04-30T05:49:13.226Z", - "contributors": [ - "adilsonmandlate" - ] - }, - "Glossário/Flexbox": { - "modified": "2019-04-08T06:38:43.855Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Glossário/GCS": { - "modified": "2020-06-13T09:32:48.386Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Git": { - "modified": "2020-06-13T09:39:03.707Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/HTML": { - "modified": "2019-03-23T22:13:01.389Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Hipertexto": { - "modified": "2019-03-23T22:01:40.877Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/IANA": { - "modified": "2020-06-07T13:01:45.679Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/ISP": { - "modified": "2020-07-16T14:02:41.646Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Idempotent": { - "modified": "2019-07-11T10:59:59.365Z", - "contributors": [ - "FilipePintoReis" - ] - }, - "Glossário/IndexedDB": { - "modified": "2019-03-23T22:30:22.618Z", - "contributors": [ - "GoToLoop" - ] - }, - "Glossário/Lazy_load": { - "modified": "2020-06-09T04:59:38.616Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Metadados": { - "modified": "2019-03-18T21:46:57.702Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/MitM": { - "modified": "2019-03-18T21:29:48.838Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Modo_de_operação_de_cifra_de_bloco": { - "modified": "2020-07-19T20:41:55.171Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Motor": { - "modified": "2019-03-23T22:24:10.538Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Navegador": { - "modified": "2019-03-23T22:01:42.054Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Node.js": { - "modified": "2019-03-23T22:30:21.428Z", - "contributors": [ - "Anonymous", - "GoToLoop" - ] - }, - "Glossário/OOP": { - "modified": "2019-03-18T21:47:01.837Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/OTA": { - "modified": "2019-03-23T22:30:21.528Z", - "contributors": [ - "GoToLoop" - ] - }, - "Glossário/Objeto": { - "modified": "2019-03-18T21:46:57.221Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Polyfill": { - "modified": "2019-03-23T22:04:04.730Z", - "contributors": [ - "pedrodfcosta" - ] - }, - "Glossário/Prototype-based_programming": { - "modified": "2019-03-18T21:47:01.974Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Referencia_de_objeto": { - "modified": "2019-03-18T21:18:01.122Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Servidor": { - "modified": "2019-03-23T22:30:25.987Z", - "contributors": [ - "GoToLoop" - ] - }, - "Glossário/UTF-8": { - "modified": "2019-03-18T20:40:41.143Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Valor": { - "modified": "2019-03-18T21:18:07.651Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Viewport": { - "modified": "2020-06-10T11:59:40.452Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/Viewport_Visual": { - "modified": "2020-06-10T13:52:57.763Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/WHATWG": { - "modified": "2020-06-12T08:44:24.569Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/WebRTC": { - "modified": "2020-06-07T12:24:38.989Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/WebVTT": { - "modified": "2020-06-12T12:26:29.739Z", - "contributors": [ - "joaonunomota" - ] - }, - "Glossário/World_Wide_Web": { - "modified": "2019-03-18T21:46:52.018Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/Wrapper": { - "modified": "2019-03-18T21:17:53.688Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/XML": { - "modified": "2019-03-23T22:01:48.146Z", - "contributors": [ - "Anonymous" - ] - }, - "Glossário/booliano": { - "modified": "2019-03-18T21:45:55.769Z", - "contributors": [ - "Anonymous" - ] - }, - "Guia_do_desenvolvedor": { - "modified": "2019-03-24T00:00:34.143Z", - "contributors": [ - "SphinxKnight", - "teoli", - "Leandro Mercês Xavier" - ] - }, - "HTMLToDelete/Element/figure": { - "modified": "2019-03-24T00:07:13.574Z", - "contributors": [ - "wbamberg", - "jwhitlock", - "teoli", - "f.sanxz" - ] - }, - "JavaScript_Shells": { - "modified": "2019-03-23T23:49:32.077Z", - "contributors": [ - "SphinxKnight", - "Verruckt" - ] - }, - "Java_em_Extensões_do_Firefox": { - "modified": "2019-03-23T23:44:51.954Z", - "contributors": [ - "SphinxKnight", - "RuiMaciel" - ] - }, - "Javascript_orientado_a_objetos": { - "modified": "2019-03-24T00:11:38.222Z", - "contributors": [ - "flowck", - "Leandro Mercês Xavier" - ] - }, - "Jogos": { - "modified": "2019-09-09T15:34:18.541Z", - "contributors": [ - "SphinxKnight", - "Aschlla", - "wbamberg", - "rPetas", - "fscholz", - "Anonymous" - ] - }, - "Jogos/Tutoriais": { - "modified": "2019-03-18T21:30:51.808Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Learn": { - "modified": "2020-07-21T13:37:41.344Z", - "contributors": [ - "joaonunomota", - "VITOR77777", - "PRigter", - "SphinxKnight", - "svarlamov", - "Anonymous", - "DoviMaj", - "joao-neves95", - "albertocastro", - "mrmorais", - "Jeremie" - ] - }, - "Learn/Acessibilidade": { - "modified": "2020-07-21T16:29:40.277Z", - "contributors": [ - "joaonunomota", - "Anonymous" - ] - }, - "Learn/CSS": { - "modified": "2020-07-16T22:25:36.875Z", - "contributors": [ - "joaonunomota", - "Anonymous" - ] - }, - "Learn/CSS/Estilo_de_texto": { - "modified": "2020-07-16T22:26:00.007Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/CSS/Howto": { - "modified": "2020-07-16T22:25:44.063Z", - "contributors": [ - "Anonymous", - "chrisdavidmills" - ] - }, - "Learn/CSS/Howto/FAQ_de_CSS": { - "modified": "2020-07-16T22:25:45.869Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web": { - "modified": "2020-11-09T11:59:04.208Z", - "contributors": [ - "joaonunomota", - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web/A_web_e_os_padroes_da_web": { - "modified": "2020-08-15T18:38:33.155Z", - "contributors": [ - "joaonunomota", - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web/Apresentacao_do_meu_site": { - "modified": "2020-07-16T22:34:19.154Z", - "contributors": [ - "joaonunomota", - "diogo-panaca", - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web/CSS_basico": { - "modified": "2020-08-17T15:28:30.827Z", - "contributors": [ - "joaonunomota", - "diogo-panaca", - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web/Como_funciona_a_Web": { - "modified": "2020-07-21T16:44:13.094Z", - "contributors": [ - "joaonunomota", - "gabodin", - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web/Elementar_de_JavaScript": { - "modified": "2020-08-17T15:31:44.919Z", - "contributors": [ - "joaonunomota", - "diogo-panaca", - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web/HTML_basicos": { - "modified": "2020-08-15T18:37:16.181Z", - "contributors": [ - "joaonunomota", - "diogo-panaca", - "Anonymous", - "mrsilvino" - ] - }, - "Learn/Comecar_com_a_Web/Installing_basic_software": { - "modified": "2020-07-23T08:51:53.513Z", - "contributors": [ - "joaonunomota", - "diogo-panaca", - "Jacgrillon", - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web/Lidar_com_ficheiros": { - "modified": "2020-07-20T16:01:08.653Z", - "contributors": [ - "joaonunomota", - "diogo-panaca", - "Anonymous" - ] - }, - "Learn/Comecar_com_a_Web/Publicar_o_seu_site_da_Web": { - "modified": "2020-08-17T15:33:14.323Z", - "contributors": [ - "joaonunomota" - ] - }, - "Learn/Front-end_web_developer": { - "modified": "2020-11-11T23:07:52.540Z", - "contributors": [ - "nuruldecarvalho", - "VITOR77777" - ] - }, - "Learn/HTML": { - "modified": "2020-07-16T22:22:22.937Z", - "contributors": [ - "Anonymous", - "RicardoLovatel", - "chrisdavidmills" - ] - }, - "Learn/HTML/Como": { - "modified": "2020-07-16T22:22:30.740Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/HTML/Como/Adicionar_um_mapa_de_zona_clicavel_numa_imagem": { - "modified": "2020-07-16T22:22:43.567Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/HTML/Introducao_ao_HTML": { - "modified": "2020-07-16T22:22:52.576Z", - "contributors": [ - "diogo-panaca", - "joaomc", - "Anonymous" - ] - }, - "Learn/HTML/Introducao_ao_HTML/Criar_hiperligacoes": { - "modified": "2020-07-16T22:23:46.700Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Learn/HTML/Introducao_ao_HTML/Depurar_HTML": { - "modified": "2020-07-16T22:24:15.706Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Learn/HTML/Introducao_ao_HTML/Estrutura_documento_website": { - "modified": "2020-07-16T22:24:08.727Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Learn/HTML/Introducao_ao_HTML/Estruturar_pagina_de_conteudo": { - "modified": "2020-07-16T22:24:20.585Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Learn/HTML/Introducao_ao_HTML/Formatacao_avancada_texto": { - "modified": "2020-07-16T22:23:57.791Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Learn/HTML/Introducao_ao_HTML/Iniciacao_HTML": { - "modified": "2020-07-16T22:23:06.412Z", - "contributors": [ - "cmccarreiro", - "Anonymous" - ] - }, - "Learn/HTML/Introducao_ao_HTML/Os_metadados_de_head_em_HTML": { - "modified": "2020-07-16T22:23:23.598Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/HTML/Introducao_ao_HTML/demarcar_uma_carta": { - "modified": "2020-07-16T22:23:13.979Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Learn/HTML/Multimedia_and_embedding/Pagina_de_boas_vindas_da_Mozilla": { - "modified": "2020-07-16T22:25:08.049Z", - "contributors": [ - "diegobarcelar", - "Anonymous" - ] - }, - "Learn/HTML/Multimedia_e_integracao": { - "modified": "2020-07-16T22:24:28.825Z", - "contributors": [ - "Anonymous", - "chrisdavidmills" - ] - }, - "Learn/HTML/Multimedia_e_integracao/Conteudo_de_audio_e_vídeo": { - "modified": "2020-07-16T22:24:56.333Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/HTML/Tables": { - "modified": "2020-07-16T22:25:15.032Z", - "contributors": [ - "Anonymous", - "thetoni" - ] - }, - "Learn/HTML/Tables/Avaliacao_Estruturar_os_dados_dos_planetas": { - "modified": "2020-07-16T22:25:30.543Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/HTML/Tables/Avancada": { - "modified": "2020-07-16T22:25:27.234Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/HTML/Tables/Basicos": { - "modified": "2020-07-16T22:25:22.105Z", - "contributors": [ - "diogo-panaca", - "Anonymous" - ] - }, - "Learn/Index": { - "modified": "2020-07-16T22:33:40.763Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/JavaScript": { - "modified": "2020-07-16T22:29:43.788Z", - "contributors": [ - "Anonymous", - "Japroriple" - ] - }, - "Learn/JavaScript/Primeiros_passos": { - "modified": "2020-07-16T22:29:54.837Z", - "contributors": [ - "Anonymous", - "Elllenn" - ] - }, - "Learn/No-servidor": { - "modified": "2020-07-16T22:36:01.831Z", - "contributors": [ - "Anonymous", - "joao-neves95" - ] - }, - "Learn/No-servidor/Django": { - "modified": "2020-07-16T22:36:35.255Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/No-servidor/Express_Nodejs": { - "modified": "2020-07-16T22:37:54.969Z", - "contributors": [ - "Anonymous", - "joao-neves95" - ] - }, - "Learn/No-servidor/Express_Nodejs/Configurar_um_meio_de_desenvolvimento_Node": { - "modified": "2020-07-16T22:38:00.728Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/No-servidor/Express_Nodejs/Introduction": { - "modified": "2020-07-16T22:38:13.187Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/No-servidor/Servidor_node_sem_framework": { - "modified": "2020-07-16T22:36:06.037Z", - "contributors": [ - "Anonymous", - "joao-neves95" - ] - }, - "Learn/Questoes_comuns": { - "modified": "2020-07-16T22:35:26.594Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/Questoes_comuns/Como_funciona_a_Internet": { - "modified": "2020-07-16T22:35:37.920Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/Questoes_comuns/Congiurar_um_servidor_de_testes_local": { - "modified": "2020-07-16T22:35:53.519Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/Questoes_comuns/O_que_e_um_URL": { - "modified": "2020-07-16T22:35:30.214Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/Questoes_comuns/O_que_e_um_nome_de_dominio": { - "modified": "2020-07-16T22:35:44.710Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/Questoes_comuns/O_que_e_um_servidor_da_Web": { - "modified": "2020-07-16T22:35:31.962Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/Questoes_comuns/Qual_e_a_diferenca_entre_pagina_site_servidor_da_web_e_mecanismo_pesquisa": { - "modified": "2020-07-16T22:35:40.437Z", - "contributors": [ - "Anonymous" - ] - }, - "Learn/Tools_and_testing": { - "modified": "2020-07-16T22:38:57.196Z", - "contributors": [ - "Anonymous", - "Navin77" - ] - }, - "Learn/Tools_and_testing/Teste_cruzado_de_navegador": { - "modified": "2020-07-16T22:39:01.215Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Learn/Tools_and_testing/Teste_cruzado_de_navegador/Acessibilidade": { - "modified": "2020-09-24T09:24:04.432Z", - "contributors": [ - "Painatalman" - ] - }, - "Localizar_descrições_de_extensões": { - "modified": "2019-03-24T00:02:35.408Z", - "contributors": [ - "SphinxKnight", - "fscholz", - "Verruckt" - ] - }, - "Localização": { - "modified": "2019-03-24T00:03:56.319Z", - "contributors": [ - "Anonymous", - "fscholz", - "Verruckt", - "Kayalemao", - "Tagl" - ] - }, - "MDN": { - "modified": "2020-02-19T18:55:27.012Z", - "contributors": [ - "jswisher", - "SphinxKnight", - "Anonymous", - "wbamberg", - "Jeremie", - "davempso", - "Sheppy" - ] - }, - "MDN/Comunidade": { - "modified": "2019-09-11T08:01:31.979Z", - "contributors": [ - "SphinxKnight", - "Anonymous", - "wbamberg" - ] - }, - "MDN/Comunidade/Conversações": { - "modified": "2019-01-16T21:51:19.575Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "MDN/Comunidade/Doc_sprints": { - "modified": "2019-03-18T21:19:58.227Z", - "contributors": [ - "Anonymous" - ] - }, - "MDN/Comunidade/Funcoes": { - "modified": "2019-03-18T21:20:05.049Z", - "contributors": [ - "Anonymous" - ] - }, - "MDN/Comunidade/O_que_está_a_acontecer": { - "modified": "2019-03-23T22:42:12.854Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "MDN/Comunidade/Trabalhar_em_comunidade": { - "modified": "2020-02-19T19:07:51.992Z", - "contributors": [ - "jswisher", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Contribute": { - "modified": "2019-03-23T23:03:08.251Z", - "contributors": [ - "Anonymous", - "wbamberg", - "alispivak" - ] - }, - "MDN/Contribute/Feedback": { - "modified": "2020-09-30T17:52:26.093Z", - "contributors": [ - "chrisdavidmills", - "jswisher", - "SphinxKnight", - "Anonymous", - "wbamberg" - ] - }, - "MDN/Contribute/Getting_started": { - "modified": "2020-09-30T17:15:31.197Z", - "contributors": [ - "chrisdavidmills", - "joaonunomota", - "Anonymous", - "wbamberg", - "riagva", - "davempso" - ] - }, - "MDN/Contribute/Howto": { - "modified": "2019-01-16T21:51:27.704Z", - "contributors": [ - "wbamberg", - "Anonymous", - "jswisher" - ] - }, - "MDN/Contribute/Howto/Como_converter_exemplos_de_codigo_para_ficarem_live": { - "modified": "2020-03-02T17:27:21.266Z", - "contributors": [ - "carlostojal", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Contribute/Howto/Como_definir_o_resumo_para_uma_pagina": { - "modified": "2019-03-23T22:08:19.737Z", - "contributors": [ - "wbamberg", - "Saconte", - "Anonymous" - ] - }, - "MDN/Contribute/Howto/Como_efetuar_revisao_tecnica": { - "modified": "2019-05-13T07:55:49.326Z", - "contributors": [ - "Anonymous" - ] - }, - "MDN/Contribute/Howto/Como_escrever_um_artigo_para_ajudar_as_pessoas_a_aprenderem_sobre_a_Web": { - "modified": "2020-02-28T22:23:56.590Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "MDN/Contribute/Howto/Como_escrever_uma_nova_entrada_no_Glossario": { - "modified": "2019-03-23T22:12:45.769Z", - "contributors": [ - "wbamberg", - "maarysantos", - "Anonymous" - ] - }, - "MDN/Contribute/Howto/Comunicar_um_problema": { - "modified": "2020-01-07T12:19:34.416Z", - "contributors": [ - "peterbe", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Contribute/Howto/Criar_e_editar_paginas": { - "modified": "2019-04-04T11:57:15.432Z", - "contributors": [ - "diogo-panaca" - ] - }, - "MDN/Contribute/Howto/Criar_uma_conta_MDN": { - "modified": "2019-03-23T22:42:11.494Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "MDN/Contribute/Howto/Etiqueta": { - "modified": "2019-11-13T11:32:17.983Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "MDN/Contribute/Howto/Marcar_paginas_JavaScript": { - "modified": "2019-01-17T01:35:48.693Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "MDN/Contribute/Howto/Participar_testes_beta": { - "modified": "2019-03-23T22:09:29.860Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "MDN/Contribute/Howto/fazer_revisão_editorial": { - "modified": "2019-03-23T22:20:12.878Z", - "contributors": [ - "Anonymous", - "wbamberg", - "samlopes_br" - ] - }, - "MDN/Contribute/Localize": { - "modified": "2019-01-16T20:02:21.377Z", - "contributors": [ - "wbamberg", - "Anonymous", - "Sheppy" - ] - }, - "MDN/Contribute/Localize/Iniciar_uma_localizacao": { - "modified": "2019-03-23T22:09:26.952Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "MDN/Contribute/Localize/Projetos_localização": { - "modified": "2019-03-23T22:31:56.445Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "MDN/Contribute/Localize/Translating_pages": { - "modified": "2019-12-17T21:16:12.817Z", - "contributors": [ - "wbamberg", - "Anonymous", - "marquesgabriel", - "HelioCardoso", - "sUnTECH789" - ] - }, - "MDN/Editor": { - "modified": "2020-09-30T15:43:23.702Z", - "contributors": [ - "chrisdavidmills", - "Anonymous", - "wbamberg" - ] - }, - "MDN/Editor/Basicos": { - "modified": "2020-09-30T15:43:23.869Z", - "contributors": [ - "chrisdavidmills", - "Anonymous", - "wbamberg" - ] - }, - "MDN/Guidelines": { - "modified": "2020-09-30T15:31:28.524Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Guidelines/Convencoes_definicoes": { - "modified": "2020-09-30T15:31:29.524Z", - "contributors": [ - "chrisdavidmills", - "jswisher", - "Anonymous", - "wbamberg" - ] - }, - "MDN/Guidelines/Guia_de_estilo_de_escrita": { - "modified": "2020-09-30T15:31:29.280Z", - "contributors": [ - "chrisdavidmills", - "joaonunomota", - "jswisher", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Guidelines/Isto_pertence_a_MDN": { - "modified": "2020-09-30T15:31:29.806Z", - "contributors": [ - "chrisdavidmills", - "jswisher", - "Anonymous" - ] - }, - "MDN/Kuma": { - "modified": "2019-09-09T15:53:50.658Z", - "contributors": [ - "SphinxKnight", - "Anonymous", - "wbamberg" - ] - }, - "MDN/Sobre": { - "modified": "2019-09-10T08:55:19.644Z", - "contributors": [ - "SphinxKnight", - "Anonymous", - "wbamberg", - "Dilson", - "jswisher" - ] - }, - "MDN/Structures": { - "modified": "2020-09-30T12:57:09.511Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "jswisher" - ] - }, - "MDN/Structures/API_references": { - "modified": "2020-09-30T12:57:10.288Z", - "contributors": [ - "chrisdavidmills", - "wbamberg" - ] - }, - "MDN/Structures/API_references/Barras_laterais_de_referencia_da_API": { - "modified": "2020-09-30T12:57:10.465Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Structures/API_references/O_que_e_que_uma_referencia_de_API_precisa": { - "modified": "2020-09-30T12:57:10.634Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Structures/Exemplos_live": { - "modified": "2020-09-30T12:57:10.000Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Structures/Macros": { - "modified": "2020-09-30T12:57:10.153Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Tools": { - "modified": "2020-09-30T16:53:22.697Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "jswisher" - ] - }, - "MDN/Tools/Edição_de_modelo": { - "modified": "2020-09-30T16:53:23.123Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Tools/KumaScript": { - "modified": "2020-09-30T16:53:22.999Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Tools/Vigiar_pagina": { - "modified": "2020-09-30T16:53:22.646Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN/Troubleshooting": { - "modified": "2020-09-30T16:58:33.426Z", - "contributors": [ - "chrisdavidmills", - "wbamberg", - "Anonymous" - ] - }, - "MDN_at_ten": { - "modified": "2019-03-23T22:50:14.757Z", - "contributors": [ - "Anonymous", - "Matoplays" - ] - }, - "MDN_at_ten/Contribuir_para_MDN": { - "modified": "2020-02-19T18:51:00.800Z", - "contributors": [ - "jswisher", - "Anonymous" - ] - }, - "MDN_at_ten/Historia_da_MDN": { - "modified": "2019-03-23T22:09:33.028Z", - "contributors": [ - "Anonymous" - ] - }, - "Manipuladores_de_protocolo_web": { - "modified": "2019-03-23T23:52:53.802Z", - "contributors": [ - "Verruckt", - "Fernandopsilveira", - "Leandro Mercês Xavier" - ] - }, - "Melhorias_do_Gerenciador_de_Downloads_no_Firefox_3": { - "modified": "2019-01-16T14:39:25.788Z", - "contributors": [ - "fscholz", - "Verruckt" - ] - }, - "Mozilla": { - "modified": "2019-03-24T00:17:35.290Z", - "contributors": [ - "Anonymous", - "billhiba", - "Beria" - ] - }, - "Mozilla/Add-ons": { - "modified": "2019-03-18T21:08:20.167Z", - "contributors": [ - "Anonymous", - "nportugal", - "Anomitro_Munshi" - ] - }, - "Mozilla/Add-ons/WebExtensions": { - "modified": "2019-03-18T20:49:08.711Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Mozilla/Add-ons/WebExtensions/API": { - "modified": "2019-11-26T22:19:55.515Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/API/Armazenamento": { - "modified": "2020-10-15T21:59:48.396Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/API/browserAction": { - "modified": "2020-10-15T21:59:49.630Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/API/browsingData": { - "modified": "2020-10-15T22:14:48.933Z", - "contributors": [ - "ExE-Boss" - ] - }, - "Mozilla/Add-ons/WebExtensions/API/browsingData/removePluginData": { - "modified": "2020-10-15T22:14:40.836Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/API/devtools.panels": { - "modified": "2020-10-15T21:59:48.885Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/API/i18n": { - "modified": "2020-10-15T22:14:41.219Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/API/pageAction": { - "modified": "2020-10-15T21:59:47.365Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/API/sidebarAction": { - "modified": "2020-10-15T22:06:57.394Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/A_sua_primeira_extensao": { - "modified": "2019-03-18T21:04:11.435Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/A_sua_segunda_extensao": { - "modified": "2019-03-18T21:03:02.346Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Anatomia_de_uma_extensao": { - "modified": "2019-03-18T21:03:04.427Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/As_melhores_praticas_de_experiencia_do_utilizador": { - "modified": "2019-03-18T21:02:27.071Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Conversao_de_uma_extensao_legada_do_firefox": { - "modified": "2019-03-18T20:56:20.829Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/E_a_seguir": { - "modified": "2019-03-18T21:01:48.060Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Exemplos_extensoes": { - "modified": "2019-03-18T21:03:01.761Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/ExtennsoesWeb_e_a_id_do_extra": { - "modified": "2019-03-18T20:47:01.907Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Extensão_das_ferramentas_de_desenvolvimento": { - "modified": "2019-03-18T21:04:10.244Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Instalacao_temporaria_no_Firefox": { - "modified": "2019-03-18T21:03:04.634Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Interceptar_Pedidos_HTTP": { - "modified": "2019-03-18T21:03:59.316Z", - "contributors": [ - "carlosteixeiraa" - ] - }, - "Mozilla/Add-ons/WebExtensions/Internationalization": { - "modified": "2019-03-18T20:56:21.219Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/O_que_sao_WebExtensions": { - "modified": "2019-03-18T21:05:19.046Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Primeiros_passos_com_web-ext": { - "modified": "2019-03-18T21:03:10.522Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Publicar_a_sua_extensao": { - "modified": "2019-03-18T21:04:14.402Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Scripts_Conteudo": { - "modified": "2019-07-29T11:08:46.237Z", - "contributors": [ - "duduindo", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Suporte_navegador_APIs_JavaScript": { - "modified": "2020-10-15T20:55:03.457Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/Tips": { - "modified": "2019-03-18T21:01:44.598Z", - "contributors": [ - "SphinxKnight" - ] - }, - "Mozilla/Add-ons/WebExtensions/Trasnsferir_extensao_Google_Chrome": { - "modified": "2019-03-18T21:05:15.395Z", - "contributors": [ - "Anonymous", - "Nunonmac101" - ] - }, - "Mozilla/Add-ons/WebExtensions/dubla_padrões": { - "modified": "2020-10-15T22:25:44.918Z", - "contributors": [ - "martimafonso" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador": { - "modified": "2019-03-18T21:04:19.885Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Acoes_pagina": { - "modified": "2019-03-18T21:04:17.709Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Ação_navegador": { - "modified": "2019-03-18T21:04:05.718Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Barras_laterais": { - "modified": "2019-03-18T21:04:06.139Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Estilos_de_navegador": { - "modified": "2020-10-15T22:07:31.177Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Itens_do_menu_de_contexto": { - "modified": "2019-03-18T21:04:09.803Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Notificacoes": { - "modified": "2019-03-18T21:04:17.481Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Omnibox": { - "modified": "2019-03-18T21:01:59.411Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Options_pages": { - "modified": "2019-03-18T21:04:14.023Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Paginas_de_extensão": { - "modified": "2019-03-18T21:03:04.123Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/Popups": { - "modified": "2019-08-10T13:56:46.929Z", - "contributors": [ - "pedrosino", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/interface_do_utilizador/devtools_panels": { - "modified": "2019-03-18T21:04:02.641Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/manifest.json": { - "modified": "2020-10-15T21:59:48.039Z", - "contributors": [ - "Painatalman", - "wbamberg" - ] - }, - "Mozilla/Add-ons/WebExtensions/manifest.json/browser_action": { - "modified": "2020-10-15T21:59:47.236Z", - "contributors": [ - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings": { - "modified": "2020-10-15T22:07:31.462Z", - "contributors": [ - "wbamberg", - "ExE-Boss", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/manifest.json/devtools_page": { - "modified": "2020-10-15T21:59:47.989Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Mozilla/Add-ons/WebExtensions/manifest.json/icones": { - "modified": "2020-10-15T21:59:47.019Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Mozilla/Developer_guide/Source_Code": { - "modified": "2019-03-18T21:45:30.638Z", - "contributors": [ - "ntim" - ] - }, - "Mozilla/Firefox": { - "modified": "2019-09-10T15:01:27.677Z", - "contributors": [ - "SphinxKnight", - "Anonymous", - "wbamberg", - "albertocastro", - "Sheppy" - ] - }, - "Mozilla/Firefox/Releases": { - "modified": "2019-03-18T21:15:03.747Z", - "contributors": [ - "Anonymous", - "wbamberg", - "Sheppy" - ] - }, - "Mozilla/Firefox/Releases/3": { - "modified": "2019-03-23T23:19:50.195Z", - "contributors": [ - "wbamberg", - "ethertank" - ] - }, - "Mozilla/Firefox/Releases/70": { - "modified": "2019-10-01T09:44:22.188Z", - "contributors": [ - "Anonymous" - ] - }, - "Mudanças_no_Gecko_1.9_que_afetam_websites": { - "modified": "2019-03-23T23:47:04.199Z", - "contributors": [ - "wbamberg", - "Sheppy", - "Verruckt" - ] - }, - "O_DOM_e_o_JavaScript": { - "modified": "2019-12-13T21:10:33.944Z", - "contributors": [ - "wbamberg", - "fferracioli" - ] - }, - "Plugins/Ativacao_de_Flash:_comparacao_de_navegador": { - "modified": "2019-03-18T20:56:19.824Z", - "contributors": [ - "Anonymous" - ] - }, - "Plugins/Flash_para_HTML5": { - "modified": "2019-03-18T20:56:20.182Z", - "contributors": [ - "Anonymous" - ] - }, - "Referência_JSDBGAPI": { - "modified": "2019-03-23T23:44:44.830Z", - "contributors": [ - "SphinxKnight", - "RuiMaciel" - ] - }, - "Referência_do_DOM_Gecko/Prefácio": { - "modified": "2019-03-23T23:51:50.810Z", - "contributors": [ - "khalid32", - "Leandro Mercês Xavier", - "Davis.peixoto" - ] - }, - "Sobre_o_Document_Object_Model": { - "modified": "2019-03-23T23:46:25.664Z", - "contributors": [ - "SphinxKnight", - "Verruckt" - ] - }, - "Tinderbox": { - "modified": "2019-03-23T23:45:30.178Z", - "contributors": [ - "SphinxKnight", - "Verruckt" - ] - }, - "Toolkit_API": { - "modified": "2019-01-16T16:23:47.926Z", - "contributors": [ - "Tagl" - ] - }, - "Tools": { - "modified": "2020-07-16T22:44:17.493Z", - "contributors": [ - "SphinxKnight", - "Anonymous", - "wbamberg", - "robert882", - "Leite", - "caobarbosa", - "Timmi" - ] - }, - "Tools/Add-ons": { - "modified": "2020-07-16T22:36:23.718Z", - "contributors": [ - "wbamberg" - ] - }, - "Tools/Capturas_de_ecra": { - "modified": "2020-07-16T22:36:38.620Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Configurações": { - "modified": "2020-07-16T22:36:35.515Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Consola_da_Web": { - "modified": "2020-07-16T22:34:07.526Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Consola_da_Web/Abertura_Consola_Web": { - "modified": "2020-07-16T22:34:17.467Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Consola_da_Web/Ajuda": { - "modified": "2020-07-16T22:34:13.111Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Consola_da_Web/Atalhos_teclado": { - "modified": "2020-07-16T22:34:23.988Z", - "contributors": [ - "Anonymous" - ] - }, - "Tools/Consola_da_Web/Dividir_consola": { - "modified": "2020-07-16T22:34:21.158Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Consola_da_Web/Mensagens_consola": { - "modified": "2020-07-16T22:34:16.005Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Consola_da_Web/O_interprete_da_linha_de_comandos": { - "modified": "2020-07-16T22:34:19.541Z", - "contributors": [ - "Anonymous" - ] - }, - "Tools/Consola_da_Web/Rich_output": { - "modified": "2020-07-16T22:34:20.453Z", - "contributors": [ - "Anonymous" - ] - }, - "Tools/Debugger": { - "modified": "2020-07-16T22:35:06.168Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Debugger/Demonstracao_IU": { - "modified": "2020-07-16T22:35:16.876Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Debugger/How_to": { - "modified": "2020-07-16T22:35:08.333Z" - }, - "Tools/Debugger/How_to/Abrir_o_depurador": { - "modified": "2020-07-16T22:35:09.351Z", - "contributors": [ - "Anonymous" - ] - }, - "Tools/Debugger/How_to/Use_a_source_map": { - "modified": "2020-09-11T09:41:20.649Z", - "contributors": [ - "pedro-surf", - "Anonymous" - ] - }, - "Tools/Debugger/Source_map_errors": { - "modified": "2020-07-16T22:35:19.577Z", - "contributors": [ - "Anonymous" - ] - }, - "Tools/Desempenho": { - "modified": "2020-07-16T22:36:13.622Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Desempenho/Arvore_de_Chamada": { - "modified": "2020-07-16T22:36:20.006Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Desempenho/Cascata": { - "modified": "2020-07-16T22:36:18.250Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Desempenho/Como_fazer": { - "modified": "2020-07-16T22:36:21.955Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Desempenho/Frame_rate": { - "modified": "2020-07-16T22:36:19.201Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Editor_de_audio_da_Web": { - "modified": "2020-07-16T22:36:08.692Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Editor_de_estilo": { - "modified": "2020-07-16T22:35:01.029Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Inspetor_de_armazenamento": { - "modified": "2020-07-16T22:36:10.303Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Memoria": { - "modified": "2020-07-16T22:36:27.341Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Modo_de_Desenho_Adaptavel": { - "modified": "2020-07-16T22:35:22.282Z", - "contributors": [ - "Anonymous" - ] - }, - "Tools/Network_Monitor": { - "modified": "2020-07-16T22:35:31.240Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Page_Inspector": { - "modified": "2020-07-16T22:34:29.429Z", - "contributors": [ - "wbamberg", - "Anonymous", - "DevAsh" - ] - }, - "Tools/Page_Inspector/Guia_de_IU": { - "modified": "2020-07-16T22:34:49.596Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/How_to": { - "modified": "2020-07-16T22:34:31.978Z", - "contributors": [ - "wbamberg", - "Anonymous", - "sidgan" - ] - }, - "Tools/Page_Inspector/How_to/Abrir_o_inspetor": { - "modified": "2020-07-16T22:34:33.099Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/Page_Inspector/How_to/Examinar_e_editar_CSS": { - "modified": "2020-07-16T22:34:43.588Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/How_to/Examinar_e_editar_o_modelo_de_caixa": { - "modified": "2020-07-16T22:34:34.516Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/How_to/Inspecionar_e_selecionar_cores": { - "modified": "2020-07-16T22:34:35.181Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/How_to/Reposicao_de_elementos_na_pagina": { - "modified": "2020-07-16T22:34:46.213Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/How_to/Trabalhar_com_animacoes": { - "modified": "2020-07-16T22:34:37.073Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/How_to/Utilizar_a_API_do_Inspetor": { - "modified": "2020-07-16T22:34:45.056Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/How_to/Visualizar_tipos_de_letra": { - "modified": "2020-07-16T22:34:39.170Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/How_to/Visualize_transforms": { - "modified": "2020-07-16T22:34:39.722Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Page_Inspector/atalhos_de_teclado": { - "modified": "2020-07-16T22:34:52.351Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Performance/Guia_da_IU": { - "modified": "2020-07-16T22:36:15.326Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Remote_Debugging": { - "modified": "2020-07-16T22:35:37.988Z", - "contributors": [ - "Anonymous", - "wbamberg", - "Joao_Silva27" - ] - }, - "Tools/Remote_Debugging/Debugging_Firefox_Desktop": { - "modified": "2020-07-16T22:35:41.262Z", - "contributors": [ - "Anonymous" - ] - }, - "Tools/Remote_Debugging/Depuracao_remota_Thunderbird": { - "modified": "2020-07-16T22:35:40.059Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/Tools_Toolbox": { - "modified": "2020-07-16T22:35:28.091Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Tools/about:debugging": { - "modified": "2020-07-16T22:36:33.106Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Tools/atalhos_de_teclado": { - "modified": "2020-07-16T22:35:50.422Z", - "contributors": [ - "Anonymous", - "wbamberg" - ] - }, - "Transformar_XML_com_XSLT": { - "modified": "2019-03-23T23:45:21.155Z", - "contributors": [ - "SphinxKnight", - "Verruckt" - ] - }, - "Transformar_XML_com_XSLT/Para_leitura_adicional": { - "modified": "2019-03-23T23:52:21.068Z", - "contributors": [ - "SphinxKnight", - "Leandro Mercês Xavier", - "Pilinio", - "Verruckt" - ] - }, - "Tutorial_XUL": { - "modified": "2019-03-23T23:45:36.792Z", - "contributors": [ - "SphinxKnight", - "Leandro Mercês Xavier" - ] - }, - "Tutorial_XUL/Adicionando_botões": { - "modified": "2019-03-23T23:46:29.323Z", - "contributors": [ - "Verruckt", - "Leandro Mercês Xavier", - "Rodmalkav" - ] - }, - "Tutorial_XUL/Criando_uma_janela": { - "modified": "2019-03-23T23:45:36.338Z", - "contributors": [ - "SphinxKnight", - "jigs12", - "Leandro Mercês Xavier", - "Luis Henrique Sousa", - "Verruckt", - "Rodmalkav" - ] - }, - "Tutorial_XUL/Introdução": { - "modified": "2019-03-23T23:46:27.723Z", - "contributors": [ - "SphinxKnight", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Tutorial_do_Canvas": { - "modified": "2019-01-16T14:32:07.975Z", - "contributors": [ - "fscholz", - "Verruckt", - "RuiMaciel" - ] - }, - "Tutorial_do_Canvas/Formas_de_desenho": { - "modified": "2019-01-16T14:01:56.255Z", - "contributors": [ - "guerreirogabriel" - ] - }, - "Tutorial_do_Canvas/Utilização_básica": { - "modified": "2019-03-24T00:10:34.537Z", - "contributors": [ - "guerreirogabriel", - "Edgarlaguiar", - "Luiz Carlos Moraes", - "Jes", - "Vitor.blacks" - ] - }, - "Um_pequeno_exemplo_usando_AJAX": { - "modified": "2019-01-17T03:48:56.314Z", - "contributors": [ - "Leandro Mercês Xavier" - ] - }, - "Usando_privilégios_expandidos_em_navegadores_Mozilla": { - "modified": "2019-03-23T23:48:48.468Z", - "contributors": [ - "Leandro Mercês Xavier", - "Verruckt" - ] - }, - "Usando_áudio_e_vídeo_no_Firefox": { - "modified": "2019-03-24T00:00:33.796Z", - "contributors": [ - "Leandro Mercês Xavier", - "Verruckt" - ] - }, - "Using_the_W3C_DOM_Level_1_Core": { - "modified": "2019-12-13T21:06:18.400Z", - "contributors": [ - "wbamberg", - "Anonymous", - "ethertank", - "fferracioli" - ] - }, - "Utilizando_meta_tags": { - "modified": "2019-03-23T23:45:18.005Z", - "contributors": [ - "eduardoungaratto", - "AndreGazola", - "Fleury" - ] - }, - "Venkman": { - "modified": "2019-03-24T00:02:38.559Z", - "contributors": [ - "SphinxKnight", - "fscholz", - "Verruckt" - ] - }, - "Web": { - "modified": "2020-05-03T13:08:13.142Z", - "contributors": [ - "Anonymous", - "polonia", - "didi9999", - "joao-neves95", - "carlosrainhaaraujo", - "ethertank" - ] - }, - "Web/API": { - "modified": "2019-03-23T22:39:25.827Z", - "contributors": [ - "Anonymous", - "teoli", - "carlosrainhaaraujo" - ] - }, - "Web/API/API_Autenticacao_Web": { - "modified": "2020-10-15T22:03:06.934Z", - "contributors": [ - "fscholz", - "Anonymous" - ] - }, - "Web/API/API_Entradas_de_Diretoria_e_Ficheiro": { - "modified": "2019-03-18T21:46:51.385Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/API_WebRTC": { - "modified": "2019-03-23T22:12:46.226Z", - "contributors": [ - "Anonymous", - "Gurigraphics" - ] - }, - "Web/API/API_WebRTC/Tirar_fotografias": { - "modified": "2019-03-23T22:12:45.154Z", - "contributors": [ - "fscholz", - "wbamberg", - "Anonymous" - ] - }, - "Web/API/API_armazenamento": { - "modified": "2020-10-15T22:08:44.199Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/API_de_Armazenamento_da_Web": { - "modified": "2019-03-18T21:46:00.224Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/API_de_canvas": { - "modified": "2019-03-23T22:01:56.072Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/API_de_canvas/Tutorial": { - "modified": "2019-03-18T21:24:18.272Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/API_do_Estado_da_Bateria": { - "modified": "2019-03-18T21:29:01.750Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/API_transmissoes_multimedia": { - "modified": "2019-03-23T22:12:44.463Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Animation": { - "modified": "2020-10-15T22:09:54.586Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/AudioNode": { - "modified": "2019-03-23T22:12:47.243Z", - "contributors": [ - "trusktr" - ] - }, - "Web/API/Blob": { - "modified": "2020-10-15T22:32:41.617Z", - "contributors": [ - "Yayure" - ] - }, - "Web/API/Blob/Blob": { - "modified": "2020-11-16T10:19:01.877Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/Blob/size": { - "modified": "2020-10-15T22:32:50.862Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/Blob/type": { - "modified": "2020-10-15T22:33:10.637Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/Client": { - "modified": "2020-10-15T22:03:06.133Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/CloseEvent": { - "modified": "2020-10-15T22:32:54.165Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/CloseEvent/CloseEvent": { - "modified": "2020-10-15T22:32:51.831Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/DOMString": { - "modified": "2020-08-12T17:28:52.261Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/Document": { - "modified": "2019-07-02T18:26:33.145Z", - "contributors": [ - "Anonymous", - "chrisdavidmills" - ] - }, - "Web/API/Document.dir": { - "modified": "2019-03-23T23:22:09.179Z", - "contributors": [ - "khalid32", - "carlosrainhaaraujo" - ] - }, - "Web/API/Document/querySelector": { - "modified": "2020-10-15T22:32:00.428Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/Document/visibilitychange_event": { - "modified": "2019-04-08T07:39:14.855Z", - "contributors": [ - "irenesmith", - "Anonymous" - ] - }, - "Web/API/Eventos_de_Luz_Ambiente": { - "modified": "2020-10-15T22:07:41.555Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/File": { - "modified": "2020-10-15T22:32:24.351Z", - "contributors": [ - "Yayure" - ] - }, - "Web/API/File/File": { - "modified": "2020-10-15T22:33:11.221Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/fileName": { - "modified": "2020-08-08T18:37:05.171Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/fileSize": { - "modified": "2020-08-08T18:32:45.995Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/getAsBinary": { - "modified": "2020-08-11T04:16:46.870Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/getAsDataURL": { - "modified": "2020-08-08T18:57:17.906Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/getAsText": { - "modified": "2020-08-11T05:01:57.694Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/lastModified": { - "modified": "2020-10-17T08:26:52.375Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/lastModifiedDate": { - "modified": "2020-10-15T22:32:46.653Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/mozFullPath": { - "modified": "2020-08-08T18:43:12.882Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/name": { - "modified": "2020-10-15T22:32:23.452Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/type": { - "modified": "2020-10-15T22:32:40.925Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/File/webkitRelativePath": { - "modified": "2020-11-17T19:01:45.948Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/FileReader": { - "modified": "2019-03-18T21:16:40.698Z", - "contributors": [ - "Sheppy" - ] - }, - "Web/API/FileReader/abort": { - "modified": "2020-10-15T22:32:42.433Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/FileReader/error": { - "modified": "2020-10-15T22:32:24.839Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/FileReader/readAsArrayBuffer": { - "modified": "2020-10-15T22:33:15.086Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/FileReader/readAsBinaryString": { - "modified": "2020-10-15T21:37:25.343Z", - "contributors": [ - "joaonunomota", - "DouglasValdo" - ] - }, - "Web/API/FileReader/readAsDataURL": { - "modified": "2020-10-15T22:34:36.565Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/FileReader/readAsText": { - "modified": "2020-10-15T22:34:36.289Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/FileReader/readyState": { - "modified": "2020-11-15T12:35:45.700Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/FileReader/result": { - "modified": "2020-10-15T22:33:14.048Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/Geolocation": { - "modified": "2019-03-23T22:01:56.989Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Geolocation/Utilizacao_da_geolocalizacao": { - "modified": "2020-10-15T21:59:09.308Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/MathMLElement": { - "modified": "2020-10-15T22:33:03.137Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/MediaDevices": { - "modified": "2019-03-23T22:01:16.705Z", - "contributors": [ - "jpmedley" - ] - }, - "Web/API/MessageEvent": { - "modified": "2020-10-15T22:32:51.894Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/Metadados": { - "modified": "2019-03-18T21:46:51.094Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/NavigatorOnLine": { - "modified": "2019-03-23T22:01:59.308Z", - "contributors": [ - "chrisdavidmills" - ] - }, - "Web/API/NavigatorOnLine/Eventos_online_e_offline": { - "modified": "2019-03-23T23:49:32.329Z", - "contributors": [ - "SphinxKnight", - "chrisdavidmills", - "Leandro Mercês Xavier", - "Roli", - "Verruckt" - ] - }, - "Web/API/Node": { - "modified": "2019-03-23T23:22:11.442Z", - "contributors": [ - "khalid32", - "carlosrainhaaraujo" - ] - }, - "Web/API/Notifications_API": { - "modified": "2019-03-23T22:42:31.459Z", - "contributors": [ - "Sebastianz" - ] - }, - "Web/API/Notifications_API/Utilizar_API_Notificações": { - "modified": "2019-03-23T22:42:28.564Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Page_Visibility_API": { - "modified": "2019-03-18T21:42:30.274Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Push_API": { - "modified": "2019-03-18T21:38:04.203Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Service_Worker_API": { - "modified": "2019-10-08T09:27:10.284Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Service_Worker_API/Using_Service_Workers": { - "modified": "2019-10-08T09:25:19.208Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/SharedWorker": { - "modified": "2020-10-15T21:59:02.760Z", - "contributors": [ - "joaonunomota", - "Anonymous" - ] - }, - "Web/API/Sistema_de_ficheiros": { - "modified": "2020-10-15T21:46:44.138Z", - "contributors": [ - "joaonunomota", - "Anonymous" - ] - }, - "Web/API/URLSearchParams": { - "modified": "2019-10-16T11:18:10.261Z", - "contributors": [ - "NunoJSantos", - "goldyteam" - ] - }, - "Web/API/WebGLRenderingContext": { - "modified": "2020-10-15T21:59:21.576Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/WebGL_API": { - "modified": "2020-10-15T21:46:44.276Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/WebGL_API/Constantes": { - "modified": "2019-03-23T22:01:30.802Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/WebGL_API/Dados": { - "modified": "2019-03-23T22:01:33.105Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/WebGL_API/Tipos": { - "modified": "2019-03-23T22:01:33.867Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/WebGL_API/Utilizar_Extensões": { - "modified": "2019-03-23T22:01:32.555Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/WebSocket": { - "modified": "2020-10-15T22:32:53.586Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/WebSocket/WebSocket": { - "modified": "2020-10-15T22:33:03.555Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/WebSockets_API": { - "modified": "2020-10-15T22:32:45.764Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/WebSockets_API/Escrever_aplicação_cliente_de_WebSocket": { - "modified": "2020-08-11T17:49:59.287Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/WebSockets_API/Escrever_servidores_de_WebSocket": { - "modified": "2020-09-18T06:53:14.308Z", - "contributors": [ - "blunderous", - "joaonunomota" - ] - }, - "Web/API/WebSockets_API/Escrever_um_servidor_WebSocket_em_C": { - "modified": "2020-12-04T13:57:23.773Z", - "contributors": [ - "peterbe", - "joaonunomota" - ] - }, - "Web/API/WebSockets_API/Escrever_um_servidor_WebSocket_em_Java": { - "modified": "2020-08-24T20:03:27.920Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/API/Web_Audio_API": { - "modified": "2019-03-23T22:12:41.433Z", - "contributors": [ - "Anonymous", - "erikadoyle" - ] - }, - "Web/API/Web_Audio_API/Utilizar_api_audio_web": { - "modified": "2019-03-23T22:12:48.158Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Web_Workers_API": { - "modified": "2019-03-23T22:02:18.370Z", - "contributors": [ - "VsevolodGolovanov" - ] - }, - "Web/API/Web_Workers_API/Functions_and_classes_available_to_workers": { - "modified": "2019-03-23T22:02:20.388Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Web_Workers_API/Utilizacao_de_web_workers": { - "modified": "2019-03-23T22:02:15.177Z", - "contributors": [ - "allanfoppa", - "Anonymous" - ] - }, - "Web/API/Window": { - "modified": "2019-03-23T22:01:06.730Z", - "contributors": [ - "Anonymous", - "goeffthomas" - ] - }, - "Web/API/Window/barra_lateral": { - "modified": "2019-03-18T21:37:22.693Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Window/console": { - "modified": "2019-03-18T21:44:07.205Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Window/open": { - "modified": "2019-03-23T22:01:10.139Z", - "contributors": [ - "SphinxKnight", - "Anonymous" - ] - }, - "Web/API/Window/postMessage": { - "modified": "2019-06-04T14:57:56.992Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/Worker": { - "modified": "2019-03-23T22:02:29.683Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/API/XMLHttpRequest": { - "modified": "2020-10-15T21:59:27.066Z", - "contributors": [ - "fscholz", - "Anonymous" - ] - }, - "Web/API/notification": { - "modified": "2019-03-23T22:51:36.861Z", - "contributors": [ - "Anonymous", - "Japroriple" - ] - }, - "Web/Accessibility/ARIA/ARIA_Techniques": { - "modified": "2020-09-18T21:14:54.007Z", - "contributors": [ - "Wind1808" - ] - }, - "Web/Accessibility/ARIA/ARIA_Techniques/Usando_o_role_status": { - "modified": "2020-09-19T05:54:31.819Z", - "contributors": [ - "Painatalman" - ] - }, - "Web/Acessibilidade": { - "modified": "2019-09-09T14:20:12.758Z", - "contributors": [ - "SphinxKnight", - "Anonymous", - "teoli", - "Verruckt", - "Kayalemao", - "RuiMaciel", - "Karla pa", - "GrandeBuzina" - ] - }, - "Web/Acessibilidade/ARIA": { - "modified": "2019-03-18T21:47:01.413Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS": { - "modified": "2020-06-10T07:53:42.003Z", - "contributors": [ - "joaonunomota", - "SphinxKnight", - "Anonymous", - "Fernando-SilvaBR", - "albertocastro", - "teoli", - "Verruckt", - "Leandro Mercês Xavier", - "Takenbot", - "RuiMaciel" - ] - }, - "Web/CSS/:after": { - "modified": "2019-03-24T00:00:16.761Z", - "contributors": [ - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/:before": { - "modified": "2019-03-24T00:00:19.264Z", - "contributors": [ - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/@font-face": { - "modified": "2019-03-23T23:13:15.857Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/@import": { - "modified": "2019-03-23T23:47:07.977Z", - "contributors": [ - "Anonymous", - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/@media": { - "modified": "2020-04-25T11:58:21.640Z", - "contributors": [ - "myspeleo", - "diogo-panaca", - "Anonymous", - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/At-rule": { - "modified": "2019-03-23T22:24:56.828Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/CSS_Background_and_Borders": { - "modified": "2019-03-23T22:44:16.974Z", - "contributors": [ - "teoli" - ] - }, - "Web/CSS/CSS_Background_and_Borders/Múltiplos_planos_de_fundo": { - "modified": "2019-03-24T00:04:47.389Z", - "contributors": [ - "Anonymous", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/CSS_Box_Model": { - "modified": "2019-03-23T22:12:41.880Z", - "contributors": [ - "Sebastianz" - ] - }, - "Web/CSS/CSS_Box_Model/Introducao_modelo_caixa_CSS": { - "modified": "2019-03-23T22:12:42.813Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/CSS_Colors/Ferramenta_selecao_cor": { - "modified": "2019-04-28T14:53:13.655Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Web/CSS/CSS_Columns": { - "modified": "2019-03-18T21:38:41.627Z", - "contributors": [ - "mfluehr" - ] - }, - "Web/CSS/CSS_Flexible_Box_Layout": { - "modified": "2019-03-18T21:44:02.737Z", - "contributors": [ - "rachelandrew" - ] - }, - "Web/CSS/CSS_Flexible_Box_Layout/alinhamento_de_itens_num_recipiente_flex": { - "modified": "2019-06-11T07:33:08.010Z", - "contributors": [ - "BIGBenfica9", - "Anonymous" - ] - }, - "Web/CSS/CSS_Flexible_Box_Layout/casos_de_utilizacao_tipicos_do_flexbox": { - "modified": "2019-03-18T21:43:55.771Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/CSS_Flexible_Box_Layout/ordenacao_dos_itens_flex": { - "modified": "2019-07-22T03:58:30.968Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/CSS_Flexible_Box_Layout/relação_do_flexbox_com_outros_métodos_de_layout": { - "modified": "2019-03-18T21:43:58.441Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/CSS_Tipos": { - "modified": "2019-03-18T21:23:17.150Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/Como_começar": { - "modified": "2019-03-23T23:44:54.310Z", - "contributors": [ - "Anonymous", - "teoli", - "Leandro Mercês Xavier", - "Verruckt", - "Pilinio", - "Luisvulcanis" - ] - }, - "Web/CSS/Como_começar/CSS_legível": { - "modified": "2019-03-24T00:00:36.923Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Luis Henrique Sousa", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Caixas": { - "modified": "2019-03-24T00:00:34.956Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Cascata_e_herança": { - "modified": "2019-03-24T00:00:35.429Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Como_o_CSS_trabalha": { - "modified": "2019-03-24T00:00:37.691Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Conteúdo": { - "modified": "2020-07-16T22:25:48.413Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Cor": { - "modified": "2019-03-24T00:00:35.276Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Disposição": { - "modified": "2019-03-24T00:00:37.327Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Estilos_de_texto": { - "modified": "2019-03-24T00:00:39.580Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/Como_começar/Gráficos_SVG": { - "modified": "2019-03-24T00:00:34.584Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/JavaScript": { - "modified": "2019-03-24T00:00:40.211Z", - "contributors": [ - "fscholz", - "teoli", - "ethertank", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Listas": { - "modified": "2019-03-24T00:00:36.171Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Luis Henrique Sousa", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Mídia": { - "modified": "2019-03-24T00:15:51.724Z", - "contributors": [ - "Anonymous", - "fscholz", - "teoli", - "maggots", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/O_que_é_CSS": { - "modified": "2019-03-24T00:00:33.943Z", - "contributors": [ - "Sebastianz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier", - "Pilinio" - ] - }, - "Web/CSS/Como_começar/O_que_é_CSS?": { - "modified": "2019-03-23T23:43:00.605Z", - "contributors": [ - "teoli", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Porque_usar_CSS": { - "modified": "2019-03-24T00:00:39.116Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier", - "Pilinio" - ] - }, - "Web/CSS/Como_começar/Seletores": { - "modified": "2019-03-24T00:00:36.764Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Como_começar/Tabelas": { - "modified": "2019-03-24T00:00:35.865Z", - "contributors": [ - "fscholz", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Consulta_de_mídia": { - "modified": "2019-04-09T16:57:57.913Z", - "contributors": [ - "diogo-panaca", - "Anonymous", - "Sebastianz", - "mrstork", - "teoli", - "Verruckt", - "Leandro Mercês Xavier" - ] - }, - "Web/CSS/Consultas_de_media": { - "modified": "2020-10-15T22:17:12.623Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Web/CSS/Folhas_de_estilo_alternativas": { - "modified": "2019-03-23T23:53:49.046Z", - "contributors": [ - "teoli", - "FelipeMorais" - ] - }, - "Web/CSS/Média_paginada": { - "modified": "2019-03-23T22:24:57.103Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/Pseudoclasses": { - "modified": "2019-03-18T21:15:25.227Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/Pseudoelementos": { - "modified": "2019-03-18T21:23:11.174Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/Referência_CSS": { - "modified": "2020-07-20T13:36:56.218Z", - "contributors": [ - "joaonunomota", - "Anonymous", - "teoli", - "Moacir Bispo", - "Verruckt" - ] - }, - "Web/CSS/Replaced_element": { - "modified": "2019-03-23T22:32:04.311Z", - "contributors": [ - "andrekutianski", - "josketres" - ] - }, - "Web/CSS/Shorthand_properties": { - "modified": "2019-03-18T21:44:05.610Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/Usando_transformações_CSS": { - "modified": "2019-03-24T00:04:50.895Z", - "contributors": [ - "teoli", - "Verruckt", - "Leandro Mercês Xavier", - "Jürgen Jeka" - ] - }, - "Web/CSS/background": { - "modified": "2019-03-23T23:46:35.449Z", - "contributors": [ - "SphinxKnight", - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/background-attachment": { - "modified": "2019-03-23T23:12:53.495Z", - "contributors": [ - "SphinxKnight", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/background-color": { - "modified": "2019-03-23T22:16:20.029Z", - "contributors": [ - "SphinxKnight", - "teoli", - "Verruckt", - "ethertank" - ] - }, - "Web/CSS/background-image": { - "modified": "2019-03-23T23:47:07.090Z", - "contributors": [ - "SphinxKnight", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/background-position": { - "modified": "2019-03-23T23:47:05.241Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/background-repeat": { - "modified": "2019-03-18T21:15:14.751Z", - "contributors": [ - "SphinxKnight", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border": { - "modified": "2019-01-16T15:59:54.146Z", - "contributors": [ - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/border-bottom": { - "modified": "2019-03-23T23:47:10.248Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-bottom-color": { - "modified": "2019-03-23T23:47:06.644Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-bottom-style": { - "modified": "2019-03-23T23:47:07.572Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-bottom-width": { - "modified": "2019-03-23T23:47:10.824Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-collapse": { - "modified": "2019-03-23T23:47:06.488Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-color": { - "modified": "2019-03-24T00:02:05.127Z", - "contributors": [ - "wbamberg", - "teoli", - "gerson23", - "Verruckt" - ] - }, - "Web/CSS/border-left": { - "modified": "2019-01-16T15:59:39.346Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-left-color": { - "modified": "2019-01-16T19:20:48.785Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-left-style": { - "modified": "2019-01-16T15:59:50.769Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-left-width": { - "modified": "2019-01-16T16:00:08.928Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-right": { - "modified": "2019-01-16T15:59:50.709Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-right-color": { - "modified": "2019-01-16T15:59:44.072Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-right-style": { - "modified": "2019-01-16T15:59:50.407Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-right-width": { - "modified": "2019-01-16T16:00:01.042Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-spacing": { - "modified": "2019-03-23T23:47:07.851Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-top": { - "modified": "2019-01-17T10:27:59.370Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-top-color": { - "modified": "2019-01-16T19:20:46.774Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-top-style": { - "modified": "2019-01-16T15:59:52.923Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-top-width": { - "modified": "2019-01-16T16:00:01.372Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/border-width": { - "modified": "2019-03-23T23:12:52.902Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/bottom": { - "modified": "2019-01-16T16:00:22.463Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/clear": { - "modified": "2019-03-23T23:35:13.332Z", - "contributors": [ - "wbamberg", - "teoli", - "Luis Henrique Sousa", - "Verruckt" - ] - }, - "Web/CSS/color": { - "modified": "2019-01-16T19:20:48.419Z", - "contributors": [ - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/content": { - "modified": "2019-03-24T00:02:07.101Z", - "contributors": [ - "teoli", - "Half-blood" - ] - }, - "Web/CSS/counter-increment": { - "modified": "2019-03-23T23:47:04.420Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/counter-reset": { - "modified": "2019-03-23T23:47:10.117Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/cursor": { - "modified": "2019-03-24T00:02:03.227Z", - "contributors": [ - "wbamberg", - "teoli", - "Half-blood", - "Verruckt" - ] - }, - "Web/CSS/direction": { - "modified": "2019-01-16T16:56:47.948Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/CSS/display": { - "modified": "2019-03-23T23:49:28.516Z", - "contributors": [ - "wbamberg", - "Anonymous", - "teoli", - "ethertank", - "Leandro Mercês Xavier", - "Verruckt" - ] - }, - "Web/CSS/float": { - "modified": "2019-03-23T23:47:04.610Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/font": { - "modified": "2019-03-23T23:47:10.686Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/font-size": { - "modified": "2019-03-23T23:47:15.600Z", - "contributors": [ - "wbamberg", - "RCat", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/font-size-adjust": { - "modified": "2019-03-23T23:47:06.762Z", - "contributors": [ - "wbamberg", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/font-smooth": { - "modified": "2020-10-15T22:20:31.703Z", - "contributors": [ - "LPJFilho" - ] - }, - "Web/CSS/font-style": { - "modified": "2019-03-23T23:51:37.862Z", - "contributors": [ - "wbamberg", - "fscholz", - "teoli", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/font-weight": { - "modified": "2019-03-23T23:47:17.771Z", - "contributors": [ - "gusbemacbe", - "SphinxKnight", - "teoli", - "Verruckt" - ] - }, - "Web/CSS/grid-gap": { - "modified": "2020-10-15T22:00:32.351Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/height": { - "modified": "2019-03-23T23:47:57.733Z", - "contributors": [ - "wbamberg", - "teoli", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/inherit": { - "modified": "2019-01-16T15:39:13.615Z", - "contributors": [ - "teoli", - "Hillus" - ] - }, - "Web/CSS/layout_de_grelha_css": { - "modified": "2020-04-12T22:44:10.924Z", - "contributors": [ - "carlosaffrc", - "Anonymous" - ] - }, - "Web/CSS/list-style": { - "modified": "2019-03-23T23:47:53.661Z", - "contributors": [ - "SphinxKnight", - "teoli", - "Luis Henrique Sousa" - ] - }, - "Web/CSS/top": { - "modified": "2019-01-16T14:40:15.687Z", - "contributors": [ - "teoli", - "Half-blood" - ] - }, - "Web/CSS/transform": { - "modified": "2019-03-23T22:12:47.007Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/CSS/width": { - "modified": "2019-03-23T23:47:51.459Z", - "contributors": [ - "wbamberg", - "Redeagle48", - "teoli", - "Luis Henrique Sousa", - "Verruckt" - ] - }, - "Web/CSS/z-index": { - "modified": "2019-01-17T04:06:04.605Z", - "contributors": [ - "teoli", - "Verruckt", - "Luis Henrique Sousa" - ] - }, - "Web/Componentes_Web": { - "modified": "2019-08-20T17:28:31.563Z", - "contributors": [ - "filipe095", - "Anonymous" - ] - }, - "Web/Eventos": { - "modified": "2019-04-30T14:29:45.980Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Web/Guide": { - "modified": "2020-11-12T11:23:45.364Z", - "contributors": [ - "nuruldecarvalho", - "Anonymous", - "Onsteroids" - ] - }, - "Web/Guide/AJAX": { - "modified": "2019-03-23T23:43:06.644Z", - "contributors": [ - "Anonymous", - "chrisdavidmills", - "Leandro Mercês Xavier", - "Takenbot", - "Dria", - "RuiMaciel" - ] - }, - "Web/Guide/AJAX/Como_começar": { - "modified": "2019-03-23T23:58:34.669Z", - "contributors": [ - "Anonymous", - "chrisdavidmills", - "flaviomicheletti", - "Leandro Mercês Xavier", - "Fmtakaki", - "Verruckt", - "TroyDF", - "Japa al", - "Mederafael", - "Juliandavi", - "Thomaskp", - "Caed", - "Takenbot", - "Filipesperandio", - "Pmdweb", - "RuiMaciel" - ] - }, - "Web/Guide/AJAX/Comunidade": { - "modified": "2019-03-18T21:47:01.551Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/Guide/Eventos": { - "modified": "2019-03-23T22:01:48.833Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/Guide/Gráficos": { - "modified": "2019-03-18T21:46:51.581Z", - "contributors": [ - "ivolvicente", - "Anonymous" - ] - }, - "Web/Guide/HTML/Categorias_de_conteudo": { - "modified": "2019-03-18T21:30:45.160Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/Guide/HTML/Utilizar_estruturas_e_seccoes_de_HTML": { - "modified": "2019-03-18T21:46:45.859Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/HTML": { - "modified": "2020-07-22T17:12:42.326Z", - "contributors": [ - "joaonunomota", - "SphinxKnight", - "duduindo", - "tyreecruz6", - "Anonymous", - "Devenancio", - "didi9999", - "jwhitlock" - ] - }, - "Web/HTML/Aplicar_cor_elementos_HTML_utilizando_CSS": { - "modified": "2019-03-23T22:01:35.840Z", - "contributors": [ - "jwhitlock", - "Anonymous" - ] - }, - "Web/HTML/Atributos": { - "modified": "2019-03-23T22:12:57.935Z", - "contributors": [ - "jwhitlock", - "Anonymous", - "ricardomartins" - ] - }, - "Web/HTML/Atributos/rel": { - "modified": "2020-10-15T22:34:32.449Z", - "contributors": [ - "Painatalman" - ] - }, - "Web/HTML/Atributos_globais": { - "modified": "2019-03-23T22:02:25.995Z", - "contributors": [ - "Anonymous", - "jwhitlock" - ] - }, - "Web/HTML/CORS_settings_attributes": { - "modified": "2020-10-15T22:18:00.790Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/HTML/Elemento": { - "modified": "2020-11-30T19:06:39.688Z", - "contributors": [ - "jotafe32", - "joaonunomota", - "MacedoAna", - "Anonymous", - "jwhitlock", - "teoli", - "Leandro Mercês Xavier" - ] - }, - "Web/HTML/Elemento/Audio": { - "modified": "2019-03-24T00:00:34.265Z", - "contributors": [ - "jwhitlock", - "teoli", - "Leandro Mercês Xavier" - ] - }, - "Web/HTML/Elemento/Video": { - "modified": "2019-03-24T00:00:37.866Z", - "contributors": [ - "jwhitlock", - "teoli", - "Leandro Mercês Xavier" - ] - }, - "Web/HTML/Elemento/fieldset": { - "modified": "2020-10-15T22:23:45.358Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/HTML/Elemento/figcaption": { - "modified": "2019-03-24T00:12:29.922Z", - "contributors": [ - "wbamberg", - "jwhitlock", - "teoli", - "f.sanxz" - ] - }, - "Web/HTML/Elemento/head": { - "modified": "2020-10-15T21:59:43.855Z", - "contributors": [ - "jwhitlock", - "Anonymous" - ] - }, - "Web/HTML/Elemento/nav": { - "modified": "2020-10-15T21:57:44.552Z", - "contributors": [ - "jwhitlock", - "JoseRicardoGomes" - ] - }, - "Web/HTML/Elemento/progress": { - "modified": "2019-03-24T00:11:12.291Z", - "contributors": [ - "wbamberg", - "jwhitlock", - "teoli", - "gustavowiller", - "Leandro Mercês Xavier" - ] - }, - "Web/HTML/HTML5": { - "modified": "2019-03-24T00:15:44.005Z", - "contributors": [ - "InesFF", - "Anonymous", - "teoli", - "emilianocarvalho", - "vigia122", - "Dwchiang", - "Verruckt" - ] - }, - "Web/HTML/HTML5/Forms_no_HTML5": { - "modified": "2019-03-24T00:05:42.238Z", - "contributors": [ - "juliano_aguiar", - "teoli", - "Verruckt" - ] - }, - "Web/HTML/HTML5/Introdução_ao_HTML5": { - "modified": "2019-03-24T00:13:41.465Z", - "contributors": [ - "SphinxKnight", - "teoli", - "mauricio.araldi", - "xaky", - "Verruckt" - ] - }, - "Web/HTML/HTML5/Parser_HTML5": { - "modified": "2019-03-24T00:07:33.282Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/HTML/Referencia": { - "modified": "2019-09-09T07:20:05.681Z", - "contributors": [ - "SphinxKnight", - "wbamberg", - "jwhitlock", - "Anonymous" - ] - }, - "Web/HTML/Tipos_de_hiperligacao": { - "modified": "2019-03-23T22:02:19.809Z", - "contributors": [ - "jwhitlock", - "Anonymous" - ] - }, - "Web/HTML/Utilizar_a_cache_de_aplicacao": { - "modified": "2020-10-15T22:13:54.682Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/HTTP": { - "modified": "2019-05-08T19:34:36.815Z", - "contributors": [ - "wellick53", - "Joao-Henrique", - "CarlosAlbertoSzygalski", - "fscholz" - ] - }, - "Web/HTTP/CORS": { - "modified": "2020-10-15T22:15:14.685Z", - "contributors": [ - "mfuji09" - ] - }, - "Web/HTTP/CORS/Errors": { - "modified": "2019-03-18T20:48:04.840Z", - "contributors": [ - "nchevobbe" - ] - }, - "Web/HTTP/CORS/Errors/CORSDidNotSucceed": { - "modified": "2019-07-29T10:54:39.520Z", - "contributors": [ - "duduindo", - "emagombe" - ] - }, - "Web/HTTP/Headers": { - "modified": "2019-03-23T22:13:14.622Z", - "contributors": [ - "fscholz" - ] - }, - "Web/HTTP/Headers/Allow": { - "modified": "2020-07-25T17:41:28.755Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/HTTP/Headers/X-Content-Type-Options": { - "modified": "2020-10-15T21:53:51.221Z", - "contributors": [ - "tjgfernandes" - ] - }, - "Web/HTTP/Proxy_servers_and_tunneling": { - "modified": "2020-06-30T09:55:24.162Z", - "contributors": [ - "lutzleonardo15" - ] - }, - "Web/HTTP/Status": { - "modified": "2020-10-15T22:17:14.857Z", - "contributors": [ - "zhouqichao" - ] - }, - "Web/HTTP/Status/205": { - "modified": "2019-04-07T10:34:18.946Z", - "contributors": [ - "preira" - ] - }, - "Web/HTTP/Status/405": { - "modified": "2020-07-25T17:18:32.968Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/HTTP/Status/502": { - "modified": "2020-10-15T22:31:56.172Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/HTTP/Status/504": { - "modified": "2020-10-15T22:32:01.046Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/JavaScript": { - "modified": "2020-09-29T15:05:06.845Z", - "contributors": [ - "jnascimentogcc", - "Anonymous", - "SphinxKnight", - "diogo-panaca", - "ruiribeiro97", - "teoli", - "jaydson", - "Charleno Pires", - "leobalter", - "Verruckt", - "Leandro Mercês Xavier", - "Enigma", - "RuiMaciel" - ] - }, - "Web/JavaScript/Estruturas_de_dados": { - "modified": "2020-03-12T19:47:10.844Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Gestao_Memoria": { - "modified": "2020-03-12T19:47:35.757Z", - "contributors": [ - "FgfdCBVCbnsebtgf" - ] - }, - "Web/JavaScript/Guia": { - "modified": "2020-03-12T19:36:11.358Z", - "contributors": [ - "Anonymous", - "teoli", - "dancasttro", - "ethertank", - "trevorh", - "italotoffolo", - "clebermatheus", - "Verruckt" - ] - }, - "Web/JavaScript/Guia/Detalhes_do_modelo_de_objeto": { - "modified": "2020-03-12T19:44:04.803Z", - "contributors": [ - "wbamberg", - "Anonymous" - ] - }, - "Web/JavaScript/Guia/Expressoes_e_Operadores": { - "modified": "2020-03-12T19:38:04.189Z", - "contributors": [ - "duduindo", - "teoli", - "italotoffolo" - ] - }, - "Web/JavaScript/Guia/Gramática_e_tipos": { - "modified": "2020-03-12T19:44:01.097Z", - "contributors": [ - "mauraodev", - "Anonymous" - ] - }, - "Web/JavaScript/Guia/Introdução": { - "modified": "2020-03-12T19:44:03.775Z", - "contributors": [ - "jhonatansychochi", - "Redeagle48", - "Anonymous" - ] - }, - "Web/JavaScript/Guia/Introdução_ao_JavaScript": { - "modified": "2019-03-24T00:08:50.034Z", - "contributors": [ - "teoli", - "Verruckt" - ] - }, - "Web/JavaScript/Guia/Sobre": { - "modified": "2019-03-24T00:08:17.375Z", - "contributors": [ - "Anonymous", - "teoli", - "dancasttro", - "Verruckt" - ] - }, - "Web/JavaScript/Guia/Valores,_Variáveis_e_Literais": { - "modified": "2019-08-21T13:40:23.925Z", - "contributors": [ - "chibichibibr", - "SphinxKnight", - "teoli", - "Verruckt" - ] - }, - "Web/JavaScript/O_que_é_o_JavaScript": { - "modified": "2019-03-23T23:53:53.371Z", - "contributors": [ - "teoli", - "Sheppy", - "RafaelMS" - ] - }, - "Web/JavaScript/Reference": { - "modified": "2020-07-11T02:27:11.550Z", - "contributors": [ - "KINGRANDOLPH", - "Anonymous", - "dd-pardal", - "LJHarb" - ] - }, - "Web/JavaScript/Reference/Classes": { - "modified": "2020-10-15T22:00:39.801Z", - "contributors": [ - "preira", - "peter.kehl" - ] - }, - "Web/JavaScript/Reference/Classes/static": { - "modified": "2020-10-15T22:00:38.342Z", - "contributors": [ - "Painatalman" - ] - }, - "Web/JavaScript/Reference/Errors": { - "modified": "2020-03-12T19:47:09.947Z", - "contributors": [ - "Sheppy" - ] - }, - "Web/JavaScript/Reference/Errors/Not_a_function": { - "modified": "2020-07-25T16:58:44.866Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/JavaScript/Reference/Errors/Stmt_after_return": { - "modified": "2020-03-12T19:47:09.548Z", - "contributors": [ - "Anonymous", - "joao-neves95", - "PANC" - ] - }, - "Web/JavaScript/Reference/Errors/Unexpected_token": { - "modified": "2020-03-12T19:47:17.066Z", - "contributors": [ - "pedlima" - ] - }, - "Web/JavaScript/Reference/Errors/declaração_função_sem_nome": { - "modified": "2020-03-12T19:48:30.296Z", - "contributors": [ - "hudelgado" - ] - }, - "Web/JavaScript/Reference/Extratos_e_declarações": { - "modified": "2020-10-15T21:46:52.013Z", - "contributors": [ - "Anonymous", - "LucianoDos" - ] - }, - "Web/JavaScript/Reference/Extratos_e_declarações/bloco": { - "modified": "2020-10-15T22:29:44.918Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Extratos_e_declarações/for": { - "modified": "2020-10-15T22:29:45.538Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Extratos_e_declarações/return": { - "modified": "2020-10-15T21:59:53.428Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Extratos_e_declarações/throw": { - "modified": "2020-10-15T21:59:14.757Z", - "contributors": [ - "Anonymous", - "joao-neves95" - ] - }, - "Web/JavaScript/Reference/Funcionalidades_obsoletas": { - "modified": "2020-03-12T19:48:08.798Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Funcoes": { - "modified": "2020-10-15T21:59:57.286Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Funcoes/Funcoes_seta": { - "modified": "2020-10-15T22:29:39.575Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Funcoes/arguments": { - "modified": "2020-10-15T22:13:56.842Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Funcoes/parametros_rest": { - "modified": "2020-10-15T22:29:46.349Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Global_Objects": { - "modified": "2020-03-12T19:39:49.774Z", - "contributors": [ - "Anonymous", - "Redeagle48", - "SphinxKnight", - "fscholz" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array": { - "modified": "2020-10-15T21:54:01.173Z", - "contributors": [ - "joaonunomota", - "claudepache" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/concat": { - "modified": "2019-03-23T22:13:06.712Z", - "contributors": [ - "ricardomartins" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/find": { - "modified": "2020-10-15T22:02:06.522Z", - "contributors": [ - "JMoreira93" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/forEach": { - "modified": "2020-10-15T22:13:53.352Z", - "contributors": [ - "ricardomartins" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/includes": { - "modified": "2020-10-15T22:04:42.050Z", - "contributors": [ - "SandroMiguel" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/join": { - "modified": "2020-10-15T21:54:14.959Z", - "contributors": [ - "joaonunomota", - "ricardomartins" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/map": { - "modified": "2020-10-15T22:33:11.742Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/pop": { - "modified": "2020-10-15T21:58:52.123Z", - "contributors": [ - "kapz" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/reverse": { - "modified": "2019-03-23T22:12:30.952Z", - "contributors": [ - "ricardomartins" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Array/slice": { - "modified": "2020-10-15T22:31:52.359Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/JavaScript/Reference/Global_Objects/ArrayBuffer": { - "modified": "2019-03-23T22:16:35.915Z", - "contributors": [ - "anguelov" - ] - }, - "Web/JavaScript/Reference/Global_Objects/AsyncFunction": { - "modified": "2020-10-15T22:14:28.403Z", - "contributors": [ - "ramongr" - ] - }, - "Web/JavaScript/Reference/Global_Objects/AsyncFunction/prototype": { - "modified": "2020-10-15T22:14:24.948Z", - "contributors": [ - "ramongr" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Boolean": { - "modified": "2020-10-15T21:59:47.399Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Function": { - "modified": "2019-03-23T22:14:25.079Z", - "contributors": [ - "nmve" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Function/arguments": { - "modified": "2020-10-15T22:14:27.893Z", - "contributors": [ - "ramongr" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Function/call": { - "modified": "2020-10-15T21:53:17.055Z", - "contributors": [ - "joaonunomota", - "JuniorDiasOliveira", - "waveiro", - "Mega85" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Infinity": { - "modified": "2020-10-15T22:31:55.049Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Math": { - "modified": "2019-03-23T22:12:29.962Z", - "contributors": [ - "ricardomartins" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Math/ceil": { - "modified": "2020-10-15T21:58:11.563Z", - "contributors": [ - "carlos-menezes", - "MarcioFonseca" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number": { - "modified": "2019-03-23T22:49:01.559Z", - "contributors": [ - "Redeagle48", - "fscholz" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/MAX_VALUE": { - "modified": "2019-03-23T22:49:07.538Z", - "contributors": [ - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/MIN_VALUE": { - "modified": "2019-03-23T22:49:09.973Z", - "contributors": [ - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/NEGATIVE_INFINITY": { - "modified": "2020-10-15T21:38:19.186Z", - "contributors": [ - "joaonunomota", - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/NaN": { - "modified": "2019-03-23T22:49:09.414Z", - "contributors": [ - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/isFinite": { - "modified": "2019-03-23T22:49:12.149Z", - "contributors": [ - "SphinxKnight", - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/isInteger": { - "modified": "2019-03-23T22:49:17.052Z", - "contributors": [ - "SphinxKnight", - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/isNaN": { - "modified": "2019-03-23T22:49:10.417Z", - "contributors": [ - "SphinxKnight", - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/prototype": { - "modified": "2019-03-23T22:49:04.241Z", - "contributors": [ - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Number/toString": { - "modified": "2019-03-23T22:49:00.338Z", - "contributors": [ - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Object": { - "modified": "2020-10-15T21:30:54.647Z", - "contributors": [ - "Anonymous", - "wbamberg", - "fscholz" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Object/hasOwnProperty": { - "modified": "2019-03-23T22:42:57.159Z", - "contributors": [ - "gabrielpconceicao" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Object/prototype": { - "modified": "2020-10-15T22:13:51.986Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Global_Objects/String": { - "modified": "2020-10-15T21:38:27.657Z", - "contributors": [ - "erickbRodrigues", - "Anonymous", - "ricardomartins", - "lpimenta-ptc", - "Sheppy" - ] - }, - "Web/JavaScript/Reference/Global_Objects/String/Trim": { - "modified": "2019-03-23T22:13:05.964Z", - "contributors": [ - "ricardomartins" - ] - }, - "Web/JavaScript/Reference/Global_Objects/String/indexOf": { - "modified": "2019-03-23T22:49:09.792Z", - "contributors": [ - "SandroMiguel", - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/String/length": { - "modified": "2019-03-23T22:49:00.693Z", - "contributors": [ - "Redeagle48" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Symbol": { - "modified": "2019-03-23T22:24:48.766Z", - "contributors": [ - "ZeikJT" - ] - }, - "Web/JavaScript/Reference/Global_Objects/Symbol/hasInstance": { - "modified": "2019-03-23T22:24:53.893Z", - "contributors": [ - "GoToLoop" - ] - }, - "Web/JavaScript/Reference/Global_Objects/encodeURI": { - "modified": "2020-03-12T19:42:17.895Z", - "contributors": [ - "kempcarlos" - ] - }, - "Web/JavaScript/Reference/Operadores": { - "modified": "2020-10-15T21:46:57.076Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Operadores/Operador_virgula": { - "modified": "2020-10-15T22:29:46.734Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Operadores/Precedencia_operador": { - "modified": "2020-05-03T13:58:58.457Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Operadores/função": { - "modified": "2020-10-15T22:29:38.999Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/JavaScript/Reference/Sobre": { - "modified": "2020-03-12T19:44:03.544Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/Manifest": { - "modified": "2020-10-15T22:23:27.262Z", - "contributors": [ - "nersofiripi", - "Anonymous" - ] - }, - "Web/MathML": { - "modified": "2020-11-09T15:01:38.012Z", - "contributors": [ - "joaonunomota", - "Joao_Ledo_Fonseca", - "Anonymous" - ] - }, - "Web/MathML/Attribute": { - "modified": "2020-08-21T12:44:51.026Z", - "contributors": [ - "joaonunomota", - "fscholz" - ] - }, - "Web/MathML/Attribute/Valores": { - "modified": "2020-07-22T19:30:01.211Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Authoring": { - "modified": "2020-08-15T14:39:49.860Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element": { - "modified": "2020-08-16T17:33:47.904Z", - "contributors": [ - "joaonunomota", - "fscholz" - ] - }, - "Web/MathML/Element/maction": { - "modified": "2020-10-15T22:32:30.845Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/math": { - "modified": "2020-10-15T22:32:00.988Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/menclose": { - "modified": "2020-10-15T22:31:58.519Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/merror": { - "modified": "2020-10-15T22:31:57.892Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mfenced": { - "modified": "2020-10-15T22:32:16.693Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mfrac": { - "modified": "2020-10-15T22:32:37.302Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mglyph": { - "modified": "2020-10-15T22:32:17.025Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mi": { - "modified": "2020-10-15T22:32:20.399Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mlabeledtr": { - "modified": "2020-10-15T22:32:27.553Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mmultiscripts": { - "modified": "2020-10-15T22:32:37.118Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mn": { - "modified": "2020-10-15T22:32:26.157Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mo": { - "modified": "2020-10-15T22:32:19.754Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mover": { - "modified": "2020-10-15T22:32:19.618Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mpadded": { - "modified": "2020-10-15T22:32:28.264Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mphantom": { - "modified": "2020-10-15T22:32:22.218Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mroot": { - "modified": "2020-10-15T22:32:22.430Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mrow": { - "modified": "2020-10-15T22:31:58.300Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/ms": { - "modified": "2020-10-15T22:32:22.427Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mspace": { - "modified": "2020-10-15T22:31:55.582Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/msqrt": { - "modified": "2020-10-15T22:32:22.151Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mstyle": { - "modified": "2020-10-15T22:33:04.564Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/msub": { - "modified": "2020-10-15T22:32:21.086Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/msubsup": { - "modified": "2020-10-15T22:32:22.170Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/msup": { - "modified": "2020-10-15T22:32:20.360Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mtable": { - "modified": "2020-10-15T22:33:04.410Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mtd": { - "modified": "2020-10-15T22:32:00.353Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mtext": { - "modified": "2020-10-15T22:31:59.109Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/mtr": { - "modified": "2020-10-15T22:31:55.409Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/munder": { - "modified": "2020-10-15T22:32:18.823Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/munderover": { - "modified": "2020-10-15T22:32:21.240Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Element/semantics": { - "modified": "2020-10-15T22:32:26.955Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Examples": { - "modified": "2020-08-18T09:59:11.744Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Examples/Derivar_a_Formula_Resolvente": { - "modified": "2020-08-16T17:37:40.689Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Examples/MathML_teorema_de_Pitagoras": { - "modified": "2020-08-16T17:39:52.993Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/MathML/Index": { - "modified": "2020-08-16T17:30:38.516Z", - "contributors": [ - "joaonunomota" - ] - }, - "Web/Progressive_web_apps": { - "modified": "2020-04-23T09:44:00.269Z", - "contributors": [ - "Anonymous", - "chrisdavidmills" - ] - }, - "Web/Progressive_web_apps/Guia_de_programacao": { - "modified": "2020-04-23T09:38:24.576Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/Progressive_web_apps/Identificavel": { - "modified": "2019-03-18T20:52:07.669Z", - "contributors": [ - "chrisdavidmills", - "Anonymous" - ] - }, - "Web/Progressive_web_apps/Responsivo": { - "modified": "2019-03-18T20:52:08.064Z", - "contributors": [ - "chrisdavidmills", - "Anonymous" - ] - }, - "Web/Progressive_web_apps/Responsivo/Elementos_base_desenho_adaptavel": { - "modified": "2019-04-16T06:29:21.711Z", - "contributors": [ - "diogo-panaca" - ] - }, - "Web/Progressive_web_apps/Seguro": { - "modified": "2019-03-18T20:52:08.238Z", - "contributors": [ - "chrisdavidmills", - "Anonymous" - ] - }, - "Web/Reference": { - "modified": "2020-07-20T13:13:52.229Z", - "contributors": [ - "joaonunomota", - "Anonymous", - "carlosrainhaaraujo", - "kscarfone" - ] - }, - "Web/Reference/API": { - "modified": "2019-03-23T23:22:11.761Z", - "contributors": [ - "Anonymous", - "carlosrainhaaraujo" - ] - }, - "Web/SVG": { - "modified": "2020-04-23T09:30:08.420Z", - "contributors": [ - "Anonymous", - "teoli", - "guerreirogabriel", - "fscholz", - "Verruckt", - "RuiMaciel" - ] - }, - "Web/SVG/Aplicar_efeitos_SVG_conteudo_HTML": { - "modified": "2019-03-23T22:01:45.461Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/SVG/Element": { - "modified": "2020-04-23T09:28:28.562Z", - "contributors": [ - "Anonymous", - "ricardomartins" - ] - }, - "Web/SVG/Namespaces_Crash_Course": { - "modified": "2019-03-23T22:01:50.555Z", - "contributors": [ - "Anonymous", - "somascope" - ] - }, - "Web/SVG/Namespaces_Crash_Course/Exemplo": { - "modified": "2019-03-23T22:01:57.842Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/SVG/SVG_animacao_com_SMIL": { - "modified": "2020-04-23T08:20:39.391Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/SVG/Tutorial": { - "modified": "2019-01-16T14:01:46.161Z", - "contributors": [ - "Anonymous", - "teoli", - "guerreirogabriel" - ] - }, - "Web/SVG/Tutorial/Introducao": { - "modified": "2020-04-23T09:22:08.765Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/SVG/Tutorial/SVG_na_Introducao_HTML": { - "modified": "2019-03-23T22:01:48.509Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/Security/Conteudo_misto": { - "modified": "2019-03-23T22:05:48.971Z", - "contributors": [ - "Anonymous", - "sideshowbarker" - ] - }, - "Web/Security/Mixed_content/Como_corrigir_um_site_da_Web_com_conteudo_misto_bloqueado": { - "modified": "2019-03-23T22:05:54.761Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/Security/Secure_Contexts": { - "modified": "2019-03-23T22:01:19.367Z", - "contributors": [ - "Anonymous", - "Sheppy" - ] - }, - "Web/Seguranca": { - "modified": "2019-09-10T16:45:22.612Z", - "contributors": [ - "SphinxKnight", - "Anonymous" - ] - }, - "Web/Seguranca/Palavras-passe_inseguras": { - "modified": "2019-03-23T22:01:41.675Z", - "contributors": [ - "rborges77", - "Anonymous" - ] - }, - "Web/Seguranca/Same-origin_policy": { - "modified": "2020-09-26T17:57:02.589Z", - "contributors": [ - "Samuel-Ferdnand" - ] - }, - "Web/Tutoriais": { - "modified": "2020-05-03T14:51:14.988Z", - "contributors": [ - "Anonymous" - ] - }, - "Web/WebAPI": { - "modified": "2019-03-23T22:01:53.174Z", - "contributors": [ - "Anonymous", - "wbamberg", - "fscholz" - ] - }, - "Web/XML": { - "modified": "2020-04-23T08:26:21.649Z", - "contributors": [ - "Anonymous", - "ExE-Boss" - ] - }, - "Web/XML/Introducao_a_XML": { - "modified": "2019-05-01T21:54:16.756Z", - "contributors": [ - "ExE-Boss", - "Anonymous" - ] - }, - "Web/XSLT": { - "modified": "2019-03-24T00:03:57.070Z", - "contributors": [ - "ExE-Boss", - "Anonymous", - "fscholz", - "Verruckt", - "RuiMaciel" - ] - }, - "Web/XSLT/Comunidade": { - "modified": "2019-01-16T16:00:25.874Z", - "contributors": [ - "ExE-Boss", - "Leandro Mercês Xavier" - ] - }, - "Web/XSLT/Elementos": { - "modified": "2019-03-23T23:45:26.056Z", - "contributors": [ - "ExE-Boss", - "Verruckt" - ] - }, - "WebAssembly": { - "modified": "2020-10-15T22:07:45.071Z", - "contributors": [ - "Anonymous" - ] - }, - "WebAssembly/Utilizar_API_JavaScript_WebAssembly": { - "modified": "2019-03-18T21:28:49.091Z", - "contributors": [ - "Anonymous" - ] - }, - "XForms": { - "modified": "2019-03-23T23:46:37.205Z", - "contributors": [ - "Luis Henrique Sousa" - ] - }, - "XForms/Controles_Customizados": { - "modified": "2019-01-16T16:02:25.038Z", - "contributors": [ - "Kayalemao", - "Leandro Mercês Xavier", - "Verruckt" - ] - }, - "XForms_especiais_para_Mozilla": { - "modified": "2019-03-23T23:56:39.810Z", - "contributors": [ - "Verruckt", - "Kayalemao" - ] - }, - "XHTML": { - "modified": "2019-03-23T23:40:29.099Z", - "contributors": [ - "Anonymous", - "RuiMaciel" - ] - }, - "XMLHttpRequest": { - "modified": "2019-03-23T23:50:48.749Z", - "contributors": [ - "SphinxKnight", - "Leandro Mercês Xavier", - "RuiMaciel" - ] - }, - "XML_no_Mozilla": { - "modified": "2019-11-21T20:42:12.364Z", - "contributors": [ - "wbamberg", - "Verruckt", - "Victorino" - ] - }, - "XPath/Eixos": { - "modified": "2019-01-16T16:02:01.247Z", - "contributors": [ - "Verruckt" - ] - }, - "XPath/Funções": { - "modified": "2019-01-16T16:07:00.758Z", - "contributors": [ - "Verruckt" - ] - } -} \ No newline at end of file diff --git a/files/pt-pt/archive/add-ons/communication_between_html_and_your_extension/index.html b/files/pt-pt/archive/add-ons/communication_between_html_and_your_extension/index.html deleted file mode 100644 index c3b06f74f9..0000000000 --- a/files/pt-pt/archive/add-ons/communication_between_html_and_your_extension/index.html +++ /dev/null @@ -1,130 +0,0 @@ ---- -title: Comunicação entre HTML e a sua extensão -slug: Archive/Add-ons/Communication_between_HTML_and_your_extension -tags: - - Desenvolvimento da Web - - Extensões - - Extras -translation_of: Archive/Add-ons/Communication_between_HTML_and_your_extension ---- -

Consulte também Interação entre páginas privilegiadas e não privilegiadas.

- -

Comunicação entre uma página HTML e a extensão

- -

After building a sample extension by reading carefully and following the complete instructions for Building an Extension I was able to get an extension that could display something on the status bar. What I wanted to do was have an extension "look" for something on an HTML page and if it found that something perform some operation on the found thing and then update the status bar with the results of the operation. With a lot of help from irc://irc.mozilla.org#js and irc://irc.mozilla.org#extdev I was able to get it running pretty well, but I still would rather have the client less responsible for pinging the extension to "look" for what is on the page.

- -
O que eu tentei
- - - - - -

The basic problem with the event model is probably due to what I was trying to do. In my HTML I have an input element in a form. I set the onBlur action to a little javascript function that performed a standard AJAX request to get a result. The onreadystatechange was set to another little javascript function that would update a specific element on the HTML page with the result. The result of the AJAX request was the something that I wanted the extension to find. There were only a handful of events that seemed relevant (Load, Change, DOMInsertNode, DOMInsertNodeIntoDocument, DOMActivate) and I tried them all in many different ways. Some of the events only apply to certain types of elements so I included trying to modify the result of the AJAX request to be of the appropriate element type (img, which supports "onLoad," rather than span, which doesn't, for example).

- -

The problem with the events is the timing. I wasn't sure about the difference between the capture or bubbling flag that you pass to addEventListener but every time I would catch the event in the extension, the element from the AJAX request wasn't fully updated into the HTML page. What that meant is that everytime the extension went looking for the element, it wasn't there yet.

- -

As a last ditch effort I tried setting a timeout using setTimeout when I got the event in the extension to wait a few milliseconds before looking for the desired element. This was non-optimal and the timeout wasn't very reliable for some reason. Sometimes I would get the timeout, sometimes I would'nt.

- -
O que eu consegui no final
- -

Some helpful information on the irc channel led me to believe that a custom event might help. I started to research custom events on Google but everything that I found was far too complicated for what I wanted to achieve. Eventually I put the creation of the custom event into the stateChanged function that was handling the receipt of the AJAX request. After the HTML component was update with the result of the AJAX request, I created and dispatched the event like this:

- -
   var event = document.createEvent("Events");
-   event.initEvent("my-custom-event", true, true);
-   document.body.dispatchEvent(event);
-
- -

In the code of the extension that catches the loading of a new page I added this code:

- -
   var doc = aEvent.originalTarget; // doc is document that triggered "onload" event
-   // do something with the loaded page.
-   // doc.location is a Location object (see below for a link).
-   // You can use it to make your code executed on certain pages only.
-   if (doc && doc.addEventListener)
-     doc.addEventListener("my-custom-event", myExtension.customReceived, false);
-
- -

Since the event is dispatched after the element in the HTML is updated by the statusChanged function, the element that extension is looking for is there to find.

- -
- - - - - -
diff --git a/files/pt-pt/archive/add-ons/extensoes_bootstrapped/index.html b/files/pt-pt/archive/add-ons/extensoes_bootstrapped/index.html deleted file mode 100644 index e665476bcb..0000000000 --- a/files/pt-pt/archive/add-ons/extensoes_bootstrapped/index.html +++ /dev/null @@ -1,352 +0,0 @@ ---- -title: Extensões bootstrapped -slug: Archive/Add-ons/Extensoes_bootstrapped -tags: - - Extensões - - Extras - - Firefox 4 - - Gecko 2.0 - - Guía - - Localização - - Tradução -translation_of: Archive/Add-ons/Bootstrapped_extensions ---- -

browser.bookmarks.export( function() {...} // optional function ){{LegacyAddonsNotice}}{{AddonSidebar}}

- -

{{ gecko_minversion_header("2.0") }}

- -

Traditional extensions include overlays, wherein the application can load up XUL from the extension's package and automatically apply it on top its own UI. While this makes creating extensions that add to the application's user interface relatively easy, it means that updating, installing, or disabling an extension requires an application restart.

- -

Gecko 2.0 {{ geckoRelease("2.0") }} introduces bootstrapped extensions. These are special extensions that, instead of using overlays to apply their user interface to the application, programmatically insert themselves into the application. This is done using a special script file that's included in the extension that contains functions the browser calls to command the extension to install, uninstall, start up, and shut down.

- -

All the application does is call into this script file; the extension is responsible for adding and removing its user interface and handling any other setup and shutdown tasks it requires.

- -

This article discusses how bootstrapped extensions work. See this tutorial on converting from an overlay extension to restartless for a practical step by step guide to migrating.

- -

O processo de arranque e encerramento

- -

A key feature of bootstrapped extensions is that they must be able to start up and shut down on demand by the application. When the extension's startup() function is called, it must manually inject its user interface and other behavior into the application. Similarly, when its shutdown() function is called, it must remove anything that it has added to the application, as well as all references to any of its objects.

- -

There are several scenarios in which the startup() function may be called; for example:

- - - -

Some examples of when the shutdown() function may be called:

- - - -

Notas na modificação da inteface da aplicação do utilizador

- -

chrome.manifest nos extras de bootstrapped

- -

You can use a chrome.manifest file in bootstrapped add-ons to:

- - - -

Not all chrome.manifest instructions are supported in bootstrapped add-ons, for example you still cannot register XUL Overlays from a bootstrapped add-on. See the chrome.manifest documentation for details.

- -

In Firefox 10 and later the chrome.manifest file located in the root of the add-on's XPI (i.e. a sibling of the install.rdf) is loaded automatically. In Firefox 8 and 9 you had to load/unload the manifest manually using {{ ifmethod("nsIComponentManager", "addBootstrappedManifestLocation") }} and {{ ifmethod("nsIComponentManager", "removeBootstrappedManifestLocation") }}. This feature was unavailable in Firefox versions before 8.

- -

Adicionar manualmente a interface do utilizador

- -

If you decide to go ahead and try to develop a bootstrapped extension that modifies the application's user interface, here are a few suggestions to get you started.

- -

You need to look up the relevant application UI elements by their ID by calling {{ domxref("document.getElementById()") }}, then manipulate them to inject your UI. For example, you can get access to the menu bar in Firefox with document.getElementById("main-menubar").

- -

Be sure that at shutdown time, you remove any user interface you've added.

- -

Criar uma extensão bootstrapped

- -

To mark an extension as bootstrappable, you need to add the following element to its install manifest:

- -
<em:bootstrap>true</em:bootstrap>
- -

Then you need to add a bootstrap.js file that contains the required functions; this should be alongside the install.rdf file in the extension's package.

- -

Compatibilidade com versões anteriores

- -

Because older versions of Firefox don't know about the bootstrap property or bootstrap.js file, it's not overly difficult to create an XPI that will work on both as a bootstrappable extension and as a traditional extension. Create your extension as a bootstrappable extension, then add the traditional overlays as well. Newer versions of Firefox will use the bootstrap.js script, ignoring the components and overlays, while older versions will use the overlays.

- -

Pontos de entrada de bootstrap

- -

The bootstrap.js script should contain several specific functions, which are called by the browser to manage the extension. The script gets executed in a privileged sandbox, which is cached until the extension is shut down.

- -

arranque

- -

Called when the extension needs to start itself up. This happens at application launch time, when the extension is enabled after being disabled or after it has been shut down in order to install an update. As such, this can be called many times during the lifetime of the application.

- -

This is when your add-on should inject its UI, start up any tasks it may need running and so forth.

- -
void startup(
-  data,
-  reason
-);
-
- -
Parameters
- -
-
data
-
A bootstrap data structure.
-
reason
-
One of the reason constants, indicating why the extension is being started up. This will be one of APP_STARTUP, ADDON_disable, ADDON_INSTALL, ADDON_UPGRADE, or ADDON_DOWNGRADE.
-
- -

encerramento

- -

Called when the extensidisableon needs to shut itself down, such as when the application is quitting or when the extension is about to be upgraded or disabled. Any user interface that has been injected must be removed, tasks shut down, and objects disposed of.

- -
void shutdown(
-  data,
-  reason
-);
-
- -
Parameters
- -
-
data
-
A bootstrap data structure.
-
reason
-
One of the reason constants, indicating why the extension is being shut down. This will be one of APP_SHUTDOWN, ADDON_DISABLE, ADDON_UNINSTALL, ADDON_UPGRADE, or ADDON_DOWNGRADE.
-
- -

instalar

- -

Your bootstrap script must include an install() function, which the application calls before the first call to startup() after the extension is installed, upgraded, or downgraded.

- -
void install(
-  data,
-  reason
-);
-
- -
Parameters
- -
-
data
-
A bootstrap data structure.
-
reason
-
One of the reason constants, indicating why the extension is being installed. This will be one of ADDON_INSTALL, ADDON_UPGRADE, or ADDON_DOWNGRADE.
-
- -

desinstalar

- -

This function is called after the last call to shutdown() before a particular version of an extension is uninstalled.

- -
Nota: If you open the add-on manager and then click "Remove" on an add-on, it will not call uninstall function right away. This is a soft uninstall because of the available "Undo" option. If the add-on manager is closed or another event takes place such that the "Undo" option becomes unavailable, then the hard uninstall takes place and the uninstall function is called.
- -
Nota: The uninstall function fires on downgrade and upgrade as well so you should make sure it is an uninstall by doing this:
-function uninstall(aData, aReason) {
-     if (aReason == ADDON_UNINSTALL) {
-          console.log('really uninstalling');
-     } else {
-          console.log('not a permanent uninstall, likely an upgrade or downgrade');
-     }
-}
- -
void uninstall(
-  data,
-  reason
-);
-
- -
Parâmetros
- -
-
data
-
Uma estrutura de dados de bootstrap.
-
reason
-
One of the reason constants, indicating why the extension is being uninstalled. This will be one of ADDON_UNINSTALL, ADDON_UPGRADE, or ADDON_DOWNGRADE.
-
- -

Contantes reason

- -

The bootstrap functions accept a reason parameter, which explains to the extension why it's being called. The reason constants are:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstanteValorDescrição
APP_STARTUP1The application is starting up.
APP_SHUTDOWN2The application is shutting down.
ADDON_ENABLE3The add-on is being enabled.
ADDON_DISABLE4The add-on is being disabled. (Also sent during uninstallation)
ADDON_INSTALL5The add-on is being installed.
ADDON_UNINSTALL6The add-on is being uninstalled.
ADDON_UPGRADE7The add-on is being upgraded.
ADDON_DOWNGRADE8The add-on is being downgraded.
- -

Dados de bootstrap

- -

Each of the entry points is passed a simple data structure containing some useful information about the add-on being bootstrapped. More information about the add-on can be obtained by calling AddonManager.getAddonByID(). The data is a simple JavaScript object with the following properties:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PropriedadeTipoDescrição
idstringThe ID of the add-on being bootstrapped.
versionstringThe version of the add-on being bootstrapped.
installPathnsIFileThe installation location of the add-on being bootstrapped. This may be a directory or an XPI file depending on whether the add-on is installed unpacked or not.
resourceURInsIURIA URI pointing at the root of the add-ons files, this may be a jar: or file: URI depending on whether the add-on is installed unpacked or not. {{ gecko_minversion_inline("7.0") }}
oldVersionstringThe previously installed version, if the reason is ADDON_UPGRADE or ADDON_DOWNGRADE, and the method is install or startup. {{ gecko_minversion_inline("22.0") }}
newVersionstringThe version to be installed, if the reason is ADDON_UPGRADE or ADDON_DOWNGRADE, and the method is shutdown or uninstall. {{ gecko_minversion_inline("22.0") }}
- -
-

Nota: An add-on may be upgraded/downgraded at application startup, in this case the startup method reason is APP_STARTUP, and the oldVersion property is not set. Also be aware that in some circumstances an add-on upgrade/downgrade may occur without the uninstall method being called.

-
- -

Depurador de extra (add-on)

- -

From Firefox 31 onwards, you can use the Add-on Debugger to debug bootstrapped add-ons.

- -

Localização (L10n)

- -

Localizing bootstrapped add-ons is very much the same since Firefox 7, as that is when chrome.manifest compatibility landed.

- -

Ficheiros JS e JSM - Utilizando Ficheiros de Propriedade

- -

Para localizar os seus ficheiros .js e .jsm tem de utilziar os ficheiros de propriedade.

- -

The absolute minimum needed here is:

- -
    -
  1. File: install.rdf
    2. -
  2. File: chrome.manifest
    3. -
  3. File: bootstrap.js
    4. -
  4. Folder: locale -
      -
    1. Folder: VALID_LOCALE_HERE -
        -
      1. File: ANYTHING.properties
        2. -
      -
      2. -
    -
    5. -
- -

In the locale folder you must have folders for each of the languages you want to provide; each folder must be named a valid locale (ex: en-US). Inside this folder must be a property file. Inside the chrome.manifest file these locale must be defined. For example if you had a subfolder of en-US in locale folder your chrome.manifest file will have to contain: locale NAME_OF_YOUR_ADDON en-US locale/en-US/

- -

Here is an example: GitHub :: l10n-properties - on startup of this add-on it will show a prompt saying USA or Great Britain, which ever it deems closest to your locale. You can test different locale by going to about:config and changing preference of general.useragent.locale to en-US and then to en-GB and disabling then re-enabling the add-on.

- -

XUL and HTML Files - Using Entities from DTD Files

- -

Many times HTML pages are used, however they cannot be localized with DTD files. There are three changes you must make:

- -
    -
  1. You have to change the HTML file's extension to be .xhtml
    2. -
  2. The doctype must be defined point to a DTD file in your locale folder such as: <!DOCTYPE html SYSTEM "chrome://l10n/locale/mozilla.dtd">
    3. -
  3. Must add xmlns attribute to html tag for example: <html xmlns="http://www.w3.org/1999/xhtml">
    4. -
  4. If you have multiple DTD files read on here: Using multiple DTDs
    5. -
- -

The bare minimum needed is:

- -
    -
  1. File: install.rdf
    2. -
  2. File: chrome.manifest
    3. -
  3. File: bootstrap.js
    4. -
  4. Folder: locale -
      -
    1. Folder: VALID_LOCALE_HERE -
        -
      1. File: ANYTHING.dtd
        2. -
      -
      2. -
    -
    5. -
- -

The chrome.manifest file must include a definition for content for example: content NAME_OF_YOUR_ADDON ./

- -

The chrome.manifest file must also include a line pointing to the locale, just like in the above property section, if you had a folder named en-US in locale, the chrome.manifest file should contain: locale NAME_OF_YOUR_ADDON en-US locale/en-US/

- -

Here is an example add-on that opens an HTML page and a XUL page on install: GitHub :: l10n-xhtml-xul. Here is an example showing how to use a localized HTML page as an options page: GitHub :: l10n-html-options. You can go to about:config and change the value of the preference general.useragent.locale to en-US and then to en-GB and then reload the open pages to see the localization change.

- -

Leitura adicional

- - diff --git a/files/pt-pt/archive/add-ons/index.html b/files/pt-pt/archive/add-ons/index.html deleted file mode 100644 index 9c0f942944..0000000000 --- a/files/pt-pt/archive/add-ons/index.html +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Add-ons -slug: Archive/Add-ons -tags: - - NeedsTranslation - - TopicStub -translation_of: Archive/Add-ons ---- -

Archived add-ons documentation.

- -

{{SubpagesWithSummaries}}

diff --git a/files/pt-pt/archive/add-ons/interaction_between_privileged_and_non-privileged_pages/index.html b/files/pt-pt/archive/add-ons/interaction_between_privileged_and_non-privileged_pages/index.html deleted file mode 100644 index 3b8723a163..0000000000 --- a/files/pt-pt/archive/add-ons/interaction_between_privileged_and_non-privileged_pages/index.html +++ /dev/null @@ -1,375 +0,0 @@ ---- -title: Interação entre páginas privilegiadas e não privilegiadas -slug: Archive/Add-ons/Interaction_between_privileged_and_non-privileged_pages -tags: - - Code snippets - - Extensões - - Extras -translation_of: Archive/Add-ons/Interaction_between_privileged_and_non-privileged_pages ---- -

Enviar dados de um documento sem privilégios para o chrome

- -

An easy way to send data from a web page to an extension is by using custom DOM events. In your extension's browser.xul overlay, write code which listens for a custom DOM event. Here we call the event MyExtensionEvent.

- -
var myExtension = {
-  myListener: function(evt) {
-    alert("Received from web page: " +
-          evt.target.getAttribute("attribute1") + "/" +
-          evt.target.getAttribute("attribute2"));
-  }
-}
-document.addEventListener("MyExtensionEvent", function(e) { myExtension.myListener(e); }, false, true);
-// The last value is a Mozilla-specific value to indicate untrusted content is allowed to trigger the event.
-
- -

The data from the web page (unprivileged code) will be the values of attribute1 and attribute2. To trigger the alert() in the listener and pass the data from the web page, write code such as this in the web page:

- -
var element = document.createElement("MyExtensionDataElement");
-element.setAttribute("attribute1", "foobar");
-element.setAttribute("attribute2", "hello world");
-document.documentElement.appendChild(element);
-
-var evt = document.createEvent("Events");
-evt.initEvent("MyExtensionEvent", true, false);
-element.dispatchEvent(evt);
-
- -

This code creates an arbitrary element -- <MyExtensionDataElement/> -- and inserts it into the web page's DOM. Values are set for two arbitrary attributes on the element. These can also be named anything you like, but we've chosen attribute1 and attribute2. Finally, the code creates and dispatches a custom event named MyExtensionEvent -- similar to the standard DOM click event you catch with onclick handlers. The event bubbles up from the web page and reaches the extension (privileged code) where your listener catches it and reads the attribute values from the DOM element where the event originated.

- -

(To better ensure others do not also implement the same event with a different meaning, one might either attach a namespace to <MyExtensionDataElement/>  and check on the event handler for the correct namespaceURI property, or as per the DOM specification, use initEvent() with an event name that is itself namespaced (XML Name characters only): "It is also strongly recommended that third parties adding their own events use their own prefix to avoid confusion and lessen the probability of conflicts with other new events.")

- -

In the case where your extension's overlay does not interact directly with browser.xul, such as in a sidebar, it might be easier to add the event listener to the top-level document directly as shown below (also see: accessing the elements of the top-level document from a child window).

- -
var mainWindow = window.QueryInterface(Components.interfaces.nsIInterfaceRequestor)
-                  .getInterface(Components.interfaces.nsIWebNavigation)
-                  .QueryInterface(Components.interfaces.nsIDocShellTreeItem)
-                  .rootTreeItem
-                  .QueryInterface(Components.interfaces.nsIInterfaceRequestor)
-                  .getInterface(Components.interfaces.nsIDOMWindow);
-mainWindow.document.addEventListener("MyExtensionEvent", function(e) { myExtension.myListener(e); }, false, true);
-
- -

If you need to to pass lots of data, consider using CDATA sections instead of the simple attributes on a custom element.

- -

Note: If you're using HTML5's postMessage() to send a message from unprivileged code to privileged code, adding 'true' to the end of your event listener in your privileged chrome code will allow the message to be received.

- -

 

- -
document.addEventListener("message", function(e) { yourFunction(e); }, false, true);
- -

Enviar dados do chrome para um documento sem privilégios

- -

To "answer" the web page (e.g., return code), your extension can set an attribute or attach child elements on the event target element (<MyExtensionDataElement/> in this example).

- -

You can optionally clean up the created element, or create it once when the web page loads then re-use it each time.

- -

Another option is to send a return event from the extension to the web page. This can be done using the same principle as the above example.

- -

There is only one extension, but there can be many active web pages. So to trigger the right event on the right page we have to tell the extension which page to call. The information we need for that is contained in evt.target.ownerDocument.

- -

We can extend the above example with some data transfer from the extension to the web page. In the following code sample 2 methods are combined: Setting an extra attribute in the original event target element, and creating a new event message with a new event target element. For this to work we need to define the original target element globally. We need a new event trigger in the web page and some code to show the event message actually arrived. In the extension we have to dispatch an event message to the right web page.

- -

The code containing the callback could look like this:

- -

In the extension:

- -
var myExtension =
-{
-  myListener: function(evt)
-  {
-    alert("Received from web page: " +
-           evt.target.getAttribute("attribute1") + "/" +
-           evt.target.getAttribute("attribute2"));
-
-/* the extension answers the page*/
-    evt.target.setAttribute("attribute3", "The extension");
-
-    var doc = evt.target.ownerDocument;
-
-    var AnswerEvt = doc.createElement("MyExtensionAnswer");
-    AnswerEvt.setAttribute("Part1", "answers this.");
-
-    doc.documentElement.appendChild(AnswerEvt);
-
-    var event = doc.createEvent("HTMLEvents");
-    event.initEvent("MyAnswerEvent", true, false);
-    AnswerEvt.dispatchEvent(event);
-  }
-}
-
-document.addEventListener("MyExtensionEvent", function(e) { myExtension.myListener(e); }, false, true);
-// The last value is a Mozilla-specific value to indicate untrusted content is allowed to trigger the event.
-
- -

In the web page:

- -
document.addEventListener("MyAnswerEvent",function(e) { ExtensionAnswer(e); },false);
-
-var element;
-
-function CallExtension()
-{
-  var element = document.createElement("MyExtensionDataElement");
-  element.setAttribute("attribute1", "foobar");
-  element.setAttribute("attribute2", "hello world");
-  document.documentElement.appendChild(element);
-  var evt = document.createEvent("Events");
-  evt.initEvent("MyExtensionEvent", true, false);
-  element.dispatchEvent(evt);
-}
-
-function ExtensionAnswer(EvtAnswer)
-{
-  alert(element.getAttribute("attribute3") + " " +
-        EvtAnswer.target.getAttribute("Part1"));
-}
-
- -

Basic example of similar idea, extension passes information via attributes and fires event on div in page, here.

- -

Chromium-like messaging: json request with json callback

- -

Web page:

- -
<html>
-  <head>
-    <script>
-      var something = {
-        send_request: function(data, callback) { // analogue of chrome.extension.sendRequest
-          var request = document.createTextNode(JSON.stringify(data));
-
-          request.addEventListener("something-response", function(event) {
-            request.parentNode.removeChild(request);
-
-            if (callback) {
-              var response = JSON.parse(request.nodeValue);
-              callback(response);
-            }
-          }, false);
-
-          document.head.appendChild(request);
-
-          var event = document.createEvent("HTMLEvents");
-          event.initEvent("something-query", true, false);
-          request.dispatchEvent(event);
-        },
-
-        callback: function(response) {
-          return alert("response: " + (response ? response.toSource() : response));
-        }
-      }
-    </script>
-  </head>
-  <body>
-    <button onclick="return something.send_request({foo: 1}, something.callback)">send {foo: 1} with callback</button>
-    <button onclick="return something.send_request({baz: 3}, something.callback)">send {baz: 3} with callback</button>
-    <button onclick="return something.send_request({mozilla: 3})">send {mozilla: 3} without callback</button>
-    <button onclick="return something.send_request({firefox: 4}, something.callback)">send {firefox: 4} with callback</button>
-  </body>
-</html>
-
- -

Overlay on browser.xul in your extension:

- -
var something = {
-  listen_request: function(callback) { // analogue of chrome.extension.onRequest.addListener
-    document.addEventListener("something-query", function(event) {
-      var node = event.target;
-      if (!node || node.nodeType != Node.TEXT_NODE)
-        return;
-
-      var doc = node.ownerDocument;
-      callback(JSON.parse(node.nodeValue), doc, function(response) {
-        node.nodeValue = JSON.stringify(response);
-
-        var event = doc.createEvent("HTMLEvents");
-        event.initEvent("something-response", true, false);
-        return node.dispatchEvent(event);
-      });
-    }, false, true);
-  },
-
-  callback: function(request, sender, callback) {
-    if (request.foo) {
-      return setTimeout(function() {
-      callback({bar: 2});
-      }, 1000);
-    }
-
-    if (request.baz) {
-      return setTimeout(function() {
-      callback({quux: 4});
-      }, 3000);
-    }
-
-    if (request.mozilla) {
-      return alert("alert in chrome");
-    }
-
-    return callback(null);
-  }
-}
-
-something.listen_request(something.callback);
-
- -

Message Passing in Chromium

- -

Enviar dados estruturados

- -

The above mechanisms use element attributes and are thus only strings. You may want to transfer objects. Gecko prevents chrome to access custom object properties added by the content, because that can create security holes. A workaround is to treat the communication between webpage and chrome as a normal network protocol and use XML.

- -

With element attributes and E4X, this is fairly easy. You do need to convert your data to/from E4X objects, though. And your chrome needs to carefully check every value passed (you need to do that either way).

- -
var targetDoc = null;
-
-function onLoad() {
-  var iframe = document.getElementById("contentiframe");
-  targetDoc = iframe.contentDocument;
-  iframe.contentWindow.addEventListener("newStuff", receiveStuffFromPage, false);
-}
-
-function receiveStuffFromPage(event) {
-  var uc = getEventData(event); // uc = unchecked data in form of E4X XML
-  var stuff = {};
-  stuff.id = sanitize.integer(uc.@id);
-  stuff.name = sanitize.label(uc.@name);
-}
-
-function sendSomethingToPage (something) {
-  var somethingXML = <something/>; // |something| object as E4X XML
-  somethingXML.@id = something.id;
-  somethingXML.@weight = something.weight;
-  sendMsg("sendSomething", somethingXML);
-}
-
-/**
- * Send msgs from chrome to the page
- * @param type {String} the event type. The receiver needs to use that
- * when doing addEventListener(type, ...)
- * @param dataXML {E4X} the data or detail
- */
-function sendMsg(type, dataXML) {
-  var el = targetDoc.body;
-  el.setAttribute("eventDataToPage", dataXML ? dataXML.toString() : "");
-  var event = targetDoc.createEvent("Event")
-  event.initEvent(type, true, true);
-  el.dispatchEvent(event);
-}
-
-/**
- * Verifies that the event is indeed coming from our page
- * as expected, and returns the data for that event.
- * @returns {E4X} the (unchecked) detail data from the page.
- * You must check the data.
- * @see <https://developer.mozilla.org/en-US/docs/Code_snippets/
- * Interaction_between_privileged_and_non-privileged_pages#Security_notes>
- */
-function getEventData(event) {
-  if (event.target.ownerDocument != targetDoc)
-    throw "event from unexpected source";
-  return new XML(event.target.getAttribute("eventDataFromPage"));
-}
-
- -

Notas de segurança

- - - -

Recursos

- -

Fórum de Discussão de Mozillazine

- -

Comunicação entre HTML e a sua extensão

- -

Consulte também

- - - -
- - - -
diff --git a/files/pt-pt/archive/add-ons/trabalhar_com_multiprocessos_firefox/index.html b/files/pt-pt/archive/add-ons/trabalhar_com_multiprocessos_firefox/index.html deleted file mode 100644 index ce794196ea..0000000000 --- a/files/pt-pt/archive/add-ons/trabalhar_com_multiprocessos_firefox/index.html +++ /dev/null @@ -1,286 +0,0 @@ ---- -title: Trabalhar com multiprocessos do Firefox -slug: Archive/Add-ons/Trabalhar_com_multiprocessos_Firefox -translation_of: Archive/Add-ons/Working_with_multiprocess_Firefox ---- -
- - -
-

Add-ons using the techniques described in this document are considered a legacy technology in Firefox. Don't use these techniques to develop new add-ons. Use WebExtensions instead. If you maintain an add-on which uses the techniques described here, consider migrating it to use WebExtensions.

- -

Starting from Firefox 53, no new legacy add-ons will be accepted on addons.mozilla.org (AMO) for desktop Firefox and Firefox for Android.

- -

Starting from Firefox 57, only extensions developed using WebExtensions APIs will be supported on Desktop Firefox and Firefox for Android.

- -

Even before Firefox 57, changes coming up in the Firefox platform will break many legacy extensions. These changes include multiprocess Firefox (e10s), sandboxing, and multiple content processes. Legacy extensions that are affected by these changes should migrate to use WebExtensions APIs if they can. See the "Compatibility Milestones" document for more information.

- -

A wiki page containing resources, migration paths, office hours, and more, is available to help developers transition to the new technologies.

-
-
- -
-

This article explains how an add-on developer can check whether their add-on is compatible with multiprocess Firefox, and if it isn't, how to fix it.

-
- -

In older versions of Firefox, chrome code (including code inserted by extensions) and content run in the same operating system process. So extensions can access content directly:

- -
gBrowser.selectedBrowser.contentDocument.body.innerHTML = "replaced by chrome code";
- -

However, in multiprocess Firefox (also called Electrolysis or E10S), the extension's code will run in a different process from content, and this kind of direct access will no longer be possible.

- -

Checking whether you're affected

- -

As a rule, you won't be affected if:

- - - -

You will be affected if:

- - - -

For more details, see the article on Limitations of chrome scripts, which lists patterns that will no longer work in the chrome process.

- -

Testes

- -

In multiprocess Firefox, add-ons can run in two different modes: either with compatibility shims or without them. Add-ons are more likely to work with compatibility shims, but they will run much more slowly if they access web content often. Shims will be removed six months after multiprocess Firefox is released to users, so developers should avoid shims if possible.

- -

Testing if your add-on works with shims: Make sure you're running Firefox Nightly, in which multiprocess support is enabled by default. To verify that multiple process are being used, visit about:support and confirm that the "Multiprocess Windows" row contains "default: true". (If you see a different value, open Firefox preferences and check "Enable multi-process Nightly" in the General pane.) Now install your add-on and test that all features work. If you're testing an unsigned version of your extension, make sure you turn signing enforcement off.

- -

Testing if your add-on works without shims: As before, make sure you're running Firefox Nightly with multiple processes enabled. Next, add a new property to your extension's install.rdf named multiprocessCompatible, with a value of true. Now install your add-on and test that all features work.

- -

The rest of this document explains how to make broken add-ons work in multiprocess Firefox without using shims.

- -

Adaptação ao Múltiplos Processos

- -

If your add-on is not multiprocess-compatible, the best solution is to rewrite your add-on as a WebExtension. WebExtensions APIs are compatible with multiprocess Firefox. WebExtensions are the future of Firefox add-ons: other types of add-on, including XUL overlay add-ons, bootstrapped add-ons, and SDK add-ons, are now considered deprecated. From version 57, Firefox will no longer load such add-ons.

- - - -

Note that WebExtensions don't give you all the same features that legacy add-ons do. However we are open to extending the WebExtension APIs to support the needs of add-on developers, so if you have ideas, we'd love to hear them. You can reach the WebExtensions team on the dev-addons mailing list or #webextensions on IRC.

- -

If you can't port to WebExtensions yet, the Add-on SDK's high-level APIs are the next best choice. But note that this is not a future-proof solution, since SDK add-ons will not be supported from Firefox 57 onwards.

- -

The last option is to use the message manager to communicate with the content process. The message manager can be used from the Add-on SDK or from overlay or bootstrapped add-ons.

- - - -

Again, note that this is not a future-proof solution, since SDK, overlay, and bootstrapped add-ons will not be supported from Firefox 57 onwards.

- -

If you need help, please contact us in the #addons channel at irc.mozilla.org. We're here to help!

diff --git a/files/pt-pt/archive/apps/ferramentas_e_frameworks/index.html b/files/pt-pt/archive/apps/ferramentas_e_frameworks/index.html deleted file mode 100644 index 46face0a4a..0000000000 --- a/files/pt-pt/archive/apps/ferramentas_e_frameworks/index.html +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Ferramentas e frameworks -slug: Archive/Apps/Ferramentas_e_frameworks -tags: - - Aplicações - - Bibliotecas - - Ferramentas - - Firefox OS - - Frameworks - - Ritmos de Trabalho -translation_of: Archive/Apps/Tools_and_frameworks ---- -
-

This part of the App Center provides guides to using tools, frameworks and libraries to speed up Open Web App development — Brick, app templates, X-Tag, and Firefox OS Cordova support.

-
- -
-
-

Componentes e modelos

- -
-
Web components and Mozilla Brick
-
Mozilla Brick is a Web component library, based on the X-Tag library, which allows easy usage of custom elements.
-
Utilização de modelos de aplicaçãoes
-
To help you get going with app development as quickly as possible, there are some template apps you can use as a basis for your own apps. This guide provides information on those templates, how to get them, and how to work with them.
-
X-Tag
-
X-Tag and the Web components specification family provide a means for us to define custom elements that will dealt with as first class citizens by the browser, rather than as an inefficient afterthought. This guide explains how they work.
-
Elementos personalizados
-
This article describes some of the most useful custom elements available inside Mozilla's X-Tag library.
-
-
- -
-

Aplicações de plataforma cruzada e ferramentas de criação

- -
-
Cordova support for Firefox OS
-
This article provides a basic introduction to Apache Cordova and explains how to use it to generate an Open Web App for installation on Firefox OS.
-
Cordova Firefox OS plugin reference
-
Reference showing sample code and examples for the Cordova plugins that currently support Firefox OS.
-
-
-
- -

 

diff --git a/files/pt-pt/archive/apps/index.html b/files/pt-pt/archive/apps/index.html deleted file mode 100644 index 41b0a9c452..0000000000 --- a/files/pt-pt/archive/apps/index.html +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Apps -slug: Archive/Apps -tags: - - Apps - - Firefox OS - - NeedsTranslation - - TopicStub - - Web -translation_of: Archive/Apps ---- -

This page includes archived content for Apps, including obsolete web app content, Firefox OS app-related content, and so forth.

- -

{{SubpagesWithSummaries}}

diff --git a/files/pt-pt/archive/b2g_os/api/camera_api/index.html b/files/pt-pt/archive/b2g_os/api/camera_api/index.html deleted file mode 100644 index 435465c622..0000000000 --- a/files/pt-pt/archive/b2g_os/api/camera_api/index.html +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Camera API -slug: Archive/B2G_OS/API/Camera_API -tags: - - API - - Firefox OS - - Graphics - - NeedsTranslation - - Reference - - Référence(2) - - TopicStub - - WebAPI - - camera -translation_of: Archive/B2G_OS/API/Camera_API ---- -

- -

-

Non-standard
- This feature is not on a current W3C standards track, but it is supported on the Firefox OS platform. Although implementations may change in the future and it is not supported widely across browsers, it is suitable for use in code dedicated to Firefox OS apps.

-

- -

The Camera API allows applications to manage the camera of the device. It allows them to take photographs, record videos, and get information like the focus, the zoom, the white balance, the flash, … It is a priviledged API and can only be used by certified applications.

- -

This API was initially only available to certified applications, but is available to privileged apps on Firefox 2.0 onwards.

- -
-

Note: Except if you are implementing a replacement for the default Camera application, you shouldn't use this API. Instead, if you want to use the camera in your device, you should use the Web Activities API.

-
- -

See also

- - diff --git a/files/pt-pt/archive/b2g_os/api/camera_api/introducao/index.html b/files/pt-pt/archive/b2g_os/api/camera_api/introducao/index.html deleted file mode 100644 index d64e05da53..0000000000 --- a/files/pt-pt/archive/b2g_os/api/camera_api/introducao/index.html +++ /dev/null @@ -1,178 +0,0 @@ ---- -title: Introdução à API de Câmara -slug: Archive/B2G_OS/API/Camera_API/Introducao -tags: - - API da Web - - API de Câmara - - Intermediário - - Multimedia - - Precisa de Atualização - - Referencia DOM Gecko - - cámara -translation_of: Archive/B2G_OS/API/Camera_API/Introduction ---- -

 

- - - -

 

- -

Through the Camera API, it is possible to take pictures with your device's camera and upload them into the current web page. This is achieved through an input element with type="file" and an accept attribute to declare that it accepts images. The HTML looks like this:

- -
<input type="file" id="take-picture" accept="image/*">
-
- -

When users choose to activate this HTML element, they are presented with an option to choose a file, where the device's camera is one of the options. If they select the camera, it goes into picture taking mode. After the picture has been taken, the user is presented with a choice to accept or discard it. If accepted, it gets sent to the <input type="file"> element and its onchange event is triggered.

- -

Get a reference to the taken picture

- -

With the help of the File API you can then access the taken picture or chosen file:

- -
var takePicture = document.querySelector("#take-picture");
-takePicture.onchange = function (event) {
-    // Get a reference to the taken picture or chosen file
-    var files = event.target.files,
-        file;
-    if (files && files.length > 0) {
-        file = files[0];
-    }
-};
-
- -

Presenting the picture in the web page

- -

Once you have a reference to the taken picture (i.e., file), you can then use window.URL.createObjectURL() to create a URL referencing the picture and setting it as the src of an image:

- -
// Image reference
-var showPicture = document.querySelector("#show-picture");
-
-// Create ObjectURL
-var imgURL = window.URL.createObjectURL(file);
-
-// Set img src to ObjectURL
-showPicture.src = imgURL;
-
-// For performance reasons, revoke used ObjectURLs
-URL.revokeObjectURL(imgURL);
-
- -

If createObjectURL() isn't supported, an alternative is to fallback to FileReader:

- -
// Fallback if createObjectURL is not supported
-var fileReader = new FileReader();
-fileReader.onload = function (event) {
-    showPicture.src = event.target.result;
-};
-fileReader.readAsDataURL(file);
-
- -

Complete example

- -

If you want to see it in action, take a look at the complete working Camera API example.

- -

Here is the code used for that demo:

- -

HTML page

- -
<!DOCTYPE html>
-<html>
-    <head>
-        <meta charset="utf-8">
-        <title>Camera API</title>
-        <link rel="stylesheet" href="css/base.css" type="text/css" media="screen">
-    </head>
-
-    <body>
-
-        <div class="container">
-            <h1>Camera API</h1>
-
-            <section class="main-content">
-                <p>A demo of the Camera API, currently implemented in Firefox and Google Chrome on Android. Choose to take a picture with your device's camera and a preview will be shown through createObjectURL or a FileReader object (choosing local files supported too).</p>
-
-                <p>
-                    <input type="file" id="take-picture" accept="image/*">
-                </p>
-
-                <h2>Preview:</h2>
-                <p>
-                    <img src="about:blank" alt="" id="show-picture">
-                </p>
-
-                <p id="error"></p>
-
-            </section>
-
-            <p class="footer">All the code is available in the <a href="https://github.com/robnyman/robnyman.github.com/tree/master/camera-api">Camera API repository on GitHub</a>.</p>
-        </div>
-
-
-        <script src="js/base.js"></script>
-
-
-    </body>
-</html>
-
- -

JavaScript file

- -
(function () {
-    var takePicture = document.querySelector("#take-picture"),
-        showPicture = document.querySelector("#show-picture");
-
-    if (takePicture && showPicture) {
-        // Set events
-        takePicture.onchange = function (event) {
-            // Get a reference to the taken picture or chosen file
-            var files = event.target.files,
-                file;
-            if (files && files.length > 0) {
-                file = files[0];
-                try {
-                    // Create ObjectURL
-                    var imgURL = window.URL.createObjectURL(file);
-
-                    // Set img src to ObjectURL
-                    showPicture.src = imgURL;
-
-                    // Revoke ObjectURL
-                    URL.revokeObjectURL(imgURL);
-                }
-                catch (e) {
-                    try {
-                        // Fallback if createObjectURL is not supported
-                        var fileReader = new FileReader();
-                        fileReader.onload = function (event) {
-                            showPicture.src = event.target.result;
-                        };
-                        fileReader.readAsDataURL(file);
-                    }
-                    catch (e) {
-                        //
-                        var error = document.querySelector("#error");
-                        if (error) {
-                            error.innerHTML = "Neither createObjectURL or FileReader are supported";
-                        }
-                    }
-                }
-            }
-        };
-    }
-})();
-
diff --git a/files/pt-pt/archive/b2g_os/api/index.html b/files/pt-pt/archive/b2g_os/api/index.html deleted file mode 100644 index 706080ff54..0000000000 --- a/files/pt-pt/archive/b2g_os/api/index.html +++ /dev/null @@ -1,156 +0,0 @@ ---- -title: B2G OS APIs -slug: Archive/B2G_OS/API -tags: - - API - - B2G API - - NeedsTranslation - - TopicStub - - b2g os api's -translation_of: Archive/B2G_OS/API ---- -

List of B2G OS APIs 

- -

-A -B -C -D - - -F - - -H - - - - - - - - -M -N - - -P - - - - -S -T -U - - -W - - - - - - - -

diff --git a/files/pt-pt/archive/b2g_os/firefox_os_apps/building_apps_for_firefox_os/index.html b/files/pt-pt/archive/b2g_os/firefox_os_apps/building_apps_for_firefox_os/index.html deleted file mode 100644 index ddb6c550ff..0000000000 --- a/files/pt-pt/archive/b2g_os/firefox_os_apps/building_apps_for_firefox_os/index.html +++ /dev/null @@ -1,361 +0,0 @@ ---- -title: Building apps for Firefox OS -slug: Archive/B2G_OS/Firefox_OS_apps/Building_apps_for_Firefox_OS -tags: - - Firefox OS - - Installation - - Layout - - Manifest - - NeedsTranslation - - TopicStub - - distribution - - packaging -translation_of: Archive/B2G_OS/Firefox_OS_apps/Building_apps_for_Firefox_OS ---- -

- -
-

Firefox OS apps are essentially no different to standard websites or web apps. They are built using standard open web technologies — HTML, CSS, JavaScript, etc. — and can be accessed using a web browser. The main differences lie in their ability to be installed on devices and work offline, access to advanced APIs that allow interaction with device features such as camera, gyroscope and address book, and the existence of a solid developer ecosystem — including a Marketplace for distribution of free and paid apps. Generally, they provide users with an "app experience", while still being based on open, cross platform technologies.

-
- -

Firefox OS apps have a low barrier for entry, especially for existing web developers and mobile developers; they are also a lot more portable across platforms than native equivalents, and not locked into walled gardens. As we've already mentioned Firefox OS apps are based on web technologies — HTML, CSS, and JavaScript — so if you've written a web page you already know the basics. Even if you don't have the basics you'll be able to easily follow this guide, but you may want to check out our list of Beginner's tutorials to learn more about developing with open web technologies.

- -

This section of MDN provides a detailed reference on web app development topics specific to creating apps that are installable on Firefox OS (and other Firefox-supported platforms like Android), including app manifests, writing install functionality, permissions for using device APIs, and more. It is targeted towards experienced developers that are just looking to create or port an existing app to Firefox OS.

- -
-

Note: There is also a very useful screencast series available, if you prefer watching videos — App Basics for Firefox OS.

-
- -
-

Note: If you are a complete beginner to web apps (perhaps you just know a bit of HTML/CSS/JS) and want a very simple guide to building up an app, check out our Firefox OS app beginners tutorial.

-
- -

Firefox OS

- -

Firefox OS (also referred to by its codename Boot to Gecko — or B2G) is Mozilla's open source mobile operating system. It's based on a Linux kernel, which boots into a Gecko-based runtime that lets users install and run open web apps, Gecko being the rendering engine that the Firefox browser uses to render and display web content.

- -

Firefox OS comes with Gaia, which forms the entire UI layer of Firefox OS and the default suite of apps that handle the fundamental functions of the phone such as settings, calls, SMS, taking and storing photos, etc.

- -

Mozilla's open web apps are installable on Firefox OS, and other Firefox-supported platforms via Mozilla's web run time technology. For more details, see Open web apps for Android, and Open web apps for Desktop.) In future, the technologies should be standardized and adopted across a wider range of platforms.

- -

Installable app workflow

- -

An installable open web app is very similar to a normal web app or web site — it is built using familiar web technologies like HTML, CSS and JavaScript. The difference is in the additional features the Firefox (OS) platform has available. The following diagram illustrates how those features work together.

- -

- -
    -
  1. Start with a fairly standard web application, built using your favourite toolchain.
    2. -
  2. Identify this as an installable web app by adding a manifest.webapp file to the web app root directory. This defines a number of things about the app such as its name, icons, localization information, and probably most importantly the permissions the app needs to access device APIs such as Camera, Device Storage, Bluetooth and SMS.
    3. -
  3. Create any functionality you require that makes use of special device APIs.
    4. -
  4. Create the assets your app needs, such as the icons.
    5. -
  5. Package and distribute your app. This can be done in a variety of ways, from simple self-published hosted apps (in which case you'd have to write your own install functionality), to packaged apps distributed via the Firefox Marketplace (which handles the install functionality for you.)
    6. -
- -

Recommendations

- -

This section provides recommendations and best practices for creating installable open web apps.

- -

Web app manifest files

- -

Your app's manifest.webapp file should be placed in the root of your app directory, and contain a simple JSON structure, as explained in detail in our App Manifest reference. A simple App Manifest JSON looks like so:

- -
{
-  "name": "My App",
-  "description": "My elevator pitch goes here",
-  "launch_path": "/index.html",
-  "icons": {
-    "512": "/img/icon-512.png",
-    "128": "/img/icon-128.png"
-  },
-  "developer": {
-    "name": "Your name or organization",
-    "url": "http://your-homepage-here.org"
-  },
-  "default_locale": "en"
-}
- -

For simple apps, this is all you'll need, but you may also need other fields, as discussed in appropriate places below.

- -

Functionality, Device APIs, and permissions

- -

One of the main strengths of the Firefox OS platform is the provision of new Web APIs to access key device services like the contacts, and hardware like NFC, Bluetooth and SMS. There are many examples of the different new APIs available along with examples throughout our App Center Build section, but in this section we'll give you some specific pointers towards tasks you might want to accomplish with them. Common task categories include:

- - - -

Different APIs have different levels of security, with some APIs being limited in who can access them. This makes sense — it would be really insecure to just let any app have access to say, a device's SMS and dialer functionality. The different levels are as follows:

- - - -

To request permission to use a restricted API, you have to include a permissions field in your manifest file, and set the type field to privileged in the case of privileged APIs. These fields will look something like this:

- -
"type" : "privileged",
-"permissions": {
-  "contacts": {
-    "description": "Required for autocompletion in the share screen",
-    "access": "readcreate"
-    },
-  "alarms": {
-    "description": "Required to schedule notifications"
-  }
-}
- -
-

Note: You can find out exactly what permissions (if any) each API requires by looking at our App permissions reference; this reference also lists which version of Firefox OS supports each API. To find out what API features are new as of each version of Firefox OS, consult our Firefox OS developer release notes.

-
- -

Using Web activities also requires that you specify their type and required data in the activities field, for example:

- -
"activities": {
-  "share": {
-    "filters": {
-      "type": [ "image/png", "image/gif" ]
-    },
-    "href": "foo.html",
-    "disposition": "window",
-    "returnValue": true
-  }
-}
- -

Lastly, some APIs such as the Alarm and Notification APIs also require you to specify a messages field, which details what kind of system messages are to be captured by the app, and what page(s) will handle them:

- -
"messages": [
-    { "alarm": "/index.html" },
-    { "notification": "/index.html" }
-  ]
- -

Icons and other design best practices

- -

The best practices you would use for creating a Firefox OS app are pretty much the same as those you would use for creating any standard web app, in terms of both coding and design.

- -
    -
  1. You should use responsive design techniques to make sure your app layout will work well on a variety of screen sizes, especially media queries and viewport. Because many devices have high resolution screens these days, this should include use of resolution media queries to optimize for different resolutions.
    2. -
  2. You should take advantage of the building blocks and design patterns we've made available (see our app Design section.)
    3. -
  3. You should also make sure to optimize your code as much as possible so it is more likely to work on low-memory devices, which many Firefox OS devices are (see our Performance topic).
    4. -
  4. For the visual design of Firefox apps, you are free to follow your own path, but you could certainly get some useful pointers from our Firefox OS style guide.
    5. -
  5. For your app icons, you should make sure to include at least a 512x512 icon and a 128x128 icon. Read Icon implementation for Apps for more information.
    6. -
- -

App packaging, installation and distribution

- -

When an App is ready to be distributed, you have a few options of how to publish them:

- - - -
-

Note: Self-published apps don't have the ability to access privileged APIs, for security reasons.

-
- -
-

Note: Another common cause of failure in app installation is incorrect paths in manifests and install code. These paths should be relative to the origin of the server location. So for example, if your example's root is at http://www.mysite.com/myapp/, and your icon is at http://www.mysite.com/myapp/manifest.webapp, the install path would be /myapp/manifest.webapp, not /manifest.webapp.

-
- -
-

Note: Installable open web apps used to have a "single app per origin" security policy, but this was lifted as of Firefox 34/Firefox OS 2.1 (read this FAQ entry for more information). If you still need to support older versions, consider hosting your apps at separate origins; one strategy is to create different subdomains for your apps.

-
- -

Multi-locale apps

- -

You can create multi-locale apps quite easily. This is done by:

- -
    -
  1. Adding special data-l10n-id attributes to each HTML element that requires localization, the value of which should be an identifier for that string. For example:
    2. -
  2. <h1 data-l10n-id="app-title">My app</h1>.
    3. -
  3. Including the l10n.js library in your page using a regular <script> element.
    4. -
  4. Creating a locales folder inside your app directory containing a folder for each separate locale, then placing an app.properties file inside each one containing that language's translations, each one on a new line. For example app-title = Mon application for French.
    5. -
  5. Creating a locales.ini file inside the locales folder, which specifies the default locale and the path to each app.properties file. This will look like so: - 
    @import url(en/app.properties)
-
-[es]
-@import url(fr/app.properties)
    -
    6. -
  6. Referencing locales.ini from your HTML file using a <link> element, like so: - 
    <link rel="resource" type="application/l10n" href="locales/locales.ini" />
    -
    7. -
  7. Updating your manifest file to include a default locale and locales field containing information about your supported locales: - 
    "default_locale": "en",
-"locales": {
-  "fr": {
-    "name" : "Mon application",
-    "description" : "Mon application description"
-  }
-}
    -
    8. -
- -

For more details, begin with our Getting started with app localization article, then check out the rest of our articles about app localization.

- -

Debugging apps

- -

Mozilla provides a number of tools to help you test Firefox OS apps.

- -

Testing on Firefox desktop

- -

The quickest way to test your app's basic functionality is to simply load it in Firefox desktop (open the index.html file in the browser) — this supports most of the features you'll be using to develop your app (with the exception of some of the device APIs.) From here you can use the standard Firefox Toolbox to debug your code, and the Responsive Design View to test responsive/mobile layouts.

- -

Testing in the Firefox OS simulator

- -

You can also test the app in a Firefox OS simulator via our WebIDE tool. This will give you a more realistic idea of how it will look on a real device.

- -
-

Note: Our new WebIDE tool is currently only available in Firefox Nightly, but will be rolled out across all versions soon. It does everything App Manager does and more, including in-app code editing, creation of new apps, and tools like the Monitor, which enables to track performance across an app's lifespan.

-
- -

Testing on a Firefox OS device

- -

Some device APIs — such as the vibration API — can't be tested successfully on a simulator. To fully test this you'll need to get hold of a real Firefox OS device. If you've got one, you can connect it to your computer and install apps contained on your local drive straight onto it via the App Manager/WebIDE.

- -

Logcat

- -

The Android adb logcat tool is very useful for getting debugging output from a Firefox OS device, if you are comfortable with command line tools. For example, you can get info on dying apps using the following:

- -
adb logcat GeckoConsole:* *:F | grep -vE "parsing value|Unknown property|declaration|invalid source| but found |pseudo-"
- -

Supporting cross-Firefox OS versions

- -

Note that when developing apps for Firefox OS, you need to bear in mind what platform versions will be available on the devices your customers will have (see our available phones table for a list.) Remember that it is not as simple to update phone platform software as it is desktop software — users tend to be at the mercy of the network providers. You therefore need to develop apps to support these versions. As an example, multiline Flexbox doesn't work on Firefox OS versions below 1.3, so you may need to use a simpler layout method or provide a fallback for older versions.

- -

This issue should go away soon, as more consumer Firefox OS devices appear, equipped with newer versions of Firefox OS out of the box.

- -
-

The current baseline platform we recommended developing for is Firefox OS 1.1.

-
- -
-

Note: MDN's web platform reference pages include browser/platform support information, plus you can find support information for more App-specific technologies on our Apps API Reference.

-

- -

Examples

- -

You can find many examples throughout the App Center Build section; there are also some examples in our Reference apps section.

- -

Tutorials

- -

Installable app basics

- -
-
Firefox OS app beginners tutorial
-
A complete beginner's guide to creating a Firefox OS app.
-
Packaged apps
-
A packaged app is an Open Web App that has all of its resources contained in a zip file, instead of having its resources on a Web server. In here you'll learn all you need to know about packaged apps.
-
Hosted apps
-
A hosted app is an Open Web App that has all of its resources (HTML, CSS, JavaScript, app manifest and so on) stored on a Web server. This article will tell you all you need to know about hosted apps.
-
Packaged or hosted?
-
Should you make your app hosted or packaged? This article will help you decide.
-
Self-publishing apps
-
This guide explains how to write the code that controls publishing apps, should you wish to write it yourself rather than use the Firefox Marketplace.
-
- -

Advanced topics

- -
-
Icon implementation for apps
-
Implementation specifics for implementing Firefox app icons, including different sizes needed.
-
Updating apps
-
How app updates are handled.
-
- -
-

Reference

- -
-
Firefox OS app tools
-
This page provides a list of useful tools, libraries and examples that are useful for Firefox OS app developers, whether you want an code template to copy, or need help with adding a specific feature to your Firefox OS app.
-
App manifest
-
A detailed guide to Open Web App manifest files, and the different options they can contain.
-
App permissions
-
Access to device APIs is key to creating many useful apps. Here is what's available and how to access them. -
-

Note: you can use the Firefox OS App Generator to automatically generate and install FxOS apps with particular permissions, message-listeners, types, etc.

-
-
-
Firefox OS API support table
-
A list of the different APIs available to Firefox OS, and what support is available for them.
-
App installation and management APIs
-
A reference for the installation and management APIs that control installation and other functions of installable Open Web Apps.
-
Platform-specific details of app installation
-
There are some differences in how apps are installed across the various platforms that support Open Web Apps; this article will help you to understand them.
-
CSP for open web apps
-
Unlike traditional web sites, privileged and certified apps enforce a CSP (content security policy) by default. This may cause quite a bit of existing code to break while porting and cause a significant amount of confusion if developers are unaware that the CSP exists. This article explains what the restrictions imposed by the open web app CSP are.
-
- -

FAQ

- -
-
App manifests FAQ
-
Manifest frequently asked questions.
-
-
- -
-
 
-
diff --git a/files/pt-pt/archive/b2g_os/firefox_os_apps/building_apps_for_firefox_os/manifesto/index.html b/files/pt-pt/archive/b2g_os/firefox_os_apps/building_apps_for_firefox_os/manifesto/index.html deleted file mode 100644 index fc1eb924f0..0000000000 --- a/files/pt-pt/archive/b2g_os/firefox_os_apps/building_apps_for_firefox_os/manifesto/index.html +++ /dev/null @@ -1,926 +0,0 @@ ---- -title: Manisfesto da Aplicação -slug: Archive/B2G_OS/Firefox_OS_apps/Building_apps_for_Firefox_OS/Manifesto -tags: - - Aplicações - - B2G - - Firefox OS - - Manifesto - - Marketplace - - Movel - - Não Padrão - - OS -translation_of: Archive/B2G_OS/Firefox_OS_apps/Building_apps_for_Firefox_OS/Manifest ---- -

{{ non-standard_header() }}

- -
-

Importante: este documento refere-se ao formato de manifesto do sistema operativo Firefox, e não às  especificações do manifesto 3C, concebido para aplicações da Web progressivas de vários navegadores. 

-
- -
-

The Firefox OS app manifest provides information about an app (such as name, author, icon, and description) in a simple document usable by both users and app stores. Most importantly, it contains a list of Web APIs that your app needs. This allows users to make informed decisions about apps before installing them. It is one of the key things that distinguishes a Firefox OS App from a website.

-
- -
-

Nota: Browsers that handle manifests and allow installation of Firefox OS apps incorporate a Web runtime. This includes Firefox OS, and newer versions of Firefox for Android and Firefox for desktop.

-
- -
-

Nota: You can find answers to common questions about app manifests in our App Manifest FAQ.

-
- -

Criar um manisfesto da aplicação

- -

This section details the critical details you need to create and use an app manifest.

- -

Convenções: nome de ficheiro, localização, e formato

- - - -

Manipulação do caminho

- - - -

Requisitos para submeter para Firefox Marketplace

- -

If you want to publish your app to the Firefox Marketplace, your app manifest must contain the following fields:

- - - -

Requisitos para as Aplicações da Web Abertas

- -

If you're building a generic hosted app that will not be published in the Firefox Marketplace, your app manifest must contain the following fields below:

- - - -
-

Note: To self-publish an app from a page that you control, you have to provide a mechanism for users to trigger installation of the app. This is usually done by calling navigator.Apps.install() when a button is clicked in the case of a hosted app, or navigator.Apps.installPackage() in the case of a packaged app.

-
- -

Validação do manifesto da aplicação

- -

If you're submitting to the Firefox Marketplace, your app manifest must pass Marketplace Validation.

- -

Try our App Validator, which will help you identify any errors. Or you can use this API to validate your app manifest.

- -

Atualização de manifestos

- -

For information on updating apps, see Updating apps.

- -

Exemplo de manifesto

- -

The following is a minimal manifest. You can copy it into a text file and replace the values with your own information.

- -
{
-  "name": "My App",
-  "description": "My elevator pitch goes here",
-  "launch_path": "/index.html",
-  "icons": {
-    "512": "/img/icon-512.png",
-    "128": "/img/icon-128.png"
-  },
-  "developer": {
-    "name": "Your name or organization",
-    "url": "http://your-homepage-here.org"
-  },
-  "default_locale": "en",
-  "chrome": { "navigation": true }
-}
- -

Campos do manifesto da aplicação requeridos

- -

The fields in your manifest can be in any order. Fields in the manifest other than the ones listed below will be ignored.

- -

name

- -
-

Nota: Required for all app manifests.

-
- -

A human-readable name for the app. Maximum length is 128 characters.

- -

If you change the name of your app after distribution, the name will not be updated for any existing installations.

- -
"name": "The Open Web!"
- -

description

- -
-

Nota: Required for all app manifests.

-
- -

A human-readable description for the app. Maximum length is 1024 characters.

- -
"description": "Exciting Open Web App!"
- -

launch_path

- -
-

Nota: Required for all app manifests.

-
- -

The path within the app's origin that is loaded when the app starts.

- -

Specifies the starting point of the content local to the zip file containing the packaged app. For example, if the launch_path is /mywebapp/index.html, the app will open the file at /mywebapp/index.html when the app is launched.

- -
Dicas: - - -
- -
"launch_path": "/index.html"
- -

icons

- -
-

Nota: 1 icon sized 128×128 required for all app manifests. 1 icon sized 512×512 recommended for all app manifests.

-
- -

A map of icon sizes to URIs of the icons.

- -

Remember that internal paths to icons must be absolute from the app's origin, while paths to externally hosted icons must be fully qualified.

- -

Icons must be square, and in .png format. Icons should not have solid backgrounds that extend to all four corners of the icon.

- -
-
Cuidado: if you're submitting to the Firefox Marketplace, your icons must also follow the Firefox Marketplace app icon guidelines.
-
- -

Required icon sizes

- -
-
128×128
-
For display on the Firefox Marketplace and devices.
-
- - - -
-
512×512
-
From Firefox 2.0 onwards, larger icons are needed for crisp display on all the different possible combinations of Phone and tablet screen sizes, screen resolutions, and 3 and 4-column layouts. We accept a 512×512 icon, which is then scaled for all the different uses across devices. This size is also useful for display on other platforms apps can be installed across, such as Android.
-
- -

Other icon sizes that might be useful

- -
-
60×60
-
For the exact on-device icon size on older Firefox OS versions.
-
16×16, 32×32, 48×48, 64×64, 90×90, 128×128 and 256×256
-
These icon sizes are used on various other platforms your app can be installed on, such as Windows, OS X and Android.
-
- -
"icons": {
-  "128": "/img/icon-1.png",
-  "512": "/img/icon-2.jpg"
-}
- -
-

Nota: For a thorough explanation of how we decided on the 512×512 icon size, read our Icon implementation guide.

-
- -

developer

- -
-

Nota: Only the name is required for all app manifests.

-
- - - -
"developer": {
-    "name": "The Open Web!",
-    "url": "http://www.mywebapp.com"
-}
- -

default_locale

- -
-

Nota: If {{anch("locales")}} is defined, default_locale is required for your app manifest.

-
- -

A language tag (RFC 4646) that defines the language you used in the field values of your app manifest.

- -

Although default_locale is not required for apps that don't have locales, it is recommended that you include it. If you do not define a default_locale, the Firefox Marketplace will guess your app's language.

- -

For example, if your app uses English, it's default_locale would be:

- -
"default_locale": "en"
- -

type

- -
-

Nota: If your app is privileged or internal (certified), type is required for your app manifest.

-
- -

The app's type, which defines its level of access to sensitive device WebAPIs. If you do not define type, it will default to web as the type.

- - - -
-

Nota: For more information on app types, see Packaged apps.

-
- -
"type": "certified"
- -

Optional app manifest fields

- -

The following fields are optional.

- -

activities

- -

A set of Web Activities that your app supports (full list). It's structured like so:

- - - -

For example, here's an entry with one activity named share.

- -
"activities": {
-  "share": {
-    "filters": {
-      "type": [ "image/png", "image/gif" ]
-    },
-    "href": "foo.html",
-    "disposition": "window",
-    "returnValue": true
-  }
-}
- -

The object for the share activity in the example has filters, href, disposition and returnValue properties. These are described in Activity handler description.

- -

appcache_path

- -

The absolute path to the application cache (AppCache) manifest. When a Firefox OS app is installed, the AppCache manifest will be fetched and parsed, and its static assets under the CACHE header will be cached.

- -
-

Nota: Packaged apps cache assets on the device when installed. You don't need to set an AppCache for packaged apps.

-
- -
-

Nota: AppCache is a flawed technology, and will soon be replaced by the much more effective Service Workers.

-
- -
"appcache_path": "/cache.manifest"
- -

chrome

- -

A set of navigation controls on the bottom of the screen that consists of Back, Forward, Reload and Favorite.

- -

chrome navigation

- -
-

Note: We'd recommend designing a back button for your app interface, instead of relying on this option.

-
- -
"chrome": { "navigation": true }
- -

csp

- -
-

Note: Optional; applies to all packaged apps installed on Firefox OS, Firefox Desktop or Firefox for Android.

-
- -

This field can be used to define a Content Security Policy (CSP) that is applied to all pages in the app. The policies you can add to a CSP are listed in CSP policy directives, and for an app you'll need to include them in a line like so:

- -
"csp" : "default-src *; script-src 'self'; object-src 'none'; style-src 'self' 'unsafe-inline'"
- -

The default policies applied to Firefox OS privileged and internal/certified apps are as follows:

- -
-
Privileged CSP
-
- 
default-src *; script-src 'self'; object-src 'none'; style-src 'self' 'unsafe-inline'
-
-
Certified/Internal CSP
-
- 
default-src *; script-src 'self'; object-src 'none'; style-src 'self'
-
-
- -

These defaults can’t be overridden, only added to, i.e. the CSP policy in the manifest can only make the actual CSP applied more restrictive in the case of privileged/internal apps.

- -
-

Note: See the Apps CSP page for more details on the CSP restrictions particular to apps.

-
- -

datastores-owned

- -
-

Note: Applies only to internal/certified apps to be installed on Firefox OS.

-
- -

When making use of the Data Store API, the app that owns the data store MUST include the datastores-owned field in its manifest to claim ownership, for example:

- -
"datastores-owned": {
-  "myData": {
-    "access": "readwrite",
-    "description": "my data store"
-  }
-}
- -

You can include multiple properties to represent different data stores, and each one can use an access of readonly/readwrite to specify whether the data store can be read/modified by other applications. A description is also included to describe the purpose of the data store.

- -

datastores-access

- -
-

Note: Applies only to internal/certified apps to be installed on Firefox OS.

-
- -

When making use of the Data Store API, any non-owner app that wants access to the the data store MUST include the datastores-access field in its manifest, for example:

- -
"datastores-access": {
-  "myData": {
-    "access": "readwrite",
-    "description": "Read and modify my data store"
-  }
-}
- -

Without this field being specified, the default behaviour is "no access". Again, multiple properties can be included if you want to access multiple data stores, and an access of readonly or readwrite can be set to declare what access type is needed by the app.

- -

fullscreen

- -

A control that tells the runtime whether or not to launch the app in full-screen mode.

- -

Since most apps run in fullscreen, we recommend setting this to true.

- -
"fullscreen": "true"
- -

inputs

- -

Specifies supported layouts for the keyboard app. Each layout is described using a key-value pair, where the key represents the layout name (which will be displayed in the Settings app), and the value describes detailed information about the layout, including launch path of the layout and supported input types.

- -

The allowed values in the types field is a subset of the {{htmlelement("input")}} element {{htmlattrxref("type","input")}} attribute values. Currently allowed values are text, search, tel, number, url, email.

- -

An example follows:

- -
"inputs": {
-   "en": {
-     "launch_path": "/index.html#en",
-     "name": "English",
-     "description": "English layout",
-     "types": ["url", "text"],
-     "locales": {
-       "en-US": {
-         "name": "English",
-         "description": "English layout"
-       },
-       "zh-TW": {
-         "name": "英文",
-         "description": "英文鍵盤"
-       }
-     }
-   },
-   "en-Dvorak": {
-     "launch_path": "/index.html#en-Dvorak",
-     "name": "English (Dvorak)",
-     "description": "Dvorak layout",
-     "types": ["url", "text"]
-   },
-   "es": {
-     "launch_path": "/index.html#es",
-     "name": "Spanish",
-     "description": "Spanish layout",
-     "types": ["url", "text"]
-   },
-
-  ...
-
-}
- -

installs_allowed_from

- -

One (or more) URLs to the domains where your app can be installed from.

- -

This field is intended for apps that end-users can purchase. The field identifies the app stores with whom you have a commercial relationship. If left empty, your app can be installed from anywhere.

- -
-
Caution: Do not put a trailing slash at the end of URLs, because the installation will fail.
-
- -

For example, if your app can be installed from the Firefox Marketplace, installs_allowed_from will look like this:

- -
"installs_allowed_from": [
-  "https://marketplace.firefox.com"
-]
- -

Note: The array ["*"] would mean that installations of this app are allowed from any site. This is the default. Note that an empty array [] would disallow installation from any site, including your own.

- -

locales

- -

A map of one or more language-specific overrides of the field values in your app manifest.

- -

Each locales entry contains a list of the app manifest fields you want to override for a specific language. Keys for locales use the same language tags as for default_locale (RFC 4646).

- -
-
-

Caution:

- -
    -
  • -

    If you are defining locales, remember to also define default_locale.

    -
    • -
  • -

    Do not define the value of default_locale again in locales.

    -
    • -
  • -

    You cannot override these fields: default_locale, locales, and installs_allowed_from.

    -
    • -
-
-
- -

For example, your apps' default language is English, so its default_locale would be en. But you want to override the name and description for your Italian and German users with translated name and description. So your locales entries would look like this:

- -
"locales": {
-  "it": {
-    "name": "L'Open Web",
-    "description": "Eccitante azione di sviluppo web open!"
-  },
-  "de": {
-    "name": "Der Open Web",
-    "description": "Spannende offene Web-Entwicklung-Action!"
-  }
-}
- -

messages

- -
-

Note: Applies only to apps to be installed on Firefox OS.

-
- -

The system messages you allow the app to capture, and the pages in your app that will display when those messages occur.

- -

Below is an example from the Firefox OS Dialer app. Every time an incoming call comes in (system message: telephony-new-call), the device shows the dialer's keypad (URL: /dialer/index.html#keyboard-view).

- -
"messages": [
-  { "alarm": "/index.html" }
-  { "notification": "/index.html" }
-  { "telephony-new-call": "/dialer/index.html#keyboard-view" }
-]
- -

orientation

- -
-

Note: Applies only to apps using Android or Firefox OS.

-
- -

The positioning at which the application will stay locked.

- -

Illustration of possible values:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
valueApp will stay locked to
portrait-primaryPhone upright in portrait orientation
portrait-secondaryPhone upsidedown in portrait orientation
portrait
- If you declare this, there's no need to write
- -primary or -secondary		Phone upright in portrait orientationPhone upsidedown in portrait orientation
landscape-primaryPhone lying on its left hand side in landscape orientation
landscape-secondaryPhone lying on its right hand side in landscape orientation
landscape
- If you declare this, there's no need to write
- -primary or -secondary		 -

Phone lying on its left hand side in landscape orientation

- -

Phone lying on its right hand side in landscape orientation

-
- -
"orientation": [ "landscape-primary" ]
- -

origin

- -
-

Note: Applies only to privileged or internal (certified) packaged apps.

-
- -

Packaged apps have a special internal protocol of app://UUID where UUID is a string unique to each device the app is installed on. UUID is not easily accessible at this time. The origin field allows you to replace this UUID value with a single domain name that will be used by each installed app.

- -
-

Remember: domain name must start with app://, and you must be the owner of the domain name you specify.

-
- -
"origin": "app://mywebapp.com"
- -

permissions

- -

The user permissions for sensitive device APIs that your app needs, for example, access to the user's Contacts. See a full list of WebAPI permissions/features.

- -

Each permission requires:

- - - -

For example, here's a manifest entry for an app that needs permission to use the device's contacts and alarms.

- -
"permissions": {
-  "contacts": {
-    "description": "Required for autocompletion in the share screen",
-    "access": "readcreate"
-    },
-  "alarms": {
-    "description": "Required to schedule notifications"
-  }
-}
- -
-

Note: If an app tries to use one of these APIs without a corresponding entry in the permissions field, it will fail to run.

-
- -

There are many APIs, some of whom require the app type to be privileged or internal (certified). For example, systemXHR requires the type field to be set to privileged in order to work:

- -
  "type": "privileged",
-  "permissions": {
-    "systemXHR": {
-      "description": "Required to download podcasts."
-    }
-  }
-
- -

precompile

- -
-

Note: Applies only to packaged apps.

-
- -

The path to JavaScript files containing asm.js code that you want compiled at install time.

- -

Compilation at install time makes the installation process longer, but reduces the time it takes to start up an app.

- -
"precompile": [
-  "game.js",
-  "database.js"
-]
- -

redirects

- -
-

Note: Applies only to privileged/internal (certified) apps that are to be installed on Firefox OS.

-
- -

The internal URLs your app uses to handle external processes.

- -

For example, your app might use Facebook OAuth authentication to get a user's contacts. When the authentication is finished, the server usually redirects back to a URL that you control. Because packaged apps are not hosted on the web, a packaged app does not have a valid URL that can be redirected to. So you use the redirects field to redirect an external URL to an internal app URL.

- -

In the scenario above, the redirects field will look like this:

- -
"redirects": [
-  {"from": "http://facebook.com/authentication/success.html",
-    "to": "/app/main_interface.html"}
-]
- -

The scope of the redirects declared by redirects is limited to the app that declares them. That makes it so that several apps can redirect the same public URL to their own local resources, and it also prevents global hijacking of public URLs by an application.

- -

role

- -

The role field is mainly for internal use by the Gaia engineering team; it allows you to specify how an app should be used by B2G, its role in the system. For example, is it a keyboard, or a homescreen replacement?

- -
"role": "system",
- -

Options include:

- - - -

version

- -
-

Note: Required for packaged app manifests.

-
- -

A string that represents the version of the app, shown in Marketplace and when installing the app.

- -

In packaged apps the version is used to determine distinguish if an update needs to be installed. The field needs to be incremented when uploading an update of your app to Marketplace.

- -

In hosted apps this field is for your convenience; it's not used by the runtime, so version can be any value. Defining it is recommended.

- -
"version": "2.1"
- -

Serving manifests

- -

The app manifest must be served from the same origin that the app is served from.

- -

The manifest should be stored with a file extension of .webapp. App manifests must be served with a Content-Type header of application/x-web-app-manifest+json. This is currently not enforced by Firefox but is enforced by the Firefox Marketplace. Firefox OS only checks this if the origin of the page where the user triggers the install is different from the origin of the app itself. You don't need other headers such as Content-Security-Policy and X-UA-Compatible.

- -

Manifests can be served over SSL to mitigate certain classes of attacks. You can also serve the manifest with HTTP compression. The manifest should not be cached.

- -

The manifest must be in UTF-8 encoding in order for the app to be submitted to Firefox Marketplace. It is recommended that you omit the byte order mark (BOM). Other encodings can be specified with a charset parameter on the Content-Type header (i.e. Content-Type: application/x-web-app-manifest+json; charset=ISO-8859-4), although this will not be respected by the Marketplace.

- -

User Agents when possible should meaningfully message the site identity and TLS status when prompting a user to install an app.

- -

Serving from Apache

- -

In your .htaccess file, you must add the following:

- -
AddType application/x-web-app-manifest+json .webapp
- -

If adding in an .htaccess file didn't work for you, you can add the same line in your Apache configuration file. Your configuration file might be named httpd.conf or 000-default.conf, depending upon your operating system and configuration.

- -

Serving from Apache, using a PHP snippet

- -

It may be that on a shared hosting plan, changing the Content-Type header with a .htaccess file is not working because this is globally disallowed. Meanwhile, if this hosting supports PHP, using the following short script can serve the purpose:

- -
<?php
-// Serving the manifest file 'manifest.webapp' with the appropriate header
-header('Content-type: application/x-web-app-manifest+json');
-readfile('manifest.webapp');
-?>
- -

This code should be placed in the same directory as the manifest, and named manifest.webapp.php for example.

- -

Serving from Tomcat

- -

In your web.xml file, you need to set the mime mapping

- -
<mime-mapping>
-    <extension>webapp</extension>
-    <mime-type>application/x-web-app-manifest+json</mime-type>
-</mime-mapping>
- -

 

- -

Serving from IIS

- -

You need to edit your web.config file. This will probably be located in the web site's root directory.

- -

You will have to add a new entry in the <configuration> <system.webServer> <staticContent> section.

- -
<remove fileExtension=".webapp" />
-<mimeMap fileExtension=".webapp" mimeType="application/x-web-app-manifest+json; charset=UTF-8" />
- -
-

Note: For more information, read Adding Static Content MIME Mappings <mimeMap>.

-
- -

Serving from nginx

- -

You need to edit your mime.types file in the conf directory. This will probably be located in either /etc/nginx/ or /opt/nginx/.

- -

You should have something similar to the following. Add the last line seen here:

- -
types {
-  text/html   html htm shtml;
-  text/css    css;
-  text/xml    xml;
-  application/x-web-app-manifest+json   webapp;
-}
- -

Serving from GitHub

- -

If you serve your manifest file from GitHub Pages, GitHub will serve it with the Content-Type header of application/x-web-app-manifest+json.

- -

Serving from Python

- -

If you have Python installed, you can easily run a server from the local directory using the following:

- -
import SimpleHTTPServer
-import SocketServer
-SimpleHTTPServer.SimpleHTTPRequestHandler.extensions_map['.webapp'] = 'application/x-web-app-manifest+json'
-httpd = SocketServer.TCPServer(("", 3000), SimpleHTTPServer.SimpleHTTPRequestHandler)
-httpd.serve_forever()
-
- -

Serving from Flask (Python)

- -

If you have flask project you don't need create file manifest.webapp but you can use route() decorator to tell Flask what URL should trigger our function. First you need import Response from Flask

- -
from flask import Response
- -

in your flask application, add the route() decorator, as indicated below:

- -
@app.route('/manifest.webapp')
-def manifest():
-        data = json.dumps({
-            "name": "Flask Application",
-            "version": "1.0",
-            "description": "Example of manifest.webapp",
-            "launch_path": "/",
-            "icons": {
-                    "256": "/img/256.png",
-                    "128": "/img/128.png",
-                    "120": "/img/120.png",
-                    "90": "/img/90.png",
-                    "60": "/img/60.png",
-                    "32": "/img/32.png"
-                },
-            "developer": {
-            "name": "Rizky Ariestiyansyah",
-            "url": "http://oonlab.com"
-            },
-            "orientation": ["portrait"],
-            "default_locale": "en"
-        })
-        return Response(data, mimetype='application/x-web-app-manifest+json')
- -

Serving from Rack (Ruby)

- -

In config/initializers/mime_types.rb, add:

- -
Rack::Mime::MIME_TYPES['.webapp'] = 'application/x-web-app-manifest+json'
- -

Especificação

- -

Not part of any specification — this document refers to the proprietary Firefox OS manifest format, and not the W3C manifest spec. We will hopefully document this at a different location, sometime soon.

- -

Compatibilidade do navegador

- -

For obvious reasons, support is primarily expected on mobile browsers.

- -

{{ CompatibilityTable() }}

- -
- - - - - - - - - - - - - - - - - - - -
FeatureChromeFirefox (Gecko)Internet ExplorerOperaSafari
Basic support{{ CompatNo() }}{{ CompatNo() }}{{ CompatNo() }}{{ CompatNo() }}{{ CompatNo() }}
-
- -
- - - - - - - - - - - - - - - - - - - - - -
FeatureAndroidFirefox Mobile (Gecko)Firefox OS (Gecko)IE MobileOpera MobileSafari Mobile
Basic support{{ CompatNo() }}{{ CompatNo() }}1.0.1{{ CompatNo() }}{{ CompatNo() }}{{ CompatNo() }}
-
- -
- - - - - -
diff --git a/files/pt-pt/archive/b2g_os/firefox_os_apps/index.html b/files/pt-pt/archive/b2g_os/firefox_os_apps/index.html deleted file mode 100644 index 4b6226ee81..0000000000 --- a/files/pt-pt/archive/b2g_os/firefox_os_apps/index.html +++ /dev/null @@ -1,140 +0,0 @@ ---- -title: Firefox OS apps -slug: Archive/B2G_OS/Firefox_OS_apps -tags: - - Apps - - Building - - Components - - Firefox OS - - Installing - - NeedsTranslation - - TopicStub - - device APIs -translation_of: Archive/B2G_OS/Firefox_OS_apps ---- -

- -

This section of the Firefox OS docs covers the specific techniques required — and available tools — for building Firefox OS apps. You'll find a number of details below, from Firefox OS building blocks/web components, to device APIs and App installation.

- -

Building Firefox OS apps

- -
-
Building apps for Firefox OS
-
Firefox OS/Firefox platform app specifics, including App installation and management APIs, manifest files, packaged and hosted apps, handling API permissions.
-
Localization
-
This set of articles provides information for developers wishing to provide localized versions of their apps.
-
Performance
-
This page lists performance-related topics specific to Firefox OS.
-
Firefox Accounts on Firefox OS
-
This article provides an overview of using Firefox Accounts in Firefox OS.
-
Reference apps
-
This page lists a number of sample apps we've put together for you to download, install, play with and learn from. Have fun!
-
Screencast series: App Basics for Firefox OS
-
In this collection of short videos, developers from Mozilla and Telenor explain in a few steps how you can get started with building applications for Firefox OS.
-
- -

Building blocks

- -
-
Building Blocks
-
The Firefox OS Building Blocks are reusable UI components (also called 'common controls') that reflect OS-wide design patterns. Building Blocks are used to create the interfaces of all Gaia default apps. You are free to make use of these components in your own Firefox OS apps, or general Web apps.
-
- -

Styleguides

- -
-
Firefox OS Visual styleguide
-
Our style guide for Firefox OS visual design, covering colours, typeface, backgrounds, app icons, and the design of specific UI elements.
-
Firefox OS Copy styleguide
-
This guide outlines the rules we follow for writing Firefox OS app copy, but can be used as a general guide to writing good copy for any app interfaces.
-
Firefox OS in Arabic
-
A guide to the specific UX design implementation Firefox OS has in place for dealing with Arabic (and other RTL languages.)
-
- -

Assets

- -
-
Firefox OS design asset library
-
In this section you'll find design assets, artwork, graphic templates, fonts and other materials that will be helpful as you design Firefox OS/Gaia apps.
-
Firefox OS icon font
-
Firefox OS has its own icon font set available: this article explains how to use it in your own apps.
-
Firefox OS transitions
-
A reference to some of the transitions used in Firefox OS to move between different states in apps, including animated GIFs demonstrating the animations used, plus code samples to show the CSS animation code needed to implement these animations.
-
- -

References

- -
-
Firefox OS device APIs
-
This article provides a list of pages covering those APIs, as well as the app manifest permissions for each one.
-
Firefox OS app tools
-
This page provides a list of useful tools, libraries, examples, etc. that are useful for Firefox OS app developers, whether you want a code template to copy, or need help with adding a specific feature to your Firefox OS app.
-
- -

Other app topics

- -
-
Porting Chrome apps to Firefox OS Apps
-
This article discusses the differences between Chrome apps and Firefox OS Apps, and how you can convert between the two.
-
App development FAQ
-
This FAQ is a compilation of answers to common app development questions.
-
- -

See also

- - diff --git "a/files/pt-pt/archive/b2g_os/firefox_os_apps/localiza\303\247\303\243o/index.html" "b/files/pt-pt/archive/b2g_os/firefox_os_apps/localiza\303\247\303\243o/index.html" deleted file mode 100644 index f9cfe4bca2..0000000000 --- "a/files/pt-pt/archive/b2g_os/firefox_os_apps/localiza\303\247\303\243o/index.html" +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: Localização de aplicação -slug: Archive/B2G_OS/Firefox_OS_apps/Localização -tags: - - Aplicações - - Apps - - B2G - - Firefox OS - - Gaia - - L10n.js - - Localization - - Localização -translation_of: Archive/B2G_OS/Firefox_OS_apps/Localization ---- -

- -
-

This set of articles provides information for developers wishing to provide localized versions of their apps.

-
- -

Tutoriais

- -
-
Getting started with app localization
-
This tutorial provides a detailed guide to app localization.
-
Connecting developers and translators with Transifex
-
This article explores the use of Transifex for managing translation work, both for app developers and localizers.
-
- -

Referência

- -
-
L10n.js reference
-
This article provides a reference for the l10n.js library, and its associated date helper, l10n_date.js.
-
Internationalization helpers: IntlHelper and mozIntl
-
This article looks at how Firefox OS handles localization of dates, times, numbers and collators from version 2.5 onwards, using the Internationalization API and Gaia's built in helpers, IntlHelper and mozIntl.
-
App localization code best practices
-
Localization best practices and advanced techniques for experienced Gaia/app developers.
-
Developing Bidi Apps
-
Best coding practices and guidelines for developing bi-directional (left-to-right and right-to-left, RTL) apps.
-
- -

Ferramentas

- -
-
Translation tester
-
This app is for testing translations for Firefox OS apps and provides a blueprint for adding translation support to your own apps.
-
diff --git "a/files/pt-pt/archive/b2g_os/firefox_os_apps/permissoes_de_aplica\303\247\303\243o/index.html" "b/files/pt-pt/archive/b2g_os/firefox_os_apps/permissoes_de_aplica\303\247\303\243o/index.html" deleted file mode 100644 index 403b62c93d..0000000000 --- "a/files/pt-pt/archive/b2g_os/firefox_os_apps/permissoes_de_aplica\303\247\303\243o/index.html" +++ /dev/null @@ -1,690 +0,0 @@ ---- -title: Permissões de Aplicação -slug: Archive/B2G_OS/Firefox_OS_apps/Permissoes_de_aplicação -tags: - - Aplicações - - Firefox OS - - Intermediário - - Permissões - - Referencia - - Referência(2) - - WebAPI -translation_of: Archive/B2G_OS/Firefox_OS_apps/App_permissions ---- -
-

O campo de permissões no manisfesto da aplicação controla o acesso a várias APIs sensíveis no dispositivo (algumas vezes chamada de WebAPIs). As permissões são descritas nas tabelas seguintes.

-
- -

Os três níveis de permissão, em resumo, são:

- - - -

For more information on app types, see Types of packaged apps.

- -
-

Nota: If you use the App Manager/WebIDE to test your app, it will display an easy to read table of which permissions are allowed, denied, or require a prompt on the current device or simulator you are connected to.

-
- -

Hosted app and privileged app permissions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Manifest permissionAPI nameDescriptionMinimum app type requiredaccess propertyDefault grantedPlatform/version supported
alarmsAlarmSchedule a notification, or schedule an application to be started.hostednoneAllowFxOS 1.0.1
audio-capture -

getUserMedia, Web Speech API

- 		Obtain MediaStream from audio input devices, e.g. microphone. This is needed to allow audio capture in Firefox OS 1.2+.hosted for getUserMedia, privileged for Web Speech APInonePrompt for all installed App types for getUserMedia, Allow for Web Speech API.FxOS 1.2 and
- Desktop Firefox 20+ for getUserMedia, FxOS 2.5 and Desktop Firefox 44 for Web Speech API.
audio-channel-alarmAudioChannelsAlarm clock, calendar alarms.privilegednoneAllowFxOS 1.0.1
audio-channel-contentAudioChannelsMusic, video.hostednoneAllowFxOS 1.0.1
audio-channel-normalAudioChannelsUI sounds, Web content, music, radio.hostednoneAllowFxOS 1.0.1
audio-channel-notificationAudioChannelsNew email, incoming SMS.privilegednoneAllowFxOS 1.0.1
browserBrowserEnables the app to implement a browser in an iframe.privilegednoneAllowFxOS 1.0.1
cameraCamera -

Take photos, shoot video, record audio, and control the camera.

- -
-

Note: camera was limited to certified apps initially because the app sandbox was preventing access to the camera hardware. Fixed from Firefox OS 2.0 onwards.

-
- 		-

privileged in Firefox OS 2.0+ internal/certified up to Firefox OS 1.4

- 		nonePrompt for all installed App types.FxOS 1.0.1-1.4 certified
- FxOS 2.0+ privileged
contactsContactsAdd, read, or modify contacts from the address book on the device and read contacts from the SIM.privilegedreadonly, readwrite, readcreate, or createonlyPrompt for all installed App types.FxOS 1.1
- Firefox Android 18
desktop-notificationmozNotification for Gecko <22, Notification for Gecko 22+Display a notification on the user's desktop. Note that this has changed, so for Gecko <22 (Firefox OS <1.2) you need to use mozNotification, while for Gecko 22+ (Firefox 1.2+) you need to use Notification.hostednonePrompt for Web content. Allow for all installed App types.FxOS 1.0.1, Android 4.0, Desktop 4.0 for prefixed version
- FxOS 1.2, Android 22, Desktop 22 for non-prefixed version
device-storage:musicDevice StorageAdd, read, or modify music files stored on the device.privilegedreadonly, readwrite, readcreate, or createonlyPromptFxOS 1.0.1
device-storage:picturesDevice StorageAdd, read, or modify picture files stored on the device.privilegedreadonly, readwrite, readcreate, or createonlyPromptFxOS 1.0.1
device-storage:sdcardDevice StorageAdd, read, or modify files stored on the device's SD card.privilegedreadonly, readwrite, readcreate, or createonlyPromptFxOS 1.0.1
device-storage:videosDevice StorageAdd, read, or modify video files stored on the device.privilegedreadonly, readwrite, readcreate, or createonlyPromptFxOS 1.0.1
fmradioFM RadioControl the FM radio.hostednoneAllowFxOS 1.0.1
geolocationGeolocationObtain the current location of the user.hostednonePrompt (even for certified Apps)FxOS 1.0.1, Desktop Firefox 3.5, Android 4.0
inputKeyboardAllows the app to act as a virtual keyboard by listening to focus change events in other apps. All IME apps need this permission for sending input keys and updating the value of a input field.privilegednoneAllowFxOS 1.2
mobileidMobile identityAllows an app to obtain a verified phone number (MSISDN) after the user selects the number to be shared and gives explicit permission for the app to obtain it.privileged/nonePromptFxOS 2.0
mobilenetworkMobile NetworkObtain mobile network information (MCC, MNC, etc.).privilegednoneAllowFxOS 1.0.1
moz-firefox-accountsFirefox AccountsAllows the use of Firefox Accounts when using the navigator.mozId API.privilegednonePrompt for all installed App types.FxOS 2.0
nfcNFC APINFC enables an app to transmit data to other devices via near field communication. This permission is required for reading and writing data.PrivilegednoneAllowFxOS 2.2
nfc-shareNFC APIThis permission is just required for sharing tags via NFC.PrivilegednoneAllowFxOS 2.2
nfc-read, nfc-writeNFC APIThese permissions were used to request reading and writing privileges in Firefox OS 2.0/2.1Was certified/internal at this stage in development.noneAllowFxOS 2.0
pushSimple PushEnable an app to wake up to receive notification.hostednoneAllowFxOS 1.1
speech-recognitionWeb Speech APIAllows an app to use speech recognition.privilegednoneAllowFxOS 2.5 and Desktop Firefox 44.
systemXHRSystemXHRAllows anonymous (no cookies) cross-origin XHR without the target site having CORS enabled. Similar to the TCP Socket API but restricted to XHR, not just raw sockets, so it is slightly less risky. See XMLHttpRequest.privilegednoneAllowFxOS 1.0.1
tcp-socketTCP SocketCreate TCP sockets and communicate over them.privilegednoneAllowFxOS 1.0.1,
- Desktop (early versions)
video-captureGetUserMediaObtain MediaStream from video input devices, e.g. camera. This is needed to allow video capture in Firefox OS 1.4+.hostednonePrompt for all installed App types.FxOS 1.4
- -
-

Note: To declare an app as privileged, you need to put "type" : "privileged" into your app manifest. You don't need to include the type field in your manifest for web apps, as web is the default value.

-
- -

Internal (Certified) app permissions

- -

The following permissions require a internal app and are granted implicitly without prompting the user. Most app developers will not be able to use internal APIs, because they are intended for system-level apps and default apps created by Mozilla/operators/OEMs.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Manifest permissionAPI nameDescriptionMinimum app type requiredaccess propertyPlatform
attentionAttention Screen -

Allow content to open a window in front of all other content. Used by telephone and SMS.

- -
-

Note: Attention screens use the Firefox OS-specific attention feature name when calling {{domxref("window.open()")}}.

-
- 		internal (certified)noneFxOS 1.0.1
audio-channel-ringerAudioChannelsIncoming phone calls.internal (certified)noneFxOS 1.0.1
audio-channel-telephonyAudioChannelsPhone calls, VoIP calls.internal (certified)noneFxOS 1.0.1
audio-channel-publicnotificationAudioChannelsForced camera shutter sounds.internal (certified)noneFxOS 1.2
background-sensorsBackground SensorAbility to listen to proximity sensor events in the background. (All apps recieve these events in the foreground.)internal (certified)noneFxOS 1.0.1
backgroundservice (Deprecated)Background Services -

Enable an app to run in the background and perform tasks like syncing or responding to incoming messages.

- -
-

Note: this functionality has been removed.

-
- 		internal (certified)noneFxOS 1.0.1
bluetooth Low level access to Bluetooth hardware.internal (certified)noneFxOS 1.0.1
browser:embedded-system-appBrowserEnables an app opened in a browser {{htmlelement("iframe")}} to call methods of the API on — and listen and respond to related events fired by — itself (usually the parent window of the iframe calls the Browser API.) See {{bug("1196654")}} for further information.internal (certified)noneFxOS 2.5
cameraCamera -

Take photos, shoot video, record audio, and control the camera.

- -
-

Note: camera was limited to certified apps initially because the sandbox that apps run in was preventing access to the camera hardware. This has been fixed from Firefox OS 2.0 onwards.

-
- 		internal (certified) up to Firefox OS 1.4, privileged in Firefox OS 2.0+noneFxOS 1.0.1-1.4 certified
- FxOS 2.0+ privileged
cellbroadcast Fires an event when a specific type of cell network message is received (an emergency network notification).internal (certified)noneFxOS 1.0.1
No permission needed, but datastores-access/datastores-owned needs to be set in the manifest (see Data Store API Manifest fields.)Data StoreA powerful, flexible storage mechanism for Firefox OS applications to use to store and share data.internal (certified)datastores-access/
- datastores-owned		FxOS 1.0.1
device-storage:appsDevice StorageAdd, read, or modify files stored in the apps location on the device.
-
- When this is used, the webapps-manage permission is also required alongside it (see below.)		internal (certified)readFxOS 1.0.1
embed-appsEmbed AppsAbility to embed apps in mozApp frames.internal (certified)noneFxOS 1.0.1
idleIdleNotify the app if the user is idle.internal (certified)noneFxOS 1.0.1
mobileconnectionMobile ConnectionObtain information about the current mobile voice and data connection.internal (certified)noneFxOS 1.0.1
network-eventsNetwork EventsMonitor network uploads and downloads.internal (certified)noneFxOS 1.0.1
networkstats-manageNetwork StatsObtain statistics of data usage per interface.internal (certified)noneFxOS 1.0.1
open-remote-windowOpen out-of-process windowsAllows normal window.open calls, but the resulting window is opened in a new process.internal (certified)noneFxOS 1.0.1
permissionsPermissions (Firefox OS)Allow an app to manage other permissions of other apps.internal (certified)noneFxOS 1.0.1
phonenumberservice????internal (certified)none??
powerPower ManagementTurn the screen on or off, control CPU, device power, and so on. Listen for and inspect resource lock events.internal (certified)noneFxOS 1.0.1
presentation-device-managePresentationObtain the list of available devices that can be used as external display and trigger device discovery.internal (certified)noneFxOS 3.0
settingsSettingsConfigure or read device settings.internal (certified)readonly or readwriteFxOS 1.0.1
smsWebSMSSend and receive SMS messages.internal (certified)noneFxOS 1.0.1,
- 1.1 for MMS
telephonyWeb TelephonyAccess all telephony-related APIs to make and recieve phone calls.internal (certified)noneFxOS 1.0.1
timeTimeManagerSet current time. Time zone information is controlled by the Settings API. Formerly called systemclock.internal (certified)noneFxOS 1.0.1
voicemailVoicemailAccess voicemail.internal (certified)noneFxOS 1.0.1
webapps-manageOpen WebappsObtain access to the navigator.mozApps.mgmt API to manage installed Open Web Apps.
-
- Required alongside the device-storage:apps permission (see above.)		internal (certified)noneFxOS 1.0.1, Desktop, Android
wifi-manageWiFi ManagementEnumerate available WiFi networks, get signal strength, connect to a network.internal (certified)noneFxOS 1.0.1
wappushWAP PushReceive WAP Push messages.internal (certified)noneFxOS 1.0.1
- -
-

Nota: The internal codename for internal apps is certified apps. To declare an app as internal, you need to put "type" : "certified" into your app manifest.

-
- -

Consulte também

- -

A tabela de permissões (descontinuada e substituida por DXR) é onde são definidas as permissões da API do Firefox OSno código fonte do Firefox.

- -
- - - - - -
diff --git a/files/pt-pt/archive/b2g_os/index.html b/files/pt-pt/archive/b2g_os/index.html deleted file mode 100644 index c618cb8e2f..0000000000 --- a/files/pt-pt/archive/b2g_os/index.html +++ /dev/null @@ -1,241 +0,0 @@ ---- -title: B2G OS -slug: Archive/B2G_OS -tags: - - B2G - - Firefox OS - - Gaia - - Iniciação Firefox OS - - Principiante - - Resumo - - Sinopse - - básico -translation_of: Archive/B2G_OS ---- -
-

Firefox OS é o sistema operativo móvel desenvolvido pela Mozilla, baseado no Linux e no motor de renderização poderoso Gecko do Firefox.

-
- -

Firefox OS is open source software that allows developers to harness the power and flexibility of the Web to create advanced end-user applications. The entire user interface is a web app, which can display and launch other apps. A Firefox OS web app is made with HTML, CSS, and JavaScript. In addition, Firefox OS web apps have access to the device hardware and services via an Application Programing Interface (API).

- -

From a product perspective, Firefox OS is Mozilla's (and our OEM partners') branding and support services applied on top of Boot to Gecko (B2G), which is the operating system's engineering codename. Boot to Gecko is developed by a team of engineers inside Mozilla plus many external contributors from the wider Mozilla/open source community.

- -
-

Desenvolver aplicações para o Firefox OS

- -

Head over to our App Center for all the information you could possibly need on building open web apps that can be installed on Firefox OS !

-
- -
-
-

Guias da Plataforma

- -

Guides for platform developers on how the different components of the Firefox OS platform fit together and work.

- - -
- -
-

Criar e Instalar

- -

Guides covering building and installing Firefox OS on an emulator, compatible device, or desktop simulator.

- - -
- -
-

Developer phones

- -

Information on specific developer phones, such as tweaking, updating, recovering, and buying.

- - -
-
- -
-
-

Get started with Firefox OS add-ons

- -

Firefox OS add-ons are new in Firefox OS 2.5! To start developing add-ons and getting involved in the add-ons community, read Getting started with Firefox OS add-ons.

-
- -
-

Other useful pages

- - -
-
- -
-

Note: We are keeping track of ongoing work on Firefox OS documentation on our Firefox OS documentation status page. If you want to help contribute to Firefox OS documentation, please have a look at this page to see what work needs tweaking!

-
- - - -
    -
  1. Introduction
    2. -
  2. Platform guide -
      -
    1. Platform guide overview
      2. -
    2. Architecture overview
      3. -
    3. Apps architecture
      4. -
    4. Gonk
      5. -
    5. Gecko
      6. -
    6. Gaia
      7. -
    7. Gaia apps guide
      8. -
    8. Security -
        -
      1. The Firefox OS security model
        2. -
      2. System security
        3. -
      3. Application security in Firefox OS
        4. -
      4. Securely installing and updating applications
        5. -
      -
      9. -
    9. Out of memory management on Firefox OS
      10. -
    10. Feature support chart
      11. -
    11. Settings list
      12. -
    -
    3. -
  3. Build and install -
      -
    1. Build and install overview
      2. -
    2. Firefox OS build process summary
      3. -
    3. Build prerequisites
      4. -
    4. Preparing for your first build
      5. -
    5. Building Firefox OS
      6. -
    6. Building Firefox OS for flame on OSX
      7. -
    7. Choosing how to run Gaia or Firefox OS
      8. -
    8. Building the Firefox OS simulator
      9. -
    9. Using the Firefox OS emulators
      10. -
    10. Installing Firefox OS on a mobile device
      11. -
    11. Creating and applying Firefox OS update packages
      12. -
    12. Building and installing FOTA community builds
      13. -
    13. B2G build variables reference sheet
      14. -
    -
    4. -
  4. Developing Firefox OS -
      -
    1. Developing Firefox OS overview
      2. -
    2. Filing bugs against Firefox OS
      3. -
    3. Modifying the hosts file
      4. -
    4. Customization with the .userconfig file
      5. -
    5. Customizing the b2g.sh script
      6. -
    6. Porting Firefox OS
      7. -
    -
    5. -
  5. Developing Gaia -
      -
    1. Developing Gaia overview
      2. -
    2. Running the Gaia codebase
      3. -
    3. Understanding the Gaia codebase
      4. -
    4. Making Gaia code changes
      5. -
    5. Testing Gaia code changes
      6. -
    6. Submitting a Gaia patch
      7. -
    7. Gaia build system primer
      8. -
    8. Customizing build-time apps
      9. -
    9. Market customizations guide
      10. -
    10. Customizing the keyboard in Firefox OS apps
      11. -
    11. Localizing Firefox OS
      12. -
    12. L10n Best Practices
      13. -
    13. Make options reference
      14. -
    14. Gaia tools reference
      15. -
    -
    6. -
  6. Firefox OS add-ons -
      -
    1. Firefox OS add-ons overview
      2. -
    2. Developing Firefox OS add-ons
      3. -
    -
    7. -
  7. Firefox OS phone guide -
      -
    1. Firefox OS phone guide overview
      2. -
    2. Phone and device specs
      3. -
    3. Geeksphone
      4. -
    4. ZTE OPEN
      5. -
    5. ZTE OPEN C
      6. -
    6. Flame
      7. -
    7. General device features
      8. -
    8. Troubleshooting
      9. -
    9. Best practices for open reference devices
      10. -
    -
    8. -
  8. Firefox OS on TVs and connected devices -
      -
    1. TVs and connected devices overview
      2. -
    2. How to connect WebIDE to TV (VIERA CX/CR series)
      3. -
    3. TV broadcast streams on Firefox OS products
      4. -
    4. Web animations on large screens
      5. -
    5. Implementing TV remote control navigation
      6. -
    6. Keyboard events in Firefox OS TV
      7. -
    7. TV remote control button mapping to keyboard
      8. -
    8. Firefox OS for TV UX Overview
      9. -
    -
    9. -
  9. Firefox OS release notes -
      -
    1. Firefox OS release notes overview
      2. -
    2. Firefox OS 2.2 for developers
      3. -
    3. Firefox OS 2.1 for developers
      4. -
    4. Firefox OS 2.0 for developers
      5. -
    5. Firefox OS 1.4 for developers
      6. -
    6. Firefox OS 1.3 for developers
      7. -
    7. Firefox OS 1.2 for developers
      8. -
    8. Firefox OS 1.1 for developers
      9. -
    9. Firefox OS 1.0.1 for developers
      10. -
    -
    10. -
  10. Automated testing -
      -
    1. Firefox OS automated testing overview
      2. -
    2. Running tests on Firefox OS: A guide for developers
      3. -
    3. Gaia UI tests
      4. -
    4. Gaia integration tests
      5. -
    5. Gaia unit tests
      6. -
    6. Gaia performance tests
      7. -
    7. Mochitests
      8. -
    8. Reftests
      9. -
    9. WebAPI tests
      10. -
    10. xpcshell tests
      11. -
    11. MTBF test
      12. -
    12. Marionette
      13. -
    13. Treeherder
      14. -
    -
    11. -
  11. Debugging -
      -
    1. Firefox OS debugging overview
      2. -
    2. Developer settings for Firefox OS
      3. -
    3. Connecting a Firefox OS device to the desktop
      4. -
    4. Setting up to debug Firefox OS using Firefox developer tools
      5. -
    5. On-device console logging
      6. -
    6. Installing and using ADB
      7. -
    7. Taking screenshots
      8. -
    8. Using the WebIDE
      9. -
    9. Firefox OS crash reporting
      10. -
    10. Debugging out of memory errors on Firefox OS
      11. -
    11. Debugging and security testing with Firefox OS
      12. -
    12. Debugging B2G using gdb
      13. -
    13. Debugging B2G using Valgrind
      14. -
    -
    12. -
diff --git a/files/pt-pt/archive/b2g_os/phone_guide/flame/index.html b/files/pt-pt/archive/b2g_os/phone_guide/flame/index.html deleted file mode 100644 index 5f874186ca..0000000000 --- a/files/pt-pt/archive/b2g_os/phone_guide/flame/index.html +++ /dev/null @@ -1,305 +0,0 @@ ---- -title: Flame -slug: Archive/B2G_OS/Phone_guide/Flame -translation_of: Archive/B2G_OS/Phone_guide/Flame ---- -

A picture of the Flame device, showing the Firefox OS homescreen containing several app icons.

- -

Available to order

- -

The Flame developer reference phone is a milestone in Firefox OS device releases. The Flame hardware offers a representative set of specs — including FWVGA display and dual-core processor — to help developers build great content and experiences. A single hardware platform is also good for testers, making it easier to test and address specific software issues without having to worry about device model-specific bugs, etc.

- -

If you have your phone in hand and want to start playing with it, developing and distributing apps, or contributing to the Firefox platform, the following links will get you where you need to go:

- - - -

If you’d like to find out more about updating the operating system, recovering it, pushing apps to it, or phone specs, you’ll find the information you need below.

- -

Purchasing a device

- -

Our device manufacturer partner has made the device available to order on everbuying.com, for US$170 including global shipping (device cost is $145, shipping is $25 and custom fees may still apply, depending on the destination country). The device is bootloader- and carrier-unlocked, and it utilizes a quad-band GSM+UMTS radio so that it can work with a wide variety of operators/carriers.

- -
-

Note: Another option for getting hold of a Flame is to participate in our Flames for Apps scheme, aimed at experienced HTML5 app developers wishing to port their highly-rated apps onto Firefox OS.

-
- -

Important steps to follow first

- -

There are a couple of steps you should make sure you follow for your particular operating system, before you start trying to update your device, for example by updating your Flame's version of Firefox OS, or pushing apps to your phone (both are covered below.)

- -

All operating systems

- -

You need to install ADB and Fastboot on your computer — these are applications that allow you to interact with your phone from your computer when the two are connected via the phone's USB charger cable. They are needed for Flashing your phone to a new version of Firefox OS, recovering from an unresponsive state, pushing apps to your phone, etc.

- -
-

Note: If you are on Ubuntu you can install ADB and Fastboot simply by using sudo apt-get install android-tools-adb android-tools-fastboot on the command line.

-
- -

ADB and Fastboot are available in the Android Developer Toolkit:

- -
    -
  1. Go to this link
    2. -
  2. Press the Download Eclipse ADT button
    3. -
  3. Agree to the license conditions
    4. -
  4. Choose between the 32-bit and 64-bit version (32-bit will do if you are not sure)
    5. -
  5. Click the final Download Eclipse ADT with the Android SDK... button.
    6. -
  6. Once the download is complete, unzip the zip file's contents onto your computer's desktop
    7. -
  7. The folder name is a bit complicated; rename it to just adt
    8. -
- -

ADB is a tool that you run from the command line. If you open your terminal/command prompt, go to adt/sdk/platform-tools and run the adb command, you should see a load of information thrown back at you about what you can do with ADB. Running adb devices should return the line List of devices attached, and nothing else, because you haven't got any devices attached yet.

- -

But at this point, you need to set the PATH variable to point to the ADB tool, so you can run it from anywhere, not just when you are in the exact directory that ADB is in. To do this:

- - - -

On Mac/Linux:

- - - -

Linux and Mac

- -

No additional steps should be required if you are using a Linux or Mac system, although depending on your Linux distro, you might need to add a udev rule for your phone.

- -

The udev rule for the Flame should look something like the following:

- -
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9025", GROUP="users", MODE="0666"
- -

Make sure to --reload-rules, then unplug and replug and your device before continuing.

- -

Windows

- -

To access the Flame device with the App Manager/ADB, a USB driver is required. Follow the steps outlined in the below sections to install it.

- -

Downloading the driver

- -

Download the Windows driver from this location. Once downloaded, extract the contents of the ZIP file to a suitable place on your hard drive.

- -
-

Note: The Android Debug Bridge (ADB) must be installed first.

-
- -

Installing the USB Driver

- -

At this point, connect your Flame device to your computer using a USB cable.

- -

To install the driver, open the Alcatel_USB_Driver_Q_4.0.0_2013_11_11_noinstall directory within the extracted ZIP file and double click on the DriverInstaller.exe executable. You may receive a warning at this point that the executable is from an unknown publisher. If so, select the Yes button and the executable will be launched.

- -

Simple dialog box showing a picture of a phone along with install and uninstall buttons.

- -

Click on the Install button to install the driver.

- -

After the driver installs, you can check that it is working by opening a command line window and typing adb devices. This should list the connected device with an output something like:

- -
List of devices attached
-3561d02a          device
- -

If your device is not showing up here, check in the Windows Device Manager. Your Flame may be showing up as "ACER ADB Interface". You can confirm this by unplugging the device and seeing if it disappears from the device manager. Uninstall the driver software by right-clicking on "ACER ADB Interface" and clicking uninstall.  Be sure to check the box in the dialog to delete the driver software.  Now re-run the installer above. It is advisable to set the screen timeout on your Flame to something high (Settings > Display > Screen timeout) as Windows sometimes appears to reinstall the default drivers when the screen turns off.

- -

Updating your Flame's software

- -

We will have two main "channels" of Firefox OS software version releases for the Flame phone:

- - - -

While our partners are working out a final storage solution for the software builds, you can get recovery files and tools at the following storage locations:

- - - -

To install the base image on your device:

- -
    -
  1. Make sure remote debugging is enabled on your Flame, using the Remote debugging/Debugging via USB option in the device's Developer settings (the option is different, depending on whether you have Firefox 1.3 and under, or Firefox 1.4+ installed).
    2. -
  2. Connect your Flame to your computer via a USB cable if it isn't already. Verify that the computer is connected to the device by running the adb devices command in a terminal.
    3. -
  3. Download and Extract the .zip file referenced above. Unzip it onto your Desktop.
    4. -
  4. Go into the directory you extracted the software into and run it: -
      -
    • On Windows, enter the directory in your command prompt, then run the flash.bat script using flash.bat.
      • -
    • On Linux / OSX, enter the directory in your terminal, then run the flash.sh script using sudo ./flash.sh (if you don't run it using sudo, the flash script may fail to see your device, and it won't work).
      • -
    -
    5. -
- -
-

Note: You are also welcome to build your own builds to install on the Flame: see Building and installing Firefox OS.

-
- -

Updating your Flame to a nightly build

- -
-

Note: For this current build, Nightly development builds of Firefox OS do not support A-GPS, which may lead to slow performance of GPS functionality. We plan to resolve this in an updated future Nightly channel.

-
- -
    -
  1. Before updating your phone to a Nightly build you should flash the latest base image to make sure the underlying systems are up to date. Download a base image and use it to update your device's software, as explained above.
    2. -
  2. Because the above step installs a fresh operating system on your device, you'll need to enable remote debugging on your Flame again, using the Remote debugging option in the device's Developer settings.
    3. -
  3. Next, choose a Nightly build to install (found on http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/.) You'll want one of the following: - -
    4. -
  4. Pick a version and download both the b2g-XX.XX.en-US.android-arm.tar.gz and gaia.zip files. Save them inside a directory on your Desktop called something like fxos.
    5. -
  5. Download the shallow flash script and save it in the same directory as the above two files: follow the link, press the Raw button, then use your browser's save functionality to save the page directly as shallow_flash.sh.
    6. -
  6. In your Terminal, cd into the directory you saved the files in and Flash the builds to your phone using the following command: -

    Mac

    - - 
    ./shallow_flash.sh -g gaia.zip -G b2g-XX.XX.en-US.android-arm.tar.gz
    - -

    Linux

    - - 
    ./shallow_flash.sh -ggaia.zip -Gb2g-XX.XX.en-US.android-arm.tar.gz
-
    - -

    Windows (Note: instruction still being worked out, may not work yet)

    - - 
    shallow_flash.sh -g gaia.zip -G b2g-XX.XX.en-US.android-arm.tar.gz
-
    -
    7. -
- -
-

Note: If you get a "permission denied" error when running the above command, your shell script probably doesn't have the right permissions. Running chmod +x shallow_flash.sh on it should solve this problem.

-
- -
-

Note: A "shallow flash" updates Gecko and Gaia plus data directories, as opposed to a full flash, which updates Gecko/Gaia, but also the underlying Gonk layer and associated binaries particular to that device type. This is why it is a good idea to update to the official base image first, as suggested above, then shallow flash over the top of that, once you've got the Gonk/binary layer right.

-
- -
-

Important: When running a shallow or full flash, your phone data will be overwritten: you should therefore back up your data before updating!

-
- -

Once the install procedure finishes the phone should reboot into the updated build and display the first time user workflow.

- -

Font fix

- -

After updating Gecko and Gaia to nightly with the v123 base image, there will be a mismatch between the fonts that Gecko and Gaia expects and what the base image provides. To fix this, download our font update package, extract it, navigate into the directory created by extracting, and run the supplied flash.sh script.

- -
-

Note: Another option is to use the update_system_fonts.sh script, which will download and flash the system fonts automatically.

-
- -

Fastboot mode

- -

If flashing a new build to your phone fails to work, your phone may become unresponsive, leading to the phone rebooting in recovery mode. The recovery mode provides few options (Reboot, Update from adb, Wipe data, Wipe cache, and Update from sdcard). Unfortunately, selecting Update from adb triggers a sideload mode in which you cannot use the other adb commands. The adb sideload command would work but the various flash scripts rely on other adb commands.

- -

From sideload mode, you can force fastboot mode as follows:

- -
    -
  1. Power off the phone (which may involve removing the battery in extreme cases...)
    2. -
  2. Plug in the USB cable.
    3. -
  3. Power the phone up again by pressing the Volume Down and Power buttons together.
    4. -
- -

The phone should only display the very first static logo and stay there, without displaying the boot animation. It seems stuck but is not really: it is in fastboot mode and is waiting for a USB connection. At this point, a USB-connected, computer with adb installed should see the phone listed when the fastboot devices command is run. Note that regular adb would not see the device — only fastboot sees it. In this mode, you can use the flash script to install v123 as explained above. As the script does use both adb and fastboot commands, you may see some initial error and warnings from adb, but the device should be flashed properly at the end of the procedure.

- -

Emergency download mode

- -

If flashing a new build to your phone fails to work, your phone becomes unresponsive, and the phone cannot enter fastboot mode, you can use emergency mode for recovery. A USB cable and the Emergency Download Tool are required to enter emergency download mode. Install this tool and follow the instructions.

- -

Recovery mode

- -

You can enter recovery mode to clear your phone data or manually update the firmware. There are two ways to enter this mode:

- - - -

When in recovery mode, press the Volume up/down keys to move the selection highlight, and the Power key to select. Make sure you have your phone data (Contacts, SMS, etc.) backed up before clearing data, and your upgrade packages downloaded before updating.

- -

Pushing apps to your Flame

- -

The App Manager tool makes it easy to push apps to your phone, for testing, etc. Full instructions are available in the article Using the App Manager.

- -
-

Note: If you are running Firefox Nightly, you can instead make use of our next generation WebIDE tool, which performs the same functions as the App Manager, plus more.

-
- -

RAM adjustment

- -

You can adjust the available RAM capacity to see how apps perform on Firefox OS phones with lower memory footprints.

- -

This is accomplished by entering fastboot mode (install fastboot first, which is available on the same SDK page as ADB) and typing:

- -
adb reboot bootloader
-fastboot oem mem [0|256-1024]
- -

“0” is the memory automatically detected and “256-1024” is the number of megabytes. For example, if you want to adjust device RAM capacity to 512M, enter fastboot oem mem 512.

- -

You'll need to then reboot your device for the settings to take effect. This can be done using:

- -
fastboot reboot
- -

The current memory size can be returned by entering fastboot mode and typing:

- -
fastboot getvar mem
-
- -

Network and Device specs

- -

Network:

- - - -

Hardware: You can find more of the hardware features listed on our Phone and device specs page.

- -

Additional features include:

- - - -

See also

- - diff --git a/files/pt-pt/archive/b2g_os/phone_guide/index.html b/files/pt-pt/archive/b2g_os/phone_guide/index.html deleted file mode 100644 index d90e90d259..0000000000 --- a/files/pt-pt/archive/b2g_os/phone_guide/index.html +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Firefox OS developer phone guide -slug: Archive/B2G_OS/Phone_guide -tags: - - B2G - - Firefox OS - - Landing - - NeedsTranslation - - Phones - - TopicStub -translation_of: Archive/B2G_OS/Phone_guide ---- -
-

This section contains developer information relevant to specific phones that run Firefox OS. We have general information available on Building and installing Firefox OS and Hacking Firefox OS, so please go there for information about building and installing the platform from scratch. Developers with specific phones in their possession may however find the following articles useful.

-
-

Specific device information

-
-
- Firefox OS phone data
-
- In this article we list the various available Firefox OS phones along with information such as their code names, availability, and specific hardware features.
-
- Flame
-
- Information on Mozilla's high-end Firefox OS reference phone, codenamed the Flame, and produced in partnership with T2Mobile.
-
- Geeksphone
-
- In this article we cover some basic tips on how to keep your Geeksphone up-to-date and how to tweak the system Gaia applications.
-
- ZTE OPEN
-
- This article contains information on the ZTE OPEN Firefox OS device.
-
- ZTE OPEN C
-
- The ZTE Open C is an updated ZTE-produced Firefox OS device, with higher end hardware and newer software.
-
-

General Firefox OS information

-
-
- General device features
-
- This page lists typical Firefox OS hardware features and minimum hardware requirements.
-
- Troubleshooting
-
- This article provides tips for resolving common problems you may have while using Firefox OS.
-
- Best practices for open reference devices
-
- A set of best practices that we believe should come highly recommended for any widely available open reference devices. All of the recent Firefox OS reference devices have followed these practices.
-
diff --git a/files/pt-pt/archive/b2g_os/simulator/index.html b/files/pt-pt/archive/b2g_os/simulator/index.html deleted file mode 100644 index 1c8c9341a6..0000000000 --- a/files/pt-pt/archive/b2g_os/simulator/index.html +++ /dev/null @@ -1,118 +0,0 @@ ---- -title: Simulador do Firefox OS -slug: Archive/B2G_OS/Simulator -tags: - - Aplicações - - Ferramentas - - Firefox OS -translation_of: Archive/B2G_OS/Simulator ---- -
-

Esta página descreve o Simulador do Firefox OS para os programadores que segmentam o Firefox OS 1.2 ou superior. Se está a desenvolver aplicações para o Firefox OS 1.1, em vez disso, consulte a documentação do Firefox OS 1.1 Simulator.

-
- -

The Firefox OS Simulator is a version of the higher layers of Firefox OS that simulates a Firefox OS device, but runs on the desktop. This means that in many cases, you don't need a real device to test and debug your app. It runs in a window the same size as a Firefox OS device, includes the Firefox OS user interface and built-in apps, and simulates many of the Firefox OS device APIs.

- -

The Simulator is packaged and distributed as a Firefox add-on. Once you've downloaded it and installed it in Firefox, you can run it, push apps to it, and attach the developer tools to it using the App Manager tool or WebIDE.

- -

Instalação

- -

To install the simulator, use WebIDE's Manage Extra Components pane (available as part of Firefox 34 and onwards). Multiple versions are available, and you are advised to install them all, for maximum flexibility.

- -
-

Starting with Firefox 43, the about:addons page may display warnings about your addon being unsigned. The simulators are properly signed at install time, however they are subsequently modified and thus appear "broken". They will continue to run successfully despite this warning message. Details are in {{ Bug(1197262) }}.

-
- -

To start the Simulator, you choose it from WebIDE's runtime list. For more details, see the instructions in the WebIDE documentation. Once the Simulator's running, you can push apps to it and debug them using the WebIDE, just as you can with a real device.

- -

If you are using the App Manager (an older tool available prior to the WebIDE), you can install a simulator via the following button:

- -

Instalar Simulador

- -

A IU do Simulador

- -

The Simulator appears as a separate window, sized so the simulated screen area is 320x480 pixels. To simulate touch events you can click the mouse button and drag while holding the button down. So by clicking and dragging right-to-left from the Home Screen, you'll see the built-in apps, as well as any apps you have added:

- -

- -

The Simulator has two buttons in a toolbar at the bottom:

- - - -

Emulação do cartão SD

- -

In the Simulator the device SD card is mapped to the "fake-sdcard" directory in the Simulator's profile, which is itself located inside the "extensions" directory under the Firefox profile in which the Simulator is installed. For example:

- -
/path/to/Firefox/Profiles/Firefox-profile-name/extensions/fxos_2_2_simulator@mozilla.org/profile/fake-sdcard
- -

Files read or written using the getDeviceStorage API will appear here.

- -

Before version 2.2 of the Simulator, you had to create the "fake-sdcard" directory manually for this to work. From 2.2 onwards, the "fake-sdcard" directory is created for you automatically.

- -

Also from version 2.2 onwards, if you're running the Simulator from the command line you can define a different directory by passing the --storage-path option.

- -
Note: this is mostly meant for API testing. Music will be read not from the "fake-sdcard" directory, but from your system's ~/Music, pictures from ~/Pictures, videos from ~/Videos. Downloads go to ~/Downloads. user-dirs.dirs redefinitions are supported.
- -

Limitações do Simulador

- -

Note that the Firefox OS Simulator isn't a perfect simulation.

- -

Limitações do Hardware

- -

Apart from screen size, the Simulator does not simulate the hardware limitations of a Firefox OS device such as available memory or CPU speed.

- -

Codecs de áudio/vídeo

- -

The following codecs depend on hardware-accelerated decoding and are therefore not yet supported:

- - - -

This means it isn't possible to use the Simulator to test video playback in apps and on websites like Youtube that rely on these codecs.

- -

APIs Não Suportadas

- -

Certain APIs that work on the device won't work on the Simulator, generally because the supporting hardware is not available on the desktop. We've implemented simulations for some APIs such as geolocation, and expect to add more in future releases. However, at the moment the following APIs are not supported. Using them might throw errors or just return incorrect results:

- - - -

Obter ajuda

- -

If you have a question, try asking us on the dev-developer-tools mailing list or on #devtools on irc.mozilla.org.

- -

How to enable verbose logging

- -

You can see messages logged from your app in the Web Console, which you can attach to your app using the WebIDE. If you want to catch early messages happening during app startup, before the console gets connected and working, you can enable verbose logging in the Simulator.

- -

Visit about:config and create a new preference. The preference name is different for each version of the Simulator:

- - - -

Set it to the string value "all", and disable, then reenable, the add-on in the Add-on Manager. Now extra messages about the Simulator's operation will appear in the Browser Console.

- -

Criar o Simulador

- -

If you'd like to test patches to the Gecko or Gaia code that the Simulator contains, you may be interested in modifying the simulator to use a custom Gecko build or Gaia profile. Alternatively, you can build a new Simulator from your Gecko checkout.

- -

Alternativas

- -

Different ways to run Gaia — including a list of them in order of ease for running and reverse order of closeness to the shipped product (according to it, Firefox OS Simulator is easiest but furthest).

diff --git "a/files/pt-pt/archive/b2g_os/utilizar_o_gestor_de_aplicac\303\265es/index.html" "b/files/pt-pt/archive/b2g_os/utilizar_o_gestor_de_aplicac\303\265es/index.html" deleted file mode 100644 index 96d59b7659..0000000000 --- "a/files/pt-pt/archive/b2g_os/utilizar_o_gestor_de_aplicac\303\265es/index.html" +++ /dev/null @@ -1,283 +0,0 @@ ---- -title: Utilizar o Gestor de Aplicações -slug: Archive/B2G_OS/Utilizar_o_Gestor_de_Aplicacões -translation_of: Archive/B2G_OS/Using_the_App_Manager ---- -
-

Importante: O Gestor de Aplicações deverá ser considerado desaprovado; o trabalho para remover o código do Gestor de Aplicações do Firefox já foi iniciado (consultar {{bug("1007061")}}), e se em vez disso, já utilizar WebIDE, a menos que tenha uma boa razão para o não fazer.

-
- -
-

The App Manager is a tool for Firefox Desktop which provides a number of useful tools to help developers test, deploy and debug HTML5 web apps on Firefox OS phones & Simulator, directly from Firefox browser. This page documents how to use the App Manager.

- -

App Manager is available for Firefox OS 1.2 or later, lower versions are supported in Firefox OS 1.1 Simulator. The App Manager is being replaced by the WebIDE, starting from Firefox 33. The WebIDE provides all the features of the App Manager and also features an editing environment to create and develop Firefox OS apps.

-
- -

{{EmbedYouTube("z1Bxg1UJVf0")}}

- -

The App Manager is composed of:

- - - -

Quick setup

- -

This section is designed to get you up and running as soon as possible; if you need some more detail please skip forward to the {{ anch("Device and system configuration") }} section and start reading from there.  Also see the {{ anch("Troubleshooting") }} section for help if you are having trouble.

- -
    -
  1. Make sure you have Firefox Desktop 26+ installed
    2. -
  2. Open the App Manager (in the URL bar, type about:app-manager, or go to Tools > Web Developer > App Manager in your Firefox menu.) This should appear in a new browser tab.
    3. -
  3. If you don't have a real device: -
      -
    1. Install the Firefox OS Simulator add-on, then go back to the App Manager tab of your browser.
      2. -
    2. In App Manager's bottom toolbar, click on Start Simulator, then click on the name of the installed simulator, which should appear there.
      3. -
    -
    4. -
  4. If you have a real device: -
      -
    1. Make sure your device is running Firefox OS 1.2+
      2. -
    2. On Windows, make sure to install the drivers provided by your phone manufacturer
      3. -
    3. In the Settings of your device, disable Screen Lock (Settings > Phone lock > Lock Screen) and enable Remote Debugging (Settings > Device information > More information > Developer)
      4. -
    4. Install the ADB Helper add-on in Firefox Desktop
      5. -
    5. Connect your device to your machine via a USB cable
      6. -
    6. You should see the name of your device in the App Manager's bottom bar. Click on it.
      7. -
    -
    5. -
  5. The bottom bar should show "Connected to: xxx"
    6. -
  6. Click on the Apps panel and add an app (packaged or hosted)
    7. -
  7. The Refresh button validates your app and installs it on the Simulator/Device
    8. -
  8. The Debug button connects the developer tools to the running app
    9. -
  9. See the {{ anch("Troubleshooting") }} section for help if you are having trouble
    10. -
- -

Device and system configuration

- -

The first thing you'll need to do when using the App Manager is make sure your system and phone are set up correctly. This section will run through all the steps required.

- -

Firefox OS 1.2+ required

- -

Make sure your device is running Firefox OS 1.2/Boot2Gecko 1.2 or higher. To check which version of Firefox OS the device is runing, go to Settings > Device Information > Software.

- -

If you don't have a high enough version installed, depending on what phone you have you will need to either install an available nightly build of Firefox 1.2+, or configure and build it yourself from source.

- -

Builds available:

- - - -
-

Note: To build your own Firefox OS 1.2+ distribution, follow the instructions located at Building and installing Firefox OS, starting with Firefox OS build prerequisites.

-
- -

Remote debugging

- -

Next, you need to enable remote debugging in Firefox OS. To do so, go to Settings > Device information > More information > Developer and check the Remote Debugging checkbox.

- -

ADB or ADB helper

- -

The process uses the Android Debug Bridge (ADB) to handle the device-computer connection and communication. There are two options for running ADB:

- - -
-

Note: There's no need to run this command if you installed the ADB Helper Add-on.

-
- -

Connecting your device to the App Manager

- -

With all your configuration done, it's now time to plug your device into your computer and start the App Manager:

- -
    -
  1. Plug the device into your computer via USB.
    2. -
  2. Disable Screen lock on your device by going to Settings > Screen Lock and unchecking the Lock Screen checkbox. This is a good idea because when the screen gets locked, the phone connection gets lost, meaning it is no longer available for debugging.
    3. -
  3. Start the App Manager — In Firefox Desktop select the Tools > Web Developer > App Manager menu option, or type about:app-manager in the URL bar.
    4. -
  4. At the bottom of the App Manager tab, you will see a connection status bar (see screenshot below). You should be able to connect your device by clicking the "Connect to localhost:6000" button.
    5. -
  5. If this works successfully, a prompt should appear on your device: "An incoming request to permit remote debugging connection was detected. Allow connection?". Tap the OK button (You may also have to press the power button on the phone so you can see the prompt.) The connection status bar should update to say "Connected to B2G", with a Disconnect button available to press if you want to cancel the connection.
    6. -
- -

- -
-

Note: The other controls in the connection status bar allow you to connect a simulator to the App Manager, which we cover in the next section, below, and change the port that the connection happens on. If you change the port, you'll also need to enable port forwarding for this port as well, as instructed in the {{anch("Enable port forwarding")}} section, above.

-
- -

Using a Firefox OS Simulator Add-on

- -

If you haven't got a real device available to use with App Manager, you can still try it out using a Firefox OS Simulator Add-on. To start off, install the simulator with the following button (multiple versions are available; you are advised to install them all, for maximum flexibility):

- -

Install Simulator

- -

Once you've installed the simulator(s), you need to go to about:app-manager to see the connection status bar at the bottom of the App Manager tab, and click the "Start simulator" button. At least three buttons will appear:

- - - -
-

Note: The Firefox OS 1.5 Simulator has been removed, as 1.5 was changed to 2.0. If you have the Firefox OS 1.5 Simulator installed, it won't automatically update to 2.0, so you should uninstall 1.5 and install 2.0 instead. The Firefox OS 2.0 simulator will then automatically update.

-
- -
-

Note: The Firefox OS 1.2 Simulator has been removed, as no phones are likely to be released with version 1.2 installed — this version is therefore of limited value, and it makes more sense to spend your time debugging on other versions.

-
- -

Running custom builds in the App Manager

- -

Note that you can run custom B2G Desktop and Gaia/Gecko builds in the App Manager via the simulator. Read Running custom Firefox OS/Gaia builds in the App Manager for instructions on how to do this.

- -

Apps panel: Test and debug Firefox OS apps

- -

Now that everything is working, let's review the functionality available inside the App Manager, starting with the Apps panel. From here, you can import an existing app to push onto your device, for testing and debugging:

- - - -

Information about your app should appear on the right hand side of the window, as seen below:

- -

- -

Manifest editor

- -

From Firefox 28 onwards, the Apps Panel includes an editor for the app manifest:

- -

- -

Debugging

- -

Clicking on "Update" will update (install) the app on the device. Clicking on "debug" will connect a toolbox to the app, allowing you to debug its code directly:

- -

- -
-

You'll enjoy playing around with the toolbox — try altering the DOM, CSS etc. and you'll see the updates reflected on the device in realtime. Such updates will be saved on the installed app code; you'll see them next time you open the app on the device.

-
- -

Before Firefox 28, the tools are launched in a separate window. From Firefox 28 onwards, the tools are launched in a separate tab in the App Manager itself, alongside the Apps and Device tabs. The tab is given your app's icon so it's easy to find:

- -

- -

Errors

- -

If an app was not added successfully — for example if the URL was incorrect, or you selected a packaged app folder — an entry will be added to the page for this app, but this will include error information.

- -

- -

You can also delete an app from this view, by hovering over the App name/description on the left of the window, and pressing the "X" button that appears in each case. This however doesn't remove the app from the device. To do that you need to manually remove the app using the device itself.

- -

Device panel

- -

The Device tab displays information about the connected device. From the "Installed Apps" window, apps on the device can be started and debugged.

- -

- -
-

Note: Certified Apps are not listed by default. See how to debug certified apps.

-
- -

The "Permissions" window shows the required privileges for different Web APIs on the current device:

- -

- -

Finally, you can take a screenshot of the current device display by clicking the "Screenshot" button. The screenshot appears in a new tab on Firefox, and from there you can save or discard it as you wish.

- -

Debugging Certified Apps

- -

Currently only devices running a development build of Firefox OS 1.2+ are capable of debugging certified apps. If you have a development build, you can enable certified app debugging by changing the pref devtools.debugger.forbid-certified-apps to false in your profile. To do this, follow the steps below:

- -

Using a real device

- -
    -
  1. -

    On your computer, enter the following command in Terminal/console to enter your device's filesystem via the shell:

    - - 
    adb shell
    - -

    Your prompt should change to root@android.

    -
    2. -
  2. -

    Next, stop B2G running using the following command:

    - - 
    stop b2g
    -
    3. -
  3. -

    Navigate to the following directory:

    - - 
    cd /data/b2g/mozilla/*.default/
    -
    4. -
  4. -

    Here, update the prefs.js file with the following line:

    - - 
    echo 'user_pref("devtools.debugger.forbid-certified-apps", false);' >> prefs.js
    -
    5. -
  5. -

    After you've finished editing and saving the file, start B2G again using the following command:

    - - 
    start b2g
    -
    6. -
  6. -

    Exit the android filesystem using the exit command; this will return you to your normal terminal prompt.

    -
    7. -
  7. -

    Next, reconnect to the App Manager and you should see certified apps appear for debugging.

    -
    8. -
- -

Using the B2G desktop client

- -

With the B2G desktop client, the preference is already defined in your profile in greprefs.js, located at the root of your B2G desktop client folder. Stop your B2G desktop client and edit the file to turn the devtools.debugger.forbid-certified-apps preference to false. Then restart the B2G client and connect the App Manager. You should now see all applications.

- -
-

Note: If you want to add this preference to your Gaia build you can run make DEVICE_DEBUG=1 reset-gaia.

-
- -

Troubleshooting

- -

If the device is not recognized:

- - - -

Can't connect your device to the App Manager or start the simulator? Let us know or file a bug. and

diff --git a/files/pt-pt/archive/css3/index.html b/files/pt-pt/archive/css3/index.html deleted file mode 100644 index 5cabcb8ebd..0000000000 --- a/files/pt-pt/archive/css3/index.html +++ /dev/null @@ -1,1090 +0,0 @@ ---- -title: CSS3 -slug: Archive/CSS3 -tags: - - CSS - - Precisa de Tradução - - Referencia -translation_of: Archive/CSS3 ---- -

CSS3 is the latest evolution of the Cascading Style Sheets language and aims at extending CSS2.1. It brings a lot of long-awaited novelties, like rounded corners, shadows, gradients, transitions or animations, as well as new layouts like multi-columns, flexible box or grid layouts. Experimental parts are vendor-prefixed and should either be avoided in production environments, or used with extreme caution as both their syntax and semantics can change in the future.

- -

Módulos e processo de uniformização

- -

CSS Level 2 needed 9 years, from August 2002 to June 2011 to reach the Recommendation status. This was due to the fact that a few secondary features held back the whole specification. In order to accelerate the standardization of non-problematic features, the CSS Working Group of the W3C, in a decision referred as the Beijing doctrine, divided CSS in smaller components called modules . Each of these modules is now an independent part of the language and moves towards standardization at its own pace. While some modules are already W3C Recommendations, other still are early Working Drafts. New modules are also added when new needs are identified.

- -

CSS Modules and Snapshots as defined since CSS3 Formally, there is no CSS3 standard per se . Each module being standardized independently, the standard CSS consists of CSS2.1 amended and extended by the completed modules, not necessary all with the same level number. At each point of time, a snapshot of the CSS standard can be defined, listing CSS2.1 and the mature modules.

- -

The W3 consortium periodically publishes such snapshots, like in 2007, 2010, 2015, 2017, and 2018.

- -

Though today no module with a level greater than 3 is standardized, this will change in the future. Some modules, like Selectors 4 or CSS Borders and Backgrounds Level 4 already have an Editor's Draft, though they haven't yet reached the First Published Working Draft status.

- -

Estado dos módulos CSS

- -

Módulos concluídos

- -

A few CSS modules already became a standard as a W3C Recommendation. These should be no more changes.

- - - - - - - - - - - -
{{ SpecName("CSS3 Colors", "", "") }}{{ Spec2("CSS3 Colors") }} since June 7th, 2011
-

Adds the {{ cssxref("opacity") }} property, and the hsl(), hsla(), rgba() and rgb() functions to create {{cssxref("<color>")}} values. It also defines the currentColor keyword as a valid color.

- -

The transparent color is now a real color (thanks to the support for the alpha channel) and is a now an alias for rgba(0,0,0,0.0).

- -

It deprecates the system-color keywords that shouldn't be used in a production environment anymore.

-
- - - - - - - - - - - -
{{ SpecName("CSS3 Namespaces", "", "") }}{{ Spec2("CSS3 Namespaces") }} since September 29th, 2011
-

Adds the support for the XML Namespaces by defining the notion of CSS qualified name, using the ' | ' syntax and adding the {{ cssxref("@namespace") }} CSS at-rule.

-
- - - - - - - - - - - -
{{ SpecName("CSS3 Selectors", "", "") }}{{ Spec2("CSS3 Selectors") }} since September 29th, 2011
-

Adds:

- -
    -
  • Substring matching attribute selectors, E[attribute^="value"], E[attribute$="value"], E[attribute*="value"] .
    • -
  • New pseudo-classes: {{ cssxref(":target") }}, {{ cssxref(":enabled") }} and {{ cssxref(":disabled") }}, {{ cssxref(":checked") }}, {{ cssxref(":indeterminate") }}, {{ cssxref(":root") }}, {{ cssxref(":nth-child") }} and {{ cssxref(":nth-last-child") }}, {{ cssxref(":nth-of-type") }} and {{ cssxref(":nth-last-of-type") }}, {{ cssxref(":last-child") }}, {{ cssxref(":first-of-type") }} and {{ cssxref(":last-of-type") }}, {{ cssxref(":only-child") }} and {{ cssxref(":only-of-type") }},{{ cssxref(":empty") }}, and {{ cssxref(":not") }}.
    • -
  • Pseudo-elements are now characterized by two colons rather than one: :after becomes {{ cssxref("::after") }}, :before becomes {{ cssxref("::before") }}, :first-letter becomes {{ cssxref("::first-letter") }}, and :first-line becomes {{ cssxref("::first-line") }}.
    • -
  • The new general sibling combinator ( h1~pre ).
    • -
-
- -

The next iteration of the Selectors specification is already in progress, though it still hasn't reached the First Public Working Draft stage.

- - - - - - - - - - - -
{{ SpecName("CSS3 Media Queries", "", "") }}{{ Spec2("CSS3 Media Queries") }} since June 19th, 2012
-

Extends the former media type ( print, screen, … ) to a full language allowing queries on the device media capabilities like only screen and (color) .

- -

Media queries are not only used in CSS document but also in some attributes of HTML Elements, like the {{ htmlattrxref("media","link") }} attribute of the {{ HTMLElement("link") }} element.

-
- -

The next iteration of this specification is in the work, allowing to tailor a Web site regarding the input methods available on the user agent, with new media features like hover or pointer. Detection of EcmaScript support, using the script media features is also proposed.

- - - - - - - - - - - -
{{ SpecName("CSS3 Style", "", "") }}{{ Spec2("CSS3 Style") }} since November 7th, 2013
Formally defines the syntax of the content of the HTML style global attribute.
- - - - - - - - - - - -
{{ SpecName("CSS3 Fonts", "", "") }}{{ Spec2("CSS3 Fonts") }} since September 20th, 2018
-

Amends the CSS2.1 Font matching algorithm to be closer to what is really implemented.

- -

Adds:

- -
    -
  • Support for downloadable fonts via the CSS {{ cssxref("@font-face") }} at-rule.
    • -
  • The control of the contextual inter-glyph spacing via the CSS {{ cssxref("font-kerning") }} property.
    • -
  • The choice of language-specific glyphs via the CSS {{ cssxref("font-language-override") }} property.
    • -
  • The choice of glyphs with specific OpenType features via the CSS {{ cssxref("font-feature-settings") }} property.
    • -
  • The control of the aspect ratio to use when fallback fonts are selected via the CSS {{ cssxref("font-size-adjust") }} property.
    • -
  • The choice of alternative font faces using the CSS {{ cssxref("font-stretch") }}, {{ cssxref("font-variant-alternates") }}, {{ cssxref("font-variant-caps") }}, {{ cssxref("font-variant-east-asian") }}, {{ cssxref("font-variant-ligatures") }}, {{ cssxref("font-variant-numeric") }}, and {{ cssxref("font-variant-position") }} properties. It also extends the related CSS {{ cssxref("font-variant") }} shorthand property and introduces the {{ cssxref("@font-feature-values") }} at-rule.
    • -
  • The control of the automatic generation of an oblique or bold face when none are found via the CSS {{ cssxref("font-synthesis") }} property.
    • -
-
- - - - - - - - - - - -
{{ SpecName("CSS3 Basic UI", "", "") }}{{ Spec2("CSS3 Basic UI") }} since June 21st, 2018
-

Adds:

- -
    -
  • The ability to tweak the box model using the CSS {{ cssxref("box-sizing") }} property.
    - At risk: due to insufficient browser support, standardization of the padding-box value may be postponed to the next iteration of this module.
    • -
  • Allow the styling of forms according their content using the CSS {{ cssxref(":indeterminate") }}, {{ cssxref(":default") }}, {{ cssxref(":valid") }}, {{ cssxref(":invalid") }}, {{ cssxref(":in-range") }}, {{ cssxref(":out-of-range") }}, {{ cssxref(":required") }}, {{ cssxref(":optional") }}, {{ cssxref(":read-only") }}, and {{ cssxref(":read-write") }} pseudo-classes and the {{ cssxref("::value") }}, {{ cssxref("::choices") }}, {{ cssxref("::repeat-item") }}, and {{ cssxref("::repeat-index") }} pseudo-elements.
    - At risk: due to insufficient browser support, standardization of the pseudo-elements {{ cssxref("::value") }}, {{ cssxref("::choices") }}, {{ cssxref("::repeat-item") }}, and {{ cssxref("::repeat-index") }} may be postponed to the next iteration of this module .
    • -
  • Support for icons, defined by the CSS {{ cssxref("icon") }} property simultaneously with the new icon value of the CSS {{ cssxref("content") }} property.
    - At risk: due to insufficient browser support, standardization of the {{ cssxref("icon") }} property and the icon value may be postponed to CSS4.
    • -
  • Support for the CSS {{ cssxref("outline-offset") }} property giving more control on the position of the outline.
    • -
  • Support for the CSS {{ cssxref("resize") }} property allowing Web authors to control if and how elements should be resized.
    • -
  • Support for the CSS {{ cssxref("text-overflow") }} property defining how text overflows, if needed.
    - At risk: due to insufficient browser support, the 2-value syntax of this property as well as the support for {{cssxref("<string>")}} values may be postponed to the next iteration of this module.
    • -
  • The ability to define the hotspot of a cursor as well as the new none, context-menu, cell, vertical-text, alias, copy, no-drop, not-allowed, nesw-resize, nwse-resize, col-resize, row-resize, all-scroll, zoom-in, zoom-out, extending the {{ cssxref("cursor") }} property.
    • -
  • The ability to specify the sequential navigation order (that is the tabbing order ) using the CSS {{ cssxref("nav-index") }}, {{ cssxref("nav-up") }}, {{ cssxref("nav-right") }}, {{ cssxref("nav-left") }}, {{ cssxref("nav-down") }} properties.
    - At risk: due to insufficient browser support, standardization of the navigation properties may be postponed to the next iteration of this module.
    • -
  • The ability to control the usage of an IME editor, using the CSS {{ cssxref("ime-mode") }} property.
    - At risk: due to insufficient browser support, standardization of the {{ cssxref("ime-mode") }} property may be postponed to the next iteration of this module.
    • -
-
- -

An early list of what could be in the next iteration of the CSS Basic User Interface Module is available.

- -

Módulos estáveis

- -

A few CSS modules are already fairly stable and have reached one of the three recommendation level of the CSSWG: Candidate Recommendation, Proposed Recommendation or Recommendation. These can be used without prefix and are pretty stable, though a few features can still be dropped at the Candidate Recommendation stage.

- -

These modules extend and amend the CSS2.1 specification which build the core of the specification. Together with it, they are the current snapshot of the CSS specification.

- - - - - - - - - - - -
{{ SpecName("CSS3 Backgrounds", "", "") }}{{ Spec2("CSS3 Backgrounds") }}
-

Adds:

- -
    -
  • Support, on backgrounds, for any type of {{cssxref("<image>")}}, and not only for uri() defined ones.
    • -
  • Support for multiple background images.
    • -
  • The {{ cssxref("background-repeat") }} space and round values, and for the 2-value syntax of this CSS property.
    • -
  • The {{ cssxref("background-attachment") }} local value.
    • -
  • The CSS {{ cssxref("background-origin") }}, {{ cssxref("background-size") }}, and {{ cssxref("background-clip") }} properties.
    • -
  • Support for curved border corners, with the CSS {{ cssxref("border-radius") }}, {{ cssxref("border-top-left-radius") }}, {{ cssxref("border-top-right-radius") }}, {{ cssxref("border-bottom-left-radius") }}, and {{ cssxref("border-bottom-right-radius") }} properties.
    • -
  • Support for the use of an {{cssxref("<image>")}} as the border with the CSS {{ cssxref("border-image") }}, {{ cssxref("border-image-source") }}, {{ cssxref("border-image-slice") }}, {{ cssxref("border-image-width") }}, {{ cssxref("border-image-outset") }}, and {{ cssxref("border-image-repeat") }} properties.
    • -
  • Support for shadows of the element with the CSS {{ cssxref("box-shadow") }} property.
    • -
-
- -

The CSS4 iteration of the Backgrounds and Borders specification is already in progress, though it still hasn't reached the First Public Working Draft stage, it plans to add the ability to clip a border (with the CSS {{ cssxref("border-clip") }}, {{ cssxref("border-clip-top") }}, {{ cssxref("border-clip-right") }}, {{ cssxref("border-clip-bottom") }}, and {{ cssxref("border-clip-left") }} properties) or to control the shape of the border in a corner (using the CSS {{ cssxref("border-corner-shape") }} property).

- - - - - - - - - - - -
{{ SpecName("CSS3 Conditional", "", "") }}{{ Spec2("CSS3 Conditional") }}
Adds features for conditional processing of parts of style sheets, conditioned on capabilities of the browser or the document the style sheet is being applied to. It consists mainly in allowing nested at-rules inside {{ cssxref("@media") }} and the adding of a new CSS at-rule, {{ cssxref("@supports") }}, and a new DOM method {{domxref("CSS.supports()")}}.
- - - - - - - - - - - -
{{ SpecName("CSS3 Multicol", "", "") }}{{ Spec2("CSS3 Multicol") }}
Adds support for easy multi-column layouts using the CSS {{ cssxref("columns") }}, {{ cssxref("column-count") }}, {{ cssxref("column-fill") }}, {{ cssxref("column-gap") }}, {{ cssxref("column-rule") }}, {{ cssxref("column-rule-color") }}, {{ cssxref("column-rule-style") }}, {{ cssxref("column-rule-width") }}, {{ cssxref("column-span") }}, {{ cssxref("column-width") }}, {{ cssxref("break-after") }}, {{ cssxref("break-before") }}, and {{ cssxref("break-inside") }}.
- - - - - - - - - - - -
{{ SpecName("CSS3 Values", "", "") }}{{ Spec2("CSS3 Values") }}
-

Makes initial and inherit keywords usable on any CSS property.

- -

Formally defines the CSS data types of CSS 2.1, that were implicitely defined by their grammar token and some textual precisions.

- -

Adds:

- -
    -
  • Definition for new font-relative length units: rem and ch .
    • -
  • Definition for viewport-relative length units: vw, vh, vmax, and vmin .
    • -
  • Precision about the real size of the absolute length units, which are not really absolute, but defined in relation with the reference pixel .
    • -
  • Definition for {{ cssxref("<angle>") }}, {{cssxref("<time>")}}, {{cssxref("<frequency>")}}, {{cssxref("<resolution>")}}.
    • -
  • Normative value to the definition of {{cssxref("<color>")}}, {{cssxref("<image>")}}, and {{cssxref("<position>")}}.
    • -
  • Definition for the {{ cssxref("calc", "calc()") }}, {{ cssxref("attr", "attr()")}}, and toggle() functional notations.
    - At risk: due to insufficient browser support, standardization of the calc(), attr(), and toggle() functional notations may be postponed to the next iteration of this module.
    • -
-
- -

Several types definition, like <ident> and <custom-ident>, have been deferred to CSS Values and Units Module Level 4.

- - - - - - - - - - - -
{{ SpecName("CSS3 Flexbox", "", "") }}{{ Spec2("CSS3 Flexbox") }}
Add a flexbox layout to the CSS {{ cssxref("display") }} property and several new CSS properties to control it: {{ cssxref("flex") }}, {{ cssxref("flex-align") }}, {{ cssxref("flex-direction") }}, {{ cssxref("flex-flow") }}, {{ cssxref("flex-item-align") }}, {{ cssxref("flex-line-pack") }}, {{ cssxref("flex-order") }}, {{ cssxref("flex-pack") }}, and {{ cssxref("flex-wrap") }}.
- - - - - - - - - - - -
{{ SpecName("CSS3 Cascade", "", "") }}{{ Spec2("CSS3 Cascade") }}
-

Adds:

- -
    -
  • The {{ cssxref("initial") }}, {{ cssxref("unset") }} values for properties.
    • -
  • The CSS {{ cssxref("all") }} property.
    • -
  • The scoping mechanism.
    • -
- -

Clarifies:

- -
    -
  • Interaction of media-dependent @import statements and style sheet loading requirements.
    • -
-
- - - - - - - - - - - -
{{ SpecName("CSS3 Writing Modes", "", "") }}{{ Spec2("CSS3 Writing Modes") }}
Defines the writing modes of both horizontal and vertical scripts and clarifies how the CSS {{ cssxref("direction") }} and {{ cssxref("unicode-bidi") }} properties interact with the new CSS {{ cssxref("text-orientation") }} property, and extends them where needed.
- - - - - - - - - - - -
{{ SpecName("CSS3 Counter Styles", "", "") }}{{ Spec2("CSS3 Counter Styles") }}
- -

Módulos de teste

- - - - - - - - - - - -
{{ SpecName("CSS3 Images", "", "") }}{{ Spec2("CSS3 Images") }}
-

Defines the {{cssxref("<image>")}} data type.

- -

Extends the url() syntax to support image slices using media fragments.

- -

Adds:

- -
    -
  • The dppx unit to the {{cssxref("<resolution>")}} data type.
    • -
  • The image() function as a more flexible alternative to url() to define an image from an url.
    - At risk: due to insufficient browser support, standardization of the image() function may be postponed to the next iteration of this module.
    • -
  • Support for linear-gradient(), repeating-linear-gradient(), radial-gradient() and repeating-radial-gradient().
    • -
  • The ability to define how a replaced element should fit in its element, using the CSS {{ cssxref("object-fit") }} property.
    - At risk: due to insufficient browser support, standardization of the {{ cssxref("object-fit") }} and property may be postponed to the next iteration of this module.
    • -
  • The ability to override the resolution and orientation of an external image using the CSS {{ cssxref("image-resolution") }} and {{ cssxref("image-orientation") }} properties.
    - At risk : due to insufficient browser support, standardization of the {{ cssxref("image-resolution") }} and {{ cssxref("image-orientation") }} properties may be postponed to the next iteration of this module
    • -
-
- -

The CSS Image Values and Replaced Content Level 4 which will supersede CSS Image Level 3 is in development and is a {{Spec2("CSS4 Images")}}.

- - - - - - - - - - - -
{{ SpecName("CSS3 Speech", "", "") }}{{ Spec2("CSS3 Speech") }}
Defines the speech media type, an aural formatting model and numerous properties specific for speech-rendering user agents.
- - - - - - - - - - - -
{{ SpecName("CSS3 Text Decoration", "", "") }}{{ Spec2("CSS3 Text Decoration") }}
-

Extends:

- -
    -
  • the CSS {{ cssxref("text-decoration") }} property by making it a shorthand for the CSS {{ cssxref("text-decoration-line") }}, {{ cssxref("text-decoration-color") }}, and {{ cssxref("text-decoration-style") }} properties. And adds the {{ cssxref("text-decoration-skip") }}, and {{ cssxref("text-underline-position") }} properties.
    • -
- -

Adds:

- -
    -
  • Support for East-Asian-script emphasis marks with the CSS {{ cssxref("text-emphasis") }}, {{ cssxref("text-emphasis-style") }}, {{ cssxref("text-emphasis-color") }}, and {{ cssxref("text-emphasis-position") }} properties.
    • -
  • Support for script shadows with the CSS {{ cssxref("text-shadow") }} property.
    • -
- -

Clarifies:

- -
    -
  • The paint order of the decorations.
    • -
- -

At risk: due to insufficient browser support, standardization of the text-decoration-skip, line positioning rules and the ability to place both emphasis marks and ruby above the same base text may be postponed to the next iteration of this module.

-
- - - - - - - - - - - -
{{ SpecName("CSS Shapes", "", "") }}{{ Spec2("CSS Shapes") }}
Defines geometric shapes, which can be applied to floats. These shapes describe areas, around which inline content wraps instead of wrapping around the bounding box.
- - - - - - - - - - - -
{{ SpecName("CSS Masks", "", "") }}{{ Spec2("CSS Masks") }}
Defines a way for partially or fully hiding portions of visual elements. It describes how to use another graphical element or image as a luminance or alpha mask.
- - - - - - - - - - - -
{{ SpecName("CSS3 Fragmentation", "", "") }}{{ Spec2("CSS3 Fragmentation") }}
Defines how partitions of a Web page should happen, that is page, column breaks, and widows and orphans handling. -

Adds:

- -
    -
  • Support for defining the behavior of decorations, that is borders and background colors or images, when a box is breaked (at a page, column or line-break) with the CSS {{ cssxref("box-decoration-break") }} property.
    • -
-
- - - - - - - - - - - -
{{ SpecName("CSS3 Variables", "", "") }}{{ Spec2("CSS3 Variables") }}
Defines a mechanism allowing to define variables in CSS.
- - - - - - - - - - - -
{{ SpecName("Compositing", "", "") }}{{ Spec2("Compositing") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Syntax", "", "") }}{{ Spec2("CSS3 Syntax") }}
Clarifies how charsets are determined; minor changes in parsing and tokenization algorithms.
- - - - - - - - - - - -
{{ SpecName("CSS3 Grid", "", "") }}{{ Spec2("CSS3 Grid") }}
Add a grid layout to the CSS display property and several new CSS properties to control it: {{cssxref("grid")}}, {{cssxref("grid-area")}}, {{cssxref("grid-auto-columns")}}, {{cssxref("grid-auto-flow")}}, {{cssxref("grid-auto-position")}}, {{cssxref("grid-auto-rows")}}, {{cssxref("grid-column")}}, {{cssxref("grid-column-start")}}, {{cssxref("grid-column-end")}}, {{cssxref("grid-row")}}, {{cssxref("grid-row-start")}}, {{cssxref("grid-row-end")}}, {{cssxref("grid-template")}}, {{cssxref("grid-template-areas")}}, {{cssxref("grid-template-rows")}}, and {{cssxref("grid-template-columns")}}.
- - - - - - - - - - - -
{{ SpecName("CSS3 Display", "", "") }}{{ Spec2("CSS3 Display") }}
- - - - - - - - - - - -
{{ SpecName("CSS Will Change", "", "") }}{{ Spec2("CSS Will Change") }}
- - - - - - - - - - - -
{{ SpecName("CSS4 Media Queries", "", "") }}{{ Spec2("CSS4 Media Queries") }}
- - - - - - - - - - - -
{{ SpecName("Geometry Interfaces", "", "") }}{{ Spec2("Geometry Interfaces") }}
- - - - - - - - - - - -
{{ SpecName("CSS4 Cascade", "", "") }}{{ Spec2("CSS4 Cascade") }}
- - - - - - - - - - - -
{{SpecName("CSS Scroll Snap Points")}}{{Spec2("CSS Scroll Snap Points")}}
- - - - - - - - - - - -
{{SpecName('CSS Painting API')}}{{Spec2('CSS Painting API')}}
- - - - - - - - - - - -
{{SpecName('CSS Containment')}}{{Spec2('CSS Containment')}}
- - - - - - - - - - - -
{{SpecName('CSS4 Writing Modes')}}{{Spec2('CSS4 Writing Modes')}}
- -

Modules in the refining phase

- -

Specifications that are deemed to be in the refining phase are already fairly stable. Though changes are still expected, they shouldn't create incompatibilities with current implementations; they should mainly define behavior in edge cases.

- - - - - - - - - - - -
{{ SpecName("CSS3 Animations", "", "") }}{{ Spec2("CSS3 Animations") }}
Allows the definition of animations effects by adding the CSS {{ cssxref("animation") }}, {{ cssxref("animation-delay") }},{{ cssxref("animation-direction") }}, {{ cssxref("animation-duration") }}, {{ cssxref("animation-fill-mode") }}, {{ cssxref("animation-iteration-count") }}, {{ cssxref("animation-name") }}, {{ cssxref("animation-play-state") }}, and {{ cssxref("animation-timing-function") }} properties, as well as the {{ cssxref("@keyframes") }} at-rule.
- - - - - - - - - - - -
{{ SpecName("Web Animations", "", "") }}{{ Spec2("Web Animations") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Text", "", "") }}{{ Spec2("CSS3 Text") }}
-

Extends:

- -
    -
  • the CSS {{ cssxref("text-transform") }} property with the value full-width.
    • -
  • the CSS {{ cssxref("text-align") }} property with the value start, end, start end, and match-parent for a better support of documents with multiple directionalities of text.
    • -
  • the CSS {{ cssxref("text-align") }} property with a {{cssxref("<string>")}} value to align on that character. This is useful to align number on the decimal point.
    • -
  • the CSS {{ cssxref("word-spacing") }} and {{ cssxref("letter-spacing") }} properties with range constraints to control flexibility in justification.
    • -
- -

Adds:

- -
    -
  • Control on how whitespaces are displayed using the CSS {{ cssxref("text-space-collapse") }} and {{ cssxref("tab-size") }} properties.
    • -
  • Control on line breaks and word boundaries using the CSS {{ cssxref("line-break") }}, {{ cssxref("word-break") }}, {{ cssxref("hyphens") }}, {{ cssxref("text-wrap") }}, {{ cssxref("overflow-wrap") }}, and {{ cssxref("text-align-last") }} properties.
    • -
  • Control on how justification is happening, in order to support more type of scripts, using the CSS {{ cssxref("text-justify") }} property.
    • -
  • Control on edge effect using the CSS {{ cssxref("text-indent") }} and {{ cssxref("hanging-punctuation") }} properties.
    • -
-
- -

A few features present in early CSS Text Level 3 draft have being postponed to the next iteration of this module .

- - - - - - - - - - - -
{{ SpecName("CSS3 Transforms", "", "") }}{{ Spec2("CSS3 Transforms") }}
-

Adds:

- -
    -
  • the support of bi-dimensional transforms to be applied to any element using the CSS {{ cssxref("transform") }} and {{ cssxref("transform-origin") }} properties. The supported transforms are: matrix(), translate(), translateX(), translateY(), scale(), scaleX(), scaleY(), rotate(), skewX(), and skewY().
    • -
  • the support of tri-dimensional transforms to be applied to any element by adding the CSS {{ cssxref("transform-style") }}, {{ cssxref("perspective") }}, {{ cssxref("perspective-origin") }}, and {{ cssxref("backface-visibility") }} properties and extended the {{ cssxref("transform") }} property with the following transforms are: matrix 3d(), translate3d(), translateZ(), scale3d(), scaleZ(), rotate3d(), rotateX(), rotateY(), rotateZ(), and perspective().
    • -
- -

Note: this specification is a merge of CSS 2D-Transforms, CSS 3D-Transforms and SVG transforms.

-
- - - - - - - - - - - -
{{ SpecName("CSS3 Transitions", "", "") }}{{ Spec2("CSS3 Transitions") }}
Allows the definition of transitions effects between two properties values by adding the CSS {{ cssxref("transition") }}, {{ cssxref("transition-delay") }}, {{ cssxref("transition-duration") }}, {{ cssxref("transition-property") }}, and {{ cssxref("transition-timing-function") }} properties.
- - - - - - - - - - - -
{{ SpecName("CSS3 Box Alignment", "", "") }}{{ Spec2("CSS3 Box Alignment") }}
- - - - - - - - - - - -
{{ SpecName("CSS4 Selectors", "", "") }}{{ Spec2("CSS4 Selectors") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Lists", "", "") }}{{ Spec2("CSS3 Lists") }}
Extends the list counter mechanism so that list markers can be styled and Web developers can define new list counter schemes.
- - - - - - - - - - - -
{{ SpecName("Motion Path Level 1", "", "") }}{{ Spec2("Motion Path Level 1") }}
- - - - - - - - - - - -
{{ SpecName("CSS4 Fonts", "", "") }}{{ Spec2("CSS4 Fonts") }}
- - - - - - - - - - - -
CSS Easing Functions Level 1Working Draft
- - - - - - - - - - - -
{{ SpecName("CSS Logical Properties", "", "") }}{{ Spec2("CSS Logical Properties") }}
- -

Modules in the revising phase

- -

Modules that are in the revising phase are much less stable than those in the refining phase. Often the syntax is still under scrutiny and may evolve a lot, in a non-compatible way. Alternative syntaxes are tested and often implemented.

- - - - - - - - - - - -
{{ SpecName("CSS3 Paged Media", "", "") }}{{ Spec2("CSS3 Paged Media") }}
- - - - - - - - - - - -
{{ SpecName("CSSOM View", "", "") }}{{ Spec2("CSSOM View") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Sizing", "", "") }}{{ Spec2("CSS3 Sizing") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Ruby", "", "") }}{{ Spec2("CSS3 Ruby") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Overflow", "", "") }}{{ Spec2("CSS3 Overflow") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Box", "", "") }}{{ Spec2("CSS3 Box") }}
- - - - - - - - - - - -
{{ SpecName("CSS Scrollbars", "", "") }}{{ Spec2("CSS Scrollbars") }}
- -

Modules in the exploring phase

- - - - - - - - - - - -
CSS Backgrounds and Borders Level 4Working Draft
- - - - - - - - - - - -
{{ SpecName("CSS3 Device", "", "") }}{{ Spec2("CSS3 Device") }}
Adds a new at-rule, {{ cssxref("@viewport") }}, allowing to specify the size, zoom factor, and orientation of the viewport that is used as the base for the initial containing block.
- - - - - - - - - - - -
{{ SpecName("CSS Exclusions", "", "") }}{{ Spec2("CSS Exclusions") }}
Extends the floats mechanism to define exclusion regions in any positioning scheme. Adds the notion of shapes, in which content must flows.
- - - - - - - - - - - -
{{ SpecName("Filters 1.0", "", "") }}{{ Spec2("Filters 1.0") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 GCPM", "", "") }}{{ Spec2("CSS3 GCPM") }}
Adds the ability to tailor printed version of a document by allowing to control header, footer but also references tables like indexes or tables of content.
- - - - - - - - - - - -
CSS Page FloatsWorking Draft
- - - - - - - - - - - -
{{ SpecName("CSS3 Template", "", "") }}{{ Spec2("CSS3 Template") }}
- - - - - - - - - - - -
{{ SpecName("CSS Line Grid", "", "") }}{{ Spec2("CSS Line Grid") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Positioning", "", "") }}{{ Spec2("CSS3 Positioning") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Regions", "", "") }}{{ Spec2("CSS3 Regions") }}
Defines a new mechanism allowing content to flow across, eventually non-contiguous, multiple areas called regions.
- - - - - - - - - - - -
{{ SpecName("CSSOM", "", "") }}{{ Spec2("CSSOM") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Font Loading", "", "") }}{{ Spec2("CSS3 Font Loading") }}
- - - - - - - - - - - -
{{ SpecName("CSS Scope", "", "") }}{{ Spec2("CSS Scope") }}
- - - - - - - - - - - -
{{ SpecName("CSS3 Inline", "", "") }}{{ Spec2("CSS3 Inline") }}
- - - - - - - - - - - -
{{ SpecName("CSS4 Images", "", "") }}{{ Spec2("CSS4 Images") }}
-

Extends:

- -
    -
  • the image() functional notation to describe the directionality of the image (rtl or ltr), allowing for bidi-sensitive images.
    • -
  • the {{ cssxref("image-orientation") }} property by adding the keyword from-image, allowing to follow EXIF data stored into images to be considered.
    • -
- -

Adds:

- -
    -
  • the image-set() functional notation to allow the definition to equivalent images at different resolution allowing for resolution-negotiated selection of images.
    • -
  • the element() functional notation allowing the use of part of the page as image.
    • -
  • the cross-fade() functional notation allowing to refer to intermediate images when transitioning between two images and defines the interpolation between two images.
    • -
  • the conic-gradient() and repeating-conic-gradient() functional notation describing a new type of gradient.
    • -
  • the {{cssxref("image-rendering")}} property that allow to define how resize of the object should be handled.
    • -
-
- -

Modules in the rewriting phase

- -

Modules that are in the rewriting phase are outdated and require to be rewritten. The syntax is still under scrutiny and may evolve a lot, in a non-compatible way. Alternative syntaxes are tested and often implemented.

- - - - - - - - - - - -
{{ SpecName("CSS3 Content", "", "") }}{{ Spec2("CSS3 Content") }}
- -

Abandoned modules

- - - - - - - - - - - -
{{ SpecName("CSS Non-element Selectors", "", "") }}{{ Spec2("CSS Non-element Selectors") }}
diff --git a/files/pt-pt/archive/devtools_api_social/index.html b/files/pt-pt/archive/devtools_api_social/index.html deleted file mode 100644 index 68ab1e2393..0000000000 --- a/files/pt-pt/archive/devtools_api_social/index.html +++ /dev/null @@ -1,213 +0,0 @@ ---- -title: Utilizar Firefox Devtools com a API Social -slug: Archive/Devtools_API_Social -translation_of: Archive/Social_API_Devtools ---- -

O Firefox tem um número de ferramentas de desenvolvimento que podem ser utilizadas para ajudar com o desenvolvimento dos provedores de API Social. Contudo, até que o bug 839959 termine, o processo não é tão simples como deveria ser. Enquanto isso, esta página descreve algumas soluções alternativas.

- -

Ativar Devtools do Chrome

- -

Both of the techniques below require the chrome devtools to be manually enabled. To do this, open about:config in a tab, and after verifying that you will be careful, toggle the boolean value devtools.chrome.enabled to true.

- -

Utilizar o Inspetor de DOM e Profiler

- - - -
// Uncomment one of the following lines. NOTE: You must ensure the element you
-// want to inspect has been created - e.g., the sidebar must be visible, the flyouts
-// must have been opened once, etc.
-
-// The sidebar
-let w = document.getElementById("social-sidebar-browser").contentWindow;
-
-// The "flyout" panel
-// let w = document.getElementById("social-flyout-panel").firstChild.contentWindow;
-
-// The "notification" panel - this will show the most-recently-used panel
-// let w = document.getElementById("social-notification-panel").firstChild.contentWindow;
-
-
-if (!w) {
-    alert("This window is yet to be created");
-} else {
-    XPCOMUtils.defineLazyModuleGetter(this, "Toolbox",
-      "resource:///modules/devtools/Toolbox.jsm");
-    XPCOMUtils.defineLazyModuleGetter(this, "TargetFactory",
-      "resource:///modules/devtools/Target.jsm");
-    let target = TargetFactory.forWindow(w);
-    let toolbox = gDevTools.getToolbox(target);
-    toolbox ? toolbox.destroy() : gDevTools.showToolbox(target, undefined, "window");
-}
- - - -

Utilizar o 'Depurador' com os elementos sociais.

- - - -
// want to inspect has been created - eg, the sidebar must be visible, the flyouts
-// must have been opened once, etc.
-
-// The sidebar:
-let w = document.getElementById("social-sidebar-browser").contentWindow;
-
-// The "flyout" panel.
-// let w = document.getElementById("social-flyout-panel").firstChild.contentWindow
-
-// The "notification" panel - this will show the most-recently-used panel.
-// let w = document.getElementById("social-notification-panel").firstChild.contentWindow;
-
-
-if (!w) {
-    alert("This window is yet to be created");
-} else {
-    XPCOMUtils.defineLazyModuleGetter(this, "Toolbox",
-      "resource:///modules/devtools/Toolbox.jsm");
-    XPCOMUtils.defineLazyModuleGetter(this, "TargetFactory",
-      "resource:///modules/devtools/Target.jsm");
-    let target = TargetFactory.forWindow(w);
-    let toolbox = gDevTools.getToolbox(target);
-    toolbox ? toolbox.destroy() : gDevTools.showToolbox(target, undefined, "window");
-}
- -
// Uncomment one of the following lines.  NOTE: You must ensure the element you
-// want to inspect has been created - eg, the sidebar must be visible, the flyouts
-// must have been opened once, etc.
-
-// The sidebar:
-let w = document.getElementById("social-sidebar-browser").contentWindow;
-
-// The "flyout" panel.
-// let w = document.getElementById("social-flyout-panel").firstChild.contentWindow
-
-// The "notification" panel - this will show the most-recently-used panel.
-// let w = document.getElementById("social-notification-panel").firstChild.contentWindow;
-
-
-if (!w) {
-    alert("This window is yet to be created");
-} else {
-    XPCOMUtils.defineLazyModuleGetter(this, "Toolbox",
-      "resource:///modules/devtools/Toolbox.jsm");
-    XPCOMUtils.defineLazyModuleGetter(this, "TargetFactory",
-      "resource:///modules/devtools/Target.jsm");
-    let target = TargetFactory.forWindow(w);
-    let toolbox = gDevTools.getToolbox(target);
-    toolbox ? toolbox.destroy() : gDevTools.showToolbox(target, undefined, "window");
-}
- -
// Uncomment one of the following lines.  NOTE: You must ensure the element you
-// want to inspect has been created - eg, the sidebar must be visible, the flyouts
-// must have been opened once, etc.
-
-// The sidebar:
-let w = document.getElementById("social-sidebar-browser").contentWindow;
-
-// The "flyout" panel.
-// let w = document.getElementById("social-flyout-panel").firstChild.contentWindow
-
-// The "notification" panel - this will show the most-recently-used panel.
-// let w = document.getElementById("social-notification-panel").firstChild.contentWindow;
-
-
-if (!w) {
-    alert("This window is yet to be created");
-} else {
-    XPCOMUtils.defineLazyModuleGetter(this, "Toolbox",
-      "resource:///modules/devtools/Toolbox.jsm");
-    XPCOMUtils.defineLazyModuleGetter(this, "TargetFactory",
-      "resource:///modules/devtools/Target.jsm");
-    let target = TargetFactory.forWindow(w);
-    let toolbox = gDevTools.getToolbox(target);
-    toolbox ? toolbox.destroy() : gDevTools.showToolbox(target, undefined, "window");
-}
- -
// Uncomment one of the following lines.  NOTE: You must ensure the element you
-// want to inspect has been created - eg, the sidebar must be visible, the flyouts
-// must have been opened once, etc.
-
-// The sidebar:
-let w = document.getElementById("social-sidebar-browser").contentWindow;
-
-// The "flyout" panel.
-// let w = document.getElementById("social-flyout-panel").firstChild.contentWindow
-
-// The "notification" panel - this will show the most-recently-used panel.
-// let w = document.getElementById("social-notification-panel").firstChild.contentWindow;
-
-
-if (!w) {
-    alert("This window is yet to be created");
-} else {
-    XPCOMUtils.defineLazyModuleGetter(this, "Toolbox",
-      "resource:///modules/devtools/Toolbox.jsm");
-    XPCOMUtils.defineLazyModuleGetter(this, "TargetFactory",
-      "resource:///modules/devtools/Target.jsm");
-    let target = TargetFactory.forWindow(w);
-    let toolbox = gDevTools.getToolbox(target);
-    toolbox ? toolbox.destroy() : gDevTools.showToolbox(target, undefined, "window");
-}
- -
// Uncomment one of the following lines.  NOTE: You must ensure the element you
-// want to inspect has been created - eg, the sidebar must be visible, the flyouts
-// must have been opened once, etc.
-
-// The sidebar:
-let w = document.getElementById("social-sidebar-browser").contentWindow;
-
-// The "flyout" panel.
-// let w = document.getElementById("social-flyout-panel").firstChild.contentWindow
-
-// The "notification" panel - this will show the most-recently-used panel.
-// let w = document.getElementById("social-notification-panel").firstChild.contentWindow;
-
-
-if (!w) {
-    alert("This window is yet to be created");
-} else {
-    XPCOMUtils.defineLazyModuleGetter(this, "Toolbox",
-      "resource:///modules/devtools/Toolbox.jsm");
-    XPCOMUtils.defineLazyModuleGetter(this, "TargetFactory",
-      "resource:///modules/devtools/Target.jsm");
-    let target = TargetFactory.forWindow(w);
-    let toolbox = gDevTools.getToolbox(target);
-    toolbox ? toolbox.destroy() : gDevTools.showToolbox(target, undefined, "window");
-}
- -
// Uncomment one of the following lines.  NOTE: You must ensure the element you
-// want to inspect has been created - eg, the sidebar must be visible, the flyouts
-// must have been opened once, etc.
-
-// The sidebar:
-let w = document.getElementById("social-sidebar-browser").contentWindow;
-
-// The "flyout" panel.
-// let w = document.getElementById("social-flyout-panel").firstChild.contentWindow
-
-// The "notification" panel - this will show the most-recently-used panel.
-// let w = document.getElementById("social-notification-panel").firstChild.contentWindow;
-
-
-if (!w) {
-    alert("This window is yet to be created");
-} else {
-    XPCOMUtils.defineLazyModuleGetter(this, "Toolbox",
-      "resource:///modules/devtools/Toolbox.jsm");
-    XPCOMUtils.defineLazyModuleGetter(this, "TargetFactory",
-      "resource:///modules/devtools/Target.jsm");
-    let target = TargetFactory.forWindow(w);
-    let toolbox = gDevTools.getToolbox(target);
-    toolbox ? toolbox.destroy() : gDevTools.showToolbox(target, undefined, "window");
-}
diff --git a/files/pt-pt/archive/firefox_os/index.html b/files/pt-pt/archive/firefox_os/index.html deleted file mode 100644 index 591f6946fa..0000000000 --- a/files/pt-pt/archive/firefox_os/index.html +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Firefox OS -slug: Archive/Firefox_OS -tags: - - NeedsTranslation - - TopicStub -translation_of: Archive/B2G_OS ---- -

This page lists archived content for the Firefox OS product, and the open source project it is based on, B2G OS. For current B2G OS material, see the B2G OS page.

- -

{{SubpagesWithSummaries}}

diff --git a/files/pt-pt/archive/index.html b/files/pt-pt/archive/index.html deleted file mode 100644 index ebdf47390c..0000000000 --- a/files/pt-pt/archive/index.html +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Arquivo de conteúdo obsoleto -slug: Archive -tags: - - Arquivo - - Landing -translation_of: Archive ---- -

{{QuickLinksWithSubpages("/pt-PT/docs/Archive", 2, 0, 1)}}

- -

Aqui na MDN, nós tentamos evitar a eliminação imediata de conteúdo que pode ser útil para pessoas que segmentam plataformas legadas, sistemas operativos, e navegadores. Talvez o seu público alvo sejam pessoas que estão a utilizar hardware mais antigo, por exemplo, e não podem atualizar para os navegadores mais recentes e melhores. Ou, por "motivos", a sua empresa precisa de utilizar um software muito antigo e você precisa de criar um conteúdo da Web que seja executado nesse software. Ou talvez esteja apenas curioso sobre o histórico de uma funcionaldiade ou API obsoleta, e como esta funcionou.

- -

Existem muitas razões pelas quais a documentação antiga pode ser útil. Então, nós estabelecemos esta área na qual podemos arquivar a documentação antiga. O material nesta zona de conteúdo 'Arquivado' não deve ser utilizado para criar novos sites da Web ou aplicações para os navegadores modernos. Está aqui apenas para referência histórica.

- -
-

Nota para autores: nós precisamos de tentar manter as subpáginas aqui organizadas, em vez de serem todas colocadas numa pasta grande. Tente criar subárvores para categorias de material. Além disso, mova apenas as páginas que são extremamente obsoletas. Se alguém puder realisticamente precisar da informação num produto vivo, pode não ser apropriado movê-la aqui. Em geral, pode ser melhor discutir isso no canal MDN Web Docs antes de mover conteúdo para aqui.

-
- -

{{SubpagesWithSummaries}}

- - diff --git a/files/pt-pt/archive/mdn/index.html b/files/pt-pt/archive/mdn/index.html deleted file mode 100644 index 9e550840e3..0000000000 --- a/files/pt-pt/archive/mdn/index.html +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: MDN Archive -slug: Archive/MDN -tags: - - Archive - - MDN - - NeedsTranslation - - TopicStub -translation_of: Archive/MDN ---- -

{{MDNSidebar}}

- -
-

Obsolete
- This documentation is obsolete.

-
- -

The documentation listed below is archived, obsolete material about MDN itself.

- -

{{LandingPageListSubpages}}

diff --git a/files/pt-pt/archive/meta_docs/conteudo_mdn_em_webplatform.org/index.html b/files/pt-pt/archive/meta_docs/conteudo_mdn_em_webplatform.org/index.html deleted file mode 100644 index 29379105c4..0000000000 --- a/files/pt-pt/archive/meta_docs/conteudo_mdn_em_webplatform.org/index.html +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Conteúdo MDN em WebPlatform.org -slug: Archive/Meta_docs/Conteudo_MDN_em_WebPlatform.org -translation_of: Archive/Meta_docs/MDN_content_on_WebPlatform.org ---- -

Web Platform Docs (WPD) é um site para a documentação e educação sobre os padrões da Web, mantido por W3C e apoiado pela Mozilla, entre outros. Anyone is welcome to contribute content from MDN to WebPlatform.org, under the terms of MDN's Creative Commons Share-Alike 2.5 (CC-BY-SA) license. Content that originates from MDN must be attributed to MDN, with a link to the source article. The Web Platform Docs site provides support for doing this in a systematic way.

- -

If you create an account on WPD and create a new page, you’ll see that there is an option in the "new page" form to indicate that the content you’re contributing came from MDN, and to provide the original URL on MDN. There is also a way on WPD to mark sections of articles as coming from MDN, for cases where they get merged into CC-BY content. (CC-BY is the default license for reuse on WPD.) The External Attribution page on WebPlatform.org describes how to do all of that.

- -

Questões?

- -
-
Sobre a MDN ou o seu conteúdo
-
Publique-o no fórum de discussão da MDN, ou pergunte em #mdn on irc.mozilla.org.
-
Sobre os termos da licença da Mozilla
-
Envie uma mensagem para licensing@mozilla.org.
-
Sobre os 'Documentos da Plataforma da Web', o seu conteúdo, a sua licença, ou os seus termos de utilização
-
Publique-os na lista de endereços (discussão) public-webplatform, mantida por W3C, pu pergunte em #webplatform on irc.freenode.org.
-
diff --git a/files/pt-pt/archive/meta_docs/escrever_conteudo/index.html b/files/pt-pt/archive/meta_docs/escrever_conteudo/index.html deleted file mode 100644 index e2d9caad57..0000000000 --- a/files/pt-pt/archive/meta_docs/escrever_conteudo/index.html +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Escrever conteúdo -slug: Archive/Meta_docs/Escrever_conteudo -tags: - - MDN -translation_of: Archive/Meta_docs/Writing_content ---- -

There are always things that can be added or updated on MDN. Whether it's all-new documentation for a sparkling new API or a revision to an older API that's changed subtly, you'll find lots of opportunities to help.

- -

Editar uma página existente

- -

If you've found a page you'd like to revise, simply click the "edit" button at its top right corner. This will open the WYSIWYG editor for working on the page's contents. See the MDN editor guide for details on how to work with the editor, as well as how to work with the macro system we use to help automate the construction and formatting of content.

- -

There are lots of reasons you might edit an existing page:

- - - -

Adicionar uma nova página

- -

This is the big one! Adding a new page to MDN makes the Web love you and want to hug you. There are several obvious reasons to create a new page, including to document an API that's not yet documented or to add a new tutorial or guide on a topic.

- -

There are some ways to go about creating a new page on MDN, once you've logged in:

- -
-
Click a "missing page" link
-
As you browse MDN, you'll occasionally find links to pages that don't exist yet. Often, as we create articles, we include links to pages that need to be created, even if they haven't been made yet. This helps us keep track of things that need to eventually be done, although sometimes it takes some time to get back to them. You should feel free to do so! Just click these links and you'll be taken straight into the editor for the new page.
-
Create a subpage
-
Near the top-right corner of each article is a "Advanced" drop-down menu. In that menu is a "New sub-page" option. Clicking that option opens the page editor for a new page whose parent page in the site hierarchy is the page on which you chose "New sub-page". Simply fill out the title and slug and start writing the article's content.
-
Create a clone
-
You can also clone an existing page using the "Clone this page" option in the "This page" drop-down menu. Clicking this option makes a copy of the current page, whose parent page is the same as the current page, and opens the editor on that page, where you can set the page's title and slug, as well as edit the content of the page. This is typically a good way to add a new page to an existing reference area of the site, for example, because it gets you a sample layout for the content.
-
Create a link to a page that doesn't exist, then click it
-
This is a bit of a hybrid method. Since every page ought to be linked to from somewhere, you could start by creating a link to the new article by adding it to an existing page, then, after saving that page, you can click the link you just inserted to open an editor for the new article.
-
- -
-

Note: If you're not logged in, you will get a 404 error when trying to visit an article that doesn't exist, instead of being offered an editor for a new page.

-
- -

Encontrar informação

- -

There's a lot of information out there, and it can be tricky to hunt down the exact help you need. Here are some tips to get you started.

- -
-
Module owner lists
-
Mozilla projects work on a "module owner" basis; each major component has an owner or owners who are responsible for what goes on there. These owners are often your best source of information — or at least a great way to find the right person to talk to.
-
Mozilla source cross-reference
-
MXR, the Mozilla cross-reference, lets you access all the source code for the Mozilla project (with the exception of some things, like much of Firefox OS, which is located on GitHub). The code and its comments are often a great resource for information.
-
Mozilla wiki
-
The Mozilla wiki — often referred to as "wikimo" — is a repository of process and design notes, drafts, plans, and preliminary specifications. Despite being often a cluttered mess, it's a treasure trove of invaluable information.
-
diff --git a/files/pt-pt/archive/meta_docs/index.html b/files/pt-pt/archive/meta_docs/index.html deleted file mode 100644 index 52de2c8447..0000000000 --- a/files/pt-pt/archive/meta_docs/index.html +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: MDN "meta-documentation" archive -slug: Archive/Meta_docs -tags: - - Archive - - MDN - - NeedsTranslation - - TopicStub -translation_of: Archive/Meta_docs ---- -

Here you'll find archived "meta-documentation"; that is, documentation about how to write documentation on MDN. The articles here are obsolete and should no longer be referenced; we are retaining them here for reference while we migrate some content to new places, but very little of this is useful.

-

{{LandingPageListSubpages}}

diff --git a/files/pt-pt/archive/meta_docs/trello/index.html b/files/pt-pt/archive/meta_docs/trello/index.html deleted file mode 100644 index ba96cd940a..0000000000 --- a/files/pt-pt/archive/meta_docs/trello/index.html +++ /dev/null @@ -1,101 +0,0 @@ ---- -title: Trello -slug: Archive/Meta_docs/Trello -tags: - - Guía - - Metadados MDN - - Processos - - Trello -translation_of: Archive/Meta_docs/Trello ---- -

The MDN community uses a Trello board to organize and keep track of the things that need to be done to improve, update, and add to our content. This guide will help you learn what Trello is and how we use it.

- -
-

The Trello-based process has been replaced with a new process, using a platform called Taiga. Please see MDN's agile process to learn more.

-
- -

Having a tool like this to maintain a public task list lets our entire community participate in planning, and helps everyone understand what we're working on. That way, both MDN staff writers and our amazing community of volunteer contributors can know what's going on at a glance. Our board is public, meaning that everyone can see it. If you already have an account on Trello, you can star (favorite/bookmark) the board so that you can get to it quickly whenever you connect to Trello.

- -

Introdução ao Trello

- -

The Trello software is a Web application (created by Trello, Inc.) which you can access using your Web browser or an app on your mobile device (Android, iOS, Kindle Fire, and Windows 8 are among the supported platforms). This lets you check or update the Trello board at your convenience. For more information, you can read their "about" page.

- -

O quadro do Trello

- -

A board is composed of lists, and each list is composed of cards. Every card represents an "action item", which is a task that needs to be accomplished. You can add comments, due dates, detailed lists of sub-tasks, etc. on every card. But most importantly, you can drag and drop a card from a list to another, which means the task has changed status; for instance, you might drag a card from the "Doing" column to the "Review needed" column, which indicates that you've finished the task and would like for someone to review your work.

- -

Screenshot of the MDN content Trello board.

- -

Listas

- -

A list is a set of cards; while you can assign whatever meaning you wish to each column, the MDN team uses each column to represent the status of the task. The farther to the right the column is, the closer to complete the task is. This is similar to the método GTD ou a metodologia Kanban.

- -

We have the following primary lists (other lists may crop up temporarily from time to time):

- -
-
A Aguardar
-
The tasks here have been accepted as something that need to be done, but are not currently being actively worked on. When work begins on a task, it should advance to the next column.
-
Ações
-
The tasks in this column are actively being worked on.
-
Precisa de Revisão
-
The tasks in this list have been completed but the writer(s) would like someone to review the work to ensure that it's accurate and/or stylistically/grammatically.
-
Sem atualizações nos últimos 14 dias
-
Bugs in this list have been languishing with no new information for more than two weeks. These bugs are in danger of being moved back into the On Hold list unless their status is updated soon.
-
Concluído em...
-
We create lists of bugs created in specific months to help us track our rate of progress and to be able to provide achievement lists
-
- -

Lists are simply are a collection of cards with a title, used to organize cards.

- -

Fichas

- -

A card has much more content in it. As mentioned earlier, a card corresponds to a specific task or project. The card is described by its title which is displayed on the "front" of the card when you're looking at the board. Clicking on a card "flips" the card, showing you a panel with additional details. The detail view looks something like this:

- -

- -

A visualizaçao detalhada de uma ficha tem estas secções:

- -
-
1. Membros
-
The members of the board that are assigned to this task/card. These are the Trello users that are working on the task in some way. Here, we can see that four people are involved with this task.
-
2. Etiquetas
-
You can think of labels as themes or categories that can apply to more than one list. Here, we can see that this card is related to "Open Web Docs" (a category), "Q1 Delivery" (a planning tag), "Learning Area" (a tag indicating a section of MDN), etc. These labels are used for organizational purposes, but are also helpful for filtering; see {{anch("Filters")}} below.
-
3. Data limite
-
You can add a due date for a card to help with planning. This date can also be used for sorting and filtering. Trello can also be configured to display a calendar showing items that are due in a given time period, but this feature is not currently enabled on the MDN Content Team Status board.
-
4. Conteúdo
-
In this example, the card has a checklist to detail the precise actions that are needed to complete the task. You might also find comments and attachments inside a card. So if someone wants to put a note for this card, one can add a comment and so on. Usually, checklists are used to break down a task in smaller units which do not need to be displayed for everyone on the board.
-
- -

Filtros

- -

If you look back at the first screenshot, you can see that there are a lot of cards. While working on some project, you might want to focus on specific ones (such as those associated with a particular technology or project). To make the board clearer and to find the right cards more efficiently, you can use filters.

- -

For example, if you only want to see the cards representing tasks or projects that are first quarter goals, you can turn on the corresponding filter on the label "Q1 Deliverables" and get this as a result:

- -

- -

Experiment with filters! You can filter on members (to find work being done by specific people), due dates, and more.

- -

Como utilizar o Trello

- -

Every member of the writing staff is a member of this board. In addition, volunteers can easily get access too. See {{anch("Getting involved")}} to learn how.

- -

Once you have access, you can either create cards representing proposed or ongoing projects, and you can add yourself to a card to indicate that you intend to work on that task. You can then update cards with new details such as new comments, attachments, or changes to to-do lists on the cards.

- -

Participar

- -

We encourage you to join us and contribute to these tasks! Pick a task that is described on one of the cards and start working on it. Once you are working on it, you'll need to be able to edit the corresponding card. For this you'll need to have a Trello account, which is free. Then you will need an administrator of the board to add you to the board. To contact an administrator, you can:

- - - -

Consulte também

- - diff --git a/files/pt-pt/archive/mozilla/drag_and_drop/index.html b/files/pt-pt/archive/mozilla/drag_and_drop/index.html deleted file mode 100644 index b963b08118..0000000000 --- a/files/pt-pt/archive/mozilla/drag_and_drop/index.html +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: Drag and Drop -slug: Archive/Mozilla/Drag_and_drop -tags: - - NeedsTranslation - - TopicStub - - XUL -translation_of: Archive/Mozilla/Drag_and_drop ---- -

{{ Next("Drag and Drop JavaScript Wrapper") }}

-

{{ deprecated_header("gecko1.9.1") }}

-
- As of Gecko 1.9.1 (Firefox 3.5), these APIs are officially deprecated the newer, simpler, portable API should be used in their place.
-

This section describes how to implement objects that can be dragged around and dropped onto other objects.

-

The Drag and Drop Interface

-

Many user interfaces allow one to drag particular objects around within the interface. For example, dragging files to other directories, or dragging an icon to another window to open the document it refers to. Mozilla and XUL provide a number of events that can handle when the user attempts to drag objects around.

-

A user can start dragging by holding down the mouse button and moving the mouse. The drag stops when the user releases the mouse. Event handlers are called when the user starts and ends dragging, and at various points in-between.

-

Mozilla implements dragging by using a drag session. When a user requests to drag something that can be dragged, a drag session should be started. The drag session handles updating the mouse cursor and where the object should be dropped. If something cannot be dragged, it should not start a drag session. Because the user generally has only one mouse, only one drag session is in use at a time.

-

Note that drag sessions can be created from within Mozilla itself or from other applications. Mozilla will translate the data being dragged as needed.

-

The list below describes the event handlers that can be called, which may be placed on any element. You only need to put values for the handlers where you need to do something when the event occurs.

-
-
- ondrag {{ Fx_minversion_inline(3) }}
-
- Called periodically throughout the drag and drop operation.
-
- ondraggesture 
-
- Called when the user starts dragging the element, which normally happens when the user holds down the mouse button and moves the mouse. The script in this handler should set up a drag session.
-
- ondragstart {{ Fx_minversion_inline(3) }} 
-
- An alias for ondraggesture; this is the HTML 5 spec name for the event and may be used in HTML or XUL; however, for backward compatibility with older versions of Firefox, you may wish to continue using ondraggesture in XUL.
-
- ondragover 
-
- This event handler is called for an element when something is being dragged over top of it. If the object can be dropped on the element, the drag session should be notified.
-
- ondragenter 
-
- Called for an element when the mouse pointer first moves over the element while something is being dragged. This might be used to change the appearance of the element to indicate to the user that the object can be dropped on it.
-
- ondragexit 
-
- Called for an element when the mouse pointer moves out of an element while something is being dragged. The is also called after a drop is complete so that an element has a chance to remove any highlighting or other indication.
-
- ondragdrop 
-
- This event handler is called for an element when something is dropped on the element. At this point, the user has already released the mouse button. The element can simply ignore the event or can handle it some way, such as pasting the dragged object into itself.
-
- ondragend {{ Fx_minversion_inline(3) }} 
-
- Called when the drag operation is finished.
-
-

There are two ways that drag and drop events can be handled. This first involves using the drag and drop XPCOM interfaces directly. The second is to use a JavaScript wrapper object that handles some of this for you. The code for this wrapper can be found in a file named {{ Source("toolkit/content/nsDragAndDrop.js nsDragAndDrop.js") }} which is contained in the widget-toolkit (or global) package.

-

XPCOM Drag and Drop interfaces

-

Two interfaces are used to support drag and drop. The first is a drag service, nsIDragService and the second is the drag session, nsIDragSession.

-

The nsIDragService is responsible for creating drag sessions when a drag starts, and removing the drag session when the drag is complete. The function invokeDragSession should be called to start a drag inside an ondraggesture event handler. Once this function is called, a drag has started.

-

The function invokeDragSession takes four parameters, as described below:

-
invokeDragSession(element,transferableArray,region,actions)
-
-
-
- element 
-
- A reference to the element that is being dragged. This can be retrieved by getting the property event.target during the event handler.
-
- transferableArray 
-
- An array of nsITransferable objects, one for each item being dragged. An array is used because you might want to drag several objects at once, such as a set of files.
-
- region 
-
- A region used for feedback indication. This should usually be set to null.
-
- actions 
-
- The actions that the drag uses. This should be set to one of the following constants, or several added together. The action can be changed during the drag depending on what is being dragged over.
-
-
-
- nsIDragService.DRAGDROP_ACTION_NONE 
-
-
-
- Used to indicate that no drag is valid.
-
- nsIDragService.DRAGDROP_ACTION_COPY 
-
- The item being dragged should be copied to its dropped location.
-
- nsIDragService.DRAGDROP_ACTION_MOVE 
-
- The item being dragged should be moved to its dropped location.
-
- nsIDragService.DRAGDROP_ACTION_LINK 
-
- A link (or shortcut or alias) to the item being dragged should be created in the dropped location.
-
-
-
-

The interface {{ interface("nsIDragService") }} also provides the function getCurrentSession which can be called from within the drag event handlers to get and modify the state of the drag. The function returns an object that implements {{ interface("nsIDragSession") }}.

-

The interface nsIDragSession is used to get and set properties of the drag that is currently occuring. The following properties and methods are available:

-
-
- canDrop 
-
- Set this property to true if the element the mouse is currently over can accept the object currently being dragged to be dropped on it. Set the value to false if it doesn't make sense to drop the object on it. This should be changed in the ondragover and ondragenter event handlers.
-
- dragAction 
-
- Set to the current action to be performed, which should be one or more of the constants described earlier. This can be used to provide extra feedback to the user.
-
- numDropItems 
-
- The number of items being dragged. For example, this will be set to 5 if five bookmarks are being dragged.
-
- getData(transfer,index) 
-
- Get the data being dragged. The first argument should be an nsITransferable object to hold the data. The second argument, index, should be the index of the item to return.
-
- sourceDocument 
-
- The document where the drag started.
-
- sourceNode 
-
- The DOM node where the drag started.
-
- isDataFlavorSupported(flavor) 
-
- Returns true if the data being dragged contains data of the specified flavor.
-
-

{{ Next("Drag and Drop JavaScript Wrapper") }}

-
-

Original Document Information

- -
diff --git a/files/pt-pt/archive/mozilla/index.html b/files/pt-pt/archive/mozilla/index.html deleted file mode 100644 index 0acec76e6d..0000000000 --- a/files/pt-pt/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 ---- -

These articles are archived, obsolete documents about Mozilla, Gecko, and the process of building Mozilla projects.

-

{{SubpagesWithSummaries}}

diff --git a/files/pt-pt/archive/mozilla/uris_and_urls/index.html b/files/pt-pt/archive/mozilla/uris_and_urls/index.html deleted file mode 100644 index f6a2802999..0000000000 --- a/files/pt-pt/archive/mozilla/uris_and_urls/index.html +++ /dev/null @@ -1,122 +0,0 @@ ---- -title: URIs and URLs -slug: Archive/Mozilla/URIs_and_URLs -tags: - - Guía - - Mozilla - - Necko - - NeedsUpdate -translation_of: Archive/Mozilla/URIs_and_URLs ---- -
-

Aviso: O conteúdo deste artigo pode estar desatualizado. Ultima atualização do artigo original foi em 2002.

-
- -

Resumo

- -

A gestão da rede e dos recursos recuperáveis localmente é uma parte central da Necko. Os recursos são identificados pelo "Uniform Resource Identifier" do URI (Extraído do RFC 2396):

- -
-
-
Uniform
-
Uniformity provides several benefits: it allows different types of resource identifiers to be used in the same context, even when the mechanisms used to access those resources may differ; it allows uniform semantic interpretation of common syntactic conventions across different types of resource identifiers; it allows introduction of new types of resource identifiers without interfering with the way that existing identifiers are used; and, it allows the identifiers to be reused in many different contexts, thus permitting new applications or protocols to leverage a pre-existing, large, and widely-used set of resource identifiers.
-
Resource
-
A resource can be anything that has identity. Familiar examples include an electronic document, an image, a service (e.g., "today's weather report for Los Angeles"), and a collection of other resources. Not all resources are network "retrievable"; e.g., human beings, corporations, and bound books in a library can also be considered resources. The resource is the conceptual mapping to an entity or set of entities, not necessarily the entity which corresponds to that mapping at any particular instance in time. Thus, a resource can remain constant even when its content---the entities to which it currently corresponds---changes over time, provided that the conceptual mapping is not changed in the process.
-
Identifier
-
An identifier is an object that can act as a reference to something that has identity. In the case of URI, the object is a sequence of characters with a restricted syntax.
-
-A URI can be further classified as a locator, a name, or both. The term "Uniform Resource Locator" (URL) refers to the subset of URI that identify resources via a representation of their primary access mechanism (e.g., their network "location"), rather than identifying the resource by name or by some other attribute(s) of that resource. ... The URI scheme defines the namespace of the URI, and thus may further restrict the syntax and semantics of identifiers using that scheme. Although many URL schemes are named after protocols, this does not imply that the only way to access the URL's resource is via the named protocol. Gateways, proxies, caches, and name resolution services might be used to access some resources, independent of the protocol of their origin, and the resolution of some URL may require the use of more than one protocol (e.g., both DNS and HTTP are typically used to access an "http" URL's resource when it can't be found in a local cache).
- -

Em Necko, cada esquema URI é representado por um manipulador de protocolo. Por vezes, um manipulador de protocolo representa mais do que um esquema. O manipulador de protocolos fornece informações e métodos específicos do esquema para criar URIs dos esquemas que apoia. Um dos principais objetivos da Necko é fornecer um suporte de protocolo "plug able". Isto significa que deve ser possível adicionar novos protocolos ao Necko apenas implementando o nsIProtocolHandler e o nsIChannel. Também pode ser necessário implementar um novo urlparser para um novo protocolo, mas isso pode não ser necessário porque Necko já fornece implementações URI que podem lidar com uma série de esquemas, implementando o urlparser genérico definido no RFC 2396.

- -

nsIURI e nsIURL

- -

Num sentido estrito, Necko conhece apenas URLs, URIs pela definição acima são demasiado genéricos para serem devidamente representados dentro de uma biblioteca.

- -

Existem, contudo, duas interfaces que se relacionam vagamente com a distinção entre URI e URL de acordo com a definição acima: nsIURI e nsIURL.

- -

nsIURI representa o acesso a uma forma muito simples e muito genérica de um URL. Falando simplesmente do seu esquema e não esquema, separado por dois pontos, como "about". nsIURL herda de nsIURI e representa o acesso a URLs comuns com esquemas como "http", "ftp", ...

- -

nsSimpleURI

- -

Uma implementação do nsSimpleURI é o nsSimpleURI que é a base para protocolos como "sobre". nsSimpleURI contém setters e getters para o URI e os componentes de um URI: esquema e caminho (não esquema). Não existem suportes pré-escritos para URIs simples, devido à sua estrutura simples.

- -

nsStandardURL

- -

A implementação mais importante do nsIURL é o nsStandardURL, que é a base para protocolos como o http, ftp, ...

- -

Estes esquemas apoiam um sistema hierárquico de nomenclatura, onde a hierarquia do nome é denotada por um "/" delimitador que separa os componentes no caminho. nsStandardURL também contém as facilidades para analisar estes tipos de URLs, para quebrar a especificação do URL nos segmentos mais básicos.

- -

A especificação consiste no path e prepath. O prepath consiste dum esquema e autoridade. A autoridade consiste dum prehost, host e port. O prehost consiste num nome de utilizador e senha. O path consiste em diretório, nome de ficheiro, parametro, query e ref. O nome do ficheiro consiste em filebasename e fileextension.

- -

Se a especificação estiver completamente decomposta, consiste em: esquema, nome de utilizador, palavra-passe, anfitrião (host), port, diretório, nome base de ficheiro, extensão de ficheiro, param, consulta e ref. Juntos, estes segmentos formam a especificação do URL com a seguinte sintaxe:

- -

scheme://username:password@host:port/directory/filebasename.fileextension;param?query#ref

- -

Por razões de desempenho, a especificação completa é armazenada de forma fugida no objecto nsStandardURL com pointers (position e length) para cada segmento básico e para os segmentos mais globais como caminho e pré-hospedeiro, por exemplo.

- -

A Necko fornece urlparsers pré-escritos para esquemas baseados em sistemas de nomenclatura hierárquica.

- -

Escapar

- -

Para processar um URL seguramente é necessário às vezes "escapar" alguns caracteres, para os esconder do processador. Um carácter escaped é codificado como um carácter triplo, que consiste do carácter de percentagem "%" seguido por dois dígitos hexadecimais a representar um byte de código. Por exemplo, "%20" é a codificação escapada do carácter de espaço no US-ASCII.

- -

Para citar o RFC 2396:

- -
A URI is always in an "escaped" form, since escaping or unescaping a completed URI might change its semantics. Normally, the only time escape encodings can safely be made is when the URI is being created from its component parts; each component may have its own set of characters that are reserved, so only the mechanism responsible for generating or interpreting that component can determine whether or not escaping a character will change its semantics. Likewise, a URI must be separated into its components before the escaped characters within those components can be safely decoded.
- -

Isto significa que segmentos de URLs são escapados de forma diferente. Isto é feito através do NS_EscapeURL que faz parte do xpcom, mas começou como parte do Necko. A informação de como escapar cada segmento é guardado numa matriz.

- -

Um string não deve ser escapado mais que uma vez. O Necko não escapa um caráter que já foi escapado, a não ser que é forcado por uma máscara especial que pode ser usado se se sabe que um string não está escapado.

- -

Processar URLs

- -

RFC 2396 define um processador de URL que pode lidar com a sintaxe que é comum à maioria de esquemas de URL que existem atualmente.

- -

Por vezes, é necessária uma análise específica do esquema. Também para ser um pouco tolerante a erros de sintaxe, o analisador tem de saber mais sobre a sintaxe específica dos URLs para esse esquema. Para se manter quase genérico Necko contém três analisadores para as principais classes de URLs padrão. Qual deles tem de ser utilizado é definido pela implementação do nsIProtocolhandler para o esquema em questão.

- -

As três classes principais são:

- -
-
Authority
-
Os URLs têm um segmento de autoridade, como "http".
-
NoAuthority
-
Estes URLs não têm um segmento de autoridade, ou têm um degenerado, como o esquema "file". Este parser também pode identificar drives se possível dependendo na plataforma.
-
Standard
-
Não se sabe se existe um segmento de autoridade, menos correção de sintaxe pode ser aplicado neste caso.
-
- -

Diferenças Notáveis

- -
    -
  1. Necko não apoia certos formatos de URLs relativos que estão depreciados, baseado nesta parte do RFC 2396:
    - -
    If the scheme component is defined, indicating that the reference starts with a scheme name, then the reference is interpreted as an absolute URI and we are done. Otherwise, the reference URI's scheme is inherited from the base URI's scheme component. Due to a loophole in prior specifications (RFC1630), some parsers allow the scheme name to be present in a relative URI if it is the same as the base URI scheme. Unfortunately, this can conflict with the correct parsing of non-hierarchical URI. For backwards compatibility, an implementation may work around such references by removing the scheme if it matches that of the base URI and the scheme is known to always use the "hier_part" syntax. The parser can then continue with the steps below for the remainder of the reference components. Validating parsers should mark such a misformed relative reference as an error.
    - -

    Foi decidido não ter compatibilidade com formatos depreciados, portanto URLs como "http:page.html" ou "http:/directory/page.html" são interpretados como URLs absolutos e são corrigidos pelo processador.

    -
    2. -
  2. A gestão dos segmentos de consulta é diferente dos exemplos dados no RFC 2396:
    - -
    Within an object with a well-defined base URI of http://a/b/c/d;p?q the relative URI would be resolved as follows: ... ?y = http://a/b/c/?y ...
    - Em vez disso ?y = http://a/b/c/d;p?y foi implementado como sugerido pelo RFC 1808 mais antigo. Esta decisão é baseada num correio eletrónico de Roy T. Fielding, um dos autores do RFC 2396, afirmando que o exemplo dado está errado. Detalhes podem ser encontrados no bug 90439.
    3. -
  3. Atualmente, os url-objects de Necko apenas apoiam as autoridades de alojamento ou as URLs sem autoridades. Autoridades baseadas em registos como definido no RFC 2396
    - -
    Many URI schemes include a top hierarchical element for a naming authority, such that the namespace defined by the remainder of the URI is governed by that authority. This authority component is typically defined by an Internet-based server or a scheme-specific registry of naming authorities. ... The structure of a registry-based naming authority is specific to the URI scheme, but constrained to the allowed characters for an authority component.
    - -

    não são apoiados.

    -
    4. -
- -

Referencias

- -

 A referência principal para URIs, URLs e URL-parsing é RFC 2396.

- -
-

Informação de Documento Original

- - -
diff --git a/files/pt-pt/archive/mozilla/xbl/index.html b/files/pt-pt/archive/mozilla/xbl/index.html deleted file mode 100644 index f3e30b0280..0000000000 --- a/files/pt-pt/archive/mozilla/xbl/index.html +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: XBL -slug: Archive/Mozilla/XBL -tags: - - XBL -translation_of: Archive/Mozilla/XBL ---- -

XML Binding Language (XBL, as vezes tambem chamado Extensible Bindings Language) é uma linguagem para descrever Bindings que podem ser conectadas a elementos em outros documentos. O elemento ao que o Binding é conectado, chamado de elemento ligado, adquire o comportamento novo especificado pela ligação.

- -

Ligações podem conter manipuladores de eventos que estão registrados no elemento ligado, uma implementação de novos métodos e propriedades que se tornam acessíveis através do elemento ligado, e conteúdo anônimo que é inserido abaixo do elemento ligado.

- -

Muitos XUL widgets são no mínimo parcialmente implantados usando XBL. Você pode desenvolver seus próprios widgets reutilizáveis através de XUL, HTML, SVG, e outros primitivos usando XBL.

- -

Especificações

- -

XBL 1.0 é especificado na XBL 1.0 Reference. Infelizmente a implementação atual no Mozilla é diferente das especificações, e não existe documentação conhecida descrevendo as diferenças. Existe a esperança que a Referência seja atualizada para descrever estas diferenças.

- -

XBL 1.0 é uma tecnologia específica do Mozilla, e não um padrão W3C. Entretanto, no mínimo dois padrões estão sendo desenvolvidos: sXBL and XBL 2.0.but there are

- - - -

Algumas diferenças entre sXBL e XBL2 estão listados em um artigo de Anne van Kesteren.

- -

Veja também

- - - - diff --git a/files/pt-pt/archive/mozilla/xul/comunidade/index.html b/files/pt-pt/archive/mozilla/xul/comunidade/index.html deleted file mode 100644 index a2712cc2a1..0000000000 --- a/files/pt-pt/archive/mozilla/xul/comunidade/index.html +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Comunidade -slug: Archive/Mozilla/XUL/Comunidade ---- -

-

diff --git a/files/pt-pt/archive/mozilla/xul/image/index.html b/files/pt-pt/archive/mozilla/xul/image/index.html deleted file mode 100644 index 5316e18ebd..0000000000 --- a/files/pt-pt/archive/mozilla/xul/image/index.html +++ /dev/null @@ -1,154 +0,0 @@ ---- -title: image -slug: Archive/Mozilla/XUL/image -tags: - - Elementos XUL - - Referência XUL -translation_of: Archive/Mozilla/XUL/image ---- -
- « XUL Reference home [ - Examples | - Attributes | - Properties | - Methods | - Related ] -
- -

Resumo

- -

Um elemento que exibe uma imagem, bem como o elemento img de HTML. O atributo src pode ser utilziado para especificar o URL da imagem.

- -

Está disponível mais informação no Tutorial de XUL.

- -
-
-

Nota: Prior to Gecko 8.0, images did not shrink down with the same ratio in both directions when specifying maximum sizes using maxheight or maxwidth. The new behavior aligns more with the HTML <img> element and shrinks both the width and height down proportionally.

-
-
- -
-
Atributos
-
onerror, onload, src, validate
-
- -
-
Propriedades
-
accessibleType, src
-
- -
-
Classes de estilo
-
alert-icon, error-icon, message-icon, question-icon
-
- -

Exemplos

- -
Image:Firefoxlogo2.png
- -
<image src='Firefoxlogo.png' width='135' height='130'/>
-
- -

Atributos

- -

- - -
-
onerror
-
Type: script code
-
This event is sent to an image element when an error occurs loading the image.
-
-
- - -
-
image.onload
-
Type: script code
-
This event handler will be called on the image element when the image has finished loading. This applies whether the image is applied via the src attribute or the list-style-image style property. If you change the image, the event will fire again when the new image loads. This event will not bubble up the element tree.
-
-
- -
-
- src
-
- Type: URI
-
- The URI of the content to appear in the element.
-
- - -
- - -
-
validate
-
Type: one of the values below
-
This attribute indicates whether to load the image from the cache or not. This would be useful if the images are stored remotely or you plan on swapping the image frequently. The following values are accepted, or leave out the attribute entirely for default handling:
-
-
-
always
-
The image is always checked to see whether it should be reloaded.
-
never
-
The image will be loaded from the cache if possible.
-
-
-
-
- -

Propriedades

- -
-
-
- accessibleType
-
- Type: integer
-
- A value indicating the type of accessibility object for the element.
-
-
- -
-
src
-
Type: URL
-
Gets and sets the value of the src attribute.
-
-

Inherited Properties
align, , allowEvents, , boxObject, builder, , , , className, , , , , collapsed, contextMenu, controllers, database, datasources, dir, , , flex, height, hidden, id, , , left, , maxHeight, maxWidth, menu, minHeight, minWidth, , , , , , , observes, ordinal, orient, , pack, , persist, , , , ref, resource, , , , , statusText, style, ,, tooltip, tooltipText, top, width
- -

Métodos

- - -

Inherited Methods
addEventListener(), appendChild(), blur, click, cloneNode(), compareDocumentPosition, dispatchEvent(), doCommand, focus, getAttribute(), getAttributeNode(), getAttributeNodeNS(), getAttributeNS(), getBoundingClientRect(), getClientRects(), getElementsByAttribute, getElementsByAttributeNS, getElementsByClassName(), getElementsByTagName(), getElementsByTagNameNS(), getFeature, getUserData, hasAttribute(), hasAttributeNS(), hasAttributes(), hasChildNodes(), insertBefore(), isDefaultNamespace(), isEqualNode, isSameNode, isSupported(), lookupNamespaceURI, lookupPrefix, normalize(), querySelector(), querySelectorAll(), removeAttribute(), removeAttributeNode(), removeAttributeNS(), removeChild(), removeEventListener(), replaceChild(), setAttribute(), setAttributeNode(), setAttributeNodeNS(), setAttributeNS(), setUserData
- -

Classes de estilo

- -
-
- alert-icon
-
- Class that adds an alert icon. This typically looks like an exclamation mark. This and the other icon classes may be used by image elements or other elements which can have an image.
-
-
error-icon
-
Class that adds an error icon. This will typically be a red "X" icon.
-
-
message-icon
-
Class that adds a message box icon.
-
-
question-icon
-
Class that adds a question icon, which usually looks like a question mark.
-
- -

Relacionado

- -

See also the image and icon attributes.

- -

Interfaces

- - - -
diff --git a/files/pt-pt/archive/mozilla/xul/index.html b/files/pt-pt/archive/mozilla/xul/index.html deleted file mode 100644 index 3485d951c8..0000000000 --- a/files/pt-pt/archive/mozilla/xul/index.html +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: XUL -slug: Archive/Mozilla/XUL -tags: - - Todas_as_Categorias - - XUL -translation_of: Archive/Mozilla/XUL ---- -

 

- -
Tutorial XUL - -

Um tutorial introdutório ao XUL, originário do XULPlanet.

-
- -
-

A XML User Interface Language (XUL) (em português "linguagem XML de interface de usuário") é a linguagem de interface de usuário da Mozilla baseada na XML que permite construir aplicações multi-plataformas ricas em características que podem rodar ligadas ou desligadas da internet. Essas aplicações são facilmente personalizadas com texto, gráficos e disposições alternativas, fazendo com que possam ser marcadas e localizadas para vários mercados. Desenvolvedores Web que já estejam familiarizados com DHTML irão aprender XUL rapidamente e vão logo poder criar aplicações.

-
- - - - - - - - -
-

Documentação

- -
-
Referência XUL
-
Veja também a documentação MDC em prefwindow.
-
- -
-
Controles XUL
-
Uma rápida lista de todos os controles XUL disponíveis.
-
- -
-
Visão Geral do XUL
-
Descreve as características chave e os componentes do XUL.
-
- -
-
Guia modelo do XUL
-
Um guia detalhado sobre modelos XUL, que é um meio de gerar conteúdo de um código de dados.
-
- -
-
Sobreposições XUL
-
Um artigo sobre sobreposições XUL. Sobreposições são usadas para descrever conteúdo extra para a UI. Ele proporciona um poderoso mecanismo para extender e customizar aplicações XUL existentes.
-
- -

Veja todos...

- 		-

Comunidade

- -

{{ DiscussionList("dev-tech-xul", "mozilla.dev.tech.xul") }}

- - - -

Ferramentas

- - - -

Veja todas...

- -

Tópicos relacionados

- -

JavaScript, CSS, RDF, XBL, Extensões, XULRunner

- -

Categorias

- -

Interwiki Language Links

- -

 

-
diff --git a/files/pt-pt/archive/mozilla/xul/namespaces/index.html b/files/pt-pt/archive/mozilla/xul/namespaces/index.html deleted file mode 100644 index 53bc371053..0000000000 --- a/files/pt-pt/archive/mozilla/xul/namespaces/index.html +++ /dev/null @@ -1,153 +0,0 @@ ---- -title: Espaços de nomes -slug: Archive/Mozilla/XUL/Namespaces -tags: - - Extensões - - Extras -translation_of: Archive/Mozilla/XUL/Namespaces ---- -

 

- -

Em adição a este documento, consulte Namespaces Crash Course.

- -

Espaços de nomes XML fornecem uma maneira para distinguir nomes duplicados de elementos e atributos. Os nomes de elementos e atributos duplicados podem ocorrer quando um documento XML contém elementos e atributos de dois ou mais esquemas XML diferentes (ou DTDs). para citar Wikipédia: "Em geral, um espaço de nome é um recipiente abstrato que fornece contexto para os itens... este contém e permite a desambiguação de itens com o mesmo nome."

- -

If you are familiar with C++ namespaces, Java packages, perl packages, or Python module importing, you are already familiar with the namespace concept.

- -

An XML namespace is identified by an unique name (called a URI, not a URL, even though it can look like a URL). An URI is any string, although most people choose a URL-based URI because URLs are an easy way to hope for uniqueness. Although there's nothing preventing someone else from using the namespace http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul, it's fairly unlikely anyone would choose that accidentally. Even if they did accidentally choose it, they may not define the same elements as XUL anyway (e.g., <textbox/>) in their schema/DTD.

- -

Any element type or attribute name in an XML namespace can be uniquely identified by its XML namespace and its "local name". Together, these two items define a qualified name, or QName.

- -

For example, <xul:textbox/> uses a namespace named "xul" and a local name "textbox". This distinguishes it from, for example, <foobar:textbox/> which might occur in the same document. The xul and foobar namespaces must be defined at the top of the XML document in which they are used, like so:

- -
 <foobar:some-element
-     xmlns:xul="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
-     xmlns:foobar="the-foobar-namespace">
-   <xul:textbox id="foo" value="bar"/>
-   <foobar:textbox favorite-food="pancakes"/>
- </foobar:some-element>
-
- -

Notice I've mixed two <textboxes/> in the same document. The only way to distinguish that they have different meanings is with namespaces.

- -

There's only one other thing to know: "default namespace". Every XML element has a "default namespace", and this is used with XUL elements all the time. In XUL documents, you'll usually see this:

- -
 <window
-     id="foo"
-     xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">
-   ...
-   ...
- </window>
-
- -

and in XHTML documents, you'll see this:

- -
 <html xmlns="http://www.w3.org/1999/xhtml">
-   ...
-   ...
- </html>
-
- -

There is a very subtle difference here than before. Before I wrote xmlns:xul="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul" but here the :xul piece is omitted. This signifies to the XML parser that http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul is the default namespace for the element and its descendant elements (unless further overridden by a default namespace on a descendant element), and that any element without a namespace (i.e., no prefix and colon) belongs to the default namespace. That's why we can write the shorthand <textbox/> instead of <xul:textbox/> in XUL (although the latter is just as correct when not using http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul as the default namespace) -- the XUL namespace is defined as the default on the topmost element. In other words, a default namespace permits a kind of short-hand to be used for all descendants of an element.

- -

Here's a question: what namespace contains the element foo in the XML document below?

- -
  <foo/>
-
- -

The answer is that it's in no namespace, or alternately, it's in the namespace denoted by the empty string:

- -
  <foo xmlns=""/>
-
- -

This second example is semantically equivalent to the first.

- -

Now, a second question: what namespaces are the bar, baz, and quux attributes in?

- -
  <foo bar="value">
-    <element xmlns="namespace!" baz="value">
-      <element quux="value"/>
-    </element>
-  </foo>
-
- -

bar is obviously not in a namespace. What about baz and quux? The answer is that they aren't in a namespace either. In fact no unprefixed attribute is ever in a namespace, primarily because XML originally didn't have namespaces, and all XML from that time had to stay in no namespace. This is a source of perennial confusion for XML namespaces.

- -
- - - - - -
diff --git a/files/pt-pt/archive/mozilla/xul/outros_recursos/index.html b/files/pt-pt/archive/mozilla/xul/outros_recursos/index.html deleted file mode 100644 index fba234096d..0000000000 --- a/files/pt-pt/archive/mozilla/xul/outros_recursos/index.html +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Outros recursos -slug: Archive/Mozilla/XUL/Outros_recursos ---- -

-

diff --git a/files/pt-pt/archive/mozilla/xul/scale/index.html b/files/pt-pt/archive/mozilla/xul/scale/index.html deleted file mode 100644 index fab8882332..0000000000 --- a/files/pt-pt/archive/mozilla/xul/scale/index.html +++ /dev/null @@ -1,235 +0,0 @@ ---- -title: scale -slug: Archive/Mozilla/XUL/scale -tags: - - PrecisaDeConteúdo ---- -

- - « XUL Reference home [ - Examples | - Attributes | - Properties | - Methods | - Related ] - -

Uma escala permite ao usuário selecionar um valor de uma faixa. Uma barra exibida horizontalmente ou verticalmente permite ao usuário selecionar um valor arrastando um ponteiro na barra. -

Use o atributo de orientação para especificar a orientação da escala. O valor padrão é <tt>horizontal</tt>, que exibe uma escala horizontal. Valores pequenos são para a esquerda e valores maiores para a direita. Configure o atributo orient para <tt>vertical</tt> para usar uma escala vertical. -

O usuário pode usar as teclas de flecha para incrementar ou decrementar o valor em uma unidade, ou as teclas de "page up" e "page down" para incrementar ou decrementar uma página, como especificado pelo atributo pageincrement. As teclas "home" e "end" configuram o valor da escala para os valores mínimo e máximo, respectivamente. -

-
Atributos -
disabled, increment, max, min, pageincrement, tabindex, value -
-
Propriedades -
disabled, max, min, increment, pageIncrement, tabIndex, value,
-
Métodos -
decrease, decreasePage, increase, increasePage, -
-

Examples

-

Escala horizontal: -

-
<scale min="1" max="10"/>
-
-

Image:Controlguide-scale.png -

Escala vertical: -

-
<scale min="1" max="10" orient="vertical"/>
-
-

Atributos

-

-

- - -
-
disabled
-
Type: boolean
-
Indicates whether the element is disabled or not. If this attribute is set, the element is disabled. Disabled elements are usually drawn with grayed-out text. If the element is disabled, it does not respond to user actions, it cannot be focused, and the command event will not fire. In the case of form elements, it will not be submitted. Do not set the attribute to true, as this will suggest you can set it to false to enable the element again, which is not the case. - -
The disabled attribute is allowed only for form controls. Using it with an anchor tag (an <a> link) will have no effect.
- -
- The element will, however, still respond to mouse events. To enable the element, leave this attribute out entirely.
-
-
Visible controls have a disabled property which, except for menus and menuitems, is normally preferred to use of the attribute, as it may need to update additional state.
-
- - -
-
- -
-
- increment
-
- Type: integer
-
- The amount by which the curpos (for scroll bars) or value (for number boxes and scale) attribute changes when the arrows are clicked(or scales are dragged). The default value is 1.
-
-
-
- -
-
- min
-
- Type: integer
-
- The minimum value the control's value may take. The default value is 0.
-
-

 

-
-
- -
-
- Type: integer
-
- The maximum value that the scale or number box may be set to. The default value is 100 for scales and Infinity for number boxes.
-
- -

 

-
-
- - -
-
pageincrement
-
Type: integer
-
The amount by which the value of the curpos or value attribute changes when the tray of the scroll bar (the area in which the scroll bar thumb moves) is clicked, or when the page up or page down keys are pressed. The default value is 10.
-
-
-
- - -
-
tabindex
-
Type: integer
-
The tab order of the element. The tab order is the order in which the focus is moved when the user presses the "tab" key. Elements with a higher tabindex are later in the tab sequence.
-
-
-
- - -
-
value
-
Type: string
-
The string attribute allows you to associate a data value with an element. It is not used for any specific purpose, but you can access it with a script for your own use. Be aware, however, that some elements, such as textbox will display the value visually, so in order to merely associate data with an element, you could 1) Use another attribute like "value2" or "data-myAtt" (as in the HTML5 draft), as XUL does not require validation (less future-proof); 2) Use setAttributeNS() to put custom attributes in a non-XUL namespace (serializable and future-proof); 3) Use setUserData() (future-proof and clean, but not easily serializable). For user editable menulist elements, the contents, as visible to the user, are read and set using the Menulist.value syntax. For those elements, setAttribute("value", myValue) and getAttribute("value") do not access or affect the contents displayed to the user.
-
- - - -

 

-
- -

Propriedades

-

-

-
-
- disabled
-
- Type: boolean
-
- Gets and sets the value of the disabled attribute.
-
-
-
-
-
- increment
-
- Type: integer
-
- Gets and sets the value of the increment attribute.
-
-
-
-
- min
-
- Type: integer
-
- Gets and sets the value of the min attribute.
-
-
-
-
- max
-
- Type: integer
-
- Gets and sets the value of the max attribute.
-
-
-
-
- pageIncrement
-
- Type: integer
-
- Gets and sets the value of the pageincrement attribute.
-
-
-
-
- tabIndex
-
- Type: integer
-
- Gets and sets the value of the tabindex attribute.
-
-
-
-
- value
-
- Type: string
-
- Gets and sets the value of the value attribute. For textbox and user editable menulist elements, the contents, as visible to the user, are read and set using the Textbox.value and Menulist.value syntax.
-
- -

 

- -

Métodos

- -

Inherited Methods
addEventListener(), appendChild(), blur, click, cloneNode(), compareDocumentPosition, dispatchEvent(), doCommand, focus, getAttribute(), getAttributeNode(), getAttributeNodeNS(), getAttributeNS(), getBoundingClientRect(), getClientRects(), getElementsByAttribute, getElementsByAttributeNS, getElementsByClassName(), getElementsByTagName(), getElementsByTagNameNS(), getFeature, getUserData, hasAttribute(), hasAttributeNS(), hasAttributes(), hasChildNodes(), insertBefore(), isDefaultNamespace(), isEqualNode, isSameNode, isSupported(), lookupNamespaceURI, lookupPrefix, normalize(), querySelector(), querySelectorAll(), removeAttribute(), removeAttributeNode(), removeAttributeNS(), removeChild(), removeEventListener(), replaceChild(), setAttribute(), setAttributeNode(), setAttributeNodeNS(), setAttributeNS(), setUserData
-
-
- decrease()
-
- Return type: no return value
-
- Decreases the value of the scale or number box by the increment.
-
-
-
- decreasePage()
-
- Return type: no return value
-
- Decreases the value of the scale by the pageincrement.
-
-
-
- increase()
-
- Return type: no return value
-
- Increases the value of the scale or number box by the increment.
-
-
-
- increasePage()
-
- Return type: no return value
-
- Increases the value of the scale by the page increment.
-
- -

Relacionado

-
Interfaces -
nsIDOMXULControlElement -
-

Categorias -

Interwiki Language Links -

diff --git a/files/pt-pt/archive/mozilla/xul/tutorial/adicionar_etiquetas_e_imagens/index.html b/files/pt-pt/archive/mozilla/xul/tutorial/adicionar_etiquetas_e_imagens/index.html deleted file mode 100644 index 7f6d53c292..0000000000 --- a/files/pt-pt/archive/mozilla/xul/tutorial/adicionar_etiquetas_e_imagens/index.html +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: Adicionar Etiquetas e Imagens -slug: Archive/Mozilla/XUL/Tutorial/Adicionar_Etiquetas_e_Imagens -tags: - - Tutoriais - - Tutorial de XUL - - XUL -translation_of: Archive/Mozilla/XUL/Tutorial/Adding_Labels_and_Images ---- -
-

« AnteriorPróxima »

-
- -

Esta secção descreve uma maneira para adicionar etiquetas e imagens a uma janela. Além disso, nós consideramos em como incluir os elementos em grupos.

- -

Elementos de Texto

- -

You cannot embed text directly into a XUL file without tags around it and expect it to be displayed. You can use two XUL elements for this purpose.

- -

Elemento Etiqueta

- -

The most basic way to include text in a window is to use the label element. It should be used when you want to place a descriptive label beside a control, such as a button. An example is shown below:

- -

Example 1 : Source View

- -
<label value="This is some text"/>
-
- -

The value attribute can be used to specify the text that you wish to have displayed. The text will not wrap, so the text will all be displayed on a single line. This syntax is the most common of labels.

- -

If the text needs to wrap, you can place the text content inside opening and closing tags as in the following example:

- -

Example 2 :

- -
<label>This is some longer text that will wrap onto several lines.</label>
-
- -

As with HTML, line breaks and extra whitespace are collapsed into a single space. Later, we'll find out how to constrain the width of elements so that we can see the wrapping more easily.

- -
Atributo de Controle
- -

You can use the control attribute to set which control the label is associated with. When the user clicks on an associated label, that control will be focused. This association is also important for accessibility, so that screen readers read aloud the label for the control as the user tabs to it. Set the value of the control attribute to the id of the element to be focused.

- -

Example 3 : Source View

- -
<label value="Click here:" control="open-button"/>
-<button id="open-button" label="Open"/>
-
- -

In the example above, clicking the label will cause the button to be focused.

- -

Elemento Descrição

- -

For descriptive text not associated with any particular control, you can use the description tag. This element is useful for informative text at the top of a dialog or a group of controls for example. As with the label element, you can either use the value attribute for a single line of text or place text or XHTML content inside opening and closing description tags for longer blocks of text. It is more common to use the attribute syntax for labels, and the text content syntax for descriptions.

- -

Example 4 : Source View

- -
<description>
-  This longer section of text is displayed.
-</description>
-
- -

You can set the text via script using the textContent property, as in the following example:

- -
<description id="text" width="200"/>
-
-document.getElementById('text').textContent = "Some lengthy word wrapped text goes here.";
-
- -

Internally, both the label element and the description elements are the same. The label element is intended for labels of controls, such as text fields. The control attribute is only supported for labels. The description element is intended for other descriptive text such as informative text at the top of a dialog box.

- -

Imagens

- -

XUL has an element to display images within a window. This element is appropriately named image. Note that the tag name is different than HTML (image instead of img). You can use the src attribute to specify the URL of the image file. The example below shows this:

- -
<image src="images/banner.jpg"/>
-
- -

Although you can use this syntax, it would be better in order to support different themes to use a style sheet to set the image URL. A later section will describe how to use style sheets, but an example will be shown here for completeness. You can use the list-style-image CSS property to set the URL for the image. Here are some examples:

- -
XUL:
- <image id="image1"/>
- <image id="search"/>
-
- -
Style Sheet:
- #image1 {
-   list-style-image: url("chrome://findfile/skin/banner.jpg");
- }
-
- #search {
-   list-style-image: url("http://example.com/images/search.png");
- }
-
- -

These images come from within the chrome directory, in the skin for the findfile package. Because images vary by theme, you would usually place images in the skin directory.

- -

In the next section, we will learn how to add some input controls to a window.

- -
-

« AnteriorPróxima »

-
diff --git a/files/pt-pt/archive/mozilla/xul/tutorial/ficheiros_de_propriedade/index.html b/files/pt-pt/archive/mozilla/xul/tutorial/ficheiros_de_propriedade/index.html deleted file mode 100644 index 44657ee360..0000000000 --- a/files/pt-pt/archive/mozilla/xul/tutorial/ficheiros_de_propriedade/index.html +++ /dev/null @@ -1,115 +0,0 @@ ---- -title: Ficheiros de Propriedade -slug: Archive/Mozilla/XUL/Tutorial/Ficheiros_de_propriedade -tags: - - Internacionalização - - Localização - - Tutoriais - - Tutorial de XUL - - XUL -translation_of: Archive/Mozilla/XUL/Tutorial/Property_Files ---- -

 

- -

{{ PreviousNext("XUL Tutorial:Localization", "XUL Tutorial:Introduction to XBL") }}

- -

Num script, não pode ser utilizadas as entities. Em vez disso, são utilizados 'ficheiros de Propriedade'.

- -

Properties

- -

DTD files are suitable when you have text in a XUL file. However, a script does not get parsed for entities. In addition, you may wish to display a message which is generated from a script, if, for example, you do not know the exact text to be displayed. For this purpose, property files can be used.

- -

A property file contains a set of strings. You will find property files alongside the DTD files with a .properties extension. Properties in the file are declared with the syntax name=value. An example is shown below:

- -
notFoundAlert=No files were found matching the criteria.
-deleteAlert=Click OK to have all your files deleted.
-resultMessage=%2$S files found in the %1$S directory.
-
- -

Here, the property file contains three properties. These would be read by a script and displayed to the user.

- -

A property file can also include comments. A line that begins with a hash sign ('#') is treated as a comment:

- -
# This is a comment
-welcomeMessage=Hello, world!
-# This is another comment
-goodbyeMessage=Come back soon!
-
- -

Stringbundles

- -

You could write the code to read properties yourself, however XUL provides the {{ XULElem("stringbundle") }} element which does this for you. The element has a number of functions which can be used to get strings from the property file and get other locale information. This element reads in the contents of a property file and builds a list of properties for you. You can then look up a particular property by name.

- -
<stringbundleset id="stringbundleset">
-<stringbundle id="strings" src="strings.properties"/>
-</stringbundleset>
-
- -

Including this element will read the properties from the file 'strings.properties' in the same directory as the XUL file. Use a chrome URL to read a file from the locale:

- -
<stringbundleset id="stringbundleset">
-<stringbundle id="strings" src="chrome://myplugin/locale/strings.properties"/>
-</stringbundleset>
-
- -

Like other non-displayed elements, you should declare all your stringbundles inside a {{ XULElem("stringbundleset") }} element so that they are all kept together.

- -

Getting a String from the Bundle

- -

This {{ XULElem("stringbundle") }} element has a number of properties. The first is getString which can be used in a script to read a string from the bundle.

- -
var strbundle = document.getElementById("strings");
-var nofilesfound=strbundle.getString("notFoundAlert");
-
-alert(nofilesfound);
-
- - - -

Text Formatting

- -

The next method is getFormattedString(). This method also gets a string with the given key name from the bundle. In addition, each occurrence of formatting code (e.g. %S) is replaced by each successive element in the supplied array.

- -
var dir = "/usr/local/document";
-var count = 10;
-
-var strbundle = document.getElementById("strings");
-var result = strbundle.getFormattedString("resultMessage", [ dir, count ]);
-
-alert(result);
-
- -

This example will display following message in an alert box.

- -
10 files found in the /usr/local/document directory.
-
- -

You will notice the formatting codes %1$S and %2$S is used, and replaced different order in the array. Formatting code %n$S is specify the position of corresponding parameter directly. Although the word order is not the same in all the languages, by using getFormattedString() the specification of the order can be put out the property files.

- -

In case you need to format a string that already contains the percentage character in it (to get something like "50% Off" returned), escape the percentage character with another percentage character, like this:

- -
my.percentage.string = %S%% Off
-
- -

Not escaping the percentage character will generate an incorrect string that strips the space character between the percentage character and the next word of the string ("50%Off").

- -

Non-ASCII Characters, UTF-8 and escaping

- -

Gecko 1.8.x (or later) supports property files encoded in UTF-8. You can and should write non-ASCII characters directly without escape sequences, and save the file as UTF-8 without BOM. Double-check the save options of your text editor, because many don't do this by default. See Localizing extension descriptions for more details.

- -

In some cases, it may be useful or needed to use escape sequences to express some characters. Property files support escape sequences of the form: \uXXXX , where XXXX is a Unicode character code. For example, to put a space at the beginning or end of a string (which would normally be stripped by the properties file parser), use \u0020 .

- -


- In the next section, we will look at XBL, which can be used to define the behavior of an element.

- -

{{ PreviousNext("XUL Tutorial:Localization", "XUL Tutorial:Introduction to XBL") }}

- -

Consulte Também

- - diff --git a/files/pt-pt/archive/mozilla/xul/tutorial/index.html b/files/pt-pt/archive/mozilla/xul/tutorial/index.html deleted file mode 100644 index 8071ee6794..0000000000 --- a/files/pt-pt/archive/mozilla/xul/tutorial/index.html +++ /dev/null @@ -1,142 +0,0 @@ ---- -title: XUL Tutorial -slug: Archive/Mozilla/XUL/Tutorial -tags: - - NeedsTranslation - - TopicStub - - Tutorials - - XUL - - XUL_Tutorial -translation_of: Archive/Mozilla/XUL/Tutorial ---- -

This tutorial describes XUL, the XML User-interface Language. This language was created for the Mozilla application and is used to describe its user interface.

-

Introduction

- -

Simple Elements

- -

The Box Model

- -

More Layout Elements

- -

Toolbars and Menus

- -

Events and Scripts

- -

Document Object Model

- -

Trees

- -

RDF and Templates

- -

Skins and Locales

- -

Bindings

- -

Specialized Window Types

- -

Installation

- -
-

This XUL tutorial was originally created by Neil Deakin. He has graciously given us permission to use it as part of the MDN.

-
-
-

Original Document Information

- -
-

 

diff --git a/files/pt-pt/archive/mozilla/xul/tutorial/modificar_o_tema_predefinido/index.html b/files/pt-pt/archive/mozilla/xul/tutorial/modificar_o_tema_predefinido/index.html deleted file mode 100644 index 9c403175a6..0000000000 --- a/files/pt-pt/archive/mozilla/xul/tutorial/modificar_o_tema_predefinido/index.html +++ /dev/null @@ -1,70 +0,0 @@ ---- -title: Modificar o Tema Predefinido -slug: Archive/Mozilla/XUL/Tutorial/Modificar_o_tema_predefinido -tags: - - Firefox - - Intermediário - - Personalização - - Tutoriais - - Tutorial XUL - - XUL -translation_of: Archive/Mozilla/XUL/Tutorial/Modifying_the_Default_Skin ---- -

{{ PreviousNext("XUL Tutorial:Styling a Tree", "XUL Tutorial:Creating a Skin") }}

- -
-

Esta documentação não foi atualizada para o Firefox Quantum. Support for the userChrome.css file and any of its elements described below are not guaranteed in future versions of Firefox. Using it may lead to hard-to-diagnose bugs or crashes. Use at your own risk!

-
- -

Esta secção descreve como modificar o tema de uma janela.

- -

O Essencial do Tema

- -

A skin is a set of style sheets, images and behaviors that are applied to a XUL file. By applying a different skin, you can change the look of a window without changing its functionality. Firefox provides a skin by default, and you may download others. The XUL for any skins is the same, however the style sheets and images used are different.

- -

For a simple personalized look to a Firefox window, you can easily change the style sheets associated with it. Larger changes can be done by creating an entirely new skin. Firefox has a Theme Manager for changing the default skin. (Although the underlying code for Mozilla calls them skins and the user interface calls them themes, they're both referring to the same thing).

- -

A skin is described using CSS, allowing you to define the colors, borders and images used to draw elements. The file classic.jar contains the skin definitions. The global directory within this archive contains the main style definitions for how to display the various XUL elements. By changing these files, you can change the look of the XUL applications.

- -

Personalizar com userChrome.css

- -

If you place a file called 'userChrome.css' in a directory called 'chrome' inside your user profile directory, you can override settings without changing the archives themselves. This directory should be created when you create a profile and some examples placed there. The file 'userContent.css' customizes Web pages, whereas 'userChrome.css' customizes chrome files.

- -

For example, by adding the following to the end of the file, you can change all {{ XULElem("menubar") }} elements to have a red background.

- -
menubar {
-  background-color: red;
-}
-
- -

If you open any Firefox window after making this change, the menu bars will be red. Because this change was made to the user style sheet, it affects all windows. This means that the browser menu bar, the bookmarks menu bar and even the find files menu bar will be red.

- -

Pacotes de Temas

- -

To have the change affect only one window, change the style sheet associated with that XUL file. For example, to add a red border around the menu commands in the bookmarks manager window, add the following to bookmarksManager.css in the classic.jar or your favorite skin archive.

- -
menuitem {
-  border: 1px solid red;
-}
-
- -

If you look in one of the skin archives, you will notice that each contain a number of style sheets and a number of images. The style sheets refer to the images. You should avoid putting references to images directly in XUL files if you want your content to be skinnable. This is because a particular skin's design might not use images and it may need some more complex design. By referring to the images with CSS, they are easy to remove. It also removes the reliance on specific image filenames.

- -

You can assign images to a button, checkbox and other elements by using the list-style-image property as in the following:

- -
checkbox {
-  list-style-image: url("chrome://findfile/skin/images/check-off.jpg");
-}
-
-checkbox[checked="true"] {
-  list-style-image: url("chrome://findfile/skin/images/check-on.jpg");
-}
-
- -

This code changes the image associated with a checkbox. The first style sets the image for a normal checkbox and the second style sets the image for a checked checkbox. The modifier 'checked=true' makes the style only apply to elements which have their checked attributes set to true.

- -

See also : creating a skin for Firefox and CSS getting started

- -

Na secção seguinte, nós iremos abordar a criação de um novo tema

- -

{{ PreviousNext("XUL Tutorial:Styling a Tree", "XUL Tutorial:Creating a Skin") }}

diff --git a/files/pt-pt/archive/mozilla/xul/tutorial/xbl_bindings/index.html b/files/pt-pt/archive/mozilla/xul/tutorial/xbl_bindings/index.html deleted file mode 100644 index 9b5dd8f99f..0000000000 --- a/files/pt-pt/archive/mozilla/xul/tutorial/xbl_bindings/index.html +++ /dev/null @@ -1,215 +0,0 @@ ---- -title: XBL bindings -slug: Archive/Mozilla/XUL/Tutorial/XBL_bindings -tags: - - 'CSS:Como_começar' -translation_of: Archive/Beginner_tutorials/Using_XBL_from_stylesheets ---- -

{{ PreviousNext("CSS:Como começar:JavaScript", "CSS:Como começar:Interfaces de usuário XUL") }}

- -

Esta página ilustra como o você pode usar as CSS no Mozilla para melhorar a estrutura de aplicações complexas, fazendo o código e recursos mais facilmente reutilizáveis.

- -

Você aplica esta técnica em uma simples demonstração.

- -

Informação: XBL bindings

- -

A estrutura proporcionada pela linguagem de marcação e as CSS não é ideal para aplicações complexas onde partes precisam ser autônomas e reutilizáveis. Você pode colocar folhas de estilo em arquivos separados, e pode também colocar os scripts em arquivos separados. Mas você precisa ligar estes arquivos no documento como um todo.

- -

Outra limitação estrutural concerne ao conteúdo. Você pode usar as CSS para proporcionar conteúdo para elementos selecionados, mas o conteúdo é limitado a textos e imagens, e seu posicionamento é limitado em antes ou depois do elemento selecionado.

- -

Mozilla proporciona um mecanismo que supera estas limitações: XBL (XML Bindings Language). Você pode usar o XBL para ligar elementos selecionados ao próprio:

- - - -

Evitando ligar tudo no nível do documento, você pode fazer as partes autônomas que são fáceis de manter e reutilizar.

- - - - - - - - -
Mais detalhes
Para mais informação sobre XBL bindings, veja a página XBL neste wiki.
- -

Ação: Uma demonstração XBL

- -

Crie um novo documento HTML, doc6.html. Copie e cole o conteúdo daqui:

- -
-
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-
-<HEAD>
-<TITLE>Como Começar Mozilla CSS - Demonstração XBL </TITLE>
-<LINK rel="stylesheet" type="text/css" href="style6.css">
-</HEAD>
-
-<BODY>
-<H1>Demonstração XBL</H1>
-<DIV id="square">Clique Aqui</DIV>
-</BODY>
-
-</HTML>
-
-
- -

Crie um novo arquivo CSS, style6.css. Esta folha de estilo contém o documento de estilo. Copie e cole o conteúdo daqui:

- -
-
/*** Demonstração XBL ***/
-#square {
-  -moz-binding: url("square.xbl#square");
-  }
-
-
- -

Crie um novo arquivo de texto, square.xbl. Este arquivo contém o XBL binding. Copie e cole o conteúdo daqui, tendo certeza de ter rolado a tela para pegar tudo isto:

- -
-
<?xml version="1.0"?>
-<!DOCTYPE bindings>
-<bindings xmlns="http://www.mozilla.org/xbl"
-             xmlns:html="http://www.w3.org/1999/xhtml">
-
-<binding id="square">
-
-  <resources>
-    <stylesheet src="bind6.css"/>
-    </resources>
-
-  <content>
-    <html:div anonid="square"/>
-    <html:button anonid="button" type="button">
-      <children/>
-      </html:button>
-    </content>
-
-  <implementation>
-
-    <field name="square"><![CDATA[
-      document.getAnonymousElementByAttribute(this, "anonid", "square")
-      ]]></field>
-
-    <field name="button"><![CDATA[
-      document.getAnonymousElementByAttribute(this, "anonid", "button")
-      ]]></field>
-
-    <method name="doDemo">
-      <body><![CDATA[
-        this.square.style.backgroundColor = "#cf4"
-        this.square.style.marginLeft = "20em"
-        this.button.setAttribute("disabled", "true")
-        setTimeout(this.clearDemo, 2000, this)
-        ]]></body>
-      </method>
-
-    <method name="clearDemo">
-      <parameter name="me"/>
-      <body><![CDATA[
-        me.square.style.backgroundColor = "transparent"
-        me.square.style.marginLeft = "0"
-        me.button.removeAttribute("disabled")
-        ]]></body>
-      </method>
-
-    </implementation>
-
-  <handlers>
-    <handler event="click" button="0"><![CDATA[
-     if (event.originalTarget == this.button) this.doDemo()
-     ]]></handler>
-    </handlers>
-
-  </binding>
-
-</bindings>
-
-
- -

Crie um novo arquivo CSS, bind6.css. Esta folha de estilo separada contém o estilo para o binding. Copie e cole o conteúdo daqui:

- -
-
/*** Demonstração XBL ***/
-[anonid="square"] {
-  width: 20em;
-  height: 20em;
-  border: 2px inset gray;
-  }
-
-[anonid="button"] {
-  margin-top: 1em;
-  padding: .5em 2em;
-  }
-
-
- -

Abra o documento no seu navegador e pressione o botão.

- -

O wiki não suporta JavaScript nas páginas, então não é possível demonstrar aqui. Deve parecer como isto, antes e depois de você pressionar o botão:

- - - - - - - - -
- - - - - - -
-

Demonstração XBL

-
- 		- - - - - - -
-

Demonstração XBL

-
-
- -

Notas sobre esta demonstração:

- - - - - - - - - - -
Desafios
Mude o arquivo XBL de modo que o quadrado dobre a largura ao mudar de cor, em vez de saltar para a direita. -

Use a ferramenta DOM Inspector para inspecionar o documento, reavaliando o conteúdo adicionado.

-
- -

O que vem depois?

- -

Se você teve dificuldade para entender esta página, ou se você tem algum comentário sobre ela, por favor contribua nesta página de Discussão.

- -

Nesta demonstração, o quadrado e o botão foram widgets independentes que funcionam com um documento HTML. Mozilla tem uma linguagem de marcação especializada para criação de interfaces de usuários. A próxima página demostra isto: Interfaces de usuário XUL

- -

{{ PreviousNext("CSS:Como começar:JavaScript", "CSS:Como começar:Interfaces de usuário XUL") }}

- -

Categorias

- -

Interwiki Language Links

diff --git a/files/pt-pt/archive/normas_web/index.html b/files/pt-pt/archive/normas_web/index.html deleted file mode 100644 index f7debd671a..0000000000 --- a/files/pt-pt/archive/normas_web/index.html +++ /dev/null @@ -1,151 +0,0 @@ ---- -title: Normas da Web -slug: Archive/Normas_Web -tags: - - Normas da Web -translation_of: Archive/Web_Standards ---- -
As normas da Web são cuidadosamente projetadas para distribuir os maiores benefícios para o maior número de utilizadores da Web enquanto assegura a viabilidade a longo prazo de qualquer documento publicado na Web. Projetar e criar com estas normas simplifica e baixa o custo de produção, enquanto distribui sites que estão acessíveis para mais pessoas e mais tipos de dispositivos da Internet. Os sites desenvolvidos com a utilziação destas linhas irão continuar a funcionar corretamente enquanto os navegadores de PCs tradicionais evoluem, e à medida que os novos dispositivos da Internet chegam ao mercado.
- - - - - - - - -
-

Documentação

- -
-
Migrando aplicações do Internet Explorer para o Mozilla
-
Ever have trouble getting your Internet Explorer-specific Web applications to work with Mozilla? This article covers common issues associated with migrating applications to the open source Mozilla-based browser.
-
- -
-
Utilizar as Normas da Web nas suas Páginas da Web
-
This article provides an overview of the process for upgrading the content of your web pages to conform to the W3C web standards.
-
- -
-
Choosing Standards Compliance Over Proprietary Practices
-
In the development world, there is a need for standards because applications are designed across multiple development groups.
-
- -
-
The Business Benefits of Web Standards
-
This article discusses how adhering to web standards, and leaving behind proprietary markup and technologies, can contribute to a company's business goals.
-
- -

Veja todos...

- 		-

Comunidade

- -

{{ DiscussionList("dev-web-development", "mozilla.dev.web-development") }}

- - - -

Ferramentas

- - - -

Veja todas...

- -

Tópicos relacionados

- -
-
CSS, DHTML, HTML, Desenvolvimento da Web, XHTML, XML
-
-
- -
-

 O Projeto de Normas da Web

- -
- - - -
diff --git a/files/pt-pt/archive/plugins/out_of_process_plugins/o_detetor_plugin_hang_detector/index.html b/files/pt-pt/archive/plugins/out_of_process_plugins/o_detetor_plugin_hang_detector/index.html deleted file mode 100644 index c02e3fa0c1..0000000000 --- a/files/pt-pt/archive/plugins/out_of_process_plugins/o_detetor_plugin_hang_detector/index.html +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: O detetor de falhas de plug-ins -slug: Archive/Plugins/Out_of_process_plugins/O_detetor_plugin_hang_detector -tags: - - Extras - - Plug-ins - - Plugins -translation_of: Archive/Plugins/Out_of_process_plugins/The_plugin_hang_detector ---- -

Para ajudar a proteger os utilizadores contra plug-ins e scripts de plug-ins que deixam de responder, o Firefox agora inclui um "detector de falhas", que vigia os plug-ins que deixam de funcionar.

- -

Como é que este funciona

- -

When Firefox makes an NPAPI call to a plugin which is running in its own process, the NPAPI call is translated into an inter-process communication (IPC) request that is posted to the process. Firefox then waits for the response. If a response is not received within a given amount of time (by default, this is 45 seconds), the plugin is assumed to have locked up, and Firefox terminates the plugin by following these steps:

- -
    -
  1. The plugin's process is stopped and a plugin-process "crash" mini-dump is retrieved.
    2. -
  2. A "crash" mini-dump is collected from the main browser process.
    3. -
  3. The plugin's process is terminated.
    4. -
  4. The crashed plugin user interface is displayed; this interface lets the user choose to reload the page and try again.
    5. -
- -

O que ativa o detetor de falhas

- -

There are several possible situations that can trigger the hang detector:

- - - -

O que acontece com o relatório de falhas?

- -

When the hang detector catches a problem, it gathers up the mini-dumps and submits the data to crash-stats, providing handy debugging information to developers so that the problem can be categorized and, if possible, corrected. The advanced query page makes it possible to differentiate between crash reports and hang reports, and lets search results be limited to either the browser process or the plugin process. In addition, the browser hang report and the corresponding plugin hang report are automatically cross-linked for you.

- -

E se eu não quiser terminar a falha de plug-ins?

- -

Sometimes developers may want to prevent hung plugins from being terminated; this could be useful, for example, while debugging script code in Flash or if you're using a debugger that causes event processing to be delayed (such as the Flash debugger).

- -

You can change the timeout period used by the hang detector by changing the value of the dom.ipc.plugins.timeoutSecs preference. The value of this preference indicates the number of seconds an event response must take before the plugin is considered to be hung.

- -

Setting this preference to -1 disables the plugin hang detector entirely.

- -

See about:config on MozillaZine for information on changing preferences like this one.

diff --git "a/files/pt-pt/archive/rss/como_come\303\247ar/como_o_rss_trabalha/index.html" "b/files/pt-pt/archive/rss/como_come\303\247ar/como_o_rss_trabalha/index.html" deleted file mode 100644 index 3473649d08..0000000000 --- "a/files/pt-pt/archive/rss/como_come\303\247ar/como_o_rss_trabalha/index.html" +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Como Funciona o RSS -slug: Archive/RSS/Como_começar/Como_o_RSS_trabalha -tags: - - 'RSS:Como_começar' -translation_of: Archive/RSS/Getting_Started/How_RSS_Works ---- -

Esta página explica como funciona o RSS. Ainda não estará pronto para criar os seus próprios ficheiros RSS, mas estará a aprender sobre os diferentes sistemas que fazem parte do RSS syndication.

- -

Como Funciona o RSS

- -

São dois, os componentes principais que fazem parte do RSS syndication: o servidor e o cliente final.

- -

O servidor é a parte do sistema que produz o feed RSS. Um sistema de notícias ou um sistema de blog estaria no lado servidor do RSS syndication. Um rádio por IP estaria no lado servidor do RSS syndication. Uma TV por IP estaria no lado servidor do RSS syndication.

- -

O cliente é a parte final do RSS syndication que chega ao usuário. O navegador Mozilla Firefox estaria no lado cliente do RSS syndication. Um agregador desktop de RSS estaria no lado cliente do RSS. Um agregador web também estaria no lado cliente do RSS syndication.

- -

{{ PreviousNext("RSS:Como começar:Porque usar RSS", "RSS:Como começar:Sindicar") }}

diff --git "a/files/pt-pt/archive/rss/como_come\303\247ar/index.html" "b/files/pt-pt/archive/rss/como_come\303\247ar/index.html" deleted file mode 100644 index 547a924f4d..0000000000 --- "a/files/pt-pt/archive/rss/como_come\303\247ar/index.html" +++ /dev/null @@ -1,57 +0,0 @@ ---- -title: Como começar -slug: Archive/RSS/Como_começar -tags: - - PrecisaDeRevisãoEditorial - - RSS - - 'RSS:Como_começar' -translation_of: Archive/RSS/Getting_Started ---- -

 

-

Introdução

-

Este tutorial é uma introdução à Really Simple Syndication (RSS).

-

Isto guia-o, passo-a-passo, através do básico do RSS e mostra você trabalhando exemplos em ação. Este tutorial segue o mantra que - - o melhor caminho para aprender é fazer - . Por isso, você deverá criar seus próprios arquivos RSS à mão.

-

Quem deve usar este tutorial?

-

Este tutorial é na maior parte para iniciantes em RSS (i.e., com nenhum ou muito pouca experiência prévia em RSS). Entretanto, estes experimentos com RSS podem também achar este útil como uma ajuda no prenchimento de qualquer informação perdida sobre RSS que não estavam cientes sobre, ou como um guia para "refrescar".

-

Este tutorial assume que você tem alguma experiência com HTML (ou XML) e que você está confortável com os básicos da - - marcação - . Em outras palavras, um código como este não atrapalha você:

-
   Isto é um pouco de marcação com tags <b>bold</b>.
-
-

Se você está confortável com isto, você não deve ter problemas aprendendo RSS.

-
-

NOTA: Se você NÃO é um desenvolvedor web e NÃO que se tornara um, então este tutorial NÃO é para você. Você precisa estar confortável com a criação - - marcação - para estar apto para usar este tutorial efetivamente.

-
-

O que você necessita antes de começar?

-

Para pegar o máximo deste tutorial, você precisará de um editor de texto e um leitor RSS. Você precisa também saber como usar cada um destes.

-
-

NOTA: Um processador de palavras não é um editor de texto. Se um processador de palavras é usado, você DEVE ter certeza de salvar seus arquivos RSS em um (puro e simples) formato de texto.

-
-

Não é obrigatória a criação de arquivos RSS neste tutorial (você pode somente ler), mas isto seria um meio menos eficiente para você aprender. Você reterá mais informação e absorverá melhor se você criar os seus próprios arquivos RSS.

-

Como usar este tutorial

-

Embora cada página neste tutorial tenha sido escrita de modo que que possa agir como um tutorial - - sozinho - , isto assume que você já possuí o conhecimento da informação ensinada nas páginas anteriores deste tutorial. Embora você possa pular para qualquer ponto do tutorial que você deseje, nós sugerimos aos iniciantes em RSS que leiam este tutorial na ordem.

-

Tutorial

-
    -
  1. O que é RSS
    2. -
  2. Porque usar RSS
    3. -
  3. Como o RSS trabalha
    4. -
  4. Hello World (artigo ainda não escrito) link removido porque muitas pessoas colocam seus hello word nele
    5. -
  5. Sindicar
    6. -
  6. Blogs
    7. -
  7. Broadcatching
    8. -
  8. Microformatos
    9. -
  9. Advanced Broadcatching
    10. -
-

Categorias

-

Interwiki Language Links

-

{{ languages( { "en": "en/RSS/Getting_Started", "es": "es/RSS/Primeros_pasos", "fr": "fr/RSS/Premiers_pas", "pl": "pl/RSS/Na_pocz\u0105tek" } ) }}

diff --git "a/files/pt-pt/archive/rss/como_come\303\247ar/o_que_\303\251_rss/index.html" "b/files/pt-pt/archive/rss/como_come\303\247ar/o_que_\303\251_rss/index.html" deleted file mode 100644 index dceb21a856..0000000000 --- "a/files/pt-pt/archive/rss/como_come\303\247ar/o_que_\303\251_rss/index.html" +++ /dev/null @@ -1,242 +0,0 @@ ---- -title: O que é RSS -slug: Archive/RSS/Como_começar/O_que_é_RSS -tags: - - 'RSS:Como_começar' -translation_of: Archive/RSS/Getting_Started/What_is_RSS ---- -

Esta página explica o que é o RSS. Você ainda não criará seus próprios arquivos RSS, mas você verá como o RSS é comumente usado e exemplos simples de arquivos RSS para uso comum. Você também acompanhará um pouco da história do RSS.

- -

O que é RSS?

- -

As versões de RSS mais populares são as baseadas na linguagem de marcação XML usada para publicação (syndication). (Apesar dos formatos RSS baseados em RDF existirem. Os antigos RSS 0.90 e RSS 1.0.) Os usos mais comuns do RSS syndication são para publicações de web sites de notícias, blogs, rádio de Internet e programação televisiva para Internet.

- -

Este tutorial ensina o RSS 2.0. Mas se esforça em apontar as diferenças com as outras versões de RSS.

- -

O RSS é praticamente nunca escrito à mão, mas quase sempre criado por softwares de servidores (normalmente escritos em uma linguagem como PHP, Java, C# ou Python) nos servidores web. Contudo, para que possamos aprender sobre o RSS nós criaremos os scripts RSS à mão.

- -

Uma breve história do RSS

- -

Em março de 1999 a Netscape lançou o RSS 0.90. Era muito diferente do RSS de hoje. Não era realmente um formato para publicação, mas um formato que fornecia um sumário de um website. Na verdade, naquele tempo, o RSS não atendia por Really Simple Syndication mas por Rich Site Summary.

- -

Em julho de 1999 o RSS 0.91 da Netscape foi lançado. Como o RSS 0.90, o RSS 0.91 da Netscape também era de um formato para fornecimento de um sumário de um website e não realmente um formato de publicação (como é hoje). O RSS 0.91 da Netscape foi criado para simplificar as coisas. O RSS 0.90 era baseado em RDF. (O que muitos acharam ser excessivamente complexo). Já o RSS 0.91 da Netscape era apenas baseado em XML e acrescentou um DTD para permitir diversas entities (comumente encontradas em HTML).

- -

E nesse ponto a Netscape tornou o RSS 0.90 baseado em RDF obsoleto e disse a todos que usassem o RSS 0.91 da Netscape que era baseado no XML.

- -

Em junho de 2000 o RSS 0.91 da Userland foi lançado. (E, sim, isso significa que havia 2 diferentes versões de RSS 0.91). A diferença entre as 2 diferentes versões de RSS 0.91 — da Netscape e da Userland — é que a da Userland não possuia o DTD que o Netscape trazia; e por isso, não possuía os entities extras que o Netscape tinha (comumente encontradas em HTML). Fora isso entretanto, eram a mesma coisa. Tecnicamente falando, o RSS 0.91 da Userland era um subset do RSS 0.91 da Netscape.

- -

Em dezembro de 2000 o grupo RSS-DEV lançou o RSS 1.0. Essa versão não era mais puramente baseado em XML, mas baseado em RDF (como o original, e agora obsoleto RSS 0.90). O grupo RSS-DEV mudou o significado de RSS, e transformou-o em RDF Site Summary. (Ao menos, era assim que atendia a versão do RSS deles.)

- -

Então aqui tínhamos o RSS 0.91 da Netscape, o RSS 0.91 da Userland, e o RSS 1.0 do grupo RSS-DEV.

- -

Mais tarde, ainda em dezembro, a Userland lançou o RSS 0.92. O RSS 0.92 deveria substituir o RSS 0.91 deles. (Se você perceber, entretanto, os números das versões dos RSS ficaram bagunçados neste ponto, pois o RSS 0.92 era mais novo que o RSS 1.0.)

- -

E aqui tínhamos o RSS 0.91 da Netscape, o RSS 1.0 do grupo RSS-DEV, e o RSS 0.92 da Userland.

- -

Em abril de 2001 a Userland lançou um beta para o RSS 0.93. Essa versão do RSS nunca foi transformado em "final" e permaneceu beta nunca tornando-se um substituto para o RSS 0.92.

- -

Em agosto de 2002 a Userland lançou o beta do RSS 0.94. E assim como o RSS 0.93, essa versão nunca foi feita "final" e permaneceu beta, nunca tornando-se um substituto para o RSS  RSS 0.92.

- -

Então, aqui ainda tínhamos o RSS 0.91 da Netscape, o RSS 1.0 do grupo RSS-DEV, e o RSS 0.92 da Userland. (Apesar de alguns estarem usando RSS 0.93 e RSS 0.94 mesmo que não devessem.)

- -

Em setembro de 2002 a Userland lança o RSS 2.0. O RSS 2.0 deveria substituir o RSS 0.92 (e os betas RSS 0.93 e RSS 0.94 que ninguém deveria estar usando). A Userland pulou esses números de versão até o 2.0 porque o RSS-DEV já havia usado o 1.0 em seu RSS 1.0 baseado em RDF.

- -

Neste ponto tínhamos o RSS 0.91 da Netscape, o RSS 1.0 do grupo RSS-DEV e o RSS 2.0 da Userland.

- -

Agora, a história não acaba simplesmente lá. Uma vez em novembro de 2002 e outra em janeiro de 2003, o RSS 2.0 foi modificado de sua especificação original pela Userland. E apesar desses serem diferentes, foram todos chamados de RSS 2.0 no elemento <rss>.

- -

E aqui, nesse ponto, nós ainda temos o RSS 0.91 da Netscape (uma vez que a Netscape nunca o tornou obsoleto) apesar da maioria das pessoas não usarem mais. Elas usavam tanto o RSS 1.0 baseado no RDF como o RSS 2.0 baseado no XML. Com o RSS 2.0 baseado no XML parecendo ser o mais popular. (Esse tutorial usa o RSS 2.0.)

- -

Como o RSS é utilizado hoje

- -

Hoje, o RSS é principalmente usado para publicação (syndication). Syndication é o processo de dizer aos outros que você tem conteúdo para eles consumirem. Em outras palavras, quando você publica (syndicate), você está dizendo a todos algo como: "Ei pessoal, eu tenho artigos que gostaria que todos viessem e lessem. Basta se inscrever ao meu RSS feed e você poderá acessar os mais recentes todas as vezes."

- -
-

NOTA: Se você fornecer um RSS não protegido por password, você estará implicitamente dando a todos permissão para usar o conteúdo em seu RSS feed em todos os meios que eles verem que se encaixa. Eles podem ler. Eles podem fazer uma cópia local. Podem compartilhar essa cópia local. Podem pôr em seus websites. Podem até mesmo republicar. E mais.

- -

Se você não quer que nada disso aconteça então não ponha um RSS feed não protegido por password. (E não torne o password público, claro.)

-
- -

Os websites de notícias usam RSS para fornecer a todos uma lista de seus mais recentes artigos. Por exemplo:

- -
        <?xml version="1.0"?>
-
-      <rss version="2.0">
-
-               <channel>
-             <title>Example News Site</title>
-             <description>This is an Example News Site.</description>
-             <lastBuildDate>Wed, 27 Jul 2005 00:30:30 -0700</lastBuildDate>
-             <link>http://news.example.com/</link>
-
-              <item>
-                 <title>News Flash: I Like Bread</title>
-                 <guid isPermaLink="false">4d4a0a12-f188-4c97-908b-eea27213c2fe</guid>
-                 <pubDate>Wed, 27 Jul 2005 00:30:30 -0700</pubDate>
-                 <link>http://news.example.com/artcle/554</link>
-              </item>
-              <item>
-                 <title>Big News Today: Birds Fly</title>
-                 <guid isPermaLink="false">c4a63f09-b45b-466b-8773-6ff264001ab7</guid>
-                 <pubDate>Tue, 19 Jul 2005 04:32:51 -0700</pubDate>
-                 <link>http://news.example.com/artcle/553</link>
-              </item>
-              <item>
-                 <title>Fire is Hot</title>
-                 <guid isPermaLink="false">c1795324-d5ea-44fa-95b1-b5ce2090d4f1</guid>
-                 <pubDate>Sun, 15 May 2005 13:02:08 -0700</pubDate>
-                 <link>http://news.example.com/artcle/552</link>
-              </item>
-              </channel>
-
-      </rss>
- -

Os blogs usam o RSS para fornecer a todos uma lista de seus posts mais novos. Por exemplo:

- -
        <?xml version="1.0"?>
-
-      <rss version="2.0">
-
-              <channel>
-             <title>Joe Blow's Blog</title>
-             <description>This is the Weblog of Joe Blow</description>
-             <lastBuildDate>Sun, 15 May 2005 13:02:08 -0500</lastBuildDate>
-             <link>http://joe-blow.example.net/</link>
-
-              <item>
-                 <title>I Be Blogging...</title>
-                 <guid>http://joe-blow.example.net/log/21</guid>
-                 <pubDate>Sun, 15 May 2005 13:02:08 -0500</pubDate>
-                 <link>http://joe-blow.example.net/log/21</link>
-             </item>
-             <item>
-                 <title>I am so SMRT</title>
-                 <guid>http://joe-blow.example.net/log/20</guid>
-                 <pubDate>Sat, 14 May 2005 22:19:18 -0500</pubDate>
-                 <link>http://joe-blow.example.net/log/20</link>
-             </item>
-             <item>
-                 <title>Huh?</title>
-                 <guid>http://joe-blow.example.net/log/19</guid>
-                 <pubDate>Sat, 14 May 2005 09:55:59 -0500</pubDate>
-                 <link>http://joe-blow.example.net/log/19</link>
-             </item>
-             <item>
-                 <title>Black Cat Spotted</title>
-                 <guid>http://joe-blow.example.net/log/18</guid>
-                 <pubDate>Fri, 13 May 2005 13:13:13 -0500</pubDate>
-                 <link>http://joe-blow.example.net/log/18</link>
-             </item>
-         </channel>
-
-          </rss> 
-
- -

Aqueles que criam Internet Rádio usam o RSS para permitir aos usuários ouvirem seus shows (broadcatching). Por exemplo:

- -
        <?xml version="1.0"?>
-
-      <rss version="2.0">
-
-              <channel>
-             <title>Joe's IPradio Show</title>
-             <description>The best IPradio Show on the Internet, staring Joe!</description>
-             <lastBuildDate>Mon, 15 Aug 2005 16:12:37 -0400</lastBuildDate>
-             <link>http://joe.ipradio.example.net/</link>
-
-              <item>
-                 <title>I C UR Tan Line</title>
-                 <guid>http://joe.ipradio.example.net/show/55</guid>
-                 <pubDate>Mon, 15 Aug 2005 16:11:57 -0400</pubDate>
-                 <enclosure url="http://joe.ipradio.example.net/show/55"
-                            length="4487216"
-                            type="application/ogg"
-                 />
-             </item>
-             <item>
-                 <title>Car Care for Car Fanatics</title>
-                 <guid>http://joe.ipradio.example.net/show/54</guid>
-                 <pubDate>Mon, 8 Aug 2005 13:12:12 -0400</pubDate>
-                 <enclosure url="http://joe.ipradio.example.net/show/54"
-                            length="4892178"
-                            type="audio/x-mp3"
-                 />
-             </item>
-             <item>
-                 <title>Best Beaches in BC</title>
-                 <guid>http://joe.ipradio.example.net/show/53</guid>
-                 <pubDate>Mon, 1 Aug 2005 18:22:14 -0400</pubDate>
-                 <enclosure url="http://joe.ipradio.example.net/show/53"
-                            length="3984215"
-                            type="application/ogg"
-                 />
-             </item>
-         </channel>
-
-          </rss>     
-
- -
-

NOTA: Ouvir um Broadcatching de um Internet Rádio é também chamado de Podcasting, IPradio, e Audio Blogging.

-
- -

Aqueles que criam programas televisivos para Internet usam o RSS para permitir aos usuários transmitir seus shows (broadcatch). Por exemplo:

- -
        <?xml version="1.0"?>
-
-      <rss version="2.0">
-
-              <channel>
-             <title>Kate's IPTV Show</title>
-             <description>Watch it or else!  You know you want to.</description>
-             <lastBuildDate>Tue, 23 Aug 2005 21:02:05 -0800</lastBuildDate>
-             <link>http://katetv.example.com/</link>
-
-              <item>
-                 <title>This is Fun</title>
-                 <guid>http://katetv.example.com/show/4</guid>
-                 <pubDate>Tue, 23 Aug 2005 21:02:05 -0800</pubDate>
-                 <enclosure url="http://katetv.example.com/show/4"
-                            length="1911146"
-                            type="application/ogg"
-                 />
-             </item>
-             <item>
-                 <title>Watch This</title>
-                 <guid>http://katetv.example.com/show/3</guid>
-                 <pubDate>Tue, 16 Aug 2005 16:11:57 -0400</pubDate>
-                 <enclosure url="http://katetv.example.com/show/3"
-                            length="1387442"
-                            type="application/ogg"
-                 />
-             </item>
-             <item>
-                 <title>It is me again</title>
-                 <guid>http://katetv.example.com/show/2</guid>
-                 <pubDate>Tue, 9 Aug 2005 13:12:12 -0400</pubDate>
-                 <enclosure url="http://katetv.example.com/show/2"
-                            length="1894877"
-                            type="video/mpeg"
-                 />
-             </item>
-             <item>
-                 <title>Hello</title>
-                 <guid>http://katetv.example.com/show/1</guid>
-                 <pubDate>Tue, 2 Aug 2005 18:22:14 -0400</pubDate>
-                 <enclosure url="http://katetv.example.com/show/1"
-                            length="17442215"
-                            type="application/ogg"
-                 />
-             </item>
-         </channel>
-
-          </rss>     
-
- -

O leitor observador deve ter percebido que os exemplos dos websites de notícias e dos blogs eram do mesmo tipo de RSS. Também que os exemplos de Internet Rádio e dos programas de TV para Internet eram do mesmo tipo de RSS. Na verdade, a única diferença real entre os RSS de notícias/blogs e de Internet Rádio/TV para Internet é que os RSS de notícias/blogs usam o elemento <link> e os Internet Rádio/Internet TV usam o elemento <enclosure>.

- -
-

NOTA: Esses exemplos de RSS são muito, muito simples. E foram desenhados para dar a você uma idéia de como o RSS se parece basicamente. Todos esses exemplos de RSS são bem mínimos. Quando você criar seus próprios RSS feeds, você provavelmente irá querer fazê-los mais complexos que esses e incluir elementos RSS adicionais fazendo uso dos vários Módulos de RSS.

-
- -

{{Next("RSS:Como começar:Porque usar RSS")}}

diff --git "a/files/pt-pt/archive/rss/como_come\303\247ar/porque_usar_rss/index.html" "b/files/pt-pt/archive/rss/como_come\303\247ar/porque_usar_rss/index.html" deleted file mode 100644 index 904ce6ee43..0000000000 --- "a/files/pt-pt/archive/rss/como_come\303\247ar/porque_usar_rss/index.html" +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Porque usar RSS -slug: Archive/RSS/Como_começar/Porque_usar_RSS -tags: - - 'RSS:Como_começar' -translation_of: Archive/RSS/Getting_Started/Why_use_RSS ---- -

Esta página explica por quê você pode querer usar o RSS. Você ainda não criará seus próprios arquivos RSS, mas aprenderá sobre as razões de usá-lo.

- -

Por que usar RSS?

- -

Se você está lendo isso, provavelmente já tem seus próprios motivos para querer usar o RSS. Existem, na verdade, diversas razões para usar RSS. Mas os 2 maiores motivos podem ser amplamente declaradas dizendo: #1 (obviamente apenas use se) atende a suas necessidades e #2 possui uma grande quantidade de movimentação — todos estão usando.

- -

O RSS possui uma imensa quantidade de movimentação. As pessoas estão usando para publicar todo tipo de coisas. Artigos de notícias, blogs, bookmards, shows de Internet Rádio, shows de TV para Internet, atualizações de software, e-mails, mailing lists, music playlists, e mais. Se é esporádico, pode ser publicado com RSS.

- -

Software que lê e pode fazer uso do RSS também está por todos os lugares. O Mozilla Firefox possui algum suporte ao RSS (com sua tecnologia Live Bookmark). Existem muitos agregadores de RSS de desktop afora para listá-los. E agregadores RSS web-based demais para listar. Além disso, software customizado também está fazendo uso do RSS.

- -

Agregadores RSS estão em todos os lugares

- -

Um motivo para usar o RSS para publicar é porque existem enormes quantidades de agregadores RSS web-based para desktop. (Demais para listar) E se você publicar usando RSS então todos aqueles desktops e agregadores RSS web-based serão capazes de usar e ler seu RSS feed.

- -

{{ PreviousNext("RSS:Como começar:O que é RSS", "RSS:Como começar:Como o RSS trabalha") }}

diff --git "a/files/pt-pt/archive/rss/como_come\303\247ar/sindicar/index.html" "b/files/pt-pt/archive/rss/como_come\303\247ar/sindicar/index.html" deleted file mode 100644 index 60cf684500..0000000000 --- "a/files/pt-pt/archive/rss/como_come\303\247ar/sindicar/index.html" +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: Sindicar -slug: Archive/RSS/Como_começar/Sindicar -tags: - - PrecisaDeRevisãoEditorial - - 'RSS:Como_começar' -translation_of: Archive/RSS/Getting_Started/Syndicating ---- -

Esta página explica a Web Syndication, ou Publicação Web, com o RSS. Você aprenderá como fazer isso para que ambas — pessoas e máquinas — possam encontrar seu RSS feed, ou alimentador de RSS.

- -

O que é Syndication (Publicação)

- -

Syndication (ou Web Syndication) é o ato de tornar um conteúdo disponível para outros lerem, ouvirem ou assistirem. Quando você cria um blog, um rádio de Internet ou um programa televisivo para Internet, você está publicando (syndicating).

- -

O RSS ajuda você a publicar. Ele organiza sua publicação em um formato fácil para as máquinas entenderem.

- -

Publicar com RSS pode significar 3 coisas:

- -
    -
  1. Criar um RSS feed (também conhecido por alimentador de RSS).
    2. -
  2. Adicionar um elemento especial <link> à(s) página(s) HTML.
    3. -
  3. Adicionar um elemento especial <a> à(s) página(s) HTML.
    4. -
- -

Nós já falamos sobre o item 1 — Criar um RSS feed — então nos focaremos nos itens 2 e 3 aqui.

- -

Adicionando o <link>

- -

Freqüentemente o dado em um RSS feed é também disponibilizado em uma página web HTML. Quando este é o caso, a página web HTML pode avisar pessoas e máquinas sobre o feed com um código como o seguinte:

- -
<link rel="alternate" type="application/rss+xml" href="http://exemplo.com/feed" />
-
- -

Muitas vezes as pessoas querem anunciar o RSS feed em outros lugares também. Por exemplo, em um artigo de blog. Você pode fazer isso com um código como o seguinte:

- -
<link rel="home" type="application/rss+xml" href="http://exemplo.com/feed" />
-
- -

Note que este parece quase exatamente a mesma coisa do código anterior. A única coisa modificada foi o valor do atributo rel. (O código anterior teve um rel de valor alternate. E este código teve um rel de valor home.)

- -
-

NOTA: Tem havido muito abuso no uso do elemento <link> para publicação com RSS. Alguns bloggers o têm usado para que outros se inscrevam em seus blogs de qualquer página do blog (e não apenas da home page). O que resultou na adição de vários <link> com rel="alternate" por todos os lugares. (Nas entradas de blogs também e não apenas nas home page.) Isso é errado! Usar rel="alternate" neste caso é errado. Deve ser usado o rel="home". (Veja Understanding rel and rev para mais informações.) A parte importante quando se usa o <link> para publicar seu RSS feed é pôr o type="application/rss+xml".

-
- -

Adicionando o <a>

- -

Embora o uso do elemento HTML <link> seja poderoso; ele é na maioria das vezes escondido. Para anunciar o RSS feed de um modo mais direto, o elemento HTML <a> pode ser utilizado. Fazendo isso pode-se conseguir o mesmo resultado do elemento <link> discutido acima.

- -

Quando puser um link de uma página web HTML onde os dados em um RSS feed também são disponibilizados use:

- -
<a rel="alternate" type="application/rss+xml" href="http://exemplo.com/feed">...</a>
-
- -

Quando puser um link de alguma coisa como um artigo de post de um blog, use o seguinte código:

- -
<a rel="home" type="application/rss+xml" href="http://example.com/feed">...</a>
-
- -

Mais uma vez, note que esses dois trechos de código parecem quase exatamente os mesmos. A única coisa modificada foi o valor do atributo rel. (O primeiro trecho de código tem um rel de valor alternate e o segundo trecho tem um rel de valor home.)

- -

Ícones de Feed

- -

RSS (e outros) feeds utilizam um ícone especial. É recomendado que use este ícone quando criar um link especial <a> para seu alimentador. O ícone parece como este:

- -
-
Feed-icon-32x32.png
-
- -

Você pode conseguir mais ícones como este do Feed Icons. (Outros tamanhos e cores também estão disponíveis. Arquivos fontes também estão disponíveis.)

- -

Técnicas Avançadas de Publicação (Syndication)

- -

Embora esta técnica de publicação não seja necessária, é recomendado seu suporte; especialmente para web sites e aplicações que necessitam de alta performance.

- -

O protocolo HTTP — uma das tecnologias núcleo por trás da web — provê uma forma de priorizar o tipo de conteúdo que um cliente HTTP prefere para receber. Esta técnica toma vantagem disso fazendo com que os clientes prefer o RSS (acima do HTML ou outros formatos). Aqui está um exemplo simples de como é feito:

- -
Accept: application/rss+xml, text/html
-
- -

Apesar de na realidade, na produção de software, se pareça mais com isso.

- -
Accept: application/rss+xml, application/xhtml+xml, text/html
-
- -

Eis um exemplo mais completo:

- -
GET / HTTP/1.1
-Host: example.com
-Accept: application/rss+xml, application/xhtml+xml, text/html
-
- -

Quando um servidor HTTP (ou scripts de servidores) pega isso, ele deve redirecionar para o cliente HTTP do feed. Ele deve fazer isso com um HTTP 302 Found. Algo como:

- -
HTTP/1.1 302 Found
-Location: http://exemplo.com/feed
-
- -


- {{ PreviousNext("RSS:Como começar:Como o RSS trabalha", "RSS:Como começar:Blogs") }}

diff --git a/files/pt-pt/archive/rss/index.html b/files/pt-pt/archive/rss/index.html deleted file mode 100644 index 49eda2566c..0000000000 --- a/files/pt-pt/archive/rss/index.html +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: RSS -slug: Archive/RSS -tags: - - RSS -translation_of: Archive/RSS ---- -
Como começar -

Um tutorial introdutório ao RSS

-
- -
-

O Really Simple Syndication é um formato de dados baseado no XML que permite distribuir conteúdos simples.

-
- - - - - - - - -
-

Documentação

- -

Veja todos...

- 		-

Comunidade

- -

{{ DiscussionList("dev-tech-xml", "mozilla.dev.tech.xml") }}

- - - -

Tópicos relacionados

- -
-
Atom, RDF, XML
-
- -

Categorias

- -

Interwiki Language Links

- -

 

-
diff --git "a/files/pt-pt/archive/rss/vers\303\243o/0.90/index.html" "b/files/pt-pt/archive/rss/vers\303\243o/0.90/index.html" deleted file mode 100644 index 7001b622b7..0000000000 --- "a/files/pt-pt/archive/rss/vers\303\243o/0.90/index.html" +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: RSS/Versão/0.90 -slug: Archive/RSS/Versão/0.90 -translation_of: Archive/RSS/Version/0.90 ---- -

 

-

{{ Deprecated_header() }}

-

RSS 0.90

-

O RSS 0.90 é a versão mais antiga conhecida de RSS lançado ao público, e substituído pela Netscape RSS 0.91 (Revisão 1). Criado pela Netscape para ser um formato metadata provendo um sumário de um web site. (E não apenas um formato de publicação como é atualmente.)

-

O RSS 0.90 é um formato baseado no RDF.

-

Quando ele foi criado, o significado inicial do RSS era Rich Site Summary e não Really Simple Syndication. (Veja RSS - O que há em um nome para mais informações sobre o histórico do nome do RSS.))

-
-

NOTA: O RSS 0.90 teve seu uso desaprovado. Produtores de RSS NÃO DEVEM criar RSS 0.90 feeds, e DEVEM ao invés usar um novo e não-desaprovado formato RSS. (Veja a Lista de Versões de RSS para uma lista de formatos não-desaprovados.) Contudo, consumidores de RSS ainda DEVEM ser capazes de aceitar os RSS 0.90 feeds.

-
-

 

-

Exemplos

-

RSS 0.90 parece com algo assim:

-
-    <?xml version="1.0"?>
-
-    <rdf:RDF
-       xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-       xmlns="http://my.netscape.com/rdf/simple/0.9/"
-    >
-
-        <channel>
-            <title>Mozilla Dot Org</title>
-            <link>http://www.mozilla.org</link>
-            <description>the Mozilla Organization web site</description>
-        </channel>
-
-        <image>
-            <title>Mozilla</title>
-            <url>http://www.mozilla.org/images/moz.gif</url>
-            <link>http://www.mozilla.org</link>
-        </image>
-
-        <item>
-            <title>New Status Updates</title>
-            <link>http://www.mozilla.org/status/</link>
-        </item>
-
-        <item>
-            <title>Bugzilla Reorganized</title>
-            <link>http://www.mozilla.org/bugs/</link>
-        </item>
-
-        <item>
-            <title>Mozilla Party, 2.0!</title>
-            <link>http://www.mozilla.org/party/1999/</link>
-        </item>
-
-        <item>
-            <title>Unix Platform Parity</title>
-            <link>http://www.mozilla.org/build/unix.html</link>
-        </item>
-
-        <item>
-            <title>NPL 1.0M published</title>
-            <link>http://www.mozilla.org/NPL/NPL-1.0M.html</link>
-        </item>
-
-    </rdf:RDF>
-    
-
-

Note que aqui o RSS está sendo usado para listar seções de um web site ao invés de publicação (syndication).

-

 

-

Especificação

-

A especificação original do RSS 0.90 desapareceu de sua localização original:

-
-
- http://my.netscape.com/publish/help/quickstart.html
-
-

Cópias dele foram salvas e podem ser vistas nas seguintes localizações:

- -

{{ languages( { "ja": "ja/RSS/Version/0.90", "pl": "pl/RSS/Wersje/0.90" } ) }}

diff --git "a/files/pt-pt/archive/rss/vers\303\243o/index.html" "b/files/pt-pt/archive/rss/vers\303\243o/index.html" deleted file mode 100644 index f034387784..0000000000 --- "a/files/pt-pt/archive/rss/vers\303\243o/index.html" +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: Versão -slug: Archive/RSS/Versão -translation_of: Archive/RSS/Version ---- -

Versões de RSS

-

RSS tem uma história sórdida. Diferentes pessoas e grupos criaram especificações amplamente unilaterais que denominaram RSS. Alguns formatos RSS eram baseados em XML e outros baseados em RDF.

-

A lista abaixo é de todas as versões de RSS conhecidas. Eles estão listados em ordem cronológica de quando foram lançados.

-
-

NOTA: Na lista abaixo, apesar do RSS 1.0 parecer estar fora de lugar está na verdade no lugar cronologicamente correto

-
-
-

NOTA: Existem 3 diferentes versões de RSS 0.91. O RSS 0.91 da Netscape (Revisão 1), o RSS 0.91 da Netscape (Revisão 3) e o RSS 0.91 da Userland.

-
-
-

NOTA: O RSS 0.93 e o RSS 0.94 foram lançados apenas como beta e nunca se tornaram versões finais e por isso não eram para ter sido utilizados.

-
-

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameStatusRelease DateBased OnAuthor
RSS 0.90{{ Deprecated_inline() }}Março 1999RDFNetscape
Netscape RSS 0.91 (Revisão 1){{ Deprecated_inline() }}?XMLNetscape
Netscape RSS 0.91 (Revisão 3){{ Obsolete_inline() }}Julho 10, 1999XMLNetscape
Userland's RSS 0.91{{ Deprecated_inline() }}Junho 4, 2000XMLUserland
RSS 1.0PadrãoDezembro 9, 2000RDFgrupo RSS-DEV
RSS 0.92{{ Deprecated_inline() }}Dezembro 25, 2000XMLUserland
RSS 0.93{{ Deprecated_inline() }}Abril 20, 2001XMLUserland
RSS 0.94{{ Deprecated_inline() }}Agosto 19, 2002XMLUserland
RSS 2.0{{ Deprecated_inline() }}Setembro 2002XMLUserland
RSS 2.0 (post 2002-11-11){{ Deprecated_inline() }}Novembro 11, 2002XMLUserland
RSS 2.0 (post 2003-01-21)PadrãoJaneiro 21, 2003XMLUserland
-

{{ languages( { "es": "es/RSS/Versiones", "fr": "fr/RSS/Version", "ja": "ja/RSS/Version", "pl": "pl/RSS/Wersje" } ) }}

diff --git a/files/pt-pt/archive/themes/index.html b/files/pt-pt/archive/themes/index.html deleted file mode 100644 index aff151946d..0000000000 --- a/files/pt-pt/archive/themes/index.html +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Themes -slug: Archive/Themes -tags: - - NeedsTranslation - - TopicStub -translation_of: Archive/Themes ---- -

Archived theme documentation.

- -

diff --git a/files/pt-pt/archive/utilizar_normas_web_nas_suas_paginas_da_web/index.html b/files/pt-pt/archive/utilizar_normas_web_nas_suas_paginas_da_web/index.html deleted file mode 100644 index 61629f890d..0000000000 --- a/files/pt-pt/archive/utilizar_normas_web_nas_suas_paginas_da_web/index.html +++ /dev/null @@ -1,123 +0,0 @@ ---- -title: Utilizar as Normas da Web nas suas Páginas da Web -slug: Archive/Utilizar_Normas_Web_nas_suas_Paginas_da_Web -tags: - - Desenvolvimento da Web - - Normas da Web - - Padrões da Web -translation_of: Archive/Using_Web_Standards_in_your_Web_Pages ---- -

 

- -
"Browser makers are no longer the problem. The problem lies with designers and developers chained to the browser-quirk-oriented markup of the 1990s-often because they don't realize it is possible to support current standards while accommodating old browsers." -
- Web Standards Project
-
- -

This article provides an overview of the process for upgrading the content of your web pages to conform to the World Wide Web Consortium (W3C) web standards. The first 2 sections address exclusively validation issues, benefits of validation, deprecated elements, deprecated attributes. How to upgrade a webpage markup code to pass validation and how to implement CSS are addressed by providing recommendations, tutorials and references.

- -

The other sections address DOM and DHTML coding practices which are at odds with the W3C web standards and suggest replacements. Every proposed W3C web standards replacement in this article is working without a problem in modern browsers like MSIE 7, Firefox 2, Opera 9, Safari 3, Konqueror 3.5+, Icab 4, etc.

- -

The next-to-last section, Summary of Changes, outlines all the changes described in this article. The last section offers excellent and best references for those wishing to learn more about upgrading techniques presented in this article and more for those wishing to perfect their web pages.

- -

Conteúdos

- -
    -
  1. Benefits of using web standards
    2. -
  2. Making your page using web standards - how to
    3. -
  3. Using the W3C DOM
    4. -
  4. Developing Cross Browser and Cross Platform Pages
    5. -
  5. Using XMLHttpRequest
    6. -
  6. Summary of Changes
    7. -
  7. References
    8. -
- -
-

Informação do Documento Origina

- - -
- -

{{ languages( { "ja": "ja/Using_Web_Standards_in_your_Web_Pages", "zh-cn": "cn/\u5728\u60a8\u7684\u7f51\u9875\u4e2d\u5e94\u7528Web\u6807\u51c6" } ) }}

- -
- - - - - -
diff --git a/files/pt-pt/chrome.manifest/index.html b/files/pt-pt/chrome.manifest/index.html deleted file mode 100644 index d43a339e81..0000000000 --- a/files/pt-pt/chrome.manifest/index.html +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: chrome.manifest -slug: chrome.manifest -tags: - - Extensões - - Toolkit API -translation_of: Archive/Mozilla/Creating_a_Skin_for_SeaMonkey_2.x/chrome.manifest ---- -

 

-

O que é Chrome?

-

Chrome é o conjunto de elementos da interface de usuário na janela do aplicativo localizado fora da área da janela de conteúdo. Barras de ferramentas, barras de menu, barras de progresso e barras do título da janela são todos os exemplos de elementos que normalmente fazem parte do chrome.

-

Fornecedores Chrome

-

Um fornecedor de chrome para um determinado tipo de janela (e.g., para a janela do navegador) é chamado de fornecedor chrome. Os fornecedores trabalham juntos para fornecer um kit completo de chrome para uma janela particular, das imagens dos botões na barra de ferramentas aos arquivos que descrevem o texto, conteúdo e aparência da própria janela.

-

Existem três tipos básicos de fornecedores chrome:

-

Content (conteúdo)

-

O arquivo fonte principal para a descrição de uma janela vem do forneceder content (conteúdo), e ele pode ser qualquer tipo de arquivo visível com o Mozilla. Normalmente será um arquivo XUL, desde que o XUL seja desenhado para descrever os conteúdos das janelas e diálogos. Os arquivos javascript que definem a interface de usuário são também contidas com o pacote content (conteúdo), assim como a maioria dos arquivos XBL binding.

-

Locale (local)

-

Aplicativos localizáveis mantêm toda a informação localizada em fornecedores locale (local). Isto permite a tradutores ligá-lo em um diferente pacote chrome para traduzir um aplicativo sem alterar o resto do código fonte. Os dois tipos principais de arquivos localizáveis são arquivos DTD e arquivos de propriedade java-style.

-

Skin (pele)

-

Um fornecedor skin (pele) é responsável por proporcionar um kit completo de arquivos que descrevem a aparência visual do chrome. Normalmente um fornecedor skin (pele) proporcionará arquivos CSS e imagens.

-

O registro Chrome

-

O gecko runtime mantém um serviço sabido como o registro chrome que proporciona mapeamentos de nomes de pacotes chrome à localização física do pacote chrome no disco.

-

Este registro chorme é configurável e persistente, e assim um usuário pode instalar diferentes fornecedores chrome, e selecionar um preferido skin (pele) e locale (local). Isto é realizado através do xpinstall e do gerenciador de extensões.

-

Em ordem para informar o registro chrome do chrome disponível, um manifesto texto é usado: este manifesto é "chrome.manifest" na raiz de uma extensão, ou tema, e chrome/*manifest em um aplicativo XULRunner.

-

O texto simples do manifesto chrome tem um formato simples baseado em linhas. Cada linha é analizada gramaticalmente e individualmente; se a linha estiver correta o registro chrome pega a ação identificada por aquela linha; caso contrário o registro chrome ignora aquela linha (e imprime uma mensagem de aviso no console de runtime error).

-
locale packagename localename path/to/files
-skin packagename skinname path/to/files
-
-

Instruções do Manifesto

-

Comentários

-

Uma linha é um comentário se ela iniciar com o caractere '#'; qualquer outro caractere na linha é ignorado.

-
# esta linha é um comentário — você pode colocar o que quiser aqui
-
-

content (conteúdo)

-

Um pacote content (conteúdo) é registrado com a linha:

-
content packagename uri/to/files/ [flags]
-
-

Isto irá registrar a localização para usar quando for resolvida a URL chrome://packagename/content/.... A URL pode ser absoluta ou relativa à localização do arquivo de manifesto. Note que é necessário acabar com uma '/'.

-

locale (local)

-

Um pacote locale (local) é registrado com a linha

-
locale packagename localename uri/to/files/ [flags]
-
-

Isto irá registrar o pacote locale (local) quando for resolvida a URL chrome://packagename/locale/... . O localename (nome local) é normalmente um simples idenficador de língua "en" ou um identificador língua-país "en-US". Se mais de um local for registrado para um pacote, o registro chrome irá selecionar o melhor local usando as preferências do usuário.

-

skin (pele)

-

Um pacote skin (pele) é registrado com a linha

-
skin packagename skinname uri/to/files/ [flags]
-
-

Isto irá registrar um pacote skin (pele) quando for resolvida a URL chrome://packagename/skin/... . O skinname (nome da pele) é uma sring opaca identificando uma skin (pele) instalada. Se mais de uma pele for registrada para um pacote, o registro chrome irá selecionar a melhor pele usando as preferências do usuário.

-

overlay (sobreposição)

-

XUL overlays (sobreposições XUL) são registradas com a seguinte sintaxe:

-
overlay chrome://URI-to-be-overlayed chrome://overlay-URI [flags]
-
-

style (estilo)

-

Style overlays (sobreposições de estilo) (CSS customizado que será aplicado à página chrome) é registrado com a seguinte sintaxe:

-
style chrome://URI-to-style chrome://stylesheet-URI [flags]
-
-

override (substituição)

-

Em alguns casos uma extensão ou encaixe pode desejar substituir um arquivo chrome providenciado pela aplicação ou XULRunner. A fim de permitir isto, o manifesto de registro chrome permite instruções para "substituição":

-
override chrome://package/type/original-uri.whatever new-resolved-URI [flags]
-
-

Marcadores do Manifesto

-

Linhas do manifesto podem ter múltiplos espaços delimitados por marcadores adicionados no final da linha de registro. Estes marcadores marcam atributos especiais do chrome no pacote, ou limitam as condições sob qual linha é usada.

-

application (aplicativo)

-

Extensões podem instalar múltiplos aplicativos. Existem algumas linhas com registro chrome que somente se aplicam a um aplicativo particular. O marcador

-
application=app-ID
-
-

indica que a instrução deve ser aplicada somente se a extensão instalada no aplicativo identificado por app-ID estiver rodando. Múltiplos marcadores de aplicativos podem ser incluídos em uma única linha, neste caso a linha é aplicada se qualquer um dos marcadores rodar.

-

appversion (versão do aplicativo)

-

Extensões podem instalar em múltiplas versões de um aplicativo. Existem algumas extensões que podem instalar múltiplas versões de um aplicativo. O marcador

-
appversion=version
-appversion<version
-appversion<=version
-appversion>version
-appversion>=version
-
-

indica que a instrução deve somente ser aplicada se a extensão instalada no aplicativo tiver versão identificada. Múltiplos marcadores appversion podem ser incluídos em uma única linha. neste caso a linha é aplicada se qualquer um dos marcadores rodar. A versão da string precisa estar conforme o Toolkit version format.

-

platform (plataforma)(Pacotes específicos da plataforma)

-

Alguns pacotes são marcados com um marcador especial indicando que ele tem uma plataforma específica. Algumas partes do content (conteúdo), skin (pele), locales (locais) podem ser diferentemente baseados para a plataforma que rodam. Estes pacotes contém três diferentes grupos de arquivos, para windows/os2, macintosh, e plataformas como o unix. Por exemplo, a ordem dos botões "OK" e "cancelar" em um diálogo é diferente, assim como o nome de alguns itens.

-

O modificador de "plataforma" é somente analizado gramaticamente para o registro de conteúdo, não é reconhecido pelo registro de local e pele. Entretanto isto se aplica às partes conteúdo, local, e pele do pacote, quando especificado.

-

Para indicar se um pacote tem plataforma específica, adicione o modificador "plataform" à linha do "content" após o trajeto, por exemplo:

-
content global-platform jar:toolkit.jar!/toolkit/content/global-platform/ platform
-
-

Uma vez especificado isto em seu manifesto você assegura-se então que abaixo do diretório da plataforma global existem sub-diretórios win (Windows/OS2), mac (OS9/OSX), ou unix (Todos os outros). Alguma coisa residindo do lado de fora destes sub-diretórios será ignorado.

-

xpcnativewrappers

-

Pacotes chrome podem decidir se para usar o mecanismo de segurança xpcnativewrappers para proteger seu código contra conteúdos maliciosos que possam ter acesso. Veja en:Safely accessing content DOM from chrome para detalhes.

-

Com o Firefox 1.5 lançamento alpha (Deer Park alphas), este marcador está *desligado* por padrão, e precisa ser explicitamente ativado especificando-se xpcnavitewrappers=yes.

-

Com o Firefox 1.5 lançamento beta, este marcador será ativado por padrão, e extensões que tiverem um acesso inseguro aos objetos de conteúdo serão requeridas para especificar xpcnavitewrappers=no.

-

O marcador xpcnativewrappers aplica somente ao pacote content (conteúdo): ele não é reconhecido pelo registro locale (local) ou skin (pele).

-

Exemplo de Manifesto Chrome

-
content       necko                   jar:comm.jar!/content/necko/ xpcnativewrappers=yes
-locale	       necko       en-US       jar:en-US.jar!/locale/en-US/necko/
-content       xbl-marquee             jar:comm.jar!/content/xbl-marquee/
-content       pipnss                  jar:pipnss.jar!/content/pipnss/
-locale        pipnss      en-US       jar:en-US.jar!/locale/en-US/pipnss/
-# Firefox-only
-overlay chrome://browser/content/pageInfo.xul           chrome://pippki/content/PageInfoOverlay.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}
-overlay chrome://communicator/content/pref/preftree.xul chrome://pippki/content/PrefOverlay.xul
-overlay chrome://navigator/content/pageInfo.xul         chrome://pippki/content/PageInfoOverlay.xul application=seamonkey@applications.mozilla.org
-content       pippki                  jar:pippki.jar!/content/pippki/ xpcnativewrappers=yes
-locale        pippki      en-US       jar:en-US.jar!/locale/en-US/pippki/
-content       global-platform         jar:toolkit.jar!/content/global-platform/ platform
-skin          global      classic/1.0 jar:classic.jar!/skin/classic/global/
-override chrome://global/content/netError.xhtml jar:embedder.jar!/global/content/netError.xhtml
-content       inspector               jar:inspector.jar!/content/inspector/ xpcnativewrappers=no
-
-

Manifestos contents.rdf com estilo antigo

-

Antes do manifesto de texto simples foram introduzidos (os quais funcionam no Firefox 1.5, Toolkit 1.8), manifestos RDF chamados "contents.rdf" que foram usados para registrar o chrome. Este formato é desaprovado; todavia, a Suíte Mozilla (SeaMonkey) não suporta o formato do manifesto de texto simples ainda, então o manifesto contents.rdf é requerido para extensões que desejam deixar para trás o mantimento da compatibilidade com o Firefox 1.0 ou à suíte.

diff --git a/files/pt-pt/creating_a_skin_for_seamonkey_2.x/index.html b/files/pt-pt/creating_a_skin_for_seamonkey_2.x/index.html deleted file mode 100644 index 063b065a0f..0000000000 --- a/files/pt-pt/creating_a_skin_for_seamonkey_2.x/index.html +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Creating a Skin for SeaMonkey 2.x -slug: Creating_a_Skin_for_SeaMonkey_2.x -tags: - - NeedsTranslation - - SeaMonkey - - TopicStub -translation_of: Archive/Mozilla/Creating_a_Skin_for_SeaMonkey_2.x ---- -

Introduction

- - -

You're going to make a theme for SeaMonkey 2, but don't know how? I hope this manual will help you.

- - -

Contents

- diff --git a/files/pt-pt/criando_um_patch/index.html b/files/pt-pt/criando_um_patch/index.html deleted file mode 100644 index 0ebf20b893..0000000000 --- a/files/pt-pt/criando_um_patch/index.html +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Criando um patch -slug: Criando_um_patch -tags: - - Desenvolvimento_Mozilla - - Todas_as_Categorias -translation_of: Mercurial/Using_Mercurial ---- -

 

-

Depois de obter o código fonte, modifique-o, compile-o e teste-o, você pode querer receber suas mudanças revisadas e checadas]. Em ordem de fazer isto, você precisa criar um arquivo listando as mudanças que você fez, chamado patch ou diff file. Você pode gerá-lo usando o comando cvs diff.

-

Criando um diff de um arquivo único

-

Em ordem para criar um diff de um arquivo local único contra o arquivo atual no repositório, use:

-
$ cvs diff -u8p FILENAME
-
-

Isto cria um diff no então chamado formato 'unified' (-u), com 8 linhas de contexto. O diff é impresso para stdout por padrão. Para redirecionar a saída para um arquivo, use algo como:

-
$ cvs diff -u8p FILENAME > OUT_FILE
-
-

Criando um diff para arquivos múltiplos

-

Se, ao invés de usar um arquivo regular para FILENAME, você providenciar um diretório, então este diretório assim como todos os subdiretórios serão buscados recursivamente. Por exemplo

-
$ cvs diff -u8p . > OUT_FILE
-
-

comparará todos os arquivos no diretório corrente e todos os seus subdiretórios contra as versões no repositório, e escreverá as diffs combinadas e unificadas para um arquivo chamado OUT_FILE, usando 8 linhas de contexto.

-

Deve haver contexto suficiente no patch para que seja endendido sem abrir o código fonte. A linha-guia padrão é usar 8 linhas de contexto; se for colocado mais contexto, é necessário fazer o patch entendível, substitua 8 por um número maior. Também note que a maior quantidade de contexto que você inclui, aumenta a chance de permitir também aplicar o patch a um arquivo que difere pesadamente do código original contra o que o diff foi preparado.

-

Incluindo novos arquivo em um patch

-

Para incluir um novo arquivo em seu patch use a opção -N:

-
$ cvs diff -u8pN . > OUT_FILE
-
-

Um problema comum aqui é que cvs diff não incluirá os novos arquivos que não foram cvs added (cvs adicionado), e cvs requer acesso de escrita ao repositório.

-

A solução é usar a utilidade cvsdo , que edita CVS/Entries para fazer o cvs pensar que o arquivo foi adicionado ao repositório:

-
$ cvsdo add NEWFILE
-$ cvs diff -u8pN NEWFILE > OUT_FILE
-
-

Note que este truque não trabalhará para novos diretórios; para isto, cvs add atualmente têm de modificar o repositório imediatamente, que requere acesso à escrita

diff --git a/files/pt-pt/criando_um_visual_para_o_firefox/contents.rdf/index.html b/files/pt-pt/criando_um_visual_para_o_firefox/contents.rdf/index.html deleted file mode 100644 index f074db7f8e..0000000000 --- a/files/pt-pt/criando_um_visual_para_o_firefox/contents.rdf/index.html +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: contents.rdf -slug: Criando_um_visual_para_o_Firefox/contents.rdf -translation_of: Archive/Themes/Creating_a_Skin_for_Firefox/contents.rdf ---- -

-

Copie o texto seguinte e cole em um arquivo de texto, depois salve este arquivo como "contents.rdf": -

-
<?xml version="1.0"?>
-
-<RDF:RDF xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-          xmlns:chrome="http://www.mozilla.org/rdf/chrome#">
-
-  <!-- Lista todas os visuais fornecidos neste tema -->
-  <RDF:Seq about="urn:mozilla:skin:root">
-    <RDF:li resource="urn:mozilla:skin:Meu_Tema"/>
-  </RDF:Seq>
-
-  <RDF:Description about="urn:mozilla:skin:Meu_Tema"
-    chrome:displayName="Meu_Tema"
-    chrome:accessKey="N"
-    chrome:author=""
-    chrome:authorURL=""
-    chrome:description=""
-    chrome:name="Meu_Tema"
-    chrome:image="preview.png" >
-    <chrome:packages>
-      <RDF:Seq about="urn:mozilla:skin:Meu_Tema:packages">
-        <RDF:li resource="urn:mozilla:skin:Meu_Tema:browser"/>
-        <RDF:li resource="urn:mozilla:skin:Meu_Tema:communicator"/>
-        <RDF:li resource="urn:mozilla:skin:Meu_Tema:global"/>
-        <RDF:li resource="urn:mozilla:skin:Meu_Tema:mozapps"/>
-        <RDF:li resource="urn:mozilla:skin:Meu_Tema:help"/>
-      </RDF:Seq>
-    </chrome:packages>
-  </RDF:Description>
-
-  <!-- Informação da Versão. Indica que funciona somente em versão superior a 1 do pacote. -->
-  <RDF:Description chrome:skinVersion="1.5" about="urn:mozilla:skin:Meu_Tema:browser"/>
-  <RDF:Description chrome:skinVersion="1.5" about="urn:mozilla:skin:Meu_Tema:communicator"/>
-  <RDF:Description chrome:skinVersion="1.5" about="urn:mozilla:skin:Meu_Tema:global"/>
-  <RDF:Description chrome:skinVersion="1.5" about="urn:mozilla:skin:Meu_Tema:mozapps"/>
-  <RDF:Description chrome:skinVersion="1.5" about="urn:mozilla:skin:Meu_Tema:help"/>
-</RDF:RDF>
-
-{{ languages( { "en": "en/Creating_a_Skin_for_Firefox/contents.rdf", "fr": "fr/Cr\u00e9er_un_th\u00e8me_pour_Firefox/contents.rdf", "pl": "pl/Tworzenie_sk\u00f3rek_dla_Firefoksa/contents.rdf" } ) }} diff --git a/files/pt-pt/criando_um_visual_para_o_firefox/iniciando/index.html b/files/pt-pt/criando_um_visual_para_o_firefox/iniciando/index.html deleted file mode 100644 index c082b560dc..0000000000 --- a/files/pt-pt/criando_um_visual_para_o_firefox/iniciando/index.html +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: Iniciando -slug: Criando_um_visual_para_o_Firefox/Iniciando -translation_of: Archive/Mozilla/Creating_a_sking_for_Firefox_Getting_Started ---- -

 

-

Instalação

-

Baixe a mais recente versão do Firefox e instale. Certifique-se de instalar a extensão DOM Inspector incluída.

-

Extrair tema

-

Você pode iniciar com qualquer tema projetado para o Firefox, porém, para uma melhor compreensão estaremos editando o Winstripe (tema padrão do Firefox). Ele está situado no arquivo classic.jar e é encontrado no diretório da instalação do Firefox. Um arquivo .jar é na realidade um zip renomeado, abra-o em um programa zip do mesmo modo que abriria um arquivo comum. Entretanto, se a aplicação zip não interpretar com um formato válido, renomeie o arquivo para classic.zip e continue a extração.

-
Localizações do classic.jar
-

Linux: /usr/lib/MozillaFirefox/chrome/classic.jar

-

Windows: \Arquivos de Programas\Mozilla Firefox\chrome\classic.jar

-

Para Mac OS X:

- -

Copie classic.jar para outra pasta mais facilmente acessível -- é recomendado usar Classico -- extraia o conteúdo nesta pasta, garantindo a permanência da mesma estrutura de diretório.

-

Nota: Você pode alterar o arquivo .jar para .jar.zip então extrair ela para colocar dentro de uma pasta!

-

Diretórios

-

Dentro do classic.jar há um diretório skin, e inclui mais dois arquivos preview.png e icon.png.

-
skin
skin um simples recipiente para o diretório classic que mantem todo o material importante.
classic
classic contem os seguintes diretórios.
browser
browser contem todos os ícones da barra de ferramentas, como também os ícones para a barra de navegação, sistema de feeds, segurança de navegação. organizador de favoritos, janela de opções e pesquisa.
communicator
Não é obrigatório e normalmente é esquecido.
global
global contem quase todos os mais importante arquivos CSS que definem a aparência do navegador. Este é o diretório o mais crítico em um tema.
help
help contem todos os arquivos para aplicar o tema no diálogo da janela de ajuda.
mozapps
mozapps contem todos os estilos e ícones para certos mecanismos do navegador, como o gerenciador de complementos e o assistente de atualização.
-
-

Instalar seu novo tema

-

Antes que você possa ver as alterações feitas no tema do Firefox (desde que a última edição seja de difícil ajuste) você deve primeiramente aprender como re-compactar o tema clássico para fazê-lo instalável. Para este exemplo chamaremos seu tema de "Meu_Tema", embora possa ser substituído por qualquer outro nome.

-
Copiando os arquivos necessários
-

O primeiro passo é mover todos os arquivos na correta estrutura do diretório. Então crie um novo diretório chamado Meu_Tema. Dentro deste diretório ponha como diretórios principais: browser, communicator, global, help, mozapps e também os arquivos icon.png, preview.png (sim, isto significa que a estrutura deste diretório e o novo classico.jar será ligeiramente diferente do classic).

-
Criando os arquivos de instalação
-
contents.rdf
-

Faça uma cópia do contents.rdf ponha em \Meu_Tema e abra em seu editor de texto. Este arquivo é um pequeno Banco de dados XML Database que é utilizado para descrever o visual.

-

No código pesquise por todos resultados de "Meu_Tema" e substitua com o nome escolhido para o seu tema.

-

A seção packages lista que componentes você está alterando. Se nós possuirmos visuais para o Chatzilla, necessitamos adicionar outra linha semelhante e alterar a parte final para Chatzilla. Porém, esta lista inclui tudo que alteramos, por isto substitua apenas a parte do texto em azul para manter o nome/versão que você usou nas seções antes desta.

-
<RDF:li resource="urn:mozilla:skin:Meu_Tema:communicator"/>
-<RDF:li resource="urn:mozilla:skin:Meu_Tema:editor"/>
-<RDF:li resource="urn:mozilla:skin:Meu_Tema:global"/>
-<RDF:li resource="urn:mozilla:skin:Meu_Tema:messenger"/>
-<RDF:li resource="urn:mozilla:skin:Meu_Tema:navigator"/>
-
-

Salve o arquivo e saia do editor de texto.

-
install.rdf
-

Faça uma cópia install.rdf e ponha em seu diretório Meu_Tema, depois abra em seu editor de texto. Este arquivo é um pequeno banco de dados XML que descreve a instalação do visual.

-
  <Description about="urn:mozilla:install-manifest">
-    <em:id>{UUID_do_Tema}</em:id>
-    <em:version>Versao_do_Tema</em:version>
-
-

A primeira seção requer que você estabeleça um UUID para o seu tema e que você dê ao seu tema um número da versão. Uma vez feito isto, insira a informação como indicado acima, e continue abaixo.

-

Você deverá ter também as atualizações entre máxima e mínima compatíveis para a aplicação (Firefox) na seguinte seção:

-
    <em:targetApplication>
-      <Description>
-        <!-- UUID do Firefox -->
-        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
-        <em:minVersion>Versao_Minima_do_Firefox</em:minVersion>
-        <em:maxVersion>Versao_Maxima_do_Firefox</em:maxVersion>
-      </Description>
-    </em:targetApplication>
-
-

Estabelecer versões compatíveis no limite entre mínima e máxima previne conflitos em alguma versão do Firefox para qual seu tema não foi desenvolvido ou não testado.

-

Arquivos CSS

-

Os arquivos CSS nesses diretórios dizem ao browser como deverá mostrar os botões e outros controles, onde posicionar as imagens, bordas e espaçamentos, e assim por diante.

-

Nesse exemplo, vamos mudar os botões de padrão do browser.

-

Vá para a pasta global e abra o arquivo button.css em seu editor de texto favorito. Desça até button {. Esta seção define o botão normal em sua posição estática (não está com o ponteiro sobre ele, e não é selecionado).

-

Mude o background-color: para DarkBlue e o color: para White, e salve o arquivo.

-

more after I get done with some tests

-

Recompactar o JAR

-

Agora tudo que você precisa fazer é compactar novamente os arquivos com a seguinte estrutura de diretório, usando seu programa favorito de compactação de arquivos:

-

/browser/*
-/communicator/*
-/global/*
-/help/*
-/mozapps/*
-/contents.rdf
-/install.rdf
-/icon.png
-/preview.png
- 

-

Certifique-se de apenas compactar os arquivos de dentro do diretório que você criou Meu_Tema. Caso o contrário seu tema não será instalado corretamente.

-

Triggering the install from the web

-

To install the theme's JAR file directly from the web, you need to run some JavaScript.

-

<a href='javascript:InstallTrigger.installChrome(InstallTrigger.SKIN,
-"myskin.jar", "My Skin Theme")'>install My Skin</a>

-

If you have JAR files on your hard drive and would like to install them, then download/use this form.

-

You can also just open the themes window in Mozilla and drag and drop your .jar file onto it.

-

Now to change your folder(s) back into a .jar Well it's easy! What you do is put your folder(s) into a .zip file and then when it's compressed make the .zip into a .jar

-

{{ languages( { "en": "en/Creating_a_Skin_for_Firefox/Getting_Started", "es": "es/Creando_un_skin_para_Firefox/Como_empezar", "fr": "fr/Cr\u00e9er_un_th\u00e8me_pour_Firefox/Premiers_pas" } ) }}

diff --git a/files/pt-pt/criando_um_visual_para_o_firefox/install.rdf/index.html b/files/pt-pt/criando_um_visual_para_o_firefox/install.rdf/index.html deleted file mode 100644 index 6ecb35c06f..0000000000 --- a/files/pt-pt/criando_um_visual_para_o_firefox/install.rdf/index.html +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: install.rdf -slug: Criando_um_visual_para_o_Firefox/install.rdf -translation_of: Archive/Themes/Creating_a_Skin_for_Firefox/install.rdf ---- -

 

- -

Copie o texto seguinte e cole em um arquivo de texto, então salve este arquivo como "install.rdf":

- -

 

- -
<?xml version="1.0"?>
-
-<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-      xmlns:em="http://www.mozilla.org/2004/em-rdf#">
-
-  <Description about="urn:mozilla:install-manifest">
-    <em:id>{UUID_do_Tema}</em:id>
-    <em:version>Versao_do_Tema</em:version>
-
-    <!-- Aplicação em que esta extensão pode ser instalada,
-          com suporte a versões entre mínima e máxima. -->
-
-    <em:targetApplication>
-      <Description>
-        <!-- UUID do Firefox -->
-        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
-        <em:minVersion>Versao_Minima_do_Firefox</em:minVersion>
-        <em:maxVersion>Versao_Maxima_do_Firefox</em:maxVersion>
-      </Description>
-    </em:targetApplication>
-
-    <!-- MetaData do Extremo Inicial -->
-    <!-- Meu_Tema -->
-    <em:name>Meu_Tema</em:name>
-    <em:description>Descricao_do_Seu_Tema</em:description>
-    <em:creator>Seu_Nome</em:creator>
-    <em:contributor>Nomes_dos_Colaboradores</em:contributor>
-    <em:homepageURL>Site_do_Tema</em:homepageURL>
-    <em:updateURL> Url_para_Localizar_Atualizacao </em:updateURL>
-    <em:aboutURL> Url_para_Página_Sobre </em:aboutURL>
-
-    <!-- Ganchos de Integração do Extremo Incial
-          (utilizado pelo Gerenciador de Complementos/Temas)-->
-    <em:internalName>Meu_Tema</em:internalName>
-  </Description>
-
-</RDF>
-
diff --git a/files/pt-pt/criando_um_visual_para_o_firefox/uuid/index.html b/files/pt-pt/criando_um_visual_para_o_firefox/uuid/index.html deleted file mode 100644 index e7010bb2e5..0000000000 --- a/files/pt-pt/criando_um_visual_para_o_firefox/uuid/index.html +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: UUID -slug: Criando_um_visual_para_o_Firefox/UUID -translation_of: Archive/Themes/Creating_a_Skin_for_Firefox/UUID ---- -

-

-

UUID: Indentificador Único Universal (Universal Unique Identifier)

-

Um UUID pode ser obtido visitando http://www.famkruithof.net/uuid/uuidgen ou digitando "firebot: uuid?" em irc.mozilla.org. -

-

Veja Também

-

Gerando_GUIDs -

{{ languages( { "en": "en/Creating_a_Skin_for_Firefox/UUID", "fr": "fr/Cr\u00e9er_un_th\u00e8me_pour_Firefox/UUID", "pl": "pl/Tworzenie_sk\u00f3rek_dla_Firefoksa/UUID" } ) }} diff --git "a/files/pt-pt/empacotando_extens\303\265es/index.html" "b/files/pt-pt/empacotando_extens\303\265es/index.html" deleted file mode 100644 index 96b5988408..0000000000 --- "a/files/pt-pt/empacotando_extens\303\265es/index.html" +++ /dev/null @@ -1,29 +0,0 @@ ---- -title: Empacotando Extensões -slug: Empacotando_Extensões -tags: - - Extensões - - Toolkit API -translation_of: Archive/Add-ons/Extension_Packaging ---- -

Extensões são uma forma de Installable Bundle (Pacotes Instaláveis) os quais podem ser baixados e instalados por um usuário, ou proporcionado por um pré-pacote com a aplicação ou por um programa externo. Extensões usam uma directory structure (estrutura de diretórios) que podem proporcionar chrome, componentes e outros arquivos para extender a funcionalidade de um programa XUL.

-

Toda extensão deve proporcionar um arquivo install.rdf que contém metadados sobre a extensão, como IDs únicos, versão, autor e informações sobre compatibilidade.

-

Depois dos arquivos da extensão e o install.rdf estarem preparados, existem vários caminhos para preparar uma extensão para instalação: comprima o diretório da extensão dentro de um arquivo XPI (XPInstall), desempacote a extensão diretamente dentro da aplicação do usuário ou diretório do perfil, ou registre a extensão no registro do Windows.

- -

Fazendo uma Extensão XPI

-

Um arquivo XPI (XPInstall) é simplesmente um arquivo ZIP contendo os arquivos da extensão, com o arquivo install.rdf no raiz do ZIP. Usuários podem baixar e instalar os arquivos XPI de um website ou de uma pasta local, abrindo-o ou arrastando-o para uma janela de Gerenciamento de Extensões.

-

O tipo MIME reconhecido pelo Firefox pelos arquivos XPI é application/x-xpinstall. A maioria dos servidores de HTTP não está configurada por padrão para retornar este tipo MIME para a extensão .xpi, você provavelmente precisará configurar seu servidor HTTP. No Servidor Apache HTTP, isto pode ser feito adicionando as seguintes diretrizes ao arquivo de configuração ou ao .htaccess:

-
AddType application/x-xpinstall .xpi
-
- -

Instalar Arquivos de Extensão Diretamente

-

Se você sabe a localização da aplicativos (se você estiver instalando uma extensão como parte de um instalador de aplicativos, por exemplo), você pode instalar os arquivos da extensão diretamente em <appdir>/extensions/<extensionID>. A extensão será encontrada automaticamente pelo Gerenciador de Extensões da próxima vez que o aplicativo for iniciado.

-

Quando usando este método você deve verificar se as permissões do arquivo de sistema para os diretórios e arquivos da extensão estejam postas adequadamente. Contrariamente, o Gerenciador de Extensões pode não funcionar adequadamente com a extensão ou ela pode não funcionar adequadamente.

-

Registrar um Local de Extensão Usando o Registro do Windows

-

Instaladores externos (como o Java runtime)podem desejar instalar pontos de integração da aplicação como extensão mesmo se o aplicativo ainda não está instalado. Isto pode ser efetuado no Windows usando o registro (Adding Extensions using the Windows Registry).

- -

Extensões Multi-Item XPI

-

Em alguns casos um simples arquivo XPI podem desejar instalar múltiplas extensões/temas. Um tipo especial de extensão XPI chamado de Multiple Item Package que explica como criar este tipo de pacote. (Firefox 1.5/XULRunner 1.8 é requerido.)

- -

Referências Oficiais para Toolkit API

-
{{page("/pt-PT/docs/Toolkit_API/Official_References")}}
diff --git a/files/pt-pt/empacotando_temas/index.html b/files/pt-pt/empacotando_temas/index.html deleted file mode 100644 index 264a4b1045..0000000000 --- a/files/pt-pt/empacotando_temas/index.html +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: Empacotando Temas -slug: Empacotando_Temas -tags: - - Temas - - Todas_as_Categorias - - Toolkit API -translation_of: Mozilla/Thunderbird/Thunderbird_extensions/Theme_Packaging ---- -

 

-

Este documento descreve como empacotar temas para o Firefox e o Thunderbird.

-

Pré Requisitos

-

Fazer um tema para o Firefox ou Thunderbird requer conhecimentos em Cascading Style Sheets (CSS), provavelmente XBL, e um pouco de design gráfico e habilidade estética (...ou talvez não). Este documento descreve somente como Temas são empacotados em ordem para serem mostrados na janela de Temas do Firefox.

-

Disposição do Arquivo de Tema

-

Os temas do Firefox/Thunderbird são empacotados em um arquivo JAR com a seguinte estrutura:

-
theme.jar:
-  install.rdf
-  contents.rdf
-  preview.png
-  icon.png
-  browser/files
-  global/files
-  mozapps/files
-  communicator/files
-  ...
-
-
- -

install.rdf

-

Seu manifesto install.rdf parecerá com isto:

-
<?xml version="1.0"?>
-
-<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-     xmlns:em="http://www.mozilla.org/2004/em-rdf#">
-
-  <Description about="urn:mozilla:install-manifest">
-    <em:type>4</em:type>more properties
-  </Description>
-</RDF>
-
-

Propriedades Requeridas de install.rdf

-

Seu arquivo install.rdf deve ter as seguintes propriedades. Veja a Referência install.rdf para mais informações:

- -

Propriedades Opcionais de install.rdf

- -

Note que se o seu tema estiver disponível no website http://addons.mozilla.org, ele não deve incluir uma URL de atualização.

-

Arquivo de Amostra install.rdf

-
<?xml version="1.0"?>
-
-<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-     xmlns:em="http://www.mozilla.org/2004/em-rdf#">
-
-  <Description about="urn:mozilla:install-manifest">
-    <em:id>{18b64b56-d42f-428d-a88c-baa413bc413f}</em:id>
-    <em:version>1.0</em:version>
-    <em:type>4</em:type>
-
-    <!-- Target Application this extension can install into,
-         with minimum and maximum supported versions. -->
-    <em:targetApplication>
-      <Description>
-        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
-        <em:minVersion>0.8</em:minVersion>
-        <em:maxVersion>0.9</em:maxVersion>
-      </Description>
-    </em:targetApplication>
-
-    <!-- Front End MetaData -->
-    <em:name>New Theme 1</em:name>
-    <em:description>A test theme for Firefox</em:description>
-    <em:creator>Ben Goodger</em:creator>
-    <em:contributor>John Doe</em:contributor>
-    <em:homepageURL>http://www.bengoodger.com/</em:homepageURL>
-
-    <!-- Front End Integration Hooks (used by Theme Manager)-->
-    <em:internalName>newtheme1</em:internalName>
-  </Description>
-</RDF>
-
-

Os seguir estão algumas aplicações comuns de alvos GUIDs que você pode usar na sua propriedade targetApplication:

-
Firefox      {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
-Thunderbird  {3550f703-e582-4d05-9a08-453d09bdfdc6}
-Sunbird      {718e30fb-e89b-41dd-9da7-e25a45638b28}
diff --git a/files/pt-pt/eventos_arrastar_e_soltar/index.html b/files/pt-pt/eventos_arrastar_e_soltar/index.html deleted file mode 100644 index 5c224cd109..0000000000 --- a/files/pt-pt/eventos_arrastar_e_soltar/index.html +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Eventos arrastar e soltar -slug: Eventos_arrastar_e_soltar -tags: - - Firefox 3 -translation_of: Archive/Mozilla/Drag_and_drop/Drag_and_drop_events ---- -

{{ Fx_minversion_header(3) }}

-

Firefox 3 acrescenta dois novos eventos que lhe permitem determinar quando operações de arrastar começam e terminam. Estes eventos são novos no atual projeto da especificação HTML 5.

-
-
- drag
-
- Emitido quando a operação de arrasto começa.
-
- dragend
-
- Emitido quando a operação de arrasto finaliza.
-
-

Para mais informações sobre arrastar e soltar, veja o artigo Drag and Drop (em inglês).

-

Você pode ver um exemplo destes eventos em ação aqui:

- -

Veja também

- -

Categorias

-

Interwiki Language Links

diff --git a/files/pt-pt/extras_xml/index.html b/files/pt-pt/extras_xml/index.html deleted file mode 100644 index bd4279062c..0000000000 --- a/files/pt-pt/extras_xml/index.html +++ /dev/null @@ -1,116 +0,0 @@ ---- -title: XML Extras -slug: Extras_XML -tags: - - Todas_as_Categorias - - XML -translation_of: Mozilla/Tech/XML_Extras ---- -

 

-

O módulo XML Extras contém inúmeras características que permitem que os desenvolvedores tratem XML como dados e não somente como um outro formato de documento. O módulo é estruturado como um componente drop-in e expõe suas características XML-as-data tanto para usuários de JavaScript como para usuários de C++/XPCOM. O módulo XML Extras é construído por padrão em todas as plataformas e é incluído no instalador do browser, de modo que, ele está disponível no nightly builds.

-

Status das Features

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FeatureStatus
XMLSerializerDisponível
XMLHttpRequestDisponível
DOMParser (string and stream input source)Disponível
Serviços Web com SOAP e WSDLDisponível desde a versão 1.4alpha. Movida para o módulo Serviços Web durante a versão 1.4beta.
Persistência XML 
FIXptr e XPointerDisponível desde a versão 1.4alpha no núcleo Mozilla. Movida para os Extras XML durante a versão 1.4beta.
-

Veja também:

- -

Perguntas Respostas e Testes

-

Existem alguns testes online principalmente para o exercício do método HTTP GET através do XMLHttpRequest.

-

Outros casos de teste para cada um dos componentes implementadas listados acima existem em extensions/xmlextras/tests/. Conjuntos de testes mais exaustivos precisam ser criadas, no entanto. Se você quiser ajudar com QA, você pode fazer o seguinte:

- -

Documentação

-

Provavelmente a melhor maneira de aprender a usar estas tecnologias é através de exemplos. Existem vários em extensions/xmlextras/tests/. Se você siguir o link para ver os exemplos que você vai precisar olhar no código fonte da página para os documentos HTML.

-

Para objetos XMLHttpRequest você pode confiar na  documentação Microsoft XMLHttpRequest, com algumas ressalvas: todas as funções e nomes de propriedades começam com uma letra minúscula e a criação do objeto é diferente. Algumas propriedades não são implementadas.

-

Thad Hoffman escreveu um documento que mostra como você pode imitar a Separação de Dados XML na Mozilla. Edmond Woychowsky também tem escrito artigos sobre a Separação de Dados XML na Mozilla: "Faça os dados da separação XML trabalhar na Mozilla", "Construir código de paginação XML cross-browser" e "Implementar um carrinho de compras flexível com XML e ASP". O Mozilla Developer Center tem várias páginas para XMLHttpRequest.

-

Abaixo estão alguns diferencias importantes em "Extras XML" entre Mozilla e Microsoft software:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DiferençaMicrosoftMozilla
Nomes dos membrosDiferencia maiúsculas de minúsculas?Começa com letra minúscula
Criação de XMLHttpRequestnew ActiveXObject("Msxml2.XMLHTTP")new XMLHttpRequest()
XMLHttpRequest.send("some string")okok começando com marco 0.9.7 (atualmente nightly 2001-11-28). Com versões mais antigas, passando para strings send() só funciona no cromo, ver post.html. A "solução" é usar o objeto DOMParser parseFromString() para criar um documento de string, e passar o documento temporário em send().
XMLHttpRequest.open("aHost")okfile:// documentos podem acessar http:// documentos, mas você precisa habilitar os privilégios UniversalBrowserRead nos seus scripts - ver o documento Segurança JavaScript: Scripts assinados para mais detalhes. Normalmente, os arquivos devem residir em um servidor web para que isso não represente um problema (não que você não precisa que a linha seja). Adicionalmente, "foo.com:80" e "foo.com:313" são considerados hospedeiros diferentes para fins de segurança. Você não pode abrir uma conexão com um host diferente.
DOMParser Creationnão disponívelnew DOMParser()
XMLSerializer Creationnão disponívelnew XMLSerializer()
-

Documentação mínima para os componentes listados acima podem ser encontrados usando a documentação Mozilla gerada pelo Doxygen. Arquivos de erros novos para contribuições adicionais de documentação, serão especificamente destinados a desenvolvedores de JavaScript ou para completar e esclarecer os comentários no estilo JavaDoc nos arquivos IDL.

- -

Por favor, consulte a seção ligando e apontando XML no documento XML na Mozilla para documentação FIXptr e XPointer.

-

Como eu posso ajudar?

- -

Categorias

-

Interwiki Language Links

diff --git a/files/pt-pt/gecko/index.html b/files/pt-pt/gecko/index.html deleted file mode 100644 index 52dad9bc73..0000000000 --- a/files/pt-pt/gecko/index.html +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Gecko -slug: Gecko -tags: - - Disposição - - Gecko - - Gecko versões - - Mozilla -translation_of: Mozilla/Gecko ---- -

Gecko é o nome do mecanismo de disposição (layout) desenvolvido pelo Projeto da Mozilla. Este foi originalmente chamado de NGLayout.

- -

A função do Gecko é ler o conteúdo da Web, tal como CSS, HTML,  JavaScript e XUL, e renderizá-lo no ecrã do utilizador ou imprimí-lo. Nas aplicações baseadas em XUL, Gecko também é utilziado para renderizar a interface do utilizador da aplicação.

- -

Gecko é utilizado em muitas aplicações, incluindo alguns navegadores, tal como Firefox, SeaMonkey, etc. (para uma lista completa, por favor, consulte Artigo da Wikipedia sobre Gecko (em inglês)). Os produtos que utilizam a mesma versão do Gecko têm um suporte idêntico para os padrões.

- -

O nome Gecko e o logótipo são marcas registadas da Netscape Communications Corporation, utilizados sob a licença.

- -

Versões do Gecko

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Versão do GeckoAplicações baseadas
Gecko 2 (em desenvolvimento)Firefox 4
Gecko 1.9.2Firefox 3.6, Thunderbird 3.1
Gecko 1.9.1Firefox 3.5, Thunderbird 3, {{ interwiki('wikimo', 'SeaMonkey:New_for_2.0', 'SeaMonkey 2.0') }}
Gecko 1.9Firefox 3
Gecko 1.8.1Firefox 2, Thunderbird 2, SeaMonkey 1.1
Gecko 1.8Firefox 1.5, Thunderbird 1.5, SeaMonkey 1.0
Gecko 1.7Firefox 1.0, Thunderbird 1.0, Nvu 1.0, Mozilla Suite 1.7
versões mais antigas do Gecko são compatíveis com as versões da Mozilla Suite
- - - - - - - - -
-

Documentação

- -
-
FAQs do Gecko
-
Perguntas mais frequentes sobre o Gecko.
-
- -
-
Introdução para a Disposição no Mozilla
-
Conversa técnica sobre disposições.
-
- -
-
Integração do Mozilla
-
Utilizando o Gecko na sua própria aplicação.
-
- -
-
{{ interwiki('wikimo', 'Gecko:Home_Page', 'Gecko Home Page on MozillaWiki') }}
-
Lar para os desenvolvedores ativos. Roadmaps e mais recursos atualizados.
-
- -

Ver todos...

- 		-

Comunidade

- -
    -
  • Ver fóruns da Mozilla... {{ DiscussionList("dev-tech-layout", "mozilla.dev.tech.layout") }}
    • -
- -

Tópicos Relacionados

- -
-
Normas Web, XUL, Embutindo o Mozilla, Desenvolvimento da Mozilla
-
-
- -

{{ languages( { "ko": "ko/Gecko", "en": "en/Gecko", "es": "es/Gecko", "fr": "fr/Gecko", "it": "it/Gecko", "ja": "ja/Gecko", "zh-cn": "cn/Gecko", "de": "de/Gecko", "pl": "pl/Gecko" } ) }}

diff --git a/files/pt-pt/gecko_dom_reference/introduction/index.html b/files/pt-pt/gecko_dom_reference/introduction/index.html deleted file mode 100644 index b47cd81e5f..0000000000 --- a/files/pt-pt/gecko_dom_reference/introduction/index.html +++ /dev/null @@ -1,319 +0,0 @@ ---- -title: Introdução ao DOM -slug: Gecko_DOM_Reference/Introduction -tags: - - DOM - - Guía - - Referencia - - Referência (2) - - Referência 2 -translation_of: Web/API/Document_Object_Model/Introduction ---- -

{{ ApiRef() }}

- -

Esta secção proporciona uma breve introdução conceitual ao DOM: o que é, como é que este fornece a estrutura para documentos HTML e XML, como o pode aceder, e como esta API apresenta a informação de referência e exemplos.

- -

O que é o DOM?

- -

O 'Modelo de Objeto de Documento (DOM) 'é uma interface de programação para documentos HTML e XML. Ele provê uma representação estruturada do documento e define um meio pelo qual a estrutura pode ser acessada por programas permitindo-os alterar a estrutura do documento, estilo e conteúdo. O DOM provê uma representação do documento como um conjunto estruturado de nós e objetos que têm propriedades e métodos. Essencialmente ele conecta páginas de internet a scripts ou linguagens de programação.

- -

Uma página de internet é um documento. Este documento pode ser exibido numa janela de navegador, ou como código-fonte HTML. Mas é o mesmo documento em ambos os casos. O Document Object Model (DOM) provê uma outra forma de representar, armazenar e manipular o mesmo documento. O DOM é uma representação orientada a objeto completa da página, e pode ser modificada com uma linguagem de script como o JavaScript.

- -

Os padrões W3C DOM e WHATWG DOM são implementados nos navegadores mais modernos. Muitos navegadores estendem o padrão, por isso deve-se ter cuidado ao utilizá-los na Web onde os documentos podem ser acedidos pelos vários navegadores com diferentes DOMs.

- -

Por exemplo, o DOM padrão especifica que o método getElementsByTagName no código abaixo deve devolver uma lista de todos os elementos <P> no documento:

- -
paragraphs = document.getElementsByTagName("P");
-// paragraphs[0] é o primeiro elemento <p>
-// paragraphs[1] é o segundo elemento <p>, etc.
-alert(paragraphs[0].nodeName);
-
- -

Todas as propriedades, métodos, e eventos disponíveis para manipular e criar páginas estão organizados em objetos (por exemplo, o objeto document representa o próprio documento, o objeto table implementa a interface DOM HTMLTableElement para acessar tabelas HTML, e assim por diante). Esta documentação dispõe uma referência objeto a objeto para o DOM implementado nos navegadores baseados no Gecko.

- -

DOM e JavaScript

- -

O rápido exemplo acima, parecido com a maioria dos exemplos desta referência, é JavaScript. Ou seja, ele foiescrito em JavaScript, mas eleusa o DOM para acessar o documento e seus elementos. O DOM não é uma linguagem de programação, mas sem ele, a linguagem JavaScript não teria nenhum modelo ou noção de páginas web, páginas XML e elementos com os quais ela geralmente lida. Todo elemento num documento—o documento como um todo, o cabeçalho, tabelas dentro do documento, cabeçalhos de tabelas, o texto dentro das células— faz parte do document object model para aquele documento, portanto eles podem ser acessados e manipulados fazendo-se uso do DOM e de uma linguagem de scripting como o JavaScript.

- -

No início, JavaScript e o DOM eram fortemente ligados, mas eventualmente evoluíram em entidades separadas. O conteúdo da página é armazenado no DOM e pode ser acessado e manipulado via JavaScript, portanto nós podemos escrever esta equação aproximada:

- -

API(web ou página XML) = DOM + JS(linguagem de scripting)

- -

O DOM foi desenvolvido para ser independente de qualquer linguagem de programação em particular, tornando a representação estrutural do documento para uma única API consistente. Embora nos concentramos exclusivamente em JavaScript nesta documentação de referência, implementações do DOM por ser construídas para qualquer linguagem, como este exemplo em Python demonstra:

- -
# Python DOM example
-import xml.dom.minidom as m
-doc = m.parse("C:\\Projects\\Py\\chap1.xml");
-doc.nodeName # DOM property of document object;
-p_list = doc.getElementsByTagName("para");
-
- -

For more information on what technologies are involved in writing JavaScript on the web, see JavaScript technologies overview.

- -

Como é que eu acedo ao DOM?

- -

Você não tem que fazer nada de especial para começar a usar o DOM. Navegadores diferentes tem implementações diferentes do DOM, e estas implementações exibem graus de conformidade variantes em relação ao verdadeiro padrão DOM (um tema que tentamos evitar nesta documentação), mas cada navegador usa algum document object model para tornar as páginas acessíveis para script.

- -

Quando você cria um script–quer seja um elemento in-line <script> or através de uma instrução de carregamento externo–você pode imediatamente começar a fazer uso da API para os elementos document ou window para manipular o próprio documento ou para acessar os filhos do documento, que são os vários elementos na página. Sua programação em DOM pode ser algo simples como o seguinte código, que mostra uma mensagem atráves da função alert() do objeto window, ou pode usar métodos do DOM mais sofisticados para realmente criar novos conteúdos como no exemplo maior mais abaixo.

- -

O código JavaScript a seguir exibe um alerta quando o documento é carregado (e quando todo o DOM está disponível para uso).

- -
<body onload="window.alert('Welcome to my home page!');">
-
-
- -

A função abaixo, cria um novo elemento H1, adiciona texto nesse elemento e então adiciona o H1 ná árvore de elementos deste documento.

- -
<html>
-  <head>
-    <script>
-       // executa essa função quando o documento é carregado
-       window.onload = function() {
-
-         // cria dois elementos em uma página HTML que estava vazia
-         var heading = document.createElement("h1");
-         var heading_text = document.createTextNode("Big Head!");
-         heading.appendChild(heading_text);
-         document.body.appendChild(heading);
-      }
-    </script>
-  </head>
-  <body>
-  </body>
-</html>
-
- -

Tipos de Dados Importantes

- -

Esta referência tenta descrever os vários objetos e tipos da maneira mais simples quanto possível. Mas há uma série de diferentes de tipos de dados sendo passados pela API dos quais você deve estar ciente. Por uma questão de simplicidade, exemplos de sintaxe nesta referência da API tipicamente se referem aos nós como elements, a arrays de nós como nodeLists (ou simplesmente elements), e a atributos dos nós como attributes.

- -

A seguinte tabela descreve brevemente estes tipos de dados.

- - - - - - - - - - - - - - - - - - - - - - - - -
documentQuando um membro retorna um objeto do tipo document (por exemplo, a propriedade ownerDocument de um elemento retorna o document ao qual pertence), este objeto é o próprio objeto document raiz. O capítulo Referência document do DOM descreve o objeto document.
elementelement se refere a um elemento ou a um nó do tipo element retornado por um membro da API do DOM. Ai invés de dizer, por exemplo, que o método document.createElement() retorna uma referência de objeto para um node, nós apenas dizemos que o método retorna o element que acabou de ser criado no DOM. Objetos element implementam a interface DOM Element e também a interface mais básica Node, ambas que estão incluídas juntas nesta referência.
nodeListUm nodeList é um array de elementos, como o tipo que é retornado pelo método document.getElementsByTagName(). Itens em uma nodeList são acessados pelo índice em qualquer uma das duas formas: -
    -
  • list.item(1)
    • -
  • list{{ mediawiki.external(1) }}
    • -
- -

Estas duas formas são equivalentes. Na primeira, item() é um único método do objeto nodeList. A última usa uma típica sintaxe de array para buscar o segundo item na lista.

-
attributeQuando um attribute é retornado por um membro (por exemplo, pelo método createAttribute()), ele é uma referência de objeto que expõe uma interface especial (embora pequena) para atributos. Atributos são nós no DOM assim como os elementos o são, embora você raramente pode usá-los como tal.
namedNodeMapUm namedNodeMap é como um array, mas os itens são acessados por nome ou índice, embora este último caso é meramente uma conveniência de enumeração, uma vez que estão em nenhuma ordem especial na lista. Um namedNodeMap tem um método item() para este propósito, e você também pode adicionar e remover itens de um namedNodeMap.
- -

Interfaces DOM

- -

Este guia é sobre os objetos e as verdadeirascoisas que você pode usar para manipular a hierarquia do DOM. É muitas vezes uma questão de indiferença que o objeto representando o elemento HTML form pegue sua propriedade name da interface HTMLFormElement mas sua propriedade className da própria interface HTMLElement. Em ambos os casos, a propriedade que você quer está simplesmente no objeto form.

- -

Mas a relação entre objetos e interfaces que eles implementam no DOM podem ser confusos, e portanto esta seção tenta dizer um pouco mais sobre as interfaces reais da especificação do DOM e como elas se tornam disponíveis.

- -

Interfaces e Objetos

- -

Muitos objetos se valem de muitas interfaces diferentes. O objeto table, por exemplo, implementa uma Interface do elemento HTML Table especializada, que inclui métodos como createCaption e insertRow. Mas desde que ele também é um elemento HTML, table implementa a interface Element descrita no capítulo Referência de element do DOM. E finalmente, com um elemento HTML também é, assim como o DOM lhe considera, um nó em uma árvore de nós que criam um modelo de objeto para uma página web ou uma página XML, o elemento table também implementa a mais básica interface Node, a partir da qual o Element deriva.

- -

Quando você tem uma referência para um objeto table, como no exemplo a seguir, você rotineiramente usa todas as três interfaces indiferentemente no objeto, talvez sem saber.

- -
var table = document.getElementById("table");
-var tableAttrs = table.attributes; // Node/Element interface
-for(var i = 0; i < tableAttrs.length; i++){
-  // HTMLTableElement interface: border attribute
-  if(tableAttrs[i].nodeName.toLowerCase() == "border")
-    table.border = "1";
-}
-// HTMLTableElement interface: summary attribute
-table.summary = "note: increased border";
-
- -

Interfaces do núcleo no DOM

- -

Esta seção lista algumas das interfaces mais comumente usadas no DOM. A idéia não é descrever aqui o que estas APIs fazem, mas sim te dar uma idéia dos tipos de métodos e propriedades que você verá muitas vezes enquanto você usa o DOM. Estas APIs comuns são usadas nos exemplos mais extensos no capítulo Exemplos de DOM no final deste livro.

- -

Os objetos document e window são os objetos cuja interface você geralmente vai usar na maioria das vezes na programação com DOM. Em termos simples, o objeto window representa algo como o navegador, e o objeto document é a raiz do próprio documento. Element descende da interface genérica Node, e estas duas juntas fornecem muitos dos métodos e propriedades que você usa em elementos individuais. Estes elementos também podem ter interfaces específicas para lidar com os tipos de dados que eles contém, como no exemplo do objeto table na seção anterior.

- -

A seguir está uma breve lista das APIs comuns para scripting usando o DOM em web e páginas XML.

- - - -

Testar a API de DOM

- -

Este documento fornece amostras para cada interface que você pode usar em seu próprio desenvolvimento web. Em alguns casos, as amostras são páginas HTML completas, com o acesso ao DOM em um elemento <script>, a interface (por exemplo, botões) necessária para disparar o script em um form, e os elementos HTML sobre os quais o DOM opera listados. Quando for este o caso, você pode copiar a colar o conteúdo do exemplo dentro de um novo arquivo HTML, salvá-lo, e executar o exemplo em um navegador.

- -

Há casos, no entanto, que os exemplos são mais concisos. Para executar exemplos que apenas demonstram a relação básica da interface para com os elementos HTML, você pode criar uma página de teste na qual as interfaces podem facilmente ser acessadas por scripts. A seguinte página web, bem simples, fornece um elemento <script> no seu cabeçalho onde você pode colocar funções que testam a interface, alguns poucos elementos HTML com atributos que você pode remover, criar, ou alterar, e a interface web necessária para chamar aquelas funções pelo navegador.

- -

Você pode usar esta página de teste ou criar uma similar a fim de testar as interfaces do DOM nas quais você está interessado e ver como elas funcionam na plataforma do navegador. Você pode atualizar o conteúdo da função test() como necessário, criar mais botões, ou adicionar elementos conforme a necessidade.

- -
<html>
-  <head>
-    <title>DOM Tests</title>
-    <script type="application/javascript">
-    function setBodyAttr(attr, value){
-      if (document.body) eval('document.body.'+attr+'="'+value+'"');
-      else notSupported();
-    }
-    </script>
-  </head>
-  <body>
-    <div style="margin: .5in; height: 400;">
-      <p><b><tt>text</tt></b></p>
-      <form>
-        <select onChange="setBodyAttr('text',
-        this.options[this.selectedIndex].value);">
-          <option value="black">black
-          <option value="darkblue">darkblue
-        </select>
-        <p><b><tt>bgColor</tt></b></p>
-        <select onChange="setBodyAttr('bgColor',
-        this.options[this.selectedIndex].value);">
-          <option value="white">white
-          <option value="lightgrey">gray
-        </select>
-        <p><b><tt>link</tt></b></p>
-        <select onChange="setBodyAttr('link',
-        this.options[this.selectedIndex].value);">
-          <option value="blue">blue
-          <option value="green">green
-        </select>  <small>
-        <a href="http://www.brownhen.com/dom_api_top.html" id="sample">
-        (sample link)</a></small><br>
-      </form>
-      <form>
-        <input type="button" value="version" onclick="ver()" />
-      </form>
-    </div>
-  </body>
-</html>
-
- -

Para testar muitas interfaces em uma única página–por exemplo, uma "suite" de propriedades que afetam as cores de sua página web–você pode criar uma página de testes similar com um completo console de botões, campos de texto e outros elementos HTML. A seguinte captura de tela pode te dar alguma idéia de como as interfaces podem estar agrupadas para teste.

- -
-
Figura 0.1 Página de Teste de Amostra de DOM
-Image:DOM_Ref_Introduction_to_the_DOM.gif
- -

Neste exemplo, os menus suspensos atualizam dinamicamente, tais como aspetos de acessibilidade DOM da página da Web como a cor de fundo (bgColor), a cor das hiperligações (aLink), e a cor do texto (text). Contudo, você cria as suas próprias páginas de teste, e testa as interfaces à medida que as lê, é uma parte importante de aprendizagem em como utilizar o DOM efetivamente.

- - - - - -
- - - - - -
diff --git a/files/pt-pt/gecko_sdk/index.html b/files/pt-pt/gecko_sdk/index.html deleted file mode 100644 index c215853e97..0000000000 --- a/files/pt-pt/gecko_sdk/index.html +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Gecko SDK -slug: Gecko_SDK -translation_of: Mozilla/Gecko/Gecko_SDK ---- -

Geral

-

O Gecko SDK é um conjunto de arquivos XPIDL, cabeçalhos e ferramentas para desenvolver XPCOM componentes, que pode, então, por sua vez, por exemplo, Ser acessado a partir de XUL usando JavaScript.

-

Note-se que, a fim de desenvolver esses componentes, você não precisa ter a plena fontes de eg Firefox, uma vez que você não acessar partes do front end dentro de um componente. Além disso, uma vez que contém um componente funcionalidade básica, que se destina a executar com todos os produtos da Mozilla plataforma. Portanto, não faz sentido usar um produto específico para construir geral funcionalidade. Essa é a razão pela qual o Gecko SDK foi concebido.

-

Não confundir com o Gecko SDK XULRunner. O Gecko SDK é um conjunto de cabeçalho arquivos e ferramentas utilizadas para desenvolver geral XPCOM componentes que acrescentam funcionalidades à plataforma existente, que XULRunner é um quadro que pode ser usada para executar autônomo ou incorporados aplicações baseadas na Mozilla quadro.

-

O Gecko SDK contém todas as ferramentas necessárias para fazer script e cabeçalhos NPAPI plugins incluindo o compilador xpidl / linker e as última

-

Receba o SDK

-
-

Atualizações

-
-

Não há necessidade de fazer o download ou reconstruir o Gecko SDK correspondentes às atualizações de segurança do Mozilla (por exemplo, o Mozilla 1.7.3), uma vez que os cabeçalhos e cola libs no Gecko SDK geralmente não são alteradas como resultado de atualizações de segurança. Você tem que fazer para receber e distribuir o mais recente Gecko componentes (gklayout.dll etc)

-

Baixando

-
-

Ao fazer o download do SDK Gecko, é importante escolher a versão que corresponde à versão do Mozilla mais rapidamente que você deseja atingir. Em outras palavras, você não deve fazer o download do SDK 1,7 Gecko se pretender utilizar o componente com 1,6 Mozilla. Isto é importante porque a compatibilidade binária é assegurada apenas com versões futuras do Gecko runtime. Para este tutorial, vamos estar usando a versão 1,7 do Gecko SDK para que o nosso componente binário é compatível com Mozilla 1.7 (e quaisquer produtos derivados, tais como Firefox 1,0 ou Netscape 7.2).

diff --git a/files/pt-pt/install.rdf/index.html b/files/pt-pt/install.rdf/index.html deleted file mode 100644 index 370f879e28..0000000000 --- a/files/pt-pt/install.rdf/index.html +++ /dev/null @@ -1,255 +0,0 @@ ---- -title: install.rdf -slug: install.rdf -tags: - - Extensões - - Toolkit API -translation_of: Archive/Mozilla/Creating_a_Skin_for_SeaMonkey_2.x/install.rdf ---- -

Introdução

-

Um Manifesto de Instalação é o arquivo que o Gerenciador de Complementos ativa os usos do aplicativo XUL para determinar informações sobre um complemento enquanto está sendo instalado. Ele contém metadados identificando o complemento, proporcionando informações sobre quem o criou, onde podem ser encontradas mais informações sobre ele, quais versões do aplicativo são compatíveis com esta, como esta pode ser atualizada, e assim por diante.

-

O formato do Manifesto de Instalação é RDF/XML.

-

O arquivo deve ter o nome de install.rdf e estar no nível mais elevado de um arquivo XPI de complemento.

-

Disposição

-

A disposição básica de um Manifesto de Instalação é assim:

-
<?xml version="1.0"?>
-
-<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-     xmlns:em="http://www.mozilla.org/2004/em-rdf#">
-  <Description about="urn:mozilla:install-manifest">
-    <!-- properties -->
-  </Description>
-</RDF>
-
-

Algumas propriedades são necessárias, algumas são opcionais. Algumas tem strings com valores simples, algumas são complexos recursos.

-

Referência necessária da propriedade

-

Seu Manifesto de Instalação deve especificar estas propriedades corretamente, caso contrário seu complemento poderá não instalar.

-

id (identificação)

-

O id da extensão, o qual é um:

- -

extensionname@organization.tld

-

O último formato é significantemente mais fácil de gerar e manipular. O Firefox 1.5 checará para assegurar que seu id caia em um formato ou outro e irá recusar-se a instalar complementos que tenham ids malformados.

-

Exemplos

-
<em:id>myextension@mysite.com</em:id>
-
-<em:id>{daf44bf7-a45e-4450-979c-91cf07434c3d}</em:id>
-
-

version (versão)

-

Uma string de versão identifica a versão do complemento fornecido.

-

Para o Firefox/Thunderbird 1.0, o formado deve ser conforme as regras especificadas em en:Extension Versioning, Update and Compatibility. Para Firefox/Thunderbird 1.5, veja en:Toolkit version format.

-

Exemplos

-
<em:version>2.0</em:version>
-
-<em:version>1.0.2</em:version>
-
-<em:version>0.4.1.2005090112</em:version>
-
-
-

Firefox 1.5 / XULRunner 1.8 - complementos que não utilizam um formato de versão válida não serão instalados. O formato da versão é diferente, embora seja compatível com 1.0 mais antigas.

-

Para complementos hospedados em addons.mozilla.org — o site de atualizações Mozilla pode re-empacotar seu complemento e corrigir ou rejeitar strings de versão malformadas.

-

type (tipo)

-

Um valor inteiro representando o tipo do complemento.

- - - - - - - - - - - - - - - - - - - - - - - -
2Extensões
4Temas
8Locais
16Plugins
32Multiple Item Package
-

Exemplos

-
<em:type>2</em:type>
-
-

Firefox 1.5 Esta propriedade foi adicionada ao Firefox 1.5, e é somente necessário para complementos que não sejam Extensões e Temas.

-

targetApplication (alvo do aplicativo)

-

Um objeto especificando um aplicativo marcado por este complemento. Este meio que o complemento irá trabalhar com o aplicativo identificado pela propriedade id (<em:id>) especificado (para uma lista compreensível de IDs de aplicativos veja "Valid App Versions for Addon Developers" em Mozilla Addons FAQ), da versão mínima (<em:minVersion>) subindo e incluindo a versão máxima (<em:maxVersion>). Estas strings da versão são formatadas do mesmo modo como version property e serão comparados à versão do aplicativo; isto permite ao autor da extensão especificar quais as versões do Firefox e extensões foram testadas com.

-

Nota: O Firefox 1.0-1.0.6 todo tem uma versão de aplicativo de 1.0. Atualizações de segurança e estabilidade do Firefox 1.5 têm versão do aplicativo 1.5.0.1, 1.5.0.2, etc. Extensões compatíveis com o Firefox ou Thunderbird 1.5 devem especificar uma maxVersion de 1.5.0.*, de modo que são automaticamente compatíveis com atualizações de segurança e estabilidade.

-

Extensões compatíveis com o Firefox 2 devem especificar uma maxVersion de 2.0.0.*

-

O Manifesto de Instalação deve especificar ao menos um destes objetos, e pode especificar mais se os alvos múltiplos da aplicação do complemento suportarem o Gerenciador de Complementos (e.g. Firefox e Thunderbird)

-

Exemplos

-
<em:targetApplication>
- <Description>
-  <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id> Firefox
-  <em:minVersion>1.5</em:minVersion>
-  <em:maxVersion>3.0.*</em:maxVersion>
- </Description>
-</em:targetApplication>
-
-

name (nome)

-

O nome do complemento — entendido por exibir o UI.

-

Exemplos

-
<em:name>My Extension</em:name>
-
-

Referência de propriedade opcional

-

Você pode necessitar fornecer estas propriedades, dependendo das capaciadades do seu complemento.

-

 

-

description (descrição)

-

Uma pequena descrição do complemento &mdash para exibição na interface de usuário. Esta descrição deve caber em uma curta linha de texto.

-

Exemplos

-
<em:description>Ferramentas avançadas de rodapé.</em:description>
-
-

creator (criador)

-

O nome do criador/principal desenvolvedor &mdash para exibição na interface de usuário.

-

Exemplos

-
<em:creator>John Doe</em:creator>
-
-

or

-
<em:creator>CoolExtension Team</em:creator>
-
-

developer (desenvolvedor)

-

Os nomes dos co-desenvolvedores. Você pode especificar mais de um valor para especificar múltiplos desenvolvedores. Novo no Firefox 2.0

-

Exemplos

-
<em:developer>Jane Doe</em:developer>
-<em:developer>Koos van der Merwe</em:developer>
-
-

translator (tradutor)

-

Os nomes dos tradutores. Você pode especificar mais de um valor para especificar múltiplos tradutores. Novo no Firefox 2.0

-

Exemplos

-
<em:translator>Janez Novak</em:translator>
-<em:translator>Kari Nordmann</em:translator>
-
-

contributor (contribuidor)

-

Os nomes de contribuidores adicionais. Você pode especificar mais de um valor para especificar múltiplos contribuidores.

-

Exemplos

-
<em:contributor>John Doe</em:contributor>
-
-<em:contributor>John Doe</em:contributor>
-<em:contributor>Jane Doe</em:contributor>
-<em:contributor>Elvis Presley</em:contributor>
-
-

homepageURL (página principal da URL)

-

Um link para a página principal do complemento &mdash para exibir na inteface de usuário.

-

Exemplos

-
<em:homepageURL>http://www.foo.com/</em:homepageURL>
-
-

updateURL (URL de atualização)

-

Um link para um arquivo customizado de Manifesto de Atualização que especifique atualizações disponíveis para o complemento. O formato é descrito abaixo. Se habilitado, o Gerenciador de Complementos periodicamente checará com o arquivo de Manifesto para determinar se novas versões estão disponíveis.

-

Seu servidor deve enviar este arquivo como text/rdf ou o checador de atualizações não irá trabalhar. text/xml também parece trabalhar (projetos em mozdev.org)

-

O Gerenciador de Complementos irá substituir os seguintes valores neste URL em casos de você querer gerar a resposta RDF dinamicamente, tal como usar PHP ou CGI:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
%REQ_VERSION%A versão requisitada. Atualmente 1
%ITEM_ID%O id do complemento que terá de atualizar
%ITEM_VERSION%A version (versão) do complemento que terá de atualizar
%ITEM_MAXAPPVERSION%A maxVersion (versão máxima) do objeto targetApplication (alvo de aplicação) correspondente à aplicação atual para o complemento ser atualizado.
%APP_ID%O id atual da aplicação
%APP_VERSION%A version (versão) atual aplicação
%APP_OS%O valor de OS_TARGET do sistema de construção do Firefox, identificando o sistema operacional a ser usado. Novo no Firefox 1.5
%APP_ABI%O valor de TARGET_XPCOM_ABI do sistema de construção do Firefox, identificando o compilador/combinação de arquitetura usada para compilar a atual aplicação. Novo no Firefox 1.5
-

Exemplos

-
<em:updateURL>http://www.foo.com/update.cgi?id=%ITEM_ID%&amp;version=%ITEM_VERSION%</em:updateURL>
-<em:updateURL>http://www.foo.com/extension/windows.rdf</em:updateURL>
-
-

Para complementos hospedados em addons.mozilla.org: Você não pode especificar a propriedade de URL de atualização. Por padrão, aplicativos Mozilla usando o Gerenciador de Complementos (tal como o Firefox e o Thunderbird) enviaram requerimentos de atualização para addons.mozilla.org usando o serviço web padrão. Toda a vez que você atualiza para uma nova versão do seu complemento ou muda seus parâmetros de compatibilidade através da interface do autor, seu Manifesto de Atualização será gerado automaticamente.

-

Formato do Manifesto de Atualização: O Manifesto de Atualização é uma fonte de dados RDF/XML. Para exemplos de um Manifesto de Atualização, veja Extension Versioning, Update and Compatibility e en:Enabling Extension Updates (external).

-

optionsURL (URL de opções)

-

A URL chrome:// da caixa de diálogo das opções da extensão. Isto é utilizável somente para extensões. Se esta propriedade é especificada, quando a extensão é selecionada na lista de Extensões, o botão de Opções é habilitado e mostrará isto.

-

Exemplos

-
<em:optionsURL>chrome://myext/content/options.xul</em:optionsURL>
-
-

aboutURL (URL sobre)

-

A URL chrome:// da caixa de diálogo de opções da extensão. Isto é utilizável somente para extensões. Se esta propriedade é especificada, quando a extensão é selecionada na lista de Extensões, o link Sobre... no menu de contexto da extensão exibirá este diálogo, antes que o padrão.

-

Exemplos

-
<em:aboutURL>chrome://myext/content/about.xul</em:aboutURL>
-
-

iconURL (URL de ícones)

-

Um URL chrome:// para um ícone 32x32 para exibir na lista de complementos. Se esta propriedade não é especificada um ícone padrão é utilizado.

-
<em:iconURL>chrome://myext/skin/icon.png</em:iconURL>
-
-

Nota: Para o exemplo acima trabalhar você também terá que adicionar uma linha skin package ao seu arquivo chrome.manifest. Veja Registro Chrome. Alternativamente você pode colocar seu ícone no diretório especificado na linha do seu content package.

-

hidden (oculto)

-

Um valor booleano que pode ser true (verdadeiro) faz que o complemento não apareça na lista de complementos, proporcionando um complemento que é instalado em uma área de acesso restrito (então ela não trabalhará para complementos instalados no perfil). Isto é para empacotar ganchos de integração às aplicações maiores onde ter uma entrada na lista de Extensões não faz sentido.

-

Exemplos

-
<em:hidden>true</em:hidden>
-
-

targetPlatform (plataforma alvo)

-

Uma string especificando uma plataforma que o complemento suporte. Isto contém qualquer valor de OS_TARGET sozinho ou combinado com :en:TARGET_XPCOM_ABI, separado por sublinhado (_).

-

OS_TARGET é típicamente a saída do comando 'uname -s' na plataforma alvo, e.g.:

- -

Você pode especificar múltiplas propriedades targetPlatform por manifesto. Se algum valor inicia os parâmetros de construção do aplicativo, ele estará instalado; se não, o usuário receberá uma mensagem de erro apropriada.

-

Exemplos

-
<em:targetPlatform>WINNT_x86-msvc</em:targetPlatform>
-
-<em:targetPlatform>Linux</em:targetPlatform>
-
-<em:targetPlatform>Darwin_ppc-gcc3</em:targetPlatform>
-
-

Normalmente, você usaria somente a parte do sistema operacional para temas ou para extensões que não são interamente "cross-plataform". Para extensões incluindo componentes binários (compilados), você nunca deve usar o sistema operacional sozinho, mas inclua o :en:ABI (s) que compilou os componentes com. Se você quer incluir múltiplas versões de componentes, você devia usar também :en:Platform-specific Subdirectories.

-

Notas

- - -

Firefox 1.5 Esta propriedade foi adicionada para o Firefox/Thunderbird 1.5. Versões anteriores destes aplicativos irão ignorar as restrições e instalaram o complemento sem levar em conta a plataforma.

-

Referência de propriedade obsoleta

-

Estas propriedades são requisitadas em versões antigas do Gerenciador de Complementos, mas tem que ser recolocadas com mecanismos novos e melhores.

-

file (arquivo)

-

Firefox 1.0 Esta propriedade aponta para um arquivo chrome .jar que contém pacotes chrome que requisitam registro com o Registro Chrome.

-

A propriedade <em:file> tem um objeto de valor complexo. O URL deste valor é urn:mozilla:extension:file:jarFile.jar onde jarFile.jar é o nome do arquivo jar que contém o pacote de arquivos chrome, un-jarred (e.g. urn:mozilla:extension:file:directory).

-

Este objeto tem uma propriedade de package (pacote) (com um caminho demtro do arquivo jar ou diretório que leva à localização de onde o arquivo contents.rdf está responsável pelo registro de onde o pacote está localizado), uma propriedade locale (idem, mas para registrar o local) e a propriedade skin (idem, mas para registrar o material do tema).

-

Em extensões para o Firefox 1.5, esta propriedade não é necessária: o chrome.manifest no nível máximo do XPI é usado para localizar o chrome para registrar. Se não há chrome.manifest, esta propriedade ainda é lida pelo Gerenciador de Complementos e o chrome.manifest é gerado de um antigo estilo contents.rdf.

-

Exemplos

-
<em:file>
- <Description about="urn:mozilla:extension:file:myext.jar">
-  <em:package>content/myext/</em:package>
-  <em:locale>locale/en-US/myext/</em:locale>
-  <em:skin>skin/classic/myext/<em:skin>
- </Description>
-</em:file>
-
-

Um Manifesto de Instalação pode especificar múltiplas propriedades file, um por um arquivo jar ou subdiretório que contenha o chrome para registrar.

-

Glossário

-

Área de acesso restrito

-

Uma área de acesso restrito é um local de instalação que pode ser restrito com uma conta de acesso restrito, sem ter em conta se a situação é restringida com privilégios do usuário atual (veja nsIInstallLocation::restricted). Normalmente, a pasta ($APPDIR)/extensions e a localização do registro de instalação embaixo de HKEY_LOCAL_MACHINE (veja en:Adding Extensions using the Windows Registry para detalhes) são restritas.

-

Os ($PROFILE)/extensions e HKEY_CURRENT_USER locais de instalação, na outra mão, não são restritos.

diff --git a/files/pt-pt/melhorias_das_css_no_firefox_3/index.html b/files/pt-pt/melhorias_das_css_no_firefox_3/index.html deleted file mode 100644 index 5f192a3142..0000000000 --- a/files/pt-pt/melhorias_das_css_no_firefox_3/index.html +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Melhorias das CSS no Firefox 3 -slug: Melhorias_das_CSS_no_Firefox_3 -tags: - - CSS - - Firefox 3 - - Todas_as_Categorias -translation_of: Mozilla/Firefox/releases/3/CSS_improvements ---- -
{{FirefoxSidebar}}

{{ Fx_minversion_header(3) }}

-

O Firefox 3 oferece algumas melhorias à sua implementação CSS. Enquanto estas mudanças são documentadas nas páginas apropriadas da documentação, este artigo proporciona uma introdução destas melhorias para que desenvolvedores possam aprender mais facilmente quais foram estas mudanças.

- -

Veja também

- -

Categorias

-

Interwiki Language Links

-

{{ languages( { "en": "en/CSS/improvements_in_Firefox_3", "es": "es/Mejoras_CSS_en_Firefox_3", "fr": "fr/Am\u00e9liorations_CSS_dans_Firefox_3", "ja": "ja/CSS_improvements_in_Firefox_3", "pl": "pl/Poprawki_CSS_w_Firefoksie_3" } ) }}

diff --git a/files/pt-pt/mozilla/add-ons/amo/index.html b/files/pt-pt/mozilla/add-ons/amo/index.html deleted file mode 100644 index 3857ed65ca..0000000000 --- a/files/pt-pt/mozilla/add-ons/amo/index.html +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: AMO -slug: Mozilla/Add-ons/AMO -tags: - - NeedsTranslation - - TopicStub -translation_of: Mozilla/Add-ons/AMO ---- -

Content to be added.

diff --git a/files/pt-pt/mozilla/add-ons/amo/policy/em_destaque/index.html b/files/pt-pt/mozilla/add-ons/amo/policy/em_destaque/index.html deleted file mode 100644 index 71eafffe67..0000000000 --- a/files/pt-pt/mozilla/add-ons/amo/policy/em_destaque/index.html +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: AMO - Políticas de Extensões em Destaque -slug: Mozilla/Add-ons/AMO/Policy/Em_destaque -translation_of: Mozilla/Add-ons/AMO/Policy/Featured ---- -

{{AddonSidebar}}

- -

Featured add-ons are top-quality extensions and themes highlighted on AMO, Firefox's Add-ons Manager, and across other Mozilla websites. These add-ons showcase the power of Firefox customization and are useful to a wide audience.

- -

Featured extensions are chosen by the Featured Extensions Advisory Board, a small group of extension developers and fans from the Mozilla community who have volunteered to review and vote on nominations.

- -

Todos os meses, são escolhidas novas extensões em destaque.

- -

Critérios para Extensões em Destaque

- -

Before nominating an extension to be featured, please ensure it meets the following criteria:

- -
    -
  1. The extension must have a complete and informative listing on AMO. This means: -
      -
    • a 64-pixel custom icon
      • -
    • a clear and concise name (no lengthy keywords)
      • -
    • a clear and concise summary of the extension's functionality
      • -
    • detailed description and privacy policy, if applicable
      • -
    • updated screenshots of the extension's functionality
      • -
    -
    2. -
  2. The extension must have excellent user reviews and any problems or support requests must be promptly addressed by the developer.
    3. -
  3. The extension must have a minimum of 500 users.
    4. -
  4. The extension must be built with WebExtensions API.
    5. -
  5. The extension must be compatible with the latest release of Firefox.
    6. -
  6. Most importantly, the extension must have wide consumer appeal to Firefox's users and be outstanding in nearly every way: user experience, performance, security, and usefulness or entertainment value.
    7. -
- -

Painel de Descoberta

- -

The Get Add-ons section (also referred to as the Discovery Pane) in about:addons serves a distinct editorial function: it is a tightly curated list of extensions and themes selected by Mozilla staff to address an array of the most common user needs (e.g. ad blockers, screenshot tools, etc.). The Discovery Pane is primarily intended to introduce extensions to Firefox users who have limited experience with browser customization. As such, we only select extensions that meet the highest standards of functionality, user experience, and Firefox compatibility.

- -

Only content that is part of AMO’s Featured Extensions collection will be considered for the Discovery Pane; please note that featured content must meet certain criteria.

- -

Discovery Pane content is updated monthly, though some highly popular extensions may remain on the page for an indefinite period of time.

- -

If you’d like to nominate a great extensions for consideration in the Discovery Pane, please send us a link to the add-on on AMO to amo-featured@mozilla.org and we’ll add your nomination to the editorial review queue. There’s no need to mention you’re nominating add-ons specifically for the Discovery Pane, but feel free to note that if you like.

- -

Nomear um Extra

- -

If you wish to nominate an extension to be featured and it meets the criteria above, send an email to amo-featured@mozilla.org with:

- - - -

Extension nominations are reviewed by the Advisory Board once a month. Common reasons for rejection include lacking wide appeal to consumers, a suboptimal user experience, quality or security issues, incompatibility, and similarity to another featured extension. Rejected extension cannot be re-nominated within 3 months.

- -

Rodar Extensões em Destaque

- -

Mozilla and the Featured Extensions Advisory Board regularly evaluate and rotate out featured extensions. Some of the most common reasons for extensions being removed from the featured list are:

- - - -

Aderir ao Conselho Consultivo de Extensões em Destaque

- -

Every six months a new Advisory Board is chosen based on applications from the add-ons community. Members must:

- - - -

Members of the Mozilla Add-ons team may veto any extension's selection because of security, privacy, compatibility, or any other reason, but in general it is up to the Board to select extensions to feature.

- -

This featured policy only applies to the addons.mozilla.org global list of featured extensions. Extensions featured in other locations are often pulled from this list, but Mozilla may feature any extension in other locations without the Board's consent. Additionally, locale-specific features override the global defaults, so if a locale has opted to select its own features, some or all of the global features may not appear in that locale.

- -

Follow the Add-ons Blog or @mozamo on Twitter to learn when the next application period opens.

- -

Última atualização: 12 de abril de 2018

- -

How up-and-coming add-ons become featured and what's involved in the process.

diff --git a/files/pt-pt/mozilla/add-ons/amo/policy/index.html b/files/pt-pt/mozilla/add-ons/amo/policy/index.html deleted file mode 100644 index 2dd894f5bd..0000000000 --- a/files/pt-pt/mozilla/add-ons/amo/policy/index.html +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Políticas AMO -slug: Mozilla/Add-ons/AMO/Policy -tags: - - NeedsTranslation - - TopicStub -translation_of: Mozilla/Add-ons/AMO/Policy ---- -

Mozilla está empenhada em garantir uma grande experiência com os extras para os nossos utilizadores e desenvolvedores. Por favor, reveja as políticas abaixo antes de submeter o seu extra.

- -
-
Developer Agreement
-
Effective January 5, 2016
Review Process
-
Add-ons extend the core capabilities of Firefox, allowing users to modify and personalize their Web experience. A healthy add-on ecosystem, built on trust, is vital for developers to be successful and users to feel safe making Firefox their own. For these reasons, Mozilla requires all add-ons to comply with the following set of policies on acceptable practices. The below is not intended to serve as legal advice, nor is it intended to serve as a comprehensive list of terms to include in your add-on’s privacy policy.
Featured Add-ons
-
How up-and-coming add-ons become featured and what's involved in the process.
Contacting us - -

How to get in touch with us regarding these policies or your add-on.

- -
diff --git "a/files/pt-pt/mozilla/add-ons/amo/policy/revis\303\265es/index.html" "b/files/pt-pt/mozilla/add-ons/amo/policy/revis\303\265es/index.html" deleted file mode 100644 index 96e6d880f5..0000000000 --- "a/files/pt-pt/mozilla/add-ons/amo/policy/revis\303\265es/index.html" +++ /dev/null @@ -1,160 +0,0 @@ ---- -title: Políticas de Extras -slug: Mozilla/Add-ons/AMO/Policy/Revisões -tags: - - Extras - - Política de Revisão -translation_of: Mozilla/Add-ons/AMO/Policy/Reviews ---- -

{{AddonSidebar}}

- -

Os extras estendem os recursos principais do Firefox, permitindo que os utilizadores modifiquem e personalizem a sua experiência na Web. Um ecossistema de extras saudável, baseado na confiança, é vital para que os programadores sejam bem-sucedidos e os utilizadores se sintam seguros, tornando o Firefox deles próprio. Por estes motivos, a Mozilla requer que todos os extras estejam em conformidade com o seguinte conjunto de políticas sobre as práticas aceitáveis. O abaixo, não se destina para servir como aconselhamento jurídico, nem pretende servir como uma lista abrangente de termos para incluir na política de privacidade do seu extra.

- -

Todos os extras estão sujeitos a estas políticas, independentemente de como eles são distribuídos. Os extras que não estejam em conformidade com estas políticas podem estar sujeitos à rejeição ou desativação pela Mozilla.

- -

Sem Surpresas

- -

As surpresas podem ser apropriadas em muitas situações, mas não são bem-vindas quando a segurança, a privacidade e o controlo do utilizador estão em jogo. É extremamente importante ser o mais transparente possível quando submeter um extra. Os utilizadores deverão ser capazes de discernir facilmente qual é a funcionalidade do seu extra e não receber experiências inesperadas do utilizador depois de o instalal.

- -

Funcionalidades Inesperadas

- -

“Funcionalidades" inesperadas são aquelas que não estão relacionadas com a função principal do extra e provavelmente não são do nome do extra ou da descrição esperada por um utilizador que está a instalar esse extra.

- -

Um extra deveria incluir qualquer funcionalidade inesperada que se enquadre numa das seguintes categorias:

- - - -

Então, a(s) funcionalidade(s) "inesperada(s)" devem seguir todos os seguintes requisitos:

- - - -

Conteúdo

- -

Os extras que utilizarem as marcas registadas da Mozilla devem obedecer à Política de Marcas Registadas da Mozilla. Se o extra utiliza “Firefox” no seu nome, o padrão de nomeação que o extra deve seguir é “<nome do Extra> por Firefox”.

- -

Além disso, os extras listados em Extras para o Firefox (AMO) devem seguir as seguintes políticas:

- - - -

Linhas Diretrizes de Submissão

- -

Os extras devem funcionar apenas conforme o descrito e devem fornecer uma experiência de utilizador atraente. Com base na descrição do extra, um utilizador deve ser capaz de entender e utilizar os recursos do extra sem exigir conhecimento especializado. Dicas sobre como criar uma boa experiência do utilziador para o seu extra podem ser encontradas aqui.

- -

During review, the add-on undergoes basic testing in addition to code review. To facilitate the functional testing, the add-on author must provide testing information and, if applicable, testing credentials required to use the add-on if an account is needed for any part of the add-on’s functionality.

- -

Issues brought up during review must be addressed using best efforts. If corrections have been requested, the new version should not contain unrelated changes, as this complicates the review process and can lead to further rejections.

- -

Submissão de Código Fonte

- -

Add-ons may contain transpiled, obfuscated, minified or otherwise machine-generated code, but Mozilla needs to review a copy of the human-readable source code. The author must provide this information to Mozilla during submission as well as instructions on how to reproduce the build.

- -

The provided source code will be reviewed by an administrator and will not be redistributed in any way. The code will only be used for the purpose of reviewing the add-on. Failure to provide this information will result in rejection.

- -

Please read our Source Code Submission guidelines to avoid unexpected rejections.

- -

Práticas de Desenvolvimento

- -

In general, developers are free to maintain their add-ons in the manner they choose. However, in order to maintain appropriate data security and effectively review code, we do have certain technical requirements that all add-ons must meet. In particular, potentially dangerous APIs may only be used in ways that are demonstrably safe, and code within add-ons that cannot be verified as behaving safely and correctly may need to be refactored.

- -

While any code, method or practice in a submitted add-on is subject to review and rejection, the following requirements are of particular importance:

- - - -

Gestão, Recolha e Divulgação de Dados

- -

You must disclose how the add-on collects, uses, stores and shares user data in the privacy policy field on AMO. Mozilla expects that the add-on limits data collection whenever possible, in keeping with Mozilla’s Lean Data Practices and Mozilla’s Data Privacy Principles, and uses the data only for the purpose for which it was originally collected.

- -

User data includes all information the add-on collects, regardless of the manner. It can be personal data actively provided by the user (such as a name or email address), technical data (such as operating system, build ID, version numbers, crash reports, activation, updates), and interaction or activity data (add-on activity data, visited URLs, console logs), including interactions with Firefox.

- -

The add-on’s privacy policy must be the full policy text; it cannot be a link to an externally hosted privacy policy. In addition, the privacy policy must:

- - - -

A summary of this information must be included in the add-on’s listing description. Finally, you and your add-on must also comply with all applicable data privacy laws as well as any other laws that may apply to your specific add-on.

- -

Interações do Utilizador e Dados Técnicos

- - - -

Cookies

- - - -

Dados Pessoais

- - - -

Protocolos de Privacidade Adicionais

- - - -

Vulnerabilidades de Segurança

- -

Because add-ons run in an environment with elevated privileges relative to ordinary web pages, they present a very serious set of security considerations. They have the potential to open security holes not only in the add-ons themselves, but also in the browser, in web pages, and, in particularly distressing cases, the entire system the browser is running on.

- -

As a result, we take our security policies very seriously and apply them to all add-ons, whether hosted on AMO or not. We expect all add-ons to be secure and well-maintained in handling both their own data and their user’s data. They must also securely manage all of their interactions with the web, the browser and the operating system.

- -

Monetização

- - - -

Conformidade e Lista de Bloqueio

- -

Para os extras que não correspondem com estas políticas, a Mozilla pode rejeitar ou bloquear as versões afetadas ou extras completos, dependendo da extensão da sua não conformidade.

- -

Geralmente, a Mozilla tentará entrar em contacto com o(s) programador(es) do extra e fornecer um prazo razoável para que os problemas sejam corrigidos antes que um bloqueio seja implementado. Se um extra for considerado malicioso ou se os seus programadores tiverem se mostrado inalcançáveis ou não responderem, ou no caso de violações recorrentes, a inclusão na listagem de bloqueio ser imediata.

- -

A Mozilla reserva o direito de bloquear ou eliminar a conta do programador em addons.mozilla.org, evitando assim a utilização adicional do serviço.

diff --git "a/files/pt-pt/mozilla/add-ons/cri\303\247\303\243o_de_extens\303\265es_firefox_com_sistema_mozilla/index.html" "b/files/pt-pt/mozilla/add-ons/cri\303\247\303\243o_de_extens\303\265es_firefox_com_sistema_mozilla/index.html" deleted file mode 100644 index 35a9c7fbe1..0000000000 --- "a/files/pt-pt/mozilla/add-ons/cri\303\247\303\243o_de_extens\303\265es_firefox_com_sistema_mozilla/index.html" +++ /dev/null @@ -1,518 +0,0 @@ ---- -title: >- - Criação de extensões personalizadas do Firefox com o sistema de criação da - Mozilla -slug: Mozilla/Add-ons/Crição_de_extensões_Firefox_com_Sistema_Mozilla -translation_of: >- - Archive/Add-ons/Creating_Custom_Firefox_Extensions_with_the_Mozilla_Build_System ---- -

{{AddonSidebar}}

- -

Existe uma abundância de  material na criação de extensões para Firefox. Todos estes documentos atualmente assumem, contudo, que está a desenvolver a sua extensão utilizando apena JavaScript e XUL. Para extenões complexas, poderá ser necessário criar componentes em C++ que proporcionam uma funcionalidade adicional. Os motivos pelos quais poderá querer incluir componentes C++ na sua extensão incluem:

- -
-
-
-
-
-
 
-
-
-
-
-
- - - -
Note: With the modern JIT Javascript Engine in Gecko and js-ctypes more extension code can be written only in JavaScript than ever before.  Please consider all of your options carefully before deciding to use native code (C++) in your extension. In addition, binary components need to be recompiled for every major Firefox release, which can be frustrating.
- -

This article describes how to set up the development environment for a large, complex Firefox extension with any or all of the above-mentioned requirements. I should also stress that you do not have to build Mozilla or use the Mozilla build system if you want to create C++ components for Mozilla. If you are just looking to create an XPCOM component or two, this is probably overkill, and you might want to take a look at this guide instead. On the other hand, if you are an experienced developer or team, and you know that you are going to build a large, complex extension, you would do well to consider the approach described in this article.

- -

One final note: I’ve only tried these techniques inside Firefox, but they’ll probably work more or less unchanged on other Gecko-based platforms like Thunderbird or Seamonkey. If someone can confirm this and/or provide guidelines for what’s different, I’ll update the article to incorporate this information.

- -

Bambi Cruza-se com Mozilla

- -

None of this is for the faint of heart. In particular, the initial step involves building Mozilla, which is a huge - nay, gargantuan! - project. Many intelligent developers have been driven to the brink of insanity trying to build it for the first time. If you're not an experienced C++ developer, I wouldn’t even bother. Stick to JavaScript.

- -

Nas Plataformas do Windows

- -

The first time I built Mozilla I used this guide. I can’t even remember why anymore, but I got stuck in a number of places, and the whole affair ended up taking far longer than I originally expected. Much furniture was smashed, much hair torn out by the roots. Here’s a comprehensive looking guide that’s gotten good reviews. Follow every step methodically and you’ll probably be alright. Focus on the fact that once you get the build working, it’ll probably work effortlessly from then on. Maybe.

- -

Em Outras Plataformas

- -

On other platforms, namely Linux and MacOS, the process is much easier. All the tools for building are available built-in, and therefore all you have to do is run some commands in the terminal. You can find full instructions for almost any OS here.

- -

Estruturar o Seu Projeto

- -

Mozilla includes a number of complex extensions that are integrated into its build process. It has thus been necessary to solve all of the issues involved in creating and registering XPCOM components, building JAR files and manifests, installing the lot into the Firefox extensions/ directory and so forth. So it behooves us to piggyback on this infrastructure to build our extension.

- -

First of all, think of a catchy name for your extension and create a directory with that name under the /mozilla/extensions/ directory. Use only lowercase letters. You should see a bunch of other directories (inspector/, reporter/ and so forth) at the same level in the build tree.

- -

Note that before actually building anything, the Mozilla build system invokes a configuration process that generates the actual makefiles used for the build from makefile templates called Makefile.in. The actual makefiles tend to be very similar or identical to the templates, but the extra flexibility gained from having the makefiles generated dynamically is one of the things that makes the build system so powerful.

- -

Anatomia de uma Extensão C++ Simples

- -

We assume that you are using C++ to write XPCOM components that can be used either from other C++ components or from JavaScript. The process of creating a component is actually relatively straightforward when the Mozilla build system is used.

- -

In the simplest case, a component will consist of a single main directory with two subdirectories, public/ and src/. The main directory and each subdirectory must contain a Makefile.in (from now on I’ll just refer to this file as a makefile although we know that it is actually used to generate the real makefile). This makefile says two things. First of all, it lists the subdirectories that make up the extension, so the build system knows where to look for additional makefiles. Secondly, it instructs the build system to create a new extension, rather than copying the components directly into Firefox’s binary directory. The main advantage of using an extension is that it is easy to package everything up and install it on another machine.

- -

So here’s your basic, plain-vanilla top-level makefile (Makefile.in in the main extension directory):

- -
DEPTH		= ../..
-topsrcdir	= @top_srcdir@
-srcdir		= @srcdir@
-VPATH		= @srcdir@
-
-include $(DEPTH)/config/autoconf.mk
-
-MODULE = myextension
-
-DIRS		= public src
-
-XPI_NAME		= myextension
-INSTALL_EXTENSION_ID	= myextension@mycompany.com
-XPI_PKGNAME		= myextension
-
-DIST_FILES = install.rdf
-
-include $(topsrcdir)/config/rules.mk
-
- -

A detailed description of the make process, describing the key features of this makefile, can be found here. MODULE and XPI_NAME are both set to the name of your extension; they should be repeated in all project makefiles so that all of the files land in the same place in the XPI staging area (see below). INSTALL_EXTENSION_ID is the unique ID of your extension. This can be a GUID, but the format shown above is prettier and, let’s face it, a lot easier to remember. You don’t have to provide an XPI_PKGNAME, but if you do an XPI file, suitable for distribution, is automatically created in the root of the XPI staging area (/mozilla/$(MOZ_OBJDIR)/dist/xpi-stage/).

- -

Every extension must include an install.rdf file that tells Firefox how to install it. This file should be located in the main extension directory and look something like this:

- -
<?xml version="1.0"?>
-
-<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-     xmlns:em="http://www.mozilla.org/2004/em-rdf#">
-  <Description about="urn:mozilla:install-manifest">
-    <em:id>myextension@mycompany.com</em:id>
-    <em:version>0.1</em:version>
-
-    <em:targetApplication>
-      <!-- Firefox -->
-      <Description>
-        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
-        <em:minVersion>1.0+</em:minVersion>
-        <em:maxVersion>1.0+</em:maxVersion>
-      </Description>
-    </em:targetApplication>
-
-    <!-- front-end metadata -->
-    <em:name>My First Extension</em:name>
-    <em:description>Just an example.</em:description>
-    <em:creator>allpeers.com</em:creator>
-    <em:homepageURL>http://www.allpeers.com/blog/</em:homepageURL>
-  </Description>
-</RDF>
-
- -

There's a detailed description of the format of the install.rdf file. Use the DIST_FILES variable in the makefile to tell make to copy the file into the extension directory and (optional) XPI file.

- -

Interfaces Públicas

- -

The public/ directory contains any interfaces that need to be accessed by other modules. These can be IDL files describing XPCOM interfaces, which are used to generate normal C++ header files for inclusion in your source files. They can also be normal C++ header files that are to be used directly by other modules. The easiest way to accomplish the latter is to use inline implementations for all methods so you don’t have any additional linking dependencies. Otherwise you will have to link statically to your module if you use these public headers in other modules. Personally I would discourage this practice (among other things, static linking means the same code gets loaded more than once into memory, and the code won’t be available from JavaScript or other non-C++ languages) and encourage the use of XPCOM wherever possible.

- -

The makefile in the public/ directory should follow this model:

- -
DEPTH		= ../../..
-topsrcdir	= @top_srcdir@
-srcdir		= @srcdir@
-VPATH		= @srcdir@
-
-include $(DEPTH)/config/autoconf.mk
-
-MODULE		= myextension
-XPIDL_MODULE	= myextension
-
-XPI_NAME = myextension
-
-EXPORTS = \
-  myHeader.h \
-  $(NULL)
-
-XPIDLSRCS = \
-  myIFirstComponent.idl \
-  myISecondComponent.idl \
-  $(NULL)
-
-include $(topsrcdir)/config/rules.mk
-
- -

XPIDL_MODULE is the name of the generated XPT file that contains type information about your IDL interfaces. If you have multiple modules, make absolutely sure that you use a different value for XPIDL_MODULE for each one. Otherwise the first module’s XPT file will be overwritten by the second and you’ll get NS_ERROR_XPC_BAD_IID errors when you try to access its IDL interfaces from your code. The files under EXPORTS are copied directly to the /mozilla/$(MOZ_OBJDIR)/dist/include/ directory and are thus accessible from other modules (the value of MOZ_OBJDIR is defined in /mozilla/.mozconfig). XPIDLSRCS are run through the IDL processor, and the generated C++ headers are copied into the same include directory. In addition, an XPT (type library) file is generated and placed in the components/ subdirectory of your extension.

- -

Ficheiros Fonte

- -

Now it’s time to create the makefile and source files in the src/ subdirectory. If you're implementing interfaces that you've described using IDL, the easiest way to do this is to leave the src/ directory empty and run make on the public/ directory only; this will be explained shortly.

- -

Then open the generated header file for your interface from /mozilla/$(MOZ_OBJDIR)/dist/include/. It contains stubs for the component .H and .CPP files that you can copy and paste into your implementation files. All you have to do is fill in the implementation stubs in the C++ file and you’re good to go.

- -

Here’s an example of the makefile you need to place into your src directory:

- -
DEPTH		= ../../..
-topsrcdir	= @top_srcdir@
-srcdir		= @srcdir@
-VPATH		= @srcdir@
-
-include $(DEPTH)/config/autoconf.mk
-
-IS_COMPONENT = 1
-MODULE = myextension
-LIBRARY_NAME =  myExtension
-USE_STATIC_LIBS = 1
-
-XPI_NAME = myextension
-
-CPPSRCS	= \
-  myFirstComponent.cpp \
-  mySecondComponent.cpp \
-  myExtension.cpp \
-  $(NULL)
-
-include $(topsrcdir)/config/rules.mk
-
-EXTRA_DSO_LDOPTS += \
-  $(MOZ_COMPONENT_LIBS) \
-  $(NSPR_LIBS) \
-  $(NULL)
-
- -

In this example, the first two files contain the implementation of the extension’s two components. The final file, myExtension.cpp, contains the code necessary to register these components, as described in the next section.

- -

Registar os Seus Componentes

- -

Este artigo explica como registar os componentes XPCOM no Gecko 2.0 e superior.

- -

Criação de Extensão

- -

As mentioned above, you’ll probably want to build your extension immediately after creating your IDL files in order to generate the C++ stubs for your component implementations. I’m assuming that you’ve already built Firefox successfully. If not, return immediately to the beginning of this article and don’t come back til you have a functioning firefox.exe. Do not pass go. Do not collect $200.

- -

Still here? Okay, now we have to modify your .mozconfig (in the /mozilla/ root directory) so that your extension is built along with Mozilla. Add the following line at the end of the file:

- -
ac_add_options --enable-extensions=default,myextension
-
- -

Now launch make from the Mozilla root:

- -
make -f client.mk build
-
- -

Even if you have an up-to-date Firefox build, you’ll have to wait a while for make to recurse over the entire Mozilla source tree looking for new stuff (on my machine, which is pretty fast, this takes a good 10-15 minutes). Eventually it will reach your extension and generate a bunch of stuff under /mozilla/$(MOZ_OBJDIR)/:

- - - -

A lot of this stuff won’t get created on this first pass since make will gag when it doesn’t find the source files for your components. Don’t worry about this; all you need are the generated header files that contain the C++ implementation stubs. Go back and flesh out the C++ implementation of your components so that the build can complete next time. Remember that you should never, ever modify any of these generated files. Always modify the files used to generate them and rerun make. If you’re changing the generated files directly, you’re probably doing something wrong.

- -

The process of walking the entire Mozilla tree takes a long time. If you already have a Mozilla build, you can avoid this by creating a makefile for your extension directly. Go to the root of your $(MOZ_OBJDIR) and (from a bash-compatible shell) enter:

- -
../build/autoconf/make-makefile extensions/myextension
-
- -

If your $(MOZ_OBJDIR) is located outside your $(TOPSRCDIR), you'll need to do:

- -
$(TOPSRCDIR)/build/autoconf/make-makefile -t $(TOPSRCDIR) extensions/myextension
-
- -

in order for the script to know where your source is (it'll use the extension path you gave it relative to the current dir to figure out where you want your makefiles to go).

- -

This will generate the proper makefile for your extension. Whether you build the whole Mozilla tree or take this shortcut, you can build from now on by going to /mozilla/$(MOZ_OBJDIR)/extensions/myextension/ and typing "make" on the command line. It should build your component without bothering with the rest of Mozilla. If everything works out, you’ll see your XPI file in the XPI staging area. You’ll also see the "exploded" version of the XPI (i.e. the unzipped directory structure) underneath /mozilla/$(MOZ_OBJDIR)/dist/bin/extensions. (If something goes wrong, figure out what, fix it and then come back here and add it to this article.)

- -

To make sure that the build really finished, launch Firefox and check that your extension is listed when you select Tools/Extensions. If you are using Firefox as your regular browser (and if you’re not, why not!?), you might be annoyed by the fact that you have to close regular Firefox before running your custom-built version. If so, try setting the MOZ_NO_REMOTE environment variable to "1" before running the development version of Firefox. You’ll also need to use a different profile for your development version:

- -
firefox -P development
-
- -

Where development is replaced with the name of the extra profile you’ve created. This will let you run both versions of Firefox simultaneously, saving you oodles of time over the course of the build/test cycle.

- -

Nenhum Local Como o Chrome

- -

Yippee-ki-yay! Now you have an extension that does, well, absolutely nothing. It’s time to do something with those groovy components that you’ve implemented and registered. The simplest way to do this is to write some JavaScript and XUL code. At this point, it would be very helpful to have a bit of experience writing "regular" extensions (i.e. without using custom C++ components). If you’ve never done this, I strongly recommend that you think of a cool idea for something simple that you’ve always wanted to tweak in Firefox and write it. Just displaying a new menu item that opens a "Hello, World!" dialog box would be already be a great exercise to get warmed up with.

- -

Assuming you know how to write XUL/JavaScript extensions, you’re aware that the most important stuff goes in the chrome/ directory of your extension. Well, the fact that you’re also using C++ components doesn’t change that one whit. So now you need to create the normal content/, locale/ and skin/ directories in which to place your chrome files. Personally I like placing these directly under the root directory of my module, but I don’t suppose it makes any difference if you prefer putting them under a chrome/ subdirectory or whatever. Let freedom reign!

- -

Once you’ve written the necessary chrome files (for instance, an overlay that adds a menu item to instantiate and use one of your components), you need to package them up as part of your extension. This is accomplished through the use of a JAR Manifest. For our simple extension example, this file might look something like this:

- -
myextension.jar:
-%  content myextension %content/
-%  locale myextension en-US %locale/en-US/
-%  skin myextension classic/1.0 %skin/classic/
-%  overlay chrome://browser/content/browser.xul chrome://myextension/content/MyExtensionOverlay.xul
-	content/MyExtensionOverlay.js		(content/MyExtensionOverlay.js)
-	content/MyExtensionOverlay.xul		(content/MyExtensionOverlay.xul)
-	locale/en-US/MyExtension.dtd		(locale/en-US/MyExtension.dtd)
-	locale/en-US/MyExtension.properties	(locale/en-US/MyExtension.properties)
-	skin/classic/MyExtension.css		(skin/classic/MyExtension.css)
-
- -

Place this code in a file called jar.mn in the root directory of your extension, making sure that the paths in parentheses point to actual files (when interpreted relative to the root directory). You also have to make one small change to the makefile in the same directory, adding the following line:

- -
USE_EXTENSION_MANIFEST = 1
-
- -

This tells make to create a single manifest file called chrome.manifest instead of creating separate manifests with goofy names for each package.

- -

Now launch make again, and you should see a chrome subdirectory appear in your extension (/mozilla/$(MOZ_OBJDIR)/dist/bin/extensions/myextension@mycompany.com/). Note that the chrome directory contains a JAR (i.e. ZIP) file with all the chrome files listed in jar.mn as well as a complete directory structure mirroring that of the JAR file. The directory structure, however, is empty. Why? I don’t know. Don’t worry about this, the files in the JAR are the ones that are actually used.

- -

Mantedo-a Complexa

- -

If you’re developing a really complex extension with lots of XPCOM components, you’ll probably want to divide your code up into smaller modules.

- -
Kinda, Sorta Complex Extensions
- -

For a moderately complex extension, it’s probably enough just to subdivide the code into a single level of modules. Let’s assume that you have a base/ module that defines a bunch of basic XPCOM components and an advanced/ module that defines some chrome as well as other components that use the basic components. Your complete directory structure will look something like this:

- - - -

Other than that, nothing really changes. The makefiles in the base/ and advanced/ directories should look more or less like your original root makefile, remembering to change the DEPTH variable to account for the fact that they’ve moved a level further away from the Mozilla root. You also need to remove the DIST_FILES variable since that’s going to be in the top-level makefile. Every makefile that generates anything should define the XPI_NAME variable to make sure generated files go into your extension and not into the global components/ directory. In fact, just define this in every makefile to be safe. You can use the same MODULE in both base/ and advanced/ so that all the generated include files go into the same directory, but make sure that you don’t use the same XPIDL_MODULE in the two public/ directories or one of the component type libraries (i.e. XPT files) will overwrite the other one and all hell will break loose.

- -

Each module must also have a different value for the LIBRARY_NAME variable. This is the name of the generated dynamic library, so if we call the libraries "myBase" and "myAdvanced", we’ll end up with myBase.dll and myAdvanced.dll (on Windows, at least). And each of these modules is going to have a separate C++ file for registering components. So there will be two files that look like myExtension.cpp in the original example, say Base.cpp and Advanced.cpp. Finally, each module will obviously have its own jar.mn, though they can reference the same JAR filename and package name if you want all the chrome files to be organized in a single JAR file and package. The only file that really stays put is install.rdf, which still exists once and only once in the extension root directory.

- -

As for the top-level makefile, it will now look like this:

- -
DEPTH		= ../..
-topsrcdir	= @top_srcdir@
-srcdir		= @srcdir@
-VPATH		= @srcdir@
-
-include $(DEPTH)/config/autoconf.mk
-
-MODULE = myextension
-
-DIRS		= base advanced
-
-XPI_NAME               = myextension
-INSTALL_EXTENSION_ID   = myextension@mycompany.com
-XPI_PKGNAME		= myextension
-
-DIST_FILES = install.rdf
-
-include $(topsrcdir)/config/rules.mk
-
- -
Extensões Complexas Sérias
- -

At some point, even a single module may grow to the point where you want to divide it further into submodules. The difference between having separate modules and having a single module with separate submodules is that the submodules all share the same file for registering components (the famous myExtension.cpp file), and when compiled they create a single dynamic library. The decision to split a module into submodules is all about code organization; it doesn’t really affect the final product at all.

- -

To split a module into submodules, first create a subdirectory for each submodule. Then create an additional directory called build/. Each submodule will be configured to create a static library, and the build/ directory will pull these libraries together to create a single dynamic component library. Confused? Here’s an example, showing just the advanced/ subbranch of the myextension/ directory:

- - - -

As you can see, we’ve split advanced/ into two submodules: intricate/ and multifarious/, and we’ve added an additional build/ subdirectory. We’ve left the chrome directories directly under advanced/, since they aren’t tied to any specific submodule. This means that jar.mn will stay in the same place.

- -

The intricate/ and multifarious/ makefiles will look a lot like the original advanced/ makefile, but we’ll need to tweak them a bit. As always, we have to adjust the DEPTH variable since the makefiles are deeper in the directory structure. And we should change the LIBRARY_NAME to indicate that we’re generating a static library for each submodule. By convention the "_s" suffix is used for this purpose. So let’s call them "myIntricate_s" and "myMultifarious_s". Finally, we define the variable FORCE_STATIC_LIB, resulting in a makefile that starts something like this:

- -
DEPTH		= ../../../../..
-topsrcdir	= @top_srcdir@
-srcdir		= @srcdir@
-VPATH		= @srcdir@
-
-include $(DEPTH)/config/autoconf.mk
-
-MODULE = myextension
-LIBRARY_NAME = myIntricate_s
-FORCE_STATIC_LIB = 1
-USE_STATIC_LIBS = 1
-
-XPI_NAME = myextension
-
-...more stuff here...
-
- -

The build makefile pulls together the static libraries generated by the submodules and creates a single (dynamic) component library:

- -
DEPTH		= ../../../..
-topsrcdir	= @top_srcdir@
-srcdir		= @srcdir@
-VPATH		= @srcdir@
-
-include $(DEPTH)/config/autoconf.mk
-
-IS_COMPONENT = 1
-MODULE = myextension
-LIBRARY_NAME = myAdvanced
-USE_STATIC_LIBS = 1
-
-XPI_NAME = myextension
-
-DEFINES += XPCOM_GLUE
-
-SHARED_LIBRARY_LIBS = \
-		$(DIST)/lib/$(LIB_PREFIX)myIntricate_s.$(LIB_SUFFIX) \
-		$(DIST)/lib/$(LIB_PREFIX)myMultifarious_s.$(LIB_SUFFIX) \
-                $(DIST)/lib/$(LIB_PREFIX)xpcomglue_s.$(LIB_SUFFIX) \
-                $(DIST)/lib/$(LIB_PREFIX)xul.$(LIB_SUFFIX) \
-                $(DIST)/lib/$(LIB_PREFIX)nss3.$(LIB_SUFFIX) \
-		$(NULL)
-
-CPPSRCS		= \
-		Advanced.cpp \
-		$(NULL)
-
-include $(topsrcdir)/config/rules.mk
-
-LOCAL_INCLUDES += \
-        -I$(srcdir)/../intricate/src \
-        -I$(srcdir)/../multifarious/src \
-        $(NULL)
-
- -

The makefile in the advanced/ directory should list the intricate/, multifarious/ and build/ directories in its DIRS variable. Make sure that build/ comes last since it can’t create the component library until the other makefiles have completed.

- -

Outros Tópicos

- -

Adicionar Ficheiros de Dados às Suas Extensões

- -

In some cases, you may wish to include additional files in your extension that don’t belong in the chrome/ subdirectory. Examples might be database files or XML schemas. This can be achieved by adding a custom step to your makefile that copies the files from the source tree into the extension’s target directory.

- -
Copiar Ficheiros de Dados para a Diretoria de Destino
- -

Let’s say that you have some data files containing statistical information that you want to include in your extension and make available to your components. You’ve placed these files, which have the extension .TXT, into a stats/ subdirectory under your extension directory in the source tree. The following makefile rule can be used to copy these files into the final target directory of the extension:

- -
export::
-	if test ! -d $(FINAL_TARGET)/stats; then \
-		$(NSINSTALL) -D $(FINAL_TARGET)/stats; \
-	fi
-	$(INSTALL) $(srcdir)/*.txt $(FINAL_TARGET)/stats
-
- -
Aceder aos Ficheiros de Dados a partir dos Componentes
- -

The trick to accessing your data files is to figure out where the home directory of your extension is. Rumor has it that at some future date, this will possible through the nsIExtensionManager interface or something similar. In the meantime, there is a simple and reliable hack that can be used to achieve this. In the implementation of any JavaScript XPCOM component, there is a special __LOCATION__ (two leading and two trailing underscores) symbol that points to the component’s implementation file. So you can write a simple component which deduces the root directory of your extensions by extrapolating from its location.

- -

This article explains how to create an XPCOM component in JavaScript. You’ll need an IDL file for an interface that looks something like this:

- -
interface myILocation : nsISupports
-{
-    readonly attribute nsIFile locationFile;
-};
-
- -

Place the IDL file in the public/ directory of your project or subproject. In the src/ directory, place the JavaScript file that implements the component. The component implementation will include the methods for retrieving the path or file for the extension’s home directory:

- -
myLocation.prototype =
-{
-  QueryInterface: function(iid)
-  {
-    if (iid.equals(nsISupports))
-      return this;
-    if (iid.equals(myILocation))
-      return this;
-
-    Components.returnCode = Components.results.NS_ERROR_NO_INTERFACE;
-    return null;
-  },
-
-  get locationFile()
-  {
-     return __LOCATION__.parent.parent;
-  }
-}
-
- -

This assumes that the component resides in a subdirectory of the extension directory (by convention, this directory is called components/). The parent property of __LOCATION__ returns the components/, and the parent of this is the extension directory.

- -

The last step is to modify the makefile of the source directory where you placed your JavaScript file so that it is copied into the appropriate location in the extension:

- -
export::
-	$(INSTALL) $(srcdir)/*.js $(FINAL_TARGET)/components
-
- -

Now you can instantiate an instance of this component and use the locationFile property to get an nsIFile interface that points to your extension’s home directory.

- -

Using Third-Party Libraries

- -

For more sophisticated extensions, you may want to integrate third-party libraries that provide specialized functionality for database connectivity, image processing, networking and the like. If you want your extension to run on all Firefox platforms, you will need to have the source code for the library in question, so I assume that this is available.

- -

The most convenient approach from the perspective of the development cycle is to create a Mozilla-style makefile for the library. This works well for libraries that have a straightforward make process without extensive configuration. A good example of this is the SQLite library included in the Mozilla build tree at db/sqlite. By adapting the makefile in this way, the library is created as part of the standard Mozilla build process, which eliminates additional build steps. The downside is that you will need to update the modified makefile any time a new version of the library is released.

- -

For libraries that have complex configuration processes, use a non-standard compiler or have other special characteristics, it may be unfeasible to create a Mozilla-compliant makefile. In this case, I would recommend placing the entire library distribution inside the project or subproject that uses it. So if library acmelib is used inside the multifarious/ subproject in the above example, it would be placed as a subdirectory underneath that subproject (at the same level as public/ and src/).

- -

Of course, this means that you will have to build acmelib manually on all platforms before launching the Mozilla build. But at least you can then refer to include files and import libraries from your component using relative paths.

- -

Building for Multiple Platforms

- -

TODO

- -
-

Original Document Information

- - -
- -

 

diff --git a/files/pt-pt/mozilla/add-ons/distribuicao/index.html b/files/pt-pt/mozilla/add-ons/distribuicao/index.html deleted file mode 100644 index eede6b7581..0000000000 --- a/files/pt-pt/mozilla/add-ons/distribuicao/index.html +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Assinar e distribuir os seus extras -slug: Mozilla/Add-ons/Distribuicao -tags: - - Extensões - - Extensões da Web - - Extras - - assinatura - - distribuição - - publicação - - revisões -translation_of: Mozilla/Add-ons/Distribution ---- -
{{AddonSidebar}}
- -

Os extras precisam de ser assinados antes de serem instalados nas versões beta e de lançamento do Firefox. Este processo de assinatura ocorre via addons.mozilla.org (AMO), independentemente de optar por distribuir o seu extra via AMO ou por si mesmo.

- -

Nós aqui analisamos os requisitos de assinatura e as revisões relacionadas, antes de discutir como escolher entre o distribuir no AMO ou distribuir um extra por si mesmo. Nós também analisamos os canais disponíveis no AMO e respondemos a questões sobre propriedade e disputas de código.

- -

Assinar os seus extras

- -

Starting with Firefox 43, add-on extensions and multi-item add-ons that include extensions need to be signed by Mozilla before they can install in release and beta versions of Firefox. Themes, and other types of add-ons such as spelling dictionaries, don't need to be signed.

- -

Unsigned extensions can be installed in Developer Edition, Nightly, and ESR versions of Firefox, after toggling the xpinstall.signatures.required preference in about:config.

- -

Mozilla signs add-ons through the AMO website and provides three methods for submitting your add-on for signing:

- - - -

All the signing options are subject to the Firefox Add-on Distribution Agreement.

- -

Using the signing API or web-ext returns you signed add-ons, with no distribution listing created on AMO. If you take the option to upload your add-on through the AMO Developer Hub, you're given a choice between listing on AMO or self-distribution. If you choose self-distribution, at the end of the process you download signed copies of your add-on.

- -

Regardless of the method used all add-ons must pass an automated validation before they are signed. They may also be subject to a manual code review. The review criteria applied to add-ons are found in the Add-on Policies.

- -

Distributir o seu extra

- -

You aren't required to list or distribute your add-on through AMO. You'll, therefore, need to decide if you want to distribute and list your add-on through AMO or distribute it yourself. Here are some things you should consider:

- - - -

For more information on how to submit an add-on for distribution on AMO or self-distribution, see Submitting an add-on.

- -

Mais informação sobre AMO

- -

Propriedade

- -

Os extras no AMO podem ter vários utilizadores com permissão para atualizar e gerir a listagem. Os autores de um extra podem transferir a propriedade e adicionar programadores à listagem de um extra por meio do Hub do Programdor. Não é necessária nenhuma interação com os representantes da Mozilla para uma transferência de propriedade.

- -

 

- -

Para transferir propriedade

- - - -

 

- -

Disputas de códogo

- -

Many add-ons allow their source code to be viewed. This does not mean that the source code is open source or available for use in another add-on. The original author of an add-on retains copyright of their work unless otherwise noted in the add-on's license.

- -

If we're notified of a copyright or license infringement, we will take steps to address the situation per the DMCA, which may include taking down the add-on listing. Details about this process and how to report trademark or licensing issues can be found here.

- -

If you are unsure of the current copyright status of an add-on's source code, you must contact the author and get explicit permission before using the source code.

diff --git a/files/pt-pt/mozilla/add-ons/linhas_diretrizes_para_extras/index.html b/files/pt-pt/mozilla/add-ons/linhas_diretrizes_para_extras/index.html deleted file mode 100644 index 4293fe9c74..0000000000 --- a/files/pt-pt/mozilla/add-ons/linhas_diretrizes_para_extras/index.html +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Linhas Diretrizes para Extras -slug: Mozilla/Add-ons/Linhas_diretrizes_para_extras -translation_of: 'https://extensionworkshop.com/documentation/publish/add-on-policies/' ---- -
-

Este documento já não é válido. Por favor, consulte o documento de Políticas de Revisão para o conjunto atual das políticas de extras.

-
diff --git a/files/pt-pt/mozilla/add-ons/sdk/index.html b/files/pt-pt/mozilla/add-ons/sdk/index.html deleted file mode 100644 index 1c160220ae..0000000000 --- a/files/pt-pt/mozilla/add-ons/sdk/index.html +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: Add-on SDK -slug: Mozilla/Add-ons/SDK -tags: - - Add-on SDK - - Jetpack -translation_of: Archive/Add-ons/Add-on_SDK ---- -
-

Support for extensions using XUL/XPCOM or the Add-on SDK was removed in Firefox 57, released November 2017. As there is no supported version of Firefox enabling these technologies, this page will be removed by December 2020.

- -

Add-ons using the techniques described in this document are considered a legacy technology in Firefox. Don't use these techniques to develop new add-ons. Use WebExtensions instead. If you maintain an add-on which uses the techniques described here, consider migrating it to use WebExtensions.

- -

Starting from Firefox 53, no new legacy add-ons will be accepted on addons.mozilla.org (AMO) for desktop Firefox and Firefox for Android.

- -

Starting from Firefox 57, only extensions developed using WebExtensions APIs will be supported on Desktop Firefox and Firefox for Android.

- -

Even before Firefox 57, changes coming up in the Firefox platform will break many legacy extensions. These changes include multiprocess Firefox (e10s), sandboxing, and multiple content processes. Legacy extensions that are affected by these changes should migrate to use WebExtensions APIs if they can. See the "Compatibility Milestones" document for more information.

- -

A wiki page containing resources, migration paths, office hours, and more, is available to help developers transition to the new technologies.

-
-

Pode criar extras do Firefox utilizando Add-on SDK. Pode utilizar várias tecnologias da Web padrão: CSS, HTML e JavaScript, para criar os extras. O SDK inclui as APIs de JavaScript APIs, que pode utilziar para criar extras e ferramentas para a criação, execução, testes, e empacotamento dos extras.

- -
-

Tutoriais

- -
-
-
-
Getting started
-
How to install the SDK and use the jpm tool to develop, test, and package add-ons.
-
Interact with the browser
-
Open web pages, listen for pages loading and list open pages.
-
Development techniques
-
Learn about common development techniques, such as unit testing, logging, creating reusable modules, localization, and mobile development.
-
-
- -
-
-
Create user interface components
-
Create user interface components such as toolbar buttons, context menus, menu items, and dialogs.
-
Modify web pages
-
Modify pages matching a URL pattern or dynamically modify a particular tab.
-
Putting it together
-
Walkthrough of the Annotator example add-on.
-
-
-
- -
-

Guias

- -
-
-
-
Contributor's guide
-
Learn how to start contributing to the SDK and about the most important idioms used in the SDK code such as modules, classes and inheritance, private properties, and content processes.
-
SDK infrastructure
-
Aspects of the SDK's underlying technology: modules, the Program ID and the rules defining Firefox compatibility.
-
Content scripts
-
A detailed guide to working with content scripts.
-
-
- -
-
-
SDK idioms
-
The SDK's event framework and the distinction between add-on scripts and content scripts.
-
XUL migration
-
A guide to porting XUL add-ons to the SDK. This guide includes a comparison of the two toolsets and a working example of porting a XUL add-on.
-
Multiprocess Firefox and the SDK
-
How to check whether your add-on is compatible with multiprocess Firefox or not and fix it accordingly.
-
-
-
- -
-

Referência

- -
-
-
-
High-Level APIs
-
Reference documentation for the high-level SDK APIs.
-
Tools reference
-
Reference documentation for the jpm tool used to develop, test and package add-ons, the console global used for logging, and the package.json file.
-
-
- -
-
-
Low-Level APIs
-
Reference documentation for the low-level SDK APIs.
-
-
-
diff --git a/files/pt-pt/mozilla/add-ons/themes/conceitos_tema/index.html b/files/pt-pt/mozilla/add-ons/themes/conceitos_tema/index.html deleted file mode 100644 index bb59c4386f..0000000000 --- a/files/pt-pt/mozilla/add-ons/themes/conceitos_tema/index.html +++ /dev/null @@ -1,230 +0,0 @@ ---- -title: Conceitos de Tema -slug: Mozilla/Add-ons/Themes/Conceitos_tema -tags: - - Tema - - extra -translation_of: Mozilla/Add-ons/Themes/Theme_concepts ---- -
{{AddonSidebar()}}
- -

Os temas desenvolvidos utilizando a WebExtensions API no Firefox permitem-lhe alterar a aparência do navegador ao adicionar imagens na área do cabeçalho do navegador Firefox; esta é a área por trás da barra de menus, barras de ferramentas, barra de endereço, barra de pesquisa e seuparador de faixa.

- -

Estas opções de temas podem ser implementadas como temas estáticos (embora as próprias imagens do tema possam ser animadas) ou como temas dinâmicos criados numa extensão do navegador.

- -
-

If you have a lightweight theme it will be converted to this new theme format automatically before lightweight themes are deprecated. You do not need to port your theme. However, please feel free to update your themes to use any of the new features described here.

-
- -

Temas estásticos

- -

Static themes are specified using the same resources as a browser extension: a manifest.json file to define the theme components with those components stored in the same folder as the manifest.json file or a sub folder. These resources are then packed in a zip for publication on addons.mozilla.org (AMO).

- -
-

A theme and browser extension functionality cannot be defined in one package, such as including a theme to complement an extension. You can, however, programmatically include a theme in an extension using the Theme API. See Dynamic themes.

-
- -

Definir um tema

- -

To create a theme (in this example a simple, single image theme):

- - - -

Static theme approaches

- -

There are two approaches you can take to theming the header area of Firefox: using a single image or using multiple images. You could combine the two, but it’s easier to treat them separately.

- -

Single image themes

- -

This is the basic or minimal theming option, where you define:

- - - -

The area your header image needs to fill is a maximum of 200 pixels high. The maximum image width is determined by the resolution of the monitor Firefox is displaying on and how much of the monitor Firefox is using. Practically, this means you would need to allow for a width of up to 5120 pixels wide (for the next generation of 5k monitors). However, rather than creating a very wide image, a better approach is to use a narrower image with a transparent left edge so that it fades to the background color. For example, we could use this image
- An image of a weta (the common name for a group of about 70 insect species in the families Anostostomatidae and Rhaphidophoridae, endemic to New Zealand) with the left edge fading to total transparency.
- combined with a complementary background color, to create this effect in the header
- A single image theme using the weta.png image

- -

See details about this theme in the themes example weta_fade.

- -

Obviously, you can still provide a single wide image if you prefer.

- -

Multiple image themes

- -

As an alternative to creating a single image theme, you have the option to use multiple images. These images can be individually anchored to locations within the header, with the option to apply tiling to each image.

- -

Depending on the effect you want to create you may need to suppress the mandatory "headerURL": image with an empty or transparent image. You would use an empty or transparent image if, for example, you wanted to tile a centrally justified image, such as
- An image of a weta (the common name for a group of about 70 insect species in the families Anostostomatidae and Rhaphidophoridae, endemic to New Zealand) with the left and right edges fading to total transparency.
- to create this effect
- A single image theme using the additional images option to align an image to the center of the heading and tile it.
- Here you specify the weta image like this:

- -
"images": {
-  "headerURL": "empty.png",
-  "additional_backgrounds": [ "weta_for_tiling.png"]
-},
- -

and the images tiling with:

- -
"properties": {
-  "additional_backgrounds_alignment": [ "top" ],
-  "additional_backgrounds_tiling": [ "repeat"  ]
-},
- -

Full details of how to setup this theme can be found in the themes example weta_tiled. Full detais of the alignment and tiling options can be found in the "theme" key description.

- -

Alternatively, you can use multiple images, say combining the original weta image with this one anchored to the left of the header
- An image of a weta (the common name for a group of about 70 insect species in the families Anostostomatidae and Rhaphidophoridae, endemic to New Zealand) with the right edge fading to total transparency.
- to create this effect
- A theme using the additional images option to place two mirrored image to the left and right of the browser header.

- -

Where the images are specified with:

- -
"images": {
-  "headerURL": "empty.png",
-  "additional_backgrounds": [ "weta.png", "weta-left.png"]
-},
- -

and their alignment by:

- -
"properties": {
-  "additional_backgrounds_alignment": [ "right top" , "left top" ]
-},
- -

Full details of how to setup this theme can be found in the themes example weta_mirror. Full detais of the alignment options can be found in the "theme" key description.

- -

Static animated themes

- -

It is possible to create an animated theme using an APNG format image, as in the themes example animated. However, remember that rapid animations, such as the one in the example might be too distracting for a practical theme.

- -

You can also animate themes programmatically, which we discuss in Dynamic themes.

- -

Temas dinâmicos

- -

As an alternative to defining a static theme, you can use the {{WebExtAPIRef("theme")}} API to control the theme used in Firefox from within a browser extension. There are a couple of use cases for this option:

- - - -

And, obviously, you can combine the two and bundle a programmatically controlled theme with your extension.

- -

Using the {{WebExtAPIRef("theme")}} API is straightforward. First, request "theme" permission in the extension's manifest.json file. Next, you build a JSON object containing the same information you would use in a static theme’s manifest.json, Finally, pass the JSON object in a {{WebExtAPIRef("theme.update()")}} call.

- -

For example, the following code, from the dynamic theme example defines the content for the day and night elements of the dynamic theme:

- -
const themes = {
-  'day': {
-    images: {
-     headerURL: 'sun.jpg',
-    },
-    colors: {
-     accentcolor: '#CF723F',
-     textcolor: '#111',
-    }
-  },
-  'night': {
-    images: {
-     headerURL: 'moon.jpg',
-    },
-    colors: {
-     accentcolor: '#000',
-     textcolor: '#fff',
-    }
-  }
-};
- -

The theme.Theme object is then passed to {{WebExtAPIRef("theme.update()")}} to change the header theme, as in this code snippet from the same example:

- -
function setTheme(theme) {
-  if (currentTheme === theme) {
-    // No point in changing the theme if it has already been set.
-    return;
-  }
-  currentTheme = theme;
-  browser.theme.update(themes[theme]);
-}
- -

Learn more about dynamic themes and see an additional example in the following video:

- -

{{EmbedYouTube("ycckyrUN0AY")}}

- -

 

- -

If you have not built a browser extension before, check out Your first extension for a step-by-step guide.

- -

Compatibilidade entre navegadores

- -

There is currently limited compatibility between themes in the major browsers. Opera takes an entirely different approach, and Microsoft Edge themes are not yet open to developers.

- -

There is some compatibility between Firefox static themes and Chrome themes, providing the ability to port a single header image theme from Firefox to Chrome. This would be done by amending the manifest.json keys as follows:

- - - -

Noting that "frame": and "tab_text": support RGB color definition only.

- -

So, in the single image theme example (weta_fade) could be supported in Chrome using the following manifest.json file:

- -
{
-  "manifest_version": 2,
-  "version": "1.0",
-  "name": "<your_theme_name>",
-  "theme": {
-    "images": {
-      "theme_frame": "weta.png"
-    },
-    "colors": {
-      "frame": [ 173 , 176 , 159 ],
-      "tab_text": [ 0 , 0 , 0 ]
-    }
-  }
-}
- -

However, there will be a couple of differences:

- - - -

The basic theme example using the Chrome compatible manifest.json keys, showing the differences in how those keys are implemented.

- -

For more information, see the notes on Chrome compatibility.

diff --git a/files/pt-pt/mozilla/add-ons/themes/index.html b/files/pt-pt/mozilla/add-ons/themes/index.html deleted file mode 100644 index 26dfb24673..0000000000 --- a/files/pt-pt/mozilla/add-ons/themes/index.html +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Temas -slug: Mozilla/Add-ons/Themes -tags: - - Apresentação e Disposição - - Extras - - Temas -translation_of: Mozilla/Add-ons/Themes ---- -

{{AddonSidebar}}

- -

Temas permite-lhe alterar a apresentação e disposição da interface do utilizador e personalizar a seu gosto. Saiba como criar e partilhar os temas!

- -
-
-

Temas de Navegador

- -
-
Browser theme concepts
-
Get an introduction to creating themes for the latest versions of Firefox
-
- -

Temas Simples

- -
-
Lightweight themes
-
Building lightweight themes for Firefox
-
Lightweight themes FAQ
-
Get answers to commonly asked questions
-
-
- -
-

Ferramentas e Recursos

- - -
-
- -

 

- -

 

diff --git a/files/pt-pt/mozilla/add-ons/themes/obsolete/creating_a_skin_for_firefox/index.html b/files/pt-pt/mozilla/add-ons/themes/obsolete/creating_a_skin_for_firefox/index.html deleted file mode 100644 index 9d187b7315..0000000000 --- a/files/pt-pt/mozilla/add-ons/themes/obsolete/creating_a_skin_for_firefox/index.html +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Creating a Skin for Firefox -slug: Mozilla/Add-ons/Themes/Obsolete/Creating_a_Skin_for_Firefox -tags: - - Add-ons - - NeedsTranslation - - Themes - - TopicStub -translation_of: Archive/Themes/Creating_a_Skin_for_Firefox ---- -

Introduction

- -

In order to create a skin for Firefox, there are three things you need to know: how to edit images, how to extract zip files, and how to modify CSS. Firefox uses standard GIF, PNG, and JPEG images for the buttons and CSS to style everything else in the interface.

- -

What is a skin?

- -

A skin does not totally change the interface; instead, it just defines how the interface looks. You can't change what happens when the user right clicks on an image, but you can change the look of the right click menu (Make it blue with pink polka dots, for example). If you want to change the functionality of Firefox, you'll have to look into modifying the chrome, which is beyond the scope of this document.

- -

Contents

- - - -
-

Informações Sobre o Documento Original

- -
diff --git a/files/pt-pt/mozilla/add-ons/themes/obsolete/index.html b/files/pt-pt/mozilla/add-ons/themes/obsolete/index.html deleted file mode 100644 index d420b6ebf0..0000000000 --- a/files/pt-pt/mozilla/add-ons/themes/obsolete/index.html +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Obsolete -slug: Mozilla/Add-ons/Themes/Obsolete -tags: - - NeedsTranslation - - TopicStub -translation_of: Mozilla/Add-ons/Themes/Obsolete ---- -

This page collects theme docs that we don't expect will ever be updated, but which we're keeping for the time being as potential source material for updated docs.

-

{{ ListSubPages ("/en-US/Add-ons/Themes/Obsolete", 5) }}

diff --git a/files/pt-pt/mozilla/add-ons/thunderbird/index.html b/files/pt-pt/mozilla/add-ons/thunderbird/index.html deleted file mode 100644 index b15b535a59..0000000000 --- a/files/pt-pt/mozilla/add-ons/thunderbird/index.html +++ /dev/null @@ -1,135 +0,0 @@ ---- -title: Thunderbird extensions -slug: Mozilla/Add-ons/Thunderbird -tags: - - Add-ons - - Extensions - - NeedsTranslation - - TopicStub - - thunderbird -translation_of: Mozilla/Thunderbird/Thunderbird_extensions ---- -
Building a Thunderbird extension
-Step-by-step explanation on how to build an extension for Thunderbird.
- -
-

{{AddonSidebar}}

-The following documentation provides help for creating extensions for Mozilla's Thunderbird email client. Although there are many similarities with Firefox extensions there are also some differences that may confound the starting developer.
- -

-Please help! You can add a how-to (a question or an answer or a code snippet), summarize and link to a relevant newsgroup discussion, or create a tutorial. Need help? Contact jenzed.
- - - - - - - - -
-

Documentation

- -

Getting started with Thunderbird

- -

A brave, young developer wants to develop an add-on for Thunderbird. Here's a few links to help them through this journey.

- -
    -
  • Start by reading the tutorial and learn how to build a Thunderbird extension (Outdated, still talks about overlays and the add-on builder is no longer available but the tutorial has not been updated.)
    • -
  • Read about the main windows so that you know what one means when they say « thread pane », « preview pane », and « folder pane ».
    • - -
  • Want to do some real stuff? See how to inspect a message (demo add-on included!)
    • -
  • Play with our other demo add-on that exercises some more advanced Thunderbird-specific features
    • -
  • Want to do even more stuff? Don't reinvent the wheel: steal functions from the thunderbird-stdlib project (doc here). Functions for dealing with messages (delete them, archive them, change their tags, etc.) are included.
    • -
  • Haven't found what you're looking for? Read the Thunderbird how-tos; they contain a lot of recipes for things extensions want to do.
    • -
  • Still haven't managed to do what you wanted? See the list of all Thunderbird communication channels so that you know where to ask when you get stuck :-).
    • -
  • Feeling really brave? Read the source using a fancy interface; you can often find tests that demonstrate how to do what you're trying to achieve.
    • -
- -

The Gloda database

- -

Thunderbird has a subsystem called Gloda. Gloda stands for « Global Database », and creates Thunderbird-wide relations between objects. Gloda provides concepts such as Conversations, Messages, Identities, Contacts. All these concepts are related together: a Conversation contains Messages which are linked to Identities (from field, to field) which are themselves part of a Contact: indeed, a contact has multiple identities.

- -

Typical use cases for Gloda: find all messages whose subject matches [search term], find all messages from [person], find all messages in the same thread as [a given message], find all messages involving [person], etc. etc.

- -

Gloda is extremely powerful and is used heavily by add-ons such as Thunderbird Conversations. Learn more about Gloda:

- - - - - -

Some of these links may be wildly out of date, but they still provide valuable information on the codebase.

- - - - - - - 		-

Community

- - - -

{{ DiscussionList("dev-extensions", "mozilla.dev.extensions") }}

- - - -

Tools

- - - -

... more tools ...

- -

View All...

- - - -
-
XUL, JavaScript, XPCOM, Themes, Developing Mozilla
-
-
- -

Categories

- -

{{ languages( { "ja": "ja/Extensions/Thunderbird" } ) }}

diff --git a/files/pt-pt/mozilla/calendar/calendar_versions/index.html b/files/pt-pt/mozilla/calendar/calendar_versions/index.html deleted file mode 100644 index 7e8c1a7958..0000000000 --- a/files/pt-pt/mozilla/calendar/calendar_versions/index.html +++ /dev/null @@ -1,1037 +0,0 @@ ---- -title: Versões de Calendário -slug: Mozilla/Calendar/Calendar_Versions -tags: - - Calendário - - Lightning - - Sunbird -translation_of: Mozilla/Calendar/Calendar_Versions ---- -

Esta página tem como objetivo fornecer um resumo de qual a versão do Lightning que é compatível com a versão do Thunderbird. Esta também mostra qual a versão da plataforma Mozilla que é utilizada na respetiva versão do Sunbird e do Lightning.

- -

O objetivo principal da 'Equipa do Calendário' é sincronizar o ciclo de lançamento do Lightning com o Thunderbird. Isto geralmente significa que nós iremos utilizar o código base mais recente do Thunderbird e da Mozilla (comm-central e mozilla-central) para o desenvolvimento ativo. Se o agendamento do Thunderbird ainda não estiver clara, nós retrocederemos as alterações para uma ramificação mais antiga.

- -

Nota: se estiver a ter problemas e o calendário está em falta, primeiro consulte  calendar update issues, porque depois do Thunderbird 52 Lightning está integrado (empacotado com o Thunderbird) e não deveria de ter que transferir a extensão. Mas se estiver a executar o Thunderbird - versão 45 ou anterior, utilize a hiperligação de transferência abaixo..

- -

Lightning

- -

Resumo de Desenvolvimento

- -
-

As compilações do Lightning listadas abaixo devem ser consideradas instáveis ​​e estão disponíveis apenas para fins de desenvolvimento e testes.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Lightning
- Versão		Thunderbird
- Versão		SeaMonkey
- Versão		 -

Plataforma Mozilla
- Versão

- 		Build NameChangelog
6.8a166.0a1
- "Daily"		2.63a1mozilla66"nightly"
- (comm-central)		changes in 6.8
6.7b165.0b1
- "Beta"		2.62b1mozilla65"beta"
- (comm-beta)		changes in 6.7
- -

Lançamentos Estáveis

- -

The Lightning releases listed below are considered stable and are recommend for daily usage. 

- -

If you are having trouble and calendar is missing, first see calendar update issues, because after Thunderbird 52 Lightning is built-in (bundled with Thunderbird) and you should not need to download the extension. 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Lightning
- Versão		Thunderbird
- Versão		SeaMonkey
- Versão		Plataforma Mozilla
- Versão		Data de LançamentoRegisto de Alterações
6.7b1 (Beta)65.0 (Beta)2.62mozilla65 changes in 6.7
6.6b4 (Beta)64.0 (Beta)2.61mozilla64December 2, 2018changes in 6.6
6.5b1 (Beta)63.0 (Beta)2.60mozilla63October 11, 2018changes in 6.5
6.4b1 (Beta)62.0 (Beta)2.59mozilla62---changes in 6.4
6.3b1 (Beta)61.0 (Beta)2.58mozilla61---changes in 6.3
6.2.3.360.3.32.57mozilla60December 5, 2018 
6.2.3.260.3.22.57mozilla60November 30, 2018 
6.2.3.160.3.12.57mozilla60November 15, 2018changes in 6.2.3 / changes in 6.2.3.1
6.2.2.160.2.12.57mozilla60October 2, 2018changes in 6.2.2.1
6.260.02.57mozilla60August 6, 2018changes in 6.2
6.1b2 (Beta)59.0 (Beta)2.56mozilla59---changes in 6.1
6.0b3 (Beta)58.0 (Beta)2.55mozilla58---changes in 6.0
5.9b2 (Beta)57.0 (Beta)2.54mozilla57---changes in 5.9
5.8b4 (Beta)56.0 (Beta)2.53mozilla56---changes in 5.8
5.7b2 (Beta)55.0 (Beta)2.52mozilla55---changes in 5.7
5.6b3 (Beta)54.0 (Beta)2.51mozilla54---changes in 5.6
5.5b2 (Beta)53.0 (Beta)2.50mozilla53October 10, 2017changes in 5.5
5.4.9.152.9.1---mozilla52July 10, 2018---
5.4.852.8.0---mozilla52May 18, 2018changes in 5.4.8
5.4.752.7.0---mozilla52March 23, 2018changes in 5.4.7
5.4.652.6.0---mozilla52January 25, 2018changes in 5.4.6
5.4.5.252.5.2---mozilla52December 22, 2017changes in 5.4.5
5.4.452.4.0---mozilla52October 6, 2017changes in 5.4.4
5.4.352.3.0---mozilla52August 16, 2017changes in 5.4.3
5.4.2.152.2.1----mozilla52June 23, 2017changes in 5.4.2 / changes in 5.4.2.1
5.4.1.152.1.1---mozilla52May 15, 2017changes in 5.4.1 / changes in 5.4.1.1
5.4.0.152.0.1---mozilla52April 14, 2017changes in 5.4.0.1
5.452.02.49mozilla52April 4, 2017changes in 5.4
5.3b2 (Beta)51.0 (Beta)2.48mozilla51March 19, 2017changes in 5.3
5.2b1 (Beta)50.0 (Beta)2.47mozilla50October 16, 2016changes in 5.2
5.1b1 (Beta)49.0 (Beta)2.46mozilla49October 16, 2016changes in 5.1
5.0b1 (Beta)48.0 (Beta)2.45mozilla48October 16, 2016changes in 5.0
4.9b2 (Beta)47.0 (Beta)2.44mozilla47July 1, 2016changes in 4.9
4.8b1 (Beta)46.0 (Beta)2.43mozilla46---changes in 4.8
4.7.845.8.02.42mozilla45March, 7 2017changes in 4.7.8
4.7.7.145.7.12.42mozilla45February 7, 2017changes in 4.7.7
4.7.645.6.02.42mozilla45December 28, 2016changes in 4.7.6
4.7.5.145.5.12.42mozilla45November 30, 2016changes in 4.7.5
4.7.445.4.02.42mozilla45October 3, 2016changes in 4.7.4
4.7.345.3.02.42mozilla45August 30, 2016changes in 4.7.3
4.7.245.2.02.42mozilla45June 30, 2016changes in 4.7.2
4.7.1.145.1.12.42mozilla45May 31, 2016changes in 4.7.1.1
4.745.02.42mozilla45April 25, 2016changes in 4.7
4.6b1 (Beta)44.0 (Beta)2.41mozilla44January 21, 2016changes in 4.6
4.5b1 (Beta)43.0 (Beta)2.40mozilla43January 8, 2016changes in 4.5
4.4b2 (Beta)42.0 (Beta)2.39mozilla42October 14, 2015changes in 4.4
4.3b2 (Beta)41.0 (Beta)2.38mozilla41September 16, 2015changes in 4.3
4.2b1 (Beta)40.0 (Beta)2.37mozilla40July 30, 2015changes in 4.2
4.1b1 (Beta)39.0 (Beta)2.36mozilla39---changes in 4.1
4.0.7.238.7.2---mozilla38April 4, 2016changes in 4.0.7 / changes in 4.0.7.1
4.0.638.6.0---mozilla38February 16, 2016changes in 4.0.6
4.0.5.238.5.12.35mozilla38January 21, 2016changes in 4.0.5
4.0.4.138.4.02.35mozilla38November 30, 2015changes in 4.0.4
4.0.3.138.3.02.35mozilla38October 8, 2015changes in 4.0.3
4.0.2.138.2.02.35mozilla38September 16, 2015changes in 4.0.2.1
4.0.238.2.02.35mozilla38August 14, 2015changes in 4.0.2
4.0.1.238.1.02.35mozilla38July 23, 2015changes in 4.0.1.2
4.0.138.1.02.35mozilla38July 8, 2015changes in 4.0.1
4.0.0.138.0.12.35mozilla38June 12, 2015changes in 4.0.0.1
3.9b1 (Beta)37.0 (Beta)2.34mozilla37March 14, 2015changes in 3.9
3.8b2 (Beta)36.0 (Beta)2.33mozilla36March 12, 2015changes in 3.8
3.7b1 (en-US only)---2.32mozilla35January 28, 2015changes in 3.7
3.6b3 (Beta)34.0 (Beta)2.31mozilla34December 17, 2014changes in 3.6
3.5b1 (Beta)33.0 (Beta)2.30mozilla33September 23, 2014changes in 3.5
3.4b1 (Beta)32.0 (Beta)2.29mozilla32August 18, 2014changes in 3.4
3.3.331.02.28mozilla31January 28, 2015changes in 3.3.3
3.3.231.02.28mozilla31December 27, 2014changes in 3.3.2
3.3.131.02.28mozilla31September 23, 2014changes in 3.3.1
3.331.02.28mozilla31July 21, 2014changes in 3.3
3.2b130.0 (Beta)2.27mozilla30May 9, 2014changes in 3.2
3.1b129.0 (Beta)2.26mozilla29April 24, 2014changes in 3.1
3.0b128.0 (Beta)2.25mozilla28March 6, 2014changes in 3.0
2.9b127.0 (Beta)2.24mozilla27December 19, 2013changes in 2.9
2.8b126.0 (Beta)2.23mozilla26November 15, 2013changes in 2.8
2.7b125.0 (Beta)2.22mozilla25October 17, 2013changes in 2.7
2.6.624.5.0---mozilla24.5June 19, 2014changes in 2.6.6
2.6.524.5.0---mozilla24.5May 13, 2014changes in 2.6.5
2.6.424.2.0---mozilla24.2December 11, 2013changes in 2.6.4
2.6.324.1.1---mozilla24.1.1November 19, 2013changes in 2.6.3
2.6.224.1.0---mozilla24.1October 29, 2013---
2.6.124.0.1---mozilla24.0.1October 13, 2013changes in 2.6.1
2.624.02.21mozilla24September 11, 2013changes in 2.6
2.5b2---2.20mozilla23July 8, 2013changes in 2.5
2.4b1---2.19mozilla22May 24, 2013changes in 2.4
2.3b2---2.18mozilla21May 8, 2013changes in 2.3
2.2b1---2.17mozilla20March 6, 2013changes in 2.2
2.1b1---2.16mozilla19February 12, 2013changes in 2.1
2.0b1---2.15mozilla18November 29, 2012changes in 2.0
1.9.117.02.14mozilla17March 6, 2013changes in 1.9.1
1.917.02.14mozilla17November 20, 2012changes in 1.9
1.816.02.13mozilla16October 09, 2012changes in 1.8
1.715.02.12mozilla15August 28, 2012changes in 1.7
1.614.02.11mozilla14July 17, 2012changes in 1.6
1.5.213.02.10mozilla13June 21, 2012---
1.5.113.02.10mozilla13June 14, 2012---
1.513.02.10mozilla13June 4, 2012changes in 1.5
1.412.02.9mozilla12April 23, 2012changes in 1.4
1.311.02.8mozilla11March 13, 2012changes in 1.3
1.2.310.02.7mozilla10March 9, 2012---
1.2.110.02.7mozilla10February 3, 2012---
1.210.02.7mozilla10January 23, 2012changes in 1.2
1.1.19.02.6mozilla9January 5, 2012changes in 1.1
1.08.02.5mozilla8November 7, 2011 
1.0b77.02.4mozilla7September 27, 2011 
1.0b56.02.3mozilla6July 29, 2011 
1.0b45.02.2mozilla5June 28, 2011 
1.0b23.1.*---mozilla-1.9.2June 24, 2010 
1.0b13.0.*2.0mozilla-1.9.1January 12, 2010 
0.92.0.0.*---mozilla-1.8.1September 23, 2008 
0.82.0.0.*---mozilla-1.8.1April 4, 2008 
- -

Lançamentos de ESR Estáveis

- -

Thunderbird 10 and 17 were considered Extended Support Releases (ESR), which Lightning is compatible with. We followed the ESR policy of Thunderbird and only did releases for security fixes. Additionally, some fixes may have been backported for important regressions related to enterprise features like invitations.

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Lightning
- Versão		Thunderbird
- Versão		SeaMonkey
- Versão		Plataforma Mozilla
- Versão		Data de Lançamento
1.9.117.0esr2.14mozilla17March 6, 2013
1.2.310.0esr2.7mozilla10March 9, 2012
- -

Sunbird

- -

Por favor, note que o Sunbird foi descontinuado, consulte este blogue para detalhes. Não haverá mais lançamento do Sunbird até novo aviso.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
Sunbird
- Versão		Mozilla Platform
- Versão		Data de Lançamento
1.0b11.9.1March 30, 2010
0.91.8.1September 23, 2008
0.81.8.1April 4, 2008
diff --git a/files/pt-pt/mozilla/calendar/index.html b/files/pt-pt/mozilla/calendar/index.html deleted file mode 100644 index 17e6540daa..0000000000 --- a/files/pt-pt/mozilla/calendar/index.html +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: Calendar -slug: Mozilla/Calendar -tags: - - Calendar - - NeedsTranslation - - NeedsUpdate - - TopicStub -translation_of: Mozilla/Calendar ---- - - - - - - - -
Sunbird-Logo-148x155.png -

The Mozilla Calendar Project is a community driven project based on the Mozilla application architecture. The Project's heart is a calendaring backend based on libical. The Lightning extension is built on top of this platform and provides integrated calendaring capabilities for Mozilla Messaging's Email client Thunderbird.

-

Mozilla Calendar emphasizes free and open source technology and supports standardized technology like the ical/ics (rfc2445) format and the CalDAV (rfc4791) protocol, which is implemented by many freely available servers and also some commercial providers.

-
- - - - - - - -
-

Development Topics

-
-
- Building Calendar
-
- Information about building Calendar with the new comm-central repository. There is also a simple build page for Thunderbird including Lightning and information about how comm-central works.
-
-
-
- Creating a Calendar extension
-
- Tutorial on creating a Calendar extension for Sunbird and Lightning.
-
-
-
- Localization
-
- How to get started with translating Calendar into your language and how to build Lightning in your language. 
-
- Testing Calendar
-
- CalendarUtils reference for writing Mozmill tests, which can automatically test the UI so that regressions can be easily found.
-
- Calendar Versions
-
- This page will tell you which Calendar version fits with which Mozilla Platform and where current development is being done.
-
- 		-

Tools

-
-
- Bugzilla
-
- The Bugzilla database used to track issues for Mozilla projects.
-
-  
-
- MXR
-
- Browse and search the Calendar source code repository on the Web.
-
-  
-
- Calendar Servers
-
- Setup your own calendar server, or check to see how well commercial products are supported.
-
-  
-
-
-

 

diff --git a/files/pt-pt/mozilla/criacao_barra_lateral_firefox/index.html b/files/pt-pt/mozilla/criacao_barra_lateral_firefox/index.html deleted file mode 100644 index 737ebb5925..0000000000 --- a/files/pt-pt/mozilla/criacao_barra_lateral_firefox/index.html +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Criação de uma barra lateral do Firefox -slug: Mozilla/Criacao_barra_lateral_Firefox -tags: - - Extensões - - Extras - - Firefox -translation_of: Mozilla/Creating_a_Firefox_sidebar ---- -

Os publicadores da Web podem oferecer aos visitantes uma barra lateral do Firefox para encorajar à sua participação. Existem duas maneiras de criar uma barra lateral para os utilizadores do Firefox: a API Social e uma extensão. Pode escolher dependendo das suas necessidades e recursos.

- -

A API Social

- -
-

Este conteúdo abrange as funcionalidades introduzidas no Firefox 17.

-
- -

A API Social é uma nova API da Mozilla que permite aos serviços de redes sociais integrar o seu conteúdo na jabela do navegador. De momento, o Cliqz, Facebook, mixi e a MSN têm uma parceria com a Mozilla, como provedores sociais. Agora que a API está disponível para todos os programadores da Web, então vale a pena conferir se está a oferecer um serviço social.

- -

Uma extensão

- -

An extension is a kind of add-ons that adds new functionalities to Firefox. There is a wide range of extensions available, and some of them provide a sidebar. Such kind of sidebar can be a simple Web panel or a full-featured extension that is completely integrated with the browser. There are some ways to create an extension:

- - - -

A API window.sidebar

- -

{{ obsolete_header(23) }}

- -

As of Firefox 23, the addPanel and addPersistentPanel functions have been removed from the deprecated, Netscape-derived {{ domxref("window.sidebar") }} object. That means the ability to add a traditional sidebar panel is no longer available from Web content. The new Social API or an extension can be used instead as described above.

- -

Consulte Também

- - diff --git "a/files/pt-pt/mozilla/cria\303\247\303\243o_de_um_complemento_de_dicion\303\241rio_de_verifica\303\247\303\243o_ortogr\303\241fica/index.html" "b/files/pt-pt/mozilla/cria\303\247\303\243o_de_um_complemento_de_dicion\303\241rio_de_verifica\303\247\303\243o_ortogr\303\241fica/index.html" deleted file mode 100644 index 50a536375d..0000000000 --- "a/files/pt-pt/mozilla/cria\303\247\303\243o_de_um_complemento_de_dicion\303\241rio_de_verifica\303\247\303\243o_ortogr\303\241fica/index.html" +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: Criação de um complemento de dicionário de verificação ortográfica -slug: Mozilla/Criação_de_um_complemento_de_dicionário_de_verificação_ortográfica -tags: - - Complemento - - add-on -translation_of: Mozilla/Creating_a_spell_check_dictionary_add-on ---- -

Esta página descreve como montar um dicionário de verificação ortográfica Hunspell como um complemento do Firefox, ou como atulizar um complemento existente, e assim, este pode ser instalado, desinstalado e atualizado sem reiniciar.

- -

Partes necessárias

- -

To create a dictionary add-on, you first need two things:

- - - -

If you are creating a new dictionary, as opposed to updating an existing one, please make sure that there is not already a dictionary available for your locale. If there already is one, try contacting the author to get it updated, or contact AMO editors if the author does not respond.

- -

Packaging

- -

A Firefox add-on is a ZIP file renamed to use an .xpi file extension instead of the normal .zip file extension. To create a dictionary add-on, simply create a ZIP file which contains the following files and folders:

- -

my-dictionary.xpi

- - - -

The .dic and .aff files must be placed in a subfolder named dictionaries within the ZIP file. Both files must have the locale code as their file name. You also have to add a file named install.rdf to the root of the ZIP file. This file contains information about your add-on such as name and version number (see below). In addition to these required files, you may add optional files, for example to give your add-on an icon or to describe the license of the dictionary.

- -

Here is an example of the install.rdf file. You can create and edit it with a plain text editor such as Notepad.

- -

<?xml version="1.0"?>
- <RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-      xmlns:em="http://www.mozilla.org/2004/em-rdf#">
-   <Description about="urn:mozilla:install-manifest">
-     <em:id>locale-code@dictionaries.addons.mozilla.org</em:id>
-     <em:version>version number</em:version>
-     <em:type>64</em:type>
-     <em:unpack>true</em:unpack>
-     <em:name>Name</em:name>
-     <!--
-       Other install.rdf metadata such as em:localized, em:description, em:creator,
-       em:developer, em:translator, em:contributor or em:homepageURL
-     -->
-
-     <!-- Firefox -->
-     <em:targetApplication>
-       <Description>
-         <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
-         <em:minVersion>18.0a1</em:minVersion>
-         <em:maxVersion>46.0</em:maxVersion>
-       </Description>
-     </em:targetApplication>
-
-     <!-- Thunderbird -->
-     <em:targetApplication>
-       <Description>
-         <em:id>{3550f703-e582-4d05-9a08-453d09bdfdc6}</em:id>
-         <em:minVersion>18.0a1</em:minVersion>
-         <em:maxVersion>22.0</em:maxVersion>
-       </Description>
-     </em:targetApplication>
-
-     <!-- SeaMonkey -->
-     <em:targetApplication>
-       <Description>
-         <em:id>{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}</em:id>
-         <em:minVersion>2.15a1</em:minVersion>
-         <em:maxVersion>2.49</em:maxVersion>
-       </Description>
-     </em:targetApplication>
-   </Description>
- </RDF>

- -

There are some rules about how you should adapt the install.rdf file:

- - - -

Once you have added these files to your ZIP file and renamed the file to have the .xpi extension, you can install your add-on in Firefox and test it. After a successful test, you can upload your add-on to addons.mozilla.org and ask for it to be included in the Dictionaries & Language Packs page.

diff --git "a/files/pt-pt/mozilla/firefox/edi\303\247\303\243o_programador/index.html" "b/files/pt-pt/mozilla/firefox/edi\303\247\303\243o_programador/index.html" deleted file mode 100644 index 3f3e7d3c90..0000000000 --- "a/files/pt-pt/mozilla/firefox/edi\303\247\303\243o_programador/index.html" +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Edição do Programador -slug: Mozilla/Firefox/Edição_Programador -tags: - - Beta - - Bugs - - Developer Edition - - Edição de Desenvolvimento - - Edição do Programador - - Erros - - Latest - - Mais Recentes -translation_of: Mozilla/Firefox/Developer_Edition ---- -
{{FirefoxSidebar}}
- -

A 'Edição do Programador' do Firefox é uma versão do Firefox que está preparada para os programadores da Web. Esta inclui:

- - - -

Novidades na Edição do Programador?

- -

Transferir a Edição do Programador

diff --git a/files/pt-pt/mozilla/firefox/multiple_profiles/index.html b/files/pt-pt/mozilla/firefox/multiple_profiles/index.html deleted file mode 100644 index b7935947d7..0000000000 --- a/files/pt-pt/mozilla/firefox/multiple_profiles/index.html +++ /dev/null @@ -1,244 +0,0 @@ ---- -title: Múltiplos perfis do Firefox -slug: Mozilla/Firefox/Multiple_profiles -tags: - - Firefox - - Guía - - Perfis - - Perguntas e Respostas - - Principiante -translation_of: Mozilla/Firefox/Multiple_profiles ---- -
{{FirefoxSidebar}}
- -

Um perfil no Firefox é a coleção de definições. personalizações, extras, e outras personalizações que um utilizador criou ou instalou na sua cópia do Firefox. Pode encontrar mais detalhes sobre os perfis no site de apoio do utilizador final da Mozilla.

- -

Razões para ter múltiplos profiles

- -

The casual user may want to have different profiles for different family members. Having different profiles would allow each person to have his or her own set of bookmarks, settings, and add-ons.

- -

Web developers might want a secondary profile for testing websites, apps, or other projects on different Firefox channels. For example, you might want to have some extensions installed for Web development, but not for general-purpose Web browsing. While using the Nightly channel, you may encounter some add-ons that have become temporarily incompatible with new API changes, until the add-on developer has a chance to update them. You can remove such add-ons from your profile for Nightly use while keeping them for use with other profiles.

- -

For QA, testing, and bug triaging contributors, you may want to have multiple development versions of Firefox installed, each with its own profile. Creating new profiles for testing can keep you from losing your preferences, bookmarks, and history. It takes little time to set up a new profile, and once it is complete, all of your Firefox versions will update separately and can be run simultaneously.

- -

Canais de desenvolvimento do navegador disponíveis

- -

There are four available browser channels, each at a different level of stability and development. The four channels are Release, Beta, Developer Edition, and Nightly. The Release channel is recommended for most users, as it is the "official release" channel. However, for those more adventurous, you can try one of the other three channels to see what is coming in Firefox and play around with emerging features. The Beta channel contains the features that are expected to be in the next release of Firefox and are in final stages of testing. Aurora contains experimental features, which are not yet at beta quality. Nightly contains the latest code from Firefox developers and is the least stable channel.

- -

Ferramentas de terceiros

- -

In addition to the built-in Profile Manager and the external Profile Manager, there are a few third-party tools that make working with multiple profiles easy.

- -
-

This list is by no means exhaustive. Please add any helpful tools you discover to the list!

-
- -

Mac OS X

- - - -

Gestão de perfis

- -

Determining the profile while Firefox is running

- -

To determine the profile of a currently-running Firefox instance in Windows, macOS or Linux,

- -
    -
  1. Type about:profiles into the browser URL search bar.
    2. -
  2. The page presents a list of all of your profiles, each beginning with "Profile: " followed by its name.
    3. -
  3. The one being run by this Firefox instance will include the bold text "This is the profile in use" For example, if you find that text beneath the entry for "Profile: Suzie", then you are running in a profile named Suzie.
    4. -
- -

Launching Firefox into a Desired Profile

- -

You cannot change the profile while Firefox is running.  Although it is possible in some cases to have multiple instances of Firefox running in different profiles, to avoid confusion, you should first exit/quit/terminate all running instances of Firefox, FirefoxDeveloperEdition or Nightly.  Then follow the instructions below, applicable to your operating system.

- -

Windows

- -
Windows XP
- -
    -
  1. Click the Start button.
    2. -
  2. Click "Run".
    3. -
  3. -

    Type firefox --ProfileManager.

    -
    4. -
- -
Windows Vista/7
- -
    -
  1. Click the Start button.
    2. -
  2. Click the search bar at the bottom.
    3. -
  3. -

    Type firefox --ProfileManager.

    -
    4. -
- -
Windows 8/8.1
- -
    -
  1. Press "Windows + R" on your keyboard.
    2. -
  2. Type firefox --ProfileManager.
    3. -
- -

If the Profile Manager window does not open, Firefox may have been running in the background, even though it was not visible. Close all instances of Firefox, or restart the computer, and then try again.

- -

Linux

- -

If Firefox is already included in your Linux distribution, or if you have installed Firefox with the package manager of your Linux distribution:

- -
    -
  1. At the top of the Firefox window, click on the File menu and select Quit.
    2. -
  2. In Terminal run firefox --ProfileManager
    3. -
- -

If the Profile Manager window does not open, Firefox may have been running in the background, even though it was not visible. Close all instances of Firefox, or restart the computer and then try again.

- -

macOS

- -
    -
  1. Run the Terminal application, which is found in Applications/Utilities.
    2. -
  2. Type or paste in the path to Firefox, followed by .app/Contents/MacOS/firefox.  For example, if Firefox is installed in the recommended location, you would enter /Applications/Firefox.app/Contents/MacOS/firefox.
    3. -
  3. If you have the path to your desired profile handy, enter a space character, followed by -profile followed by another space character, followed by the full path to the profile folder you wish to launch into.  This will launch Firefox immediately.  Otherwise, enter a space character followed by --profilemanager.  This will present the Profile Manager window in which you can make your selection.
    4. -
  4. Hit return.
    5. -
- -

Here is a complete example Terminal command from steps 2-3:

- -
/Applications/Firefox.app/Contents/macOS/firefox -profile /Users/Suzie/Library/Application\ Support/Firefox/Profiles/r99d1z7c.default
- -

If you want to do this frequently and more easily, you may wish to create an Automator application, as explained in this tutorial.

- -

Criar um perfil

- -

Creating a profile through the Profile Manager

- -

These instructions should be the same for all operating systems.

- -
    -
  1. To start the Create Profile Wizard, click "Create Profile..." in the Profile Manager.
    2. -
  2. Click Next and enter the name of the profile. Use a profile name that is descriptive, such as your personal name. This name is not exposed to the Internet.
    3. -
  3. You can also choose where to store the profile on your computer. To select storage location, click Choose Folder....
    4. -
  4. If you choose your folder location for the profile, select a new or empty folder. If you choose a folder that isn't empty, and you later remove the profile and choose the \"Delete Files\" option, everything inside that folder will be deleted.
    5. -
  5. To create the new profile, click Finish.
    6. -
- -

Creating a profile through the Firefox browser

- -

You can create a new Firefox profile directly from the browser.

- -
    -
  1. Type about:profiles into the browser URL search bar
    2. -
  2. On the page, click Create a New Profile button
    3. -
  3. Read the introduction, and click Next
    4. -
  4. Enter a profile name for your new Profile. Use a profile name that is descriptive, such as your personal name. This name is not exposed to the Internet.
    5. -
  5. Optionally, to change where the profile will be stored on your computer, click Choose Folder...
    6. -
  6. To create the new profile, click Finish.
    7. -
- -

Eliminar um perfil

- -
    -
  1. In the Profile Manager, select the profile to remove, and click Delete Profile....
    2. -
  2. Confirm that you wish to delete the profile: -
      -
    • Don't Delete Files removes the profile from the Profile Manager yet retains the profile data files on your computer in the storage folder so that your information is not lost. "Don't Delete Files" is the preferred option, because it saves the old profile's folder, allowing you to recover the files to a new profile.
      • -
    • Delete Files removes the profile and its files, including the profile bookmarks, settings, passwords, etc.
      -
      - {{ warning("If you use the \"Delete Files\" option, the profile folder, and files will be deleted. This action cannot be undone.") }}
      • -
    • Cancel interrupts the profile deletion.
      • -
    -
    3. -
- -

Renomear um perfil

- -
    -
  1. In the Profile Manager, select the profile you want to rename, and then click "Rename Profile".
    2. -
  2. Enter a new name for the profile and click on OK.
    3. -
- -
-

Nota: The folder containing the files for the profile is not renamed.

-
- -

Opções

- -

Trabalhar off-line

- -

Choosing this option loads the selected profile, and starts Firefox offline. You can view previously viewed web pages, and experiment with your profile.

- -

Não perguntar no arranque

- -

If you have multiple profiles, Firefox prompts you for the profile to use each time you start Firefox. Select this option to allow Firefox to load the selected profile, without prompting at startup.

- -
-

Nota: To access other profiles after selecting this option, you must start the Profile Manager first.

-
- -

Utilizar os perfis

- -

Windows

- -

If you want to have the profile manager to pop up each time you start Firefox, so you can choose a profile, you will need to edit the "Target" of the launch icon. To do this:

- -
    -
  1. Right-click the icon and choose "Properties".
    2. -
  2. When the properties dialog box pops up, you should see a "Target" text field that you can edit, and it should show the current file path.
    3. -
  3. After the closing quote, add -ProfileManager.
    4. -
  4. Click Ok.
    5. -
- -

Now whenever you double click that icon, the profile manager should appear, allowing you to choose which profile you'd like to use.

- -

If you want individual icons to launch specific profiles, you will need to edit the "Target" of each icon. To do this:

- -
    -
  1. Right-click the icon and choose "Properties".
    2. -
  2. When the properties dialog box pops up, you should see a "Target" text field that you can edit, and it should show the current file path.
    3. -
  3. To permanently set a specific profile, add -p PROFILE_NAME to the target path, but outside of the quotes, replacing "PROFILE_NAME" with the actual profile name you chose.
    4. -
  4. If you would also like to allow multiple instances of Firefox to run at the same time, add -no-remote after the profile name.
    5. -
- -

Once you are all done, click Ok. Do this for each icon you'd like to have a specific profile for. Once done, each one should automatically start with the specified profile.

- -

Linux

- -

There is no extremely straightforward way to create custom application launchers in Gnome 3 like there was in Gnome 2. The following tutorial will help get you going overall: Gnome 3 Custom application launcher. Once you get to the point of adding a new item, you can have the profile dialog show up every time or set the launcher to launch a specific profile.

- -

If you want to have the profile manager to pop up each time you start Firefox, so you can choose a profile, you will need to set the command line for your new launcher.

- -
    -
  1. Set the "command" text field to target the executable file, likely "/usr/bin/firefox", and add the -p parameter.
    2. -
- -

If you want individual icons to launch specific profiles, you will need to set the command line for your new launcher. To do this:

- -
    -
  1. Set the "command" text field to target the executable file, likely "/usr/bin/firefox", and add the -p PROFILE_NAME parameter, replacing "PROFILE_NAME" with the specific profile.
    2. -
  2. Repeat as necessary, for each additional profile you want to set.
    3. -
  3. If you would also like to allow multiple instances of Firefox to run at the same time, add "-no-remote" after the profile name.
    4. -
- -

Mac OS X

- -

You can find a useful tutorial to set up custom launchers here: Managing Multiple Firefox Profiles in OSX. Do note it's best to follow all steps in the "Creating the scripts" section, including the "edit Info.plist" step. Leave off the profile name if you want the profile selector to show up every time you launch.

- -

Configurar vários perfis para diferentes canais do Firefox

- -

This section will be especially helpful if you are a developer, wanting to work with multiple channels, and each having their separate launcher.

- -

Windows

- -

In Windows, the Developer and Nightly builds get their own directory in the "Programs" folder, so you don't have to worry about where to store the downloaded files. However, all three will attempt to use the same profile by default. You won't want to keep this behavior, because the different channels have different levels of features. To set each launcher, follow the Windows instructions at Windows Launcher.

- -

Linux

- -

In Linux, things aren't as automatically set up. You will likely get a prompt to download a tar.bz2 file to extract from. Extract the files to a new directory, and use the new launcher instructions from here. The only change you will need to make is the command path. You will want to set it to the directory where you extracted the Firefox channel's tar.bz2 file, and the executable "firefox" file located within this directory. The remaining profile assignment methods will remain the same. You will want to, for sure, add the -no-remote part to the end of the command field, so that you could run multiple instances at the same time.

- -

Mac OS X

- -

You can find a useful tutorial to set up custom launchers here: Managing Multiple Firefox Profiles in OSX. Do note it's best to follow all steps in the "Creating the scripts" section, including the "edit Info.plist" step. Also, you'll want to change the path in the do shell script to point to the correct .app file for the Firefox channel you want to target.

diff --git a/files/pt-pt/mozilla/firefox/multiprocess_firefox/cross_process_object_wrappers/index.html b/files/pt-pt/mozilla/firefox/multiprocess_firefox/cross_process_object_wrappers/index.html deleted file mode 100644 index d6efcd07ea..0000000000 --- a/files/pt-pt/mozilla/firefox/multiprocess_firefox/cross_process_object_wrappers/index.html +++ /dev/null @@ -1,157 +0,0 @@ ---- -title: Cross Process Object Wrappers -slug: Mozilla/Firefox/Multiprocess_Firefox/Cross_Process_Object_Wrappers -translation_of: Mozilla/Firefox/Multiprocess_Firefox/Cross_Process_Object_Wrappers ---- -
{{FirefoxSidebar}}
-

Este documento descreve Cross Process Object Wrappers (CPOWs), que permite ao código de chrome aceder sincronamente ao conteúdo no 'Multiprocessos do Firefox'.

-
- -
-

Note that from Firefox 47 onwards, unsafe CPOW usage is no longer permitted in browser code. If browser code tries an unsafe CPOW operation, the browser will throw an exception and you'll see an "unsafe CPOW usage forbidden” error in the Browser Console.

- -

Add-on code is still allowed to use CPOWs "unsafely". However, if an add-on passes a CPOW into a platform API, and that platform API then attempts an unsafe operation on it, this will throw an exception. So as a general rule, add-ons should avoid passing CPOWs into non-addon code.

-
- -

In multiprocess Firefox, chrome code runs in a different process from web content. So chrome code can't directly interact with web content: instead, it must factor out the code that interacts with web content into separate scripts that are called frame scripts.

- -

Chrome code can load frame scripts into the content process using the message manager, and can then communicate with them using a message-passing API. To learn more about this, see the documentation on using the message manager.

- -

Chrome to content messaging must be asynchronous. This is because the chrome process runs the Firefox UI, so if it were blocked by the content process, then a slow content process could cause Firefox to become unresponsive to users.
-
- Converting synchronous code to be asynchronous can be difficult and time-consuming. As a migration aid, the messaging framework enables frame scripts to make content objects available to chrome through a wrapper called a Cross Process Object Wrapper, also known as a CPOW. However, although CPOWs are convenient, they have serious limitations and can cause responsiveness problems, so should only be used when necessary and only as a migration aid.

- -

Passagem de CPOWs de frame scripts

- -

Frame scripts can send messages to chrome using one of two global functions: sendAsyncMessage() or sendSyncMessage(). The optional third parameter to each of these functions is an object whose properties are objects to wrap. For example, this frame script sends a DOM node to chrome when the user clicks it, as the clicked property of the third argument:

- -
// frame script
-addEventListener("click", function (event) {
-  sendAsyncMessage("my-e10s-extension-message", {}, { clicked : event.target });
-}, false);
- -

In the chrome script, the DOM node is now accessible through a Cross Process Object Wrapper, as a property of the objects property of the message. The chrome script can get and set the wrapped object's properties and call its functions:

- -
// chrome script
-windowMM.addMessageListener("my-e10s-extension-message", handleMessage);
-
-function handleMessage(message) {
-  let wrapper = message.objects.clicked;
-  console.log(wrapper.innerHTML);
-  wrapper.innerHTML = "<h2>Modified by chrome!</h2>"
-  wrapper.setAttribute("align", "center");
-}
- -

CPOWs gerados automaticamente

- -

Add-ons that have not declared themselves multiprocess compatible are set up with a number of compatibility shims. One of these shims provides the following behavior: whenever chrome code tries to access content directly (for example, through window.content or browser.contentDocument), it is given back a CPOW that wraps the content object. This means that examples like this will actually work, even in multiprocess Firefox:

- -
gBrowser.selectedBrowser.contentDocument.body.innerHTML = "replaced by chrome code";
- -

It's still important to keep in mind, though, that this is access through a CPOW and not direct access to content.

- -

CPOWs bidirecionais

- -

A common pattern is for chrome code to access content objects and add event listeners to them. To deal with this, CPOWs are bidirectional. This means that if content passes a CPOW to the chrome process, the chrome process can synchronously pass objects (such as event listener functions) into functions defined in the CPOW.

- -

This means you can write code like this:

- -
// frame script
-
-/*
-On mouseover, send the button to the chrome script as a CPOW.
-*/
-
-var button = content.document.getElementById("click-me");
-
-button.addEventListener("mouseover", function (event) {
-  sendAsyncMessage("my-addon-message", {}, { element : event.target });
-}, false);
- -
// chrome script
-
-/*
-Load the frame script, then listen for the message.
-When we get the message, extract the CPOW and add
-a function as a listener to the button's "click" event.
-*/
-
-  browserMM.loadFrameScript("chrome://my-addon/content/frame-script.js", false);
-  browserMM.addMessageListener("my-addon-message", function(message) {
-    let wrapper = message.objects.element;
-    wrapper.addEventListener("click", function() {
-      console.log("they clicked");
-    });
-  });
-
- -

Mapear conteúdo de documentos para navegadores XUL

- -

A common pattern is to get the XUL <browser> that corresponds to a content document. To enable this, gBrowser.getBrowserForDocument and gBrowser.getBrowserForContentWindow can be passed a CPOW for the content document and content window, respectively, and return the XUL  <browser> that these documents / windows belong to. Both return null if no such browser can be found.

- -

Limitações de CPOWs

- -

Although CPOWs can be convenient they have several major limitations, which are listed below.

- -

CPOWs e APIs de plataforma

- -

You can't pass CPOWs into platform APIs that expect to receive DOM objects. For example, you can't pass a CPOW into nsIFocusManager.setFocus().

- -

Also, from Firefox 47 onwards, browser code can no longer perform unsafe CPOW operations. This means that as an add-on developer, you should not pass CPOWs into browser APIs.

- -

Reação de Chrome

- -

The lack of a synchronous API on the chrome side is intentional: because the chrome process runs the Firefox UI, any responsiveness problems affect the whole browser. By making the chrome process block on the content process, CPOWs break this principle and allow unresponsive content process to make the whole browser unresponsive.

- -

Consulte em baixo CPOWs seguros e inseguros para mais sobre isto.

- -

Desempenho

- -

Although the wrapper looks just like an object completely contained in the chrome script scope, it's really just a reference to an object in the content process. When you access a property of the wrapper, it sends a synchronous message to the content process and returns the result. This means it is many times slower to use than an object.

- -

Ordenação de mensagem

- -

CPOWs can violate assumptions you might make about message ordering. Consider this code:

- -
mm.addMessageListener("GotLoadEvent", function (msg) {
-  mm.sendAsyncMessage("ChangeDocumentURI", {newURI: "hello.com"});
-  let uri = msg.objects.document.documentURI;
-  dump("Received load event: " + uri + "\n");
-});
-
- -

This sends a message asking the frame script to change the current document URI, then accesses the current document URI via a CPOW. You might expect the value of uri to come back as "hello.com". But it might not: in order to avoid deadlocks, CPOW messages can bypass normal messages and be processed first. It’s possible that the request for the documentURI property will be processed before the "ChangeDocumentURI" message, in which case uri will have its previous value.
-
- For this reason, it’s best not to mix CPOWs with normal message manager messages. It’s also a bad idea to use CPOWs for anything security-related, since you may get results that are not consistent with surrounding code that might use the message manager.

- -

CPOWs seguros e inseguros

- -

The main reason CPOWs can be bad for responsiveness is that they make the chrome process block on the content process.

- -

Essentially, the problem is this: suppose the content process is busy with some long-running operation (for example, garbage collection). In multiprocess Firefox, the browser UI is still responsive, because it's running in a different process. But if the chrome process then tries to use a CPOW, the chrome process will block until the content process is ready to respond. Suddenly, what looked like a simple property access could block the UI for a noticeable amount of time:

- -

- -

There is one scenario, though, in which this is not a problem: when the content process is already blocking on a synchronous message it sent to the chrome process.

- -

The content process is blocked anyway waiting for the chrome process, so there's no chance, in this situation, that the CPOW call will block on some long-running activity in the content process. The content process can respond immediately to the CPOW call:

- -


-

- -

There is still a performance cost to the CPOW in this situation, because the CPOW call is an IPC call instead of a simple property access in the same process. However, the potential impact on responsiveness is much smaller.

- -

Also, in this situation, the content process is in a known state. We know it's blocked waiting for the synchronous message to return, and we know that won't change during the CPOW call. This makes the CPOW call much safer than it would otherwise be.

- -

This situation is thus called "safe CPOW usage". All other uses of CPOWs are called "unsafe CPOW usage".

- -

Consulyat também:

- - - -

 

- -

 

diff --git a/files/pt-pt/mozilla/firefox/multiprocess_firefox/depuracao_de_frame_scripts/index.html b/files/pt-pt/mozilla/firefox/multiprocess_firefox/depuracao_de_frame_scripts/index.html deleted file mode 100644 index 6f22e9a0b7..0000000000 --- a/files/pt-pt/mozilla/firefox/multiprocess_firefox/depuracao_de_frame_scripts/index.html +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Depuração de frame scripts -slug: Mozilla/Firefox/Multiprocess_Firefox/Depuracao_de_frame_scripts -tags: - - Caixa de ferramentas de Conteúdo de Navegador - - Multiprocessos do Firefox -translation_of: Mozilla/Firefox/Multiprocess_Firefox/Debugging_frame_scripts ---- -
{{FirefoxSidebar}}
-

A Caixa de Ferramentas de Conteúdo de Navegador só está disponível no Firefox Nightly, e apenas se extiver a executar o Firefox no modo de multiprocessos.

-
- -

You can use the Browser Content Toolbox to debug frame scripts. The Browser Content Toolbox is a separate window that includes some of the standard Firefox Developer Tools - specifically: the console, the JavaScript debugger, and Scratchpad - but attaches them to the browser's content process. This means you can debug the frame scripts in your add-on.

- -

Abrir a Caixa de Ferrmanetas de Conteúdo de Navegador

- -

{{EmbedYouTube("Cg6X_zIu7Xk")}}

- -

To open the Browser Content Toolbox, you'll need to:

- - - -

You should now see an item labeled "Browser Content Toolbox" in the Developer submenu in the Firefox Menu (or Tools menu if you display the menu bar or are on OS X). It opens in a separate window:

- -

If you've used the Firefox Developer Tools before, this should look pretty familiar.

- -

Along the top is a row of tabs that you can use to switch the active tool. Currently, we only support the Console, the Debugger, and Scratchpad in the Browser Content Toolbox. At the right of this row are three buttons that activate the split console, open settings, and close the toolbox.

- -

The rest of the toolbox is taken up with the tool you've currently selected.

- -

Utilização

- -

{{EmbedYouTube("XF0ULNnNOxg")}}

- -

O Depurador

- -

The Debugger lists all the scripts that are loaded into the content process. You'll find your frame scripts listed under the chrome:// URL you registered for them:

- -

You can set breakpoints, of course, and do all the other things supported by the debugger.

- -

A Consola

- -

The Console logs output from your frame scripts. If you want to use it to evaluate JavaScript in your frame script's scope, there's a trick you need to know:

- - - -

Now the console's scope is your frame script's scope, and you can interact directly with it:

- -

diff --git a/files/pt-pt/mozilla/firefox/multiprocess_firefox/gestor_de_mensagens/index.html b/files/pt-pt/mozilla/firefox/multiprocess_firefox/gestor_de_mensagens/index.html deleted file mode 100644 index 88d8419e69..0000000000 --- a/files/pt-pt/mozilla/firefox/multiprocess_firefox/gestor_de_mensagens/index.html +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Gestor de mensagens -slug: Mozilla/Firefox/Multiprocess_Firefox/Gestor_de_mensagens -tags: - - API - - Guia(2) - - JavaScript -translation_of: Mozilla/Firefox/Multiprocess_Firefox/Message_Manager ---- -
{{FirefoxSidebar}}

Os gestores de mensagens fornecem uma maneira para o código de JavaScript chrome-privilegiado para comunicar através dos limites de processo. Eles são particularmente úteis para permitir que código do chrome, incluindo o código do navegador e o código de extensão, para aceder ao conteúdo da Web enquanto o navegador está a executar conteúdo da Web num processo separado

- -

Message managers provide a way for chrome-privileged JavaScript code to communicate across process boundaries. They are particularly useful for allowing chrome code, including the browser's code and extension's code, to access web content while the browser is running web content in a separate process.

- -

These guides explain how to use message managers in multiprocess Firefox.

- -

Note that none of this requires multiprocess Firefox: everything described here will work with single-process Firefox, so the same code will work on both variants.

- -
-

Guias

- -
-
-
-
Message manager overview
-
 
-
Frame script loading and lifetime
-
 
-
Communicating with frame scripts
-
 
-
Performance Best Practices
-
 
-
-
- -
-
-
Frame script environment
-
 
-
Limitations of frame scripts
-
 
-
Process scripts
-
 
-
-
-
- -
-

Referência de API

- -
-
-
-
nsIFrameScriptLoader
-
 
-
nsIMessageListenerManager
-
 
-
nsIMessageBroadcaster
-
 
-
nsIMessageSender
-
 
-
-
- -
-
-
nsISyncMessageSender
-
 
-
nsIContentFrameMessageManager
-
 
-
nsIProcessScriptLoader
-
 
-
-
-
diff --git a/files/pt-pt/mozilla/firefox/multiprocess_firefox/glossario/index.html b/files/pt-pt/mozilla/firefox/multiprocess_firefox/glossario/index.html deleted file mode 100644 index 22bb1b5b57..0000000000 --- a/files/pt-pt/mozilla/firefox/multiprocess_firefox/glossario/index.html +++ /dev/null @@ -1,36 +0,0 @@ ---- -title: Glossário -slug: Mozilla/Firefox/Multiprocess_Firefox/Glossario -translation_of: Mozilla/Firefox/Multiprocess_Firefox/Glossary ---- -
{{FirefoxSidebar}}
-
-
-
Child-to-parent CPOWs
-
CPOWs that refer to objects in the parent (chrome) process.
-
Chrome process (also called the parent process)
-
The operating system process that runs the Firefox UI, including the toolbar, dialog boxes, and features like session restoration. All add-on code that doesn't run in frame scripts runs here.
-
Content process (also called the child process)
-
The operating system process that runs web content, in multiprocess Firefox. Code for frame scripts runs in this process.
-
Content scripts
-
Deprecated term for frame scripts.
-
CPOWs
-
CPOW stands for Cross Process Object Wrapper. A CPOW gives chrome code synchronous access to content objects, as a migration aid. See more about CPOWs.
-
-
- -
-
-
Frame scripts
-
When chrome code needs to interact with web content, it factors the code that needs to access content into separate scripts, and loads them into the content process. These separate scripts are called frame scripts. We used to call these scripts "content scripts" but have deprecated that term.
-
Message manager
-
Message managers enable chrome code to load frame scripts into content processes, and communicate with them using a message-passing API. See more about message managers.
-
Parent-to-child CPOWs
-
CPOWs that refer to objects that live in the child (content) process.
-
Shim
-
...
-
-
-
- -

 

diff --git a/files/pt-pt/mozilla/firefox/multiprocess_firefox/index.html b/files/pt-pt/mozilla/firefox/multiprocess_firefox/index.html deleted file mode 100644 index 8bf746e32a..0000000000 --- a/files/pt-pt/mozilla/firefox/multiprocess_firefox/index.html +++ /dev/null @@ -1,79 +0,0 @@ ---- -title: Multiprocessos do Firefox -slug: Mozilla/Firefox/Multiprocess_Firefox -tags: - - Firefox -translation_of: Mozilla/Firefox/Multiprocess_Firefox ---- -
{{FirefoxSidebar}}
- -

Nas versões antigas do Firefox para PC, todo o navegador era executado num único processo do sistema operativo. Em particular, o JavaScript que executa a IU do navegador (também conhecido como "código do chrome") executa o mesmo processo como o código nas páginas da Web (também conhecido como "conteúdo" ou "conteúdo da Web").
-
- As últimas versões do Firefox executam a IU do navegador num processo separado do conteúdo da Web. Na primeira iteração dessa arquitetura, todos os separadores do navegador funcionam no mesmo processo e a IU do navegador é executada num processo diferente. Em iterações futuras, nós esperamos ter mais doque um processo de conteúdo. O projeto que está a distribuir 'Multiprocessos do Firefox' é chamado de Electrolysis, por vezes abreviado para e10s.

- -

As páginas da Web normais não são afetadas pelo 'Multiprocessos do Firefox'. As pessoas que trabalham no próprio Firefox e os programadores de extras do Firefox não serão afetados se o seu código depende de ser capaz de aceder diretamente ao conteúdo da Web.

- -

Em vez de aceder ao conteúdo da web diretamente, o código do chrome terá que utilizar o gestor de mensagens. Para ajudar a facilitar esta transição, nós implementamos Cross Process Object Wrappers e alguns shims de compatibilidade para os programadores de extras. Se é um programador de extras perguntando-se a si mesmo se está ou não afetado por esta alteração, consulte o guia para trabalhar com multiprocessos do Firefox.

- -
-
-
-
-
Resumo técnico
-
A very high-level view of how multiprocess Firefox is implemented.
-
Guia de compatibilidade do conteúdo da Web
-
Guidelines and details on potential Web site compatibility issues that may arise due to the transition. Tip: there aren't very many!
-
Glossário
-
Uma referência para o gíria utilizada em 'Multiprocessos do Firefox'.
-
Gestor de mensagens
-
Complete guide to the objects used to communicate between chrome and content.
-
Extras baseados em SDK
-
How to migrate add-ons developed using the Add-on SDK.
-
Quais os URIs que carregam e onde
-
A quick guide to which URIs - chrome:, about:, file:, resource: - are loaded into which process.
-
-
- -
-
-
Motivação
-
Why we are implementing multiprocess Firefox: performance, security, and stability.
-
Guia de migração de extras
-
If you are an add-on developer, find out if you are affected and how to update your code.
-
Cross Process Object Wrappers
-
Cross Process Object Wrappers are a migration aid, giving chrome code synchronous access to content.
-
Depuração de processos do conteúdo
-
How to debug code running in the content process, including frame and process scripts.
-
Seleção de separador nos multiprocessos do Firefox
-
How switching tabs works in multiprocess Firefox.
-
-
-
- -
-
-
-
-
Limitações de chrome scripts
-
Práticas que já não irão funcionar no código de chrome, e como as fixar.
-
-
- -
-
-
Limitações de frame scripts
-
Práticas que já não irão funcionar dentro de frame scripts, e o que fazer.
-
-
-
- -
-

Contacte-nos

- -

Saiba mais sobre o projeto, participe, ou coloque as suas perguntas.

- - diff --git a/files/pt-pt/mozilla/firefox/multiprocess_firefox/limitacoes_de_chrome_scripts/index.html b/files/pt-pt/mozilla/firefox/multiprocess_firefox/limitacoes_de_chrome_scripts/index.html deleted file mode 100644 index f761b2c6f7..0000000000 --- a/files/pt-pt/mozilla/firefox/multiprocess_firefox/limitacoes_de_chrome_scripts/index.html +++ /dev/null @@ -1,215 +0,0 @@ ---- -title: Limitações de "chrome scripts" -slug: Mozilla/Firefox/Multiprocess_Firefox/Limitacoes_de_chrome_scripts -translation_of: Mozilla/Firefox/Multiprocess_Firefox/Limitations_of_chrome_scripts ---- -
{{FirefoxSidebar}}

This page describes patterns that used to work in the chrome process that will no longer work in multiprocess Firefox. These are the sorts of things that will break an old add-on in multiprocess Firefox. The fix is generally some variant of "do that in a frame script loaded into the content process".

- -

This is one of a pair of articles: the other one lists limitations of frame scripts.

- -

Compatibilidade de shims

- -

For many of the patterns described here we've implemented compatibility shims so the patterns still work. For example: whenever extensions try to access web content from the chrome process, the browser will return a Cross Process Object Wrapper that gives the chrome code synchronous access to the content.

- -

You'll get the shims for your add-on by default, unless you set the multiprocessCompatible flag in your add-on's install manifest.

- -

However, these shims are not a substitute for migrating extensions:

- - - -

You can see all the places where your add-on uses compatibility shims by setting the dom.ipc.shims.enabledWarnings preference and watching the browser console as you use the add-on.

- -

The rest of this page documents patterns that don't work in multiprocess Firefox as well as how are shims try to paper over the problem. For each pattern we've noted:

- - - -

gBrowser.contentWindow, window.content...

- -

Sem shim

- -

All APIs in the chrome process that provide direct access to content objects will no longer work. For example:

- -
// chrome code
-
-gBrowser.contentWindow;                    // null
-
-gBrowser.contentDocument;                  // null
-
-gBrowser.selectedBrowser.contentWindow;    // null
-
-window.content;                            // null
-
-content;                                   // null
-
- -

As a special note, docshells live in the content process, so they are also inaccessible:

- -
gBrowser.docShell;                         // null
-
-gBrowser.selectedBrowser.docShell;         // null
- -

Com shim

- -

The shim will give you a CPOW for the content object in these situations.

- -

In some situations, the content process may not be initialized when an add-on asks for access to its content. In this case, the shim will return a JavaScript object that looks somewhat like a window or a document for about:blank. However, this "dummy" object is completely static and only exposes a few of the normal properties that windows and documents have. For this reason, add-ons that try to access content objects in fresh <browser> elements may run into trouble.

- -

To make the shim unnecessary: factor the code that needs to access content into a separate script, load that script into the content process as a frame script, and communicate between the chrome script and the frame script using the message-passing APIs. See the article on using the message manager.

- -

Limitações de CPOWs

- -

Cross process object wrappers (CPOWs) are a migration aid giving chrome code synchronous access to content objects. However, there are various limitations on the kinds of things you can do with a CPOW.

- -
-

Note that from Firefox 47 onwards, unsafe CPOW usage is no longer permitted in browser code. If browser code tries an unsafe CPOW operation, the browser will throw an exception and you'll see an "unsafe CPOW usage forbidden” error in the Browser Console.

- -

Add-on code is still allowed to use CPOWs "unsafely". However, if an add-on passes a CPOW into a platform API, and that platform API then attempts an unsafe operation on it, this will throw an exception. So as a general rule, add-ons should avoid passing CPOWs into non-addon code.

-
- -

nsIContentPolicy

- -

Sem shim

- -

In multiprocess Firefox, if you register the nsIContentPolicy in the chrome process then it will never see any attempts to load web content, because they happen in the content process.

- -

Com shim

- -

The shim enables you to add content policies in the chrome process. It transparently registers an nsIContentPolicy in the content process, whose shouldLoad just forwards to the chrome process. The content to check is forwarded as a CPOW. The chrome process then checks the content against the policy supplied by the add-on, and forwards the response back to the child to be enforced.

- -

To make the shim unnecessary: define and register nsIContentPolicy in the content process. If you need to ensure that the policy is only registered once, use a process script to register the policy.

- -

nsIWebProgressListener

- -

This API will work in the chrome process. There is a shim that gives you access to the DOMWindow property of the nsIWebProgress object passed into onStateChange. However, the DOMWindow is passed asynchronously, so by the time the chrome process receives it, the DOM might have changed (for example, because code running in the content process modified it or we navigated to a different page). We're working on fixing this issue in bug 1118880.

- -

Also note that unlike other shims, this shim is always active.

- -

Alternatively, you can use nsIWebProgressListener in the content process.

- -

Observadores no processo de chrome

- -

Depending on the topic, you need to register observers in either the chrome process or in a frame script.

- -

For most topics you need to register observers in the chrome process.

- -

However, you must listen to content-document-global-created and document-element-inserted in a frame script. Observers for these topics get content objects as the aSubject argument to observe(), so notifications are not sent to the chrome process.

- -

There is a shim that will forward these two topics to the chrome process, sending CPOWs as the aSubject argument.

- -

Pedidos de HTTP

- -

You can't observe HTTP requests in the content process. If you do, you'll get an error.
-
- If you do so in the chrome process, it will mostly work. The subject for the observer notification will be an nsIHttpChannel as you would expect.

- -

A common pattern here is to use the notificationCallbacks property of the nsIHttpChannel to get the DOM window that initiated the load, like this:

- -
observe: function (subject, topic, data) {
-  if (topic == "http-on-modify-request") {
-    var httpChannel = subject.QueryInterface(Ci.nsIHttpChannel);
-    var domWindow = httpChannel.notificationCallbacks.getInterface(Ci.nsIDOMWindow);
-  }
-}
- -

Or this:

- -
observe: function (subject, topic, data) {
-  if (topic == "http-on-modify-request") {
-    var httpChannel = subject.QueryInterface(Ci.nsIHttpChannel);
-    var domWindow = httpChannel.notificationCallbacks.getInterface(Ci.nsILoadContext).associatedWindow;
-  }
-}
- -

In multiprocess Firefox these patterns will no longer work: the getInterface call will fail.

- -

In multiprocess Firefox, notificationCallbacks is a special object that tries to emulate the single-process notificationsCallbacks object as best it can. It will return a dummy nsILoadContext when asked, but any attempt to get a window out of it will fail.
-
- There is an outstanding bug (bug 1108827) to implement a shim here that will make notificationCallbacks a CPOW for the objects in the content process.

- -

The correct way to access the DOM window is through a message manager. In an HTTP observer, you can get the browser message manager for the window using code like this:

- -
observe: function (subject, topic, data) {
-  if (topic == "http-on-modify-request") {
-    var httpChannel = subject.QueryInterface(Ci.nsIHttpChannel);
-    var loadContext = httpChannel.notificationCallbacks.getInterface(Ci.nsILoadContext);
-    // topFrameElement is the <browser> element
-    var topFrameElement = loadContext.topFrameElement;
-    var browserMM = topFrameElement.messageManager;
-    console.log("browserMM: " + browserMM);
-  }
-}
- -

However, before Firefox 38, this technique will not work if multiprocess Firefox is disabled: specifically, topFrameElement will be null. This means that if you need to write code that works before Firefox 38 and on both multiprocess and non-multiprocess variants, you need to implement both paths:

- - - -

From Firefox 38 onwards, the topFrameElement approach always works.

- -

Eventos DOM

- -

Sem shim

- -

In multiprocess Firefox, if you want to register an event listener on some content DOM node, that needs to happen in the content process.

- -

It used to be that if you registered a listener on the XUL <browser>  or <tab> element that hosted some DOM content, then events in the content would bubble up to the XUL and you could handle them there. This no longer happens in multiprocess Firefox.

- -

Com shim

- -

The shim intercepts chrome process code that adds listeners to XUL elements and sets up listeners in the content process, relaying the result back to the chrome process. The Event object itself is relayed to the chrome process as a CPOW.

- -

To make the shim unnecessary: register event listeners on the global object inside a frame script. For example:

- -
addEventListener("load", handler, true) // for example
- -
If you need to contact the chrome process when that happens, send it a message.
- -
 
- -

Sandboxes

- -
You can create sandboxes in the chrome or the content process. Sandboxes are often used as a safe way to manipulate web content, and if that's your goal, create the sandbox in the content process.
- -
 
- -
There is a shim for sandboxes: if you make a sandbox in the chrome process and give it content principals (by passing a CPOW as the first argument to Components.utils.Sandbox) then we'll actually make it in the content process.
- -
 
- -
-

nsIAboutModule

- -

By default, custom about: pages registered using nsIAboutModule are loaded in the chrome process. This means that you can't access their content from the content process (via XHR, for example).

- -

You can change this default in the code you use to register the about: URI. See about: and chrome: URIs.

-
- -

Módulos de código de JavaScript (JSMs)

- -
In single-process Firefox, you can use JavaScript code modules (JSMs) to maintain global state. In multiprocess Firefox, a JSM loaded into one process does not share any state with the same JSM loaded into a different process: so you can't use a JSM to share state between the chrome and content processes.
- -
 
- -
If an add-on wants to use a JSM to share state in this way, it's best to load the JSM in the chrome process, and have frame scripts store and access the JSM's state by sending messages to the chrome process using the message manager.
- -
 
- -

nsIProtocolHandler

- -
In multiprocess Firefox, code which registers a custom protocol using nsIProtocolHandler must register the custom protocol in the child content process.
- -
If the custom protocol is registered only in the chrome process, no iframes or tabs will be able to load any resource from the custom procotol.
- -
 
- -
The solution is to register the custom protocol in the content process. You can do this by loading a frame script or, with the Add-on SDK, you can use remoteRequire() in the "remote/parent" module.
diff --git a/files/pt-pt/mozilla/firefox/multiprocess_firefox/limitacoes_de_frame_scripts/index.html b/files/pt-pt/mozilla/firefox/multiprocess_firefox/limitacoes_de_frame_scripts/index.html deleted file mode 100644 index 999472c499..0000000000 --- a/files/pt-pt/mozilla/firefox/multiprocess_firefox/limitacoes_de_frame_scripts/index.html +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Limitações de frame scripts -slug: Mozilla/Firefox/Multiprocess_Firefox/Limitacoes_de_frame_scripts -translation_of: Mozilla/Firefox/Multiprocess_Firefox/Limitations_of_frame_scripts ---- -
{{FirefoxSidebar}}

Frame scripts run with system privileges and have access to the Components object, enabling them to use XPCOM objects and JSMs. Many privileged APIs will just work in a content process. Anything that just manipulates data structures will just work. XHR and Workers will work. However, some APIs  that work in the chrome process will not work in a frame script. This article lists the most important of these APIs.

- -

This is one of a pair of articles: the other one lists limitations of chrome scripts.

- -

Restrições de Segurança no Acesso de Ficheiro

- -

Processes that host remote content are isolated from the local system through a content security sandbox. One of the functions of the sandbox is to restrict access to the local file system by processes that host remote content. Since frame and process scripts often execute in remote content processes these scripts are subject to the same file access rules placed on remote content. Therefore frame scripts should not attempt to access the local file system directly, as these calls will fail.

- -

Examples of APIs Add-on authors should avoid in frame scripts:

- - - -

XUL e IU de navegador

- -

Anything that tries to touch the browser UI or anything to do with XUL is likely to not work in the content process. For example:

- - - -

Serviços

- -

Some services will not work in frame scripts.

- - - -

Janelas de Chrome

- -

Anything that needs to use chrome windows will not work in the content process. For example:

- - - -

Places API

- -

A API de Places não pode ser utilizada dentro de uma frame script. Por exemplo:

- - - -

Observadores no processo de conteúdo

- -

As noted in Observers in the chrome process, most observers should be registered in the chrome process and will not work in the content process. The exceptions are:

- - - -

These must be registered in the content process.

- -

QI from content window to chrome window

- -
There's a particular pattern often used to get from a content window to the associated chrome window. It looks something like this:
- -
 
- -
window.QueryInterface(Ci.nsIInterfaceRequestor)
-                         .getInterface(Ci.nsIWebNavigation)
-                         .QueryInterface(Ci.nsIDocShellTreeItem)
-                         .rootTreeItem
-                         .QueryInterface(Ci.nsIInterfaceRequestor)
-                         .getInterface(Ci.nsIDOMWindow);
- -
This will no longer work. In the content process the root tree item is an nsITabChild, that cannot be converted to an nsIDOMWindow, so the second getInterface call here will fail.
- -
 
- -

If you want a chrome window: send a message from the content process using the message manager. The target property of the object passed into the message handler in the chrome process is the XUL <browser> receiving the message, and you can get the chrome window from that (Note: I'm not really sure how...).

- -

nsIAboutModule

- -

By default, custom about: pages registered using nsIAboutModule are loaded in the chrome process. This means that you can't access their content from the content process (via XHR, for example).

- -

You can change this default in the code you use to register the about: URI. See about: and chrome: URIs.

- -

Módulos de código de JavaScript (JSMs)

- -
In multiprocess Firefox, a JSM loaded into the content process does not share any state with the same JSM loaded into the chrome process. See the entry in the Limitations on chrome scripts page.
diff --git a/files/pt-pt/mozilla/firefox/multiprocess_firefox/quais_os_uris_que_carregam_e_onde/index.html b/files/pt-pt/mozilla/firefox/multiprocess_firefox/quais_os_uris_que_carregam_e_onde/index.html deleted file mode 100644 index 7a4ae7a993..0000000000 --- a/files/pt-pt/mozilla/firefox/multiprocess_firefox/quais_os_uris_que_carregam_e_onde/index.html +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Quais os URIs que carregam e onde -slug: Mozilla/Firefox/Multiprocess_Firefox/Quais_os_URIs_que_carregam_e_onde -tags: - - Processo de Chrome - - Processo de Conteúdo -translation_of: Mozilla/Firefox/Multiprocess_Firefox/Which_URIs_load_where ---- -
{{FirefoxSidebar}}

Baseado inicialmente no esquema de URI da página, o navegador pode decidir se deseja carregar uma página no processo de chrome ou um processo de conteúdo. Para alguns esquemas, pode alterar o comportamento predefinido.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
EsquemaComportamento
about: -

By default, about: pages are always loaded in the chrome process. However, when you register a new about: page, you can change this default.

- -

Two new flags are defined in nsIAboutModule:

- -
    -
  • URI_CAN_LOAD_IN_CHILD: the page will be loaded in the same process as the browser that has loaded it.
    • -
  • URI_MUST_LOAD_IN_CHILD: the page will always be loaded in a child process.
    • -
- -

To use one of these flags, return it from your implementation of getURIFlags in the code that registers the about: URI.

- -

If you use these flags, you must register the about page in the framescript for each tab. If you do not set multiprocessCompatible to true in your install.rdf then shims will be used. But the e10s shims will be deprecated soon. Read more here - Bug 1257201.

-
chrome: -

By default, chrome: pages are always loaded in the chrome process. However, when you register a new chrome: page, you can change this default.

- -

Two new flags are defined in the chrome.manifest file:

- -
    -
  • remoteenabled: the page will be loaded in the same process as the browser that has loaded it.
    • -
  • remoterequired: the page will always be loaded in a child process.
    • -
-
file: -

Carregado sempre num processo de conteúdo.

- -

Nota: This does not mean file: URIs can be used freely by code in content processes. Sandboxing may blacklist particular directories and future changes may restrict file: URIs to a separate content process, isolated from regular web content. See bug 1187099 how this can affect addons attempting to load files from the profile directory.

-
resource:Carregado sempre num processo de conteúdo.
diff --git "a/files/pt-pt/mozilla/firefox/multiprocess_firefox/resumo_t\303\251cnico/index.html" "b/files/pt-pt/mozilla/firefox/multiprocess_firefox/resumo_t\303\251cnico/index.html" deleted file mode 100644 index aa2613a58e..0000000000 --- "a/files/pt-pt/mozilla/firefox/multiprocess_firefox/resumo_t\303\251cnico/index.html" +++ /dev/null @@ -1,164 +0,0 @@ ---- -title: Resumo técnico -slug: Mozilla/Firefox/Multiprocess_Firefox/Resumo_técnico -translation_of: Mozilla/Firefox/Multiprocess_Firefox/Technical_overview ---- -
{{FirefoxSidebar}}
-

This page is an edited extract from Bill McCloskey's blog post on multiprocess Firefox: http://billmccloskey.wordpress.com/2013/12/05/multiprocess-firefox/

-
- -

At a very high level, multiprocess Firefox works as follows. The process that starts up when Firefox launches is called the parent process. Initially, this process works similarly to single-process Firefox: it opens a window displaying browser.xul, which contains all the principal UI elements for Firefox. Firefox has a flexible GUI toolkit called XUL that allows GUI elements to be declared and laid out declaratively, similar to web content. Just like web content, the Firefox UI has a window object, which has a document property, and this document contains all the XML elements from browser.xul. All the Firefox menus, toolbars, sidebars, and tabs are XML elements in this document. Each tab element contains a <browser> element to display web content.

- -

The first place where multiprocess Firefox diverges from single-process Firefox is that each <browser> element has a remote="true" attribute. When such a browser element is added to the document, a new content process is started. This process is called a child process. An IPC channel is created that links the parent and child processes. Initially, the child displays about:blank, but the parent can send the child a command to navigate elsewhere.

- -

Desenho

- -

Somehow, displayed web content needs to get from the child process to the parent and then to the screen. Multiprocess Firefox depends on a new Firefox feature called off main thread compositing (OMTC). In brief, each Firefox window is broken into a series of layers, somewhat similar to layers in Photoshop. Each time Firefox draws, these layers are submitted to a compositor thread that clips and translates the layers and combines them together into a single image that is then drawn.

- -

Layers are structured as a tree. The root layer of the tree is responsible for the entire Firefox window. This layer contains other layers, some of which are responsible for drawing the menus and tabs. One subtree displays all the web content. Web content itself may be broken into multiple layers, but they’re all rooted at a single “content” layer.

- -

In multiprocess Firefox, the content layer subtree is actually a shim. Most of the time, it contains a placeholder node that simply keeps a reference to the IPC link with the child process. The content process retains the actual layer tree for web content. It builds and draws to this layer tree. When it’s done, it sends the structure of its layer tree to the parent process via IPC. Backing buffers are shared with the parent either through shared memory or GPU memory. References to this memory are sent as part of the layer tree. When the parent receives the layer tree, it removes its placeholder content node and replaces it with the actual tree from content. Then it composites and draws as normal. When it’s done, it puts the placeholder back.

- -

The basic architecture of how OMTC works with multiple processes has existed for some time, since it is needed for Firefox OS. However, Matt Woodrow and David Anderson have done a lot of work to get everything working properly on Windows, Mac, and Linux. One of the big challenges for multiprocess Firefox will be getting OMTC enabled on all platforms. Right now, only Macs use it by default.

- -

User input

- -

Events in Firefox work the same way as they do on the web. Namely, there is a DOM tree for the entire window, and events are threaded through this tree in capture and bubbling phases. Imagine that the user clicks on a button on a web page. In single-process Firefox, the root DOM node of the Firefox window gets the first chance to process the event. Then, nodes lower down in the DOM tree get a chance. The event handling proceeds down through to the XUL <browser> element. At this point, nodes in the web page’s DOM tree are given a chance to handle the event, all the way down to the button. The bubble phase follows, running in the opposite order, all the way back up to the root node of the Firefox window.

- -

With multiple processes, event handling works the same way until the <browser> element is hit. At that point, if the event hasn’t been handled yet, it gets sent to the child process by IPC, where handling starts at the root of the content DOM tree. The parent process then waits to run its bubbling phase until the content process has finished handling the event.

- -

Inter-process communication

- -

All IPC happens using the Chromium IPC libraries. Each child process has its own separate IPC link with the parent. Children cannot communicate directly with each other. To prevent deadlocks and to ensure responsiveness, the parent process is not allowed to sit around waiting for messages from the child. However, the child is allowed to block on messages from the parent.

- -

Rather than directly sending packets of data over IPC as one might expect, we use code generation to make the process much nicer. The IPC protocol is defined in IPDL, which sort of stands for “inter-* protocol definition language”. A typical IPDL file is PNecko.ipdl. It defines a set messages and their parameters. Parameters are serialized and included in the message. To send a message M, C++ code just needs to call the method SendM. To receive the message, it implements the method RecvM.

- -

IPDL is used in all the low-level C++ parts of Gecko where IPC is required. In many cases, IPC is just used to forward actions from the child to the parent. This is a common pattern in Gecko:

- -
void AddHistoryEntry(param) {
-  if (XRE_GetProcessType() == GeckoProcessType_Content) {
-    // If we're in the child, ask the parent to do this for us.
-    SendAddHistoryEntry(param);
-    return;
-  }
-
-  // Actually add the history entry...
-}
-
-bool RecvAddHistoryEntry(param) {
-  // Got a message from the child. Do the work for it.
-  AddHistoryEntry(param);
-  return true;
-}
-
- -

When AddHistoryEntry is called in the child, we detect that we’re inside the child process and send an IPC message to the parent. When the parent receives that message, it calls AddHistoryEntry on its side.

- -

For a more realistic illustration, consider the Places database, which stores visited URLs for populating the awesome bar. Whenever the user visits a URL in the content process, we call this code. Notice the content process check followed by the SendVisitURI call and an immediate return. The message is received here; this code just calls VisitURI in the parent.

- -

The code for IndexedDB, the places database, and HTTP connections all runs in the parent process, and they all use roughly the same proxying mechanism in the child.

- -

Frame scripts

- -

IPDL takes care of passing messages in C++, but much of Firefox is actually written in JavaScript. Instead of using IPDL directly, JavaScript code relies on the message manager to communicate between processes. To use the message manager in JS, you need to get hold of a message manager object. There is a global message manager, message managers for each Firefox window, and message managers for each <browser> element. A message manager can be used to load JS code into the child process and to exchange messages with it.

- -

As a simple example, imagine that we want to be informed every time a load event triggers in web content. We’re not interested in any particular browser or window, so we use the global message manager. The basic process is as follows:

- -
// Get the global message manager.
-let mm = Cc["@mozilla.org/globalmessagemanager;1"].
-         getService(Ci.nsIMessageListenerManager);
-
-// Wait for load event.
-mm.addMessageListener("GotLoadEvent", function (msg) {
-  dump("Received load event: " + msg.data.url + "\n");
-});
-
-// Load code into the child process to listen for the event.
-mm.loadFrameScript("chrome://content/content-script.js", true);
-
- -

For this to work, we also need to have a file content-script.js:

- -
// Listen for the load event.
-addEventListener("load", function (e) {
-  // Inform the parent process.
-  let docURL = content.document.documentURI;
-  sendAsyncMessage("GotLoadEvent", {url: docURL});
-}, false);
-
- -

This file is called a frame script. When the loadFrameScript function call runs, the code for the script is run once for each <browser> element. This includes both remote browsers and regular ones. If we had used a per-window message manager, the code would only be run for the browser elements in that window. Any time a new browser element is added, the script is run automatically (this is the purpose of the true parameter to loadFrameScript). Since the script is run once per browser, it can access the browser’s window object and docshell via the content and docShell globals.

- -

The great thing about frame scripts is that they work in both single-process and multiprocess Firefox. To learn more about the message manager, see the message manager guide.

- -

Cross-process APIs

- -

There are a lot of APIs in Firefox that cross between the parent and child processes. An example is the webNavigation property of XUL <browser> elements. The webNavigation property is an object that provides methods like loadURI, goBack, and goForward. These methods are called in the parent process, but the actions need to happen in the child. First I’ll cover how these methods work in single-process Firefox, and then I’ll describe how we adapted them for multiple processes.

- -

The webNavigation property is defined using the XML Binding Language (XBL). XBL is a declarative language for customizing how XML elements work. Its syntax is a combination of XML and JavaScript. Firefox uses XBL extensively to customize XUL elements like <browser> and <tabbrowser>. The <browser> customizations reside in browser.xml. Here is how browser.webNavigation is defined:

- -
<field name="_webNavigation">null</field>
-
-<property name="webNavigation" readonly="true">
-   <getter>
-   <![CDATA[
-     if (!this._webNavigation)
-       this._webNavigation = this.docShell.QueryInterface(Components.interfaces.nsIWebNavigation);
-     return this._webNavigation;
-   ]]>
-   </getter>
-</property>
-
- -

This code is invoked whenever JavaScript code in Firefox accesses browser.webNavigation, where browser is some <browser> element. It checks if the result has already been cached in the browser._webNavigation field. If it hasn’t been cached, then it fetches the navigation object based off the browser’s docshell. The docshell is a Firefox-specific object that encapsulates a lot of functionality for loading new pages, navigating back and forth, and saving page history. In multiprocess Firefox, the docshell lives in the child process. Since the webNavigation accessor runs in the parent process, this.docShell above will just return null. As a consequence, this code will fail completely.

- -

One way to fix this problem would be to create a fake docshell in C++ that could be returned. It would operate by sending IPDL messages to the real docshell in the child to get work done. We may eventually take this route in the future. We decided to do the message passing in JavaScript instead, since it’s easier and faster to prototype things there. Rather than change every docshell-using accessor to test if we’re using multiprocess browsing, we decided to create a new XBL binding that applies only to remote <browser> elements. It is called remote-browser.xml, and it extends the existing browser.xml binding.

- -

The remote-browser.xml binding returns a JavaScript shim object whenever anyone uses browser.webNavigation or other similar objects. The shim object is implemented in its own JavaScript module. It uses the message manager to send messages like "WebNavigation:LoadURI" to a content script loaded by remote-browser.xml. The content script performs the actual action.

- -

The shims we provide emulate their real counterparts imperfectly. They offer enough functionality to make Firefox work, but add-ons that use them may find them insufficient. I’ll discuss strategies for making add-ons work in more detail later.

- -

Cross-process object wrappers

- -

The message manager API does not allow the parent process to call sendSyncMessage; that is, the parent is not allowed to wait for a response from the child. It’s detrimental for the parent to wait on the child, since we don’t want the browser UI to be unresponsive because of slow content. However, converting Firefox code to be asynchronous (i.e., to use sendAsyncMessage instead) can sometimes be onerous. As an expedient, we’ve introduced a new primitive that allows code in the parent process to access objects in the child process synchronously.

- -

These objects are called cross-process object wrappers, frequently abbreviated to CPOWs. They’re created using the message manager. Consider this example content script:

- -
addEventListener("load", function (e) {
-  let doc = content.document;
-  sendAsyncMessage("GotLoadEvent", {}, {document: doc});
-}, false);
-
- -

In this code, we want to be able to send a reference to the document to the parent process. We can’t use the second parameter to sendAsyncMessage to do this: that argument is converted to JSON before it is sent up. The optional third parameter allows us to send object references. Each property of this argument becomes accessible in the parent process as a CPOW. Here’s what the parent code might look like:

- -
let mm = Cc["@mozilla.org/globalmessagemanager;1"].
-         getService(Ci.nsIMessageListenerManager);
-
-mm.addMessageListener("GotLoadEvent", function (msg) {
-  let uri = msg.objects.document.documentURI;
-  dump("Received load event: " + uri + "\n");
-});
-mm.loadFrameScript("chrome://content/content-script.js", true);
-
- -

It’s important to realize that we’re send object references. The msg.objects.document object is only a wrapper. The access to its documentURI property sends a synchronous message down to the child asking for the value. The dump statement only happens after a reply has come back from the child.

- -

Because every property access sends a message, CPOWs can be slow to use. There is no caching, so 1,000 accesses to the same property will send 1,000 messages.

- -

Another problem with CPOWs is that they violate some assumptions people might have about message ordering. Consider this code:

- -
mm.addMessageListener("GotLoadEvent", function (msg) {
-  mm.sendAsyncMessage("ChangeDocumentURI", {newURI: "hello.com"});
-  let uri = msg.objects.document.documentURI;
-  dump("Received load event: " + uri + "\n");
-});
-
- -

This code sends a message asking the child to change the current document URI. Then it accesses the current document URI via a CPOW. You might expect the value of uri to come back as "hello.com". But it might not. In order to avoid deadlocks, CPOW messages can bypass normal messages and be processed first. It’s possible that the request for the documentURI property will be processed before the "ChangeDocumentURI" message, in which case uri will have some other value.

- -

For this reason, it’s best not to mix CPOWs with normal message manager messages. It’s also a bad idea to use CPOWs for anything security-related, since you may not get results that are consistent with surrounding code that might use the message manager.

- -

Despite these problems, we’ve found CPOWs to be useful for converting certain parts of Firefox to be multiprocess-compatible. It’s best to use them in cases where users are less likely to notice poor responsiveness. As an example, we use CPOWs to implement the context menu that pops up when users right-click on content elements. Whether this code is asynchronous or synchronous, the menu cannot be displayed until content has responded with data about the element that has been clicked. The user is unlikely to notice if, for example, tab animations don’t run while waiting for the menu to pop up. Their only concern is for the menu to come up as quickly as possible, which is entirely gated on the response time of the content process. For this reason, we chose to use CPOWs, since they’re easier than converting the code to be asynchronous.

- -

It’s possible that CPOWs will be phased out in the future. Asynchronous messaging using the message manager gives a user experience that is at least as good as, and often strictly better than, CPOWs. We strongly recommend that people use the message manager over CPOWs when possible. Nevertheless, CPOWs are sometimes useful.

diff --git a/files/pt-pt/mozilla/firefox_for_android/index.html b/files/pt-pt/mozilla/firefox_for_android/index.html deleted file mode 100644 index 12be7a39c2..0000000000 --- a/files/pt-pt/mozilla/firefox_for_android/index.html +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Firefox para Android -slug: Mozilla/Firefox_for_Android -tags: - - Firefox - - Mobile -translation_of: Mozilla/Firefox_for_Android ---- -

Para cada vez mais pessoas, os dispositivos móveis são o meio principal, ou até o único meio, para aceder à Internet. Firefox para Android (nome de código Fennec) é um navegador aberto, personalizável, baseado em padrões, tal como a versão Firefox para pc.

- -

Firefox para Android cria a sua interface gráfica a partir de widgets nativos do Android em vez de XUL: isto aumenta de forma significativa o seu desempenho, especialmente o tempo de arranque, e o consumo de memória.

- -

Contribuir para o Firefox para Android

- -

O ponto de partida para informação acertca do projecto Firefox para Android é a página Wiki do projecto.

- -

Podes ajudar a criar e melhorar Firefox para Android:

- - - -

Programar para a Web móvel

- -

Nós começamos a criar um guia para desenhar sites da Web para os dispositivos móveis.

- -

Com Firefox para Android, pode aceder a um numero of APIs que expoem as capacidades subjacentes do dispositivo, diminuíndo a distância entre a Web e as aplicações nativas:

- - - -

Para testar o seu site da Web no Firefox para Android, pode instalar o Firefox para Android no seu dispositivo móvel ou pode executá-lo no seu computador utilizando o Emulador Android..

- -

Desenvolver extras para dispositivos móveis

- -

Firefox for Android supports add-ons using the exact same extension system used by all other Gecko-based applications. We did not invent a new add-on system. This means that building an add-on for Firefox on Android is the same process that would be used for desktop Firefox. Add-ons that work with desktop Firefox do not automatically work in Firefox on Android. The user interfaces are just too different.

- -
O Firefox no Android tem um identificador de aplicação único que deve ser utilizado em install.rdf. O identificador é {aa3c5121-dab2-40e2-81ca-7ea25febc110}
- -

Both classic restart-required and newer restartless add-on approaches are supported. Using the restartless approach is preferred whenever possible because the user experience is far superior to forcing an application restart when installing or removing an add-on.

- -

Resumo Rápido

- - - -

Obter ajuda com o Firefox para Android

- -

A documentação e tutoriais para utilizar e a resolução de problemas do Firefox para Android estão disponíveis no site da Web de Apoio da Mozilla.

- -

Install Firefox for Android

- -

If you don't already have Firefox installed on your Android device, you can do so at the Google Play store. See the SUMO article Install Firefox on an Android device using Google Play for detailed instructions.

- -

Alternate installs

- -

There are some unofficial builds and specialized installations for devices which don't officially support Firefox for Android. Here are some helpful links for these (keep in mind they are not supported by Mozilla and you are using them at your own risk!).

- - diff --git a/files/pt-pt/mozilla/how_to_get_a_stacktrace_for_a_bug_report/index.html b/files/pt-pt/mozilla/how_to_get_a_stacktrace_for_a_bug_report/index.html deleted file mode 100644 index 0c9d6d4e8d..0000000000 --- a/files/pt-pt/mozilla/how_to_get_a_stacktrace_for_a_bug_report/index.html +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: Como obter um rastreamento para o relatório de erros -slug: Mozilla/How_to_get_a_stacktrace_for_a_bug_report -tags: - - Bugzilla -translation_of: Mozilla/How_to_get_a_stacktrace_for_a_bug_report ---- -

Se registar um relatório de crache no Bugzilla sobre um crache, deverá incluir um rastreamento (call stack) no seu relatório. Um rastreamento irá dizer aos programadores da Mozilla o que aconteceu e fornecer um ponto de partida para investigar a sua causa. Este artigo descreve como utilizar o 'relatóriod e Crache' da Mozilla (Breakpad) para obter uma Id. de crache, que os nossos engenheiros podem utilizar para obter um rastreamento, e formas alternativas de obter um rastreamento se não conseguir uma Id. de crache.

- -

Requisitos

- -

You need a binary build of Firefox from Mozilla.org. SeaMonkey and Thunderbird also support crash reporting.

- -

Mozilla's crash report server currently only has debug information for Mozilla builds and thus the crash reporter cannot work if you use a build from a Linux distribution or if you compile from source code. In these cases you will need to use one of the alternative methods listed below.

- -
Nota: When filing a crash report, it is important to know whether the crash occurs with Firefox safe mode. This helps engineers determine whether a particular extension or plugin is the cause of the crash.
- -

Como obter uma Id. de crache com o 'Relat´rio de Crache' da Mozilla

- - - - - - - - -
-

1. Crash and submit a report to the system.

- -

The Mozilla Crash Reporter window should automatically come up after Firefox crashes. If you have any additional information about the crash, such as additional detail on what you were doing at the time that may have triggered the crash, please enter it into the comments box. Be sure that you check the "Tell Mozilla about this crash" checkbox and click the restart button. The crash reporter should now submit the crash report and Firefox should open again.

- -
The "Details" button gives additional data about the incident, however this is not useful in a bug report.
- 		-

reporter.jpg

-
- - - - - - - - -
-

2. Tell us the ID of the report you submitted.

- -

To access all of your submitted reports type "about:crashes" into the Firefox address bar and press enter. Firefox should open a list of IDs for your submitted crash reports. Copy two or three of the IDs for the appropriate crashes and paste them into your Bugzilla report. Please check the listed times to avoid copying the ID of an unrelated crash report.

- -
You can prefix a "bp-" to the beginning of an ID to make Bugzilla turn it into a link: bp-a70759c6-1295-4160-aa30-bc4772090918
- 		-

crashlist.jpg

-
- -

How to get the crash ID if Firefox crashes on startup

- -

If Firefox crashes on startup you can still access your submitted crash reports. Crash reports are accessible from all Firefox profiles, so if a new profile does not crash you can use it to access them through "about:crashes" as above.

- -

Aceder às Ids. do relatório de crache fora do Firefox

- -

If you cannot load Firefox at all you can find the crash report files at this location depending on your operating system:

- -

Windows : %APPDATA%\Mozilla\Firefox\Crash Reports\submitted\
- OS X : ~/Library/Application Support/Firefox/Crash Reports/submitted/
- Linux : ~/.mozilla/firefox/Crash Reports/submitted/

- -

Each file in this folder contains one submitted crash report ID. You can check the modified or creation time for each file to discern which crash reports are relevant to your bug report.

- -

Modos alternativos para obter um rastreamento

- -

If the Mozilla crash reporter doesn't come up or isn't available you will need to obtain a stacktrace manually:

- -

Windows

- -

See the article Create a stacktrace with Windbg for information on how to do this.

- -

For a full process dump, see How to get a process dump with Windows Task Manager [en-US]

- -

OS X

- -

Run /Applications/Utilities/Console.app.  Expand "~/Library/Logs" and "CrashReporter", then look for logs for "firefox-bin".

- -

Linux

- -

Note that for most distros the package you need to get symbols for will be something like "xulrunner", not "firefox".

- -

Os ficheiros de relatórios de crache no seu computador

- -

When Breakpad initially catches a crash it first writes crash report files (e.g. .dump and .extra files) into the 'pending' subdirectory of its 'Crash Reports' directory.

- -

If Breakpad successfully sends the crash report to the reporting server then, by default, the files added to the 'pending' subdirectory for the crash are removed, and a .txt file is placed in the 'submitted' directory containing the crash ID that the reporting server recorded the crash under. If you want Breakpad to leave the .dump and .extra files on your computer so that you can examine them locally, then set the MOZ_CRASHREPORTER_NO_DELETE_DUMP environment variable to 1.

- - diff --git a/files/pt-pt/mozilla/implementacao_do_pontoon_num_projeto_da_mozilla/index.html b/files/pt-pt/mozilla/implementacao_do_pontoon_num_projeto_da_mozilla/index.html deleted file mode 100644 index 05fb22e5c3..0000000000 --- a/files/pt-pt/mozilla/implementacao_do_pontoon_num_projeto_da_mozilla/index.html +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Implementação do Pontoon num projeto da Mozilla -slug: Mozilla/Implementacao_do_Pontoon_num_projeto_da_Mozilla -tags: - - Localização - - Tradução -translation_of: Mozilla/Implementing_Pontoon_in_a_Mozilla_website ---- -

Pontoon é uma ferramenta de localização (l10n), O-Que-Vê-É-O-Que-Obtém (WYSIWYG) baseada na Web. É uma ferramenta muito simples e intuitiva que requer poucos conhecimentos técnicos para os tradutores utilizarem, que irá reduzir o seu tempo para publicar as versões loacalizadas do seu projeto. Aqui, nós iremos discutir como é que pode utilizar o Pontoon com o seu projeto da Mozilla.

- -
-

Would you like to improve Pontoon? Learn how to get involved on GitHub.

-
- -
-

Just getting started with your project l10n? Check out the wiki on getting your project localized.

-
- -

A. Make your project localizable

- -

We realize that these are already considered to be standard best practices for localizing projects at Mozilla, but we feel it's good to add them here as a little reminder.

- -
    -
  1. Ensure that your project supports one of the l10n frameworks (gettext, XLIFF, L20n, lang, properties, etc.).
    2. -
  2. Extract localizable strings into resource files.
    3. -
  3. Push resource files to a repository (SVN, HG, Git). -
      -
    • Individual locale folders must be located at the same nesting level of the directory tree. Source locale needs to be called templates, en-US, en-us or en. If multiple folders with such name exist in the repository and contain files in a supported file format, the first one will be used. You may want to put all locale folders in a dedicated locales folder for this purpose. Locale code must not be part of the file name.
      • -
    • Correct pattern: - 
      /locales/{locale_code}/path/to/file.extension
      -
      • -
    • Incorrect pattern: - 
      /locales/{locale_code}/path/to/file.{locale_code}.extension
      -
      • -
    -
    4. -
  4. Make sure Pontoon has write access to the repository. - -
    5. -
- -

B. (optional) Enable in-page localization of your web project

- -
    -
  1. Link a script from your HTML <body> element, so Pontoon can talk to your site, detect content and make it localizable in place. You only need to do this in the environment that will be used for in-page localization, e.g. staging server: - - -
    2. -
  2. If your site uses CSP, please make sure that the following is permitted for domain pontoon.mozilla.org: -
      -
    1. loading inside iframe
      2. -
    2. loading remote CSS
      3. -
    3. loading remote images
      4. -
    -
    3. -
  3. If your site uses the X-Frame-Options header, please make sure loading inside iframe is permitted for domain pontoon.mozilla.org.
    4. -
  4. Make sure your site supports HTTPS. It's free, automated and open. Let's encrypt!
    5. -
- -

C. Add your project to Pontoon

- -

Your project is now ready to be set up in Pontoon. Please file a bug in Localization Infrastructure and Tools :: Administration / Setup and provide the following information:

- - - -

For more details, please get in touch with the Project Management Team.

diff --git a/files/pt-pt/mozilla/ligar/index.html b/files/pt-pt/mozilla/ligar/index.html deleted file mode 100644 index 2fda2a50be..0000000000 --- a/files/pt-pt/mozilla/ligar/index.html +++ /dev/null @@ -1,117 +0,0 @@ ---- -title: Ligar com Mozilla -slug: Mozilla/Ligar -tags: - - Ligar - - Mozilla -translation_of: Mozilla/Connect ---- -

Habilitar, inspirar e colaborar para tornar a Web na plataforma primária mais utilizada, para criar experiências através de todos os dispositivos interligados.

- -
-
-
-

Blogue de Hacks

- -

Um recurso chave para as pessoas desenvolverem para a Web Aberta, o blogue de Hacks da Mozilla oferece notícias e discussões sobre as últimas tecnologias da e funcionalidades de navegador.

- -
Read it now
-
-
- -
-
-

Canais de Opiniões/Críticas

- -

Teum uma idea fantástica paras as Ferramentas de Desenvolvimento? Contacte-nos e ajude a moldar as funcionalidades de futuro!

- 
-
- -
-
-

Hack na MDN

- -

Whether you hack code or text, we have ways you can help make MDN better. When you create an MDN profile, you can show off your work here, and get early access to MDN features over time as we roll them out.

- -
Join or login
-
-
-
- -
-

Ligar com Mozilla

- -

Developers are creating the future by building services and apps for people all over the world. The goal of Mozilla Developer Relations is to help developers to use open and standardized web technologies to succeed in achieving their goals. We offer help and other resources towards this goal, through various channels. We invite you to connect, learn, and share your knowledge.

- -

Reach out to us at devrel@mozilla.com or on the irc.mozilla.org #devrel IRC channel. We also have a newsletter keeping you informed about the latest happenings in the web scene around web apps and more. Subscribe to the Apps & Hacks newsletter.

- -

We have a lot of plans and ideas for iteratively expanding our Developer Relations offerings, and we want you involved as we do so! So subscribe to the Hacks blog and subscribe to the newsletter!

- -

If you're on Twitter, follow us and hear about doc updates, jobs, contributor opportunities, and more.

- -

Aderir à Mozilla

- -

If you want to go beyond connecting with Mozilla, you can join Mozilla and help realize Mozilla's mission of building a better Internet. As a developer, you have skills to contribute in many areas, as well as the opportunity to enhance your skills. Mozilla is an open source project, so we "default to open." You can "view source" and contribute to our software development projects, like the Firefox browser for desktop and Android, Firefox OS, and Mozilla's websites. You can become part of an international community and get recognition for your efforts. Here are some of the advantages of contributing to the Mozilla project.

- -

Oportunidade para aprender qualquer coisa nova

- -
-

In writing code for an open source project, you may face problems you have not encountered before, which present learning opportunities for you. You can try out new tools and techniques in an open source project. For example, if you have never done unit testing, and cannot get permission to do so at work then coding for an open source project would be an excellent place to learn more about it. Contributing to open source gives you the opportunity to collaborate with and get to know many people around the world who have similar interests. Moreover, an open source organization like Mozilla has many contributors who can help you in solving problems you encounter. If you're just getting started contributing, you can look for "mentored" bugs, where an experienced contributor has offered to help a newcomer fix them.

- -

O que eu obtenho ao contribuir?

- -

Exploring many things and gaining recognition in the community -- these are the intangible benefits of contributing to Mozilla. While we can't guarantee specific tangible benefits, many valued contributors receive free Mozilla gear and invitations to Mozilla-related events, and are first in line to be considered for internships. Moreover, your experience in contributing to an open source project might help you find a job. More and more employers of developers are looking at open source contributions. They like to see that you're blogging and contributing to mailing lists, and they like to see you listed as a contributor to an open source project. It may also help with the work experience section of your CV/resumé.

- -

Como pode contribuir para a Mozilla

- -

There are many project area for which you can contribute to Mozilla. You can find a current, complete list on the main Mozilla Get Involved page. Some areas that may interest you as a developer include:

- - -
-
- -
-
 
- -
 
-
- -

Developers at a Firefox OS workshop in Madrid.

- -
-
-

Onde está a Mozilla?

- -

View attendees and details on our Events page...

-
- -
-

Outros recursos

- - -
-
diff --git "a/files/pt-pt/mozilla/localization/aplica\303\247\303\243o_tradu\303\247\303\243o_com_mercurial/index.html" "b/files/pt-pt/mozilla/localization/aplica\303\247\303\243o_tradu\303\247\303\243o_com_mercurial/index.html" deleted file mode 100644 index ef44aa26fa..0000000000 --- "a/files/pt-pt/mozilla/localization/aplica\303\247\303\243o_tradu\303\247\303\243o_com_mercurial/index.html" +++ /dev/null @@ -1,282 +0,0 @@ ---- -title: Tradução da Aplicação com Mercurial -slug: Mozilla/Localization/aplicação_tradução_com_mercurial -translation_of: Mozilla/Localization/Application_Translation_with_Mercurial ---- -

{{draft}}

- -

Verifique qual o idioma que está disponível para tradução

- -
    -
  1. Find out on which branch localization is done for your locale: Read your localization team's page by clicking on the team with your language code (e.g. "de" for German). The localization lead for your language knows the branch. The default localization branch is aurora.
    2. -
  2. Next check what is still untranslated by going to Localization status page and click on the page for your language.
    3. -
  3. In the section "Applications & Sign-offs", you will find different products and branches which are currently in translation. -
      -
    • gaia-* denotes branches of Firefox OS, the operating system for mobile devices.
      • -
    • Firefox and fx-* denote branches of Firefox for Desktop, the browser for desktops and notebooks running, Windows, Mac OS or Linux.
      • -
    • Fennec and fennec-* denote branches of Firefox for Mobile, the Firefox browser for the Android operating system.
      • -
    • Thunderbird and tb-* denote branches of Thunderbird, the mail client, newsgroup and feed reader and chat client. The localization of the Lightning calendar add-on also takes place on these branches.
      • -
    • SeaMonkey and sea-* denote branches of SeaMonkey, the suite consisting of browser, mail and chat client and more.
      • -
    • Lightning and cal-* denote branches of Lightning, the calendar add-on for Thunderbird. The localization of Lightning now happens on Thunderbird's tb-* branches, the cal-* branches have been retired.
      • -
    -
    4. -
  4. In this example, we assume Firefox for Desktop shall be localized and that the localization branch is aurora. Scroll to the fx_aurora text.
    5. -
  5. Read the text next to it. -
      -
    • If it is 'Translated', the branch has already been translated. Either translate a different product now or contact the person responsible for localization from the team's page (see above) so he can notify you by mail when the next strings for translation become available.
      • -
    • If it is a red text consisting of a number and the word 'missing', then there are untranslated texts and you can move on with this guide.
      -  
      • -
    -
    6. -
- -

Ferramentas Necessárias

- -

Pré-requisitos de criação

- -

First, get the required programs to compile Mozilla applications like Firefox and Thunderbird from Instruções de Compilação. This is only necessary once.

- -
-

MozillaBuild deve estar instalado num caminho de ficheiro absoluto sem espaços em branco, senão este será interrompido..

-
- -

Programa de comparação de ficheiro

- -

For the translation, it is recommend to use file comparison program to compare the English file (containing the new texts) with the file of your locale (which is still missing the new strings). This example uses WinMerge: Download and install it. A comparison of alternatives (e.g. for Linux and Mac OS) is available on Wikipedia.

- -

Editor de ficheiro e texto

- -

For editing individual files a text editor can be a better choice than a file comparion program, e.g. because the file is new and everything has to be translated, the file is too customized to compare it to the English one, or special functionality is required (e.g. bookmarking untranslated lines). Use a text editor you are comfortable with. This example uses Notepad++.

- -

Ferramenta de monitorização do progresso

- -

To track which strings and files already have been translated and later also to see which new strings have already been tested in the product as being a good translation for the functionality behind the translated strings and that the translated texts fit into the available, the translation progress should be tracked. This can be done in a text editor or word processor or any other tool in which you can attach different kind of states to the individual texts to translate. The Firefox extension Scrapbook is used in this guide. Install it into your default Firefox profile (you will have more than one profile when following this guide).

- -

Obter os Textos atuais em inglês e o seu idioma

- -

Obter os textos em inglês com o código fonte

- -

Get the source code by downloading the following file:

- - - -

In the next step, we will unpack the source code:

- -
    -
  1. Open an input shell, e.g. by pressing the Windows key and R on the keyboard Screenshot of Windows key + R key or by calling the "Run..." command from the Windows "Start" button, and then typing cmd and pressing the Enter key.
    2. -
  2. Launch the installed MozillaBuild toolset by launching it with its path, e.g. C:\Mozilla\Coding\Buildtools\MozillaBuild\start-shell-msvc2010.bat You can autocomplete the file path after typing a few characters and then pressing the Tabulator key.
    - If you launch the start-shell-l10n.bat, compiling features will be disabled. You can create translation patches, but creating language packs for the application, binary repacks of the application (changing the localization of the program), and compiling the application likely won't work.
    3. -
  3. You are now in the Mozilla development environment which emulates a Linux environment. Now go to the directory where you want to put the source code. It's highly recommended to put it onto the fastest hard drive in the device. File paths here work starting with a slash (/) followed by the drive letter, and then the directory structure like on Windows, but using slashes (/) instead of backslashes (\). So let's go to C:\Mozilla by typing
    - cd /c/Mozilla/
    4. -
  4. Create a new directory for the source code:
    - mkdir mozilla-aurora
    5. -
  5. Initialize the new directory as new repository:
    - hg init mozilla-aurora
    6. -
  6. Go into the new directory:
    - cd mozilla-aurora
    7. -
  7. Unpack the source code:
    - hg unbundle /path/to/the/downloaded/mozilla-aurora.hg
    - This can take some time, mostly depending on the performance of the hard drive.
    8. -
  8. Extract the files:
    - hg update
    9. -
- -

Obter os textos para a sua localização

- -
    -
  1. Go back to the parent folder of mozilla-aurora:
    - cd ..
    2. -
  2. Find the localization repository for your branch and language on http://hg.mozilla.org/ E.g. for aurora and German (language code 'de'), it is http://hg.mozilla.org/releases/l10n/mozilla-aurora/de/ Copy that url to the clipboard.
    3. -
  3. Copy the repository to your computer by running the following command:
    - hg clone http://hg.mozilla.org/releases/l10n/mozilla-aurora/de/ de-mozilla-aurora
    - This should proceed pretty fast.
    - On Windows, you can paste the url by calling the Paste command from the window menu in the upper left corner of the window.
    4. -
- -

Configurar as suas definições de utilizador do Mercurial

- -

Still in the command prompt, go to your home directory in the file system, e.g. for a Windows user, it looks like C:\Users\MyName , depending on your Windows version:

- -

cd /c/Users/MyName

- -

Now list all the files here:

- -

ls -a

- -

If there is no file called .hgrc , create it with

- -

> .hgrc

- -

This file stores your general Mercurial settings (Mercurial is the tool which manages the source code and its history of changes).

- -

Now go in the file system to the file and open it in your favorite text editor. Windows users can use e.g. Notepad++.

- -

Paste the following content into the file:

- -
[ui]
-username = Firstname Lastname <mynick@example.com>
-merge = internal:merge
-
-[alias]
-qexport = export -g -r qtip
-qexportall = diff -r qparent
-
-[defaults]
-commit = -v
-diff = -p -U 8
-qdiff = -p -U 8
-qnew = -U
-
-[diff]
-git = 1
-showfunc = 1
-unified = 8
-
-[extensions]
-hgext.mq =
-progress =
-
-[hooks]
-
-
- -

Put in your name and email address which later will be public on the internet after your translation patch got accepted and uploaded. Save the file and close it.

- -

Ativar filas do Mercurial (correções revertíveis)

- -

Some time will pass between the moment in which you start the localization, finish it, test it, improve it, upload it for review and get review (maybe not approved on first try). Other localizers will likely have done changes to the translation, either adding new texts, removing obsolete ones or improving the current texts. This can cause conflicts between the changes you created and theirs. For this reason, updating patches kann be necessary so Mercurial is still able to find the lines in the files which it has to replace or where it has to add them. Mercurial queues allow to revert changes and also pull changes and reapply your local changes.

- -

Go back to the localization directory:

- -

cd /c/Mozilla/de-mozilla-aurora

- -

Initiate Mercurial queues:

- -

hg qinit

- -

Conhecer o estilo de tradução

- -

For having good chances that the translation suggestions get accepted, they should match the translation style of the texts in the application already translated. In general, the labels in the applications should have the same style like the operating system, e.g. use the same order of subject, verb and objects; decline verbs or not like the operating system does.

- -

The following resources can help figuring out the translation style and translate according to them:

- - - -

Escolher o que traduzir

- -

Go to the Localization status page and click on the '<number> missing' label of the Firefox branch on which you want to translate, e.g. fx_aurora. The page which opens has a bar holding information about how many texts (strings) have already been translated, how many there are in English and your locale and have the same text, and how many are missing in your local. The interesting part follows below as list of missing texts.

- -

unchanged localization report

- -

The first line shows the locale for which the texts are being translated (in this example: de - German). With the second line start the file paths of the files which require changes. The file paths follow the directory structure of the locale repository downloaded for translation. In this example, the file aboutDialog can be found in the folder browser/chrome/browser/. The text striked through are texts which have been removed in the English version and can also be removed from the locale being worked on. In this example we will translate the one new text with the id privatebrowsingpage.howToStart4 in the file aboutPrivateBrowsing.dtd.

- -

Tips for finding files with usually easily translateable texts:

- - - -

Monotorizar o progresso de tradução

- -

If you translate more than a few strings, you usually want to keep track of what has already been translated (and later if the text has been tested in the product as fitting into the available area and suiting the functionality it describes). This guide achieves this with the Firefox extension Scrapbook.

- -
    -
  1. You installed Scrapbook earlier, now open it in Firefox either by calling it from the Firefox menu bar (press the Alt key to show it if necessary) using "View" > "Sidebar" > "Scrapbook" or by clicking its toolbar button which you likely have to add by toolbar customization if you didn't do this before.
    2. -
  2. Drag the tab with the localization error showing missing and obsolete strings to the sidebar.
    3. -
  3. After Scrapbook has saved the web page to your local disk, click with the right mouse button on the page in the sidebar and choose "Properties" from the context menu which gets opened. Rename it something meaningful, e.g. "Firefox <version number> translation".
    4. -
  4. After you saved the dialog, click with the left mouse button on the page in the sidebar to open the locally saved copy.
    5. -
- -

Abrir ficheiros em inglês e o idioma de destino lado-a-lado

- -

The localization report shows the IDs of added or removed texts, but the English text itself is still unknown. We get this by comparing the English version of the file with the one of the locale we are translating in. To do so,

- -
    -
  1. Launch WinMerge.
    2. -
  2. From its "File" menu, choose "Save project".
    3. -
  3. For the file path of the left directory, go to the downloaded mozilla-aurora source code and then into its browser/locales/en-US/ folder. In this example, the absolute file path is C:\Mozilla\mozilla-aurora\browser\locales\en-US.
    4. -
  4. Enable read-only mode for the left directory.
    5. -
  5. For the file path of the right directory, go to the downloaded translation directory de-mozilla-aurora and then into its browser folder. In this example, the absolute file path is C:\Mozilla\de-mozilla-aurora\browser.
    6. -
  6. Save this comparison as project so you can easily relaunch this comparision without selecting the directories again. A good name is e.g. translation-mozilla-aurora-browser.winmerge
    7. -
  7. Open the comparison you just saved.
    8. -
- -

A tradução

- -
    -
  1. -

    Bring the console with Mercurial to the front.

    -
    2. -
  2. -

    Start tracking changes you make against the localization repository by telling it that with the qnew subcommand to save these changes as patch in a mercurial queue. This patch needs a name, choose something meaning full like "Firefox-<version number>-more-details". In this example, Firefox-29-aboutPrivateBrowsing will be used.
    - hg qnew Firefox-29-aboutPrivateBrowsing

    -
    3. -
  3. Switch back to WinMerge and navigate to browser/chrome/browser/ and open the aboutPrivateBrowsing.dtd file. You will see something like this:
    - single file comparision in WinMerge without changes by the user
    - On the left, you see an overview of the comparison of the English and the non-English file. Gray parts indicate blocks of texts which can't be found in that file, dark yellow represents changed lines and light yellow the parts of text in it which is different.
    4. -
  4. Below the license header which should never changed, the texts are organized in the following format:
    - <!ENTITY stringid "Text which will be shown in Firefox">
    5. -
  5. As you can see there is a bigger block of text not recognized. This is due to the texts which have in the English versionmoved from below the string with the id privatebrowsingpage.howToStart3 to a position above it. Cut and paste these strings in the localized file so their position corresponds to the on in the English file.
    6. -
  6. Press the F5 key or click the reload button in WinMerge's toolbar to re-compare the files.
    7. -
  7. Now copy the empty lines below privatebrowsingpage.learnMore and the line <!-- TO BE REMOVED POST-AUSTRALIS --> to the localized file. This text is a comment (which in .dtd files always can be found between <!-- and -->). There is no need to translate this text.
    8. -
  8. Now we copy the two missing lines from the English file and insert them in the localized file:
    - <!-- LOCALIZATION NOTE (privatebrowsingpage.howToStart4): please leave &newPrivateWindow.label; intact in the translation -->
    - <!ENTITY privatebrowsingpage.howToStart4               "To start Private Browsing, you can also select &newPrivateWindow.label; from the menu.">
    - The first line is a comment providing information on the localization of the text in the following line. &newPrivateWindow.label; has to be left unchanged so it can be replaced with the text of the string id &newPrivateWindow.label; whis is stored elsewhere.
    9. -
  9. Translation time: Translate the text. Afterwars, the line should look somehow like this:
    - <!ENTITY privatebrowsingpage.howToStart4               "Der private Modus kann auch über den Menü-Eintrag &newPrivateWindow.label; gestartet werden.">
    10. -
  10. Save the file.
    11. -
- -

Exportar as alterações como correção

- -

A patch is a file containing recorded changes to a repository. It can be used to apply these changes to a copy of the repository yet without these changes.

- -
    -
  1. Tell Mercurial to store the changes in the Mercurial queue with the qref command. We also create a commit message which will describe the changes in the patch and later get used when the patched gets checked in ('added') to the official repository with the localized files. For the commit message, we have to use the -m command line flag,
    - hg qref -m "Firefox 29: Localize missing string in aboutPrivateBrowsing.dtd"
    - You can change the commit message in the Mercurial queue every time by calling hg qref again.
    2. -
  2. Now export the patch to the file system using the qexport command which is defined in the .hgrc file (see above):
    - hg qexport > ../firefox-29-aboutPrivateBrowsing-v1.patch
    - This creates a patch file called firefox-29-aboutPrivateBrowsing-v1.patch containing the changes in the parent directory of de-mozilla-aurora (in this example: C:\Mozilla\).
    3. -
- -

Correção ortográfica e alterar a correção (patch)

- -

Now proof-read the patch. This detects often more than 90 percent of the possible reasons for the reviewer to not accept the patch. If you find that changes have to be done, edit the real aboutPrivateBrowsing.dtd file from the localization repository, save it and follow the steps from Exporting the changes as patch (see above).

- -

Validar a tradução no produto

- -

This guide hasn't yet a section about the validation of the translation. Please follow the instructions from the QA phase section of the Localization quick start guide.

- -

Submeter a correção (patch) para revisão

- -

Now the patch has to be shared so the people currently trusted to change the official translation can review the suggested changes.

- -
    -
  1. File a bug ("ticket") in the Mozilla Localization product and choose as component the localization for which you have translated.
    2. -
  2. Choose a meaningful bug summary which will be shown for searches etc. like in this example "Firefox 29: aboutPrivateBrowsing.dtd"
    3. -
  3. Fill any important and additional information into the description field.
    4. -
  4. Click the 'Add attachment' button.
    5. -
  5. Select the exported patch file with the file picker. The checkbox for 'patch' should get automatically checked.
    6. -
  6. Add a meaningful name for the attachment, e.g. aboutPrivateBrowsing.dtd, patch, v1
    7. -
  7. Go to the review 'Flags' category and set the one for review to ?, meaning that you request review for the patch.
    8. -
  8. In the text field next to it, add the mail address of the person leading the translation of the locale. This information can be found on the page of the localization team.
    9. -
  9. Submit the bug report.
    10. -
  10. Now you have to wait for the review of that person. This can happen on the same day, on the next weekend or later, but should happen in the timeframe given for the localization of aurora. If the person requests changes, follow the instructions under Proof-reading and altering the patch. If the reviewer accepts the changes, the patch will get uploaded and your translation will officially be added to Firefox.
    11. -
diff --git "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/configuracao_inicial/index.html" "b/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/configuracao_inicial/index.html" deleted file mode 100644 index abde7e440f..0000000000 --- "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/configuracao_inicial/index.html" +++ /dev/null @@ -1,81 +0,0 @@ ---- -title: Configuração Inciail -slug: Mozilla/Localization/Guia_iniciação_rápida/Configuracao_inicial -translation_of: Mozilla/Localization/Quick_start_guide/Initial_setup ---- -

Como um pré-requisito para contribuir com o programa de L10n, precisa de ter acesso aos códigos, ferramentas e um ambiente local adequadamente configurado (ou seja, o seu computador pessoal). Também precisa de determinar se já existe um esforço de localização para o seu idioma. Aqui, nós irmos ver as contas de que precisa, bem como as ferramentas e as suas configurações que precisa de configurar antes de contribuir.

- -

Nova ou existente

- -

Before anything else, you need to know if you will be creating a new localization or joining an existing one. This will determine what information is most applicable to you throughout the rest of this guide.

- -

Veja o que faz:

- -

Look through the existing localization community directory to see if one already exists for your locale.

- -
    -
  1. If a community already exists, reach out to them and ask how you can help.
    2. -
  2. If a community doesn't exist, send an email to the new-locales newsgroup for additional guidance.
    3. -
- -

Contas

- -

There are a handful of accounts that you need to be aware of as you begin. They're not required for you to begin contributing, but will be required when you are preparing to produce an official release. For now, simply be aware that these will become important as your efforts progress. These accounts will store your code, contributions, and help you produce an official localization.

- -
-
hg (Mercurial)
-
Mercurial is the revision control environment that houses the main Mozilla source code as well as localized code for each official Mozilla localization. You will need this for localizing Mozilla applications. Hg commit access is not necessary to begin localizing. After you have some experience with hg, you may want to get commit access. At that point, you must visit the Mozilla Committer page and follow the process outlined there. Here is an example bug that illustrates the process well. Use this bug template when filing your hg account registration bug. Add a request about creating your locale's repository to the new locales newsgroup.
-
SVN
-
SVN is a revision control environment that Mozilla uses to house Mozilla source websites and their localizations for each official Mozilla localization. See this wiki page about how to gain access to SVN. The SVN for Localizers guide will help you learn the most important SVN commands for l10n. Add a request about creating your locale's repository to the new locales newsgroup.
-
- -
-
Ferramentas de L10n baseadas na Web
-
We'll talk about these in a little bit. For now, just be aware that should you choose to use them, you may need to create a personal account.
-
Mozilla LDAP
-
You will need a Mozilla LDAP account once you're ready to have your localization registered on the main Mozilla repositories. Add a request about creating your LDAP account to the new locales newsgroup.
-
Componente de Bugzilla específico do local
-
Having a Bugzilla component specific to your locale will help us to track your localization's progress from first steps to official release. It will also notify us when you're having problems unique to your localization team's work. Add a request about creating your locale's Bugzilla component to the new locales newsgroup.
-
- -

Ferramentas de ambiente locais

- -

Similar to accounts, there is a number of environment tools that you should install on your personal computer. These tools will help you to store your contributions, build Mozilla applications and language packs, and test your work.

- -
-
Hg (Mercurial)
-
As noted above, we use Mercurial for maintaining Mozilla source code and localized code. Not only will you need a localization repository to store your localizations, but you need to have it installed and configured on your personal computer as well. You can find everything you need to know about installing and configuring Mercurial for your localization work here.
-
- -
-
comparar-idiomas
-
compare-locales is a Python script that helps you check your work without needing to run Firefox or another application. Install intructions are located here.
-
Verificações de L10n
-
L10n checks is another Python script that helps you check your work without running an application. Install instructions are located here.
-
autoconf 2.13
-
autoconf is a utility that is vital to manually creating Mozilla application builds and language packs. We use version 2.13 and higher for these builds. You can find the source files and install instructions here.
-
wget
-
wget is a command-line utility that allows you to retrieve files using internet protocols. We use it for retrieving files from repositories. You can find the source files and install instructions here.
-
Perl
-
Perl is a programming language that will help you create Mozilla application builds and language packs. You can find the source files and install instructions here.
-
Python
-
Python is a programming language in which many of our L10n testing scripts are written. You can find the source files and install instructions here.
-
Locale Switcher ou Quick Locale Switcher
-
Ambos o Locale Switcher e o Quick Locale Switcher são extras para as aplicações da Mozilla. Either one is necessary to enable you to see your work within a Mozilla application. You can install either by searching for them in Firefox's add-ons manager or following these links.
-
Um editor de texto sólido, baseado em Unicode
-
Here are some suggestions: - -
-
GNU make
-
Make is a tool which controls the generation of executables. You can find version 3.79.1 or higher here. Unfortunately, other varieties of make won't do.
-
- -

Fim da configuração inicial

- -

Agora que concluiu a configuração inicial, é hora da melhor parte: traduzir!

- -

{{ PreviousNext("Localization_Quick_Start_Guide", "Localization_Quick_Start_Guide/Translation_phase") }}

diff --git "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_da_traducao/index.html" "b/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_da_traducao/index.html" deleted file mode 100644 index cdb31df82a..0000000000 --- "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_da_traducao/index.html" +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: Fase da Tradução -slug: Mozilla/Localization/Guia_iniciação_rápida/Fase_da_Traducao -tags: - - Localização - - 'Localização: Ferramentas' - - Tradução -translation_of: Mozilla/Localization/Quick_start_guide/Translation_phase ---- -

Parabéns por completar a configuração inicial! Como recompensa pelos seus esforços, você começa a pensar no motivo pelo qual veio até aqui: localizar projetos da Mozilla.

- -

É onde o aspeto técnico do processo começa a dividir-se. Na Mozilla, nós localizamos muitos projetos diferentes que podem ser categorizados em três grupos diferentes. Cada grupo de projetos emprega um tipo diferente de ferramenta l10n para, você adivinhou, localizar os projetos. As ferramentas do l10n destinam-se a ajudá-lo a manter o seu conteúdo localizado de lançamento a lançamento e aproveitar os materiais já localizados quando localiza novo conteúdo.

- -

Aqui, nos iremo identificar esses grupos de projetos e as ferramentas de l10n associadas com os mesmo. Ao longo do caminho, nós iremos direcioná-lo para os tutoriais técnicos básicos sobre a localização desse grupo específico de projetos. Cabe a si, e à sua comunidade determinar qual a ferramenta de l10n corresponderá melhor às suas necessidades. À medida que ganha mais experiência, talvez queira localizar independentemente das ferramentas de l10n desenvolvidas pela Mozilla, que nós também discutiremos aqui.

- -

Projetos

- -

Os projetos da Mozilla e os ritmos de trabalho de l10n são divididos nestes grupos: aplicações da Mozilla, sites da Web da Mozilla, e Extras. Em baixo, irá encontrar a lista de todos os projetos da Mozilla, as suas ferramentas de l10n associadas, e hiperligações para tutoriais descrevendo os seus ritmos de trabalho.

- -

Aplicações da Mozilla

- -

So you're interested in localizing Mozilla applications. Each l10n tool follows a different workflow for localizing Mozilla application projects. We've linked a brief tutorial to each l10n tool name below. Follow the tutorials to help you decide which l10n tool fits your specific needs.

- -

These are the l10n tools we use to localize Mozilla applications:

- -
-
Pootle
-
A user-friendly web portal built on the Translate Toolkit API. This tool includes workspaces for translating strings, reviewing string submissions, and project dashboards. See the instance of Pootle used to localize Mozilla applications.
-
- -
-
Koala
-
A l10n add-on for the offline, stand-alone Komodo Edit text editor.
-
Mozilla Translator
-
Am offline, stand-alone, Java-based l10n tool that helps you translate and integrates with your repositories. Visit the Mozilla Translator (MT) download page to get your own MT client. Version 5.26 is the latest version.
-
Virtaal
-
An offline, stand-alone version of Pootle that is also built on the Translate Toolkit API.
-
- -

These are the Mozilla application projects that are localized using the l10n tools above:

- -
-
Firefox
-
The award-winning Firefox® Web browser has security, speed and new features that will change the way you use the Web. See the list of the most critical strings for localizing in Firefox, as well as a guide to understanding how they're organized.
-
Thunderbird
-
Enjoy safe, fast and easy email, Mozilla-style. The Thunderbird® email client includes intelligent spam filters, powerful search and customizable views.
-
Seamonkey
-
SeaMonkey® is the all-in-one application formerly known as the "Mozilla Application Suite", containing a web browser, a mail and newsgroups client, an HTML editor, web development tools, and an IRC chat client.
-
Firefox Mobile
-
By adding Firefox® to your mobile phone, you can access rich Web content and enjoy your favorite Firefox features wherever you go.
-
Lightning
-
Lightning is a popular calendaring, scheduling and task management extension.
-
- -

If your locale has an hg repository hosted on the Mozilla servers, you can track your localization's current progress by visiting the l10n dashboards.

- -
-

Nota: se estiver a iniciar uma nova localização e decidir utilizar uma ferramenta off-line para localizar aplicações da Mozilla, terá que familiarizar-se com a utilização de Mercurial (hg). Visite o tutorial sobre como utilizar "hg" nos seus esforços de localização aqui.

-
- -

Sites da Web da Mozilla

- -

So you're interested in localizing Mozilla websites. Each l10n tool follows a different workflow for localizing Mozilla web projects. We've linked a brief tutorial to each l10n tool name below. Follow the tutorials to help you decide which l10n tool fits your specific needs.

- -

These are the l10n tools we use to localize Mozilla web projects:

- -
-
Pontoon
-
A web-based, What-You-See-Is-What-You-Get (WYSIWYG) l10n tool that allows you to localize Mozilla websites within the site itself. Visit Pontoon here. Please note the Pontoon is not available for all web projects yet.
-
- -

These are the Mozilla web projects that are localized using the l10n tools above:

- -
-
mozilla.org
-
Every user's first Mozilla experience.
-
addons.mozilla.org (AMO)
-
A portal for all users interested in finding add-ons for their local Mozilla applications. Read the guidelines on localizing AMO, straight from the AMO team.
-
developer.mozilla.org (MDN)
-
Where you are now! Help localize the MDN user interface for everyone in your region.
-
support.mozilla.com (SUMO)
-
A portal for anyone who needs technical support for their Mozilla applications. Help localize the SUMO user interface for everyone in your region.
-
Mozilla Engagement Campaigns
-
Individual campaigns created by Mozilla to attract new contributors.
-
hacks.mozilla.org
-
For everyone interested in the leading-edge stuff that people are doing with Mozilla Firefox and the open web.
-
In-product pages
-
A set of pages used to interact with and give information to the end-user as part of their first experience with their Mozilla applications.
-
- -

Se está a criar a sua própria localização, existem vários sites da Web da Mozilla que precisam de ser localizados antes que os seus esforços se tornem numa localização lançada oficialmente. Consulte a lista de sites da Web localizados da Mozilla.

- -

Também deveria ler mais informação sobre a localização de projetos da web da Mozilla.

- -
-
 
-
- -

Extras (Add-ons)

- -

l10n for add-ons is handled by at least two other organizations/services called Babelzilla and Adofex. They both have created comprehensive programs and l10n tools for localizing any and all third-party add-ons for Mozilla applications. Visit their websites to learn how to get involved.

- - - -

Ferramenta de localização independente

- -

Are you a command-line master? Do you prefer Unicode text editors to any other applications on Earth? Do you have a pet CAT (computer-assisted translation) tool, like OmegaT? Then you may not be interested in using any of the tools listed above for your localizations. If that is the case, then this section is for you!

- -

For localizers who prefer localizing without a specialized tool the workflows for localizing Mozilla applications and Mozilla websites are essentially the same. This tutorial should provide you with all of the technical information you need to secure and maintain your tool independence.

- -

Produtibilidade

- -

Productization is an essential part of localizing Mozilla products. This is where you research and select the search plugins, content and protocol handlers, bookmarks, and links to recommended sites on the in-product pages that your locale's users will find in their Mozilla products.

- -

This tutorial will walk you through performing these productization tasks, creating productization patches, and submitting them for review.

- -

{{ PreviousNext("Localization_Quick_Start_Guide/Initial_setup", "Localization_Quick_Start_Guide/QA_phase") }}

diff --git "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_de_lancamento/index.html" "b/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_de_lancamento/index.html" deleted file mode 100644 index 310ec4344e..0000000000 --- "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_de_lancamento/index.html" +++ /dev/null @@ -1,177 +0,0 @@ ---- -title: Fase de Lançamento -slug: Mozilla/Localization/Guia_iniciação_rápida/Fase_de_lancamento -translation_of: Mozilla/Localization/Quick_start_guide/Release_phase ---- -

Você conseguiu! Configurou os seus ambientes locais e remotos, selecionou as suas ferramentas e projetos de L10n, efetuou algumas traduções e até mesmo alguns testes! Agora está pronto para a fase final: ser parte de um lançamento oficial da L10n. Aqui, nós continuaremos a ser fiéis à intenção original deste guia e apresentaremos apenas a informação técnica necessária para se tornar num lançamento oficial. Nós vamos concentrar-nos principalmente em obter a configuração do seu repositório de lançamento e comandos do Mercurial que precisa de saber para utilizar este repositório.

- -

Para obter mais informação sobre a parte de lançamento do processo L10n, visite o site da wiki da Mozilla aqui.

- -

O seu repositório oficial de lançamentos

- -

Now that your locale has been registered, the localization files will live on Mozilla Mercurial server at hg.mozilla.org. Depending on which branch you work on, the URL of your repository might look like this:

- -
http://hg.mozilla.org/releases/l10n-central/x-testing
-
- -

If you followed the Koala or plain text approach, you probably already have a local clone of the repository. Otherwise, in order to be able to make any changes to the localization files, you will need to clone the repository on your local machine and work in the local clone.

- -

There are two different protocols you can use to connet with your Mercurial repository: HTTP and SSH. Be advised that there's an important distinction between them. You can pull using both, but you can only push through SSH. Consequently, if you already have a local clone that you pulled using HTTP, you'll need to modify a config file to tell Mercurial to push through SSH. Let's go over configuring your connection protocols.

- -

Configuração

- -

Before you try pushing, you need to tell SSH which username you wish to use for connecting with hg.mozilla.org. This should be your Mozilla LDAP account name.

- -
    -
  1. Add the following lines to your ~/.ssh/config file, replacing user@host.domain with your Mozilla LDAP account name:
    2. -
- -
Host hg.mozilla.org
-User user@host.domain
- -
    -
  1. If you have already cloned the remote repository using the HTTP protocol using this command: $ hg clone http://hg.mozilla.org/releases/l10n-central/x-testing then you will need to edit the .hg/hgrc file (inside the x-testing local clone) to tell Mercurial to push using SSH. Your .hg/hgrc file shoud look like this (add the emphasized line):
    2. -
- -
[paths]
-default = hg.mozilla.org/releases/l10n-central/x-testing
-default-push = ssh://hg.mozilla.org/releases/l10n-central/x-testing
-
- -
    -
  1. If you haven't already cloned the remote repository, enter this command: hg clone ssh://hg.mozilla.org/releases/l10n-central/x-testing
    2. -
- -

Mercurial will let you know that it's cloning the repository:

- -
destination directory: x-testing
-requesting all changes
-adding changesets
-adding manifests
-adding file changes
-added 4 changesets with 242 changes to 239 files
-updating to branch default
-239 files updated, 0 files merged, 0 files removed, 0 files unresolved
-
- -

The default push URL is the same as the default pull URL (i.e., ssh://hg.mozilla.org/releases/l10n-central/x-testing).

- -

You should now be able to push to the remote repository!

- -

Commit, outgoing, and push

- -

You should try to commit your work regularly as you progress through the localization files. Keep in mind that the hg commit command will save your changes locally (in the local clone). With the hg push command you can send the changesets to the remote server. Here's how that's done:

- -
    -
  1. Run this command to see recent commits in your local clone: $ hg log -l 3
    2. -
- -

You should a list of the most recent commits, similar to this one:

- -
changeset:   0:7c543e8f3a6a
-tag:         tip
-user:        Your Name <email@example.com>
-date:        Mon Nov 23 18:08:25 2009 +0100
-summary:     Added search bar strings
-
- -
    -
  1. Now run the hg outgoing command to compare the local repository on your machine with the remote repository on hg.mozilla.org.
    2. -
- -

The hg outgoing command compares the two repositories and lists all changesets that are present locally, but not in the remote repository. These changesets will need to be pushed to the remote repository. The output will look something like this:

- -
comparing with ssh://hg.mozilla.org/releases/l10n-central/x-testing
-searching for changes
-
-changeset:   0:7c543e8f3a6a
-tag:         tip
-user:        Your Name <email@example.com>
-date:        Mon Nov 23 18:08:25 2009 +0100
-summary:     Added search bar strings
-
- -
    -
  1. Make sure this output is accurate before continuing.
    2. -
  2. Once you've made sure the outgoing output is accurate, push this changeset to hg.mozilla.org by running the hg push command.
    3. -
- -

Mercurial will connect to the remote repository, authenticate through SSH and send the changesets. The output should look something like this:

- -
pushing to ssh://hg.mozilla.org/releases/l10n-central/x-testing
-searching for changes
-adding changesets
-adding manifests
-adding file changes
-added 1 changesets with 2 changes to 2 files
-
- -

Congratulations! Your changeset has been successfully pushed to hg.mozilla.org! You can now visit http://hg.mozilla.org/releases/l10n-central/x-testing in your browser to see the new changeset in the remote repository.

- -

Resolução de problemas de SSH

- -

If pushing fails, make sure your ~/.ssh/config has the correct User set under the hg.mozilla.org host. This should be your Mozilla LDAP account name. Next, try issuing the following command: $ ssh hg.mozilla.org

- -

If SSH is working fine, you should see the following message:

- -
No interactive shells allowed here!
-Connection to hg.mozilla.org closed.
-
- -

If you don't see this message, try running the same command in a more verbose mode (with the debugging information): $ ssh -vvv hg.mozilla.org

- -

This should tell you why your connection is not succeeding. If you can't figure it out on your own, copy the output of the above command, paste it on http://pastebin.mozilla.org and ask in #l10n on the irc.mozilla.org server.

- -

Revisões técnicas e assinadas

- -

You've done some localization work and your ready for it to be released. The merge date for migrating from one product release channel to the next is rapidly approaching. You need to make sure that your work can effectively be compiled into a build for the next release channel. Do you know whether to ask for technical review of your work or a sign-off review? Do you know what what exactly is reviewed in each process? Technical and sign-off reviews apply to different localizations in different ways. Here's the basic difference between the two.

- - - - - - - - - - - - - - -
Revisão TécnicaRevisão Assinada
-
    -
  • Performed as a QA measure on a revision pushed to a new locale's L10n aurora repo in Mercurial.
    • -
  • Very comprehensive. Covers the entire product.
    • -
  • Focus is on technical accuracy and completion of L10n work; not translation quality.
    • -
  • Only performed on the first revision a new locale wants to have released to the public.
    • -
  • Must be approved prior to migrating your revision from one release channel to the next (e.g., Aurora to Beta).
    • -
- 		-
    -
  • Performed as a QA measure for maintaining a localization from release-to-release.
    • -
  • Only new L10n work is evaluated. This is done by generating a diff between the new release revision being considered and the previously approved release revision.
    • -
  • Focus is still on technical accuracy and completion of L10n work; not translation quality.
    • -
  • Release revisions are evaluated, not entire L10n repos.
    • -
  • Sign-offs do not need to be approved before revision merge between release channels, although it is recommended.
    • -
-
- -

There is a specific process to follow in Bugzilla for requesting these reviews:technical review.png

- -
    -
  1. File a bug requesting the review.
    2. -
  2. Attach your files to the bug. Once attached, open the attachment details.
    3. -
  3. In the attachment details, select the ? from the dropdown menu next to the review flag or the appropriate approval flags (see image). This will display a text box to assign the review to someone.
    4. -
  4. Enter :Pike as the Requestee.
    5. -
- -

We will perform a technical review of your work and provide you with feedback. We're happy to work with you to make sure that your work is fully functional.

- -

For more detailed information about reviews for new localizations and sign-offs for maintenance releases, visit the technical review and sign-off review pages.

- -

Tah dah!

- -

Mais uma vez, parabéns! Chegou ao final! Sinta-se à vontade para voltar a este tutorial sempre que necessário. Nós estamos felizes em o ter como um novo colaborador da Mozilla L10n e nós esperamos trabalhar de perto consigo.

- -

{{ Previous("Localization_Quick_Start_Guide/QA_phase") }}

diff --git "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_pr/index.html" "b/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_pr/index.html" deleted file mode 100644 index 48e5d343d5..0000000000 --- "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/fase_pr/index.html" +++ /dev/null @@ -1,212 +0,0 @@ ---- -title: Fase de PR -slug: Mozilla/Localization/Guia_iniciação_rápida/Fase_PR -tags: - - Localização -translation_of: Mozilla/Localization/Quick_start_guide/QA_phase ---- -

Depois de todo o trabalho duro de localização, nós temos a certeza de que não quer ver apenas o seu trabalho, mas quer ter a certeza de que está preciso! Se não tem muita experiência com código, pode até preocupar-se que tenha efetuado algo de errado (Ups!). Nós agora vamos orientá-lo na realização de alguns testes de garantia de qualidade no seu trabalho para garantir que esteja no caminho certo.

- -

If you're localizing Mozilla websites, your work will display soon after you've committed it without needing a language pack. Since such is the case, this part of the guide may not be entirely applicable to you. Feel free to skip ahead to the next section by clicking on the Next link at the bottom of the page.

- -

In order to see your work on Firefox (or another Mozilla application), you'll need to have a built language pack to install on your local instance.

- -

Criações automatizadas e manual

- -

With the click of a button, some L10n tools (like Narro and Koala) automatically create language pack builds for you. If you're using one of these tools, feel free to skip ahead to the Seeing your work section. If you're not using one of these tools, let's walk you through building your own language pack manually.

- -
Nota: Remember all of those pre-requisite tools we asked you to install in the initial setup? Here's where you'll need almost all of them. If you haven't installed them yet, now is the time to do it.
- -

Instruções preliminares

- -

We will be using the following file directories for this example:

- -
your working directory (root)/
-    mozilla-aurora (en-US source, pulled from http://hg.mozilla.org/releases/mozilla-aurora  )/
-    l10n-central (directory for L10n directories, one per L10n; often referred to as "l10n base")/
-       your-locale-code (a directory with your L10n files, in this example we'll use x-testing)
-
-Example: root/mozilla-aurora & root/l10n-central/x-testing
-
- -

Additionally, you will need to copy and translate the toolkit/defines.inc file directly from en-US before you can build. This is due to a bug in the build logic.

- -

Please either follow the above structure closely or adjust the commands below according to your custom setup.

- -

To copy this file to the appropriate directory, do the following:

- -
    -
  1. Navigate to your working directory from your command-line terminal (i.e., where you created the folder structure described above).
    2. -
  2. Enter the following commands:
    3. -
- -
mkdir -p l10n-central/x-testing/toolkit/
-
-cp mozilla-aurora/toolkit/locales/en-US/defines.inc l10n-central/x-testing/toolkit/defines.inc
-
- -

Tah-dah! Copied!

- -

Finally, you will need a file called .mozconfig to proceed with manual builds. This file contains the necessary build instructions.

- -

To create and configure this file, follow these instructions:

- -
-

Until the fix for bug 1063880 lands on mozilla-aurora and mozilla-beta when building language packs against those two trees you should:

- -
    -
  1. -

    remove ac_add_options --disable-compile-environment from .mozconfig in step 3

    -
    2. -
  2. -

    use ./mach build config after step 4

    -
    3. -
-
- -
    -
  1. Update the Mozilla source code:
    2. -
- -

$ cd mozilla-aurora
- $ hg pull -u

- -
    -
  1. Enter the following command to create the .mozconfig file: $ nano -w .mozconfig
    2. -
  2. Enter the following lines in your .mozconfig file:
    3. -
- -
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../firefox-build
-ac_add_options --disable-compile-environment
-ac_add_options --with-l10n-base=../l10n-central # path relative to MOZ_OBJDIR
-ac_add_options --enable-application=[browser or mail]
-
- -

You will need to specify which application you're localizing in the fourth line (e.g., for Firefox, that's browser, Thunderbird would be mail).

- -
    -
  1. Enter the following command to perform the configuration: $ ./mach configure
    2. -
  2. Once your command-line finishes spitting out the config command's output, navigate to the newly created directory: $ cd ../firefox-build/browser/locales
    3. -
- -

Now you're ready to build! At this point you can choose between two build options. You can either:

- - - -

Visit the links above to learn how to make these testing builds.

- -

Testar a sua L10n e ver o seu trabalho

- -

Now that you have your langpack or L10n repack, let's discuss seeing your work and testing it in the application.

- -

Testing the langpack will put you one step closer to having your localization added to the L10n releases. Follow the steps below to test your localization:

- -
    -
  1. Install Aurora in your preferred language.
    2. -
  2. Install the .xpi langpack you just created (or exported).
    3. -
  3. Set your language using the Quick Locale Switcher or Locale Switcher add-ons by navigating to Tools->Language->Your localization's language code.
    4. -
  4. Restart your browser and start testing!
    5. -
- -

Now you should be able to see all of your work up to this point. Click here for guidelines on how to test your localization.

- -

Não perca o seu trabalho!

- -

Your work is SO important! We would really hate to see you lose any of it. After you test your localization, you should send it to a remote repository, which will serve as a backup for your work and will let others follow your progress. We're going to go through the process below.

- -

The official localization teams use repositories at hg.mozilla.org. Before a team becomes official, we like to get the localizers comfortable with the Hg commands that allow for cloning, pulling, committing, and pushing work to an experimental repository.  We use a web service called Bit Bucket to start the learning process.

- -
Nota: You must have Mercurial configured before you begin. That step is back on the initial setup page. If you haven't done that yet, don't worry, we'll wait for you!
- -

Envio (Pushing) para o seu repositório

- -

There are a couple of things you should take note of before you push to your repository:

- - - -

The instructions below will help you learn how to use your Hg repository.

- -
    -
  1. After your new repository is created by the l10n-drivers, please visit the URL for your repo. We'll use x-testing here for our example. You can do this by entering the following URL into your browser: http://hg.mozilla.org/l10n-central/x-testing
    2. -
  2. Now, navigate to your locale's directory on your local machine.
    3. -
- -

If you're using Koala, this should be located at /path/to/your/koala.project/locale/3.6/x-testing, otherwise, it should be located at /path/to/your/working_dir/l10n_base/x-testing.

- -

In this directory, you should have an hg repository. You might have created it yourself by running hg init or hg clone or you might have had it created by Koala when you were setting up a new localization project. Also at this point, you shouldn't have any uncommitted changes (i.e., running the hg status command should show nothing). Let's see what the last revision in this repository is.

- -
    -
  1. Enter the following command: $ hg log -l 1
    2. -
- -

You should see an output similar to the one below:

- -
changeset:   0:7c543e8f3a6a
-tag:         tip
-user:        Your Name <email@example.com>
-date:        Mon Nov 23 18:08:25 2009 +0100
-summary:     Added search bar strings
-
- -
    -
  1. Now compare the local repository on your machine with the remote Hg repository by entering this command: $ hg outgoing http://hg.mozilla.org/l10n-central/x-testing
    2. -
- -

The hg outgoing command compares the two repositories and lists all changesets that are present locally, but not in the remote repository. These changesets will need to be "pushed" to the remote repository. You can expect to see output like this:

- -
comparing with http://hg.mozilla.org/l10n-central/x-testing
-searching for changes
-
-changeset:   0:7c543e8f3a6a
-tag:         tip
-user:        Your Name <email@example.com>
-date:        Mon Nov 23 18:08:25 2009 +0100
-summary:     Added search bar strings
-
- -
    -
  1. Let's now push this changeset. Enter the following command: hg push http://hg.mozilla.org/l10n-central/x-testing
    2. -
  2. Mercurial will connect to your repo and ask you to provide your account information (i.e., the username and the password).
    3. -
- -
real URL is http://hg.mozilla.org/l10n-central/x-testing
-pushing to http://hg.mozilla.org/l10n-central/x-testing
-searching for changes
-http authorization required
-realm: hg.mozilla.org HTTP
-user: your_id
-password:
-
- -

After you enter your account information, the changeset will be pushed.

- -
adding changesets
-adding manifests
-adding file changes
-added 1 changesets with 2 changes to 2 files
-bb/acl: your_id is allowed. accepted payload.
-quota: 979.7 KB in use, 150.0 MB available (0.64% used)
-
- -

Your changeset has been successfully pushed to your repository!

- -

As you begin to move through your translations, you should commit the changes locally and push your work to this experimental repository. For instance, if you have finished translating all the .dtd and .properties files in your x-testing/browser/chrome/browser/ directory, then you should run these commands:

- -
$ hg status
-$ hg commit -m "Translated browser/chrome/browser/"
-$ hg outgoing
-$ hg push http://hg.mozilla.org/l10n-central/x-testing
- -

Note that due to the distributed nature of Hg, hg commit saves the changes locally (i.e., in your computer's Hg repository). You can see the history of commits with hg log. After doing hg commit, you still need to send the changes to the remote repository. This is where hg push comes in. This sends your commits to the remote repository.

- -

Now you're ready to proceed to the release phase!

- -

 

- -

{{ PreviousNext("Localization_Quick_Start_Guide/Translation_phase", "Localization_Quick_Start_Guide/Release_phase") }}

diff --git "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/index.html" "b/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/index.html" deleted file mode 100644 index 7135cec329..0000000000 --- "a/files/pt-pt/mozilla/localization/guia_inicia\303\247\303\243o_r\303\241pida/index.html" +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Guia de Iniciação Rápida da Localização -slug: Mozilla/Localization/Guia_iniciação_rápida -tags: - - Guía - - Tradução -translation_of: Mozilla/Localization/Quick_start_guide ---- -

Bem-vindo à localização da Mozilla (abreviado em inglês L10n)!

- -

Se está aqui para iniciar a sua própria localização no projeto Mozilla ou para se juntar aos esforços de uma localização existente, veio ao lugar certo. Este guia é preenchido com todas as informações técnicas básicas que precisa para se envolver no programa Mozilla l10n. Nós iremos guiá-lo através dos passos para começar, desde a configuração inicial do ambiente até ao teste e lançamento da sua própria localização. Ao longo do caminho, irá aprender sobre a variedade de projetos para os quais pode contribuir e as ferramentas utilizadas para localizá-los.

- -

Quando alcamçamos exemplos específicos, nós iremos removê-los do projeto Firefox, já que é o projeto mais amplamente localizado dentro da Mozilla. Ao aproximar-se do final deste guia, poderá fazer uma alteração no Firefox na sua configuração local e, depois ver essa alteração na interface do Firefox. Para encerrar, quando terminar este guia, terá todas as ferramentas necessárias para começar a contribuir!

- -

Lembre-se, este guia irá instruí-lo apenas sobre os aspetos técnicos de L10n da Mozilla. Visite a página do Processo de L10n para saber mais sobre todo o processo.

- -
-

Configuração Inicial

-Preparação da tecnologia antes de localizar.
- -
-

Fase da tradução

-Tutoriais das ferramentas de L10n para tradução.
- -
-

Fase de PR

-Tutoriais de teste de L10n.
- -
-

Fase de Lançamento

-Passos para submeter o seu trabalho de tradução.
- -
Esses quatro estágios formam o lado técnico do programa de l10n. Para saber mais sobre qualquer um deles, clique em quaisquer das hiperligações acima. Para obter uma visão geral, nós sugerimos que comece com a bolha verde e mova de um estágio para outro.
- -

 

- -
Nota: este guia foi escrito para dois tipos de colaboradores: os que iniciam uma nova localização e os que se juntam a uma localização existente. É importante saber que informação se aplica ao tipo de colaborador. Para ajudá-lo a filtrar a informação mais aplicável, note que toda a informação que é única das que iniciam uma nova localização estarão com letra em cor de laranja. Toda a informação que é única para aqueles que se juntam a uma localização existente estará em letra azul.
- -

 

- -

{{ Next("Localization_Quick_Start_Guide/Initial_setup") }}

diff --git a/files/pt-pt/mozilla/localization/index.html b/files/pt-pt/mozilla/localization/index.html deleted file mode 100644 index 049ddf8e95..0000000000 --- a/files/pt-pt/mozilla/localization/index.html +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Localização na Mozilla -slug: Mozilla/Localization -tags: - - Landing - - Localização - - Mozilla - - Tradução - - l10n -translation_of: Mozilla/Localization ---- -

Localização (L10n) é o processo de tradução das interfaces do utilizador do software de um idioma para outro e a adaptação para o ajustar a uma cultura estrangeira. Estes recursos são para qualquer um com interesse nos aspetos técnicos involvidos na localização. Estes são para os responsáveis pelo desenvolvimento e todos os colaboradores.

- -

Consultar também

- -
-
Localizar MDN
-
Este recurso abrange a localização da documentação aqui na MDN.
-
Localização de aplicação
-
Este conjunto de documentos aplica-se mais especificamente à localização de aplicações, incluindo as aplicações do Firefox OS.
-
L10n
-
Documentos de referência para a API de L10n que a Mozilla utilzia para localizar o sistema operativo Firefox.
-
diff --git a/files/pt-pt/mozilla/localization/index/index.html b/files/pt-pt/mozilla/localization/index/index.html deleted file mode 100644 index 3b35d9f58b..0000000000 --- a/files/pt-pt/mozilla/localization/index/index.html +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Índex -slug: Mozilla/Localization/Index -tags: - - Localização - - Tradução -translation_of: Mozilla/Localization/Index ---- -

{{Index("/pt-PT/docs/Mozilla/Localization")}}

diff --git a/files/pt-pt/mozilla/localization/localizacao_e_plurais/index.html b/files/pt-pt/mozilla/localization/localizacao_e_plurais/index.html deleted file mode 100644 index 207f94128f..0000000000 --- a/files/pt-pt/mozilla/localization/localizacao_e_plurais/index.html +++ /dev/null @@ -1,384 +0,0 @@ ---- -title: Tradução e Plurais -slug: Mozilla/Localization/Localizacao_e_Plurais -tags: - - Internacionalização - - Localização - - Tradução -translation_of: Mozilla/Localization/Localization_and_Plurals ---- -

Provavelmente está aqui porque está a traduzir um ficheiro .properties e este tinha uma hiperligação para esta página. Esta página é para ajudar a explicar como localizar essas entradas de carateres para que a forma correta do plural seja mostrada ao utilizador. Por exemplo, "1 página" vs. "2 páginas".

- -

Se está aqui para criar o seu código (por exemplo, extensões) localizável para as formas de plural, pode ir diretamente para Programar com PluralForm. Também poderá ter que localizar as entradas iniciais para o seu código, por isso também seria bom que lê-se pelo menos a secção 'Utilização'.

- -

Utilização

- -

Aqui tem alguns termos utilizados nesta página para o ajudar a manter as coisas simples:

- - - -

If you're here for pluralRule in the chrome/global/intl.properties file, you'll need to figure out what plural rule to choose for your localization. This plural rule is used to determine how many plural forms are needed for each word that needs to be localized, with plurals in mind.

- -

For all other properties files that link to this page, you'll need to provide enough plural forms of the desired word, and separate them with semi-colons (;). If you don't know how many plural forms you need, check the pluralRule number in chrome/global/intl.properties, and look up the corresponding entry in the following list of plural rules.

- -

Lista das Regras de Plural

- -

Esta secção contém uma lista de regras plurais ordenadas pelo seu número de regra de plural. Cada entrada indica quantas formas de plural são necessárias ao localizar uma palavra. Para cada entrada, há uma lista de famílias e idiomas nessas famílias, para ajudá-lo a descobrir se é a regra que deve escolher para pluralRule. Além disso, há uma breve descrição de cada forma de plural, seguida por alguns números de amostra que se enquadram nessa forma específica.

- -

For a given plural rule, the order in which the plural forms are listed is the same order you need to localize a word, separated by semi-colons. For example, English uses plural rule 1, and localizing plurals would require a string of "plural;plurals" where the first word is the singular form and the second is the general plural form.

- -

Regra de plural #0 (1 forma)

- -

Famílias: Asiáticas (chinês, japonês, coreano), persa, turco/altaico (turco), Thai, Lao
- tudo: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, …

- -

Regra de plural #1 (2 formas)

- -

Famílias: Germânico (dinarmaquês, holandês, inglês, Faroese, Frisian, alemão, norueguês, sueco ), Finno-Ugric (Estonian, Finnish, Hungarian), Language isolate (Basque), Latin/Greek (Greek), Semitic (Hebrew), Românico (italiano, português, espanhol, catalão), e vietnamita
- é 1: 1
- tudo o resto: 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, …

- -

Regra de plural #2 (2 formas)

- -

Famílias: Românico (francês, português (Brasil)), Lingala
- é 0 ou 1: 0, 1
- tudo o resto: 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, …

- -

Regra de plural #3 (3 formas)

- -

Famílias: Baltic (Latvian, Latgalian)
- termina em 0: 0
- termina em 1, excluindo 11: 1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …
- tudo o resto: 2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13, 14, 15, 16, 17, 18, 19, 22, 23, 24, 25, 26, 27, 28, 29, 32, 33, 34, 35, 36, 37, 38, 39, 42, 43, 44, 45, 46, 47, 48, 49, 52, 53, …

- -

Regra de plural #4 (4 formas)

- -

Famílias: Celtic (Scottish Gaelic)
- é 1 ou 11: 1, 11
- é 2 ou 12: 2, 12
- is 3-10 ou 13-19: 3, 4, 5, 6, 7, 8, 9, 10, 13, 14, 15, 16, 17, 18, 19
- tudo o resto: 0, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, …

- -

Regra de plural #5 (3 formas)

- -

Famílias: Romanic (Romanian)
- é 1: 1
- é 0 ou termina em 01-19, excluindo 1: 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, …
- tudo o resto: 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, …

- -

Regra de plural #6 (3 formas)

- -

Famílias: Baltic (Lithuanian)
- termina em 1, excluindo 11: 1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …
- termina em 0 ou termina em 11-19: 0, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 130, 140, 150, 160, 170, 180, 190, 200, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, …
- tudo o resto: 2, 3, 4, 5, 6, 7, 8, 9, 22, 23, 24, 25, 26, 27, 28, 29, 32, 33, 34, 35, 36, 37, 38, 39, 42, 43, 44, 45, 46, 47, 48, 49, 52, 53, 54, 55, 56, 57, 58, 59, 62, 63, 64, 65, 66, 67, 68, 69, 72, 73, …

- -

Regra de plural #7 (3 formas)

- -

Famílias: Belarusian, Russian, Ukrainian
- termina em 1, excluindo 11: 1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …
- termina em 2-4, excluindo 12-14: 2, 3, 4, 22, 23, 24, 32, 33, 34, 42, 43, 44, 52, 53, 54, 62, 63, 64, 72, 73, 74, 82, 83, 84, 92, 93, 94, 102, 103, 104, 122, 123, 124, 132, 133, 134, 142, 143, 144, 152, 153, 154, 162, 163, 164, 172, 173, 174, 182, 183, …
- tudo o resto: 0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 25, 26, 27, 28, 29, 30, 35, 36, 37, 38, 39, 40, 45, 46, 47, 48, 49, 50, 55, 56, 57, 58, 59, 60, 65, 66, 67, 68, 69, 70, 75, 76, 77, …, 112, 113, ..., 212, 213, ...

- -

Regra de plural #8 (3 formas)

- -

Famílias: Eslavo (eslovaco, checo)
- é 1: 1
- é 2-4: 2, 3, 4
- tudo o resto: 0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, …

- -

Regra de plural #9 (3 formas)

- -

Famílias: Eslavo (polaco)
- é 1: 1
- termina em 2-4, excluindo 12-14: 2, 3, 4, 22, 23, 24, 32, 33, 34, 42, 43, 44, 52, 53, 54, 62, 63, 64, 72, 73, 74, 82, 83, 84, 92, 93, 94, 102, 103, 104, 122, 123, 124, 132, 133, 134, 142, 143, 144, 152, 153, 154, 162, 163, 164, 172, 173, 174, 182, 183, …
- tudo o resto: 0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 25, 26, 27, 28, 29, 30, 31, 35, 36, 37, 38, 39, 40, 41, 45, 46, 47, 48, 49, 50, 51, 55, 56, 57, 58, 59, 60, 61, 65, 66, 67, 68, …

- -

Plural rule #10 (4 forms)

- -

Famílias: Eslavo (esloveno, sérbio)
- termina em 01: 1, 101, 201, …
- termina em 02: 2, 102, 202, …
- termina em 03-04: 3, 4, 103, 104, 203, 204, …
- tudo o resto: 0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, …

- -

Plural rule #11 (5 forms)

- -

Famílias: Celtic (Irish Gaelic)
- é 1: 1
- é 2: 2
- is 3-6: 3, 4, 5, 6
- is 7-10: 7, 8, 9, 10
- tudo o resto: 0, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, …

- -

Plural rule #12 (6 forms)

- -

Famílias: Semitic (Arabic)
- é 1: 1
- é 2: 2
- termina em 03-10: 3, 4, 5, 6, 7, 8, 9, 10, 103, 104, 105, 106, 107, 108, 109, 110, 203, 204, 205, 206, 207, 208, 209, 210, …
- tudo o resto but é 0 and termina em 00-02, excluding 0-2: 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, …
- termina em 00-02, excluding 0-2: 100, 101, 102, 200, 201, 202, …
- é 0: 0

- -

Plural rule #13 (4 forms)

- -

Famílias: Semitic (Maltese)
- é 1: 1
- é 0 ou termina em 01-10, excluindo 1: 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, …
- termina em 11-19: 11, 12, 13, 14, 15, 16, 17, 18, 19, 111, 112, 113, 114, 115, 116, 117, 118, 119, 211, 212, 213, 214, 215, 216, 217, 218, 219, …
- tudo o resto: 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, …

- -

Plural rule #14 (3 forms)

- -

Famílias: unused
- ends in 1: 1, 11, 21, 31, 41, 51, 61, 71, 81, 91, 101, 111, 121, 131, 141, 151, 161, 171, 181, 191, 201, 211, 221, 231, 241, 251, 261, 271, 281, 291, …
- ends in 2: 2, 12, 22, 32, 42, 52, 62, 72, 82, 92, 102, 112, 122, 132, 142, 152, 162, 172, 182, 192, 202, 212, 222, 232, 242, 252, 262, 272, 282, 292, …
- tudo o resto: 0, 3, 4, 5, 6, 7, 8, 9, 10, 13, 14, 15, 16, 17, 18, 19, 20, 23, 24, 25, 26, 27, 28, 29, 30, 33, 34, 35, 36, 37, 38, 39, 40, 43, 44, 45, 46, 47, 48, 49, 50, 53, 54, 55, 56, 57, 58, 59, 60, 63, …

- -

Plural rule #15 (2 forms)

- -

Famílias: Icelandic, Macedonian
- termina em 1, excluindo 11: 1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …
- tudo o resto: 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 42, 43, 44, 45, 46, 47, 48, 49, 50, 52, 53, 54, …

- -

Plural rule #16 (5 forms)

- -

Famílias: Celtic (Breton)
- termina em 1, excluindo 11, 71, 91: 21, 31, 41, 51, 61, 81, 101, 121, 131, 141, 151, 161, 181, 201, 221, 231, 241, 251, 261, 281, ...
- ends in 2, excluindo 12, 72, 92: 2, 22, 32, 42, 52, 62, 82, 102, 122, 132, 142, 152, 162, 182, 202, 222, 232, 242, 252, 262, 282, ...
- ends in 3, 4 or 9 excluindo 13, 14, 19, 73, 74, 79, 93, 94, 99: 3, 4, 9, 23, 24, 29, 33, 34, 39, 43, 44, 49, 53, 54, 59, ...
- termina em 1000000: 1000000: 1000000, 2000000, 3000000, 4000000, 5000000, 6000000, 7000000, 8000000, 9000000, 10000000, ...
- tudo o resto: 0, 5, 6, 7, 8, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 25, 26, 27, 28, 30, 35, 36, 37, 38, 40, ...

- -

Plural rule #17 (2 forms)

- -

Famílias: Ecuador indigenous languages (Shuar)
- é 0: 0
- tudo o resto: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, …

- -

Plural rule #18 (6 forms)

- -

Famílias: Welsh
- é 0: 0
- é 1: 1
- é 2: 2
- is 3: 3
- é 6: 6
- tudo o resto: 4, 5, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, …

- -

Plural rule #19 (3 forms)

- -

Famílias: Slavic (bósnio, croata, sérvio)
- termina em 1, excluindo 11: 1, 21, 31, 41, 51, 61, 71, 81, 91, 101, 121, 131, 141, 151, 161, 171, 181, 191, 201, 221, 231, 241, 251, 261, 271, 281, 291, …
- termina em 2-4, excluindo 12-14: 2, 3, 4, 22, 23, 24, 32, 33, 34, 42, 43, 44, 52, 53, 54, 62, 63, 64, 72, 73, 74, 82, 83, 84, 92, 93, 94, 102, 103, 104, 122, 123, 124, 132, 133, 134, 142, 143, 144, 152, 153, 154, 162, 163, 164, 172, 173, 174, 182, 183, …
- tudo o resto: 0, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 25, 26, 27, 28, 29, 30, 35, 36, 37, 38, 39, 40, 45, 46, 47, 48, 49, 50, 55, 56, 57, 58, 59, 60, 65, 66, 67, 68, 69, 70, 75, 76, 77, …, 112, 113, ..., 212, 213, ...

- -

Exemplos

- -

A seguir tem alguns exemplos para vários idiomas e um breve processo de reflexão.

- -

Francês

- -

Some French speaking places treat 0 as plural while others treat it as singular. The only other singular é 1 while tudo o resto is plural. So pick either plural rule #1 or #2.

- -

pluralRule=2
- seconds=seconde;secondes
- minutes=minute;minutes
- hours=heure;heures
- days=jour;jours

- -

Like many other times when localizing words, gender agreement might force you to rearrange words in a way that the gender is always the same. (seconde vs jour)

- -

Chinês

- -

A word doesn't change if there is a different number in front of it, so all numbers use the same plural form. With just one plural form, it has to be plural rule #0. For each word to localize, it's just like localizing a single word with no semi-colons needed.

- -

pluralRule=0
- seconds=秒
- minutes=分
- hours=時
- days=日

- -

Polaco

- -

There's a singular form fou 1, a plural form for 2-4, and another for 5-21 at which point 22 is the same as 2. Plural rule #7 has a "termina em 2-4, not 12-14" but the singular form includes everything ending in 1 except 11. Plural rule #9 has the correct singular form for only 1.

- -

pluralRule=9
- seconds=sekunda;sekundy;sekund
- minutes=minuta;minuty;minut
- hours=godzina;godziny;godzin
- days=dzień;dni;dni

- -

Even though the last 2 plural forms of "day" are the same, both are still needed, because there needs to be 3 plural forms for each word.

- -

Sérbio

- -

There are 4 plural forms: nominative singular, nominative dual, nominative plural, genitive plural. These match up with plural rule #10.

- -

pluralRule=10
- seconds=sekunda;sekundźe;sekundy;sekundow
- minutes=mjeńšina;mjeńšinje;mjeńšiny;mjeńšin
- hours=hodźina;hodźinje;hodźiny;hodźin
- days=dźeń;dnjej;dny;dnjow

- -

Extensão de Teste

- -

Para ajudar a ter a certeza de que escolhe a regra de plural correta e fornecer formas de plural suficientes para as sequências de carateres, deveria utilizar a extensão "pluralForm Checker". Depois de instalar a extensão, esta deverá estar disponível no menu de "Ferramentas".

- -

To use it, list off the property files and properties that you want to check and click the button. The extension will load each property and display the plural forms in a table. Selecting a table entry will populate the bottom box with sample uses of the word for some numbers.

- -

Image:pluralForm-checker.0.3.png

- -

Instalar a extensão Checker v0.3 de pluralForm

- -

Entrada de extensão

- -

Seria bom manter esta lista atualizada com todas as palavras que precisam de formas plurais. As pessoas que utilizam a extensão podem copiar/colar esta entrada.

- -

chrome://mozapps/locale/downloads/do...tes,hours,days
- chrome://mozapps/locale/downloads/do...dsTitlePercent
- chrome://browser/locale/browser.prop...ausedDownloads

- -

Histórico de versão

- -

0.1: Initial version with pluralRule check, properties input loading, table generation, sample output display
- 0.2: Use PluralForm.numForms() to get the number of forms instead of figuring out locally to better support future rules - Requires build from 2007/01/27 or later
- 0.3: Generate a list of what numbers fall into which plural form to minimize the sample output to at most 3 of each form

- -

Programar com PluralForm

- -

The functionality for getting the correct plural forms is provided by a JavaScript Module, PluralForm.jsm. This module provides a couple methods for localizing to the browser's current locale as well as getting methods to localize to a desired plural rule. The latter ability of specifying a plural rule is useful for extensions because the extension doesn't necessarily have to be localized to the browser's locale.

- -

Carregar PluralForm.jsm

- -

Loading the PluralForm module from JavaScript is simple with Components.utils.import. Just put the following line somewhere that will be evaluated before you want to use PluralForm. At the top of your JavaScript file is fine.

- -
Components.utils.import("resource://gre/modules/PluralForm.jsm");
- -

Métodos: get

- -

Estes métodos utilizam o idioma atual do navegador especificado pelo valor chrome://global/locale/intl.properties's pluralRule.

- -
/**
- * Get the correct plural form of a word based on the number
- *
- * @param aNum
- *        The number to decide which plural form to use
- * @param aWords
- *        A semi-colon (;) separated string of words to pick the plural form
- * @return The appropriate plural form of the word
- */
-string pluralForm
-get(int aNum, string aWords)
- -

Aqui tem um exemplo de utilização deste método:

- -
// Load PluralForm and for this example, assume English
-Components.utils.import("resource://gre/modules/PluralForm.jsm");
-
-// PluralForm.get expects a semi-colon separated list of words
-let downloads = "download;downloads";
-// Pretend this number came from somewhere else
-let num = 10;
-
-// Display the correct plural form fou 10 downloads: "You have 10 downloads.")
-print("You have " + num + " " + PluralForm.get(num, downloads) + ".");
-
-// Try again with a different value: "You have 1 download."
-num = 1;
-print("You have " + num + " " + PluralForm.get(num, downloads) + ".")
- -

The above example works, but is still difficult to localize, because we're concatenating strings assuming a particular grammatical structure. The following would be better:

- -
Components.utils.import("resource://gre/modules/PluralForm.jsm");
-
-let downloads = "You have one download.;You have #1 downloads.";
-let num = 10;
-
-// For English, this would display "You have 10 downloads."
-print(PluralForm.get(num, downloads).replace("#1", num);
- -

Notice in the above example that the code can be written to support placeholders or not use placeholders in some forms of the string. Additionally, the localizer has control over where the placeholder is, in relation to the rest of the text.

- -

Of course, the strings to be localized will be placed in a separate file, such as yourextension.properties, instead of being hardcoded in the JavaScript code file.

- -

The following 3 file snippets show how to use PluralForm with your .xul, .properties, .js files.

- -

downloads.xul:

- -
<stringbundleset>
-  <stringbundle id="strings" src="chrome://downloads.properties"/>
-</stringbundleset>
- -

downloads.properties:

- -
# LOCALIZATION NOTE (downloadsTitleFiles): Semi-colon list of plural forms.
-# See: https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals
-# #1 number of files
-# example: 111 files - Downloads
-downloadsTitleFiles=#1 file - Downloads;#1 files - Downloads
-
-# LOCALIZATION NOTE (timePair): #1 time number; #2 time unit
-# example: 1 second; 11 seconds
-timePair=#1 #2
-seconds=second;seconds
-minutes=minute;minutes
-hours=hour;hours
-
- -

downloads.js:

- -
Components.utils.import("resource://gre/modules/PluralForm.jsm");
-let getStr = function(string) document.getElementById("strings").getString(string);
-
-// Get the correct plural form for the title
-let numDownloads = 3;
-let title = PluralForm.get(numDownloads, getStr("downloadsTitleFiles"));
-// Put in the correct number of downloads
-print(title.replace("#1", numDownloads));
-
-// Get the correct plural form of seconds
-let timeLeft = 55;
-let seconds = PluralForm.get(timeLeft, getStr("seconds"));
-// Print the localized string for "55 seconds"
-print(getStr("timePair").replace("#1", timeLeft).replace("#2", seconds));
- -

Método: makeGetter

- -

If you're writing an extension, you'll want to use makeGetter instead of PluralForm.get() or PluralForm.numForms(). This is because someone installing the extension on a different locale will be using the strings provided by your default extension locale. For example, your extension localized for English with plural rule #1, which expects 2 plural forms, is installed on a localized version of Firefox with plural rule #4, which expects 3 forms:

- -
/**
- * Create a pair of plural form functions for the given plural rule number.
- *
- * @param aRuleNum
- *        The plural rule number to create functions
- * @return A pair: [function that gets the right plural form,
- *                  function that returns the number of plural forms]
- */
-[string pluralForm get(int aNum, string aWords), int numForms numForms()]
-makeGetter(int aRuleNum)
- -

Aqui tem um exemplo de utilização de makeGetter:

- -
Components.utils.import("resource://gre/modules/PluralForm.jsm");
-
-// Let's get Irish (plural rule #11)
-let [get, numForms] = PluralForm.makeGetter(11);
-
-// Make up some values to use with "get"
-let dummyText = "form 1;form 2;form 3;form 4;form 5";
-let dummyNum = 10;
-
-// In the case of Irish, the value 10 uses plural form #4, so "form 4" is printed
-print(get(dummyNum, dummyText));
- -

In this example, the Irish plural rule was hardcoded, but this could be a value specified in the .properties file. So for your extension, specify a pluralRule value in the .properties, and call PluralForm.makeGetter(pluralRuleFromProperties), making sure to save the 2 returned functions. (You can use destructured assignment in JavaScript 1.7 to keep things clean.) The returned functions act just like PluralForm.get() and PluralForm.numForms(), except for the specified plural rule instead of the default plural rule.

- -

Créditos

- -

Inicialmente, o código da "Forma de Plural" foi implementado por {{ Bug(394516) }} - Figure out a remaining-time rounding scheme for minutes -> hours/days
- As regras de plural e as familias derivadas da documentação gettext da GNU.

diff --git a/files/pt-pt/mozilla/localization/localizar_com_mercurial/index.html b/files/pt-pt/mozilla/localization/localizar_com_mercurial/index.html deleted file mode 100644 index de4a09643f..0000000000 --- a/files/pt-pt/mozilla/localization/localizar_com_mercurial/index.html +++ /dev/null @@ -1,256 +0,0 @@ ---- -title: Localizar com Mercurial -slug: Mozilla/Localization/Localizar_com_Mercurial -tags: - - Documentação de criação - - Internacionalização - - Localização - - Tradução -translation_of: Mozilla/Localization/Localizing_with_Mercurial ---- -

In Mozilla, we use the the Mercurial version control system (Hg) to manage our source code and localizations. Mercurial allows localizers to work locally (on their machines) and then push (an Hg term) changes to a remote repository, which usually is hosted on the Mozilla servers (hg.mozilla.org). Localizing current versions of Firefox, Thunderbird and SeaMonkey includes working with Mercurial. If the documentation is incomplete or you have questions, please drop by the #l10n or #hg channels on irc.mozilla.org. The Mercurial FAQ are also worth a read, should you run into trouble.

- -

For the eager and quick, below you'll find instructions on installing and configuring Mercurial, instructions on receiving an Hg account commit priviledges, as well as a few tasks you can complete without account priviledges.

- -

Instalar Mercurial

- -

Follow the instructions below to install Mercurial on your system. Once you've installed Mercurial, we'll walk through the steps to configure it.

- -

Mercurial no Linux

- -

You can easily install Mercurial from the command line by issuing one of the following commands. Choose the appropriate command for your distribution and make sure to run as root.

- -
# Debian/ubuntu
-$ apt-get install mercurial
-
-# Fedora
-$ yum install mercurial
-
-# Gentoo
-$ emerge mercurial
-
-# Arch Linux
-$ pacman -S mercurial
-
-# OpenSolaris
-$ pkg install SUNWmercurial
-
- -

Se preferir uma interface gráfica, pode transferir e instalar o MercurialEclips e aqui.

- -

Este funcionou?

- -

Open a Terminal window and enter hg --version. If you see a message about the version of Mercurial (e.g. Mercurial Distributed SCM (version 1.3.1)), you have installed Mercurial successfully!

- -

Mais detalhes

- -

For more details on installing Hg on Linux systems, refer to the instructions on Mercurial's Download page.

- -

Mercurial no Windows

- -

With Windows, you have a couple of install options:

- - - -

Mercurial Installer.pngPart of the command line Hg install for Windows involves making sure the hg executable is in the system's %PATH% variable (TortoiseHg doesn't need this step). Use the add_path.exe utility found in C:\mozilla-build\hg to do this.

- -
PS C:\Users\your_id> cd C:\mozilla-build\hg
-PS C:\mozilla-build\hg> .\add_path.exe /result .
-
- -

Note the dot (".") at the end of the second command, which means the current directory. If the utility modified your %PATH% successfully, a dialog will open saying, "%PATH% has been updated correctly."

- -

Alternatively, you can edit the %PATH% variable manually. In order to do so, right-click on your computer icon, choose Properties > Advanced > Environmental Variables, select PATH and click Edit. If you don't see PATH among the options, you'll have to click Add and edit it within the Add dialog. See the screenshot for an example.PATH.jpg

- -

Este funcionou?

- -
    -
  1. Go to Start > Run...
    2. -
  2. Type cmd.exe and click OK. A new shell window should appear. 
    3. -
  3. Type hg --version in the new shell window. If you see a message about the version of Mercurial (e.g. Mercurial Distributed SCM (version 1.3.1)), you have installed Mercurial successfully!
    4. -
- -

Mais detalhes

- -

For more details on installing Hg on Windows, refer to the instructions on Mercurial's Download page.

- -

Mercurial no Mac OSX

- -

Installing Hg on Mac OSX is super easy. You can install Mercurial via MacPorts through the Terminal, like so:

- -

$ sudo port install mercurial

- -

You can also install it by downloading the dmg package from the Hg download page. It has an install dialog that will walk you through the process.

- -

If you prefer a graphical interface, you can download and install MercurialEclipse here.

- -

Este funcionou?

- -

Open a Terminal window and type hg --version. If you see a message about the version of Mercurial (e.g. Mercurial Distributed SCM (version 1.3.1)), you have installed Mercurial successfully!

- -

Mais detalhes

- -

For more details on installing Hg on Mac OSX, refer to the instructions on Mercurial's Download page.

- -

Configurar o Mercurial

- -

Once you've installed Mercurial, you'll need to configure it before you can use it successfully.

- -

Your Mercurial configuration is contained within a config file which you must create yourself. Your config file is called either ~/.hgrc (UNIX systems) or Mercurial.ini (Windows), depending on your operating system.

- -

Your config file should have the following settings:

- -
[ui]
-username = Your Real Name <user@example.com>
-merge = internal:merge
-
-[defaults]
-commit = -v
-
-[diff]
-git = 1
-showfunc = 1
-unified = 8
- -

To configure Hg, follow these steps:

- -
    -
  1. Create a new file in your favorite text editor.
    2. -
  2. Copy the settings above and paste them into your new file.
    3. -
  3. Save the file as either .hgrc (UNIX systems) or Mercurial.ini (Windows) and save it in either $HOME/ or C:\mozilla-build\hg\ or C:\Program Files\Mercurial\.
    4. -
- -

Now that you've installed and configured Mercurial, here are a few tasks you can do without Hg commit access priviledges.

- -

Clonar e atualizar os repositórios

- -

There are a couple of repostiories that contain en-US source files that most locales will want to deal with.

- - - -
-

When you get the comm-central repository, this will include the mozilla-central repository as well. You can therefore use the one set up for developing Firefox, SeaMonkey and Thunderbird without having to pull mozilla-central a second time.

-
- -

Here's how to get (or clone) your en-US source files for the first time:

- - - -
hg clone https://hg.mozilla.org/mozilla-central/
-
- -

This will create a clone of the mozilla-central repository in the directory mozilla-central.

- - - -
hg clone https://hg.mozilla.org/comm-central/
-cd comm-central
-python client.py checkout
-
- -

The first command will create a clone of the comm-central repository. The second command will move you into that directory. The third command will do a clone of mozilla-central, and pull some other hg repositories. The other directories are required for SeaMonkey and Thunderbird.

- - - -
hg clone https://hg.mozilla.org/l10n-central/ab-CD/
- -

Atualizar os seus repositórios locais

- - - -
hg pull -u
-
- -

This will both get new changesets from mozilla-central and apply those changes in your working copy.

- - - -
python client.py checkout
- -

This will both get new changesets from comm-central, mozilla-central and the other appropriate locations and apply those changes in your working copy.

- - - -
hg pull -u
- -

Criar correções (patches) de L10n

- -

Another thing you can do with Hg without needing account priviledges is creating L10n patches of your work for someone else to commit to your remote L10n repo on the Mozilla servers. Doing this ensures that your dashboards are always accurate, as they look at your remote repo.

- -

Here's how to create a L10n patch with Hg and the Mq extension:

- -
    -
  1. Enable Mq by adding hg.ext =  to your Mercurial config file (~/.hgrc on Unix-like systems or Mercurial.ini on Windows) under the [extensions] section.
    2. -
  2. Open your command line tool and navigate to your L10n directory.
    3. -
  3. Inside your L10n directory, init your repo with Mq by running hg init --mq.
    4. -
  4. To create a new patch, run hg qnew -m "Your commit message" patch-name.patch. The commit message should take the form of "Bug 123456 - Change this thing to work better by doing something; r=reviewers" if you are to fix a bug.
    5. -
  5. Make your change.
    6. -
  6. Once you finish making your change, run hg qrefresh to commit your changes to the patch.
    7. -
  7. Navigate to your <repository>/.hg/patches to find your .patch.
    8. -
  8. You may repeat from step 4 to create another patch. Your patches will be incremental, i.e. new patches are created based on old patches. If you want to commit all the patches to the repository and cleanup the patch queue, run hg qfinish.
    9. -
- -

Please refer to MqTutorial and Mq documentation for further uses of Mq extension to manage patches.

- -

Privilégios da Conta Mercurial

- -

Eventually, you or your team leader will need Hg account priviledges. Let's face it, it's just more convenient to commit and push your work to the remote repo yourself, rather than creating patches and asking someone else to push them for you.

- -

To get write access to the l10n hg repositories on the Mozilla server, there's a bit of paper work to be done. The localization team owner needs to file a bug requesting an hg account. This bug will request level 1 L10n priviledges. You need to follow the instructions regarding the contributor form. Write access to the hg repositories requires a ''voucher'', which, for the owner, will be done based on the review by Mozilla. For peers of a localization, the owner can vouch (once she or he is registered).

- -

Enviar alterações para a Mozilla

- -

Now that you have Hg account privileges, you can send your work to Mozilla all by yourself. Here are the steps to send your L10n work using Mercurial:

- -
    -
  1. Since your L10n work takes place in your own local repository, you should ensure that there are no changes made to the remote repository before committing your work. To do this, update your locale, as per the section above.
    2. -
  2. After finishing a change or set of changes and checking you have updated to the latest, you should commit by entering this command:
    3. -
- -
hg commit -m "your message identifying the change (bug 555)"
- -

Committing won’t send your changes to Mozilla’s repository, but prepares them for it. The next step will send your changes to your remote repo via push.

- -
    -
  1. To push to mozilla-hosted repositories, you have to have committer access, and you must edit the file (your-local-hg-root AKA the directory you pulled your locale into)/.hg/hgrc (note, this is NOT your ~/.hgrc) to add these lines (replacing ab-CD with your locale code):
    2. -
- -
[paths]
-default = https://hg.mozilla.org/l10n-central/ab-CD/
-default-push = ssh://hg.mozilla.org/l10n-central/ab-CD/
-
- -
    -
  1. You’ll also need to tell ssh which account to use for your pushes, too, by editing ~/.ssh/config and adding these lines, where user@host.domain is your account:
    2. -
- -
Host hg.mozilla.org
-User user@host.domain
-
- -
    -
  1. Now you can push your work to the repository (and check the result on the dashboard) by entering this command from your local directory:
    2. -
- -
hg push
- -

And tah dah! You're done! Congratulations on finishing the tutorial. Take a break and grab a snack, you deserve it

diff --git "a/files/pt-pt/mozilla/localization/localiza\303\247\303\243o_com_pontoon/index.html" "b/files/pt-pt/mozilla/localization/localiza\303\247\303\243o_com_pontoon/index.html" deleted file mode 100644 index 05fa58b1d6..0000000000 --- "a/files/pt-pt/mozilla/localization/localiza\303\247\303\243o_com_pontoon/index.html" +++ /dev/null @@ -1,138 +0,0 @@ ---- -title: Traduzir com Pontoon -slug: Mozilla/Localization/Localização_com_Pontoon -tags: - - Localização - - Tradução -translation_of: Mozilla/Localization/Localizing_with_Pontoon ---- -

Pontoon é uma ferramenta de localização (l10n), O-Que-Vê-É-O-Que-Obtém (WYSIWYG) baseada na Web. Na Mozilla, nós utilizamos o Pontoon para localizar todos os produtos e sites da Web da Mozilla, desde o Firefox até Mozilla.org. Pontoon é uma ferramenta muito simples e intuitiva que requer poucos conhecimentos técnicos para utilizar no ritmo de trabalho de l10n. Aqui, nós iremos discutir como utilizar o Pontoon para localizar projetos, desde o primeiro início de sessão até concluir as suas contribuições. Ao longo do caminho, nós iremos sugerir algumas funcionalidades que irão tornar mais eficiente e facilitar as suas contribuições no seu l10n.

- -
-

É um programador? Leia sobre a implementação do Pontoon no seu projeto ou saiba como participar no GitHub.

-
- -

Primeiros passos

- -

Pontoon's home page is very easy to use. To begin localizing the project, click on the Persona icon and sign in. Next, simply select the project you want to work on and your locale from the dropdown menus. Pontoon will automatically open that locale's project for you to get started. Note that for our purposes here, we'll be using Firefox Affiliates website to demo Pontoon's functionality and workflow. And there it is, opened inside Pontoon:

- -

Browser app and workspace

- -

Barra de ferramentas principal

- -

As you can see, most of the interface is taken by the website being translated. Only the toolbar on top belongs to Pontoon, containing the following items (from left to right):

- -

Main toolbar

- -

Lista de textos

- -

Opens a sidebar with a list of all strings to localize.

- -

Seletor de projeto (Afiliados)

- -

Switches between projects to localize.

- -

Seletor de recursos (Página Inicial)

- -

Switches between project resources to localize, like subpages or localization files. Hidden if no resources available for project.

- -

- -
-
- -

Seletor de idioma (Esloveno)

- -

Switches between languages to localize.

- -

Ir

- -

Opens project-resource-locale selection.

- -

Indicado do progresso

- -

Displays your progress on the resource being localized. More details are available in the popup.

- -
-
- - - -

Allows for user-specific tasks, like commiting to repository, downloading files and signing out.

- - - -

Gives important information, like the anticipated project timeline and a list of keyboard shortcuts.

- -
-
- -

Alright, how about we do some translating now?

- -
-
- -

Traduzir texto

- -

When using Pontoon for localization, you have a couple of options to translate your strings. You can translate in-context, out-of-context, or a combination of the two. We'll start with looking at in-context translation.

- -

In-context

- -

Pontoon's in-context translation mode is what puts it above others. It opens a web page (or web app) and enables real-time editing of that page. Here's how you translate your first string:

- -

In-context localization

- -
    -
  1. Hover over the text you want to translate with your mouse.
    2. -
  2. An edit button appears over that text. Click on it to enable the translate mode.
    3. -
  3. Replace the original text with its translation into your language.
    4. -
  4. Click the save button to save your translation.
    5. -
- -
-

Out-of-context

- -

Some strings are impossible to translate in-context, e.g. the contents of the <title> tag in websites and strings with placeables or different plural forms. By clicking on the hamburger icon in the main toolbar, a list of all strings and available translations will open in the sidebar. You can also use the sidebar for out-of-context localization:

- -

Out-of-context localization: list Out-of-context localization: translate

- -
    -
  1. Click on the string you'd like to translate.
    2. -
  2. Translation panel with original string and its details (e.g. comments) opens.
    3. -
  3. Translate the string in the translation area below.
    4. -
  4. Click the save button to save your translation.
    5. -
- -

As you translate strings out-of-context, translations will also appear in website, if they could also be translated in-context.

- -

Ajudas de tradução

-
- -

As you can see, suggestions from history, translation memory, machine translation and other locales are also available in the out-of-context translation panel. We call all of these translation helpers and here's how each of them will help you as you translate strings:

- -

Translation helpers: History Translation helpers: Machinery Translation helpers: Other locales Translation helpers: Search

- -

Histórico

- -

Displays previously suggested translations, including from other users.

- -

Máquina

- -

Displays matches from various services: internal translation memory, Mozilla Transvision, open source translation memory, Microsoft terminology and machine translation.

- -

Outros idiomas

- -

Displays matching translations from other locales.

- -

Pesquisar

- -

Almost like machinery, but takes provided keyword as input parameter instead of the original string.

- -

By clicking a suggestion, it gets copied into translation area.

- -
-
- -

Publicar a sua localização

- -

Suppose you now want to publish your l10n work by committing it to a repo. Pontoon lets you do that too! Actually, it does that for you by automatically syncing with repositories on hourly basis. You can now pat yourself on the back, do a little dance, go to sleep or do something else to celebrate your work!

diff --git a/files/pt-pt/mozilla/mercurial/basicos/index.html b/files/pt-pt/mozilla/mercurial/basicos/index.html deleted file mode 100644 index a57f7a3778..0000000000 --- a/files/pt-pt/mozilla/mercurial/basicos/index.html +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Básicos sobre Mercurial -slug: Mozilla/Mercurial/Basicos -tags: - - Desenvolvendo o Mozilla - - Mercurial -translation_of: Mozilla/Mercurial/Basics ---- -

I am about to tell you some stuff about Mercurial that will save you a lot of frustration. This page is cynical and survival-oriented. But I still claim Mercurial is a lot better than CVS. —jorendorff 16:06, 12 May 2008 (PDT)

- -

Expetativas

- -

Mercurial não é CVS. Os comandos não são os mesmos. Os conceitos não são os mesmos. Como é Mercurial diferente de CVS?

- -

This gun is loaded. You can shoot yourself in the foot. You can lose work. The tool tries to protect you, but it can happen anyway. The two common failure modes are: (a) you run a command without knowing what it's going to do; (b) you hg commit or hg qrefresh with a mistaken understanding of the state of your working directory. So you accidentally commit changes that you didn't want to commit; or you accidentally commit a broken merge; etc. Often it's not immediately obvious that anything is wrong.

- -

Forewarned is forearmed. Don't do these things. Don't run commands without knowing what they're going to do—hg help is your friend. Don't commit without diffing and thinking. And don't let yourself get into "play mode" and stop paying attention to the fact that what you're playing with is your own uncommitted work.

- -

Mercurial is not magic dust. Mercurial is flexible, powerful, and fun. It lets you attempt stuff you never would have tried in CVS. But of course not everything turns out to have been a good idea. (For example, we tried sharing patch queues. It sort of sucked.)

- -

Evite problemas

- -

Utilize o último lançamento estável do Mercurial.

- -

Learn how to get your bearings. Use read-only commands (like hg status, hg head, hg parents, hg log, hg diff, hg outgoing) to check the status of your repository. This is a key skill.

- -

Configure a merge program and make sure you know how to use it. DO IT NOW. Otherwise you will likely screw up your repository at some point.

- -

Mercurial doesn't leaves conflict markers in your files; instead, it wants you to fix the conflicts immediately, using a merge program (like kdiff3) which it can launch for you.

- -

This can be error-prone. By default, Mercurial uses the first merge program it finds on your system, and merge programs can have a learning curve. Mercurial does not do a good job of detecting busted merges and refusing to proceed, so just by closing a window you can unwittingly put yourself in a bad state. Bad merges may lead to seemingly inexplicable Mercurial behavior in the future.

- -

If a merge fails, make sure Mercurial knows that it has failed. When you're first learning the ropes, merges often go wrong. You might see this message:

- -
0 files updated, 0 files merged, 0 files removed, 1 files unresolved
-There are unresolved merges, you can redo the full merge using:
-  hg update -C 2
-  hg merge 1
-
- -

This means some conflicts weren't resolved during the merge. If you don't know exactly what they are and how to fix them, use that hg update -C command to tell Mercurial that you've given up on that merge.

- -

If you don't, Mercurial won't know, and the next time you commit, it'll make a merge changeset. This is bad. The result can look a lot like accidentally destroying a bunch of work, actually, but the damage can be undone.

- -

If hg parents shows two parents, you're merging.

- -

If you use Mercurial Queues, back up your work. hg qrefresh destructively replaces the old patch with the new one! Use hg qinit -c to create a separate backup repository for your patches and hg commit --mq -m backup regularly.

- -

Don't use Mercurial Queues in a repository that someone might pull from since applied (non-public) patches would also be pulled.

- -

Recuperação

- -

Ups! Mercurial cortou o seu braço!

- -

Don't randomly try stuff to see if it'll magically fix it. Remember what you stand to lose, and set down the chainsaw while you still have one good arm.

- -

Obtenha ajuda no IRC. Tente #hg ou #developers no Mozilla IRC ou #mercurial no freenode.

- -

 

- -

{{ languages( { "es": "es/Lo_b\u00e1sico_de_Mercurial", "fr": "fr/Les_bases_de_Mercurial", "ja": "ja/Mercurial_basics" } ) }}

diff --git a/files/pt-pt/mozilla/mercurial/index.html b/files/pt-pt/mozilla/mercurial/index.html deleted file mode 100644 index 4f54ee5312..0000000000 --- a/files/pt-pt/mozilla/mercurial/index.html +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Mercurial -slug: Mozilla/Mercurial -tags: - - Desenvolvendo a Mozilla - - Mercurial -translation_of: Mozilla/Mercurial ---- -
-

Por favor, consulte Mercurial para Mozillians em ReadTheDocs para as melhores práticas atuais à volta do Mercurial, including many helpful extra tools and guidelines that make using Mercurial fast and easy.

-
- -

Mercurial (também conhecido como "hg"), é um controlo de versões distribuido de software, utilizado para o desenvolvimento do Firefox, Thunderbird, e o núcleo de Gecko partilhado. Este substituiu CVS depois da ramificação 1.9 da Mozilla.

- -

hg is the Mercurial command-line tool, Hg being the chemical symbol for the element mercury.

- -

Instalação, configuração e obtenção da fonte

- -

See Installing Mercurial for installation and configuration tips.

- -

See Getting Mozilla Source Code Using Mercurial for getting a tree to build.

- -

Aprender a utilizar o Mercurial

- -

If you are new to Mercurial, you should start with the official guide.

- -

Then, move on to Mercurial basics and Mercurial FAQ and the version control tool docs for Mozilla-centric Mercurial information.

- -

Leitura adicional

- -

The Mercurial tag lists the Mercurial-related articles on MDN.

- -

And on wiki.mozilla.org, these helpful pages:

- - - -

{{ languages( { "es": "es/Mercurial", "fr": "fr/Mercurial", "ja": "ja/Mercurial" } ) }}

diff --git a/files/pt-pt/mozilla/mercurial/instaacao_mercurial/index.html b/files/pt-pt/mozilla/mercurial/instaacao_mercurial/index.html deleted file mode 100644 index b5bf466bca..0000000000 --- a/files/pt-pt/mozilla/mercurial/instaacao_mercurial/index.html +++ /dev/null @@ -1,151 +0,0 @@ ---- -title: Instalação de Mercurial -slug: Mozilla/Mercurial/Instaacao_Mercurial -tags: - - Desenvolvendo a Mozilla - - Mercurial - - Precisa de Atualização -translation_of: Mozilla/Mercurial/Installing_Mercurial ---- -

{{Note('Se ainda não leu os básicos sobre Mercurial, faça-o agora ou consulte Mercurial para outros recursos.')}}

- -
-

Please refer to Mercurial para Mozillians em ReadTheDocs for current best-practices around Mercurial, including many helpful extra tools and guidelines that make using Mercurial fast and easy.

-
- -

Instalação

- -

See Installing Mercurial from the Mozilla Version Control Guide.

- -

Configuração básica

- -

You should configure Mercurial before submitting patches to Mozilla.

- -

If you will be pulling the Firefox source code or one of the derived repositories, the easiest way to configure Mercurial is to run the mercurial-setup mach command:

- -
./mach mercurial-setup
- -

This command starts an interactive wizard that will help ensure your Mercurial is configured with the latest recommended settings. This command will not change any files on your machine without your consent.

- -

If you don't have the Firefox source code available, you should edit your Mercurial configuration file to look like the following:

- -
[ui]
-username = Your Real Name <user@example.com>
-merge = your-merge-program (or internal:merge)
-
-[diff]
-git = 1
-showfunc = 1
-unified = 8
-
-[defaults]
-commit = -v
-
- -

On Windows, these settings can be added to $HOME\.hgrc or $HOME\Mercurial.ini, or, if you'd like global settings, C:\mozilla-build\hg\Mercurial.ini or C:\Program Files\Mercurial\Mercurial.ini. On UNIX-like systems, they should be in your $HOME/.hgrc file.

- -

You can configure the editor to use for commit messages using the editor option in the [ui] section or by setting the EDITOR environment variable.

- -

If you are trying to access the repository through a proxy server, see these instructions.

- -

Outras dicas de configuração

- -

Unir programa

- -

After installing, choose a merge program. Seriously. Do it now. If you don't, Mercurial will choose one for you and spring it on you when you least expect it.

- -

A reasonable thing to do is to set ui.merge=internal:merge in the Mercurial configuration file (see below), which makes Mercurial try to merge changes and add the conflict markers (a la CVS) to the files that couldn't be merged.

- -

Under Ubuntu, you can install meld package, then in in the Mercurial configuration file (see below) set ui.merge=meld

- -

You can see the list of merge conflicts by looking for "merging ... failed!" in the update output.

- -

Configuring kdiff3 as a merge tool

- -

If you're on Linux and you have kdiff3 installed, you probably want to configure kdiff3 as a merge tool.  (It's better than meld because it will actually resolve a bunch of the conflicts without prompting you, generally quite accurately.)  You can do this by adding the following lines (which come from contrib/mergetools.hgrc in the Mercurial distribution):

- -
[merge-tools]
-kdiff3.args=--auto -L1 base --L2 local --L3 other $base $local $other -o $output
-kdiff3.regkey=Software\KDiff3
-kdiff3.regappend=\kdiff3.exe
-kdiff3.fixeol=True
-kdiff3.gui=True
-
-
- -

Extensões

- -

There's a number of extensions you can enable. See http://mercurial.selenic.com/wiki/UsingExtensions. Almost everyone should probably enable the following:

- - - -

These can all be turned on by just adding this to your .hgrc file:

- -
[extensions]
-color =
-rebase =
-histedit =
-progress =
-transplant =
-pager =
-
- -

In addition, there are some 3rd party extensions that are incredibly useful for basic development:

- -
-
mozext
-
Mozilla-specific functionality to aid in developing Firefox/Gecko.
-
trychooser
-
Automatically creates a try commit message and then pushes changes to Mozilla's Try infrastructure. Just run: - 
hg trychooser
-
-
qimportbz
-
Import patches from Bugzilla. Creates a filename and commit message for you based on the bug's metadata. - 
hg qimport bz://1234567
-
-
-
bzexport
-
Export patches to Bugzilla. There are quite a few optional arguments here to create new or update existing bugs with the attment, as well as auto matically request reviews. Type hg help bzexport for a full list but the basic syntax is: - 
hg bzexport -i 1234567
-
-
- -

Installing these is fairly easy. You'll just need to find a place on your system to store the extensions, and clone the extension repos into it:

- -
hg clone https://bitbucket.org/edgimar/crecord
-hg clone https://bitbucket.org/sfink/mqext
-hg clone https://hg.mozilla.org/users/robarnold_cmu.edu/qimportbz
-git clone https://github.com/pbiggar/trychooser
-
- -

And then add then to your .hgrc file

- -
[extensions]
-qcrecord =  /path/to/crecord/crecord
-mqext =  path/to/mqext
-qimportbz =  path/to/qimportbz
-trychooser = path/to/trychooser/trychooser
-
- -

Configuração do repositório de testes

- -

If you have access to the try server you may want to configure Mercurial so you can refer to it simply as "try", since it can be useful from all your trees.  This can be done by adding this to your ~/.hgrc (or Mercurial.ini):

- -

 

- -
[paths]
-try = ssh://hg.mozilla.org/try/
-
- -

You can also configure short names like this that are specific to a particular repository by adding a [paths] section to the .hg/hgrc file within a repository.  There are two magic names, "default" and "default-push", which are used as the default push/pull targets.  (If "default" is specified and "default-push" is not, "default" is used for both.)

- -

Alternativamente, pode instalar a extensão trychooser (versão antiga).

- -

{{ languages( { "fr": "fr/Installation_de_Mercurial" } ) }}

diff --git a/files/pt-pt/mozilla/o0coes_linha_comandos/index.html b/files/pt-pt/mozilla/o0coes_linha_comandos/index.html deleted file mode 100644 index 57a1511c23..0000000000 --- a/files/pt-pt/mozilla/o0coes_linha_comandos/index.html +++ /dev/null @@ -1,486 +0,0 @@ ---- -title: Opções da Linha de Comandos -slug: Mozilla/O0coes_Linha_Comandos -tags: - - Administração - - Desenvolvimento da Mozilla - - Documentação do Utilizador - - Extensões - - Extras - - Firefox - - Linha de Comandos - - Mozilla - - Perguntas e Respostas - - Precisa de Atualização -translation_of: Mozilla/Command_Line_Options ---- -

{{FirefoxSidebar}}

- -

As opções da linha de comandos são utilizadas para especificar várias opções de arranque para as aplicações da Mozilla. Por exemplo, pode utilizar as opções de configuração da linha de comandos para ignorar o 'Gestor de Perfis' e abrir um perfil específico (se tiver vários perfis). Também pode controlar como as aplicações da Mozilla são abertas, quais os componentes que são abertos inicialmente, e o que os componentes fazem quando são abertos. Esta página descreve as opções mais utilizadas e como utilizá-las. Pode abrir a interface da linha de comandos pressionando "Shift + F2".

- -

Regras de Sintaxe

- -

But first, let's describe the syntax rules that apply for all options.

- - - -

Utilizar as opções da linha de comandos

- -

Command line options are entered after the command to start the application. Some options have arguments. These are entered after the command line option. Some options have abbreviations. For example, the command line option "-editor" can be abbreviated as "-edit". (Where abbreviations are available, they are described in the text below.) In some cases option arguments must be enclosed in quotation marks. (This is noted in the option descriptions below.) Multiple command line options can be specified. In general, the syntax is as follows:

- -
application -option -option "argument" -option argument
-
- -

Exemplos

- -

The following examples show the use of the "-ProfileManager" command, which will open the Profile Manager prior to starting Firefox or Thunderbird:

- -

Windows

- -

Select Run from Windows Start menu. Type:

- -
firefox -ProfileManager
-
- -

Mac OS X

- -

Go to Applications > Utilities. Open Terminal and type:

- -
cd /Applications/Firefox.app/Contents/MacOS
-./firefox -ProfileManager
-
- -

If you use Firefox Nightly, you can type:

- -
cd /Applications/FirefoxNightly.app/Contents/MacOS
-./firefox -ProfileManager
-
- -

Linux

- -

Open Terminal and type:

- -
cd Thunderbird installation directory
-./thunderbird -ProfileManager
-
- -

The example above invokes the "-ProfileManager" command line option with Mozilla's Thunderbird mail client.

- -

Perfil do Utilizador

- -

-CreateProfile profile_name

- -

Create a new profile in the default directory, but do not start application. The profile will be named profile_name in the profile manager. profile_name must not contain spaces ( ). To use this successfully no instance of the application must be running, or the -no-remote options must be used.

- -
firefox -CreateProfile JoelUser
-
- -

-CreateProfile "profile_name profile_dir"

- -

Creates a new profile in the profile_dir directory, but do not start application. The profile will be named profile_name in the profile manager. Note profile_name and profile_dir are quoted together, and are separated by exactly 1 space (as with the previous syntax, profile_name must not contain spaces).

- -

To use this successfully no instance of the application must be running, or the -no-remote options must be used.

- -

NOTE: profile_dir must not exist and you must not already have a profile called profile_name.

- -
firefox -CreateProfile "JoelUser c:\internet\joelusers-moz-profile"
-
- -

-migration

- -

Start with Import Wizard.

- -

-new-instance

- -

Open new instance, not a new window in running instance, which allows multiple copies of application to be open at a time.

- -
firefox -new-instance -P "Another Profile"
-
- -
-

Nota: Not available for Windows, see {{bug(855899)}}.

-
- -

-no-remote

- -

- -

Do not accept or send remote commands; implies -new-instance.

- -
firefox -no-remote -P "Another Profile"
-
- -
-

Nota: Since Firefox 9, this does really mean what its name implies on all platforms, i.e. instances created with this parameter do not accept or send remote commands, see {{bug(650078)}}. That means that such instances won't be re-used. Also when using this argument a new instance is created in any case.

-
- -

-override /path/to/override.ini

- -

Load the specified override.ini file to override application.ini ({{Source("browser/app/application.ini")}}). This can be used to suppress the Migration Wizard at startup by loading the following override.ini. Firefox only.

- -
[XRE]
-EnableProfileMigrator=0
- -

-ProfileManager

- -

Start with Profile Manager. Short form: -P without a profile name.

- -

-P "profile_name"

- -

Bypass Profile Manager and launch application with the profile named profile_name. Useful for dealing with multiple profiles. Note profile_name is case sensitive. If you don't specify a profile name then the profile manager is opened instead. You must use an upper case P on Linux with versions older than 7.x, as there lower case invokes Purify mode (memory and leak detection). Other platforms accept both upper and lower case.

- -
firefox -P "Joel User"
-
- -

-profile "profile_path"

- -

Start with the profile with the given path. Firefox, Thunderbird and SeaMonkey2.x only.

- -

"profile_path" can either be an absolute path ("/path/to/profile") or a relative path ("path/to/profile").

- -
-

Nota: On Mac OS X specifying a relative path is not supported anymore from Firefox 4.0 and up due to a regression, see {{bug(673955)}}.

-
- - -

Navegador

- -

-browser

- -

Start with the browser component. Firefox and SeaMonkey only.

- -

-foreground

- -

Make this instance the active application.

- -

-headless

- -

Runs Firefox in headless mode, which is very useful for purposes such as debugging and automated testing. Available in Firefox 55+ on Linux, and Firefox 56+ on Windows/Mac OS X.

- -

-new-tab URL

- -

Open URL in a new tab. Firefox and SeaMonkey2.x only.

- -

-new-window URL

- -

Open URL in a new window. Firefox and SeaMonkey2.x only.

- -

-preferences

- -

Open Options/Preferences window. Firefox and SeaMonkey2.x only.

- -

-private

- -

Opens Firefox in permanent private browsing mode. Firefox 3.6 and later only.

- -

May not be applicable in older Ubuntu for Firefox 20 and later, confirmed to work in 14.04

- -

-private-window

- -

Opens a new private browsing window in an existing instance of Firefox. Firefox 20 and later only.

- -

-private-window URL

- -

Open URL in a new private browsing window. If a private browsing window is already open, a new tab is opened in the existing window. Firefox 29 and later only. Does not work in Firefox 31 on linux mint 17 nor on Firefox 48 on Windows 7. URL opens in a non-private window.

- -

-search term

- -

Search term with your default search engine. Firefox and SeaMonkey 2.1 and later only.

- -

-setDefaultBrowser

- -

Set the application as the default browser. Firefox only.

- -

-url URL

- -

Open URL in a new tab or window, depend on the browser option. -url can be omitted. You may list multiple URLs, separated by spaces. Firefox and SeaMonkey only.

- -
-

Note: When opening multiple URLs, Firefox always opens them as tabs in a new window.

-
- -
firefox www.mozilla.com
-firefox www.mozilla.com developer.mozilla.org
- -

Correio/Notícias

- -

-addressbook

- -

Start with address book. Thunderbird and SeaMonkey only.

- -

-compose message_options

- -

Start with mail composer. See syntax rules. Thunderbird and SeaMonkey only.

- -
thunderbird -compose "to=foo@nowhere.net"
- -

-mail

- -

Start with the mail client. Thunderbird and SeaMonkey only.

- -

-news news_URL

- -

Start with the news client. If news_URL (optional) is given, open the specified newsgroup. Thunderbird and SeaMonkey only.

- -
thunderbird -news news://server/group
-
- -

-options

- -

Open Options/Preferences window. Thunderbird only.

- -

-offline

- -

Start with the offline mode. Thunderbird and SeaMonkey only.

- -

-setDefaultMail

- -

Set the application as the default email client. Thunderbird only.

- -

Calendário

- -

-calendar

- -

Start with the calendar client. Sunbird only.

- -

-showdate date

- -

Show your schedule of the given date. Sunbird only.

- -
sunbird -showdate 08/04/2008
-
- -

-subscribe URL or -url URL

- -

Subscribe to the given URL. Sunbird only.

- -

Outros Componentes

- -

-chat

- -

Start with the IRC client, ChatZilla, if installed.

- -

-devtools

- -

Start with native Developer Tools opened.

- -

-editor URL or -edit URL

- -

Start with editor (Composer) for the given URL (where URL is optional). SeaMonkey only.

- -
seamonkey -edit www.mozilla.org
-
- -

-inspector URL

- -

Start with the DOM Inspector, if installed, and inspect the given URL (where URL is optional).

- -

-jsdebugger

- -

Start application with Browser Toolbox (formerly Browser Debugger). That is different to Venkman debugger (see option -venkman).

- -

-jsconsole

- -

Start application with the Error Console, or, in Firefox, the Browser Console.

- -

-purgecaches

- -

Gecko (layout engine) has a javascript cache, which is not reset on startup. This clears it.

- -

-start-debugger-server port

- -

Firefox only. Start the debugger server on port. This will enable another instance of Firefox to connect the Firefox Developer Tools to this Firefox instance. See the article on remotely debugging Firefox Desktop.

- -

The port argument is optional, and if it is omitted, the server will listen on port 6000.

- -

-venkman

- -

Start with the JavaScript debugger, Venkman, if installed.

- -

XULRunner

- -

-app /path/to/application.ini

- -

Start a new process running the XULRunner application at path/to. Also works with Firefox version 3 and above.

- -

--install-app path/to/myapplication.(xpi|xulapp)

- -

Installs the XULRunner application at path/to onto the system. Applications are installed into the default location for your system (program files|Applications|usr/lib) at vendorname/applicationName.  Applications may be uninstalled per usual methods for your system.

- -
"C:\Program Files\Mozilla XULRunner\1.8.0.4\xulrunner\xulrunner.exe" --install-app "C:\Users\Billdo\Desktop\myapplication.xpi"
- -
/opt/xulrunner/1.8.0.4/xulrunner/xulrunner --install-app ~/Desktop/myapplication.xulapp
- -
/Library/Frameworks/XUL.framework/xulrunner-bin --install-app ~/Desktop/myapplication.xpi
- -

--register-global

- -

Registers XULRunner on the system for all users. Must be run as admin / root.

- -

--register-user

- -

Registers XULRunner for a single user.

- -

--unregister-global

- -

Unregisters XULRunner for all users.

- -

--unregister-user

- -

Unregisters XULRunner for a single user.

- -

Chrome

- -

-chrome chrome_URL

- -

Load the specified chrome.

- -
firefox -chrome chrome://inspector/content
-
- -

-register chrome_URL

- -

Register the specified chrome, but do not start application.

- -

Extras

- -

{{Gecko_MinVersion_Note(1.9.2, "-install-global-extension and -install-global-theme have been removed from Gecko 1.9.2 and upwards.")}}

- -

-install-global-extension /path/to/extension

- -

Installs the extension into the application directory. The parameter is the path to the extension. You must have administrative privileges.

- -

-install-global-theme /path/to/theme

- -

Same as above, but for themes. You must have administrative privileges.

- -
-

Note: Since Firefox 2.0.0.7, use of the -install-global-extension and -install-global-theme command line arguments have been restricted to only allow installing add-ons that are on local disks or mapped drives. Installing from a network share directly will no longer succeed.

-
- -

-safe-mode

- -

Launches the application with all extensions disabled, for that launch only. (Extensions are not loaded, but are not permanently disabled in the Extension Manager data source).

- -

Controlo remoto

- -

-remote remote_command {{Obsolete_Inline}}

- -
-

This feature was removed in Firefox 36.0, restored in 36.0.1 and removed again in 39.0. See {{bug(1080319)}}.

-
- -

Execute the specified remote_command in an already running application process.

- -
firefox -remote "openURL(www.mozilla.org, new-tab)"
-
- -
-

This option is only available on X-Windows Unix platforms.

-
- -

Diversos

- -

-attach-console

- -

Write messages for the debugging console into the window which launched the application instead of opening a new window for the debugging messages. Only supported on the Windows operating system.

- -

-console

- -

Start application with a debugging console. Note: Windows only.

- -

-h or -help or -?

- -

Print the list of all available command line options. Note that on Windows this only works with a redirection such as |more ({{Bug(355889)}}). This option is available only in a command console.

- -

-osint

- -

Tells the application that it is being launched by the OS shell. This should not be specified unless the caller provides all of the functionality provided by the OS shell when launching the application ({{Bug(384384)}}).

- -

-requestPending

- -

Tells the application that there will be a Windows DDE request to open the same url specified on the command line. This should not be specified unless the caller provides all of the functionality provided by the OS shell when launching the application ({{Bug(354005)}}).

- -

-silent

- -

Don't open default windows. Useful with those command-line arguments that open their own windows but don't already prevent default windows from opening. Firefox, Thunderbird3.x and SeaMonkey2.x only.

- -

-tray

- -

Start application minimized to system tray. Useful with autorun.

- -

-v or -version

- -

Print application version. Note that on Windows this only works with a redirection such as |more ({{Bug(355889)}}). This option is available only in a command console.

- -

X11 options

- -

These options are only available for an application build for and running atop the X11/X.org display and window system to be found on Linux and other Unix-based systems.

- -

--class=WM_CLASS

- -

Set the WM_CLASS resource class of the X11 windows created by the application.

- -

--display=DISPLAY

- -

Set the X display to use.

- -

--g-fatal-warnings

- -

Make all warnings fatal.

- -

--sync

- -

Make X calls synchronous.

- -

Outras opções que precisam de ser documentadas

- - - -

Referências

- - - -
-

Informação do Documento Original

- - -
- -

 

diff --git a/files/pt-pt/mozilla/performance/about_colon_memory/index.html b/files/pt-pt/mozilla/performance/about_colon_memory/index.html deleted file mode 100644 index 02878e1d31..0000000000 --- a/files/pt-pt/mozilla/performance/about_colon_memory/index.html +++ /dev/null @@ -1,187 +0,0 @@ ---- -title: 'about:memory' -slug: 'Mozilla/Performance/about:memory' -tags: - - Desempenho - - Relatório - - diagnóstico - - memoria -translation_of: 'Mozilla/Performance/about:memory' ---- -

about:memory is a special page within Firefox that lets you view, save, load, and diff detailed measurements of Firefox's memory usage. It also lets you do other memory-related operations like trigger GC and CC, dump GC & CC logs, and dump DMD reports. It is present in all builds and does not require any preparation to be used.

- -

Como gerar relatórios de memória

- -

Let's assume that you want to measure Firefox's memory usage. Perhaps you want to investigate it yourself, or perhaps someone has asked you to use about:memory to generate "memory reports" so they can investigate a problem you are having. Follow these steps.

- - - -

Note that in both cases the generated data contains privacy-sensitive details such as the full list of the web pages you have open in other tabs. If you do not wish to share this information, you can select the "anonymize" checkbox before clicking on "Measure and save..." or "Measure...". This will cause the privacy-sensitive data to be stripped out, but it may also make it harder for others to investigate the memory usage.

- -

Carregar relatórios de memória de um ficheiro

- -

The easiest way to load memory reports from file is to use the "Load..." button. You can also use the "Load and diff..." button to get the difference between two memory report files.

- -

Single memory report files can also be loaded automatically when about:memory is loaded by appending a file query string, for example:

- -
about:memory?file=/home/username/reports.json.gz
-
- -

This is most useful when loading memory reports files obtained from a Firefox OS device.

- -

Memory reports are saved to file as gzipped JSON. These files can be loaded as is, but they can also be loaded after unzipping.

- -

Interpretar os relatórios de memória

- -

Almost everything you see in about:memory has an explanatory tool-tip. Hover over any button to see a description of what it does. Hover over any measurement to see a description of what it means.

- -

Básico de cálculo

- -

Most measurements use bytes as their unit, but some are counts or percentages.

- -

Most measurements are presented within trees. For example:

- -
 585 (100.0%) -- preference-service
- └──585 (100.0%) -- referent
-    ├──493 (84.27%) ── strong
-    └───92 (15.73%) -- weak
-        ├──92 (15.73%) ── alive
-        └───0 (00.00%) ── dead
-
- -

Leaf nodes represent actual measurements; the value of each internal node is the sum of all its children.

- -

The use of trees allows measurements to be broken down into further categories, sub-categories, sub-sub-categories, etc., to arbitrary depth, as needed. All the measurements within a single tree are non-overlapping.

- -

Tree paths can be written using '/' as a separator. For example, preference/referent/weak/dead represents the path to the final leaf node in the example tree above.

- -

Sub-trees can be collapsed or expanded by clicking on them. If you find any particular tree overwhelming, it can be helpful to collapse all the sub-trees immediately below the root, and then gradually expand the sub-trees of interest.

- -

Secções

- -

Memory reports are displayed on a per-process basis, with one process per section. Within each process's measurements, there are the following subsections.

- -

Alocação Explícitas

- -

This section contains a single tree, called "explicit", that measures all the memory allocated via explicit calls to heap allocation functions (such as malloc and new) and to non-heap allocations functions (such as mmap and VirtualAlloc).

- -

Here is an example for a browser session where tabs were open to cnn.com, techcrunch.com, and arstechnica.com. Various sub-trees have been expanded and others collapsed for the sake of presentation.

- -
191.89 MB (100.0%) -- explicit
-├───63.15 MB (32.91%) -- window-objects
-│   ├──24.57 MB (12.80%) -- top(http://edition.cnn.com/, id=8)
-│   │  ├──20.18 MB (10.52%) -- active
-│   │  │  ├──10.57 MB (05.51%) -- window(http://edition.cnn.com/)
-│   │  │  │  ├───4.55 MB (02.37%) ++ js-compartment(http://edition.cnn.com/)
-│   │  │  │  ├───2.60 MB (01.36%) ++ layout
-│   │  │  │  ├───1.94 MB (01.01%) ── style-sheets
-│   │  │  │  └───1.48 MB (00.77%) -- (2 tiny)
-│   │  │  │      ├──1.43 MB (00.75%) ++ dom
-│   │  │  │      └──0.05 MB (00.02%) ── property-tables
-│   │  │  └───9.61 MB (05.01%) ++ (18 tiny)
-│   │  └───4.39 MB (02.29%) -- js-zone(0x7f69425b5800)
-│   ├──15.75 MB (08.21%) ++ top(http://techcrunch.com/, id=20)
-│   ├──12.85 MB (06.69%) ++ top(http://arstechnica.com/, id=14)
-│   ├───6.40 MB (03.33%) ++ top(chrome://browser/content/browser.xul, id=3)
-│   └───3.59 MB (01.87%) ++ (4 tiny)
-├───45.74 MB (23.84%) ++ js-non-window
-├───33.73 MB (17.58%) ── heap-unclassified
-├───22.51 MB (11.73%) ++ heap-overhead
-├────6.62 MB (03.45%) ++ images
-├────5.82 MB (03.03%) ++ workers/workers(chrome)
-├────5.36 MB (02.80%) ++ (16 tiny)
-├────4.07 MB (02.12%) ++ storage
-├────2.74 MB (01.43%) ++ startup-cache
-└────2.16 MB (01.12%) ++ xpconnect
- -

Some expertise is required to understand the full details here, but there are various things worth pointing out.

- - - -

Some add-on memory usage is identified, as the following example shows.

- -
├───40,214,384 B (04.17%) -- add-ons
-│   ├──21,184,320 B (02.20%) ++ {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}/js-non-window/zones/zone(0x100496800)/compartment([System Principal], jar:file:///Users/njn/Library/Application%20Support/Firefox/Profiles/puna0zr8.new/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/bootstrap.js (from: resource://gre/modules/addons/XPIProvider.jsm:4307))
-│   ├──11,583,312 B (01.20%) ++ jid1-xUfzOsOFlzSOXg@jetpack/js-non-window/zones/zone(0x100496800)
-│   ├───5,574,608 B (00.58%) -- {59c81df5-4b7a-477b-912d-4e0fdf64e5f2}
-│   │   ├──5,529,280 B (00.57%) -- window-objects
-│   │   │  ├──4,175,584 B (00.43%) ++ top(chrome://chatzilla/content/chatzilla.xul, id=4293)
-│   │   │  └──1,353,696 B (00.14%) ++ top(chrome://chatzilla/content/output-window.html, id=4298)
-│   │   └─────45,328 B (00.00%) ++ js-non-window/zones/zone(0x100496800)/compartment([System Principal], file:///Users/njn/Library/Application%20Support/Firefox/Profiles/puna0zr8.new/extensions/%7B59c81df5-4b7a-477b-912d-4e0fdf64e5f2%7D/components/chatzilla-service.js)
-│   └───1,872,144 B (00.19%) ++ treestyletab@piro.sakura.ne.jp/js-non-window/zones/zone(0x100496800)
- -

More things worth pointing out are as follows.

- - - -

Outros Cálculos

- -

This section contains multiple trees, includes many that cross-cut the measurements in the "explicit" tree. For example, in the "explicit" tree all DOM and layout measurements are broken down by window by window, but in "Other Measurements" those measurements are aggregated into totals for the whole browser, as the following example shows.

- -
26.77 MB (100.0%) -- window-objects
-├──14.59 MB (54.52%) -- layout
-│  ├───6.22 MB (23.24%) ── style-sets
-│  ├───4.00 MB (14.95%) ── pres-shell
-│  ├───1.79 MB (06.68%) ── frames
-│  ├───0.89 MB (03.33%) ── style-contexts
-│  ├───0.62 MB (02.33%) ── rule-nodes
-│  ├───0.56 MB (02.10%) ── pres-contexts
-│  ├───0.47 MB (01.75%) ── line-boxes
-│  └───0.04 MB (00.14%) ── text-runs
-├───6.53 MB (24.39%) ── style-sheets
-├───5.59 MB (20.89%) -- dom
-│   ├──3.39 MB (12.66%) ── element-nodes
-│   ├──1.56 MB (05.84%) ── text-nodes
-│   ├──0.54 MB (02.03%) ── other
-│   └──0.10 MB (00.36%) ++ (4 tiny)
-└───0.06 MB (00.21%) ── property-tables
- -

Some of the trees in this section measure things that do not cross-cut the measurements in the "explicit" tree, such as those in the "preference-service" example above.

- -

Finally, at the end of this section are individual measurements, as the following example shows.

- -
    0.00 MB ── canvas-2d-pixels
-    5.38 MB ── gfx-surface-xlib
-    0.00 MB ── gfx-textures
-    0.00 MB ── gfx-tiles-waste
-          0 ── ghost-windows
-  109.22 MB ── heap-allocated
-        164 ── heap-chunks
-    1.00 MB ── heap-chunksize
-  114.51 MB ── heap-committed
-  164.00 MB ── heap-mapped
-      4.84% ── heap-overhead-ratio
-          1 ── host-object-urls
-    0.00 MB ── imagelib-surface-cache
-    5.27 MB ── js-main-runtime-temporary-peak
-          0 ── page-faults-hard
-    203,349 ── page-faults-soft
-  274.99 MB ── resident
-  251.47 MB ── resident-unique
-1,103.64 MB ── vsize
- -

Some measurements of note are as follows.

- - diff --git a/files/pt-pt/mozilla/performance/comunicacao_de_um_problema_de_desempenho/index.html b/files/pt-pt/mozilla/performance/comunicacao_de_um_problema_de_desempenho/index.html deleted file mode 100644 index a641730856..0000000000 --- a/files/pt-pt/mozilla/performance/comunicacao_de_um_problema_de_desempenho/index.html +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Comunicação de um Problema de Desempenho -slug: Mozilla/Performance/Comunicacao_de_um_problema_de_desempenho -tags: - - Desempenho - - Perfilar - - QA - - Testes -translation_of: Mozilla/Performance/Reporting_a_Performance_Problem ---- -

Este artigo irá guiá-lo na comunicação de um problema de desempenho utilizando a extensão do Gecko Profiler. Se preferir, também existe um tutorial em vídeo, em vez da leitura.

- -

Configurar a extensão Gecko Profiler

- -
    -
  1. Transferir e instalar a última versão da extensão Gecko Profiler
    2. -
  2. A exntensção de perfilar irá aparecer no topo à direita da barra do URL como um ícone globo (se não, arraste-a para lá da janela de Personalizar).
    -
    - The Gecko Profiler Add-on installed and visible within the Nightly toolbar.
    3. -
  3. Lembre-se de desativar ou desinstalar a extensão se a não estiver a utilizar.
    4. -
- -

Apenas macOS, ou para verificar se um problema foi corrigido numa versão posterior do Firefox (as compilações do macOS atualmente irão produzir informação importante dos perfis em falta):

- -
    -
  1. Transferir e instalar a compilação nightly para a sua platforma. Terá de fechar todas as instâncias do Firefox antes de executar nightly.
    2. -
  2. Nightly é uma versão de desenvolvimento, que pode conter erros, por isso, teste com um novo perfil ou efetue uma cópia de segurança dos seus dados.
    3. -
  3. Verifique se está a funcionar corretamente, indo até 'Sobre Nightly' procurando por 'nightly' como o canal de atualização (3ª. linha). O ícone deverá ser um globo azul .
    4. -
- -

Using the Add-on

- -

Once installed, the profiler becomes active immediately (the icon being blue indicates it is active). The profiler uses a fixed size buffer to store sample data. When it runs out of space in its buffer, it discards old entries so you may want to increase the buffer size if you find you are unable to capture the profile quickly enough after you notice a performance problem. In the Settings part of the UI you can adjust the size of the buffer (presently defaults to 9 MB) and the time interval between data collection (presently defaults to 1 ms). Note that increasing the buffer size uses more memory and can make capturing a profile take longer.

- -

Profiler UI

- -

Using the keyboard shortcuts is often more convenient than using the mouse to interact with the UI:

- - - -

Capturing and sharing a profile

- -
    -
  1. Reproduce the performance problem. If possible let the problem manifest itself for 5-10 seconds.
    2. -
  2. Press Ctrl+Shift+2 or click on the 'Globe' icon in the top right and select 'Capture Profile'. Try to do this within a few seconds from reproducing the performance problem as only the last few seconds are recorded. If the timeline has a large red block it's a good sign.
    - Jank markers appearing in the Perf.html profile analysis tool.
    3. -
  3. The data will open in a new tab. Wait until the "Waiting for symbol tables for library libxul.pdb..." notification disappears before sharing the profile.
    4. -
  4. There will be a button in the top right labeled 'Share' which will upload this profile and once completed will write out a link. Copy this URL to your clipboard by right clicking and add the profile URL to the bug for your performance problem and/or send it to the appropriate person. Try to give some context about what you were doing when the performance problem arose such as the URL you were viewing and what actions were you doing (ex. scrolling on gmail.com).
    - The button for sharing a profile.
    5. -
diff --git a/files/pt-pt/mozilla/performance/index.html b/files/pt-pt/mozilla/performance/index.html deleted file mode 100644 index 44fcdebce2..0000000000 --- a/files/pt-pt/mozilla/performance/index.html +++ /dev/null @@ -1,145 +0,0 @@ ---- -title: Performance -slug: Mozilla/Performance -tags: - - Add-ons - - Debugging - - Depuração - - Desempenho - - Desenvolvimento - - Development - - Extras - - Mozilla - - Performance -translation_of: Mozilla/Performance ---- -

The articles linked to from here will help you improve performance, whether you're developing core Mozilla code or an add-on.

- - - - - - - - -
-

Documentação

- -
-
Reporting a Performance Problem
-
A user friendly guide to reporting a performance problem. A development environment is not required.
-
Benchmarking
-
Tips on generating valid performance metrics.
-
Performance best practices in extensions
-
A performance "best practices" guide for extension developers.
-
Measuring Add-on Startup Performance
-
A guide for add-on developers on how to set up a performance testing environment.
-
XUL School: Add-on Performance
-
Tips for add-on developers to help them avoid impairing application performance.
-
GPU performance
-
Tips for profiling and improving performance when using a GPU.
-
Scroll-Linked Effects
-
Information on scroll-linked effects, their effect on performance, related tools, and possible mitigation techniques.
-
Automated Performance Testing and Sheriffing
-
Information on automated performance testing and sheriffing at Mozilla.
-
Best practices for Front-end Engineers
-
Tips for reducing impacts on browser performance in front-end code.
-
- -

View all pages tagged with "Performance"...

- -

Memory profiling and leak detection tools

- -
-
The Developer Tools "Memory" panel
-
The memory panel in the devtools supports taking heap snapshots, diffing them, computing dominator trees to surface "heavy retainers", and recording allocation stacks.
-
- -
-
about:memory
-
about:memory is the easiest-to-use tool for measuring memory usage in Mozilla code, and is the best place to start. It also lets you do other memory-related operations like trigger GC and CC, dump GC & CC logs, and dump DMD reports. about:memory is built on top of Firefox's memory reporting infrastructure.
-
DMD
-
DMD is a tool that identifies shortcomings in about:memory's measurements, and can also do multiple kinds of general heap profiling.
-
Are We Slim Yet
-
areweslimyet.com (a.k.a. AWSY) is a memory usage and regression tracker.
-
BloatView
-
BloatView prints per-class statistics on allocations and refcounts, and provides gross numbers on the amount of memory being leaked broken down by class. It is used as part of Mozilla's continuous integration testing.
-
Refcount tracing and balancing
-
Refcount tracing and balancing are ways to track down leaks caused by incorrect uses of reference counting. They are slow and not particular easy to use, and thus most suitable for use by expert developers.
-
GC and CC logs
-
GC and CC logs can be generated and analyzed to in various ways. In particular, they can help you understand why a particular object is being kept alive.
-
Valgrind
-
Valgrind is a tool that detects various memory-related problems at runtime, including leaks. Valgrind is used as part of Mozilla's continuous integration testing, though the coverage is limited because Valgrind is slow.
-
LeakSanitizer
-
LeakSanitizer (a.k.a. LSAN) is similar to Valgrind, but it runs faster because it uses static source code instrumentation. LSAN is part of Mozilla's continuous integration testing, with most tests running through it as part of the AddressSanitizer (a.k.a. ASAN) test jobs.
-
Apple tools
-
Apple provides some tools for Mac OS X that report similar problems to those reported by LSAN and Valgrind. The "leaks" tool is not recommended for use with SpiderMonkey or Firefox, because it gets confused by tagged pointers and thinks objects have leaked when they have not (see bug 390944).
-
Leak Gauge
-
Leak Gauge is a tool that can be used to detect certain kinds of leaks in Gecko, including those involving documents, window objects, and docshells.
-
LogAlloc
-
LogAlloc is a tool that dumps a log of memory allocations in Gecko. That log can then be replayed against Firefox's default memory allocator independently or through another replace-malloc library, allowing the testing of other allocators under the exact same workload.
-
Memory Profiler
-
The memory profiler samples allocation events and provides different views to analyze the allocation characteristic.
-
- -

See also the documentation on Leak-hunting strategies and tips.

- 		-

Profiling and performance tools

- -
-
Profiling with the Developer Tools Profiler
-
The profiler built into the developer tools has a high-level waterfall, detailed call tree, allocations and GC profiling, and flame graphs. It is available on all platforms and release channels, and also supports remote profiling b2g and Fennec.
-
- -
-
Profiling with the Gecko Profiler {{ gecko_minversion_inline("16.0") }}
-
The Gecko Profiler is a good tool to start with, particularly for understanding where time is spent within C++ code in Firefox.
-
Profiling with Instruments
-
How to use Apple's Instruments tool to profile Mozilla code.
-
Profiling with Xperf
-
How to use Microsoft's Xperf tool to profile Mozilla code.
-
Profiling with Concurrency Visualizer
-
How to use Visual Studio's Concurrency Visualizer tool to profile Mozilla code.
-
Profiling with Zoom
-
Zoom is a profiler for Linux done by the people who made Shark
-
Measuring performance using the PerfMeasurement.jsm code module {{ gecko_minversion_inline("2.0") }}
-
Using PerfMeasurement.jsm to measure performance data in your JavaScript code.
-
Adding a new Telemetry probe
-
Information on how to add a new measurement to the Telemetry performance-reporting system
-
Profiling JavaScript with Shark (obsolete - replaced by Instruments)
-
How to use the Mac OS X Shark profiler to profile JavaScript code in Firefox 3.5 or later.
-
Profiling with Shark (obsolete - replaced by Instruments)
-
How to use Apple's Shark tool to profile Mozilla code.
-
Investigating CSS Performance
-
How to figure out why restyle is taking so long
-
- -

Power profiling

- -
-
Power profiling overview
-
This page provides an overview of relevant information, including details about hardware, what can be measured, and recommended approaches. It should be the starting point for anybody new to power profiling.
-
tools/power/rapl (Mac, Linux)
-
tools/power/rapl is a command-line utility in the Mozilla codebase that uses the Intel RAPL interface to gather direct power estimates for the package, cores, GPU and memory.
-
powermetrics (Mac-only)
-
powermetrics is a command-line utility that gathers and displays a wide range of global and per-process measurements, including CPU usage, GPU usage, and various wakeups frequencies.
-
TimerFirings logging (All platforms)
-
TimerFirings logging is a built-in logging mechanism that prints data on every time fired.
-
Activity Monitor, Battery Status Menu and top (Mac-only)
-
The battery status menu, Activity Monitor and top are three related Mac tools that have major flaws but often consulted by users, and so are worth understanding.
-
Intel Power Gadget (Windows, Mac, Linux)
-
Intel Power Gadget provides real-time graphs for package and processor RAPL estimates. It also provides an API through which those estimates can be obtained.
-
perf (Linux-only)
-
perf is a powerful command-line utility that can measure many different things, including energy estimates and high-context measurements of things such as wakeups.
-
turbostat (Linux-only)
-
turbostat is a command-line utility that gathers and displays various power-related measurements, with a focus on per-CPU measurements such as frequencies and C-states.
-
powertop (Linux-only)
-
powertop is an interactive command-line utility that gathers and displays various power-related measurements.
-
- -

Rópicos Relacionados

- -
-
JavaScript, XPCOM, Developing Mozilla, Extensions, Addons
-
-
diff --git a/files/pt-pt/mozilla/performance/perfilar_com_o_profiler_integrado/index.html b/files/pt-pt/mozilla/performance/perfilar_com_o_profiler_integrado/index.html deleted file mode 100644 index 0a34c2bc64..0000000000 --- a/files/pt-pt/mozilla/performance/perfilar_com_o_profiler_integrado/index.html +++ /dev/null @@ -1,356 +0,0 @@ ---- -title: Perfilar com o Gecko Profiler -slug: Mozilla/Performance/Perfilar_com_o_Profiler_integrado -tags: - - Desempenho - - Desenvolvimento da Mozilla - - Perfilar -translation_of: Mozilla/Performance/Profiling_with_the_Built-in_Profiler ---- -

{{ gecko_minversion_header("16.0") }}

- -
-

O Gecko Profiler é um profiler que está integrado no Firefox. Possui uma integração mais apertada com o Firefox do que os profilers externos, e também pode ser utilizado em situações em que os profilers externos não estão disponíveis, tal como numa máquina de não desenvolvimento ou num dispositivo Android bloqueado. 

-
- -
-

The Gecko Profiler has been previously known as "SPS" and "the built-in profiler". We have changed as many references to the old names as possible, but there may still be some around.

-
- -

Obter o Extra Gecko Profiler

- -

First things first, you want to make sure you are using the correct build of Firefox.  An official Nightly or Beta or Release build would work.  If you are using a local build, make sure you have the --enable-profiling option turned on in your mozconfig.

- -

The Gecko Profiler has two interfaces:

- -
    -
  1. for Web developers there is a simplified profiler that can be opened from the menu Tools > Web Developer > Performance.
    2. -
  2. a more advanced interface for developers of Mozilla's internals can be accessed by installing the Gecko Profiler add-on (more details on installation are available).
    3. -
- -
-

Reporting a Performance Problem has a step-by-step guide for obtaining a profile when requested by Firefox developers.

- -

Reporting a Thunderbird Performance Problem has a step-by-step guide for obtaining a profile when requested by Thunderbird developers.

-
- -

Compreender os Perfis

- -

You can check out some frequently asked questions about the Gecko Profilers.

- -

Here's a video of Ehsan examining some profiles:

- -

- -

- -
-

If there are features you would find helpful, please file a bug with details.

-
- -

Interface

- -

1. Timeline

- -

- -

The timeline has several rows of tracing markers (colored segments) which indicate interesting events. Hover over them to see more information. Below the tracing markers are rows corresponding with activity on a variety of threads.

- -
-

Tip: Threads that are annotated with "[default]" are in the parent (aka "UI", aka "browser chrome", aka "main") process and those annotated with "[tab]" are in the Web content (aka "child") processes.

-
- -
-

Tip: Long-running tasks in the parent process will block all input or drawing with the browser UI (aka "UI jank") whereas long-running tasks in the content process will block interactivity with the page but still allowing the user to pan and zoom around thanks to APZ.

-
- -
Tracing markers
- - - -
Ranges
- -

Timeline showing ranged breadcrumbs and zoom icon

- -

Ranges of time can be zoomed in on by clicking and dragging anywhere in the tracing marker or thread areas. Once a range is selected, a magnifying glass appears which zooms into that range. Clicking on a tracing marker will create a selection corresponding with its duration allowing for easy zooming in on interesting time ranges. As you zoom in on ranges, breadcrumbs are created allowing you to easily navigate back to previously-selected ranges or the entire profile (denoted as "Full Range").

- -
-

Tip: While zooming out to a previously-selected range deletes the narrower range, the browser back button can be used to restore the narrower range.

-
- -
Thread Timeline(s)
- -

Thread/Process Timelines: Below the tracing markers we have a list of profiled threads. These threads may come from different processes. In this case, we have the 'GeckoMain [default]' process' main thread, a content process' main thread, and the main thread of the compositor process. Each of these timelines is aligned with wall clock time. So, for example, when a thread is blocked, like 'GeckoMain [tab]', on a thread like 'GeckoMain [default]', we can see what's occurring on the latter thread that is preventing it from responding to the former.

- -

X (Time) axis: The timelines go from left to right as wall clock time increases along the X axis. Elements in the timeline are spaced at the sampling frequency with an attempt to align them with time. Factors such as sampling or stack-walking variance and system load can lead to sampling delays which manifest as gaps in the timeline.

- -
-

Nota: because this is a sampling profiler, be cautious when examining running time that is equal to the sampling interval. For very time-sensitive profiling, you may want to consider a non-sampling profiler.

-
- -

Y (Stack) axis: The Y axis is the stack depth, not the CPU activity. The change in stack height is useful to find patterns like long blocking calls (long flatlines) or very tall spiky blocks (recursive calls and JS). With more experience you can read profiles faster by recognizing patterns. Also note that you can click on timeline elements (the selected element gets darker when selected) and the tree view (see below) reflects the selected element.

- - - -

2. Call Tree

- -

- -

The Call Tree shows the samples organized by 'Running Time' which will show the data by wall clock time. There are lighter grey names to the right of tree elements that indicate where the code comes from. Be aware that elements can be from JavaScript, Gecko, or system libraries. Note that if some functions are not yet named properly, symbolication may not yet be finished.

- -
-

Dica: You can right-click on a function name to get an option to copy its name to the clipboard.

-
- -

A significant portion of time can be spent in idle, blocking calls like waiting for events. This is ideal for a responsive application to be ready to service incoming events. There are OS-specific waiting functions like NtWaitForMultipleObjects seen in the example above taken on Windows or mach_msg_trap on macOS.

- -
-

Dica: You can quickly go deeper into the call tree by holding down your right arrow key. Alternatively, expand an entire tree segment by holding Alt and clicking on the arrow to the left of the collapsed tree segment.

-
- -

As we progress into a more specific part of the tree, you'll notice that the 'Running time' decreases. This happens when a function has 2 or more non-trivial calls: the running time will be split between its children.

- -
-

Dica: Focus on one section of the tree by clicking on the "arrow-in-a-circle" icon that appears to the right of the tree element as you hover over it. A "tree breadcrumb" will appear similar to the range breadcrumbs noted above.

-
- -

Clicking the "JavaScript only" option will only show JavaScript code in the Call Tree. You could compare the time with this option checked and the total time to get an idea of how much time was spent running JS. Note that long-running JS function execution may not actually be taking as long as you think because further down the call stack there may be something like painting happening.

- -

Clicking the "Invert call stack" option will sort by the time spent in a function in descending order. Note that the running time here is only the running time of that particular frame and not the total of all called instances of that function. You can see the samples in the Timeline get darker as you select different functions in the Call Tree; these are samples that were taken when the selected function was running.

- -

"Filter stacks" will allow you to search for functions by name. One of the easiest ways to find slowness caused by a page's JS is to type its URL into the "Filter stacks" box. You can then select corresponding Call Tree entries and watch the Timeline for entries in the content process main thread that get darker as you select Call Tree entries.

- -
-

Tip: If things are blank elsewhere in the UI, you may have text entered into the "Filter stacks" box.

-
- -
Custom Annotations
- -

In bug 1334218 an annotation was added to PresShell::Paint to show the URL of the document being painted. These annotations are not too complex to add so if you would like something added, file a bug.

- -

3. Partilhar o perfil

- -

Click "Share..." > Share acknowledging that the URLs you had open and your Firefox extensions will be included in the profile data sent to the server. If you select a different time range, the URL revealed by pressing "Permalink" will change so that you can be sure the recipient of the URL will see the same things you are seeing.

- -

Dicas

- -

Understanding profiles can be difficult. If you're unfamiliar with Gecko's internals, you can click the JavaScript only button to see where your JavaScript code is slow. Each entry in the Call Tree shows a call stack and how much time is spent in that call stack. For example:In the results above we can see that we're spending ~287 milliseconds in Startup::XRE_InitChildProcess, 194 ms of which are spent in PVsync::Msg_Notify and all child functions that it calls. It is useful to scan down the "Running Time" column and look for when the time changes. While looking for performance problems, you're looking for the processes that are taking the most time; then you can figure out how to optimize them.

- -

Erros (Bugs) de Desempenho Comuns no Firefox

- -

Inefficient code that is on the reflow or restyle paths is often to blame for jank. So is code that is run often in the parent process or in parts of the codebase that apply to many users.

- -

Synchronous re-flow can be caused by JS that, for example, makes changes to the page content in a loop and queries about the layout of the page in that same loop.

- -

A PresShell:Flush means that we are either recomputing styles or recomputing layout. These sorts of flushes should be avoided if possible, as they can be quite expensive. Keep your eyes out for flushes like this that are blocking the main thread for a long time. If you notice these things happening in a loop, that's a bug to be fixed, since we're likely "layout thrashing".

- -

Some more tips and answers to common questions are available in a mid-2017 FAQ document.

- -

It's a good idea to search bugzilla before filing a bug about a performance problem in Firefox but sometimes it's hard to find issues that have already been reported. Therefore, it's usually a good idea to file a bug.

- -

Perfilar compilações (builds) locais do Windows

- -

If you built Firefox for Windows locally and you would like to use the local symbols with the profiler, you will need to run an additional tool; see Profiling with the Gecko Profiler and Local Symbols on Windows.

- -

Perfilar compilações (builds) Try

- -

The profiler currently doesn't really support symbolication for profiles from Try builds. For Linux builds, there seem to be symbols inside the binaries, which the profiler should pick up correctly. But on Windows and macOS, you'll have to do some tricks to make it work:

- -
    -
  1. Put your firefox build into a directory with the name dist.
    2. -
  2. Download the crashreporter symbols zip for your build. It should be one of the "artifacts" of the build job of your try build.
    3. -
  3. Unzip the crashreporter symbols into dist/crashreporter-symbols/.
    4. -
  4. Now profile as usual.
    5. -
- -

(This abuses the symbolication logic for local builds. It's at ext-geckoProfiler.js and may stop working at any time.)

- -

Perfilar móvel Firefox

- -
    -
  1. For local builds of Fennec, you should build with optimization and STRIP_FLAGS="--strip-debug" but NOT with --enable-profiling. Nightly builds are already built with the appropriate flags.
    2. -
  2. You'll need to have adb and arm-eabi-addr2line (which is part of the Android NDK) in your bash PATH, so use locate arm-eabi-addr2line (on Linux) or mdfind name:arm-eabi-addr2line (on OS X) and stick an export to its location in ~/.bash_profile. The extension will invoke bash to use adb and addr2line.
    3. -
  3. Install the latest pre-release build in your host machine's Firefox browser that has your phone reachable via ADB. This will add a icon in the top right of the browser.
    4. -
  4. Set devtools.debugger.remote-enabled to true in about:config for Fennec.
    5. -
  5. Select target Mobile USB and press Connect. The first run will take an additional 1 minute or so to pull in the required system libraries.
    6. -
- -

Profiling Firefox Startup

- -
    -
  1. Start your Firefox with the environment variable MOZ_PROFILER_STARTUP=1 set. This way the profiler is started as early as possible during startup.
    2. -
  2. Then capture the profile using the add-on as usual.
    3. -
- -

Startup profiling does not use the settings that you configured in the add-on's panel. It uses settings that can be configured with the environment variables MOZ_PROFILER_STARTUP_ENTRIES and MOZ_PROFILER_STARTUP_INTERVAL:

- - - -

Profiling JS benchmark (xpcshell)

- -
    -
  1. To profile the script run.js with IonMonkey (-I), type inference (-n) and JäegerMonkey (-m). Thgis requires the following command: - - 
    $ xpcshell -m -I -n -e '
-    const Ci = Components.interfaces;
-    const Cc = Components.classes;
-    var profiler = Cc["@mozilla.org/tools/profiler;1"].getService(Ci.nsIProfiler);
-    profiler.StartProfiler(
-      10000000 /* = profiler memory */,
-      1 /* = sample rate: 100µs with patch, 1ms without */,
-      ["stackwalk", "js"], 2 /* = features, and number of features. */
-    );
-  ' -f ./run.js -e '
-    var profileObj = profiler.getProfileData();
-    print(JSON.stringify(profileObj));
-  ' | tail -n 1 > run.cleo
    - The xpcshell output all benchmark information and on its last line it output the result of the profiling, you can filter it with tail -n 1 and redirect it to a file to prevent printing it in your shell.  The expected size of the output is around 100 of MB.
    2. -
  2. To add symbols to your build, you need to call ./scripts/profile-symbolicate.py available in B2G repository. - 
    $ GECKO_OBJDIR=<objdir> PRODUCT_OUT=<objdir> TARGET_TOOLS_PREFIX= \
-    ./scripts/profile-symbolicate.py -o run.symb.cleo run.cleo
    -
    3. -
  3. Clone Cleopatra and start the server with ./run_webserver.sh.
    4. -
  4. Access Cleopatra from your web browser by loading the page localhost:8000, and upload run.symb.cleo to render the profile with most of the symbol information.
    5. -
- -

Native stack vs. Pseudo stack

- -

The profiler periodically samples the stack(s) of thread(s) in Firefox, collecting a stack trace, and presents the aggregated results using the Cleopatra UI.  Stack traces can be collected into two different ways: Pseudostack (the default) or Nativestack.

- -

Native stack

- -

Native stacks are the normal stacks most developers are used. They are the default.

- -

Pseudostack

- -

The pseudostack uses function entry/exit tags added by hand to important points in the code base.  The stacks you see in the UI are chains of these tags.  This is good for highlighting particularly interesting parts of the code, but they miss out on un-annotated areas of the code base, and give no visibility into system libraries or drivers.

- -

Tagging is done by adding macros of the form AUTO_PROFILER_LABEL("NAMESPACE", "NAME"). These add RAII helpers, which are used by the profiler to track entries/exits of the annotated functions.  For this to be effective, you need to liberally use AUTO_PROFILER_LABEL throughout the code. See GeckoProfiler.h for more variations like AUTO_PROFILER_LABEL_DYNAMIC.

- -

Because of the non-zero overhead of the instrumentation, the sample label shouldn't be placed inside hot loops.  A profile reporting that a large portion is spent in "Unknown" code indicates that the area being executed doesn't have any sample labels.  As we focus on using this tool and add additional sample labels coverage should improve.

- -

Sharing, saving and loading profiles

- -

After capturing and viewing a profile you will see "Share..." and "Save as file..." buttons in the top-right of the window. Sharing will upload your profile to perf-html.io and make it public. More information on sharing profiles is available.

- -

Profiling a hung process

- -

It is possible to get profiles from hung Firefox processes using lldb1.

- -
    -
  1. After the process has hung, attach lldb.
    2. -
  2. Type in2, : - 
    p (void)profiler_save_profile_to_file("somepath/profile.txt")
    -
    3. -
  3. Clone mstange’s handy profile analysis repository.
    4. -
  4. Run: - 
    python symbolicate_profile.py somepath/profile.txt
    - -

    To graft symbols into the profile. mstange’s scripts do some fairly clever things to get those symbols – if your Firefox was built by Mozilla, then it will retrieve the symbols from the Mozilla symbol server. If you built Firefox yourself, it will attempt to use some cleverness3 to grab the symbols from your binary.

    - -

    Your profile will now, hopefully, be updated with symbols. Upload it for further analysis!

    - -

    I haven’t yet had the opportunity to try this, but I hope to next week. I’d be eager to hear people’s experience giving this a go – it might be a great tool in determining what’s going on in Firefox when it’s hung!

    -
    5. -
- -

Profiling Threads

- -

The Gecko Profiler has rudimentary support for profiling multiple threads. To enable it, check the 'Multi-Thread' box then enter one or more thread names into the textbox beside it. Thread names are the strings passed to the base::Thread class at initialization. At present there is no central list of these thread names, but you can find them by grepping the source.

- -

Examples: 1 2

- -

If the filter you entered is invalid, no threads will be profiled. You can identify this by hitting Analyze (Cleopatra will show you an error message). If the filter is left empty, only the main thread is captured (as if you had not enabled Multi-Thread.)

- -

Profiler Features

- -

The profiler supports several features. These are options to gather additional data in your profiles. Each option will increase the performance overhead of profiling so it's important to activate only options that will provide useful information for your particular problem to reduce the distortion.

- -

Stackwalk

- -

When taking a sample the profiler will attempt to unwind the stack using platform specific code appropriate for the ABI. This will provide an accurate callstack for most samples. On ABIs where framepointers are not avaiable this will cause a significant performance impact.

- -

JS Profiling

- -

Javascript callstacks will be generated and interleaved with the c++ callstacks. This will introduce an overhead when running JS.

- -

GC Stats

- -

Will embed GC stats from 'javascript.options.mem.notify' in the profile.

- -

Main Thread IO

- -

This will interpose file I/O and report them in the profiles.

- -

Multi-Thread

- -

This will sample other threads. This fields accept a comma seperated list of thread names. A thread can only be profiled if it is registered to the profiler.

- -

GPU

- -

This will insert a timer query during compositing and show the result in the Frames view. This will appropriate how much GPU time was spent compositing each frame.

- -

Layers & Texture

- -

The profiler can be used to view the layer tree at each composite, optionally with texture data. This can be used to debug correctness problems.

- -

Viewing the Layer Tree

- -

To view the layer tree, the layers.dump pref must be set to true in the Firefox or B2G program being profiled.

- -

In addition, both the compositor thread and the content thread (in the case of B2G, the content thread of whichever app you're interested in) must be profiled. For example, on B2G, when profiling the Homescreen app, you might start the profiler with:

- -
./profile.sh start -p b2g -t Compositor && ./profile.sh start -p Homescreen
-
- -

Having gotten a profile this way, the layer tree for a composite can be seen by clicking on a composite in the "Frames" section of Cleopatra (you may need to a sub-range of samples to make individual composites large enough to be clicked). This will activate the "LayerTree" tab:

- -

Screenshot of layer tree view in Cleopatra, with no textures.

- -

In this screenshot, Composite #143 has been selected. The layer tree structure can be seen in the left panel. It contains, for each layer, the type of the layer, and various metrics about the layer, such as the visible region and any transforms. In the right panel, a visualization of the layer tree (based entirely on the aforementioned metrics) is shown. Hovering over a layer in the left panel highlights the layer in the right panel. This is useful for identifying what content each layer corresponds to. Here, I'm hovering over the last layer in the layer tree (a PaintedLayerComposite), and a strip at the top of the right panel is highlighted, telling me that this layer is for the system notification bar in B2G.

- -

Viewing Textures

- -

Sometimes, it's useful to see not only the structure of the layer tree for each composite, but also the rendered textures for each layer. This can be achieved by additionally setting the layers.dump-texture pref to true, or by adding -f layersdump to the profiler command line (the latter implies both the layers.dump and layers.dump-texture prefs).

- -
-

Warning: Dumping texture data slows performance considerably, and requires a lot of storage for the profile files. Expect rendering to happen at a significantly reduced frame rate when profiling this way, and keep the duration of the capture short, to ensure the samples of interest aren't overwritten.

-
- -

Here's how the Layer Tree view looks in Cleopatra with texture data:

- -

Screenshot of layer tree view in Cleopatra, with textures.

- -

This time, the visualization in right panel shows the actual textures rather than just the outlines of the layers. This can be very useful for debugging correctness problems such as a temporary visual/rendering glitch, because it allows you to find the precise composite that shows the glitch, and look at the layer tree for that composite.

- -

Visualizing a layer tree without a profile

- -

If you have a layer dump from somewhere (such as from adb logcat on B2G), you can get Cleopatra to visualize it (just the structure of course, not textures) without needing a profile. To do so, paste the layer dump into the "Enter your profile data here" text field on the front page of Cleopatra:

- -

Screenshot of front page of Cleopatra, with pasted layer dump.

- -

The resulting "profile" will have the Layer Tree view enabled (but nothing else). This is useful in cases where you want to gain a quick visual understanding of a layer dump without having to take a profile.

- -
-

On B2G, each line of a layer dump in adb logcat output is prefixed with something like I/Gecko   (30593):. Cleopatra doesn't currently understand this prefix, so it needs to be removed before pasting.

-
- -

Display List

- -

Dump the display list after each refresh with the texture data. This can be used to debug correctness problems.

- -

Contribuir

- - diff --git a/files/pt-pt/mozilla/persona/index.html b/files/pt-pt/mozilla/persona/index.html deleted file mode 100644 index 12a9d58796..0000000000 --- a/files/pt-pt/mozilla/persona/index.html +++ /dev/null @@ -1,153 +0,0 @@ ---- -title: Persona -slug: Mozilla/Persona -translation_of: Archive/Mozilla/Persona ---- -
-

Acompanhe ou peça ajuda!

-

Siga nosso blog, join our mailing list, or find us in #identity on IRC.

-
-

Mozilla Persona é um sistema de autenticação completamente descentralizado e seguro para a web baseado no protocolo aberto BrowserId. Para garantir que Persona funcione em todo lugar e para todos, Mozilla atualmente opera uma pequena suíte de serviços opcionais, centralizados.

-

Por quê você e seu site deveriam usar Persona?

-
    -
  1. Persona elimina completamente senhas para sites específicos, libertando usuários e sites do fardo de criar, gerir e armazenar seguramente senhas.
    2. -
  2. Persona é fácil de usar. Com apenas dois cliques um usuário Persona pode se cadastrar em um novo site, como Voost ou The Times Crossword, ignorando o desgaste associado à criação de contas.
    3. -
  3. Persona é fácil de implementar. Desenvolvedores podem adicionar Persona à um site em uma única tarde.
    4. -
  4. Melhor de tudo, não há bloqueio. Desenvolvedores adquirem um endereço de email para todos seus usuários, e usuários podem usar qualquer endereço de email com Persona.
    5. -
  5. Persona é baseado no protocolo BrowserID. Quando os navegadores populares implementarem BrowserID, eles não irão precisar depender da Mozilla para logar.
    6. -
-

Leia e comece!

-
- Note: Persona is in active development. Follow our blog to learn about new features, or join our mailing list and offer your feedback!
-

Using Persona on your site

- - - - - - - - - - - -
-

Getting started

-
-
- Why Persona?
-
- Learn about reasons to support Persona on your site, and how it compares to other identity and authentication systems.
-
- Quick setup
-
- A quick walkthrough showing how to add Persona to your website.
-
- 		-

Persona API reference

-
-
- The navigator.id API reference
-
- Reference for the navigator.id object, which web developers can use to integrate Persona into sites.
-
- Verification API reference
-
- Reference for the remote verification API hosted at https://verifier.login.persona.org/verify.
-
-
-

Guides

-
-
- Security considerations
-
- Practices and techniques to make sure your Persona deployment is secure.
-
- Browser compatibility
-
- Learn exactly which browsers support Persona.
-
- Internationalization
-
- Learn how Persona handles different languages.
-
- 		-

Resources

-
-
- Libraries and plugins
-
- Find a drop-in library for your favorite programming language, web framework, blog, or content management system.
-
- The Persona cookbook
-
- Example source code for Persona sites. Includes snippets in PHP, Node.JS, and more.
-
- Branding resources
-
- Sign in buttons and other graphics to help present Persona to your users.
-
-
-

 

- - - - - - - -
-

Information for Identity Providers

-

If you're an email provider or another identity-providing service, check out the links below to learn about becoming a Persona Identity Provider.

-
-
- IdP Overview
-
- A high level view of Persona Identity Providers.
-
- Implementing an IdP
-
- A detailed guide to the technical details of becoming an IdP.
-
- Development tips
-
- A set of tips and tricks useful while developing a new Identity Provider.
-
- .well-known/browserid
-
- An overview of the structure and purpose of the .well-known/browserid file, which IdPs use to advertise their support for the protocol.
-
- 		-

The Persona Project

-
-
- Glossary
-
- BrowserID and Persona terminology defined.
-
- FAQ
-
- Answers to common questions.
-
- Protocol overview
-
- A mid-level technical overview of the underlying BrowserID protocol.
-
- Crypto
-
- A look at the cryptographic concepts behind Persona and BrowserID.
-
- The Spec
-
- Deep technical details live here.
-
- The Persona Website
-
- To get Persona going, we're hosting three services at https://login.persona.org: a fallback Identity Provider, a portable implementation of the {{ domxref("navigator.id") }} APIs, and an identity assertion verification service.
-
- The Persona Source Code
-
- The code behind the Persona website lives in a repository on GitHub. Patches welcome!
-
-
-

 

diff --git a/files/pt-pt/mozilla/phishing/index.html b/files/pt-pt/mozilla/phishing/index.html deleted file mode 100644 index e553586c69..0000000000 --- a/files/pt-pt/mozilla/phishing/index.html +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: 'Phishing: uma breve definição' -slug: Mozilla/Phishing -tags: - - Segurança -translation_of: Mozilla/Phishing ---- -

Em 2014, a MSCI estimatou um impacto global anual do phishing e várias formas de roubo de identidade, chegando a US $5 bilhões. O impacto não melhorou desde então.

- -

Phishing is an attempt to collect sensitive information, such as usernames, passwords, and financial details by disguising as a trustworthy entity online.

- -

A relatively simple, yet effective, phishing scheme is sending an email with a fake invoice of a person’s favorite shopping site. This email will usually contain a link pretending to lead to the original service, but in reality, taking the victim to an attacker-controlled website. The login portal might resemble the trusted website's login page very closely, and convince users to enter their credentials, letting others hijack their account.

- -

Contramedidas passadas e atuais

- -

Various technical, and social approaches, exist to combat phishing attacks. None of these are sufficient by themselves, so we see a mix of these deployed by various services. The following is a non-exhaustive list of the most common approaches.

- -

Deitando a culpa aos utilizadores

- -

Some quick-to-implement, and cost-effective solutions, hold users accountable for their actions instead of restricting what’s technically possible. Earlier responses by affected banks, and payment providers, was to attempt educating users to not click links in emails, along with requesting to verify email legitimacy through checking for relevant personal information.

- -

Another solution is to strengthen logins with pictures, or colored words, often chosen when signing up for a service. Users look for these when logging in, and only enter their credentials when they recognize the user defined pictures or words.

- -

A study on the efficacy of security indicators, presented at the 2007 IEEE Symposium on Security and Privacy, suggests that the above countermeasures fail to protect the majority of users. This too, includes missing HTTPS or EV certificate indicators in a browser’s navigation bar.

- -

Serviços assumindo responsabilidade

- -

Technical solutions can be more efficient if implemented to protect millions of users automatically. As most phishing attacks start with unsolicited email messages, a clear starting point is improving spam filters, thus reducing the number of fraudulent messages reaching users.

- -

Web browser vendors too, are interested in protecting their users from phishing. After all, the browser plays an essential role in the scheme: a fake website is loaded in a browser and here is the maker’s last chance to preventing fraud. Since version 2.0, Firefox has used Google’s SafeBrowsing service, to detect known web forgeries, and display an alert instead of the fraudulent website.

- -

Autenticação de Dois Fatores

- -

None of the above anti-phishing measures address the basic problem: username/password combinations are often enough to impersonate users.

- -

Enter the world of second factors. A second factor is something a user possesses to further authenticate with a service. For example, a USB token, Bluetooth device, mobile phone, or simply a key stored on a separate device. The first factor is usually the password and username. If both factors don’t match, the service will reject authentication requests.

- -

Criptografia de Chave Pública

- -

Many services will soon support W3C Web Authentication, a powerful technology to evade phishing, based on public key cryptography. Web Authentication supports millions of readily avilable FIDO U2F USB security keys, and will support the more advanced FIDO 2.0 keys, once made available.

- -

Verificação via Mensagem de Texto

- -

If a service supports verification, via SMS, it sends a text message with a one-time PIN to the user’s phone number. The user then enter this PIN after the Web service verifies the username and password. This was chosen as an  early second factor 'protocol' as text messages are widely supported, however, even NIST no longer recommends SMS verification. The SS7 telephony system is vulnerable, making eavesdropping, or rerouting text messages quite trivial.

- -

Algoritmos de Palavra-passe Única

- -

A better way to use phones as second factor, are One-Time Password (OTP) protocols, like TOTP and HOTP. At service registration, the provider will often generate a QR code to be read by an OTP app. This QR code is nothing more than a random, secret key, that is stored on the user’s phone. After verifying username and password, the user is prompted to open the OTP app and enter the corresponding 6-digit code, representing a hashed version of the secret key and a nonce - potentially time-based.

- -

OTP is the most widely supported second factor schemes and can be used to secure your most important accounts. Unfortunately, some users still feel it's too tedious unlocking a phone, opening the OTP app, and manually typing a few digits each time a provider requests a new token. This can be phished by an attacker, though with TOTP apps the attacker has limited time to make their unauthorized login.

diff --git a/files/pt-pt/mozilla/projects/emscripten/index.html b/files/pt-pt/mozilla/projects/emscripten/index.html deleted file mode 100644 index c2c6e1a2dc..0000000000 --- a/files/pt-pt/mozilla/projects/emscripten/index.html +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Emscripten -slug: Mozilla/Projects/Emscripten -tags: - - C++ - - Emscripten - - JavaScript - - LLVM -translation_of: Mozilla/Projects/Emscripten ---- -

Emscripten é um compilador LLVM para JavaScript. Este utiliza bytecode do LLVM (por exemplo, gerado a partir de C/C++, utilizando Clang, ou de outra linguagem) e o compila no JavaScript, que pode ser executado na Web.

- -
-

Importante: esta página fornece uma breve introdução sobre o que Emscripten é. Para começar com Emscripten, vá para a Wiki oficial do Emscripten.

-
- -

Ao utilizar o Emscripten, pode

- - - -

Emscripten produz código nativo imediatamente disponível na Web: uma plataforma que é padrão, tem inúmeras implementações independentes e é interpretada em todo o lado desde PC's a iPad's.

- -

Com Emscripten, programadores de C/C++ não têm o alto custo de transcrever o código manualmente para JavaScript — ou ter que aprender JavaScript sequer. Programadores web também beneficiam, dado que podem usar milhares de bibliotecas nativas já existentes nos seus sites.

- -

Praticamente qualquer base de código portátil de C ou C++ pode ser compilada para JavaScript usando Emscripten, variando desde jogos de alto performance que precisam de renderizar gráficos, tocar sons, carregar e processar ficheiros até aplicações de frameworks como Qt.

- -

Emscripten gera código rápido — o formato de saída é asm.js, um subset de JavaScript que consegue executar perto de velocidades nativas em muitos casos.

- -
-

Nota: Parece interessante? Ler mais sobre Emscripten e experimentar algumas demonstrações, e depois começar a usar.

-
- -

Outros artigos de interesse na MDN

- - diff --git a/files/pt-pt/mozilla/projects/index.html b/files/pt-pt/mozilla/projects/index.html deleted file mode 100644 index 7e832a9616..0000000000 --- a/files/pt-pt/mozilla/projects/index.html +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Projects -slug: Mozilla/Projects -tags: - - Landing - - Mozilla - - NeedsContent - - NeedsTranslation - - Projects - - TopicStub -translation_of: Mozilla/Projects ---- -

Below you'll find links to documentation about various Mozilla projects; these are often parts of Firefox or other products, but may also be used in other projects as well.

-

{{ LandingPageListSubpages() }}

diff --git a/files/pt-pt/mozilla/projects/mailnews/index.html b/files/pt-pt/mozilla/projects/mailnews/index.html deleted file mode 100644 index 79fc847667..0000000000 --- a/files/pt-pt/mozilla/projects/mailnews/index.html +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: MailNews -slug: Mozilla/Projects/MailNews -translation_of: Mozilla/Projects/MailNews ---- -

MailNews significa "Correio e Listas de Notícias". MailNews é o back end de partes de mensagem do SeaMonkey e Thunderbird. Este fornece um número de funções e capacidades, incluindo:

- - - -

O código de MailNews reside na diretoria / mailnews/ de comm-central.

- -

 

- -
-
-
-
AsyncTestUtils extended framework
-
The AsyncTestUtils Extended Framework is one mechanism for testing the MailNews component of Thunderbird. See MailNews automated testing for a description of the other testing mechanisms.
-
Leak And Bloat Tests
-
This page describes how to perform tests that measure memory leaks and bloat for MailNews and its sub-components.
-
- -
-
-
- -
-
-
MailNews automated testing
-
Automated testing is an increasingly significant and important part of MailNews development. It allows reviewers to quickly pick up regressions in patches and helps developers to think about different cases.
-
-
-
- -

 

- -

Consulte as páginas etiquetadas de MailNews para informação additional especifica de MailNews.

diff --git a/files/pt-pt/mozilla/projects/rhino/index.html b/files/pt-pt/mozilla/projects/rhino/index.html deleted file mode 100644 index b84b26f977..0000000000 --- a/files/pt-pt/mozilla/projects/rhino/index.html +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Rhino -slug: Mozilla/Projects/Rhino -tags: - - JavaScript - - Mozilla - - Rhino -translation_of: Mozilla/Projects/Rhino ---- -

Image:rhino.jpg

- -

Rhino é uma implementação de código fonte aberto da linguagem JavaScript inteiramente desenvolvida em Java. Tipicamente, destina-se a ser incluída em aplicações Java como forma de providenciar funcionalidades de scripting ao utilizador final. Foi incluída no pacote J2SE como o scripting engine disponível por defeito.

- -

Baixar Rhino

- -

Como obter código fonte e ficheiros binários. 

- -

Documentação Rhino

- -

Informação sobre Rhino para desenvolvedores de scripts.

- -

Ajuda Rhino

- -

Alguns recursos para o caso de entrar em dificuldades.

diff --git a/files/pt-pt/mozilla/projects/thunderbird/localizacao_thunderbird/index.html b/files/pt-pt/mozilla/projects/thunderbird/localizacao_thunderbird/index.html deleted file mode 100644 index b639359af3..0000000000 --- a/files/pt-pt/mozilla/projects/thunderbird/localizacao_thunderbird/index.html +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: Localização do Thunderbird -slug: Mozilla/Projects/Thunderbird/Localizacao_Thunderbird -tags: - - Localização - - Thunderbird 3 - - Tradução - - thunderbird -translation_of: Mozilla/Projects/Thunderbird/Thunderbird_Localization ---- -

Esta página é destinada aos tradutores atuais e futuros do Thunderbird, o cliente de e-mail e usenet da Mozilla Messaging. Abrange muitos aspetos que um tradutor do Thunderbird deverá conhecer como ferramentas necessárias, como obter informação sobre eventos relevantes à localização e vários outros itens de interesse.

- -

Criar uma localização do Thunderbird

- -

Creating a new localization (Mercurial) - This article describes how you can create a new localization for Thunderbird.

- -

Sobre repositórios e ramificações

- -

There are 3 active repositories for Thunderbird development. Thunderbird development work is merged from one branch to the next every six weeks.

- - - -

Most locales will being working on comm-aurora. This repository/branch is stable with respect to strings for each six week period. Completing work here means it is ready for the first beta, and you won't need to work on beta branch. Your work will also automatically be carried forward.

- -

Requisitos da Localização

- -

There are not significant restrictions on what locales can change. However, we need to work together on providing search engines for Thunderbird users to use to get the right balance of search engines and the correct options set. For further information see this page.

- -

Painel da Localização

- -

The localization dashboard for Thunderbird gives localizers a precise overview of the current status of their localization. Detailed information is available on the l10n dashboard page.

- -

A localization will added to the l10n dashboard on request when it has reached a high-level of completion (> 80%) as shown by the compare-locales output. To request the addition of your locale to the dashboard, file a bug in the Thunderbird product/Build Config component.

- -

Obter informação relevante de l10n

- -

Fóruns de Discussão e Listas de Discussão

- -

Localizers of Thunderbird should read the localization newsgroups (mozilla.dev.l10n.announce mozilla.dev.l10n) to stay informed of Thunderbird-specific and general l10n-related items of interest to them. They are further encouraged to read the Thunderbird development newsgroup (mozilla.dev.apps.thunderbird) to stay informed of recent Thunderbird-related developments.

- -

These newsgroups can also be accessed via the dev-l10n-announce@lists.mozilla.org, dev-l10n@lists.mozilla.org (localization mailinglist) or dev-apps-thunderbird@lists.mozilla.org (Thunderbird development mailinglist) mailinglists, which mirror the newsgroups mentioned above. You can subscribe to or unsubscribe from these mailinglists via the web interface at lists.mozilla.org.

- -

Bugzilla

- -

Localizers should watch the thunderbird@localization.bugs mail address (or its alias :tb-l10n) to stay current on bugs that might affect Thunderbird localizers. This can be done by adding this mail address to the "User Watching" section of your Email preferences in bugzilla.

- -

Algumas hiperligações úteis

- - - -

Tiers de Idioma

- -

Locale tiers reflect locales that we need to have in a good state for release. There are 10 locales in tier 1, which are the most important for Thunderbird, because of their number of Thunderbird users or potential for growth.

- -

These locales are being treated as first-class citizens, as important as en-US, which is to say that any Tier 1 locale that does not meet the requirements may block a final release of Thunderbird.

- -

Tier 1

- -

The following are P1 (priority 1) locales in order of priority:

- -
* de             -  alemão
-* fr             -  francês
-* ja, ja-JP-mac  -  japonês
-* en-GB          -  inglês (UK)
-* es-ES          -  espanhol (continente Europeu)
-* it             -  italiano
-* pl             -  polaco
-* ru             -  russo
-* nl             -  holandês
-* pt-BR          -  português (Brasil)
-
- -

Tier 2

- -

Todas as outras localidades suportadas que estão na categoria do Tier 2.

diff --git a/files/pt-pt/mozilla/tech/index.html b/files/pt-pt/mozilla/tech/index.html deleted file mode 100644 index 36bcd94c3a..0000000000 --- a/files/pt-pt/mozilla/tech/index.html +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Tecnologias da Mozilla -slug: Mozilla/Tech -tags: - - Landing - - Mozilla - - Referencia - - TopicStub - - XUL -translation_of: Mozilla/Tech ---- -

A Mozilla tem várias tecnologias, utilizadas como componentes dos seus projetos. Estas estão documentadas aqui.

- -

{{LandingPageListSubpages}}

diff --git a/files/pt-pt/mozilla/tech/places/index.html b/files/pt-pt/mozilla/tech/places/index.html deleted file mode 100644 index 18e2e0cd95..0000000000 --- a/files/pt-pt/mozilla/tech/places/index.html +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Places -slug: Mozilla/Tech/Places -tags: - - Desenvolvimento da Mozilla - - Extensões - - Extras - - Places -translation_of: Mozilla/Tech/Places ---- -

{{ Fx_minversion_header(3) }}

- -

Places é o sistema de gestão de marcadores e histórico introduzido no Firefox 3. It offers increased flexibility and complex querying to make handling the places the user goes easier and more convenient. It also includes new features including favicon storage and the ability to annotate pages with arbitrary information. It also introduces new user interfaces for managing all this information; see {{ interwiki('wikimo', 'Places', 'Places on the Mozilla wiki') }}.

- -

Places armazena os seus dados numa base de dados SQLite, utilizando as interfaces de mozStorage.

- - - - - - - - -
-

Documentação

- -
-
Places migration guide
-
Migrating existing code to use the Places API.
-
Manipulating bookmarks using Places
-
Examples for how to work with bookmarks using the Places API.
-
Using the Places tagging service
-
How to use the tagging service.
-
Using the Places history service
-
How to access history information using the Places API.
-
Using the Places favicon service
-
How to manipulate favicons using the Places API.
-
Using the Places livemark service
-
How to create and manage livemarks.
-
Using the Places annotation service
-
How to work with the annotation service.
-
Using the Places keywords API
-
How to manage Places keywords
-
- -
-
Querying Places
-
How to query the bookmarks and history system with specific parameters.
-
Retrieving part of the bookmarks tree
-
How to fetch a section of the bookmarks tree using queries.
-
Displaying Places information using views
-
How to use Places views to display Places data in your own applications or extensions.
-
Places utilities for JavaScript
-
A library of convenient routines that make it easier to work with Places.
-
Places Database troubleshooting
-
How to deal with a corrupt places.sqlite database.
-
- -

View All...

- 		- - -
-
The Places database
-
High-level overview of the Places database design.
-
History Service Design
-
Design of the history service.
-
Bookmark Service Design
-
Design of the bookmarks service.
-
Annotation Service Design
-
Design of the annotation service.
-
The Places "frecency" algorithm
-
The algorithm behind the Places location bar (sometimes called the "awesomebar").
-
-
diff --git a/files/pt-pt/mozilla/tech/xpcom/armazenamento/index.html b/files/pt-pt/mozilla/tech/xpcom/armazenamento/index.html deleted file mode 100644 index 2410a763e4..0000000000 --- a/files/pt-pt/mozilla/tech/xpcom/armazenamento/index.html +++ /dev/null @@ -1,372 +0,0 @@ ---- -title: Armazenamento -slug: Mozilla/Tech/XPCOM/Armazenamento -tags: - - API de Kit de Ferramentas - - Armazenamento - - Guia(2) - - Interfaces -translation_of: Mozilla/Tech/XPCOM/Storage ---- -

Armazenamento é uma API de base de dados SQLite. Está disponível para os callers de confiança, ou seja, apenas extensões e componentes do Firefox.

- -

The API is currently "unfrozen", which means it is subject to change at any time; in fact, it has changed somewhat with each release of Firefox since it was introduced, and will likely continue to do so for a while.

- -
Nota: Storage is not the same as the DOM:Storage feature which can be used by web pages to store persistent data or the Session store API (an XPCOM storage utility for use by extensions).
- -

Iniciação

- -

This document covers the Storage API and some peculiarities of SQLite. It does not cover SQL or "regular" SQLite. You can find some very useful links in the See also section however. For Storage API help, you can post to mozilla.dev.apps.platform on the news server news.mozilla.org. To report bugs, use Bugzilla.

- -

The overall procedure for use is:

- -
    -
  1. Get the Storage service - {{ interface("mozIStorageService") }}.
    2. -
  2. Open a connection to the database of your choice - {{ interface("mozIStorageConnection") }}.
    3. -
  3. Create statements to execute on the connection - {{ interface("mozIStorageStatement") }}.
    4. -
  4. Bind parameters to a statement as necessary.
    5. -
  5. Execute the statement.
    6. -
  6. Check for errors.
    7. -
  7. Reset the statement.
    8. -
- -

Abrir uma ligação

- -

JavaScript example of opening my_db_file_name.sqlite in the profile directory:

- -
Components.utils.import("resource://gre/modules/Services.jsm");
-Components.utils.import("resource://gre/modules/FileUtils.jsm");
-
-let file = FileUtils.getFile("ProfD", ["my_db_file_name.sqlite"]);
-let dbConn = Services.storage.openDatabase(file); // Will also create the file if it does not exist
-
- -

Likewise, the C++ would look like this:

- -
nsCOMPtr<nsIFile> dbFile;
-rv = NS_GetSpecialDirectory(NS_APP_USER_PROFILE_50_DIR,
-                            getter_AddRefs(dbFile));
-NS_ENSURE_SUCCESS(rv, rv);
-rv = dbFile->Append(NS_LITERAL_STRING("my_db_file_name.sqlite"));
-NS_ENSURE_SUCCESS(rv, rv);
-nsCOMPtr<mozIStorageService> dbService =
-  do_GetService(MOZ_STORAGE_SERVICE_CONTRACTID, &rv);
-NS_ENSURE_SUCCESS(rv, rv);
-
-nsCOMPtr<mozIStorageConnection> dbConn;
-rv = dbService->OpenDatabase(dbFile, getter_AddRefs(dbConn));
-NS_ENSURE_SUCCESS(rv, rv);
-
- -
Note: MOZ_STORAGE_SERVICE_CONTRACTID is defined in {{ Source("storage/build/mozStorageCID.h") }}.
- -

{{ Warning("It may be tempting to give your database a name ending in '.sdb' for sqlite database, but this is not recommended. This extension is treated specially by Windows as a known extension for an 'Application Compatibility Database' and changes are backed up by the system automatically as part of system restore functionality. This can result in significantly higher overhead file operation.") }}

- -

Fechar uma ligação

- -

To close a connection on which only synchronous transactions were performed, use the mozIStorageConnection.close() method. If you performed any asynchronous transactions, you should instead use the mozIStorageConnection.asyncClose() method. The latter will allow all ongoing transactions to complete before closing the connection, and will optionally notify you via callback when the connection is closed.

- -

Statements

- -

This section demonstrates how you can execute SQL statements on your database. For a complete reference see {{ interface("mozIStorageStatement") }}.

- -

Creating a Statement

- -

There are actually two ways to execute a statement. You should choose the right one based on your needs.

- -

No Results to be Returned

- -

If you do not need to get any results back, you can use {{ ifmethod("mozIStorageConnection", "executeSimpleSQL") }} API like this in JavaScript:

- -
dbConn.executeSimpleSQL("CREATE TEMP TABLE table_name (column_name INTEGER)");
-
- -

Similarly, the C++ looks like this:

- -
rv = mDBConn->ExecuteSimpleSQL(NS_LITERAL_CSTRING("CREATE TEMP TABLE table_name (column_name INTEGER)"));
-NS_ENSURE_SUCCESS(rv, rv);
- -

Results to be Returned

- -

However, if you need to get results back, you should create the statement with the {{ ifmethod("mozIStorageConnection", "createStatement") }} API like this in JavaScript:

- -
var statement = dbConn.createStatement("SELECT * FROM table_name WHERE column_name = :parameter");
-
- -

This example uses a named placeholder called "parameter" to be bound later (described in {{ anch("Binding Parameters") }}). Similarly, the C++ looks like this:

- -
nsCOMPtr<mozIStorageStatement> statement;
-rv = dbConn->CreateStatement(NS_LITERAL_CSTRING("SELECT * FROM table_name WHERE column_name = ?1"),
-                             getter_AddRefs(statement));
-NS_ENSURE_SUCCESS(rv, rv);
-
- -

This example uses the numbered placeholder indexed by zero for a parameter to be bound later (described in {{ anch("Binding Parameters") }}).

- -

{{ Note("Numerical indexes for parameters are always one less than the number you write in the SQL. The use of numerical indexes for parameters is strongly discouraged in JavaScript where named parameters are much easier to use.") }}

- -

{{ Note("If you need to execute a statement multiple times, caching the result of createStatement will give you a noticeable performance improvement because the SQL query does not need to be parsed each time.") }}

- -

Binding Parameters

- -

In order to effectively use the statements that you create, you have to bind values to the parameters you placed in the statement. A given placeholder can appear multiple times in the same statement, and all instances of it will be replaced with the bound value. If you neglect to bind a value to a parameter, it will be interpreted as NULL.

- -
You should never try to construct SQL statements on the fly with values inserted in them. By binding the parameters, you prevent possible SQL injection attacks since a bound parameter can never be executed as SQL.
- -

Binding One Set of Parameters

- -

If you only have one row to insert, or are using the synchronous API you'll need to use this method. In JavaScript, there is a useful helper object ({{ interface("mozIStorageStatementParams") }}) available ({{ gecko_minversion_inline("1.9.1") }}) that makes binding parameters much easier:

- -
var statement = dbConn.createStatement("SELECT * FROM table_name WHERE id = :row_id");
-statement.params.row_id = 1234;
-
- -

Use :boundParameterName the same way for numeric and non-numeric columns. Do not put the :boundParameterName within apostrophes, because that the binding mechanism does that for you. You can still use this helper object by manually creating the statement wrapper, {{ interface("mozIStorageStatementWrapper") }}, which is provided in Gecko 1.9.1 and later.

- -

Using named parameters in C++ is a lot more difficult, so it's generally accepted to use numerical placeholders instead. The example below uses {{ ifmethod("mozIStorageStatement", "bindInt32Parameter") }}. The full list of binding functions can be found with the {{ interface("mozIStorageStatement") }} documentation.

- -

C++ example:

- -
nsCOMPtr<mozIStorageStatement> statement;
-rv = mDBConn->CreateStatement(NS_LITERAL_CSTRING("SELECT * FROM table_name WHERE id = ?1"),
-                              getter_AddRefs(statement));
-NS_ENSURE_SUCCESS(rv, rv);
-
-rv = statement->BindInt32Parameter(0, 1234);
-NS_ENSURE_SUCCESS(rv, rv);
-
- -

{{ Note("Numerical indexes for parameters are always one less than the number you write in the SQL. The use of numerical indexes for parameters is strongly discouraged in JavaScript where named parameters are much easier to use.") }}

- -

Binding Multiple Sets of Parameters

- -

{{ gecko_minversion_header("1.9.2") }}

- -

Starting in Gecko 1.9.2 (Firefox 3.6), there's a new, more convenient way to bind multiple sets of parameters at once prior to executing your statement asynchronously. This API is only available for asynchronous execution.

- -
let stmt = dbConn.createStatement("INSERT INTO table_name (value) VALUES(:value)");
-let params = stmt.newBindingParamsArray();
-for (let i = 0; i < 10; i++) {
-  let bp = params.newBindingParams();
-  bp.bindByName("value", i);
-  params.addParams(bp);
-}
-stmt.bindParameters(params);
-
- -

You can attach multiple sets of bindings to a statement by adding multiple {{ interface("mozIStorageBindingParams") }} objects to the array of parameter lists, adding each one through calls to the {{ ifmethod("mozIStorageBindingParamsArray", "addParams") }}. Once all the parameters are set up, a single call to {{ ifmethod("mozIStorageStatement", "bindParameters") }} will ensure that the parameters are bound before execution. You can then execute the statement asynchronously, and the statement will get each set of bindings bound to it before execution asynchronously.

- -

Executing a Statement

- -

You may execute statements either synchronously (which is supported in Firefox Gecko 1.8 and 1.9) or asynchronously (starting in Gecko 1.9.1). If your code needs to work with applications based on Gecko 1.8 or 1.9, you should the technique covered in the section {{ anch("Synchronously") }} below. Otherwise, it's strongly recommended that you use asynchronous execution, for performance reasons.

- -

Asynchronously

- -

{{ gecko_minversion_header("1.9.1") }}

- -

Gecko 1.9.1 introduced support for asynchronous execution of a statement by calling {{ ifmethod("mozIStorageStatement", "executeAsync") }} on the statement. Multiple statements can be executed in a transaction by calling {{ ifmethod("mozIStorageConnection", "executeAsync") }} on the connection and passing in an array of statements. Both of these methods have similar signatures that accept an object as input that receives notifications the execution of the statement(s). A C++ example is omitted here because it would be verbose, but real-world code can be found in the Mozilla source tree ({{ lxrsearch("ident", "i", "mozIStorageStatementCallback") }}).

- -

After you create and bind a statement, your JavaScript should look something like this to execute a statement asynchronously:

- -
statement.executeAsync({
-  handleResult: function(aResultSet) {
-    for (let row = aResultSet.getNextRow();
-         row;
-         row = aResultSet.getNextRow()) {
-
-      let value = row.getResultByName("column_name");
-    }
-  },
-
-  handleError: function(aError) {
-    print("Error: " + aError.message);
-  },
-
-  handleCompletion: function(aReason) {
-    if (aReason != Components.interfaces.mozIStorageStatementCallback.REASON_FINISHED)
-      print("Query canceled or aborted!");
-  }
-});
-
- -

The call to executeAsync takes an object that implements mozIStorageStatementCallback. See its documentation for more details on each method. The callback is optional, however, so if you do not want to receive feedback, you can pass nothing.

- -

Synchronously

- -

If you are OK with the possibility of locking up your user interface, or if you are running on a background thread, you can use {{ ifmethod("mozIStorageStatement", "executeStep") }}. This function allows you to enumerate all the results produced by the statement.

- -

As you step through each row, you can obtain each parameter by name through a helper object ({{ interface("mozIStorageStatementRow") }}) in JavaScript ( {{ gecko_minversion_inline("1.9.1") }}) like so:

- -
while (statement.executeStep()) {
-  let value = statement.row.column_name;
-}
-
- -

You can create this helper object yourself if it's not available in your version of Gecko. See {{ interface("mozIStorageStatementWrapper") }} for details.

- -

In C++, the code would look something like this:

- -
bool hasMoreData;
-while (NS_SUCCEEDED(statement->ExecuteStep(&hasMoreData)) && hasMoreData) {
-  PRInt32 value;
-  rv = statement->GetInt32(0, &value);
-  NS_ENSURE_SUCCESS(rv, rv);
-}
-
- -

You can obtain other types of data by using the various methods available on {{ interface("mozIStorageValueArray") }}.

- -

Alternatively, if you do not expect any results but still need to execute a bound statement, you can simply call {{ ifmethod("mozIStorageStatement", "execute") }}. This is equivalent to calling {{ ifmethod("mozIStorageStatement", "executeStep") }} and then {{ ifmethod("mozIStorageStatement", "reset") }}.

- -

Resetting a Statement

- -

When you execute a statement synchronously, it is important to make sure you reset your statement. You can accomplish this by calling {{ ifmethod("mozIStorageStatement", "reset") }} on the statement. If you end up finalizing the statement (see {{ ifmethod("mozIStorageStatement", "finalize") }}) you do not need to worry about calling {{ ifmethod("mozIStorageStatement", "reset") }}. You should do this before you reuse the statement.

- -

{{ Warning("If you fail to reset a write statement, it will continue to hold a lock on the database preventing future writes or reads. Additionally, if you fail to reset a read statement, it will prevent any future writes to the database.") }}

- -

In JavaScript, the language makes it pretty easy to ensure that you always reset a statement. Be aware that you should always reset even if an exception is thrown, so your code should look something like this:

- -
var statement = dbConn.createStatement("SELECT * FROM table_name");
-try {
-  while (statement.step()) {
-    // Use the results...
-  }
-}
-finally {
-  statement.reset();
-}
-
- -

In C++, Storage provides a helper object in {{ Source("storage/public/mozStorageHelper.h") }}, mozStorageStatementScoper, which ensures that the statement object is reset when the object falls out of scope. Of course, if your statement is local only to the function, you do not have to worry about calling reset since the object will be destroyed.

- -
nsresult
-myClass::myFunction()
-{
-  // mSpecialStatement is a member variable of the class that contains a statement.
-  mozStorageStatementScoper scoper(mSpecialStatement);
-  // You can use mSpecialStatement without concern now.
-
-  nsCOMPtr<mozIStorageStatement> statement;
-  // mDBConn is a database connection that is stored a member variable of the class.
-  nsresult rv = mDBConn->CreateStatement(NS_LITERAL_CSTRING("DELETE FROM table_name"),
-                                         getter_AddRefs(statement));
-  NS_ENSURE_SUCCESS(rv, rv);
-  return statement->Execute();
-  // Once this function returns, mSpecialStatement will be reset, and statement will
-  // be destroyed.
-}
-
- -

{{ Note("Calling reset is not an expensive operation, and nothing bad happens if you call reset more than once.") }}

- -

Transações

- -

Transactions can be used to either improve performance, or group statements together as an atomic operation. In both cases, you execute more than one statement inside of a transaction.

- -

In JavaScript, managing transactions can be difficult when you are using the same connection on different threads, or are using a combination of asynchronous and synchronous statement execution. The best way to deal with this is to only execute your statements asynchronously using {{ ifmethod("mozIStorageConnection", "executeAsync") }}. This method will manage the transactions for you, so you don't have to worry about them.

- -

{{ Note("The database engine does not support nested transactions, so attempting to start a transaction when one is already active will throw an exception.") }}

- -

Transactions can be started with {{ ifmethod("mozIStorageConnection", "beginTransaction") }} or {{ ifmethod("mozIStorageConnection", "beginTransactionAs") }}. The latter takes one of three constants to describe the type of transaction:

- - - -

{{ ifmethod("mozIStorageConnection", "beginTransaction") }} is equivalent to calling {{ ifmethod("mozIStorageConnection", "beginTransactionAs") }} and passing mozIStorageConnection.TRANSACTION_DEFERRED In general, this is the method you want to use.

- -

Once you start a transaction, you can either commit the changes by calling {{ ifmethod("mozIStorageConnection", "commitTransaction") }}, or rollback the changes by calling {{ ifmethod("mozIStorageConnection", "rollbackTransaction") }}.

- -

In C++ code, there is a helper class defined in {{ Source("storage/public/mozStorageHelper.h") }}, mozStorageTransaction, that will attempt to get a transaction for you, and handle it appropriately when it falls out of scope. If a transaction is already in progress, no transaction is obtained. If your function returns without calling Commit on the helper object, the transaction will be rolled back.

- -
nsresult
-myClass::myFunction()
-{
-  // mDBConn is a member variable of our mozIStorageConnection.
-  mozStorageTransaction transaction(mDBConn);
-
-  // Execute some statements.  If we encounter an error, the transaction will
-  // be rolled back.
-
-  return transaction.Commit();
-}
-
- -

Colação (ordenação)

- -

SQLite provides several collation methods (BINARY, NOCASE, and RTRIM), but these are all very simple and have no support for various text encodings or the user's locale.

- -

{{ gecko_minversion_header("1.9.2") }}

- -

{{ Gecko("1.9.2") }} added support for several new collation methods:

- -
-
locale
-
Case- and accent-insensitive collation.
-
locale_case_sensitive
-
Case-sensitive, accent-insensitive collation.
-
locale_accent_sensitive
-
Case-insensitive, accent-sensitive collation.
-
locale_case_accent_sensitive
-
Case- and accent-sensitive collation.
-
- -

You can use them quite simply in your SELECT queries, like this:

- -
var stmt = aConn.createStatement("SELECT * FROM foo ORDER BY name COLLATE locale ASC");
-var results = [];
-
-while (stmt.executeStep()) {
-  results.push(stmt.row.t);
-}
-stmt.finalize();
-
- -

How to Corrupt a Database

- -

SQLite is very good about maintaining database integrity, but there are a few things you can do that can lead to database corruption. You can find out more by reading SQLite's documentation on this. These are a few simple things you can avoid to help make sure this doesn't happen:

- - - - - - - - - -

Thread Safety

- -

{{ interface("mozIStorageService") }} and {{ interface("mozIStorageConnection") }} are thread safe. However, no other interface or method is, so do not use them on different threads at the same time!

- -

If you want to use concurrency to work on your database, you should use the asynchronous APIs provided by Storage.

- -

Consultar também

- - - - diff --git "a/files/pt-pt/mozilla/tech/xpcom/guide/altera\303\247\303\265es_xpcom_gecko_2.0/index.html" "b/files/pt-pt/mozilla/tech/xpcom/guide/altera\303\247\303\265es_xpcom_gecko_2.0/index.html" deleted file mode 100644 index ac8d2a2583..0000000000 --- "a/files/pt-pt/mozilla/tech/xpcom/guide/altera\303\247\303\265es_xpcom_gecko_2.0/index.html" +++ /dev/null @@ -1,222 +0,0 @@ ---- -title: Alterações de XPCOM no Gecko 2.0 -slug: Mozilla/Tech/XPCOM/Guide/Alterações_XPCOM_Gecko_2.0 -tags: - - Gecko 2.0 - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Guide/Changes_in_Gecko_2.0 ---- -

{{ gecko_minversion_header("2") }}

- -

Várias alterações que afetam a compatibilidade do componente XPCOM estão a ser realizadas no Gecko 2. Este artigo detalha essas alterações, e proporciona sugestões sobre como atualizar o seu código.

- -

No more frozen interfaces

- -

There are no longer any frozen interfaces; from now on, all interfaces are subject to change. Documentation will be updated as time allows to remove references to interfaces being "frozen" or "unfrozen."

- -

Component registration

- -

The way XPCOM components are registered changed in Gecko 2. Prior to Gecko 2, during component registration, all binary and JavaScript component files were loaded and called, asking them to register themselves. If you used XPCOMUtils.jsm, some of this was hidden from you, but it was still there.

- -

Starting in Gecko 2, however, components are registered using manifest files, similarly to how chrome is registered. In fact, the same chrome manifest file will be used to register components.

- -

All existing XPCOM components will need to be updated to support this. However, it's very easy to do, and you can actually support both types of registration for backward compatibility.

- -

Component manifests

- -

All component registration is now handled through manifest files. For extensions, this is the same chrome.manifest currently used to register chrome.

- -

XPT files

- -

The path of any XPT files must be listed explicitly in a manifest using an interfaces directive:

- -
interfaces components/mycomponent.xpt
- -

JavaScript components

- -

The registration information for JavaScript components is no longer located in the component itself; instead, it's located in the manifest. The component is loaded only when the XPCOM component manager needs to create a component.

- -

chrome.manifest:

- -
# The {classID} here must match the classID in mycomponent.js
-component {e6b866e3-41b2-4f05-a4d2-3d4bde0f7ef8} components/mycomponent.js
-contract @foobar/mycomponent;1 {e6b866e3-41b2-4f05-a4d2-3d4bde0f7ef8}
-category profile-after-change MyComponent @foobar/mycomponent;1
-
- -

The JavaScript code no longer exports a NSGetModule() function. It now must export a NSGetFactory() function, which accepts a class ID (CID) as a parameter.

- -

For example, in your component's JavaScript code :

- -
Components.utils.import("resource://gre/modules/XPCOMUtils.jsm");
-
-function myComponent() {
-}
-myComponent.prototype = {
-  // this must match whatever is in chrome.manifest!
-  classID: Components.ID("{e6b866e3-41b2-4f05-a4d2-3d4bde0f7ef8}"),
-
-  QueryInterface: XPCOMUtils.generateQI([Components.interfaces.nsIMyComponent]),
-
-  /* nsIMyComponent implementation goes here */
-  ...
-};
-
-// The following line is what XPCOM uses to create components. Each component prototype
-// must have a .classID which is used to create it.
-const NSGetFactory = XPCOMUtils.generateNSGetFactory([myComponent]);
-
- -

A component may implement backwards compatibility with Gecko 1.9.2 by dynamically detecting which symbols are exported by XPCOMUtils.jsm and exporting the correct function:

- -
/**
-* XPCOMUtils.generateNSGetFactory was introduced in Mozilla 2 (Firefox 4, SeaMonkey 2.1).
-* XPCOMUtils.generateNSGetModule was introduced in Mozilla 1.9 (Firefox 3.0).
-*/
-if (XPCOMUtils.generateNSGetFactory)
-    var NSGetFactory = XPCOMUtils.generateNSGetFactory([myComponent]);
-else
-    var NSGetModule = XPCOMUtils.generateNSGetModule([myComponent]);
- -

Binary components

- -

Binary components must be listed explicitly in a manifest using a binary-component directive:

- -
binary-component components/mycomponent.dll
-
- -

C++ in the component must be changed: a binary component no longer exports a NSGetModule() function. Instead, it exports an NSModule data symbol which points to a mozilla::Module structure. For more information about the mozilla::Module structure, see the Module.h header file. For an up-to-date example of implementing a dynamic modules, see nsSampleModule.cpp.

- -

Note that nsIGenericFactory.h has been removed. References to nsIGenericFactory.h should be replaced with mozilla/ModuleUtils.h.

- -

It is possible for a binary component to be compatible with Mozilla 1.9.2 and Mozilla 2.0 by using the extra macro NS_IMPL_MOZILLA192_NSGETMODULE. See nsSampleModule.cpp for more details.

- -
Note: Binary XPCOM components must be recompiled for every new major release of Firefox starting with Firefox 4. Your life would be much easier over the long term if you switch to using js-ctypes instead.
- -

Also note that extensions using binary components must now use the unpack property in the install manifest.

- -

Platform-specific directories

- -

The component/chrome system used to look in platform-specific subdirectories of an extension, such as platform/WINNT_x86-msvc/chrome.manifest on Windows. This is no longer supported. You can use the OS and ABI chrome registration directives to achieve the same effect:

- -
binary-component components/windows/mycomponent.dll ABI=WINNT_x86-msvc
-binary-component components/mac/mycomponent.dylib ABI=Darwin_x86-gcc3
-binary-component components/mac/mycomponent64.dylib ABI=Darwin_x86_64-gcc3
-binary-component components/linux/mycomponent.so ABI=Linux_x86-gcc3
-
- -

This also means that platform-specific preferences are no longer possible. If you need to adjust default preferences based on platform, you can do so at first run by looking up what platform you're on and changing the preferences at that time.

- -

Category registration

- -

Prior to Gecko 2, extensions could listen for the xpcom-startup and app-startup notifications during startup, and perform actions during those. This is no longer the case. The earliest startup notification extensions can receive now is profile-after-change, which has always been the recommended notification to observe. That's because it's among the earliest notifications that occurs after the profile folder (and therefore preferences and other services) is available.

- -

What you need to change

- -

If your extension currently observes either xpcom-startup or app-startup, you need to update your code to observe profile-after-change instead.

- -

Typically, extensions observed app-startup because in the past, you needed to load for app-startup in order to be able to register to observe profile-after-change in the first place. As of {{ gecko("1.9.1") }}, this is no longer the case, however; you can now register for profile-after-change using the Category Manager. See Receiving startup notifications for details.

- -

To add a category entry, you must insert the following line to your chrome.manifest:

- -
category profile-after-change MyComponent @foobar/mycomponent;1
-
- -
Important: Formerly, the contract id of the category entry was prefixed with "service," if the component was implemented as a service. This prefix needs to be dropped when migrating to chrome.manifest.
- -

Changed category names

- -

The XPCOM category manager is used to register certain global helper objects. Because chrome.manifest is a space-delimited format, category names with spaces cannot be registered. Therefore the following categories have changed:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Old nameNew name
JavaScript global constructorJavaScript-global-constructor
JavaScript global constructor prototype aliasJavaScript-global-constructor-prototype-alias
JavaScript global propertyJavaScript-global-property
JavaScript global privileged propertyJavaScript-global-privileged-property
JavaScript global static namesetJavaScript-global-static-nameset
JavaScript global dynamic namesetJavaScript-global-dynamic-nameset
JavaScript DOM classJavaScript-DOM-class
JavaScript DOM interfaceJavaScript-DOM-interface
XSLT extension functionsXSLT-extension-functions
- -

But why?

- -

Previously, whenever Gecko detected that the application version had changed, or one or more extensions was added, removed, enabled, or disabled, it was necessary to throw away all existing component registrations, then restart the application (what we call the "Extension Manager restart") during its startup process. This was necessary in order to ensure that any components that should no longer be available are disposed of properly, and to re-register everything, loading any new components that may be needed.

- -

In theory, this is invisible to the user, but it's a costly process, since every component needs to be loaded and executed, then unloaded, then reloaded again during the restart.

- -

On top of that, with the ongoing work to make Firefox multithreaded, content processes either need to register components on a per-process basis, or somehow share a component cache with the chrome process.

- -

The changes to the component registration model let this so-called Extension Manager restart become a thing of the past. Instead of relying on a potentially stale component cache on startup, we read the application's component registrations out of its manifest file and load those components. This gets enough of XPCOM loaded and running that we can then load the Extension Manager and perform the necessary installing, uninstalling, and updating of any installed extensions.

- -

Once that's done, the extensions can then be loaded by simply reading their manifests, loading their components, and continuing the startup process, all without having to restart the browser.

- -

Electrolysis content processes can simply read the component registrations during startup.

- -

XPCNativeWrapper changes

- -

You can't disable XPCNativeWrappers from your manifest

- -

Specifying xpcnativewrappers=no in your manifest (that is, XPCNativeWrapper automation) is no longer supported. This was always intended to be a short-term workaround to allow extensions to continue to work while their authors updated their code to use XPCNativeWrappers.

- -

If your add-on depends upon XBL bindings attached to content objects—for example, the ability to call functions or get and set properties created by the XBL binding—you will need to use the XPCNativeWrapper property wrappedJSObject to access wrapped objects.

- -

If you need to be able to call functions or access properties defined by web content, you'll need to do this as well. This may be the case if, for example, you've written an extension that adds a delete button to a web mail service, and the service defines a window.delete() function that you need to call.

- -

If, on the other hand, all you're doing with content is accessing DOM methods and properties, you've never needed to be using xpcnativewrappers=no in the first place, and should simply remove it from your manifest.

- -

Miscellaneous XPCNativeWrapper changes

- - - -

XPCOMUtils.jsm changes

- -

The XPCOMUtils.jsm code module has been updated to let you specify the application IDs of the applications you wish to register your component in.

- -

XPCOM service getters

- -

A number of commonly used XPCOM services now have service getter functions available in the mozilla::services namespace; these make it much easier to get access to these services from C++ code.

- -

See also

- - diff --git a/files/pt-pt/mozilla/tech/xpcom/guide/index.html b/files/pt-pt/mozilla/tech/xpcom/guide/index.html deleted file mode 100644 index 63fcce03c0..0000000000 --- a/files/pt-pt/mozilla/tech/xpcom/guide/index.html +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: XPCOM guide -slug: Mozilla/Tech/XPCOM/Guide -tags: - - Add-ons - - Extensions - - Guide - - Landing - - Mozilla - - NeedsTranslation - - TopicStub - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Guide ---- -

These articles provide tutorials and usage documentation for XPCOM, including how to use it in your own projects and how to build XPCOM components for your Firefox add-ons and the like.

- -
-

WebExtensions are becoming the new standard for creating add-ons. Eventually support for XPCOM add-ons will be deprecated, so you should begin to investigate porting your add-ons to use the WebExtensions API, and report any missing functionality so we can be sure to address your concerns. Work is ongoing on WebExtension capabilities, so your input will help prioritize and plan the work. To learn more about the kinds of changes that will be needed, see Comparison with XUL/XPCOM extensions. In addition, any binaries you use will then need to be converted for use with the WebExtensions native messaging API, or compiled using WebAssembly or Emscripten.

-
- -

{{LandingPageListSubpages}}

diff --git a/files/pt-pt/mozilla/tech/xpcom/index.html b/files/pt-pt/mozilla/tech/xpcom/index.html deleted file mode 100644 index 4aad9d4fe0..0000000000 --- a/files/pt-pt/mozilla/tech/xpcom/index.html +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: XPCOM -slug: Mozilla/Tech/XPCOM -tags: - - Add-ons - - Extensions - - Extensões - - Extras - - Landing - - Mozilla - - NeedsTranslation - - Precisa de Tradução - - TopicStub - - XPCOM -translation_of: Mozilla/Tech/XPCOM ---- -

XPCOM é um modelo de objeto componente de plataforma cruzada, similar a Microsoft COM. Este tem múltiplas ligações de linguagem, permitindo que os componentes XPCOM sejam utilizados e implementados no Java, JavaScript e Python, além das interfaces em C++. As interfaces no XPCOM são definidas num dialeto de IDL, nomeado de XPIDL.

- -
-

WebExtensions are becoming the new standard for creating add-ons. Eventually support for XPCOM add-ons will be deprecated, so you should begin to investigate porting your add-ons to use the WebExtensions API, and report any missing functionality so we can be sure to address your concerns. Work is ongoing on WebExtension capabilities, so your input will help prioritize and plan the work. To learn more about the kinds of changes that will be needed, see Comparison with XUL/XPCOM extensions. In addition, any binaries you use will then need to be converted for use with the WebExtensions native messaging API, or compiled using WebAssembly or Emscripten.

-
- -

XPCOM itself provides a set of core components and classes, e.g. file and memory management, threads, basic data structures (strings, arrays, variants), etc. The majority of XPCOM components are not part of this core set and are provided by other parts of the platform (e.g. Gecko or Necko) or by an application or even by an extension.

- -
-
Accessing the Windows Registry Using XPCOM
When implementing Windows-specific functionality, it is often useful to access the Windows registry for information about the environment or other installed programs. To this end, there exist XPCOM interfaces to read and write registry data. This article will show you how to use the available interfaces in several Mozilla products.
Aggregating the In-Memory Datasource
already_AddRefed
already_AddRefed in association with nsCOMPtr allows you to assign in a pointer without AddRefing it.
Binary compatibility
If Mozilla decides to upgrade to a compiler that does not have the same ABI as the current version, any built component may fail. It is a possiblity that is introduced when upgrading to a new compiler without recompiling everything. Effectively, it is a different platform.
Bundling multiple binary components
Binary XPCOM components are sometimes required to implement low-level features for extensions. Since binary components are linked against a single Gecko SDK, a dependency to a particular version of Gecko is created. If the component uses only "frozen" XPCOM interfaces, there is a good chance the same binary component will work with different versions of Gecko (version 1.8 and 1.9, for example). The more likely case is that the component uses "unfrozen" interfaces and those interfaces can change between Gecko versions. This can create a difficult situation for extension developers trying to support multiple Gecko versions (Firefox 2 and 3, for example).
Creating a Python XPCOM component
Creating Applications with Mozilla already provides a tutorial for making a simple JavaScript or C++ component (implementing the nsISimple interface). Here is how to make the same component in Python using PyXPCOM.
Fun With XBL and XPConnect
Generating GUIDs
GUIDs are used in Mozilla programming for identifying several types of entities, including XPCOM Interfaces (this type of GUIDs is callled IID), components (CID), and legacy add-ons—like extensions and themes—that were created prior to Firefox 1.5. Add-ons can (and should) be identified with IDs of the form extensionname@organization.tld since Firefox 1.5.
Generic factory
Most XPCOM factories can be very simple. Rick Potts wrote a templated-based generic factory (nsFactory<t>) that simplifies the factory creation process that just requires writing a CreateInstance() method. The new nsIGenericFactory interface takes this a step further, by providing a single interface that can be reused anytime a simple implementation of nsIFactory is needed. Here is the interface, and a description of its use.</t>
How to build a binary XPCOM component using Visual Studio
This is a simple tutorial for building XPCOM objects in C++ using Visual Studio. XPCOM is Mozilla’s cross platform component object model, similar to Microsoft’s COM technology. XPCOM components can be implemented in C, C++, and JavaScript, and can be used from C, C++, and JavaScript. That means you can call JavaScript methods from C++ and vice versa. For more information on the workings of XPCOM look elsewhere.
How To Pass an XPCOM Object to a New Window
If you want to be able to call functions within an XPCOM object from a XUL window's code, you can do so if you pass the XPCOM object as one of the arguments to the window creation method.
Interfacing with the XPCOM cycle collector
This is a quick overview of the cycle collector introduced into XPCOM for Firefox 3, including a description of the steps involved in modifying an existing C++ class to participate in XPCOM cycle collection. If you have a class that you think is involved in a cyclical-ownership leak, this page is for you.
Introduction to XPCOM for the DOM
Warning: this document has not yet been reviewed by the DOM gurus, it might contain some errors.
Language bindings
An XPCOM Language Binding is a bridge between a particular language and XPCOM to provide access to XPCOM objects from that language, and to let modules written in that language be used as XPCOM objects by all other languages for which there are XPCOM bindings.
Monitoring HTTP activity
Gecko includes the nsIHttpActivityObserver interface, which you can implement in your code to monitor HTTP transactions in real time, receiving a callback as the transactions take place.
nsCOMPtr versus RefPtr
Gecko code uses both nsCOMPtr and RefPtr as smart pointers. This guide provides some explanation and advice on how to choose between them.
Observer Notifications
The following are topics that you can observe during the course of an application. Unless otherwise noted you register for the topics using the nsIObserverService.
Setting HTTP request headers
HTTP is one of the core technologies behind the Web. In addition to the actual content, some important information is passed with HTTP headers for both HTTP requests and responses.
Storage
Storage is a SQLite database API. It is available to trusted callers, meaning extensions and Firefox components only.
The Thread Manager
The Thread Manager, introduced in Firefox 3, offers an easy to use mechanism for creating threads and dispatching events to them for processing.
-
Troubleshooting XPCOM components registration
Often the first time you create an XPCOM component, it may fail to register correctly.
Using nsCOMPtr
This document is the sum total of everything written down about nsCOMPtr. If you have a question about nsCOMPtr, and this document doesn't answer it, there probably isn't a document that answers it. You'll have to turn to the XPCOM newsgroup or another experienced nsCOMPtr user, or find the answer by experimentation.
Using nsIClassInfo
If you use a C++ class which implements nsIClassInfo from JavaScript, then you don't have to explicitly call QueryInterface on the JavaScript object to access the object's interfaces.
Using nsIDirectoryService
nsDirectoryService implements the nsIProperties interface. This implementation will allow you to Get(), Set(), Define(), and Undefine() nsIFile.
Using nsIPasswordManager
Technical review completed.
Using nsISimpleEnumerator
Using the clipboard
This section provides information about cutting, copying, and pasting to and from the clipboard.
Using the Gecko SDK
Weak reference
In XPCOM, a weak reference is a special object that contains a pointer to an XPCOM object, but doesnot keep that object alive. If the referent object is destroyed before the weak reference, the pointer inside the weak reference is set to nsnull.
Working with Multiple Versions of Interfaces
In this short note we illustrate how one can update an XPCOM module in -order for it to work in both Firefox 2 and Firefox 3, even if the interfaces have -changed in the interim.
Working with out parameters
wrappedJSObject
wrappedJSObject is a property sometimes available on XPConnect wrappers. When available, it lets you access the JavaScript object hidden by the wrapper.
XPCOM ABI
XPCOM ABI is the binary interface of XPCOM components. While XPCOM components written in a scripting language (such as JavaScript) can be moved across platforms (such as Windows and OS X) without adaptation, those written in a compiled language (such as C++) require recompilation when moving to a different platform. Often, compiled XPCOM components are called 'binary' or 'native'.
XPCOM category image-sniffing-services
In versions of Firefox prior to Firefox 3, extensions could add decoders for new image types. However, such decoders relied on servers sending correct MIME types; images sent with incorrect MIME types would not be correctly displayed.
XPCOM glue
The XPCOM Glue is a static library which component developers and embedders can link against. It allows developers to link only against the frozen XPCOM method symbols and maintain compatibility with multiple versions of XPCOM.
XPCOM guide
These articles provide tutorials and usage documentation for XPCOM, including how to use it in your own projects and how to build XPCOM components for your Firefox add-ons and the like.
XPCOM ownership guidelines
...naturally. If you create a temporary object, obviously it's up to you to destroy it. That's a sure sign of ownership. If you create an object with a longer lifespan, you will own it until you give ownership away.
XPCOM reference
This reference describes the interfaces and functions provided by the XPCOM library. In addition, it details the various helper classes and functions, as well as the components, provided by the XPCOM glue library. The contents herein are oriented primarily toward extension developers and people embedding XPCOM in other projects.
XPCOM tasks
The XPCOM module roughly parallels the C/C++ standard libraries. It overlaps them significantly, but goes beyond them in capabilities. XPCOM sits above the standard libraries. Its role is to extend them with facilities tailored to XPCOM development in general, and specifically the needs of Mozilla. Like the standard libraries, XPCOM must be a fairly self-contained library, so as not to encumber clients with any unnecessary external dependencies.
XPCOM Thread Synchronization
XPCOM thread synchronization primitives have the same semantics as those in NSPR, and each method of these synchronization objects (e.g. Mutex::Lock()) has a matching function in NSPR (PR_Lock()). This is no accident, as mozilla:: primitives are merely bare-minimum wrappers around NSPR's.
xptcall FAQ
xptcall is a small low level XPCOM method call library. It is implemented using platform specific C/C++ and assembly language code. It is used to facilitate cross language and cross thread method calls. Porting this code is required in order to make Mozilla run on any given platform.
Xptcall Porting Guide
Original Author: John Bandhauer, 31 May 1999.
Xptcall Porting Status
This is a status page for the multiplatform porting of xptcall. xptcall has a FAQ and a Porting Guide.
-
- -
- -
-

Join the XPCOM community

-
-
Choose your preferred method for joining the discussion:
- -
-
- -
-
-
- - diff --git a/files/pt-pt/mozilla/tech/xpcom/reference/glue_classes/index.html b/files/pt-pt/mozilla/tech/xpcom/reference/glue_classes/index.html deleted file mode 100644 index e98aa51571..0000000000 --- a/files/pt-pt/mozilla/tech/xpcom/reference/glue_classes/index.html +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: XPCOM glue classes -slug: Mozilla/Tech/XPCOM/Reference/Glue_classes -tags: - - Classes - - Landing - - NeedsTranslation - - TopicStub - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/Glue_classes ---- -

These "glue" classes are provided to make it easier to use XPCOM from C++ code. When these classes are used by a component, you may need to link the component against the XPCOM glue library.

-

{{LandingPageListSubpages}}

diff --git a/files/pt-pt/mozilla/tech/xpcom/reference/index.html b/files/pt-pt/mozilla/tech/xpcom/reference/index.html deleted file mode 100644 index 29d07953d6..0000000000 --- a/files/pt-pt/mozilla/tech/xpcom/reference/index.html +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: XPCOM reference -slug: Mozilla/Tech/XPCOM/Reference -tags: - - Add-ons - - Extensions - - Landing - - Mozilla - - NeedsTranslation - - Reference - - TopicStub - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference ---- -

This reference describes the interfaces and functions provided by the XPCOM library. In addition, it details the various helper classes and functions, as well as the components, provided by the XPCOM glue library. The contents herein are oriented primarily toward extension developers and people embedding XPCOM in other projects.

- -
-

WebExtensions are becoming the new standard for creating add-ons. Eventually support for XPCOM add-ons will be deprecated, so you should begin to investigate porting your add-ons to use the WebExtensions API, and report any missing functionality so we can be sure to address your concerns. Work is ongoing on WebExtension capabilities, so your input will help prioritize and plan the work. To learn more about the kinds of changes that will be needed, see Comparison with XUL/XPCOM extensions. In addition, any binaries you use will then need to be converted for use with the WebExtensions native messaging API, or compiled using WebAssembly or Emscripten.

-
- -
-

If you're working on a module in the Mozilla codebase that's compiled with the MOZILLA_INTERNAL_API flag set, some of these APIs -- the string functions and classes in particular -- are not the ones you should be using. See the XPCOM internal string guide for documentation of the internal string API used within the Mozilla codebase.

-
- -

{{LandingPageListSubpages}}

- -

Many XPCOM pages return an nsresult. Prior to Gecko 19 {{geckoRelease(19)}}, this was an integer that simply returned an error code. It is now a strongly typed enum when XPCOM is built using a C++11 compiler. This causes compile-time errors to occur when improper values are returned as nsresult values, thereby making it easier to catch many bugs.

diff --git a/files/pt-pt/mozilla/tech/xul/attribute/textbox.type/index.html b/files/pt-pt/mozilla/tech/xul/attribute/textbox.type/index.html deleted file mode 100644 index e30799ed4b..0000000000 --- a/files/pt-pt/mozilla/tech/xul/attribute/textbox.type/index.html +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: textbox.type -slug: Mozilla/Tech/XUL/Attribute/textbox.type ---- -

no redirect

diff --git a/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/como/index.html b/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/como/index.html deleted file mode 100644 index 06056d13df..0000000000 --- a/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/como/index.html +++ /dev/null @@ -1,243 +0,0 @@ ---- -title: 'Configuração automática: Como criar um ficheiro de configuração' -slug: Mozilla/Thunderbird/Autoconfiguration/FileFormat/Como -tags: - - Configuração Automática - - thunderbird -translation_of: Mozilla/Thunderbird/Autoconfiguration/FileFormat/HowTo ---- -

Definição

- -

Authoritative definition

- -

Exemplo

- -

Exemplo do mundo real

- -
<?xml version="1.0" encoding="UTF-8"?>
-
-<clientConfig version="1.1">
-  <emailProvider id="freenet.de">
-    <domain>freenet.de</domain>
-    <displayName>Freenet Mail</displayName>
-    <displayShortName>Freenet</displayShortName>
-    <incomingServer type="imap">
-      <hostname>imap.freenet.de</hostname>
-      <port>993</port>
-      <socketType>SSL</socketType>
-      <authentication>password-encrypted</authentication>
-      <username>%EMAILADDRESS%</username>
-    </incomingServer>
-    <incomingServer type="imap">
-      <hostname>imap.freenet.de</hostname>
-      <port>143</port>
-      <socketType>STARTTLS</socketType>
-      <authentication>password-encrypted</authentication>
-      <username>%EMAILADDRESS%</username>
-    </incomingServer>
-    <incomingServer type="pop3">
-      <hostname>pop.freenet.de</hostname>
-      <port>995</port>
-      <socketType>SSL</socketType>
-      <authentication>password-cleartext</authentication>
-      <username>%EMAILADDRESS%</username>
-    </incomingServer>
-    <incomingServer type="pop3">
-      <hostname>pop.freenet.de</hostname>
-      <port>110</port>
-      <socketType>STARTTLS</socketType>
-      <authentication>password-cleartext</authentication>
-      <username>%EMAILADDRESS%</username>
-    </incomingServer>
-    <outgoingServer type="smtp">
-      <hostname>smtp.freenet.de</hostname>
-      <port>587</port>
-      <socketType>SSL</socketType>
-      <authentication>password-encrypted</authentication>
-      <username>%EMAILADDRESS%</username>
-    </outgoingServer>
-    <outgoingServer type="smtp">
-      <hostname>smtp.freenet.de</hostname>
-      <port>587</port>
-      <socketType>STARTTLS</socketType>
-      <authentication>password-encrypted</authentication>
-      <username>%EMAILADDRESS%</username>
-    </outgoingServer>
-    <documentation url="http://kundenservice.freenet.de/hilfe/email/programme/config/index.html">
-      <descr lang="de">Allgemeine Beschreibung der Einstellungen</descr>
-      <descr lang="en">Generic settings page</descr>
-    </documentation>
-    <documentation url="http://kundenservice.freenet.de/hilfe/email/programme/config/thunderbird/imap-thunderbird/imap/index.html">
-      <descr lang="de">TB 2.0 IMAP-Einstellungen</descr>
-      <descr lang="en">TB 2.0 IMAP settings</descr>
-    </documentation>
-  </emailProvider>
-</clientConfig>
-
- -

Como examinar os servidores de correio eletrónico

- -

To determine a server's capabilities, you can contact the server directly and talk the POP/IMAP/SMTP protocol manually (assuming you already know the hostname).
- For non-SSL, use netcat -v hostname port (preferred) or telnet hostname port as "client".

- - - -

In all cases, the server should respond with a list of capabilities.

- -

SSL / STARTTLS

- -

There are 2 SSL variants: normal SSL and STARTTLS.

- -

SSL normal

- -

The old-style SSL (including TLS, which is just the new name for SSL) has a special port:

- - - -

On Linux, you can contact the server via

- -
openssl s_client -connect hostname:port
- -

You should see output about the SSL handshake and the certificate. Important is what is listed as "CN=". This must be the same as the hostname that you contacted, otherwise the certificate is not valid (or you need to use another hostname).
- If you see nothing, then probably the server does not support SSL.
- After that, you can have the same protocol exchange as with netcat on standard ports, as listed above.

- -

STARTTLS

- -

STARTTLS is a special, new form of SSL, which works on the standard ports (e.g. port 143 for IMAP). You can contact the server via netcat as mentioned above. If you see "STARTTLS" (for IMAP, SMTP) or "STLS" (for POP) listed as one of the capabilities, the server should support STARTTLS.
- To try it out, on Linux, you can contact the server via

- -
openssl s_client -connect hostname:port -starttls proto
- -

...where "proto" is imap, pop3 or smtp. For example:

- -
openssl s_client -connect imap.example.com:143 -starttls imap
- -

You should get the same response as described above for openssl.

- -

Formato do ficheiro de configuração

- -

Add the appropriate port and socket type for each server, depending on protocol and SSL support. For example,
- for IMAP with SSL:

- -
<port>993<port>
-
-<socketType>SSL</socketType>
- -

for IMAP with STARTTLS:

- -
<port>143<port>
-<socketType>STARTTLS</socketType>
- -

for IMAP without any SSL (deprecated!):

- -
<port>143<port>
-
-<socketType>plain</socketType>
- -

Utilizar SSL

- -

Please do not submit or serve any configurations without SSL! There's no reason in 2010 why users still need to read mail entirely unprotected.
- If you are an ISP and think the server load is too high, try adding an SSL accelerator. They are cheap and widely used. In fact, even most freemail (!) providers these days support SSL, so if users pay you money for ISP service, that's all the more reason to give them proper service. But first simply try to enable software SSL - small servers may be fine with SSL and without any additional installations.

- -

Certificado válido

- -

Either way, be sure to use a valid certificate:

- - - -

Autenticação

- -

Probe the mail server, as explained above for STARTTLS. If you see CRAM-MD5 or APOP in the response, the server should support encrypted passwords. If you only see AUTH LOGIN and/or PLAIN, or no AUTH at all, the server probably does not support secure authentication. In the former case, select "Encrypted passwords" as "Authentication method" (in Thunderbird Account Settings UI, incoming server and SMTP server), and test whether you can actually log in with a real account (because some servers are unfortunately broken with regards to authentication, often due to a wrong or misconfigured SASL installation).

- -

Formato do ficheiro de configuração

- -

In the configuration file, for each IMAP, POP and SMTP server, you need to specify the authentication method.
-
- For plaintext passwords:

- -
<authentication>password-cleartext</authentication>
- -

For CRAM-MD5:

- -
<authentication>password-encrypted</authentication>
- -


- Discouraged settings (SMTP only):
- If the SMTP server can only be used after checking incoming mail, please use

- -
<authentication>smtp-after-pop</authentication>
- -

Note that RFC 4409 disallows that and requires the customer-facing SMTP server to support proper authentication via AUTH.
- If the SMTP server can only be used within the ISP's network, and requires no authentication, use:

- -
<authentication>client-IP-address</authentication>
- -

or, if it requires authentication in addition to the user being in the ISP network, use e.g.:

- -
<authentication>password-cleartext</authentication>
-
-<restriction>client-IP-address</restriction>
-
- -

However, that means that users on the road or in the office are unable to send mail, which is a real problem for many of our users. This violates RFC 4409 as well and is an outdated configuration. Please try find a configuration that works in all cases, for the sake of the users.

- -

Por favor, suporte as palavras-passe MD5

- -

Please support authentication with CRAM-MD5. It is simple to implement, and to set up, and you can still use RADIUS or a database that stores passwords in plaintext, so you don't need to make changes to your mail server or authentication infrastructure apart from installing some software and configuring it correctly. CRAM-MD5 is particularly important when no SSL is used: Never make users send their passwords in plaintext over the network! (Not even in your ISP network.) We warn users in the Mail Account Creation dialog about such insecure configurations, and we reserve the right to block them in the future.
-
- As an ISP, you should ideally store passwords in encrypted format, which removes the risk of mass password theft (and possibly reuse on other sites) if somebody hacks your servers. You can still support plaintext passwords in this case, and encrypt passwords on the fly before comparing. (Users who use plaintext passwords would still be somewhat exposed, but at least you don't have the risk of the whole plaintext password database being stolen.) You can use both plaintext and encrypted authentication transmission with plaintext or encrypted password databases - the two issues are independent.

- -

Nome de utilizador

- -

If the user's IMAP login name is the same as his email address (for example, if "fred@example.com" is the login name), add:

- -
<username>%EMAILADDRESS%</username>
- -

Note: Use %EMAILADDRESS% as literal. Thunderbird will replace it with the email address that the user entered. Same for %EMAILLOCALPART% and other placeholders.

- -

If the login name is the same as the first segment before the @ of the email address (for example, "fred" for "fred@example.com"), use:

- -
<username>%EMAILLOCALPART%</username>
- -

Pseudónimos, ou nome de utilziador não são parte do endereço de e-mail

- -

Note that the above must be true for any email address that the user would set up - even for aliases.
-
- You can ignore aliases like info@, if that's an alias for fred@ (or both fred@ and wilma@) and Fred would set up fred@example.com in Thunderbird, not info@.
-
- If, however, Fred can set up hero@example.com as alias for fred@example.com, and neither "hero" nor "hero@example.com" would work as login name on your IMAP server, you need to set up a lookup of alias -> username on your autoconfig server. So, if you get a request for <http://autoconfig.example.com/mail/c...ro@example.com>, your autconfig server must have a script which responds to /mail/config-v1.1.xml and returns the concrete username, for example:

- -
<username>fred</username>
- -

... (or <username>fred@example.com</username>, as appropriate) for hero@example.com. This is the only way to enable automatic configuration without users having to remember what their primary login name was, which is a serious problem in practical experience. Even if you have told them all the necessary information in your welcome letter, they usually cannot find the letter. That's exactly where autoconfiguration tries to help.

- -

Ativar visiturl

- -

Some providers do not provide IMAP or POP service by default, but require it to be enabled via a web UI. If that is the case, add the URL that a logged-in user would use into this field, and the application can prompt the user to visit it.

- -

This is not yet supported by Thunderbird 3.1, but should be in the future, so please add this critical information where it applies.

- -

If you are an ISP, please by all means avoid this. It's one of those "walls" against which users run the hard way.

- -

URL da documentação

- -

If the configuration is (partially) based on a help webpage of the ISP that describes the configuration that end users should use, you can record its URL here. You may add several of them, as several elements. It is for informational purposes only and mainly for the maintenance of the config file, the client currently does not use them at all.

- -
If your URL contains ampersands (&), please remember to replace them with HTML entities (&amp;). For example:
- -
<documentation url="http://example.com/help.php?client=thunderbird&amp;lang=en"/>
- -
Otherwise your XML file will be incorrect and Thunderbird will neither be able to parse it, nor to return any error message.
diff --git a/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/definicao/index.html b/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/definicao/index.html deleted file mode 100644 index 2df3fcc731..0000000000 --- a/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/definicao/index.html +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Definição do formato de ficheiro da configuração automática -slug: Mozilla/Thunderbird/Autoconfiguration/FileFormat/Definicao -translation_of: Mozilla/Thunderbird/Autoconfiguration/FileFormat/Definition ---- -

Por favor, consulte https://wiki.mozilla.org/Thunderbird:Autoconfiguration:ConfigFileFormat (inglês).

diff --git a/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/index.html b/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/index.html deleted file mode 100644 index 76a90f2777..0000000000 --- a/files/pt-pt/mozilla/thunderbird/autoconfiguration/fileformat/index.html +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Autoconfig file format -slug: Mozilla/Thunderbird/Autoconfiguration/FileFormat -tags: - - NeedsTranslation - - TopicStub -translation_of: Mozilla/Thunderbird/Autoconfiguration/FileFormat ---- - diff --git "a/files/pt-pt/mozilla/thunderbird/configuracao_autom\303\241tica/index.html" "b/files/pt-pt/mozilla/thunderbird/configuracao_autom\303\241tica/index.html" deleted file mode 100644 index f0a647cc98..0000000000 --- "a/files/pt-pt/mozilla/thunderbird/configuracao_autom\303\241tica/index.html" +++ /dev/null @@ -1,162 +0,0 @@ ---- -title: Configuração Automática no Thunderbird -slug: Mozilla/Thunderbird/Configuracao_automática -tags: - - Administração - - empresa -translation_of: Mozilla/Thunderbird/Autoconfiguration ---- -

Autor: Ben Bucksch
- Por favor, não altere este documento sem consultar o autor.

- -

Thunderbird 3.1 and later (and 3.0 to some degree) includes mail account autoconfiguration functionality. The goal of autoconfiguration is to make it very easy for users to configure the connection of Thunderbird to their email servers. In many cases, people should be able to download and install Thunderbird, enter their real name, email address and password in the Account Setup Wizard and have a fully functioning mail client and get and send their mail as securely as possible.

- -

Consulte também:

- - - -

This document describes how Autoconfiguration in Thunderbird works, and what to do to allow mail servers to be autoconfigured.

- -

Mecanismos

- -

Thunderbird gets the server settings via different means, each of which is intended for different cases:

- - - -

All the lookup mechanisms use the email address domain as base for the lookup. For example, for the email address fred@example.com , the lookup is performed as (in this order):

- -
    -
  1. tb-install-dir/isp/example.com.xml on the harddisk
    2. -
  2. check for autoconfig.example.com
    3. -
  3. look up of "example.com" in the ISPDB
    4. -
  4. look up "MX example.com" in DNS, and for mx1.mail.hoster.com, look up "hoster.com" in the ISPDB
    5. -
  5. try to guess (imap.example.com, smtp.example.com etc.)
    6. -
- -

We may add DNS SRV records as supported mechanism in the future, but we currently do not.

- -

Como adicionar suporte para o seu domínio

- -

Classificação

- -

If you are a big ISP (> 100,000 users) providing email addresses solely under a few domains like "example.com" and "example.de", you may either submit the configuration to the ISPDB or set up a configuration server.
-
- If you support email aliases and the user's login name is not part of the email address (for example, users may have "hero@example.com" as email address, but the IMAP/POP/SMTP login name is neither "hero" nor "hero@example.com", but "u67578"), you need to set up a configuration server, which does the email address -> login name lookup.
-
- If you host customer domains, i.e. you are "hoster.com", but your customers have "fred@flintstone.com" and "louis@kent.com" as domains, with only a few users per domain, you need to set up a configuration server (or rely on DNS MX).
-
- If you are a small company installing Thunderbird on your employees' desktops, you can place a configuration file in the Thunderbird installation folder.

- -

ISPDB

- -

Database URL is <https://live.mozillamessaging.com/autoconfig/v1.1/>, append domain name, e.g. <https://live.mozillamessaging.com/autoconfig/v1.1/freenet.de>.
-
- Current process: File a bug in Bugzilla, Product "Webtools", Component "ISPDB Database Entries", with a configuration file that matches the requirements described below.  The component is actively watched for new bugs (as of November 2015) so there is no need to request review on the file.

- -

Configuração do servidor no ISP

- -

Given the email address "fred@example.com", Thunderbird first checks <http://autoconfig.example.com/mail/config-v1.1.xml?emailaddress=fred@example.com> and then <http://example.com/.well-known/autoconfig/mail/config-v1.1.xml>.

- -

Empresa pequena

- -

If you are a small company, you can put the XML configuration file on your web server, at URL <http://example.com/.well-known/autoconfig/mail/config-v1.1.xml>. (This is not yet finalized and subject to change.)

- -

Hospedeiro do domínio

- -

If you are an ISP that hosts domains for your customers - for example, you are hoster.com and your customer registers fancy.com or example.com, and your servers accept and serve the mail for example.com -, you should set up an autoconfig server.

- -

DNS

- -

For each customer domain, you add a DNS record (in addition to the existing MX, A www etc. DNS records):
- autoconfig IN A 10.2.3.4
- or
- autoconfig IN CNAME autoconfig.hoster.com.
- ... where 10.2.3.4 and autoconfig.hoster.com are IP addresses / hostnames you own.
- This allows Thunderbird to find you as hoster.

- -

To make the Version without an autoconfig DNS Entry work you have to make sure that example.com points to the Webserver you will place the config-v1.1.xml on.

- -

Example: example.com A 10.2.3.4

- -

Servidor da Web

- -

You set up a web server bound to a physical IP address. This may be on the same machine as other web servers, but the web server must be configured to the content to any requested domain.
-
- You must use a virtual host that match all autoconfig.* domains of your customers. In Apache terms, you can use a "ip-based virtual host". In the Apache configuration files, that means something like: Listen 10.2.3.4:80 (of course, you use a public IP address that you own)

- -
<VirtualHost 10.2.3.4:80> #Must be the first and only virtual host with this ip!
-    DocumentRoot /var/www/autoconfig/
-    ServerName autoconfig.hoster.com
-    <Directory /var/www/autoconfig>
-	Order allow,deny
-	allow from all
-    </Directory>
-</VirtualHost>
- -

Place the configuration file at the URL /mail/config-v1.1.xml on that host.

- -

All config files must be served as Content-Type: text/xml (or application/xml), otherwise the file will be ignored. Also, they must use charset UTF-8 (esp. if there are any non-ASCII-characters).

- -

If you like to use name-based virtual hosts you probably don't want to setup the autoconfig subdomain for every domain of your customers.
- You can add a Rewriterule in the default virtual host (on debian /etc/apache2/sites-enabled/000-default)  to match all autoconfig.* subdomains:

- -
<VirtualHost *:80> #Must be the first Virtual host
-	ServerAdmin webmaster@hoster.com
-	ServerName www
-	DocumentRoot /var/www
-	RewriteEngine On
-	RewriteCond %{HTTP_HOST} ^autoconfig\. [NC]
-	RewriteRule ^/(.*)	http://autoconfig.hoster.com/$1 [L,R=301,NE]
-        #...
-</VirtualHost>
-<VirtualHost *:80>
-    DocumentRoot /var/www/autoconfig/
-    ServerName autoconfig.hoster.com
-    <Directory /var/www/autoconfig>
- 	Order allow,deny
-	allow from all
-    </Directory>
-</VirtualHost>
-
- -

If you use nginx, you can easily add a subdomain to all your Domains, which does the same as above. Either, you can redirect them to a common hostname:

- -
server {
-	listen 10.2.3.4:80; #use your server's public IP here!
-	server_name autoconfig.*;
-	return 301 http://autoconfig.hoster.com$request_uri;
-}
-
- -

Or serve them directly from a common directory:

- -
server {
-	listen 10.2.3.4:80; #again, use your server's public IP here!
-	server_name autoconfig.*;
-	location / {
-		root /var/www/autoconfig;
-	}
-}
-
- -

 

- -

Ficheiro de configuração

- -

Isto é descrito em Como criar um ficheiro de configuração e definido nas sub páginas.

diff --git a/files/pt-pt/mozilla/thunderbird/index.html b/files/pt-pt/mozilla/thunderbird/index.html deleted file mode 100644 index 0ca93f176b..0000000000 --- a/files/pt-pt/mozilla/thunderbird/index.html +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Thunderbird -slug: Mozilla/Thunderbird -tags: - - NeedsTranslation - - TopicStub - - thunderbird -translation_of: Mozilla/Thunderbird ---- -

Thunderbird is Mozilla's mail/messaging application. These pages document Thunderbird and also provide links to documentation about the MailNews backend which is also used in other projects such as Eudora/Penelope, Seamonkey, Correo, etc.

- -

Thunderbird is Firefox's kid sibling, and is built on the same technical platform as the web browser. In development for many years, and currently one of the most popular open source email clients, it is used by millions of people around the world to bring together all their email accounts, newsgroup and feed reading in a familiar high-productivity environment. (From early 2007 to early 2011 Thunderbird was developed by Mozilla Messaging, a subsidiary that was owned by Mozilla.)

- - - - - - - - -
-

Documentation

- -
-
Building Thunderbird
-
Information about building Thunderbird with the comm-central repository. There's also information about how comm-central works, how the review process works and how to use the Mozilla symbol server to help with debugging.
-
MailNews Protocols
-
Rough documentation about mail protocols..
-
Database views
-
Backend information about {{ Interface("nsIMsgDBView") }} and related interfaces..
-
Thunderbird API documentation
-
Thunderbird API documentation
-
Extension documentation
-
Tutorials and tips for building Thunderbird extensions
-
Automated Testing
-
Details of Thunderbird's automated testing facilities
-
Thunderbird in the Enterprise
-
Help with deploying Thunderbird in large organizations
-
- -

View All...

- 		-

Community

- - - -

Tools

- - -
- -

 

diff --git a/files/pt-pt/mozilla/thunderbird/lancamentos/index.html b/files/pt-pt/mozilla/thunderbird/lancamentos/index.html deleted file mode 100644 index 354a6d7335..0000000000 --- a/files/pt-pt/mozilla/thunderbird/lancamentos/index.html +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Thunderbird - Notas de lançamento de programador -slug: Mozilla/Thunderbird/Lancamentos -tags: - - Landing - - Lançamento - - Mozilla - - thunderbird -translation_of: Mozilla/Thunderbird/Releases ---- -

Esta página fornece hiperligações para os artigos do "Thunderbird X para programadores" para cada lançamento do Thunderbird. Estas notas deixam-no ver quais as funcionalidades que foram adicionadas e os erros eliminados em cada versão do Thunderbird.

- -
{{ListSubpages("/pt-PT/docs/Mozilla/Thunderbird/Releases",1,1,1)}}
- -

Ver também

- - diff --git a/files/pt-pt/mozilla/trabalhar_com_janelas_no_codigo_chrome/index.html b/files/pt-pt/mozilla/trabalhar_com_janelas_no_codigo_chrome/index.html deleted file mode 100644 index a3f012eb7a..0000000000 --- a/files/pt-pt/mozilla/trabalhar_com_janelas_no_codigo_chrome/index.html +++ /dev/null @@ -1,397 +0,0 @@ ---- -title: Trabalhar com janelas no código chrome -slug: Mozilla/trabalhar_com_janelas_no_codigo_chrome -tags: - - Add-ons - - Extensões - - Extras - - Guía -translation_of: Mozilla/Working_with_windows_in_chrome_code ---- -

Este artigo descreve o trabalho com várias janelas no código da Mozilla (aplicações XUL e Extensões). Este contém dicas e código exemplo em como abrir novas janelas, encontrar uma janela já aberta, e passar dados entre diferentes janelas.

- -

Abertura de janelas

- -

From a <script> in a window or an overlay

- -

To open a new window, we usually use a window.open or window.openDialog DOM call, like this:

- -
-
var win = window.open("chrome://myextension/content/about.xul",
-                      "aboutMyExtension", "chrome,centerscreen");
-
-
- -

The first parameter to window.open is the URI of the XUL file that describes the window and its contents.

- -

The second parameter is the window's name; the name can be used in links or forms as the target attribute. This is different from the user-visible window title, which is specified using XUL.

- -

The third, and optional, parameter is a list of special window features the window should have.

- -

The window.openDialog function works similarly, but lets you specify optional arguments that can be referenced from the JavaScript code. It also handles window features a little differently, including always assuming the dialog feature is specified.

- -

From XPCOM components and modules

- -

If the Window object is unavailable (for example, when opening a window from XPCOM component code), you might want to use nsIWindowWatcher interface. Its parameters are similar to window.open; in fact, window.open's implementation calls nsIWindowWatcher's methods.

- -
-
var ww = Components.classes["@mozilla.org/embedcomp/window-watcher;1"]
-                   .getService(Components.interfaces.nsIWindowWatcher);
-var win = ww.openWindow(null, "chrome://myextension/content/about.xul",
-                        "aboutMyExtension", "chrome,centerscreen", null);
-
- -

Objeto de janela

- -

Note the win variable in the above section, which is assigned the return value of window.open. It can be used to access the opened window. The return value of window.open (and similar methods) is a Window object (usually ChromeWindow) – the same type as the window variable.

- -

Technically speaking, it implements a number of interfaces, including {{ interface("nsIDOMJSWindow") }} and {{ interface("nsIDOMWindow") }}, but it also contains the user-defined properties for global variables and functions of the window. So, for example, to access the DOM document corresponding to the window, you can use win.document.

- -

Note however, that the open() call returns before the window is fully loaded, so some calls, like win.document.getElementById() will fail. To overcome this difficulty, you can move the initialization code to a load handler of the window being opened or pass a callback function, as described below.

- -

You can get a Window object from a document using document.defaultView.

- -

Janelas de conteúdo

- -

When a XUL window contains a widget capable of displaying a page, such as <browser> or <iframe>, the document in that widget is, naturally, separate from the document of the chrome window itself. There also is a Window object for each sub-document, although there's no window in a common sense for the sub-document.

- -

The same holds for chrome windows opened inside a tab of <tabbrowser>. The elements above the chrome document opened in the tab are separate from your chrome document.

- -

The following two subsections describe how to cross chrome-content boundaries in either way, i.e. accessing elements which are ancestors of your chrome document, or accessing elements which are descendants of your chrome document (but nevertheless in a different context).

- -

Accessing content documents

- -

Assume you have a document loaded in a <tabbrowser>, <browser>, or <iframe> element inside your document. You can use browser.contentDocument to access that document and browser.contentWindow to access the Window object of that document.

- -

You should be aware of XPCNativeWrappers when working with untrusted content. With XPCNativeWrappers turned on (which is the default in Firefox 1.5+), your extension can safely access the DOM of the content document, but not the content JavaScript. Bypassing XPCNativeWrapper to work with content JavaScript directly can lead to security problems.

- -

See Interaction between privileged and non-privileged pages if you need to interact with the content page.

- -

The content shortcut

- -

In case of <browser type="content-primary" />, you can use the content shortcut property to accesss the Window object of the content document. For example:

- -
// alerts the title of the document displayed in the content-primary widget
-
-alert(content.document.title);
- -

For example, you can use content.document in a browser.xul overlay to access the web page in the selected tab in a Firefox window.

- -
Some examples use _content instead of content. The former has been deprecated for a while, and you should use content in the new code.
- -

Accessing a document in the sidebar

- -

Firefox has a sidebar, which is implemented as a <browser> element with id="sidebar". To access the elements and variables inside the sidebar, you need to use document.getElementById("sidebar").contentDocument or .contentWindow, like when {{ Anch("Accessing content documents") }}.

- -

For more sidebar tips, see Code snippets:Sidebar.

- -

Accessing the elements of the top-level document from a child window

- -

The opposite case is when you want to access the chrome document from a privileged script loaded in a <browser> or an <iframe>.

- -

A typical case when this can be useful is when your code runs in the sidebar in the main Firefox window and you want to access the elements in the main browser window.

- -

The DOM tree, as shown by the DOM Inspector, can look like this:

- -
#document
-  window                 main-window
-    ...
-      browser
-        #document
-          window         myExtensionWindow
-
- -

where the child window is where your code runs in.

- -

Your task is to access elements above your chrome document, i.e. to break out of your chrome window and access the ancestors. This can be done using the following statement:

- -
var mainWindow = window.QueryInterface(Components.interfaces.nsIInterfaceRequestor)
-                   .getInterface(Components.interfaces.nsIWebNavigation)
-                   .QueryInterface(Components.interfaces.nsIDocShellTreeItem)
-                   .rootTreeItem
-                   .QueryInterface(Components.interfaces.nsIInterfaceRequestor)
-                   .getInterface(Components.interfaces.nsIDOMWindow);
- -

This allows you to cross the chrome-content boundaries, and returns the main window object.

- -

Encontrar janelas já abertas

- -

The window mediator XPCOM component (nsIWindowMediator interface) provides information about existing windows. Two of its methods are often used to obtain information about currently open windows: getMostRecentWindow and getEnumerator. Please refer to the nsIWindowMediator page for more information and examples of using nsIWindowMediator. === Example: Opening a window only if it's not opened already === XXX TBD

- -

Passar dados entre janelas

- -

When working with multiple windows, you often need to pass information from one window to another. Since different windows have separate DOM documents and global objects for scripts, you can't just use one global JavaScript variable in scripts from different windows.

- -

There are several techniques of varying power and simplicity that can be used to share data. We'll demonstrate them from the simplest to the most complex in the next few sections.

- -

Note: if you want to pass data between privileged (chrome) and non-privileged (web page) windows, or vice-versa, read this instead.

- -

Example 1: Passing data to window when opening it with openDialog

- -

When you open a window using window.openDialog or nsIWindowWatcher.openWindow, you can pass an arbitrary number of arguments to that window. Arguments are simple JavaScript objects, accessible through window.arguments property in the opened window.

- -

In this example, we're using window.openDialog to open a progress dialog. We pass in the current status text as well as the maximum and current progress values. Note that using nsIWindowWatcher.openWindow is a bit less trivial . TODO: link to How To Pass an XPCOM Object to a New Window when it has a more useful example

- -

Opener code:

- -
window.openDialog("chrome://test/content/progress.xul",
-                  "myProgress", "chrome,centerscreen",
-                  {status: "Reading remote data", maxProgress: 50, progress: 10} );
- -

progress.xul:

- -
<?xml version="1.0"?>
-<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>
-
-<window onload="onLoad();" xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">
-<script><![CDATA[
-
-var gStatus, gProgressMeter;
-var maxProgress = 100;
-
-function onLoad() {
-  gStatus = document.getElementById("status");
-  gProgressMeter = document.getElementById("progressmeter");
-
-  if("arguments" in window && window.arguments.length > 0) {
-    maxProgress = window.arguments[0].maxProgress;
-    setProgress(window.arguments[0].progress);
-    setStatus(window.arguments[0].status);
-  }
-}
-
-function setProgress(value) {
-  gProgressMeter.value = 100 * value / maxProgress;
-}
-
-function setStatus(text) {
-  gStatus.value = "Status: " + text + "...";
-}
-
-]]></script>
-
-<label id="status" value="(No status)" />
-<hbox>
-  <progressmeter id="progressmeter" mode="determined" />
-  <button label="Cancel" oncommand="close();" />
-</hbox>
-
-</window>
- -

Example 2: Interacting with the opener

- -

Sometimes an opened window needs to interact with its opener; for example, it might do so in order to give notice that the user has made changes in the window. You can find the window's opener using its window.opener property or via a callback function passed to the window in a way described in the previous section.

- -

Let's add code to the previous example to notify the opener when the user presses Cancel on the progress dialog.

- - - -

If we're sure the window that opened the progress dialog declares the cancelOperation function, we can use window.opener.cancelOperation() to notify it, like this:

- -
<button label="Cancel" oncommand="opener.cancelOperation(); close();" />
-
- - - -
function onCancel() {
-  alert("Operation canceled!");
-}
-
-...
-
-window.openDialog(
-  "chrome://test/content/progress.xul",
-  "myProgress", "chrome,centerscreen",
-  {status: "Reading remote data", maxProgress: 50, progress: 10},
-  onCancel
-);
-
- -

The progress dialog can then run the callback like this:

- -
<button label="Cancel" oncommand="window.arguments[1](); close();" />
-
- -

Example 3: Using nsIWindowMediator when opener is not enough

- -

The window.opener property is very easy to use, but it's only useful when you're sure that your window was opened from one of a few well-known places. In more complicated cases you need to use the nsIWindowMediator interface, introduced above.

- -

One case in which you might want to use nsIWindowMediator is in an extension's Options window. Suppose you're developing a browser extension that consists of a browser.xul overlay and an Options window. Suppose the overlay contains a button to open the extension's Options window which needs to read some data from the browser window. As you may remember, Firefox's Extension Manager can also be used to open your Options dialog.

- -

This means the value of window.opener in your Options dialog is not necessarily the browser window -- instead, it might be the Extension Manager window. You could check the location property of the opener and use opener.opener in case it's the Extension Manager window, but a better way is to use nsIWindowMediator:

- -
var wm = Components.classes["@mozilla.org/appshell/window-mediator;1"]
-                   .getService(Components.interfaces.nsIWindowMediator);
-var browserWindow = wm.getMostRecentWindow("navigator:browser");
-// read values from |browserWindow|
- -

You might be tempted to use a similar technique to apply the changes the user made in the Options dialog, but a better way to do that is to use preferences observers.

- -

Example 4: Using nsIWindowWatcher when you don't have a window (primitives only)

- -

For those times when you don't have access to a window object (such as a JavaScript XPCOM object), you can use nsIWindowWatcher.openWindow to open a XUL window. The problem is passing the data. It's a bit harder than using window.openDialog. Here is helper function that will package the data correctly and pass it to the newly opened window:

- -
function openDialog(parentWindow, url, windowName, features) {
-    var array = Components.classes["@mozilla.org/array;1"]
-                          .createInstance(Components.interfaces.nsIMutableArray);
-    for (var i = 4; i < arguments.length; i++) {
-        var variant = Components.classes["@mozilla.org/variant;1"]
-                                .createInstance(Components.interfaces.nsIWritableVariant);
-        variant.setFromVariant(arguments[i]);
-        array.appendElement(variant, false);
-    }
-
-    var watcher = Components.classes["@mozilla.org/embedcomp/window-watcher;1"]
-                            .getService(Components.interfaces.nsIWindowWatcher);
-    return watcher.openWindow(parentWindow, url, windowName, features, array);
-}
-
- -

The function almost works the same as window.openDialog but accepts an optional parent window as first parameter. The parent window can be null. The only data types that can be passed to the new window are primitives and arrays. JavaScript objects cannot be passed. All of the arguments are passed by value, that is to say that any changes made to the values in the new window will not affect the calling code.

- -

Example 5: Using nsIWindowWatcher for passing an arbritrary JavaScript object

- -

It is still possible to pass any JavaScript object using nsIWindowWatcher, it just takes a little more effort. In this example a single object is passed, though it is possible to pass multiple objects and primitives using a combination of this and the example above.

- -
// In the calling code
-var args = {
-  param1: true,
-  param2: 42
-};
-
-args.wrappedJSObject = args;
-
-var watcher = Components.classes["@mozilla.org/embedcomp/window-watcher;1"]
-                            .getService(Components.interfaces.nsIWindowWatcher);
-
-watcher.openWindow(null, url, windowName, features, args);
- -
// In the window code
-var args = window.arguments[0].wrappedJSObject;
-
- -

This uses the wrappedJSObject trick. By passing args to openWindow xpconnect will automatically wrap it as a generic nsISupports. The opened window can then just get at the underlying JavaScript object using wrappedJSObject.

- -

Partilha de dados avançada

- -

The above code is useful when you need to pass data from one window to another or to a set of windows, but sometimes you just want to share a JavaScript variable in common between different windows. You could declare a local variable in each window along with corresponding setter functions to keep the "instances" of the variable in sync across windows, but fortunately, there's a better way.

- -

To declare a shared variable, we need to find a place that exists while the application is running and is easily accessible from the code in different chrome windows. There are actually a few such places.

- -

Using JavaScript code modules

- -

JavaScript code modules {{ Fx_minversion_inline(3) }} is a simple method for creating shared global singleton objects that can be imported into any other JavaScript scope. The importing scope will have access to the objects and data in the code module. Since the code module is cached, all scopes get the same instance of the code module and can share the data in the module. See Components.utils.import for more information.

- - - -

Using an XPCOM singleton component

- -

The cleanest and most powerful way to share data is to define your own XPCOM component (you can write one in JavaScript) and access it from anywhere using a getService call:

- -
Components.classes["@domain.org/mycomponent;1"].getService();
-
- - - -

There are several articles and books about creating XPCOM components online.

- -

Using FUEL Application object

- -
-

The FUEL library has been deprecated as of Firefox 41

-
- -

The FUEL JavaScript library {{ Fx_minversion_inline(3) }} has a simple method for sharing data between windows. The Application object supports a storage property which can be used to store data globally. This method is a simplified form of the XPCOM singleton method.

- -
Application.storage.set(keyname, data);
-
-var data = Application.storage.get(keyname, default);
-
-where: keyname is a string used to identify the data
-       data is the data
-       default is the data value to return if keyname does not exists
-
- - - -

Storing shared data in preferences

- -

If you just need to store a string or a number, writing a whole XPCOM component may be an unnecessary complication. You can use the preferences service in such cases.

- - - -

See Code snippets:Preferences for detailed description of the preferences system and example code.

- -

Example:

- -
var prefs = Components.classes["@mozilla.org/preferences-service;1"]
-                      .getService(Components.interfaces.nsIPrefService);
-var branch = prefs.getBranch("extensions.myext.");
-var var1 = branch.getBoolPref("var1"); // get a pref
- -

Consulte também

- - diff --git "a/files/pt-pt/mozilla/utiliza\303\247\303\243o_cxx_no_c\303\263digo_da_mozilla/index.html" "b/files/pt-pt/mozilla/utiliza\303\247\303\243o_cxx_no_c\303\263digo_da_mozilla/index.html" deleted file mode 100644 index 02ec29e2a2..0000000000 --- "a/files/pt-pt/mozilla/utiliza\303\247\303\243o_cxx_no_c\303\263digo_da_mozilla/index.html" +++ /dev/null @@ -1,552 +0,0 @@ ---- -title: Utilização de C++ no código da Mozilla -slug: Mozilla/Utilização_CXX_no_código_da_Mozilla -translation_of: Mozilla/Using_CXX_in_Mozilla_code ---- -

Caraterísticas da linguagem C++

- -

Mozilla code only uses a subset of C++. Runtime type information (RTTI) is disabled, as it tends to cause a very large increase in codesize. This means that dynamic_cast, typeid() and <typeinfo> cannot be used in Mozilla code. Also disabled are exceptions; do not use try/catch or throw any exceptions. Libraries that throw exceptions may be used if you are willing to have the throw instead be treated as an abort.

- -

As of Mozilla 25, C++11 mode is required to build Mozilla. As of Mozilla 37, MSVC 2013 Update 3 is required on Windows; as of Mozilla 38, gcc 4.7 is required on all platforms. As of Mozilla 48, gcc 4.8 is required on all platforms. This means that C++11 can be used where supported on all platforms. The list of acceptable features is given below:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 MSVCGCCClang 
Requisito mínimo atual20134.83.4 
FuncionalidadeMSVCGCCClangPode ser utilizada no código
type_t &&20104.32.9Sim (consultar notas)
ref qualifiers on methods20154.8.12.9Não
member initializers20134.73.0Sim
variadic templates20134.32.9Sim
Initializer lists20134.43.1Sim
static_assert20104.32.9Sim
auto20104.42.9Sim
lambdas20104.53.1Sim
decltype20104.32.9Sim
Foo<Bar<T>>20104.32.9Sim
auto func() -> int20104.43.1Sim
Templated aliasing20134.73.0Sim
nullptr20104.63.0Yes, but use decltype(nullptr) instead of std::nullptr_t.
enum foo : int16_t {};20084.42.9Sim
enum class foo {};20124.42.9Sim
enum foo;20124.63.1Sim
[[attributes]]20154.83.3Não (consultar notas)
constexpr20154.63.1Use MOZ_CONSTEXPR from mozilla/Attributes.h
alignof/alignas20154.83.3No (see notes) ; only clang 3.6 claims __has_feature(cxx_alignof)
Delegated constructors20134.73.0Sim
Inherited constructors20154.83.3Não
explicit operator bool()20134.53.0Sim
char16_t/u"string"20154.43.0Use MOZ_UTF16("string") instead of u"string".
R"(string)"20134.53.0Sim
operator""()20154.73.1Não
=delete20134.42.9Sim
=default20134.43.0Sim
unrestricted unions20154.63.1Não
for (auto x : vec)20124.63.0Yes (be careful about the type of the iterator)
override/final20124.73.0Sim
thread_local20154.83.3Não (consultar notas)
function template default arguments20134.32.9Sim
local structs as template parameters20104.52.9Sim
extended friend declarations20104.72.9Sim
0b100 (C++14)20154.92.9Não
Return type deduction (C++14)20154.93.4Não
Generic lambdas (C++14)20154.93.4Não
Initialized lambda captures (C++14)20154.93.4Não
Digit separator (C++14)20154.93.4Não
Variable templates (C++14)—5.03.4Não
Relaxed constexpr (C++14)—5.03.4Não
Concepts (Concepts TS)—6.0—Não
Inline variables (C++17)———Não
constexpr_if (C++17)———Não
constexpr lambdas (C++17)———Não
- -

Notas

- -

rvalue references: Implicit move method generation cannot be used.

- -

Attributes: Several common attributes are defined in mozilla/Attributes.h or nscore.h.

- -

Alignment: Some alignment utilities are defined in mozilla/Alignment.h.

- -

Thread locals: There is a thread-local variable helper in mozilla/ThreadLocal.h. In addition, the native thread_local of MSVC2015 may break Windows XP support. See bug 1204752. The native thread_local of clang may break OSX 10.6, too, but support for OSX 10.6 has been retired.

- -

C++14: C++14 is not enabled on compilers that support it.

- -

Blibliotecas padrão de C++ e Mozilla

- -

The Mozilla codebase contains within it several subprojects which follow different rules for which libraries can and can't be used it. The rules listed here apply to normal platform code, and assume unrestricted usability of MFBT or XPCOM APIs.

- -
-

The rest of this section is a draft for expository and exploratory purposes. Do not trust the information listed here.

-
- -

What follows is a list of standard library components provided by Mozilla or the C++ standard. If an API is not listed here, then it is not permissible to use it in Mozilla code. Deprecated APIs are not listed here. In general, prefer Mozilla variants of data structures to standard C++ ones, even when permitted to use the latter, since Mozilla variants tend to have features not found in the standard library (e.g., memory size tracking) or have more controllable performance characteristics.

- -

Estruturas de dados

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NomeCabeçalhoSTL equivalenteNotes
nsAutoTArraynsTArray.h Like nsTArray, but will store a small amount as stack storage
nsAutoTObserverArraynsTObserverArray.h Like nsTObserverArray, but will store a small amount as stack storage
mozilla::BloomFiltermozilla/BloomFilter.h Probabilistic set membership (see Wikipedia)
nsClassHashtablensClassHashtable.h Adaptation of nsTHashtable, see XPCOM hashtable guide
nsCOMArraynsCOMArray.h Like nsTArray<nsCOMPtr<T>>
nsDataHashtablensClassHashtable.hstd::unordered_mapAdaptation of nsTHashtable, see XPCOM hashtable guide
nsDequensDeque.hstd::deque 
mozilla::EnumSetmozilla/EnumSet.h Like std::set, but for enum classes.
nsInterfaceHashtablensInterfaceHashtable.hstd::unordered_mapAdaptation of nsTHashtable, see XPCOM hashtable guide
nsJSThingHashtablensJSThingHashtable.h Adaptation of nsTHashtable, see XPCOM hashtable guide
mozilla::LinkedListmozilla/LinkedList.hstd::listDoubly-linked list
nsRefPtrHashtablensRefPtrHashtable.hstd::unordered_mapAdaptation of nsTHashtable, see XPCOM hashtable guide
mozilla::SegmentedVectormozilla/SegmentedVector.hstd::dequeDoubly-linked list of vector elements
mozilla::SplayTreemozilla/SplayTree.h Quick access to recently-accessed elements (see Wikipedia)
nsTArraynsTArray.hstd::vector 
nsTHashtablensTHashtable.hstd::unordered_mapSee XPCOM hashtable guide, you probably want a subclass
nsTObserverArraynsTObserverArray.h Like nsTArray, but iteration is stable even through mutation
nsTPriorityQueuensTPriorityQueue.hstd::priority_queueUnlike the STL class, not a container adapter
mozilla::Vectormozilla/Vector.hstd::vector 
- -

Untranslated notes:

- -

ns*String - too complicated to explain

- -

Safety utilities:
- mozilla::Array mfbt/Array.h (safe array index)
- mozilla::AssertedCast mfbt/Casting.h (casts)
- mozilla::CheckedInt mfbt/CheckedInt.h (avoids overflow)
- nsCOMPtr xpcom/glue/nsCOMPtr.h (~= std::shared_ptr)
- mozilla::EnumeratedArray mfbt/EnumeratedArray.h (mozilla::Array, for enum types)
- mozilla::RangedPtr mfbt/RangedPtr.h (prevents out-of-bounds)
- mozilla::RefPtr mfbt/RefPtr.h (~= std::shared_ptr)
- nsRefPtr xpcom/base/nsRefPtr.h (~= std::shared_ptr)
- StaticRefPtr xpcom/base/StaticPtr.h (nsRefPtr w/o static constructor)
- mozilla::UniquePtr mfbt/UniquePtr.h (~= std::unique_ptr)
- mozilla::WeakPtr mfbt/WeakPtr.h (~= std::weak_ptr)
- nsWeakPtr xpcom/base/nsWeakPtr.h (~= std::weak_ptr)

- -

Algos:
- mozilla::BinarySearch mfbt/BinarySearch.h
- mozilla::BitwiseCast mfbt/Casting.h (strict aliasing-safe cast)
- mozilla/MathAlgorithms.h (rotate, ctlz, popcount, gcd, abs, lcm)
- mozilla::RollingMean mfbt/RollingMean.h ()

- -

Misc:
- mozilla::AlignedStorage mfbt/Alignment.h (replacement for std::aligned_storage)
- mozilla::Atomic mfbt/Atomic.h (replacement for std::atomic)
- mozilla::CondVar xpcom/glue/CondVar.h
- mozilla::Maybe mfbt/Maybe.h (std::optional)
- mozilla::MaybeOneOf mfbt/MaybeOneOf.h (~mozilla::Maybe<union {T1, T2}>)
- mozilla::Monitor xpcom/glue/Monitor.h
- mozilla::Mutex xpcom/glue/Mutex.h
- mozilla::Pair mfbt/Pair.h (~= std::tuple<T1, T2> -- minimal space!)
- mozilla::ReentrantMonitor xpcom/glue/ReentrantMonitor.h
- mozilla::StaticMutex xpcom/base/StaticMutex.h
- mozilla::TimeStamp xpcom/ds/TimeStamp.h (~= std::chrono::time_point)

- -

mozilla/ArrayUtils.h
- mozilla/Compression.h
- mozilla/Endian.h
- mozilla/FloatingPoint.h
- mozilla/HashFunctions.h (~= std::hash)
- mozilla/Move.h (std::move, std::swp, std::Forward)
- mozilla/PodOperations.h (C++ versions of memset, memcpy, etc.)
- mozilla/TypeTraits.h (replacement for <type_traits>)

- -

(TODO: make list of STL usability here)

diff --git a/files/pt-pt/new_compatibility_tables_beta/index.html b/files/pt-pt/new_compatibility_tables_beta/index.html deleted file mode 100644 index ac4add57e3..0000000000 --- a/files/pt-pt/new_compatibility_tables_beta/index.html +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Novas Tabelas de Compatibilidade Beta -slug: New_Compatibility_Tables_Beta -translation_of: Archive/MDN/New_Compatibility_Tables_Beta ---- -

Está aqui provavelmente porque seguiu o link das novas tabelas de compatibilidade, não foi? (Não? Quer ver as novas tabelas? Torne-se um testador da beta.)

- -

Obrigado por nos ajudar a testar estas tabelas. São parte de um projeto muito grande. Estamos a mover todos os nossos dados de compatibilidade de browsers para JSON.

- -

As novas tabelas vão aparecer em páginas assim que os dados forem convertidos.

- -

Edição

- -

Os nossos dados foram movidos para o repositório de dados de compatibilidade no GitHub.

- -

Para contribuir pode submeter um pull request ou indentificar um problema no repositório.

- -

Como ajudar

- -

Se encontrar algum problema com os dados, por favor identifique um problema no repositório.

- -

Se alguma coisa estiver errada na aparência ou functionalidade da tabela, por favor clique no botão "report an error" no menu em cima da tabela.

- -

Se tiver tempo, agradeceríamos que preenchesse este inquérito.

diff --git a/files/pt-pt/ns_addref/index.html b/files/pt-pt/ns_addref/index.html deleted file mode 100644 index e37377bbe3..0000000000 --- a/files/pt-pt/ns_addref/index.html +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: NS_ADDREF -slug: NS_ADDREF -tags: - - Macros_XPCOM - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/NS_ADDREF ---- -

 

-

Sumário

-

Macro

-

Addrefs the argument. Não se deve usar quando o apontador poderá ser null; Nesses casos deve-se usar o NS_IF_ADDREF.

-

NS_ADDREF(foo) é equivalente a

-
foo->AddRef();
-
-

Esta macro existe principalmente por motivos históricos mas por consistência e por simetria com NS_RELEASE ela também deve ser usada.

-

Sintaxe

-
NS_ADDREF(foo);
-
-

Ver Também

-

NS_IF_ADDREF NS_RELEASE

diff --git a/files/pt-pt/ns_error/index.html b/files/pt-pt/ns_error/index.html deleted file mode 100644 index 16eb74b35c..0000000000 --- a/files/pt-pt/ns_error/index.html +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: NS_ERROR -slug: NS_ERROR -tags: - - Macros_XPCOM - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/NS_ERROR ---- -

 

-

Sumário

-

Macro

-

Atira uma asserção (NS_ASSERTION) com o texto "Error: (texto de erro)", o que faz com que escreva o texto na consola (stderr) e nos registos de depuração (registos NSPR). Esta macro é destinada a erros críticos — como as asserções, os NS_ERRORs não devem ser atingíveis.

-

Sintaxe

-
NS_ERROR("texto de erro");
-
diff --git a/files/pt-pt/ns_if_addref/index.html b/files/pt-pt/ns_if_addref/index.html deleted file mode 100644 index c10a7b2b2a..0000000000 --- a/files/pt-pt/ns_if_addref/index.html +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: NS_IF_ADDREF -slug: NS_IF_ADDREF -tags: - - Macros_XPCOM - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/NS_IF_ADDREF ---- -

 

-

Sumário

-

Macro

-

Faz addref ao argumento se ele for não-null. Não faz nada a um apontador null. Usar apenas caso o apontador possa ser NULL; Use NS_ADDREF caso não possa.

-

NS_IF_ADDREF(foo) equivale a

-
if (foo)
-  foo->AddRef();
-
-

Sintaxe

-
NS_IF_ADDREF(foo);
-
-

Ver Também

-

NS_ADDREF

diff --git a/files/pt-pt/ns_if_release/index.html b/files/pt-pt/ns_if_release/index.html deleted file mode 100644 index 79004cc21c..0000000000 --- a/files/pt-pt/ns_if_release/index.html +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: NS_IF_RELEASE -slug: NS_IF_RELEASE -tags: - - Macros_XPCOM - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/NS_IF_RELEASE ---- -

 

-

- - This page still needs some work, help to improve it! -

-

Sumárop

-

Macro

-

Decrementa o contador de referência de um apontador por um. Esta macro também define o apontador como NULL. NS_IF_RELEASE não tem qualquer efeito quando o apontador é NULL. Esta macro deve ser usada quando o apontador possa ser NULL; noutros casos use-se NS_RELEASE.

-

NS_IF_RELEASE(foo) equivale a

-
if (foo) {
-  foo->Release();
-  foo = 0;
-}
-
-

Sintaxe

-
NS_IF_RELEASE(foo);
-
-

Ver Também

-

NS_ADDREF, NS_RELEASE

diff --git a/files/pt-pt/ns_postcondition/index.html b/files/pt-pt/ns_postcondition/index.html deleted file mode 100644 index 0351be6cac..0000000000 --- a/files/pt-pt/ns_postcondition/index.html +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: NS_POSTCONDITION -slug: NS_POSTCONDITION -tags: - - Macros_XPCOM - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/Glue_classes/NS_POSTCONDITION ---- -

 

-

Sumário

-

Macro

-

Tem o mesmo efeito que NS_ASSERTION. Deve sre usada para testar condições que deverão ser produzidas por um método.

-

Sintaxe

-
NS_POSTCONDITION(expressão a testar, "texto de erro");
-
-

Ver Também

- diff --git a/files/pt-pt/ns_precondition/index.html b/files/pt-pt/ns_precondition/index.html deleted file mode 100644 index 6e151ef3b1..0000000000 --- a/files/pt-pt/ns_precondition/index.html +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: NS_PRECONDITION -slug: NS_PRECONDITION -tags: - - Macros_XPCOM - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/Glue_classes/NS_PRECONDITION ---- -

 

-

Sumário

-

Macro

-

Tem o mesmo efeito que NS_ASSERTION. Deve ser usada para testar condições que o invocador dum método deve obedecer.

-

Sintaxe

-
NS_PRECONDITION(expressão a testar, "texto de erro");
-
-

Ver Também

- diff --git a/files/pt-pt/ns_release/index.html b/files/pt-pt/ns_release/index.html deleted file mode 100644 index 81b72e6b71..0000000000 --- a/files/pt-pt/ns_release/index.html +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: NS_RELEASE -slug: NS_RELEASE -tags: - - Macros_XPCOM - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/NS_RELEASE ---- -

 

-

Sumário

-

Macro

-

Decrementa o contador de referência de um apontador por um. Esta macro também define o apontador para NULL. Não usar quando o apontador possa ser NULL; use NS_IF_RELEASE nos outros casos.

-

NS_RELEASE(foo) equivale a

-
foo->Release();
-foo = 0;
-
-

Sintaxe

-
NS_RELEASE(foo);
-
-

Ver Também

-

NS_ADDREF, NS_IF_RELEASE

diff --git a/files/pt-pt/ns_warning/index.html b/files/pt-pt/ns_warning/index.html deleted file mode 100644 index 4ffe526e5d..0000000000 --- a/files/pt-pt/ns_warning/index.html +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: NS_WARNING -slug: NS_WARNING -tags: - - Macros_XPCOM - - XPCOM -translation_of: Mozilla/Tech/XPCOM/Reference/NS_WARNING ---- -

 

-

Sumário

-

Macro

-

Mostra um aviso na consola (stderr) e nos registos de depuração (registos NSPR). Ao contrário do NS_ERROR, esta macro destina-se a erros não-críticos.

-

Sintaxe

-
NS_WARNING("texto de aviso");
-
diff --git a/files/pt-pt/nsiidleservice/index.html b/files/pt-pt/nsiidleservice/index.html deleted file mode 100644 index 9635c15129..0000000000 --- a/files/pt-pt/nsiidleservice/index.html +++ /dev/null @@ -1,68 +0,0 @@ ---- -title: nsIIdleService -slug: nsIIdleService -tags: - - Interfaces - - PrecisaDeConteúdo -translation_of: Mozilla/Tech/XPCOM/Reference/Interface/nsIIdleService ---- -

-
widget/nsIIdleService.idlScriptable
- - -The idle service lets you monitor how long the user has been 'idle', that is they have not used their mouse or keyboard. - - -
- -
1.0
- -
66
- -
- -
- -
Introduced
-
Gecko 1.9.1
- -
- -
- -
-Inherits from: nsISupports -Last changed in Gecko 16 (Firefox 16 / Thunderbird 16 / SeaMonkey 2.13)
-

-

O serviço de inatividade deixa-o monitorar por quanto tempo o usuário esteve 'ausente', i.e. não usado o seu mouse ou teclado. Você pode pegar o tempo de inatividade diretamente, mas na maioria dos casos você vai querer registrar um observador para um intervalo predefinido. Documentação e predefinições de interfaces a serem escritas...

-

Atualmente as implementações no nsIIdleService existem para Windows, Mac OS X e Linux (via XScreenSaver).

-

Exemplo 1:

-
var idleService = Components.classes["@mozilla.org/widget/idleservice;1"]
-                            .getService(Components.interfaces.nsIIdleService)
-setTimeout(function() { alert(idleService.idleTime) }, 1000)
-// se você não usar o mouse ou o teclado depois de rodar este fragmento,
-// você verá um número próximo de 1000 na caixa de alerta.
-
-

Exemplo 2:

-
var idleService = Components.classes["@mozilla.org/widget/idleservice;1"]
-                            .getService(Components.interfaces.nsIIdleService)
-var idleObserver = {
-  observe: function(subject, topic, data) {
-    alert("topic: " + topic + "\ndata: " + data);
-  }
-};
-idleService.addIdleObserver(idleObserver, 60); // one minute
-// ...
-// Não se esqueça de remover o observador usando removeIdleObserver!
-idleService.removeIdleObserver(idleObserver, 60);
-
-

Métodos

-
void addIdleObserver(in nsIObserver observer, in unsigned long time);
-void removeIdleObserver(in nsIObserver observer, in unsigned long time);
-
-

Atributos

-
readonly attribute unsigned long idleTime;
-
-

Categorias

-

Interwiki Language Links

-

diff --git a/files/pt-pt/plugins/index.html b/files/pt-pt/plugins/index.html deleted file mode 100644 index 361926e555..0000000000 --- a/files/pt-pt/plugins/index.html +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Plugins -slug: Plugins -tags: - - Plugins - - Todas_as_Categorias -translation_of: Archive/Plugins ---- -
-

Plugins (ou plug-ins) no contexto de aplicações baseadas no Mozilla são componentes binários que, quando registrados com uma aplicação, podem mostrar conteúdo que a aplicação por si mesma não pode exibir nativamente. Por exemplo, o plugin Adobe Reader permite ao usuário abrir arquivos PDF diretamente dentro do navegador, e os plugins Quicktime e Real Player são usados para exibir formatos especiais de vídeo em uma página web.

- -

Plugins podem ser úteis quando se está construindo uma aplicação usando a estrutura Mozilla. Por exemplo {{ interwiki('wikipedia', 'ActiveState_Komodo', 'ActiveState Komodo') }} usa plugins para encaixar o {{ interwiki('wikipedia', 'Scintilla_(editing_component)', 'editor Scintilla') }} em sua interface de usuário XUL.

- -

Plugins são escritos usando NPAPI, a API multi-navegadores para plugins. O código principal da documentação para NPAPI é a Gecko Plugin API Reference. Para fazer seu plugin scriptable para páginas web, use npruntime. O antigo XPCOM- e LiveConnect- APIs baseadas para plugins não devem ser usadas. As tecnologias continuam a ser utilizadas, só não para plugins.

- -

Você pode usar SVG ou canvas para simples tarefas de direção de scripts gráficos e animação.

- -

Plugins são diferentes de extensões, que modificam ou melhoram a funcionalidade do próprio navegador. Plugins também são diferentes de plugins de busca, que plugam adicionais motores de busca na barra de pesquisa.

-
- - - - - - - - -
-

Documentação

- -
-
Using the Right Markup to Invoke Plugins
-
Este artigo descreve como chamar um plugin com o uso correto do HTML. Ele discute o elemento objeto e o elemento embutido também com detalhes de como usar o mais apto HTML para chamar Java numa página web .
-
Usando o XPInstall para instalar Plugins
-
XPInstall é um instalador baseado em tecnologia JavaScript que funciona em todas as plataformas que Mozilla e navegadores Netscape baseados no Mozilla (como o Netscape 7) usam. Pode ser um caminho para garantir uma bela experiência de obter plugins sem forçar o usuário a sair do navegador para usar um instalador binário (o clássico setup.exe do Windows) ou obrigando-o a reiniciar o navegador.
-
Detectando Plugins
-
"Desde que tenha horas certas, quando faz sentido usar um plugin, surge a questão de como tratar os que não tenham o plugin necessário instalado.."
-
- -

Veja todos...

- 		-

Comunidade

- - - -

Ferramentas

- - - -

Veja todas...

- - - - -
diff --git a/files/pt-pt/rdf/index.html b/files/pt-pt/rdf/index.html deleted file mode 100644 index ba92a80ef9..0000000000 --- a/files/pt-pt/rdf/index.html +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: RDF -slug: RDF -tags: - - RDF - - Todas_as_Categorias -translation_of: Archive/Web/RDF ---- -
Resource Description Framework (RDF) (moldura de descrição de recursos) é a família de especificações de um modelo de meta-dados que é frequentemente implementada como uma aplicação de XML. A família de especificações RDF é mantida pelo World Wide Web Consortium. -

O modelo de meta-dados RDF é baseado na ideia de fazer declarações sobre recursos sob a forma de expressões sujeito-predicado-objecto, denominado de "triplo" na terminologia RDF. O sujeito é o recurso, ou seja, a "coisa" a ser descrita. O predicado é uma característica descritiva ou aspecto do recurso, e por vezes expressa uma relação entre o sujeito e o objecto. O objecto é o objecto da relação ou o valor da característica descritiva.

-
- - - - - - - - -
-

Documentação

- -
-
What is RDF
-
A introdução de Tim Bray à Resource Description Framework, em XML.com.
-
- -
-
RDF in Mozilla FAQ
-
Frequently asked questions about the Resource Description Framework in Mozilla.
-
- -

; RDF em Cinquenta Palavras ou Menos : <small>Uma pequena introdução à RDF.</small>  ; RDF Datasource How-To: <small>A cookbook-style document describing how to create a native, client-side datasource that works with Mozilla's RDF implementation.</small>  ; Aggregating the In-Memory Datasource: <small>Using the aggregation with the in-memory datasource.</small>

- -

Veja todos...

- 		-

Comunidade

- -

{{ DiscussionList("dev-tech-rdf", "mozilla.dev.tech.rdf") }}

- - - -

Ferramentas

- - - -

Veja todas...

- -

Tópicos relacionados

- -
-
XML
-
-
- -

Categorias

- -

Interwiki Language Links

diff --git a/files/pt-pt/social_api/index.html b/files/pt-pt/social_api/index.html deleted file mode 100644 index ac0f0f72e7..0000000000 --- a/files/pt-pt/social_api/index.html +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: API Social -slug: Social_API -tags: - - API - - Landing - - Mozilla - - Social -translation_of: Archive/Social_API ---- -

API Social é uma arquitetura que facilita a integração dos navegadores da Web com os serviços das redes sociais, utilziando as tecnologias da Web padrão, tal como a API. Assim que um provedor de serviços sociais é implementado para o Firefox, torna-se possível para o navegador integrar-se nos recursos da Web de um serviço, controles de utilizador no Chrome e informação relacionada com esse serviço. Os artigos seguintes explicam como implementar um provedor de serviços sociais.
-
- A 'API Social' suporta casos de utilização verticais específicos centrados nas interações sociais, mas não restringe rigidamente esses casos de utilização, permitindo flexibilidade e criatividade para terceiros. As funcionalidades específicas suportadas são notificações, partilha, marcadores (ou guardar para mais tarde), barras laterais e comunicações (por exemplo, conversação e vídeo).
-  

- -
-
-

Documentação da API Social

- -
-
Glossário da API Social
-
Provides definitions of key terms you'll need to understand when using the Social API.
-
Social service manifest
-
A description of—(TBD: and guide to building)—the manifest required.
-
Social service worker API reference {{obsolete_inline(48)}}
-
A reference to the social service worker API.
-
Social service content API: MozSocial {{obsolete_inline(51)}}
-
A reference to the social service content API, which is provided by the mozSocial object.
-
Social share API
-
A reference to the Share API.
-
Social bookmarks API {{obsolete_inline(51)}}
-
A reference to the Social Bookmarks API.
-
Social status API {{obsolete_inline(51)}}
-
A reference to the Status API.
-
Social service widgets
-
A guide to the widgets provided by the social service.
-
Using the Firefox Devtools with the Social API
-
Firefox has a number of development tools that can be used to help with the development of Social API providers. However, until bug 839959 lands the process isn't as simple as it should be. In the meantime, this page describes some workarounds.
-
- -

Como criar um Provedor de API Social

- -

A step-by-step guide to create a simple Social API provider.

- -
-
Primeiros Passos
-
The basics of getting an installable social provider running.
-
Adicionar notificações de ambiente {{obsolete_inline(51)}}
-
A short guide to implementing ambient notifications using the Social API.
-
Implementar estado e notificações {{obsolete_inline(51)}}
-
A guide to implementing a status panel with notifications using the Social API.
-
Adicioanr suporte de marcadores {{obsolete_inline(51)}}
-
A short guide to implementing social bookmarks using the Social API.
-
Implementar partilha
-
A guide to implementing a share panel using the Social API.
-
Suporte para conversação {{obsolete_inline(51)}}
-
A guide to implementing chat features using the Social API.
-
- -

Ver Tudo...

-
- -
-

Obter ajuda da comunidade

- -

Precisa de ajuda com um problema relacionado com a API Social e não consegue encontrar a solução na documentação?

- -
    -
  • Coloque a sua pergunta no canal de IRC da Mozilla: #socialdev
    • -
- -

Não se esqueça sobre 'etiqueta da net'...

- -

Ferramentas e demonstrações

- - - -

Ver Tudo...

- - - -

Experimente qualquer dos vários provedores no site Diretoria de APIs Sociais (necessário Firefox 29 ou superior).

- - - - -
-
- -

 

diff --git "a/files/pt-pt/tools/debugger/configura\303\247\303\265es/index.html" "b/files/pt-pt/tools/debugger/configura\303\247\303\265es/index.html" deleted file mode 100644 index bd111e5058..0000000000 --- "a/files/pt-pt/tools/debugger/configura\303\247\303\265es/index.html" +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Configurações -slug: Tools/Debugger/Configurações -translation_of: Archive/Tools/Debugger_settings ---- -
{{ToolsSidebar}}

O Depurador tem o seu próprio menu de configurações, que pode aceder a partir de um ícone na barra de ferramentas:

- -

- -

Cada definição é um comutador simples de lig./desl.:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Auto Prettify Minified SourcesWith this option enabled, the debugger will automatically detect minified JS files and pretty-print them.
Pause on ExceptionsWhen this option is enabled, execution of the script will automatically pause whenever a JavaScript exception is thrown.
Ignore Caught Exceptions -

If this option is set (it is set by default) and "Pause on exceptions" is set, then execution will pause on an exception only if that exception is not caught.

- -

This is usually the behavior you want. You don't generally want to pause execution when an exception that is thrown is caught, since that generally indicates that your program is handling it properly.

-
Show Panes on StartupWhen this option is enabled, the debugger's variables pane is visible when you first start the debugger.
Show Only Enumerable PropertiesDo not display non-enumerable JavaScript properties.
Show Variables Filter BoxEnabling this option adds a "Filter variables" search box to the variables pane, so that you can filter the displayed list of variables.
Show Original SourcesEnabling this option will make the debugger use source maps, if they are available, to display the original source for code which has been combined, minified, or even compiled to JavaScript from a language like CoffeeScript. Defaults to true.
Automatically Black Box Minified Sources -
-

New in Firefox 33.

-
- -

Automatically black box sources whose URL ends with ".min.js". Defaults to true.

-
- -

 

diff --git a/files/pt-pt/tools/scratchpad/index.html b/files/pt-pt/tools/scratchpad/index.html deleted file mode 100644 index c232451a3f..0000000000 --- a/files/pt-pt/tools/scratchpad/index.html +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: Scratchpad -slug: Tools/Scratchpad -tags: - - Desenvolvimento da Web - - 'Desenvolvimento da Web: Ferramentas' - - Ferramentas - - Scratchpad - - 'l10n:priority' -translation_of: Archive/Tools/Scratchpad ---- -
{{ToolsSidebar}}
- -
-

Scratchpad is deprecated as of Firefox 70 (bug 1565380), and will be removed as of Firefox 72 (bug 1519103). As an alternative, starting in Firefox 71, you can use the multi-line mode of the JavaScript console input.

-
- -

Scratchpad proporciona um ambiente para testar com o código JavaScript. Pode escrever, exeutar, e examinar tos resultados do código que interage com a página da Web.

- -

Ao contrário da Consola da Web, que foi desenhada para interpretar uma única linha de código, Scratchpad deixa-o editar grandes partes do código JavaScript, depois execute-o em vários modos, dependendo do modo em que pretende utilizar a saída.

- -

{{EmbedYouTube("Pt7DZACyClM")}}

- -
-

The featured video tutorial shows a case of using Scratchpad with a page run by a local web server. It is also possible to use Scratchpad over pages opened from a local file system, if permission policies allow that. But even with possible limitations present, the HTML code can be either manually entered or copied from the source and pasted into the "about:blank" page (a new empty tab) with the use Page Inspector's Edit as HTML context menu command.

-
- -

Utilização

- -

Opening Scratchpad in its own window

- -

There are several different ways to open Scratchpad in its own window:

- - - -

This will open up Scratchpad in its own window.

- -

Abrir o Scratchpad na Caixa de Ferramentas

- -
New in Firefox 47.
- -

From Firefox 47, you can open Scratchpad inside the Toolbox. First you need to check "Scratchpad" in the "Default Firefox Developer Tools" section of the Settings page.

- -

Now Scratchpad will be available in the Toolbox, alongside other tools like the Page Inspector and the Web Console. This is especially useful in split Console mode: you can use Scratchpad for a persistent, multiline editor, and the Console to interact with the page.

- -

Edição

- -

The Scratchpad window looks something like this (on OS X the menu bar is at the top of the screen):

- -

A screenshot of the Scratchpad

- -

The File menu offers options to save and load JavaScript code snippets, so you can reuse code later if you like.

- -

Conclusão do código

- -

Scratchpad integrates the tern code analysis engine, and uses that to provide autocomplete suggestions and popups containing information on the current symbol. To list autocomplete suggestions, press Ctrl + Space.

- -

For example, try typing d, then pressing Ctrl + Space. You'll see the autocomplete box, as shown below:

- -

The icon next to each suggestion indicates the type, and the currently highlighted suggestion gets a popup with more information. ↑ and ↓ cycle through the suggestions and Enter or Tab select the highlighted choice.

- -

Inline documentation

- -

To show the inline documentation popup, press Ctrl + Shift + Space when the cursor is on an identifier. For example, if you type document.addEventListener, then press Ctrl + Shift + Space, you'll see a popup that shows a summary of the function's syntax and a short description:

- -

The "[docs]" link takes you to the MDN documentation for the symbol.

- -

Execução

- -

Once you've written your code, select the code you want to run. If you don't select anything, all the code in the window will be run. Then choose the way you want the code to run using the buttons along the top, using the Execute menu, or using the context menu. The code is executed in the scope of the currently selected tab. Any variables you declare outside of a function will be added to the global object for that tab.

- -

There are four execution options available.

- -

Executar

- -

When you choose the Run option, the selected code is executed. This is what you'd use to execute a function or other code that manipulates the content of your page without needing to see the result.

- -

Inspecionar

- -

The Inspect option executes the code just like the Run option; however, after the code returns, an object inspector is opened to let you examine the returned value.

- -

Por exemplo, se inserir o código:

- -
window
-
- -

Then choose Inspect, the object inspector is shown that looks something like this:

- -

Inspecting an object in the Scratchpad

- -

Display

- -

The Display option executes the selected code, then inserts the result directly into your Scratchpad editor window as a comment, so you can use it as a REPL.

- -

Reload And Run

- -

The Reload And Run option is only available in the Execute menu. It first reloads the page, then executes the code when the page's "load" event fires. This is useful for running the code in a pristine environment.

- -

Executar o Scratchpad no contexto do navegador

- -

You can run Scratchpad in the context of the browser as a whole rather than a specific web page. This is useful if you are working on Firefox itself or developing add-ons. To do this check "Enable chrome and add-on debugging" in the Developer Tool Settings. Once you've done this, the Environment menu has a Browser option; once that's selected, your scope is the entire browser rather than just the page content, as you will see from examining some globals:

- -
window
-/*
-[object ChromeWindow]
-*/
-
-gBrowser
-/*
-[object XULElement]
-*/
- -

The Scratchpad execution context is set to browser when a snippet file has
- // -sp-context: browser
- on the first line.

- -

Atalhos de teclado

- -

{{ Page ("en-US/docs/tools/Keyboard_shortcuts", "scratchpad") }}

- -

Atalhos do editor fonte

- -

{{ Page ("pt-PT/docs/tools/Keyboard_shortcuts", "source-editor") }}

diff --git a/files/pt-pt/tools/webide/index.html b/files/pt-pt/tools/webide/index.html deleted file mode 100644 index ade5815623..0000000000 --- a/files/pt-pt/tools/webide/index.html +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: WebIDE -slug: Tools/WebIDE -tags: - - Aplicações - - Apps - - Depuração - - Fiirefox OS - - WebIDE - - ferramenta -translation_of: Archive/WebIDE ---- -
{{ToolsSidebar}}
-

WebIDE permite-lhe criar, editar, executar, e depurar as aplicações da Web, utilizando o FSimulador de Firefox OS ou um dispositivo real com o Firefox OS.

- -

It also enables you to connect the Firefox Developer Tools to a number of other browsers, including Firefox for Android, Chrome on Android, and Safari on iOS. See the Remote Debugging page for instructions on how to connect to a specific browser.

-
- -

With WebIDE, you first set up one or more runtimes. A runtime is an environment in which you'll run and debug the app. A runtime could be a Firefox OS device connected to the desktop over USB (or over Wi-Fi since Firefox 39), or it could be a Firefox OS Simulator installed on the desktop itself.

- -

Next, you create an app, or open an existing app. If you're creating a new app you can start with a template that includes the directory structure and the minimum boilerplate you need to get started, or a more complete template that shows how to use a privileged API. WebIDE shows your app's files in a tree, and you can edit and save them using a built-in source editor. Of course, you don't have to use the built-in editor: you can develop your app entirely outside WebIDE, and only use it for debugging.

- -

Finally, you can install the app in one of the runtimes and run it. You can then open the usual suite of developer tools - the Inspector, Console, JavaScript Debugger and so on - to examine and modify the running app.

- -
-
-
Abrir WebIDE
-
How to open WebIDE from within Firefox.
-
Setting up runtimes
-
How to connect to a runtime in which you can install apps, including Firefox OS devices, the the Firefox OS Simulator, and Firefox for Android.
-
Criação e edição de aplicações
-
How to create, open, and develop apps using WebIDE.
-
The runtime menu
-
Once you've selected a runtime, use the runtime menu to get information about the runtime and its apps, modify settings, and take a screenshot.
-
Running and debugging apps
-
How to install apps to a runtime and debug them using the Firefox Developer Tools.
-
Working with Cordova apps in WebIDE
-
From Firefox 39, you can edit and debug Cordova apps using WebIDE.
-
Resolução de Problemas
-
Help for problems with WebIDE, especially problems connecting to a runtime.
-
diff --git a/files/pt-pt/web/css/azimuth/index.html b/files/pt-pt/web/css/azimuth/index.html deleted file mode 100644 index 24e469dc63..0000000000 --- a/files/pt-pt/web/css/azimuth/index.html +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: azimuth -slug: Web/CSS/azimuth -tags: - - Referencia_CSS -translation_of: Archive/Web/CSS/azimuth ---- -

{{ CSSRef() }}

-

Resumo

-

Em combinação com elevation, azimuth habilita diferentes fontes de áudio para serem posicionadas espacialmente para apresentações aurais. Isto é importante porque proporciona uma maneira natural de contar várias vozes a parte, como cada uma pode ser posicionada para originar em uma localização diferente no estágio de som. Saída estéreo produz um estágio de som lateral, enquanto instalações de fones de ouvido e microfones permitem um estágio tridimencional completo.

- -

Sintaxe

-
azimuth: angle | [[ left-side | far-left | left |
-    center-left | center | center-right | right |
-    far-right | right-side ] || behind ] | leftwards |
-    rightwards | inherit
-
-

Valores

-
-
- angle 
-
- Posição de fonte audível é descrita como um ângulo dentro da faixa de -360deg até 360deg. O valor 0deg significa diretamente adiante do centro do estágio de som (este é o valor padrão). 90deg é para a direita, 180deg é atrás e 270deg ou -90deg é para a esquerda.
-
-

Image:Azimuth.png

-

Palavras-chave relativas a posição

- -

Exemplos

-
h1   { azimuth: 30deg }
-td.a { azimuth: far-right }          /*  60deg */
-#12  { azimuth: behind far-right }   /* 120deg */
-p.comment { azimuth: behind }        /* 180deg */
-
-

Especificações

- -

== Compatibilidade com navegadores == TBD (this might be abandoned in favour of a centralized compatibility chart)

-

Veja também

-

{{ Cssxref("elevation") }}

-

Categorias

-

Interwiki Language Links

-

{{ languages( { "en": "en/CSS/azimuth", "fr": "fr/CSS/azimuth", "pl": "pl/CSS/azimuth" } ) }}

diff --git "a/files/pt-pt/web/css/como_come\303\247ar/dados_xml/index.html" "b/files/pt-pt/web/css/como_come\303\247ar/dados_xml/index.html" deleted file mode 100644 index d0245353fa..0000000000 --- "a/files/pt-pt/web/css/como_come\303\247ar/dados_xml/index.html" +++ /dev/null @@ -1,239 +0,0 @@ ---- -title: Dados XML -slug: Web/CSS/Como_começar/Dados_XML -tags: - - 'CSS:Como_começar' -translation_of: Archive/Beginner_tutorials/XML_data ---- -

{{ Previous("Web/CSS/Como_começar/Gráficos_SVG") }}

- -

 

- -

Esta página contém um exemplo de como você pode usar o CSS com dados XML.

- -

Você cria um documento XML de amostra e uma folha de estilo que você pode usar para exibí-lo em seu navegador.

- -

Informação: Dados XML

- -

XML (eXtensible Markup Language) é uma linguagem de propósito geral para qualquer tipo de dados estruturados.

- -

Por padrão, seu navegador Mozilla mostra o XML em um formato muito similar aos dados originais no arquivo XML. Você vê as tags reais que definem a estrutura dos dados.

- -

Ligando a folha de estilo CSS com o documento XML, você pode definir outras maneiras para mostrá-lo. Para fazer isto, sua folha de estilo usa regras que mapeiam os tags no documento XML para mostrar tipos usados pelo HTML.

- - - - - - - - -
Exemplo
Dados em um documento XML usando tags <INFO>. Você quer que os elementos INFO do documento sejam mostrados como parágrafos no HTML. -

Na folha de estilo do documento, você especifica como os elementos INFO serão exibidos:

- -
- 
-INFO {
-  display: block;
-  margin: 1em 0;
-  }
-
-
-
- -

Os valores mais comuns para a propriedade display são:

- - - - - - - - - - - - -
blockMonstrado como DIV do HTML (para cabeçalhos, parágrafos)
inlineMostrado como SPAN do HTML (para ênfases no texto)
- -

Adicione seu próprio estilo de regras para especificar a fonte, espaçamento e outros detalhes da mesma maneira que no HTML.

- - - - - - - - -
Mais detalhes
Outros valores de display mostram o elemento como o item de uma lista, ou como o componente de uma tabela. -

Para a lista completa de tipos de exibição, veja The display property em CSS Specification.

- -

Usando CSS sozinho, a estrutura de exibição precisa ser a mesma da estrutura do documento. Outras tecnologias pode modificar a estrutura da exibição — por exemplo, o XBL pode adicionar conteúdo, e o JavaScript pode modificar o DOM.

- -

Para mais informações sobre o XML no Mozilla, veja a página XML neste wiki.

-
- -

Ação: Uma demonstração XML

- -

Crie um novo arquivo XML, doc9.xml. Copie e cole o conteúdo daqui, tendo certeza de ter rolado a tela e pego tudo isto:

- -
-
<?xml version="1.0"?>
-<!-- XML demonstration -->
-
-<?xml-stylesheet type="text/css" href="style9.css"?>
-
-<!DOCTYPE planet>
-<planet>
-
-<ocean>
-<name>Arctic</name>
-<area>13,000</area>
-<depth>1,200</depth>
-</ocean>
-
-<ocean>
-<name>Atlantic</name>
-<area>87,000</area>
-<depth>3,900</depth>
-</ocean>
-
-<ocean>
-<name>Pacific</name>
-<area>180,000</area>
-<depth>4,000</depth>
-</ocean>
-
-<ocean>
-<name>Indian</name>
-<area>75,000</area>
-<depth>3,900</depth>
-</ocean>
-
-<ocean>
-<name>Southern</name>
-<area>20,000</area>
-<depth>4,500</depth>
-</ocean>
-
-</planet>
-
-
- -

Crie um novo arquivo CSS, style9.css. Copie e cole o conteúdo daqui, tendo certeza de ter rolado a tela e pego tudo isto:

- -
-
/*** XML demonstration ***/
-
-planet:before {
-  display: block;
-  width: 8em;
-  font-weight: bold;
-  font-size: 200%;
-  content: "Oceans";
-  margin: -.75em 0px .25em -.25em;
-  padding: .1em .25em;
-  background-color: #cdf;
-  }
-
-planet {
-  display: block;
-  margin: 2em 1em;
-  border: 4px solid #cdf;
-  padding: 0px 1em;
-  background-color: white;
-  }
-
-ocean {
-  display: block;
-  margin-bottom: 1em;
-  }
-
-name {
-  display: block;
-  font-weight: bold;
-  font-size: 150%;
-  }
-
-area {
-  display: block;
-  }
-
-area:before {
-  content: "Area: ";
-  }
-
-area:after {
-  content: " million km\B2";
-  }
-
-depth {
-  display: block;
-  }
-
-depth:before {
-  content: "Mean depth: ";
-  }
-
-depth:after {
-  content: " m";
-  }
-
-
- -

Abra o documento em seu navegador:

- - - - - - - -
-
-

Oceans

- -

Arctic
- Area: 13,000 million km²
- Mean depth: 1,200 m

- -

Atlantic
- Area: 87,000 million km²
- Mean depth: 3,900 m

- -

. . .

-
-
- -


- Notas sobre esta demonstração:

- - - -

 

- - - - - - - - -
Desafio
Mude a folha de estilo de modo que ela mostre o documento como uma tabela. -

(Veja o capítulo Tables em CSS Specification para exemplos que você pode adaptar.)

-
- -

O que vem depois?

- -

Se você teve dificuldade para entender esta página, ou se você tem algum comentário sobre ela, por favor contribua nesta página de Discussão.

- -

Esta é a última página do tutorial. Para mais informações sobre CSS no Mozilla, veja a página principal CSS neste wiki.

- -

{{ Previous("Web/CSS/Como_começar/Gráficos_SVG") }}

- -

Categorias

- -

Interwiki Language Links

diff --git "a/files/pt-pt/web/css/como_come\303\247ar/interfaces_de_usu\303\241rio_xul/index.html" "b/files/pt-pt/web/css/como_come\303\247ar/interfaces_de_usu\303\241rio_xul/index.html" deleted file mode 100644 index 46408abaa8..0000000000 --- "a/files/pt-pt/web/css/como_come\303\247ar/interfaces_de_usu\303\241rio_xul/index.html" +++ /dev/null @@ -1,336 +0,0 @@ ---- -title: Interfaces de usuário XUL -slug: Web/CSS/Como_começar/Interfaces_de_usuário_XUL -tags: - - 'CSS:Como_começar' -translation_of: Archive/Beginner_tutorials/XUL_user_interfaces ---- -

{{ PreviousNext("CSS:Como começar:XBL bindings", "CSS:Como começar:Gráficos SVG") }}

- -

Esta página ilustra a linguagem especializada do Mozilla para criação de interfaces de usuário.

- -

Você cria uma simples demonstração que roda no seu navegador Mozilla.

- -

Informação: Interfaces de usuário

- -

Embora o HTML tenha algum suporte à interfaces de usuário, ele não suporta todas as características que você precisa para fazer uma aplicação autônoma.

- -

O Mozilla supera esta limitação providenciando uma linguagem especializada para criar interfaces de usuário: XUL (XML User-interface Language, usualmente pronunciada como "zool").

- -

Em XUL, muitas características comuns de interfaces de usuário podem ser construídas. Por exemplo, XUL proporciona janelas especializadas como diálogos, assim como barras de estado, menus, barras de ferramenta, e mesmo navegadores.

- -

Mais características especializadas podem ser construídas em partes usando XUL juntamente com outras tecnologias que você viu neste tutorial: estilo CSS, código JavaScript e XBL bindings.

- -

Como outras linguagens baseadas em XML, XUL usa folhas de estilo CSS.

- - - - - - - - -
Mais detalhes
Para maiores informações sobre interfaces de usuário XUL, veja a página XUL neste wiki.
- -

Ação: Uma demonstração XUL

- -

Crie um novo documento XUL de um simples arquivo de texto, doc7.xul. Copie e cole o conteúdo daqui, tendo certeza de ter rolado a tela para pegar tudo isto:

- -
-
<?xml version="1.0"?>
-<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>
-<?xml-stylesheet type="text/css" href="style7.css"?>
-
-<window
-  xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
-  title="CSS Getting Started - XUL demonstration"
-  onload="init();">
-
-<script type="application/x-javascript" src="script7.js"/>
-
-<label class="head-1" value="XUL demonstration"/>
-
-<vbox>
-
-  <groupbox class="demo-group">
-    <caption label="Day of week calculator"/>
-    <grid>
-      <columns>
-        <column/>
-        <column/>
-        </columns>
-      <rows>
-        <row>
-          <label class="text-prompt" value="Date:"
-            accesskey="D" control="date-text"/>
-          <textbox id="date-text" type="timed"
-            timeout="750" oncommand="refresh();"/>
-          </row>
-        <row>
-          <label value="Day:"/>
-          <hbox id="day-box">
-            <label class="day" value="Sunday" disabled="true"/>
-            <label class="day" value="Monday" disabled="true"/>
-            <label class="day" value="Tuesday" disabled="true"/>
-            <label class="day" value="Wednesday" disabled="true"/>
-            <label class="day" value="Thursday" disabled="true"/>
-            <label class="day" value="Friday" disabled="true"/>
-            <label class="day" value="Saturday" disabled="true"/>
-            </hbox>
-          </row>
-        </rows>
-      </grid>
-    <hbox class="buttons">
-      <button id="clear" label="Clear" accesskey="C"
-        oncommand="clearDate();"/>
-      <button id="today" label="Today" accesskey="T"
-        oncommand="setToday();"/>
-      </hbox>
-    </groupbox>
-
-  <statusbar>
-    <statusbarpanel id="status"/>
-    </statusbar>
-
-</vbox>
-
-</window>
-
-
- -

Crie um novo arquivo CSS, style7.css. Copie e cole o conteúdo daqui, tendo certeza de ter rolado a tela para pegar tudo isto:

- -
-
/*** XUL demonstration ***/
-window {
-  -moz-box-align: start;
-  background-color: -moz-dialog;
-  font: -moz-dialog;
-  padding: 2em;
-  }
-
-.head-1 {
-  font-weight: bold;
-  font-size: 200%;
-  padding-left: 5px;
-  }
-
-
-/* the group box */
-.demo-group {
-  padding: 1em;
-  }
-
-.demo-group grid {
-  margin-bottom: 1em;
-  }
-
-.demo-group column {
-  margin-right: .5em;
-  }
-
-.demo-group row {
-  margin-bottom: .5em;
-  }
-
-.demo-group .buttons {
-  -moz-box-pack: end;
-  }
-
-
-/* the day-of-week labels */
-.day {
-  margin-left: 1em;
-  }
-
-.day[disabled] {
-  color: #777;
-  }
-
-.day:first-child {
-  margin-left: 4px;
-  }
-
-
-/* the left column labels */
-.text-prompt {
-  padding-top: .25em;
-  }
-
-
-/* the date input box */
-#date-text {
-  max-width: 8em;
-  }
-
-
-/* the status bar */
-statusbar {
-  width: 100%;
-  border: 1px inset -moz-dialog;
-  margin: 4px;
-  padding: 0px 4px;
-  }
-
-#status {
-  padding: 4px;
-  }
-
-#status[warning] {
-  color: red;
-  }
-
-
- -

Crie um novo arquivo de texto, script7.js. Copie e cole o conteúdo daqui, tendo certeza de ter rolado a tela e pego todo o conteúdo daqui:

- -
-
// XUL demonstration
-
-var dateBox, dayBox, currentDay, status; // elements
-
-// called by window onLoad
-function init() {
-  dateBox = document.getElementById("date-text")
-  dayBox = document.getElementById("day-box")
-  status = document.getElementById("status")
-  setToday();
-  }
-
-// called by Clear button
-function clearDate() {
-  dateBox.value = ""
-  refresh()
-  }
-
-// called by Today button
-function setToday() {
-  var d = new Date()
-  dateBox.value = (d.getMonth() + 1)
-    + "/" + d.getDate()
-    + "/" + d.getFullYear()
-  refresh()
-  }
-
-// called by Date textbox
-function refresh() {
-  var d = dateBox.value
-  var theDate = null
-
-  showStatus(null)
-  if (d != "") {
-    try {
-      var a = d.split("/")
-      var theDate = new Date(a[2], a[0] - 1, a[1])
-      showStatus(theDate)
-      }
-    catch (ex) {}
-    }
-  setDay(theDate)
-  }
-
-// internal
-function setDay(aDate) {
-  if (currentDay) currentDay.setAttribute("disabled", "true")
-  if (aDate == null) currentDay = null
-  else {
-    var d = aDate.getDay()
-    currentDay = dayBox.firstChild
-    while (d-- > 0) currentDay = currentDay.nextSibling
-    currentDay.removeAttribute("disabled")
-    }
-  dateBox.focus();
-  }
-
-function showStatus(aDate) {
-  if (aDate == null) {
-    status.removeAttribute("warning")
-    status.setAttribute("label", "")
-    }
-  else if (aDate === false || isNaN(aDate.getTime())) {
-    status.setAttribute("warning", "true")
-    status.setAttribute("label", "Date is not valid")
-    }
-  else {
-    status.removeAttribute("warning")
-    status.setAttribute("label", aDate.toLocaleDateString())
-    }
-  }
-
-
- -

Para ver o resultado exatamente como pretendido use o tema padrão do seu navegador. Se você usa um tema diferente, isto mode mudar alguns estilos da interface do usuário e a demonstração pode parecer estranha.

- -

Abra o documento no seu navegador Mozilla e use a interface.

- -

Este wiki não suporta XUL e JavaScript nas páginas, então não é possível fazer a demonstração aqui. Deve se parecer com isto:

- - - - - - - -
-

XUL demonstration

- -
-

Day of week calculator

- - - - - - - - - - - - - - - - -
Date:6/27/2005
Day:Sunday Monday Tuesday Wednesday Thurdsay Friday Saturday
-
-

Clear Today

-
-
-
- -
-

June 27, 2005

-
-
- -

Notas sobre esta demonstração:

- - - -

Examine a folha de estilo do documento para ver se você entende todas as regras dele. Se houver alguma regra que você não entende, comente-a e atualize o seu navegador para ver o efeito no documento.

- - - - - - - - -
Desafio
Use a ferramenta DOM Inspector para examinar a caixa de texto Date. Ela é feita de outros elementos que são gerados por seu XBL binding. -

Descubra a classe do elemento html:input. Este é o elemento que atualmente recebe a entrada do usuário.

- -

Usando este conhecimento, adicione uma regra à sua folha de estilo que faça o fundo da caixa Date de um azul pálido quando ele tiver o foco do teclado (mas branco quando o foco do teclado estiver em outro lugar).

-
- -

O que vem depois?

- -

Se você teve dificuldade para entender esta página, ou se você tem algum comentário sobre ela, por favor contribua nesta página de Discussão.

- -

Nesta demonstração, você viu que as formas retangulares padrão são comuns na maioria das interfaces de usuário. Mozilla também suporta uma linguagem especializada de gráficos para criar padrões, usando folhas de estilo CSS para especificar o estilo. A próxima página demonstra isto: Gráficos SVG

- -

{{ PreviousNext("CSS:Como começar:XBL bindings", "CSS:Como começar:Gráficos SVG") }}

diff --git a/files/pt-pt/web/javascript/novidades_no_javascript/index.html b/files/pt-pt/web/javascript/novidades_no_javascript/index.html deleted file mode 100644 index 42d40e9929..0000000000 --- a/files/pt-pt/web/javascript/novidades_no_javascript/index.html +++ /dev/null @@ -1,80 +0,0 @@ ---- -title: Novidades no JavaScript -slug: Web/JavaScript/Novidades_no_JavaScript -tags: - - NeedsTranslation - - TopicStub -translation_of: Archive/Web/JavaScript/New_in_JavaScript ---- -
{{jsSidebar("New_in_JS")}}
- -

This chapter contains information about JavaScript's version history and implementation status for Mozilla/SpiderMonkey-based JavaScript applications, such as Firefox.

- -

ECMAScript versions

- -
-
Language resources
-
Learn more about the ECMAScript standards on which the JavaScript language is based on.
-
ECMAScript 5 support
-
Implementation status for the current standard ECMA-262 Edition 5.1 in Mozilla-based engines and products.
-
ECMAScript 6 support
-
Implementation status for the draft ECMA-262 Edition 6 in Mozilla-based engines and products.
-
ECMAScript 7 support
-
Implementation status for the upcoming ECMA-262 Edition 7 in Mozilla-based engines and products.
-
- -

JavaScript release notes

- -
-
Firefox JavaScript changelog
-
See this changelog for JavaScript features implemented in Firefox 5 and later.
-
Chrome JavaScript changelog
-
(TODO). See this changelog for JavaScript features implemented in Chrome releases.
-
- -

JavaScript versions

- -

Deprecated ({{deprecated_inline()}}). The explicit versioning and opt-in of language features was Mozilla-specific and is in process of being removed. Firefox 4 was the last version which referred to an JavaScript version (1.8.5). With new ECMA standards, JavaScript language features are now often mentioned with their initial definition in ECMA-262 Editions such as Edition 6 (ES6).

- -

JavaScript was released as version 1.0 in March 1996 in Netscape Navigator 2.0 and Internet Explorer 2.0.

- -
-
JavaScript 1.1
-
Version shipped in Netscape Navigator 3.0. Released on August 19, 1996.
-
JavaScript 1.2
-
Version shipped in Netscape Navigator 4.0-4.05. Released on June 11, 1997.
-
JavaScript 1.3
-
Version shipped in Netscape Navigator 4.06-4.7x. Released on October 19, 1998.
- Standardization work to be compliant with ECMA-262 1st and 2nd Edition.
-
JavaScript 1.4
-
Version shipped in Netscape's server side JavaScript. Released in 1999.
-
JavaScript 1.5
-
Version shipped in Netscape Navigator 6.0 and Firefox 1.0. Release on November 14, 2000.
- Standardization work to be compliant with ECMA-262 3rd Edition.
-
JavaScript 1.6
-
Version shipped in Firefox 1.5. Released in November 2005.
- Includes ECMAScript for XML (E4X), new Array methods plus String and Array generics.
-
JavaScript 1.7
-
Version shipped in Firefox 2. Released in October 2006.
- Includes generators, iterators, array comprehensions, let expressions, and destructuring assignment.
-
JavaScript 1.8
-
Version shipped in Firefox 3. Released in June 2008.
- Includes expression closures, generator expressions and Array.reduce()
-
JavaScript 1.8.1
-
Version shipped in Firefox 3.5. Released on June 30, 2009.
- Includes the TraceMonkey JIT and supports native JSON.
-
JavaScript 1.8.2
-
Version shipped in Firefox 3.6. Released June 22, 2009.
- Includes only minor changes.
-
JavaScript 1.8.5
-
Version shipped in Firefox 4. Released July 27, 2010.
- Includes many new features for ECMA-262 Edition 5 compliance.
- This is the last JavaScript version.
-
- -

Features still requiring version opt-in

- -
-
let statement
-
The let statement requires the JavaScript version 1.7 (or higher) opt-in. See {{bug(932517)}} and {{bug(932513)}}.
-
diff --git a/files/pt-pt/web/javascript/novidades_no_javascript/novidades_no_javascript_1.8/index.html b/files/pt-pt/web/javascript/novidades_no_javascript/novidades_no_javascript_1.8/index.html deleted file mode 100644 index 4791e4d0e9..0000000000 --- a/files/pt-pt/web/javascript/novidades_no_javascript/novidades_no_javascript_1.8/index.html +++ /dev/null @@ -1,136 +0,0 @@ ---- -title: Novidades no Javascript 1.8 -slug: Web/JavaScript/Novidades_no_JavaScript/Novidades_no_Javascript_1.8 -tags: - - JavaScript - - Todas_as_Categorias -translation_of: Archive/Web/JavaScript/New_in_JavaScript/1.8 ---- -

{{jsSidebar("New_in_JS")}}

- -

O JavaScript 1.8 está programado para ser lançado como parte do Gecko 1.9 (que será incorporado ao Firefox 3). Esta é uma atualização menos substancial que o JavaScript 1.7, mas tem algumas atualizações para acompanhar o progresso rumo ao ECMAScript 4/JavaScript 2. Esta liberação incluirá todas as novas características especificadas no JavaScript 1.6 e JavaScript 1.7.

- -

Veja o {{ Bug(380236) }} para acompanhar o progresso do desenvolvimento do JavaScript 1.8.

- -

Usando JavaScript 1.8

- -

A fim de usar algumas das novas características do JavaScript 1.8 no HTML, use:

- -
 <script type="application/javascript;version=1.8"> ... seu código ... </script>
-
- -

Quando usando o JavaScript shell, componentes XPCOM ou elementos XUL <script>, a versão mais recente do Javascript (1.8 no Mozilla 1.9) é usada automaticamente ({{ Bug(381031) }}, {{ Bug(385159) }}).

- -

Os recursos que requerem o uso das novas palavras-chave "yield" e "let" requerem que você especifique a versão 1.7 ou mais recente, porque o código existente pode usar estas palavras-chave como variáveis ou nomes de função. Os recursos que não introduzem novas palavras-chave (como o gerador de expressões) podem ser usados sem que seja necessário especificar a versão do JavaScript.

- -

Fechamentos de expressões

- -

Esta adição nada mais é que uma abreviação para escrever funções simples, dando à linguagem algo similar a uma típica notação lambda.

- -

JavaScript 1.7 e mais antigos:

- -
 function(x) { return x * x; }
-
- -

JavaScript 1.8:

- -
 function(x) x * x
-
- -

Esta sintaxe permite que você deixe de fora as chaves e a declaração 'return' — fazendo-as implícitas. Não há benefício adicionado ao se escrever código desta maneira, à exceção de ser sintaticamente mais curto.

- -

Exemplos:

- -

Uma abreviação para ligar ouvintes de evento:

- -
 document.addEventListener("click", function() false, true);
-
- -

Usando esta notação com alguma das funções de array do JavaScript 1.6:

- -
 elems.some(function(elem) elem.type == "text");
-
- -

Gerador de expressões

- -

Esta adição permite que você crie geradores de maneira simples (que foram introduzidos no JavaScript 1.7). Tipicamente você teria que criar uma função personalizada contendo a palavra-chave yield, mas esta adição permite que você use uma sintaxe semelhante à compreensão de arrays para criar uma instrução geradora idêntica.

- -

No JavaScript 1.7, você poderia escrever algo como o seguinte, a fim de criar um gerador personalizado para um objeto:

- -
 function add3(obj) {
-   for ( let i in obj )
-     yield i + 3;
- }
-
- let it = add3(someObj);
- try {
-   while (true) {
-     document.write(it.next() + "<br>\n");
-   }
- } catch (err if err instanceof StopIteration) {
-   document.write("End of record.<br>\n");
- }
-
- -

No JavaScript 1.8, você pode contornar a criação de uma função de gerador personalizada usando um gerador de expressões em vez disso:

- -
 let it = (i + 3 for (i in someObj));
- try {
-   while (true) {
-     document.write(it.next() + "<br>\n");
-   }
- } catch (err if err instanceof StopIteration) {
-   document.write("End of record.<br>\n");
- }
-
- -

Geradores de expressões também podem ser passados como valores a uma função. Isto é particularmente notável de modo que geradores não serão executados antes que seja absolutamente necessário (diferente de típicas situações de compreensão de array, onde os arrays são construídos antes do tempo). Um exemplo da diferença pode ser visto aqui:

- -

Usando a compreensão de array do JavaScript 1.7

- -
 handleResults([ i for ( i in obj ) if ( i > 3 ) ]);
-
- function handleResults( results ) {
-   for ( let i in results )
-     // ...
- }
-
- -

Usando o gerador de expressões do JavaScript 1.8

- -
 handleResults( i for ( i in obj ) if ( i > 3 ) );
-
- function handleResults( results ) {
-   for ( let i in results )
-     // ...
- }
-
- -

A diferença significativa entre os dois exemplos, começando pelo que usa o gerador de expressões, é que você poderia usar somente o loop uma vez sobre a estrutura 'obj', ao invés de uma vez compreender o array e novamente iterar com ele.

- -

Mais extras do Array

- -

Existem dois novos métodos iterativos de Array incluídos no JavaScript 1.8, especificamente:

- - - -

Mudanças na desestruturação for..in

- -

Menção em en:New_in_JavaScript_1.7#Looping_across_objects ({{ Bug(366941) }}).

- -

Mudanças iminentes

- -

As mudanças esperadas para a chegada no JavaScript 1.8 incluem:

- - - -

Categorias

- -

Interwiki Language Links

diff --git a/files/pt-pt/xpcom_interface_reference/index.html b/files/pt-pt/xpcom_interface_reference/index.html deleted file mode 100644 index db45c7237c..0000000000 --- a/files/pt-pt/xpcom_interface_reference/index.html +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: XPCOM Interface Reference -slug: XPCOM_Interface_Reference -tags: - - NeedsTranslation - - TopicStub - - XPCOM - - XPCOM Interface Reference -translation_of: Mozilla/Tech/XPCOM/Reference/Interface ---- -

This is a reference to the XPCOM interfaces provided by the Mozilla platform.

-
- {{tree('','1')}}
-

See also

- diff --git a/files/pt-pt/xul/attribute/index.html b/files/pt-pt/xul/attribute/index.html deleted file mode 100644 index 48a1cf4f0c..0000000000 --- a/files/pt-pt/xul/attribute/index.html +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Attribute -slug: XUL/Attribute ---- -{{wiki.localize('System.API.page-generated-for-subpage')}} diff --git a/files/pt-pt/xul/attribute/textbox.type/index.html b/files/pt-pt/xul/attribute/textbox.type/index.html deleted file mode 100644 index 54bf9f518a..0000000000 --- a/files/pt-pt/xul/attribute/textbox.type/index.html +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: textbox.type -slug: XUL/Attribute/textbox.type ---- -

« XUL Reference home -

-
type -
Type: um dos valores abaixo -
Você pode configurar o atributo type para um dos valores abaixo para uma tipo mais específico de caixa de texto. Não configure o tipo se você deseja usar uma caixa de texto regular. -
- -

Veja também

- -

Categorias -

Interwiki Language Links -

diff --git a/files/pt-pt/zonas/index.html b/files/pt-pt/zonas/index.html deleted file mode 100644 index 37c44c4cbe..0000000000 --- a/files/pt-pt/zonas/index.html +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Zonas -slug: Zonas -translation_of: Zones ---- -

MDN zones provide you with one-stop access to information about specific topic areas or products. Here's a list of all the zones available to you.

- -
-
-

Desenvolvimento de aplicações e da Web

- -
-
Centro de Aplicações
-
Learn how to create open Web apps—rich experiences that run across multiple devices and form factors—using the same Web standards and open technologies you already know.
-
Área de Apredizagem
-
This zone is all about articles to help newcomers to Web development get started in this exciting new world.
-
Ferramentas de programador
-
Learn how to use the Firefox developer tools to debug, test, and optimize your Web apps and sites.
-
Mercado do Firefox
-
An open, non-proprietary online marketplace for Web applications built using HTML, CSS, and JavaScript. Submit apps to the Firefox Marketplace or use the code to build your own marketplace.
-
Desenvolvimento de jogos
-
Learn how to develop games for the Web, how to port existing games to Web technologies, and how to turn your games into Web apps.
-
-
- -
-

Produtos e projetos

- -
-
Emscripten
-
An LLVM to JavaScript compiler; this lets you compile, for example, C++ code into JavaScript code which can be run in any Web browser.
-
L20n
-
A JavaScript localization framework for unleashing your natural language's power with simple code.
-
O projeto MDN
-
The Mozilla Developer Network (this site) relies on its community of readers and contributors to grow and improve. You can learn here how to help use, contribute to, and build the code behind MDN!
-
Persona
-
A new simple, privacy-sensitive single-sign in system developed by Mozilla which lets users log into your Web site using their email address, freeing you from password management.
-
- -

Tecnologias Mozilla

- -
-
Extras
-
Learn how to build and install extensions, themes, and plug-ins for Mozilla-based software, including the popular Firefox Web browser.
-
Firefox
-
Learn all about Firefox, from how to build and revise it to how to build add-ons specifically for it.
-
Firefox OS
-
A new mobile operating system developed by Mozilla which lets users install and run open Web applications created using HTML, CSS, and JavaScript.
-
-
-
- -

 

-- cgit v1.2.3-54-g00ecf