These are chat archives for slidewinder/slidewinder

20th
Jan 2016
Richard Smith-Unna
@blahah
Jan 20 2016 12:09
sorry @all for being slow - yesterday was a write-off as I had to spend the day in london getting Max's passport
Richard Smith-Unna
@blahah
Jan 20 2016 14:00
@Ward9250 thoughts on #40 ?
I figure we have some templates, and they can have associated helper functions to generate them
just like the framework ones, except they generate individual slides from provided content
I got a bit lost trying to refactor the librarian - collection stuff yesterday, so I've gone back to the design stage to make sure I know what to do in what order
at the moment I'm mapping out the user interface routes, which will be the same across CLI and GUI but with different wrapping
Ben J. Ward
@BenJWard
Jan 20 2016 14:48
I've added a few thoughts on #40
Richard Smith-Unna
@blahah
Jan 20 2016 14:48
thanks
Richard Smith-Unna
@blahah
Jan 20 2016 16:25
@Ward9250 (and @acabunoc @acabunoc @joeyklee et al) would appreciate feedback on this: https://github.com/slidewinder/direction/blob/master/routes/routes_overview.md
planning the user interaction routes through the app
Ben J. Ward
@BenJWard
Jan 20 2016 16:59
We're talking routes as in Angular?
Richard Smith-Unna
@blahah
Jan 20 2016 17:00
not any particular technology, it's just a generic term
Ben J. Ward
@BenJWard
Jan 20 2016 17:00
ok
Richard Smith-Unna
@blahah
Jan 20 2016 17:01
often implemented with some kind of router so it could literally be route(name, options, callback)
I kept finding things I hadn't thought about when implementing the librarian
so I wanted to map out all the behaviour it should have
Ben J. Ward
@BenJWard
Jan 20 2016 17:01
'Oook!'
Richard Smith-Unna
@blahah
Jan 20 2016 17:01
and doing it based on what the users can possibly experience seemed like a good way
lol
Ben J. Ward
@BenJWard
Jan 20 2016 17:02
They remind me of git subcommands
Richard Smith-Unna
@blahah
Jan 20 2016 17:05
indeed - could be implemented that way for the non-interactive cli
I like the idea of using a router here for the behaviour because it makes it really easy to reason about both a GUI and an interactive CLI at the same time
is there anything missing from the router do you think? big or small
Ben J. Ward
@BenJWard
Jan 20 2016 17:07
pushing and pulling to a remote? Just thinking of when people download and interact with internet like slidewinder.io
Richard Smith-Unna
@blahah
Jan 20 2016 17:09
hmm yeah
so in that situation each collection can potentially have a remote, like a git repo
Ben J. Ward
@BenJWard
Jan 20 2016 17:10
This will also guide the structure of the library, actions common to routes will need to be a library function and so on.
Richard Smith-Unna
@blahah
Jan 20 2016 17:10
yeah
@zee-moz hey! tried a new tack with the design, would love to know what you think: https://github.com/slidewinder/direction/blob/master/routes/routes_overview.md
I suspect there are established ways for designers to handle these things and I'm ignoring decades of established practise
Joey Lee
@joeyklee
Jan 20 2016 17:12
.. just drawing out a workflow real quick to wrap my brain around it
Richard Smith-Unna
@blahah
Jan 20 2016 17:13
aha I see there is a concept 'user journeys' that maps to 'user personas', so I guess I've done that here
Zannah Marsh
@zee-moz
Jan 20 2016 17:14
@Blahah you may have missed this-- i put it in the fellows chat... http://www.agilemodeling.com/artifacts/uiFlowDiagram.htm
Ben J. Ward
@BenJWard
Jan 20 2016 17:14
Somewhere like slidewinder.io might have a large database containing DAGs for many slides. Your database will only have a few for the slides you actually pulled. But say someone else pulled said slide and also made mods. Say they push to slidewinder.io. Say you subsequently pull, you'd want their modified slide in your database for use.
Richard Smith-Unna
@blahah
Jan 20 2016 17:14
@zee-moz thanks!
Zannah Marsh
@zee-moz
Jan 20 2016 17:15
but that could help. i think you're on the right path thinking about routes, but users may start off on one and jump to another, like switch midway... just know that you need to account for that behavior and design it so those pathways are possible
Richard Smith-Unna
@blahah
Jan 20 2016 17:16
ok thanks - I tried to do that here by, within each route specifying which other routes they can reach from there and how
perhaps a graphical version would help
@joeyklee is on it :)
Zannah Marsh
@zee-moz
Jan 20 2016 17:16
yeah flow chart may be easier to grok
Richard Smith-Unna
@blahah
Jan 20 2016 17:17
there's a nice package for converting text flows to graphical flows I've used before... what was it
found a cool thing about 'red routes' - roads in London that are very high priority for always working
and by analogy, there are routes in UX that should be prioritised for development
Joey Lee
@joeyklee
Jan 20 2016 17:29
alrighty - hopefully this is helpful.
IMG_0370.JPG
IMG_0372.JPG
IMG_0373.JPG
so the last two images are my little experiment workflow
Richard Smith-Unna
@blahah
Jan 20 2016 17:31
@joeyklee that is awesome
helps a LOT to see it this way + the layout stuff is really nice
Joey Lee
@joeyklee
Jan 20 2016 17:35
maybe things in my mind what would be:
  1. a way to select slides and add them to a collection
  2. and manage them from the collections list
i think these things are baked in already to your routes