Firefox/Feature Brainstorming: Difference between revisions

Jump to navigation Jump to search

Firefox/Feature Brainstorming (view source)

Revision as of 23:05, 15 October 2006

2,252 bytes removed ,  15 October 2006
m
→‎More Bullshit vs. Less Bullshit: unnecessary language (will fix formatting of the whole page this wk)
m (→‎More Bullshit vs. Less Bullshit: unnecessary language (will fix formatting of the whole page this wk))
Line 43: Line 43:
; Download Progress in OSX
; Download Progress in OSX
* Implement the download progress icon on incomplete file downloads on Mac OS X like Safari and Cyberduck.
* Implement the download progress icon on incomplete file downloads on Mac OS X like Safari and Cyberduck.
</td></tr>
<tr><td>
; Services Integration in OSX
* Firefox does not supports Mac OS X services so that all the commands available in the "Services" menu are disabled. Other OS X applications (es. Safari) allows the user to use a services when some data, like a text, is selected.
</td></tr>
</td></tr>
<tr><td>
<tr><td>
Line 404: Line 400:
<tr><td>
<tr><td>
; Tabs
; Tabs
* The close [X] button should only be shown on the open tab to prevent people from accidentally closing tabs upon selecting them. Close buttons on out-of-focus tabs should only show after a 1 second mouse-over.
* Allow the tab-bar relocation, probably with a simple pull-down, that includes top, bottom, left and right.
* Allow the tab-bar relocation, probably with a simple pull-down, that includes top, bottom, left and right.
** When left or right are selected (or perhaps all the time), provide the ability to specify a fixed width for tabs/tab-bar.
** When left or right are selected (or perhaps all the time), provide the ability to specify a fixed width for tabs/tab-bar.
Line 1,834: Line 1,829:
</table>
</table>


== Feeds Handling ==
== Feeds and Microformat handling ==
<table class="fullwidth-table">
<table class="fullwidth-table">
<tr><th>Specific features</th>
<tr><th>Specific features</th>
Line 1,872: Line 1,867:
</td></tr>
</td></tr>


<tr><th colspan="2">General tasks</th></tr>
<tr><td>
<tr><td>
n/a
; Microformat Detection
* Automatically harvesting web data like mailto: link addresses, atom/RSS feed links, dates + events, other info…?
* Web data manager for browsing/searching/using auto-harvested data and microformats
* Web data preferences - What would be nice is a rules interface for web content similar to mail.  "if any of the following conditions are met, perform the following actions..."  So for example, add to address book all hcards that contain "@mozilla.com" in the email field.
</td><td>
</td><td>
n/a
- [http://simile.mit.edu/piggy-bank/ Piggy Bank]<br />
</td></tr>
</td></tr>
</table>
== Microformat Handling ==
<table class="fullwidth-table">
<tr><th>Specific features</th>
<th width="30%">References</th></tr>
<tr><td>
; Microformat Detection
* As users interact online, data elements would be detected by parsing micro-formatted content or implicit/latent micro-formats such as FedEx/UPS tracking numbers, AIM screen names, etc..
* The detectors themselves could be plug-able, so that users may replace the default detectors or add new detectors for specific content types.  Thus, research, innovation, and communities could form around creating the highest quality and most accurate content detectors.
</td>
<td></td>
</tr>
<tr><td>
; Microformat Actions
* Contextual menu items could allow users to apply actions to detected data elements.  For example, contextual menu actions for detected hCards could include "add to address book," "email contact," "dial number with Skype" etc. 
* Contextual menu add-ons could be created to link detected data elements to online services.  For example, a user could right-click an identified hCard address to save it to LinkedIn or Plaxo, or right-click a hCalendar event to save it to Google Calendar or Upcoming.org.
* Since other data detectors such as Microsoft Smart Tags and Google AutoLink redirect users to each company's respective online properties, an open system would allow users to associate content types to their choice of online services.
</td>
<td></td>
</tr>
<tr><td>
; Microformat Collection and Storage
* Once data elements are detected, they could then be normalized according to a universal schema and then added to a local data store.
* User preferences or rules engines for web content would control how information is collected and saved.  A rule would allow a user to do things like save all detected hCards found within a particular domain, etc.  Distinctions would need to be made between data that is cached or explicitly saved.
* Additionally, metadata such as timestamp, source, subject, annotations, tags, user context, etc. could also be captured, perhaps within some type of metadata index.
* Thus, the utility and value of collected data increases as information assets increase over time.
</td>
<td>
- [http://simile.mit.edu/piggy-bank/ Piggy Bank]<br />
</td>
</tr>
<tr><th colspan="2">General tasks</th></tr>
<tr><th colspan="2">General tasks</th></tr>
<tr><td>
<tr><td>
Dria
canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/36937"

Navigation menu