<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 7, 2014 at 10:17 PM, Jerry Vonau <span dir="ltr"><<a href="mailto:me@jvonau.ca" target="_blank">me@jvonau.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> On August 7, 2014 at 8:33 PM Martin Abente<br>
<div><div class="h5">> <<a href="mailto:martin.abente.lahaye@gmail.com">martin.abente.lahaye@gmail.com</a>> wrote:<br>
><br>
><br>
> On Thu, Aug 7, 2014 at 8:26 PM, Jerry Vonau <<a href="mailto:me@jvonau.ca">me@jvonau.ca</a>> wrote:<br>
><br>
> > Hi,<br>
> ><br>
> > > On August 5, 2014 at 7:34 PM Martin Abente<br>
> > > <<a href="mailto:martin.abente.lahaye@gmail.com">martin.abente.lahaye@gmail.com</a>> wrote:<br>
> > ><br>
> > ><br>
> > > Hello everyone,<br>
> > ><br>
> > > A few development cycles ago, dsd added a useful new feature:<br>
> > > automatic<br>
> > > activities updates.<br>
> ><br>
> > Um, sugar 0.100 was not that long ago, kind of liked the way the old<br>
> > sugar-update-control worked, all that was really missing was the<br>
> > auto-updating. For the record there never was a sugar-control-panel<br>
> > command<br>
> > line for the updater, that was the only piece missing. When I was<br>
> > involved<br>
> > with AU we went further, extending the updater to just select<br>
> > activities<br>
> > that were already installed, leaving the ones not installed unchecked<br>
> > by<br>
> > default. This presented a list of optional activities that MAYBE<br>
> > installed,<br>
> > ones that are updates would be pre-selected, one just needed start the<br>
> > install[1].<br>
> ><br>
> > > This has been of great help in deployments such as in<br>
> > > Australia. However, because the current implementation will always<br>
> > > update<br>
> > > or install activities (when working in automatic mode), some<br>
> > > deployments<br>
> > > might be unable to use this feature. A real case scenario is when<br>
> > > some of<br>
> > > the activities are too big for massive activities updates.<br>
> > ><br>
> ><br>
> > Think one option that is needed is to skip installing new activities<br>
> > that<br>
> > are not already installed.<br>
><br>
><br>
> Installing new activities could be needed too. Both cases are valid<br>
> though,<br>
> and is ultimately a deployment's decision. This feature can help with<br>
> both<br>
> for new install AND updates.<br>
><br>
<br>
</div></div>In this scheme how does one prevent the re-installation of a removed<br>
unwanted activity?<br></blockquote><div><br></div><div>As things are now (in sugar master) the updater will simply install (or upgrade) everything in the list. This feature tries to improve the current scheme from the deployment POV.</div>
<div><br></div><div>If someone can come up with a decent solution to handle this from the end-user POV, that would also be a nice improvement.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""> <br>
> The whole point is to give deployment the flexibility, so we (developers)<br>
> don't make the decision for them (deployments) for what should or should<br>
> not update.<br>
><br>
<br>
</div>How do you do that when the microformat page is not under the control of<br>
the end-users with no way of changing the url in UI except altering the<br>
entries in dconf? <br>
<div class=""><br>
><br>
> > The use case is "the in the field teacher" does<br>
> > not want a certain activity present for what ever reason on the XOs in<br>
> > their classroom and has removed the activity.<br>
> ><br>
> > > Therefore, I propose to extend microformat updater with an extra<br>
> > > field to<br>
> > > mark activities as optional, so these optional activities won't be<br>
> > > installed or upgraded automatically. This flexibility will allow<br>
> > > deployments to use automatic updates and user will benefit from<br>
> > > automatic<br>
> > > updates.<br>
> > ><br>
> ><br>
> > Think this is not really needed, more careful planning by the<br>
> > deployment is<br>
> > really what is needed here.<br>
><br>
><br>
><br>
><br>
> > > I have created a feature page [1] with more details and a initial<br>
> > > implementation [2] of the feature itself (because is easier for me to<br>
> > > talk<br>
> > > with working code).<br>
> > ><br>
> ><br>
> > Would ALSO benefit with the same treatment? Think that is where this<br>
> > could<br>
> > be really be useful, stopping a potentially large download from<br>
> > starting.<br>
> ><br>
> ><br>
> You mean supporting this in ASLO?<br>
><br>
><br>
<br>
</div>Yes, so SoaS/Sugar Desktop doesn't start a large unexpected download, we<br>
are talking about bandwidth usage right?<br></blockquote><div><br></div><div>Bandwidth is just one example, there are other scenarios like a deployment that simply wants to provide extra activities through the updater, but without forcing clients to install it.</div>
<div><br></div><div>It is important to notice the difference between ASLO and microformat back-ends; deployments can control microformat back-ends, is just a text file after all. To support this in ASLO, we need to change ALSO too. So is not something we can just change in Sugar.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
<br>
> > > Let me know what you guys think!<br>
> > ><br>
> > > Regards,<br>
> > > tch.<br>
> > ><br>
> ><br>
> > At one point in the past suagr-update-control did have the ability to<br>
> > look<br>
> > for a schoolserver, adding the activities found there to the list of<br>
> > activities available from both sources. That went away with the change<br>
> > in<br>
> > sugar's post 0.100 updater.<br>
> ><br>
> > Jerry<br>
> ><br>
><br>
> Thanks for the feedback!<br>
<br>
</div>The above worked via a DNS name, I'd rather see an avahi service search<br>
used to gain the ip of the update server. The could open up the possibility<br>
of using a local lan machine as the source of the updates.<br></blockquote><div><br></div><div>I don't recall seeing that in sugar master at least, but if someone has the time to upstream, it would definitely be another useful feature. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Jerry<br>
</font></span></blockquote></div><br></div></div>