[01:13] <BHSPitLappy> kwwii, so I went and retrieved my tablet
[10:58] <thorwil> happy new year!
[10:58] <thorwil> so Tom Wright took my jackalope sketch and cleaned up the background. this is way cool :)
[11:13] <darkmatter> link?
[11:14] <thorwil> https://wiki.ubuntu.com/Artwork/Incoming/Jaunty/AlphaBackgrounds
[11:15] <darkmatter> hmmm... nice.. though I still think a jackalope is.. umm.. weird.. ;)
[11:17] <thorwil> darkmatter: i wouldn't propose to use it for the final release. these are solely for pre-releases
[11:18] <darkmatter> thorwil: of course, but I mean a jackalope in general is weird.. it conveys a 'we don't take our product seriously' image, but the sketch is quite lovely
[11:21] <thorwil> it could also be taken as a "we are no stiff fuddy-duddies" ;)
[11:21] <thorwil> well, thanks :)
[11:23] <darkmatter> I finally have my aesthetic guidelines finished.. now to grind out  pixmaps and svg's... and actually get my mockups from paper to digital.. yay!
[11:25] <thorwil> darkmatter: do you have those guidelines up somewhere?
[11:29] <darkmatter> ummm... nope.. I'll need to type them out and upload.
[11:30] <darkmatter> They're somewhat picky though, it's not so much a matter of themes as it is a matter of the overall interface so it's really not just the aesthetics, but more so form AND function
[11:57] <darkmatter> also been working on some ideas regarding the workspace. one of my favorites needs a lot of ironing out as far as how to implement it, but is quite sound in concept
[12:02] <darkmatter> it's a global workflow tracker, that can save state across sessions. at the application level, it functions basically as breadcrumbs (I was thinking of displaying it in a manner similar to the way global menus are done, but again.. still working on the details)
[12:03] <darkmatter> but keeps track of position within the workflow timeline instead of location
[12:04] <thorwil> i guess you will need more detail and examples to get the idea across ;)
[12:06] <darkmatter> yup.. I have examples.. just need to do the 'flowchart for dummies' thing along with the mockups
[12:08] <darkmatter> but.. for a really simple and not very impressive example of usage, consider.. umm.. say editing a file in gedit (like a .c or whatever)
[12:10] <darkmatter> now, currently, you basicaly make your revisions, and go through the whole 'click undo/redo til your fingers bleed' methodology, and when you close the app, that's it, you have the current version plus a backup
[12:14] <darkmatter> now, using the 'tracker' idea, each revision would add a crumb to the timeline, so you could basically jump to the desired position, and upon closing a document, the timeline would be saved (be it in a sql database or whatever), so the next time you open the file, it would open the timeline with it. that's the most basic functionality it could do, but hopefully that paints a better picture
[12:16] <darkmatter> of course, then you can get into things like forking timelines, multiple document/application tracking, etc... but that's where the flowcharts come in :P
[12:16]  * thorwil wants global undo/redo with scope and tagging, no explicit save anymore since long
[12:17] <thorwil> but i got stuck each time i tried to work out the details
[12:19] <darkmatter> thorwil: yeah.. that's basically part of why I started thinking about this.. I wan't things like remembering grouped apps (like say you're programming something, have devhelp, glad, anjuta, gedit, and whatever else open, sitting on whatever workspaces you have them assigned to, etc)
[12:20] <thorwil> darkmatter: i'd treat the screen like a document, so it can be versioned like everything else
[12:20] <darkmatter> I want things to resume where I left off when reopening a doc/image/whatever, and I wan't my previous revisions available in an inteligent manner, and if multiple apps are associated with eachother within a workflow, I want the association recognized/resumed when I continue the work
[12:21] <thorwil> one fun thing with an edit history that allows branching is that you can treat the result as a tree, or still a linear list, if navigation in the history is recorded in itself
[12:21] <thorwil> food, bbl
[12:21] <darkmatter> explicit saves should only be used when something is finished.. and it's even iffy to use one then :P
[12:51] <savvas> happy new year non-chinese residents of the earth :P
[12:51] <savvas> and non-old-calendar users hehe
[12:53] <thorwil> happy new year for you, too savvas
[12:53] <thorwil> darkmatter: i'd rather have just tagging (as in associate this label with current state)
[12:55] <darkmatter> hmmm... yeah.. that too