Update:Remora Feedback: Difference between revisions

Jump to navigation Jump to search
Line 101: Line 101:
The feedback (bugs, suggestions) that we fixed/dealt with were moved to a [[Update:Remora Feedback/Alpha Feedback Fixed|reference page]].
The feedback (bugs, suggestions) that we fixed/dealt with were moved to a [[Update:Remora Feedback/Alpha Feedback Fixed|reference page]].


== fligtar's comments ==
If your comments/name has been removed from this page, your comments have either been fixed, or moved to bugzilla.  Thanks.  --clouserw, 2006-02-28
All comments fixed (2006-02-28)
 
== clouserw's comments ==
* All comments moved to bugs (2006-02-26)


== wenzel's comments ==
== wenzel's comments ==
* Search algorithm is improvable: The binary matching creates many hits with the same score in spite of their obviously different relevance.
* Search algorithm is improvable: The binary matching creates many hits with the same score in spite of their obviously different relevance.
* "find similar add-ons" sometimes shows different categories with the same name?  ([http://preview.addons.mozilla.org/en-US/addons/display/398 example])
* "find similar add-ons" sometimes shows different categories with the same name?  ([http://preview.addons.mozilla.org/en-US/addons/display/398 example])
== dria's comments ==
* Seems to be a bug at [http://preview.addons.mozilla.org/en-US/discussions/post.php?AddOnID=398] when not logged in.  At very least there should be a significantly friendlier message suggesting the user log in :)


== Dao's comments ==
== Dao's comments ==
* I don't see how the user is expected to find, say, Thunderbird extensions. AMO2 was too Firefox-centric, AMO3 seems even worse. http://www.erweiterungen.de/ does this better.
* I don't see how the user is expected to find, say, Thunderbird extensions. AMO2 was too Firefox-centric, AMO3 seems even worse. http://www.erweiterungen.de/ does this better.
** answer from cameleon: I fill the [https://bugzilla.mozilla.org/show_bug.cgi?id=367574 Bug 367574] – Ability to filter search of an Add-ons by application (Firefox or Thunderbird) on bugzilla about this problem.
** answer from cameleon: I fill the [https://bugzilla.mozilla.org/show_bug.cgi?id=367574 Bug 367574] – Ability to filter search of an Add-ons by application (Firefox or Thunderbird) on bugzilla about this problem.
== DonGato's comments ==
All comments fixed (2006-02-28)
== pascalc's comments ==
All Comments addressed in bugs (2006-02-26)


== RenegadeX's comments ==
== RenegadeX's comments ==
It's hard to test the Preview site properly with the limited # of addons currently added, but I 2nd everything already said on this page. Have you guys learnt nothing over 3+ revisions of AMO? Users are tearing out their hair crying, "All I want to do is find a specific addon or browse the mass of addons quickly and easily" - and yet with each AMO revision, it continues to be a frustrating experience:
* On an [http://preview.addons.mozilla.org/en-US/addons/display/138 Extension(or Theme)'s page], you have the Extension Name followed by Version# on the same line (good to see it back, thanks - v2 was not good). Further down the page you have Version# and timestamp, which is thus partially redundant & a waste of space. Suggestion: go back to something closer to v1's implementation ([http://img222.imageshack.us/img222/9222/amoextensionspage2oldlo0.jpg screenshot]) which put it all at the top. Clean it up a little by putting the 'released on..' on its own line.
* On an [http://preview.addons.mozilla.org/en-US/addons/display/138 Extension(or Theme)'s page], you have the Extension Name followed by Version# on the same line (good to see it back, thanks - v2 was not good). Further down the page you have Version# and timestamp, which is thus partially redundant & a waste of space. Suggestion: go back to something closer to v1's implementation ([http://img222.imageshack.us/img222/9222/amoextensionspage2oldlo0.jpg screenshot]) which put it all at the top. Clean it up a little by putting the 'released on..' on its own line.
* Ditto the above - move it up, on the other listing pages (such as [http://preview.addons.mozilla.org/en-US/addons/recommended/ Recommended Add-ons]).
'' I could easily go on with my list but this is getting depressing. This thing was meant to be an improvement, was it not? Come on, this shouldn't be this difficult!'''
[[User:RenegadeX|RenegadeX]] 04:26, 17 January 2007 (PST)
* Thank you for your extensive feedback. That helps us a lot to make Remora better. Regarding your "improvement" question: Keep in mind that the current public preview is still an "alpha" version. It is, almost by definition, incomplete, sometimes buggy, has rough edges and is far away from perfect -- or from its final state, for that matter. Therefore it is important that you tell us what you like, and what you don't, so you can influence how Remora will look and feel like when it's done. --[[User:Wenzel|wenzel]] 11:19, 17 January 2007 (PST)


== Yoko's comments ==
== Yoko's comments ==
Line 137: Line 118:
* The thunderbird's and nvu's extensions are not very easy to find.
* The thunderbird's and nvu's extensions are not very easy to find.
* I think that it's will good to multiply the section of extension. By exemple the developer tools's extensions can to be split in "PHP extension", "javascript extension", "webmaster extension", etc
* I think that it's will good to multiply the section of extension. By exemple the developer tools's extensions can to be split in "PHP extension", "javascript extension", "webmaster extension", etc
== Moe's comments (from [http://blog.mozilla.com/webdev/2007/01/18/amo-preview-updates-2/#comment-27 blog]) ==
All comments fixed (2006-02-26)


== Dolske's comments ==
== Dolske's comments ==
Line 184: Line 162:


Hmm, I guess that's enough comments for now! :-)
Hmm, I guess that's enough comments for now! :-)
== Pawell's l10n comments ==
* Links to MDC should point to corresponding localization (see Pascal's comment)
* The 'Home' link should point to {locale}.www.mozilla.com/{locale}/
* The construction of 'Browse all {addon-type}' can't be properly translated in languages with different genders and pronoun inflection
::::Example:
::::::Browse all Extensions -> Procházet všechn'''a''' rozšíření
::::::Browse all Themes    -> Procházet všechn'''y''' motivy vzhledu
Moreover, we need to use the lowercase for the {addon-type} string in the middle of the sentence.
*  The same holds for 'Popular {addon-type}'
::::Popular Extension -> Oblíben'''á''' rozšíření
::::Popular Themes    -> Oblíben'''é''' motivy vzhledu
Thanks for your comments, Pawell.  These are very relevant, and unfortunately, the tools
we're using don't provide a way to handle declinations programmatically.  For
translating the examples you've provided, we're going to have to rely on
localizers interpreting the context, and if necessary, leaving out the pronouns.
For example, instead of "Browse all Extensions" it would be translated as
"Browse Extensions".  We could add comments in the .po file to help recognize
the areas where this could come up.  Any thoughts on this? --clouserw


== Juan's comments ==
== Juan's comments ==
Confirmed users, Bureaucrats and Sysops emeriti
1,737

edits

Navigation menu