<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/3 Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
What do you mean with "emergence of sugar-toolkit-gtk3"?</blockquote><div><br></div><div><div>I do not know the story of how this package came, when.., the main purpose.., not that long ago I'm on this list</div>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5"><br><br>On Tuesday, 3 December 2013, Rogelio Mita wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>I need more context about emergence of sugar-toolkit-gtk3 but...</div><div><br></div><div>I am agree with that points:</div><div>Gonzalo says:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Another alternative is find what is crashing in webkit2 and solve it, but is out of my knowledge.</blockquote><div>Always is an alternative write code for cover backward compatibility if there are all pertinent tests to cover this features with all the effort that this entails, so we need to think very carefull on that choice like Daniel said:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I'm not completely convinced we should support webkit1 yet. I'm worried it will be pretty painful to maintain.</blockquote>
<div><br></div><div>Maybe we can ask us: <b>To whom these problems affect?</b>.</div><div>If is possible answer this questions, this can help us to take a choise.</div><div><br></div><div>Anyway, seems risky write two different backends for a short terms usage.</div>
<div>Is it possible?</div><div>- sure, but seems a lot of work, I think that is unneccessary for a short term, IMHO.</div><div><br></div><div>Other risk is expand a module that is recently born such as sugar-web that I think the goal is no clear in the horizont yet, I think that keep it small this is a good desition right now until that the usage be more clear, I mean, android, simple browser and XO is an wide spectrum to cover, if we not have clarity that this serves for its purpose, add backward support right now, is overhead in my oppinion.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/2 Daniel Narvaez <span dir="ltr"><<a>dwnarvaez@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I'd really like to get feedback from more people about this! <div><br></div><div>Ccing sugar-web contributors.<div><br><br>On Wednesday, 27 November 2013, Gonzalo Odiard wrote:<br></div><div><div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">When we started the work in web activities, we decided work with webkit2,<div>because is possible solve a few problems in the client side,</div><div>without need a local webserver.</div><div><br></div><div>
But right now, in the XOs, we have F18 working, and Webkit2 crashes,</div>
<div>then I didn't find other solution than modify webactivity to work with webkit1.</div><div>That code was included in the rpms I prepared and the testing images.</div><div><br></div><div>I would like propose include this change in master,</div>
<div>used only when a environment variable is set, to make easier the testing,</div><div>and be sure the changes we do works in both webkit1 and webkit2.</div><div><br></div><div>A first proposal is available here <a href="https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/54" target="_blank">https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/54</a></div>
<div><br></div><div>Thoughts? </div><div><br></div><div>Gonzalo</div></div>
</blockquote></div></div></div><span><font color="#888888"><br><br>-- <br>Daniel Narvaez<br clear="all"><div><br></div>-- <br>Roger<div><br><div><a href="http://activitycentral.com/" target="_blank">Activity Central</a></div>
</div>
</font></span></blockquote></div></div>
</blockquote><br><br></div></div><span class=""><font color="#888888">-- <br>Daniel Narvaez<br><br>
</font></span><br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">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>Roger<div><br><div><a href="http://activitycentral.com/" target="_blank">Activity Central</a></div></div>
</div></div>