<div dir="ltr"><div><div><div>Hi Gonzalo,<br><br></div>Both sugar-network and discourse use fixed toolbar. They are also very trendy now with material design and stuff :)<br><br>Theoretically we could change them, but it is much easier for us to do the merged toolbar. It is like 1 line of CSS change vs whole toolbar change.<br><br></div>Thanks,<br></div>Sam<br></div><br><div class="gmail_quote">On Wed, Apr 22, 2015 at 8:40 AM Gonzalo Odiard <<a href="mailto:godiard@sugarlabs.org">godiard@sugarlabs.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Sam,<div>You don't loose all the space, because you don't need a fixed toolbar in the server.</div><div>Is content, and the content will scroll. </div></div><div dir="ltr"><div><br></div><div>Gonzalo</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 21, 2015 at 7:27 PM, Sam P. <span dir="ltr"><<a href="mailto:sam.parkinson3@gmail.com" target="_blank">sam.parkinson3@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Gonzalo,<br><div><br><div class="gmail_quote"><span>On Tue, Apr 21, 2015 at 9:29 PM Gonzalo Odiard <<a href="mailto:godiard@sugarlabs.org" target="_blank">godiard@sugarlabs.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Apr 20, 2015 at 7:28 PM, Sam P. <span dir="ltr"><<a href="mailto:sam.parkinson3@gmail.com" target="_blank">sam.parkinson3@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Gonzalo,<br><div><br><div class="gmail_quote"><span>On Tue, Apr 21, 2015 at 3:37 AM Gonzalo Odiard <<a href="mailto:godiard@sugarlabs.org" target="_blank">godiard@sugarlabs.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">But if the server url can be configured (as in the proposal) <div>In theory you could Sugar Network too at the server side, right?</div><div>We only need define a standard way to provide context, like a parameter for the bundle_id</div></div></blockquote><div><br></div></span><div>Yes, that is possible. The api is very simple, the webview URL is set to:<br><br></div><div> SERVER/goto/BUNDLE<br></div><div><br></div></div></div></div></blockquote><div><br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Should be good check and agree with Sugar Network developers.</div><div>Could be a good idea add the nick name and the user colors as parameters? <br></div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="gmail_quote"><div></div><div>So, you could make sugar network respond to this, add a redirect or create a separate redirector server (as I do with <a href="http://socialhelp.sugarlabs.org" target="_blank">socialhelp.sugarlabs.org</a>).<br><br></div><div>It also has the merged native/web toolbar. The webview adds the class "sugar" to your document body so you can then compensate for the 55x55 close button on the top right.<br><br></div></div></div></div></blockquote><div><br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>I would prefer use just the standard Sugar toolbar.</div><div>If the page design change, or you use another server (like Suugar Network) or if you</div><div>have a monitor with different pixel size, the merged toolbar will look wrong.</div></div></div></div></blockquote><div><br></div></span><div>I have to disagree with you here.<br><br></div><div>For pixel size, websites just use em for the toolbar instead of px. Sites like sugar-network seem to already be doing this. You must use em in order to not look like tiny font on the xo anyway.<br><br></div><div>For other services, it is super duper easy to integrate. For example, this is all the CSS needed for discourse:<br><br> .sugar header.d-header {<br> width: -webkit-calc(100% - 2.813em);<br> }<br><br></div><div>Or for sugar-network:<br><br></div><div> .sugar #toolbar {<br> width: -webkit-calc(100% - 2.813em);<br> }<br></div><div><br></div><div>And even if the app does not have a toolbar, it is just a little button in the top right and it looks fine.<br></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>You lost 55 px, but you remove complexity and gain flexibility.</div></div></div></div></blockquote><div><br></div></span><div>55px is very important. On some platforms, it is actually even 75 px.<br><br></div><div>You loose 55px top padding, 55px bottom padding, 55px sugar toolbar and then ~55px for the web toolbar. That brings the total to 220px or 300px on a device with XO pixel density. What that equates to is very small. I had a go on my XO [1], and there was only 7cm height left for the content (almost same for discourse and sugar-network)! <br></div><div> <br></div><div>I understand that the XO is not our only platform. But on a small laptop, adding more toolbars is just counterproductive.<br></div><span><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>We can use the same viewhelp.py, just adding a toggle bottom to switch to </div><div>the social help (at the left, the only buttons aligned at the right are the Stop buttons)</div></div></div></div></blockquote><div><br><br></div></span><div>The idea of a toggle in the bottom left sounds good.<br><br></div><div>Thanks,<br></div><div>Sam<br><br></div><div>[1] <a href="http://imgur.com/FJFAcpl" target="_blank">http://imgur.com/FJFAcpl</a><br></div><div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="gmail_quote"><div></div><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Regarding the proposal, I would like to see this more integrated with the Help view.</div><div>Then the changes would be:</div><div>* Don't show two entries in the menu, one for the local help and another for the social help.</div><div>First, because in the cases where we have a help for the activity, is a good idea show</div><div>that first, and add a button to go o the server if configured.</div><div>* Right now, we show the Help menu only for activities with local Help available.</div><div>We should show the menu always, and if not local help is available go to social page.</div></div></blockquote><div><br></div></span><div>Do you have a UI design in mind?<br><br></div><div>Here is a quick mockup to start the conversation if you want: <a href="http://people.sugarlabs.org/sam/mockup.png" target="_blank">http://people.sugarlabs.org/sam/mockup.png</a><br></div><span><div> <br></div></span></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>My main concern with this feature is how to solve the change to webkit2 without break </div><div>all the webservices. I think we should include the main (and working) webservices in the sugar code,</div><div>port them to webkit2, and then land this feature.</div></div></blockquote><div><br></div></span><div>That sounds like a good idea.<br><br></div><div>If worst comes to worst, we could use webkit1. webkit2 has the new shiny stuff and webkit1 is old, we will have to move someday and why not before there are way too many web services!<br></div><div></div></div></div></blockquote><div><br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Is good know we have that alternative if we can't land all before May 18.</div><div>Maybe you can use webkit1 to land the feature and nake the change later.</div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Gonzalo</div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div> <br></div><div>Thanks,<br></div><div>Sam<br></div><div><div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div> </div><div> </div><div>Gonzalo</div><div> </div></div><div class="gmail_extra"></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 20, 2015 at 2:17 PM, Sebastian Silva <span dir="ltr"><<a href="mailto:sebastian@fuentelibre.org" target="_blank">sebastian@fuentelibre.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
For some reason this email found it's way into gmail's spam folder.<br>
<br>
However the topic is very important.<br>
<br>
I disagree that this implementation needs to be adopted.<br>
In particular, most deployments still don't have a reliable
connection to the Internet and we don't want to introduce a
dependency on it. Social help might (and should) come from peers
first.<br>
<br>
However, work has been ongoing from different deployments in this
(social) direction so it's generally accepted that Sugar needs it.
Our own work in Perú has been aligned with Alsroot's work on the
Sugar Network ( we developed the first UI, here's a short video
explaining it:
<a href="http://somosazucar.org/2012/06/04/un-avance-de-la-red-azucar-0-3-sneak-peek-of-sugar-network-0-3/" target="_blank">http://somosazucar.org/2012/06/04/un-avance-de-la-red-azucar-0-3-sneak-peek-of-sugar-network-0-3/</a>
).<br>
<br>
This work is ongoing. It involves a very light local server capable
of synchronizing user resources asynchronously (including comments,
bundles, etc) <i>in both ways</i>.<br>
<br>
The effort is very much appreciated. I think we need to morph the
proposal into something that is generic or pluggable, and try to
work with Alsroot on this.<br>
<br>
Regards,<br>
Sebastian<br>
<br>
<br>
<div>On 19/04/15 20:59, Sam P. wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Hi All,<br>
<br>
</div>
One feature I'm proposing for the 0.106 cycle is Social
Help. Social Help was previously proposed by Prasoon
Shukla as a GSOC project, however my proposal is slightly
different.<br>
<br>
</div>
Patch Link: <a href="https://github.com/sugarlabs/sugar/pull/483/commits" target="_blank">https://github.com/sugarlabs/sugar/pull/483/commits</a><br>
</div>
Feature Page: <a href="http://wiki.sugarlabs.org/go/Features/Social_Help" target="_blank">http://wiki.sugarlabs.org/go/Features/Social_Help</a><br>
</div>
<div>YouTube Video Summary: <a href="https://youtu.be/_WzwVZ60Tbw" target="_blank">https://youtu.be/_WzwVZ60Tbw</a><br>
<br>
</div>
<div>I would like to invite discussion on the feature so we can
land this for 0.106.<br>
<br>
</div>
<div>Thanks,<br>
</div>
<div>Sam<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Sugar-devel mailing list
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><span><font color="#888888">
</font></span></pre><span><font color="#888888">
</font></span></blockquote><span><font color="#888888">
<br>
<pre cols="72">--
I+D SomosAzucar.Org
"icarito" #somosazucar en Freenode IRC
"Nadie libera a nadie, nadie se libera solo. Los seres humanos se liberan en comunión" - P. Freire</pre>
</font></span></div>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br></div><div class="gmail_extra"><div><div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Software for children learning <br></div></div></div>
</div>
</blockquote></div></div></div></div>
</blockquote></div></div></div><div dir="ltr"><div class="gmail_extra"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Software for children learning <br></div></div></div>
</div></div></blockquote></div></div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Software for children learning <br></div></div></div>
</div>
</blockquote></div>