- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)
by ducasse Aug. 11, 2019

Aug. 11, 2019

> On 11 Aug 2019, at 13:19, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Excellent news! > > I should say that for GT we are currently using the minheadlessVM (Ronieâs work) out of the opensmalltalk-vm repo (https://bintray.com/opensmalltalk/vm/cog) and it works remarkably well. > > We started to play with your minheadlessVM. So far it looks like there are differences, although I am sure they are not large. like what? > > So, what is the difference between the minheadlessVM built by you versus the one from opensmalltalk-vm? > > Cheers, > Doru > > >> On Aug 8, 2019, at 9:53 AM, tesonep(a)gmail.com wrote: >> >> TL;DR; >> ====== >> >> For the anxious, you can get real headless vm and image from zero-conf. >> >> $ wget get.pharo.org/64/80+vmHeadlessLatest | bash >> >> Zero conf scripts remain unchanged for users. >> >> However, if you are launching the VM by hand from the executable >> instead of the launcher scripts (pharo and pharo-ui) as in >> >> $ ./pharoexecutable Pharo.image >> >> the image will launch in headless mode and will not open a window. >> To launch it in headfull, you can use the --interactive argument after >> the image, which will make the image open a window using SDL2. >> >> $ ./pharoexecutable Pharo.image --interactive >> >> Long version >> ============ >> >> Hi, this mail is the happy intermediate result of the work that us, >> the Pharo Consortium Team, has been doing in the last couple of >> months. >> Our main objective is to have a real headless implementation of Pharo >> where all the responsibility to open or not a World window (or other) >> is handled by the image. >> For doing so we have done a series of modifications in the image and >> the VM side. >> We consider this is the path that Pharo 8 and following versions >> should follow, as it will severely improve server-side and command >> line Pharo and in building custom desktop applications. >> >> These modifications are available only in 64-bits machines (Windows, >> OSX, and Linux). >> ARM32 and 64bits headless is in the roadmap, but it is delayed because >> we have prioritized our three major platforms for this first couple of >> months. >> >> All this work is based in Opensmalltalk-VM and Ronnie's initial work >> on headless. >> We are really grateful to all the contributors in the history of this >> nice product. >> To achieve a real headless VM we have brought modifications in the >> source tree because most of the platform code to open and manipulate >> windows is not required anymore. >> Instead, we use the SDL2 library that implements a nice layer on top >> of the OS and allows us to manage on the image side through FFI. >> >> So this mail is now an open call for (beta?)testing. >> The sources of the current VM we are building are in the headless branch in >> https://github.com/pharo-project/opensmalltalk-vm >> And we have set up a CI that is both building and testing the VM in >> https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ >> >> For the future we have a lot of ideas, that will wait for another long >> email or a beer-talk @ESUG. >> We want to hear your ideas!! >> >> Image-Side Improvements >> ======================= >> >> - The image handles the creation or not of the main world window. >> - We incorporated the idea of World renderer, where different backends >> are used to render the world. >> - We have 3 backends: VM support (compatibility with non-headless >> VMs), and OSWindow with two backends: SDL and GTK3+. >> - The modifications in the image are fully backward compatible with >> the non-headless VM and are pushed since weeks in the latest 8.0 >> image. >> - We move the handling of events to the image side when using SDL and >> GTK3+, opening the door to a richer set of events and finer-grained >> control over them. >> - SDL and GTK versions are implemented using FFI calls. >> >> VM-Side Improvements >> ==================== >> >> - VMMaker code migrated to Tonel thanks to Feenk and included in the >> repository of the VM. >> - Making VMMaker execute in Pharo 7 and 8. >> - Removing GPL code from the VM repository (GDB). >> >> - Slowly adding new tests for the JIT / Slang and VMGeneration. >> - Restructuring of the source code. >> - A new simpler CMake build. >> - Generate VM code from Slang on each build. >> - A CI process to validate (including the run of the tests in Pharo >> and the ones adding to the VM). >> - Simplification of the codebase. >> >> - Maximize the reuse of code between the platforms (preferring the >> standard versions over the platform-specific). >> - Cleaning up duplicated code. >> - All the plugins are now external plugins. >> - The VM is now a dynamic library. This is a first step towards >> embedding Pharo into other applications. >> - The main executable is a thin frontend (you can change it or >> implement your own). >> >> - Removing unused plugins. >> - Improved crash dump. Especially the crash dump works now in Windows 64bits. >> - Dummy implementation of Security plugin (it is going away.... eventually). >> - Cleanup of SSL, UUID, and Socket plugin. >> >> - Cleanup of conditional code (Still to improve). >> - Improving the types used in the functions (we have to be neat to be >> multiplatform/multi-arch). >> - Improving the lookup of modules >> - Improving the logging of the VM >> - Improving the handling of VM arguments >> >> >> Thanks a lot for reading so long!! >> We hope you enjoy the VM and please tell us all the problems you find!! >> >> Pablo, Guille, and Esteban >> > > -- > feenk.com > > "Being happy is a matter of choice." > > > > > > >

1 0

[ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)
by tesonep＠gmail.com Aug. 11, 2019

Aug. 11, 2019

TL;DR; ====== For the anxious, you can get real headless vm and image from zero-conf. $ wget get.pharo.org/64/80+vmHeadlessLatest | bash Zero conf scripts remain unchanged for users. However, if you are launching the VM by hand from the executable instead of the launcher scripts (pharo and pharo-ui) as in $ ./pharoexecutable Pharo.image the image will launch in headless mode and will not open a window. To launch it in headfull, you can use the --interactive argument after the image, which will make the image open a window using SDL2. $ ./pharoexecutable Pharo.image --interactive Long version ============ Hi, this mail is the happy intermediate result of the work that us, the Pharo Consortium Team, has been doing in the last couple of months. Our main objective is to have a real headless implementation of Pharo where all the responsibility to open or not a World window (or other) is handled by the image. For doing so we have done a series of modifications in the image and the VM side. We consider this is the path that Pharo 8 and following versions should follow, as it will severely improve server-side and command line Pharo and in building custom desktop applications. These modifications are available only in 64-bits machines (Windows, OSX, and Linux). ARM32 and 64bits headless is in the roadmap, but it is delayed because we have prioritized our three major platforms for this first couple of months. All this work is based in Opensmalltalk-VM and Ronnie's initial work on headless. We are really grateful to all the contributors in the history of this nice product. To achieve a real headless VM we have brought modifications in the source tree because most of the platform code to open and manipulate windows is not required anymore. Instead, we use the SDL2 library that implements a nice layer on top of the OS and allows us to manage on the image side through FFI. So this mail is now an open call for (beta?)testing. The sources of the current VM we are building are in the headless branch in https://github.com/pharo-project/opensmalltalk-vm And we have set up a CI that is both building and testing the VM in https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ For the future we have a lot of ideas, that will wait for another long email or a beer-talk @ESUG. We want to hear your ideas!! Image-Side Improvements ======================= - The image handles the creation or not of the main world window. - We incorporated the idea of World renderer, where different backends are used to render the world. - We have 3 backends: VM support (compatibility with non-headless VMs), and OSWindow with two backends: SDL and GTK3+. - The modifications in the image are fully backward compatible with the non-headless VM and are pushed since weeks in the latest 8.0 image. - We move the handling of events to the image side when using SDL and GTK3+, opening the door to a richer set of events and finer-grained control over them. - SDL and GTK versions are implemented using FFI calls. VM-Side Improvements ==================== - VMMaker code migrated to Tonel thanks to Feenk and included in the repository of the VM. - Making VMMaker execute in Pharo 7 and 8. - Removing GPL code from the VM repository (GDB). - Slowly adding new tests for the JIT / Slang and VMGeneration. - Restructuring of the source code. - A new simpler CMake build. - Generate VM code from Slang on each build. - A CI process to validate (including the run of the tests in Pharo and the ones adding to the VM). - Simplification of the codebase. - Maximize the reuse of code between the platforms (preferring the standard versions over the platform-specific). - Cleaning up duplicated code. - All the plugins are now external plugins. - The VM is now a dynamic library. This is a first step towards embedding Pharo into other applications. - The main executable is a thin frontend (you can change it or implement your own). - Removing unused plugins. - Improved crash dump. Especially the crash dump works now in Windows 64bits. - Dummy implementation of Security plugin (it is going away.... eventually). - Cleanup of SSL, UUID, and Socket plugin. - Cleanup of conditional code (Still to improve). - Improving the types used in the functions (we have to be neat to be multiplatform/multi-arch). - Improving the lookup of modules - Improving the logging of the VM - Improving the handling of VM arguments Thanks a lot for reading so long!! We hope you enjoy the VM and please tell us all the problems you find!! Pablo, Guille, and Esteban

4 3

Re: [Pharo-users] Old projects in ss3
by Dale Henrichs Aug. 10, 2019

Aug. 10, 2019

Thanks Carlo ... that will certainly help me solve this problem ... I probably won't be able to get ss3 patched until after ESUG :), but now I know where to look ... Dale On 8/10/19 3:20 PM, sk via Pharo-users wrote: > Hi Dale > > Looks like a NumberParser error due to the chrome Accept request > header including "v=b3". > > Chrome sends something like: " > Accept: > text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3" > which seems to break on SS3. > You could try wget and receive the same error:Â wget --header="Accept: > text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3" > Â "http://ss3.gemtalksystems.com/ss/GTDImplementation" > If you remove v=b3 or modify it to by v=3 then there is no error. > > Somewhat related bug report for a different project: > https://github.com/emicklei/go-restful/issues/400 > > Carlo

1 0

Old projects in ss3
by Sergio Fedi Aug. 10, 2019

Aug. 10, 2019

Hello, I'm coming back after a few years (Pharo 5.0) and tried to take a look and download some projects I have on ss3. I'm using a Pharo 7.0 image. Going to the ss3 site I find that I can't access my projects, a "Reading a number failed: a digit between 0 and 9 expected" error shows in the page. Trying to view them from Monticello, after adding the appropriate repository it shows weird characters for the name and versions and it is unable to load them. [image: image.png] What am I missing/doing wrong? Thanks!

5 7

Re: [Pharo-users] Pharo 1.4 porting
by dario.trussardi65 Aug. 10, 2019

Aug. 10, 2019

Ciao Carlo, thanks.... > > Hi Dario > > You could try the VM Cog.app-15.25.3390.tgz which can be found at http://www.mirandabanda.org/files/Cog/VM/2015/VM.r3390/ > > To test it you could > unzip the VM > drag your specific image onto the Cog.app and see if it works. It works fine. > If Mac OSX complains about permissions you may have to right click on the Cog.app and select 'Open', after which it will ask you which image you would like to open. You can then cancel and try to drag your specific pharo image onto the Cog.app and see if it works. > > You may then be able to replace the VM in the one-click package with this one if it works. This is not clear to me. What i need to do for this set? Thanks, Dario > > On 08 Aug 2019, at 17:08, dario.trussardi65 <dario.trussardi65(a)gmail.com> wrote: > > Ciao Carlo, > > sorry. > > I add some information about Pharo 1-4 on Mac OS X 10.14.6 ( Mojave ). > >> >> As far as I know there was an issue with the older VM's on Mac OS X where the graphics subsystem changed, causing that blank/black screen. >> >> You will probably be able to use a different VM and make it work. > > Excuse my ignorance but I have no experience in this regard. > >> I've got some older Pharo 1.2.2 images and either >> CogMT.3390.app (Squeak Cog 4.0.3390) >> or maybe even one of the other mac vm's from around that time will work. > > > Where i can download a valid mac vm's ? > > And where should i put it ? > > The Pharo-1.4 on my system have a: > > Contents folder > > and CogVM.exe > ( the relative info are: type: Microsoft Windows application > date: 22/6/2012 > size: 2MB ) > > and some other files: > FT2Plugin.dll > libfreetype-6.dll > > Pharo-1.4-one-click.bat > > Pharo-1.4-one-click.sh > SueakFFIPrims.dll > > README.txt > > > Thanks, > > Dario > > >

1 0

Destructive copy in #replaceFrom:to:with:startingAt:
by James Foster Aug. 10, 2019

Aug. 10, 2019

After many hours of debugging Iâve finally discovered that Pharoâs implementation of #replaceFrom:to:with:startingAt: does not make any check for overlapping regions to avoid destructive operations. | bytes | bytes := #(1 2 3 4 5 6 7 8) copy. bytes replaceFrom: 4 to: 7 with: bytes startingAt: 1. bytes "#(1 2 3 1 2 3 1 8) in Pharo" "#(1 2 3 1 2 3 4 8) in GemStoneâ Essentially, Pharo has taken a memcpy() approach rather than a memmove() approach (https://fresh2refresh.com/c-programming/c-interview-questions-answers/what-… <https://fresh2refresh.com/c-programming/c-interview-questions-answers/what-…>). While it isnât the implementation I would choose, at least now I know! James Foster

2 1

Re: [Pharo-users] Pharo 1.4 porting
by dario.trussardi65 Aug. 9, 2019

Aug. 9, 2019

Ciao Carlo, sorry. I add some information about Pharo 1-4 on Mac OS X 10.14.6 ( Mojave ). > > As far as I know there was an issue with the older VM's on Mac OS X where the graphics subsystem changed, causing that blank/black screen. > > You will probably be able to use a different VM and make it work. Excuse my ignorance but I have no experience in this regard. > I've got some older Pharo 1.2.2 images and either > CogMT.3390.app (Squeak Cog 4.0.3390) > or maybe even one of the other mac vm's from around that time will work. Where i can download a valid mac vm's ? And where should i put it ? The Pharo-1.4 on my system have a: Contents folder and CogVM.exe ( the relative info are: type: Microsoft Windows application date: 22/6/2012 size: 2MB ) and some other files: FT2Plugin.dll libfreetype-6.dll Pharo-1.4-one-click.bat Pharo-1.4-one-click.sh SueakFFIPrims.dll README.txt Thanks, Dario

2 1

Catalogue Browser - Bootstrap 4
by Jeff Gray Aug. 9, 2019

Aug. 9, 2019

So Bootstrap 4 has just come on to my radar - thanks Esteban. I usually look for things in the Catalogue Browser. Is that no longer the place to go? Do I need to get into searching Git instead? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

[Announcement] Camp Smalltalk - Portland 2019 - October 4-6
by Andres Valloud Aug. 8, 2019

Aug. 8, 2019

Hey all, The Portland Smalltalk Crew is hosting another Camp Smalltalk in Portland this fall. Join us! When: October 4-6 Where: CTRL-H -- Portland Hackerspace Registration: https://www.eventbrite.com/e/camp-smalltalk-portland-2019-tickets-666397061… Sponsorship: GemTalk Systems Instantiations LabWare Heidbrink Consulting Inc Corporate Smalltalk Consulting Ltd FAST Lam Research Schedule: (Talk Schedule - TBD) Friday: Noon - Camp Smalltalk begins Saturday 1:30pm - Hike in Washington Park 6pm - Social dinner @ CTRL-H Sunday: 8pm - Camp Smalltalk ends Swag: Camp Smalltalk T-Shirt Andres.

1 0

Re: [Pharo-users] Pharo 1.4 porting
by dario.trussardi65 Aug. 8, 2019

Aug. 8, 2019

Ciao Carlo, thanks. > > As far as I know there was an issue with the older VM's on Mac OS X where the graphics subsystem changed, causing that blank/black screen. > > You will probably be able to use a different VM and make it work. Excuse my ignorance but I have no experience in this regard. > I've got some older Pharo 1.2.2 images and either > CogMT.3390.app (Squeak Cog 4.0.3390) > or maybe even one of the other mac vm's from around that time will work. Where i can download a valid mac vm's ? And where should i put it ? The Pharo on my system have a Contents folder, which inside has: info.plist MacOS folder with: Pharo ( exec ) Plugins folder Resources folder Do you need more information? Thanks, Dario

1 0