1,007
edits
Labs/Site 2.0/Existing site replacement/Site content/Ubiquity: Difference between revisions
Labs/Site 2.0/Existing site replacement/Site content/Ubiquity (view source)
Revision as of 03:48, 4 July 2009
, 4 July 2009→Write Commands
| (6 intermediate revisions by the same user not shown) | |||
| Line 26: | Line 26: | ||
== Initial blog post == | == Initial blog post == | ||
'''Re-Introducing Ubiquity''' | |||
As a Labs project, Ubiquity is an investigation into two areas. The first is '''linguistic interfaces''' -- interfaces where you type what you want to do. Can such an interface be made practical as a part of everyday internet use? Can it be made close enough to natural language that people can discover how to use it without special training? Does it have significant speed advantages over a mouse-based interface? Can it be made good enough at understanding the user's intentions that it is just as usable as a point-and-click interface? Can it do all this for more languages than just English? | |||
The second area of investigation is what we call '''verbifying the Web'''. More and more websites are ''things that you do'' rather than ''places that you go to''. We Digg things, Tweet things, Google for things, blog things, map things, and so on. But in most cases, using one of these services requires copying some text, going to the appropriate website, and pasting it into a form. How about if the interface to the Web treated these services as tools that you can pick up and take with you, to use anywhere, instead of treating them as destinations? | |||
Ubiquity commands are small chunks of javascript which can interface with web services. Any website can offer Ubiquity commands; any Ubiquity user who visits the site can see the commands and choose whether to subscribe to them. Once subscribed to, those commands can be used anywhere. | |||
== Project blurb + tagline == | == Project blurb + tagline == | ||
| Line 79: | Line 86: | ||
=== Write Commands === | === Write Commands === | ||
Ubiquity commands are written in Javascript. You can open the built-in command editor by running the "open command editor" command. This is the fastest and easiest way to prototype new commands, as you won't have to restart Firefox or reload anything to see the changes in your commands. The command editor even has a button to import a template so you can | |||
[https://wiki.mozilla.org/Labs/Ubiquity/Ubiquity_0.5_Author_Tutorial The Command Author Tutorial] explains everything you need to know about the API for writing commands and the many features and options that are available to you as a command developer. | |||
If you wish to share your command with others, the above tutorial explains how to do that, too. | |||
You should also read the brief guide to [https://wiki.mozilla.org/Labs/Ubiquity/Secure_Coding_Practices secure coding practices] for Ubiquity commands, which includes making the decision about whether to share your command using the more powerful but less secure Standard Feed, or the more restricted but more secure Locked-Down Feed. | |||
Finally, there is also a [https://wiki.mozilla.org/Labs/Ubiquity/Skins_v0.5 skinning tutorial] that explains how to customize the skin of the Ubiquity interface. | |||
=== Improve Ubiquity === | === Improve Ubiquity === | ||
| Line 84: | Line 101: | ||
You don't have to be a coder to help improve Ubiquity. We're looking for Javascript coders to help out, but we're also looking for testers, translators, and people who can write good documentation. | You don't have to be a coder to help improve Ubiquity. We're looking for Javascript coders to help out, but we're also looking for testers, translators, and people who can write good documentation. | ||
'''Test and Triage Bugs''' | |||
# [https://ubiquity.mozilla.com/trac/report/1 Issue Tracker] - Used to report/discuss bugs and submit patches for Ubiquity. | # [https://ubiquity.mozilla.com/trac/report/1 Issue Tracker] - Used to report/discuss bugs and submit patches for Ubiquity. | ||
# [[Labs/Ubiquity/Trac Components and Keywords|Trac Components and Keywords]] - Keywords and categories to use when filing Trac tickets. | # [[Labs/Ubiquity/Trac Components and Keywords|Trac Components and Keywords]] - Keywords and categories to use when filing Trac tickets. | ||
Write documentation | '''Write documentation''' | ||
# [[Labs/Ubiquity/0.5_Documentation|Help Document the 0.5 code here]] - working copies of the wiki documentation for the latest source version | # [[Labs/Ubiquity/0.5_Documentation|Help Document the 0.5 code here]] - working copies of the wiki documentation for the latest source version | ||
| Line 104: | Line 113: | ||
# [[Labs/Ubiquity/Interactive_Tutorial_Workspace|Help us improve the interactive tutorial by editing this page]] | # [[Labs/Ubiquity/Interactive_Tutorial_Workspace|Help us improve the interactive tutorial by editing this page]] | ||
'''Localize''' | |||
Help localize Ubiquity to your language! Ubiquity has already been partly translated to Danish, English, Japanese, and Portugese, and volunteer localizers are working on many other languages too. | Help localize Ubiquity to your language! Ubiquity has already been partly translated to Danish, English, Japanese, and Portugese, and volunteer localizers are working on many other languages too. | ||
| Line 109: | Line 119: | ||
# [[Labs/Ubiquity/Parser_2/Localization_Tutorial|Localizing Ubiquity to Your Language]] | # [[Labs/Ubiquity/Parser_2/Localization_Tutorial|Localizing Ubiquity to Your Language]] | ||
# [[Labs/Ubiquity/Ubiquity_0.5_Command_Localization_Tutorial|Localizing Commands to Your Language]] | # [[Labs/Ubiquity/Ubiquity_0.5_Command_Localization_Tutorial|Localizing Commands to Your Language]] | ||
# [http://groups.google.com/group/ubiquity-i18n Ubiquity i18n Google Group/mailing list] for discussion of internationalization and localization topics | |||
Help out other users | |||
'''Help out other users''' | |||
# [http://groups.google.com/group/ubiquity-firefox General Google Group/mailing list] - Useful for discussion of command development, user interface, feature suggestions, and other high-level discussions. | # [http://groups.google.com/group/ubiquity-firefox General Google Group/mailing list] - Useful for discussion of command development, user interface, feature suggestions, and other high-level discussions. | ||
'''Write code''' | |||
# [https://wiki.mozilla.org/Labs/Ubiquity/Meetings Developer meetings] are open to anyone to call into: main Mozilla number, extension 92, conference room 202, at 5pm Pacific time on Wednesdays. Any changes to the meeting schedule are announced on the mailing list. | |||
# [http://groups.google.com/group/ubiquity-core Core Google Group/mailing list] - Discussion of low-level internals of Ubiquity. | |||
# [https://ubiquity.mozilla.com/hg/ubiquity-firefox/ Ubiquity HG Repository] - The Mercurial source code repository for Ubiquity. | |||
# [https://ubiquity.mozilla.com/hg/ubiquity-firefox/raw-file/tip/ubiquity/index.html Ubiquity Code Documentation] - Generated from the latest source code via [http://code.google.com/p/code-illuminated Code Illuminated]. | |||
# [[Labs/Ubiquity/Ubiquity 0.1_Development_Tutorial|Contributing to Core Development]] | |||
== Privacy + Legal notices == | == Privacy + Legal notices == | ||
There are no Ubiquity-specific notices yet. | There are no Ubiquity-specific notices yet. | ||