The relevant ticket for this is: http://labs.toolness.com/trac/ticket/409
I'm just heading out for the day, but later tonight I'll see about committing the code I have so far. As I said in the meeting, most of my work on it has been to develop a framework to make gathering data easy (and for automated reporting to a server), rather than actually getting the data or processing it. So at the moment, there's two different lists of what data can/should be gathered - one on the wiki, one on Trac. - Blair On 13/11/2008 9:35 AM, indolering wrote: > Combined with the streaming UI, statistical data gathering would allow > us to quickly and cheaply test changes on large samples, Understand > feature usage, errors, and stickiness of users. This data would > significantly change the course of innumerable future development > decisions doing it now would save a massive amount of effort. > > For example, everyone seems to think the contextual menu is the best > way to get "normal" people using Ub, but only one of the test subjects > knew of it's existence, and even then it was a last resort for him to > use it. I would bet money that it's usage rates would be near zero. > Or am I wrong, and should we, as Jono proposes, "[Take] the Ubiquity > context menu from tech-demo quality to production quality. For the > majority users who didn't grow up on command lines, the context menu > is likely to be the more widely used interface, but development on it > has lagged far behind..." then going on to suggest a list of features > to be added on. > > https://wiki.mozilla.org/Labs/Ubiquit/Usability/Statistical#Proposals_for_statistical_data_gathering > > Humbly, > -Zach : ) > > On Nov 3, 6:49 am, Aza<[EMAIL PROTECTED]> wrote: >> It's time to buckle down and figure out the quarter four goals (i.e., by the >> end of 2008) for Ubiquity. That's two months. Figuring these out is a >> community process, so what I'll do here is lay out a general outline as a >> framework for talking about specifics. >> >> *Major Goals for Ubiquity 0.2* >> >> * Streamable UI >> - At least one new and experimental UI >> * Streamable Skins >> - Including a revised default Ubiquity skin, revisiting some of the >> original design decisions >> * UI Improvements >> - A better context menu >> - Experimental integration with the Awesome Bar >> * Better command scaling and removal of hyphens in command names >> - Using "container" verbs (http://labs.toolness.com/trac/ticket/134) >> * A revised and updated API for Ubiquity commands >> - A more finalized version of the "all-in-one" command plus templates, >> - A unified method of adding and interacting with nouns, commands, and data >> detectors. >> >> *Ancillary Goals:* >> >> * A version of the Herd with a well-documented public API >> * A home site for Ubiquity with a Ubiquity "planet" >> * Both Herd, and Ubiquity homepage to be hosted at ubiquity.mozilla.com >> >> Over the course of the next couple of days, let's try to come to a rough >> consensus over what needs to be added to the goals, what needs to be >> removed, and what's doable. I'll try to sum our decisions up in a blog post >> in around a weeks time. We'll then turn the large goals into smaller >> milestones and tickets >> >> -- aza | ɐzɐ -- > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
