<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 28/01/2014 08:26, Corinne Krych
wrote:<br>
</div>
<blockquote
cite="mid:9BBFBABA-AE49-45B4-B835-5B1F6F65BE5C@gmail.com"
type="cite">
<blockquote type="cite"><br>
<blockquote type="cite"><br>
<font color="#b18cfe">Actually if you setup the sass batch
link[1], you run your environment and then you go to link[2]
loclhost as it’s running on our instance, you will see
i’ve tried it out for Pipes. In order to do it i needed to
split the documentation for iOS/Android (I haven’t done
completely JS part). with this exercice what i understand
is:<br>
1. the first view should contain code snippet with shows the
unified aspect of client lib. those sippet are not complete
code, it should be simplified.<br>
2. this simplified view is not enough for a developer.
Selecting his platform tab, he will be redirected to android
for ex complete description on Pipes. Ideally this
description is based on a cookbook exemple.<br>
3. if the developer want to test it himself he’ll have the
option to download the complete sample code (github link to
cookbook repo) and just run it<br>
<br>
So the explantion goes through 3 layers from 1)high level
description (cross platform), 2) detailled explanation
linked to a platform to 3) sample code implementation
(obvious linked to a platform).<br>
<br>
My question is How to make the transition from 1) to 2) ?
See picture below<br>
<br>
</font></blockquote>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="https://www.dropbox.com/s/tz25vzu8doh6jkk/agorg2.png">https://www.dropbox.com/s/tz25vzu8doh6jkk/agorg2.png</a></div>
<div><br>
</div>
<br>
</blockquote>
<br>
Alright, that makes sense.<br>
I have some ideas about this. I'll update the mockups and send the
to you.<br>
<br>
Hylke<br>
<br>
</body>
</html>