- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

by Norbert Hartl

This way cooler than expected. Lot of stuff already done. Great! Norbert > Am 08.08.2019 um 09:53 schrieb "tesonep(a)gmail.com" <tesonep(a)gmail.com>: > > 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 >

Aug. 8, 2019

Re: [Pharo-users] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

by Sven Van Caekenberghe

That is very impressive, thank you all ! > On 8 Aug 2019, at 09:53, 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 >

Aug. 8, 2019

Re: [Pharo-users] Pharo 1.4 porting

by dario.trussardi65

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

Aug. 8, 2019

Re: [Pharo-users] Pharo 1.4 porting

by dario.trussardi65

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

Aug. 8, 2019

Re: [Pharo-users] Pharo 1.4 porting

by sk

Hi Dario 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. 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. Cheers Carlo On 07 Aug 2019, at 17:05, dario.trussardi65 <dario.trussardi65(a)gmail.com> wrote: Ciao, i have a old Pharo1.4 Latest update: #14445 run on MacBook with Mac OS X 10.7.5 ( Lion ). In this system the Pharo image run fine. I copy the relative folder on a MacBook with Mac OS X 10.14.6 ( Mojave ). Now in this system, when i double click on the relative folder icon the system open a empty black foreground window. The System Application don't report any Pharo application. I need to register - install a Pharo application? In this last system i also copy a Pharo GemTools-1.0-beta.8.7-3101 folder. It run without problem. Any consideration is welcome. Thanks, Dario

Aug. 8, 2019

Re: [Pharo-users] A Canticle for Smalltalk

by Richard O'Keefe

Nice enough, but where is the canticle? On Tue, 6 Aug 2019 at 03:20, Richard Kenneth Eng <horrido.hobbies(a)gmail.com> wrote: > A big fan of my work created this rogue video: > https://drive.google.com/file/d/1opveHaukFK8WbQ8wg8b14wuKJsjoOZfO/view > > I appreciate the homage, but I can't take credit for it. > > It's really quite beautiful, though. I'm using it as part of my evangelism. > >

Aug. 8, 2019

Re: [Pharo-users] Desktop - just try ...

by tesonep＠gmail.com

Very very nice, and it fits perfectly!!! On Thu, Aug 8, 2019 at 12:16 AM Torsten Bergmann <astares(a)gmx.de> wrote: > > |image| > image := ZnEasy getJpeg: 'http://www.bing.com/th?id=OHR.NubbleLight_EN-US4307721919_1920x1080.jpg&rf=…'. > > World > backgroundImage: image > layout: #scaled. > -- Pablo Tesone. tesonep(a)gmail.com

Aug. 8, 2019

[ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

by tesonep＠gmail.com

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

Aug. 8, 2019

Desktop - just try ...

by Torsten Bergmann

|image| image := ZnEasy getJpeg: 'http://www.bing.com/th?id=OHR.NubbleLight_EN-US4307721919_1920x1080.jpg&rf=…'. World backgroundImage: image layout: #scaled.

Aug. 7, 2019

Re: [Pharo-users] Can I control the location of the PharoDebug.log

by Dale Henrichs

On 8/7/19 11:32 AM, Torsten Bergmann wrote: > Dale wrote: >> I used the double click trick on "Log file name" and followed it to the above messages > for the records: > > Beside double click you can also right click on a setting and select "Browse" to find > where it is implemented. You can then also "Save" the current settings. > > The settings framework is described here: http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/Settings.pdf > > Bye > T. Thanks for the additional information Torsten ... now that you point out the Browse menu, I see that it and double click do the same thing: Back when I was looking for help with the my weird local directory problem and remembered the "double click trick", I interpreted the 'browse` menu item to be mean 'browse the local directory' not 'browse the code the code that implements the settings' ... my bad:) Dale Dale

Aug. 7, 2019