<seiflotfy__> fmuellner, i am making my zeitgeist work an extension for you guys to play with
<seiflotfy__> what do you think
<seiflotfy__> is there a guide to extensions
<fmuellner> seiflotfy__: not really - there are some existing extensions in gnome-shell-extensions
<seiflotfy__> ok will take a look
<fmuellner> (though quite frankly I'm not really sure if that's a good use of time - right now we don't need code to "play with", but rather a definition of what the user experience should be for finding and reminding)
<seiflotfy__> fmuellner, i think that my code might insporie you on what to do or what not ot do
<seiflotfy__> i think prototyping is healthy
<seiflotfy__> one cant get the design right without having something to reflect on
<seiflotfy__> even before the designs are out
<fmuellner> seiflotfy__: that's what design iterations are for ;-)
<seiflotfy__> well fmuellner i just implemented the iteration based on mccann old mockups
<seiflotfy__> fmuellner, right now i am just waiting for designs to come out
<fmuellner> seiflotfy__: but still, a prototype should follow an initial design
<seiflotfy__> fmuellner, i followed the initial design form finding and remiinding and adapted it to the current shell deisgn
<seiflotfy__> i think it would help good feedback from people
<fmuellner> seiflotfy__: sure, but those mockups are more than a year old
<seiflotfy__> i know
<seiflotfy__> but i think an extension could help mccann a bit with his design decisions
<seiflotfy__> and i think making it an extension is going to make it easy for you guys to test
<fmuellner> seiflotfy__: that's where I'm not sure
<seiflotfy__> explain
<fmuellner> seiflotfy__: your extension will be based on zeitgeist's capabilities rather than user experience
<seiflotfy__> based on that one can find what user experience is missing
<fmuellner> e.g. you have a bias to overlook what zeitgeist can't do, and another to add stuff that it can do, but may be better off in a specialized app
<seiflotfy__> and evaluate hwat technology still needs to be d