1. In November: <http://status.net/trac/attachment/ticket/2017/Screen%20shot%202009-11-25%20at%2008.55.24.png> I imagined the space between the attachment icon and the Send button being used for occasional suppression of cross-posts.
2. More recently: <http://status.net/wiki/index.php?title=Talk:Location_fuzzing&oldid=5036#Pre-post_location_preview> part of that same space is imagined for a link to a map (geolocation). (I would suppress cross-posts to Twitter more often than I would suppress my location. YMMV.) 3. In a few months, or a year or so from now: there may be clamour for something additional in/around the area of the Send button. 4. At any time: a developer of a plug in (non-core) may wish for something to appear in/around the same area. Layout I'm conscious of — and agree with — the desire to not overcomplicate the UI. So: * how to change the UI neatly and effectively now, without spoiling its future potential? Speed-reading the recent conversation irc://irc.freenode.net/#statusnet irc://irc.freenode.net/#statusnet re: three options always | sometimes (user decides) | never but thinking longer-term (defocusing from geolocation/maps) and thinking AJAX (echoing the FAQ) I imagine: a) a click on the Send button could be followed by b) options for the send (include, exclude or fuzz the location) (cross-post to Twitter) (cross-post to Jaiku) (etc.) as an overlay, with the background dimmed c) if options are suitable, key return or enter to OK the send (or change options within the overlay; or key escape to return to the draft). That's the idea, in a nutshell. But it's rough — at least: you'd want a better word than 'OK' for a button in step (c). -- View this message in context: http://n3.nabble.com/UI-short-and-long-term-layouts-to-accommodate-core-and-plugged-in-features-tp102487p102487.html Sent from the Developers and admins of StatusNet mailing list archive at Nabble.com. _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
