- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Smalltalk Internet Browser

by Denis Kudriashov

2017-05-04 17:55 GMT+02:00 askoh <askoh(a)askoh.com>: > 2) Embed Chromium or ChromeHeadless or WebKit inside the Smalltalk IDE. > Browser access is through the exposed APIs. > There is also Firefox. And we already use part of it in Bloc project: Moz2D library

May 4, 2017

Re: [Pharo-dev] Pharo 6 crash when requesting memory from the JVM library

by Ben Coman

On Wed, May 3, 2017 at 10:02 PM, Raffaello Giulietti < raffaello.giulietti(a)lifeware.ch> wrote: > Hi Ben, > > > On 2017-05-03 14:56, Ben Coman wrote: > >> Thanks for the follow up. Glad to hear its nothing intrinsic to Pharo. >> >> btw, Is there somewhere in the documentation or class/method comments >> that you believe this N-base situation should be spelled out better? >> >> > > Well, I wouldn't call the parameter of ExternalAddress>>byteAt:... methods > a "byteOffset", as offset invariably indicates a *difference* between > indices or addresses. Thus, I would for example expect an offset of 0 to > refer to the first byte, whether its index is 0 or 1. > > This is in contrast with the Smalltalk convention that <something>At: > selectors with numerical arguments usually mean a 1-based *index*. > > > > BTW, just for information, what is your role in the development of Pharo? > For me Pharo is a dedicated hobby, doing a few hours most week nights and longer stints on weekends. Some people love doing crosswords. I love programming and enjoy Pharo the most. Not having any commercial time pressures has allowed me the luxury to dive deep into areas of interest, which is usually the lower level stuff like DelayScheduler, semaphores/mutexes and Processes in Image & VM - but so far I've not done anything with the JIT. My day job is this... https://www.linkedin.com/in/bencoman/?ppe=1 I dream of one day using Pharo as a soft-realtime industrial automation control system on a Beagleboard, but so far I've taken limited concrete action towards that. I'm located south of the equator in Western Australia, so quite remote from most others in the community (although I did have the pleasure of meeting Thierry & Onil once when they were visiting family here). cheers -ben P.S. I'll take this opportunity to mention I'm between jobs at the moment. So I'd be happy to hear from anyone needing some odd jobs done, while I consider my options.

May 4, 2017

Re: [Pharo-dev] Smalltalk Internet Browser

by askoh

Thanks everyone for digging out the various possibilities. It is heartening to know the community is healthy and engaging. Let me summarize the possibilities: 1) Recompile Smalltalk VM from C to WebAssembly to run inside a browser at near native speed. This means a complete Smalltalk IDE inside a browser with full access to the browser innards. 2) Embed Chromium or ChromeHeadless or WebKit inside the Smalltalk IDE. Browser access is through the exposed APIs. 3) Enhance Scamper, a basic browser written in Smalltalk, to include more and more of the capabilities of Chrome say. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Smalltalk-Internet-Browser-tp4944879p4945606.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 4, 2017

Re: [Pharo-dev] Smalltalk Internet Browser

by vfclists .

On 29 April 2017 at 03:11, askoh <askoh(a)askoh.com> wrote: > Being connected to the internet is going to be a necessity for any piece of > software in the immediate future. So every Smalltalk development > environment > or application should have that capability as default. To push that > envelop, > every image should have a Smalltalk native Internet Browser. By developing > that Internet Browser, we are demonstrating the power of Smalltalk. There > is > no reason why Smalltalk cannot be as intimate to the World Wide Web as > Javascript. We can have the IDE in Smalltalk, Internet Browser in Smalltalk > and a WWW language in Smalltalk. As is uniquely Smalltalk, every bit of > code > is visible, modifiable and debuggable. This supped up environment will grow > and grow to be a full OS. > > How can we gather the relevant Smalltalk code and necessary plugins to make > an Internet Browser? I remember Croquet had internet browser and video > player. What is missing? > > All the best, > Aik-Siong Koh > > > > -- > View this message in context: http://forum.world.st/Smalltal > k-Internet-Browser-tp4944879.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > I think the OP is speaking along these lines - other apparently smaller teams seem to have accomplished something like that: https://github.com/luakit/luakit https://github.com/felipedaragon/sandcat -- Frank Church ======================= http://devblog.brahmancreations.com

May 4, 2017

[pharo-project/pharo-core] 364b4a: 60481

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 364b4ad385d9994f0d59f92369bb854f54eefa2a https://github.com/pharo-project/pharo-core/commit/364b4ad385d9994f0d59f923… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-05-04 (Thu, 04 May 2017) Changed paths: M Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/instance/drawing/drawOn_.st M Morphic-Base.package/ToggleMenuItemShortcutWithText.class/instance/drawing/drawOn_.st A Morphic-Widgets-Tabs.package/TabBarMorph.class/instance/initialization/themeChanged.st A Morphic-Widgets-Tabs.package/TabLabelItem.class/instance/accessing/themeChanged.st A Morphic-Widgets-Tabs.package/TabManagerMorph.class/instance/initialization/themeChanged.st A Morphic-Widgets-Tabs.package/TabMorph.class/instance/protocol/themeChanged.st M Nautilus.package/AbstractNautilusUI.class/class/menu/packagesMenuGroupsItems_.st A Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/defaults/menuItemDisabledTextColorFor_.st M RPackage-Core.package/RPackageOrganizer.class/instance/system integration/hasPackageMatchingExtensionName_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60480.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60481.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60480.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60481.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60481 19984 TabExample does not switch theme correctly https://pharo.fogbugz.com/f/cases/19984 20014 Dark theme is bad for changes browser https://pharo.fogbugz.com/f/cases/20014 19975 Can add a _tag_ to a Nautilus work group but a package is expected https://pharo.fogbugz.com/f/cases/19975 20016 Extensions with the same prefix may not be categorized correctly https://pharo.fogbugz.com/f/cases/20016 http://files.pharo.org/image/60/60481.zip

May 4, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60481 Home: https://github.com/pharo-project/pharo-core

May 4, 2017

Re: [Pharo-dev] PI'm promoting new stable VMs

by Thierry Goubier

2017-05-04 7:58 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 3 May 2017, at 22:20, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > I'm now chasing an old 64 bits vm from files.pharo.org. All the new ones > for the past 2 months segfault. Would anybody have kept a ~ 2 month old 64 > bits vm (threaded or not) for linux somewhere? > > > here you can download older 64bits VM: http://files.pharo.org/vm/ > pharo-spur64/linux/ (oldest is from 10/01) > nowâ¦ I do not segfault directly. I just downloaded: > > wget -O- get.pharo.org/64/60+vmT | bash > > image starts fine for me (xubuntu 64bits 16.04) > Reusing your script, I have. - First start up is ok. got threaded priorities warning even if I have the /etc/security/limits.d/pharo.conf set. - third image building command segfault while loading packages. Very reliable. Fails every time, as far as I can see, at the same point. I bisected over all versions of the itimer and the threaded vms, and I got the following: The last vm that doesn't segfault is 201704030814-0b76880 for the itimer vm, and 201704111618-0e1fc3a for the threaded one. Regards, Thierry > â¦ and then run all tests, that produces a fairly amount of errors/failures > and *eventually* crashes the VM (crash attached). > > vm version: CoInterpreter VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: > 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 > VM: 201705022326 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Date: Tue May 2 16:26:41 2017 -0700 $ Plugins: 201705022326 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > > > > Regards, > > Thierry > > Le 03/05/2017 Ã 21:58, Nicolas Cellier a Ã©crit : > > > > 2017-05-03 17:45 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com > <mailto:eliot.miranda@gmail.com <eliot.miranda(a)gmail.com>>>: > > > > > On May 3, 2017, at 4:22 AM, Esteban Lorenzano <estebanlm(a)gmail.com < > mailto:estebanlm@gmail.com <estebanlm(a)gmail.com>>> wrote: > > > > > >> On 3 May 2017, at 12:38, Alistair Grant <akgrant0710(a)gmail.com < > mailto:akgrant0710@gmail.com <akgrant0710(a)gmail.com>>> wrote: > >> > >> Hi Esteban, > >> > >> $ curl http://get.pharo.org/64/60+vmLatest > <http://get.pharo.org/64/60+vmLatest> | bash > >> $ ./pharo --version > >> > >> Shows the build version as: > >> > >> VM: 201705022326 https://github.com/OpenSmalltalk/opensmalltalk- > vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> > >> Date: Tue May 2 16:26:41 2017 -0700 $ > >> > >> Does that mean we should be building from the opensmalltalk > repository > >> instead of the pharo-vm repository (even temporarily)? > > > > officials VM for Pharo now are built using opensmalltalk-vm, yes. > > we still keep our process for CI/testing purposes, though. > > Woot! Thank you Esteban!! > > > +1 > That will help us to help you, it's a win win. > > > > > > Esteban > > > >> > >> Thanks, > >> Alistair > >> > >> > >>> On 3 May 2017 at 09:43, Esteban Lorenzano <estebanlm(a)gmail.com > <mailto:estebanlm@gmail.com <estebanlm(a)gmail.com>>> wrote: > >>> in 15min, I will promote latest VM to stable VM. > >>> The new stable VM has a lot of bugfixes, notably: > >>> > >>> - compactor works > >>> - Cairo and Surface plugin now can coexist (and it does not crashes) > >>> - lot of other small things > >>> > >>> cheers, > >>> Esteban > >>> > >> > > > > > > > > > > >

May 4, 2017

Re: [Pharo-dev] PI'm promoting new stable VMs

by Esteban Lorenzano

> On 3 May 2017, at 22:20, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > I'm now chasing an old 64 bits vm from files.pharo.org. All the new ones for the past 2 months segfault. Would anybody have kept a ~ 2 month old 64 bits vm (threaded or not) for linux somewhere? here you can download older 64bits VM: http://files.pharo.org/vm/pharo-spur64/linux/ <http://files.pharo.org/vm/pharo-spur64/linux/> (oldest is from 10/01) nowâ¦ I do not segfault directly. I just downloaded: wget -O- get.pharo.org/64/60+vmT <http://get.pharo.org/64/60+vmT> | bash image starts fine for me (xubuntu 64bits 16.04) â¦ and then run all tests, that produces a fairly amount of errors/failures and *eventually* crashes the VM (crash attached). vm version: CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 VM: 201705022326 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 2 16:26:41 2017 -0700 $ Plugins: 201705022326 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > Regards, > > Thierry > > Le 03/05/2017 Ã 21:58, Nicolas Cellier a Ã©crit : >> >> >> 2017-05-03 17:45 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com >> <mailto:eliot.miranda@gmail.com>>: >> >> >> >> > On May 3, 2017, at 4:22 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> > >> > >> >> On 3 May 2017, at 12:38, Alistair Grant <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>> wrote: >> >> >> >> Hi Esteban, >> >> >> >> $ curl http://get.pharo.org/64/60+vmLatest >> <http://get.pharo.org/64/60+vmLatest> | bash >> >> $ ./pharo --version >> >> >> >> Shows the build version as: >> >> >> >> VM: 201705022326 https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >> >> Date: Tue May 2 16:26:41 2017 -0700 $ >> >> >> >> Does that mean we should be building from the opensmalltalk repository >> >> instead of the pharo-vm repository (even temporarily)? >> > >> > officials VM for Pharo now are built using opensmalltalk-vm, yes. >> > we still keep our process for CI/testing purposes, though. >> >> Woot! Thank you Esteban!! >> >> >> +1 >> That will help us to help you, it's a win win. >> >> >> > >> > Esteban >> > >> >> >> >> Thanks, >> >> Alistair >> >> >> >> >> >>> On 3 May 2017 at 09:43, Esteban Lorenzano <estebanlm(a)gmail.com >> <mailto:estebanlm@gmail.com>> wrote: >> >>> in 15min, I will promote latest VM to stable VM. >> >>> The new stable VM has a lot of bugfixes, notably: >> >>> >> >>> - compactor works >> >>> - Cairo and Surface plugin now can coexist (and it does not crashes) >> >>> - lot of other small things >> >>> >> >>> cheers, >> >>> Esteban >> >>> >> >> >> > >> > >> >> > >

May 4, 2017

Re: [Pharo-dev] PI'm promoting new stable VMs

by Thierry Goubier

Le 03/05/2017 Ã 23:50, Eliot Miranda a Ã©crit : > > >> On May 3, 2017, at 1:52 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >>> Le 03/05/2017 Ã 22:39, Eliot Miranda a Ã©crit : >>> Hi Thierry, >> >> Hi Eliot, >> >>>> On May 3, 2017, at 1:20 PM, Thierry Goubier >>>> <thierry.goubier(a)gmail.com> wrote: >>>> >>>> I'm now chasing an old 64 bits vm from files.pharo.org. All the new >>>> ones for the past 2 months segfault. Would anybody have kept a ~ 2 >>>> month old 64 bits vm (threaded or not) for linux somewhere? >>> >>> I think the issue is not the version of the VM sources but the >>> version of GCC. Iconoile the 64-bit Linux VMs I build with GCC 4.4.x >>> and see no problems. Bintray uses 4.6.x and apparently segfaults. >>> Are you able to checkout opensmalltalk-vm and build your own 64-bit >>> Linux vm using GCC 4.4.x? You may have more success via this route. >> >> I'm on a system with gcc 6.3.0. The previous stable pharo vm is fine (20170212) so I'm back on it. None of the newest are, but I haven't done a bisect to tell you which number triggers the segfault. >> >> I do have random lockups with OSProcess on it, but they are cured with a Ctrl+., which is nice. >> >> I've never managed to get a home-compiled 64 bits vm to work without a segfault or a deadlock, so I've given up that path (*). > > Then I'll try and have a look asap. Thanks! Thierry > >> >> Regards, >> >> Thierry >> >> (*) I've never managed to be sure I had all the dependencies right (i.e. tracking through the long log output and trying to make sure cover all the errors by loading the right package). I could compile the vm, and run it a bit (run a few image building commands) before hitting either a deadlock (OSProcess-related?) or a segfault. >> >>> HTH >>> >>>> >>>> Regards, >>>> >>>> Thierry >>>> >>>>> Le 03/05/2017 Ã 21:58, Nicolas Cellier a Ã©crit : >>>>> >>>>> >>>>> 2017-05-03 17:45 GMT+02:00 Eliot Miranda >>>>> <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>>: >>>>> >>>>> >>>>> >>>>>> On May 3, 2017, at 4:22 AM, Esteban Lorenzano >>>>>> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>>>>> >>>>>> >>>>>>> On 3 May 2017, at 12:38, Alistair Grant >>>>>>> <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>> >>>>>>> wrote: >>>>>>> >>>>>>> Hi Esteban, >>>>>>> >>>>>>> $ curl http://get.pharo.org/64/60+vmLatest >>>>> <http://get.pharo.org/64/60+vmLatest> | bash >>>>>>> $ ./pharo --version >>>>>>> >>>>>>> Shows the build version as: >>>>>>> >>>>>>> VM: 201705022326 >>>>>>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git >>>>> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >>>>>>> Date: Tue May 2 16:26:41 2017 -0700 $ >>>>>>> >>>>>>> Does that mean we should be building from the opensmalltalk >>>>>>> repository instead of the pharo-vm repository (even >>>>>>> temporarily)? >>>>>> >>>>>> officials VM for Pharo now are built using opensmalltalk-vm, >>>>>> yes. we still keep our process for CI/testing purposes, >>>>>> though. >>>>> >>>>> Woot! Thank you Esteban!! >>>>> >>>>> >>>>> +1 That will help us to help you, it's a win win. >>>>> >>>>> >>>>>> >>>>>> Esteban >>>>>> >>>>>>> >>>>>>> Thanks, Alistair >>>>>>> >>>>>>> >>>>>>>> On 3 May 2017 at 09:43, Esteban Lorenzano >>>>>>>> <estebanlm(a)gmail.com >>>>> <mailto:estebanlm@gmail.com>> wrote: >>>>>>>> in 15min, I will promote latest VM to stable VM. The new >>>>>>>> stable VM has a lot of bugfixes, notably: >>>>>>>> >>>>>>>> - compactor works - Cairo and Surface plugin now can >>>>>>>> coexist (and it does not crashes) - lot of other small >>>>>>>> things >>>>>>>> >>>>>>>> cheers, Esteban >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

May 3, 2017

Re: [Pharo-dev] PI'm promoting new stable VMs

by Eliot Miranda

> On May 3, 2017, at 1:52 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > >> Le 03/05/2017 Ã 22:39, Eliot Miranda a Ã©crit : >> Hi Thierry, > > Hi Eliot, > >>> On May 3, 2017, at 1:20 PM, Thierry Goubier >>> <thierry.goubier(a)gmail.com> wrote: >>> >>> I'm now chasing an old 64 bits vm from files.pharo.org. All the new >>> ones for the past 2 months segfault. Would anybody have kept a ~ 2 >>> month old 64 bits vm (threaded or not) for linux somewhere? >> >> I think the issue is not the version of the VM sources but the >> version of GCC. Iconoile the 64-bit Linux VMs I build with GCC 4.4.x >> and see no problems. Bintray uses 4.6.x and apparently segfaults. >> Are you able to checkout opensmalltalk-vm and build your own 64-bit >> Linux vm using GCC 4.4.x? You may have more success via this route. > > I'm on a system with gcc 6.3.0. The previous stable pharo vm is fine (20170212) so I'm back on it. None of the newest are, but I haven't done a bisect to tell you which number triggers the segfault. > > I do have random lockups with OSProcess on it, but they are cured with a Ctrl+., which is nice. > > I've never managed to get a home-compiled 64 bits vm to work without a segfault or a deadlock, so I've given up that path (*). Then I'll try and have a look asap. > > Regards, > > Thierry > > (*) I've never managed to be sure I had all the dependencies right (i.e. tracking through the long log output and trying to make sure cover all the errors by loading the right package). I could compile the vm, and run it a bit (run a few image building commands) before hitting either a deadlock (OSProcess-related?) or a segfault. > >> HTH >> >>> >>> Regards, >>> >>> Thierry >>> >>>> Le 03/05/2017 Ã 21:58, Nicolas Cellier a Ã©crit : >>>> >>>> >>>> 2017-05-03 17:45 GMT+02:00 Eliot Miranda >>>> <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>>: >>>> >>>> >>>> >>>>> On May 3, 2017, at 4:22 AM, Esteban Lorenzano >>>>> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>>>> >>>>> >>>>>> On 3 May 2017, at 12:38, Alistair Grant >>>>>> <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>> >>>>>> wrote: >>>>>> >>>>>> Hi Esteban, >>>>>> >>>>>> $ curl http://get.pharo.org/64/60+vmLatest >>>> <http://get.pharo.org/64/60+vmLatest> | bash >>>>>> $ ./pharo --version >>>>>> >>>>>> Shows the build version as: >>>>>> >>>>>> VM: 201705022326 >>>>>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git >>>> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >>>>>> Date: Tue May 2 16:26:41 2017 -0700 $ >>>>>> >>>>>> Does that mean we should be building from the opensmalltalk >>>>>> repository instead of the pharo-vm repository (even >>>>>> temporarily)? >>>>> >>>>> officials VM for Pharo now are built using opensmalltalk-vm, >>>>> yes. we still keep our process for CI/testing purposes, >>>>> though. >>>> >>>> Woot! Thank you Esteban!! >>>> >>>> >>>> +1 That will help us to help you, it's a win win. >>>> >>>> >>>>> >>>>> Esteban >>>>> >>>>>> >>>>>> Thanks, Alistair >>>>>> >>>>>> >>>>>>> On 3 May 2017 at 09:43, Esteban Lorenzano >>>>>>> <estebanlm(a)gmail.com >>>> <mailto:estebanlm@gmail.com>> wrote: >>>>>>> in 15min, I will promote latest VM to stable VM. The new >>>>>>> stable VM has a lot of bugfixes, notably: >>>>>>> >>>>>>> - compactor works - Cairo and Surface plugin now can >>>>>>> coexist (and it does not crashes) - lot of other small >>>>>>> things >>>>>>> >>>>>>> cheers, Esteban >>>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

May 3, 2017