canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,043
edits
Update:Archive/2.0/Developers: Difference between revisions
m
Update:Development:v2.0 moved to Update:Archive/2.0/Developers
No edit summary |
m (Update:Development:v2.0 moved to Update:Archive/2.0/Developers) |
||
| (20 intermediate revisions by 8 users not shown) | |||
| Line 57: | Line 57: | ||
We will do our best to adhere to the Mozilla coding standards. Since not many Mozilla projects are written in PHP, we have [[Update:Development:Best Practices|developed our own]] where necessary. | We will do our best to adhere to the Mozilla coding standards. Since not many Mozilla projects are written in PHP, we have [[Update:Development:Best Practices|developed our own]] where necessary. | ||
== TODO == | |||
* [http://lxr.mozilla.org/mozilla/source/webtools/addons/lib/session.class.php lib/session.class.php] | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=312629 simple session handler based on sid.] | |||
* lib/auth.class.php | |||
** simple session checker and auth module. | |||
** PEAR::Auth? | |||
* [http://lxr.mozilla.org/mozilla/source/webtools/addons/addcomment.php addcomment.php] - Colin | |||
** form | |||
** spam prevention - '''require login''' | |||
** input validation | |||
* <strike>[http://lxr.mozilla.org/mozilla/source/webtools/addons/addon.php addon.php]</strike> | |||
** <strike>sidebar</strike> | |||
** show compat information | |||
* [http://lxr.mozilla.org/mozilla/source/webtools/addons/history.php history.php] - Colin | |||
** show all past versions - initially done but needs improvement... | |||
** simplify? | |||
* <strike>index.php</strike> | |||
** <strike>make it look more like overview.php?</strike> | |||
* previews.php - Colin | |||
** <strike>Show all Addon previews.</strike> | |||
* ratecomment.php - Colin | |||
** spam prevention '''This needs to be thought about'''. | |||
** <strike>other than that, this is a simple toggle script.</strike> | |||
** <strike>login isn't required for this particular page.</strike> | |||
* search.php | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=277851 highlight search results] | |||
** <strike>Create search form based on DB.</strike> | |||
** <strike>Filter inputs.</strike> | |||
** <strike>Document needed options.</strike> | |||
** <strike>Create jump-to for one-result searches.</strike> | |||
* header / footer / style | |||
** Fix key-menu so that it is simplified. Each app link should be a tab, instead of offering 3 different choices per. | |||
** <strike>Make the search stick out more -- this is a key feature of this site.</strike> | |||
** <strike>Make sure CSS changes work in multiple browsers.</strike> | |||
* addon.class.php | |||
** <strike>Move manual queries in constructor to respective functions (i.e. getLatestVersion() instead of a hard query)</strike> | |||
== Use-cases and Requirements == | == Use-cases and Requirements == | ||
| Line 81: | Line 118: | ||
:How about a "my favorite extensions" section with details of latest versions and comments. Users could then "bookmark" extensions they're interested in, but might not have installed. It could also automatically keep track of extensions installed, and visted but uninstalled extensions (something like Google's My Search History). It might encourage more users to register as it's providing something of value to them. Stats could be used for recomendations. You could also track which extensions are being removed from peoples favorites. --[[User:Sam Hasler|Sam]] 14:25, 17 Jun 2005 (PDT) | :How about a "my favorite extensions" section with details of latest versions and comments. Users could then "bookmark" extensions they're interested in, but might not have installed. It could also automatically keep track of extensions installed, and visted but uninstalled extensions (something like Google's My Search History). It might encourage more users to register as it's providing something of value to them. Stats could be used for recomendations. You could also track which extensions are being removed from peoples favorites. --[[User:Sam Hasler|Sam]] 14:25, 17 Jun 2005 (PDT) | ||
:Heh. No one has written here in awhile. | |||
Maybe I'm missing something, but the main page right now doesn't even have links to look for TB extensions, or extensions for any other Moz apps besides FF. Clicking on the extensions button on the front page automatically takes you into a page showing FF extensions. So... is there no way to get to TB extensions without either going through TB or doing some sort of search? | |||
--[[User:Wjjohnst|DigDug] 22:20 05 Oct, 2006 | |||
==== Search By... ==== | ==== Search By... ==== | ||
| Line 105: | Line 148: | ||
:so, this means we need to use a column-type display for the results. I'm not sure if that's always good. Maybe only use it for advanced searches, but quicksearch gets the current-style result list? --[[User:CTho|CTho]] 19:05, 13 Jun 2005 (PDT) | :so, this means we need to use a column-type display for the results. I'm not sure if that's always good. Maybe only use it for advanced searches, but quicksearch gets the current-style result list? --[[User:CTho|CTho]] 19:05, 13 Jun 2005 (PDT) | ||
I would go for search results that have an extended result by clicking on an image with the "more" concept. Those extended results would be hidden in DIVs that will be shown bellow the line of the extension summary when the user clicks the "more" image. This is client side or if we want smaller pages we can use AJAX to bring this extended content when needed. --[[User:DonGato|DonGato]] 11:57, 28 Nov 2006 (GMT) | |||
==== Item Home ==== | ==== Item Home ==== | ||
| Line 385: | Line 430: | ||
=== Administrators === | === Administrators === | ||
* Administrators should basically have all the general functionality of all other user groups, with added rights to _all_ records and the ability to edit/bless user accounts. | * Administrators should basically have all the general functionality of all other user groups, with added rights to _all_ records and the ability to edit/bless user accounts. | ||
* It's currently too hard to create new reviewers - it requires receiving an email (the intial request), replying to tell the user to create an account, waiting for the reply, then granting them Editor privileges. This should be streamlined - maybe just a "Volunteer to be a reviewer" button on the developer pages? --[[User:CTho|CTho]] 17:58, 4 Oct 2005 (PDT) | |||
=== Systems === | === Systems === | ||
| Line 408: | Line 454: | ||
== Application Structure == | == Application Structure == | ||
; .htaccess : Set up include_path, prepend and append options. | ; .htaccess : Set up include_path, prepend and append options. | ||
; | ; addcomment.php : Add a new comment. | ||
; | ; ratecomment.php : Rate an existing comment. | ||
; comments.php : View comments for an addon. | |||
; css/ : CSS layout and formatting. | ; css/ : CSS layout and formatting. | ||
; developers : Developer tools used by developers, reviewers and admins. | ; developers : Developer tools used by developers, reviewers and admins. | ||
| Line 421: | Line 468: | ||
; LICENSE : Application license. | ; LICENSE : Application license. | ||
; README : Installation instructions for site developers. | ; README : Installation instructions for site developers. | ||
; previews.php : Addon previews. | |||
; rss : Syndicated information for addons based on type and application. | ; rss : Syndicated information for addons based on type and application. | ||
; search.php : Search for addons using a simple search, or expand simple search to refine your search. | ; search.php : Search for addons using a simple search, or expand simple search to refine your search. | ||
| Line 437: | Line 485: | ||
** Downloaded .xpi does not match reported size (5) | ** Downloaded .xpi does not match reported size (5) | ||
* There is a need client-side to implement better update features for addons, similar to those found in [Software Update]. In particular, hash checking and improved error handling (for errors above) would be great additions. | * There is a need client-side to implement better update features for addons, similar to those found in [Software Update]. In particular, hash checking and improved error handling (for errors above) would be great additions. | ||
== UI Tweaks == | |||
* Alignment of title / drop-down on 'Search Options' sidebar would look better uniform (columned). | |||
* Blue bar at the top (below 'mozilla update' text) looks incredibly empty, especially towards the right. If it's going to remain empty, perhaps consider moving the search to the right. | |||
* Tabs on home page | |||
** Incredibly plain / square. | |||
** Blue on inactive tabs doesn't really fit with the rest of the UI. | |||
** Perhaps consider using the same style tabs as on the header of this wiki? | |||