<div dir="ltr"><div dir="ltr"> </div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 5, 2020 at 2:14 AM James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Mar 04, 2020 at 07:25:58AM -0500, Walter Bender wrote: > > On Tue, Mar 3, 2020 at 8:52 PM Walter Bender <[1]<a href="mailto:walter.bender@gmail.com" target="_blank">walter.bender@gmail.com</a>> > wrote: > > Sugar yes. The new version of Browse should work nicely. > Sugarizer, no. Lionel has said it is too large. > > On Tue, Mar 3, 2020 at 7:53 PM James Cameron <[2]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote: > > Are there any plans to add Music Blocks to Sugarizer or Sugar? > > At James: What is the recommended approach to embedding inside Browse these > days? It depends on what browser features the application needs. If those features are contained within WebKit2.WebView, then not much is needed. List the features; e.g. touch events, mouse clicks, keyboard events, back and forward button, reload, etc. HelpActivity and JupyterLabs both instantiate a WebKit2.WebView. WikipediaActivity does a sideways import of Browse. Sugar Web activities have a WebKit2.WebView instantiated for them by Sugar when exec is /usr/bin/sugar-web-activity. > In the past, I simply modified the HOME_PAGE_GCONF_KEY to use a copy > of musicblocks included in the bundle. The port from GConf to Gio.Settings brought with it a design inadequacy, that configuration keys needed to be defined in a schema before the program ran, and GNOME project envisaged this would be most commonly handled by running glib-compile-schemas at package install. Sugar activity bundles don't have that available to them. There was a way around it; define a schema at runtime, but that meant the URL is stored inside the activity root directory. Details are in _get_local_settings in browser.py. > Do you recommend removing some unrelated Browse functionality, such > as the search bar? It is best to offer only user interface elements that are meaningful to use of the application. > Do you think it is worth modifying Browse itself to make it easier > to do this sort of embedding? That depends on what user interface elements are needed, and that depends on what browser features are needed. The choice will be somewhere on this spectrum; * use a WebKit2.WebView with no significant user interface elements, * use a WebKit2.WebView with a few user interface elements, * use the WebActivity and disabled a few user interface elements, * use the WebActivity with a change to default page, * start the WebActivity. </blockquote><div> </div><div>Thanks. Very helpful. FWIW, I think I will look at how the Help activity is doing this as that is the closest to what I am envisioning. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> > > regards. > > -walter > > On Tue, Mar 03, 2020 at 07:33:46PM -0500, Walter Bender wrote: > > The release reflects the contributions made during Google Code-in > 2019-2020. It > > is being designated as a major release since there are numerous > changes to the > > user experience (e.g., Widget UX) and many underlying structural > changes (e.g., > > the new Block API and storage mechanism) that impact developers. An > overhaul of > > the graphics update mechanism has lead to a major reduction in CPU > usage. As > > far as I know, there is only one "incompatibility" with previous > versions; it > > is in regard to synchronization: there are some projects that worked > previously > > that may now require the use of either the Sync block or the No-clock > block. > > (Details are outlined in the release notes.) > > > > A tip of the hat to some of the GCI participants who worked so hard > to make > > this release possible: Bottersnike, AndreaGon, Pidddgy and > Nepaltechguy2. They > > not only contributed code, but also insights into the design and > > implementation. Also, thanks to the community members who provided > them with > > code reviews and feedback (notably @eohomegrownapps, @fakela, and > @pikurasa). > > It is also important to acknowledge some of our users, Teddy Dildine > and Henry > > Rico, who have been inspiring much of the recent developments and bug > fixes. > > Look for some of their work on the Planet. Karin Kinoshita at Gakken > has also > > done testing and translation work. > > > > [1] [1][3]<a href="https://github.com/sugarlabs/musicblocks/releases/tag/v3.0" rel="noreferrer" target="_blank">https://github.com/sugarlabs/musicblocks/releases/tag/v3.0</a> > > > > -walter > > > > -- > > Walter Bender > > Sugar Labs > > [2][4]<a href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a> > > [3] > > > > References: > > > > [1] [5]<a href="https://github.com/sugarlabs/musicblocks/releases/tag/v3.0" rel="noreferrer" target="_blank">https://github.com/sugarlabs/musicblocks/releases/tag/v3.0</a> > > [2] [6]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > > [3] [7]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > > > _______________________________________________ > > Sugar-devel mailing list > > [8]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > > [9]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > -- > James Cameron > [10]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > _______________________________________________ > Sugar-devel mailing list > [11]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > [12]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > -- > Walter Bender > Sugar Labs > [13]<a href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a> > [14] > > -- > Walter Bender > Sugar Labs > [15]<a href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a> > [16] > > References: > > [1] mailto:<a href="mailto:walter.bender@gmail.com" target="_blank">walter.bender@gmail.com</a> > [2] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a> > [3] <a href="https://github.com/sugarlabs/musicblocks/releases/tag/v3.0" rel="noreferrer" target="_blank">https://github.com/sugarlabs/musicblocks/releases/tag/v3.0</a> > [4] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [5] <a href="https://github.com/sugarlabs/musicblocks/releases/tag/v3.0" rel="noreferrer" target="_blank">https://github.com/sugarlabs/musicblocks/releases/tag/v3.0</a> > [6] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [7] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [8] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > [9] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [10] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> > [11] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a> > [12] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > [13] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [14] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [15] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> > [16] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a> -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a> </blockquote></div> <div> </div>-- <div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Walter Bender Sugar Labs</div><div><a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a> <a href="http://www.sugarlabs.org" target="_blank"></a> </div></div></div></div>