April 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-users] [ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 bindings)

by Alexandre Bergel

Hi Esteban, This is fantastic! We are eager to investigate how Roassal3 can run in an external window. Alexandre > On Apr 18, 2019, at 6:08 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > People that assisted to Pharo Days 2019 (or that follow my twitter account) already know this, but it needs to be formally announced: > > We are working on Spec 2.0, and it will provide not just the classic Morphic bindings but also a new option for developers: Gtk3 bindings! > > Why we want a Spec 2.0 with different backends? > > There are reasons that converged to decide us to make it: > > â¢ First, to provide a validated abstract Spec 2.0 that can be used with different backends, preparing Pharo to be able to switch backends without needing to recreate the full IDE from scratch each time (a problem we have partially now in our way to deprecate Morphic). > â¢ Second, because we receive from different sources the requirement of having the possibility of developing real native-looking desktop applications. Yes, in moment where people talk about the cloud, SaaS and web-applications as the "next big thing" (something that is been declared since years, by the way), we believe is important to provide this, for two big reasons: > â¢ Because there is still an important place for desktop applications market and most medium-size to big business still require them. > â¢ Because Pharo itself is a desktop application! (And we need to provide the best experience possible on it). > > For us, this is a fundamental step to continue improving Pharo itself, and it matches also the work we are doing on going real-headless: Pharo users will be able to start the Morphic world, a Gtk application or the next backend to come. > > Why Gtk3? > > There are some other important players in the "native widgets scene", so why we choose Gtk3? > > Again, several reasons were taken into account: > > â¢ Gtk3 is cross platform. Yes, technically is just "native" in linux, but it works on Windows and macOS too. > â¢ It is very mature and popular. > â¢ It is made in plain C. > > Next step: tool migration > > The only way to know if you have covered what is needed is actually taking real-life use cases and implementing them. We have a list of tools that needs to be migrated and we are starting from them: > > â¢ Old GT tools will be replaced by new Spec tools (while preserving its power). > â¢ Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now). > â¢ Pharo launcher as a standalone application is a good example of what you can do with the Gtk3 bindings. > > And that's it. Pharo 8.0 will come with Spec 2.0 and users will be able to benefit of it immediately :) > > > A small screenshot of the new Inspector (WIP): > > <Screenshot 2019-04-18 at 12.07.16.png> > > Esteban

April 19, 2019

Re: [Pharo-dev] [squeak-dev] Any experts on using path in app bundles willing to help me?

by Eliot Miranda

Hi Esteban, On Fri, Apr 19, 2019 at 12:51 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yep. > The Pharo distribution uses install_name_tool to deal with it, if you want > an example already in osvm code: > > > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/build.macos64x64… > It's perhaps a case of "if it ain't broke, don't fixit", but I wonder if it would be better for Pharo to use Frameworks to hold dlls and Resources to hold plugin dlls/bindles. Contents/MacOS/Plugins is, I *think*, unique to Pharo. > Esteban > > On 18 Apr 2019, at 19:35, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Thu, Apr 18, 2019 at 10:08 AM Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > >> Hi All, >> >> I have a plugin dependent on several support libraries that may be >> shared with other plugins. So I want the support libraries in a common >> place (TheVm.app/Contents/Frameworks) while the plugins themselves are >> bundles in TheVM.app/Contents/Resources. In allowing one to install plugin >> support libraries in TheVM.app/Contents/Frameworks I have to use the >> linker's -rpath feature to specify where dlopen may find the search >> libraries. The question i don't see an answer to in Apple's documentation >> is whether one uses -rpath when linking the plugin, or when linking the VM >> into which the plugin will be loaded, or both. Anybody ever done this and >> know definitively what to do? >> > > Never mind. I think I've found what I need: > > https://medium.com/@donblas/fun-with-rpath-otool-and-install-name-tool-e3e4… > https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath > > _,,,^..^,,,_ > best, Eliot > > > > -- _,,,^..^,,,_ best, Eliot

April 19, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by ducasse

Our plan is to use Pango directly or indirectly (I do not remember exactly but via SDL2). But as everything it takes time. First the VM should get headless and more. Now if we would have some other sources of fundings Pharo would not be like it is now. Stef > On 19 Apr 2019, at 12:48, phil(a)highoctane.be wrote: > > Question: Can't we use some platform facility for renderering text on a surface instead of using FreeType? > > e.g. Windows https://docs.microsoft.com/en-us/windows/desktop/direct2d/direct2d-and-dire… <https://docs.microsoft.com/en-us/windows/desktop/direct2d/direct2d-and-dire…> > > Phil > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Garanti sans virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <x-msg://72/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > On Fri, Apr 19, 2019 at 12:12 PM Tim Mackinnon <tim(a)testit.works> wrote: > >> On 17 Apr 2019, at 23:43, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: >> >> Somebody should just decide that new version needs to be to back ported. > > Who is the somebody that would decide? If we have to live with Pharo 7.x for the next year (possibly a bit less) - some of the UI fixes would be much appreciated, particularly if its easy to do. > > Perhaps if we do a 7.0.4 we might do that? > > Tim > > p.s. 7.0.3 definitely doesnât fix the font glitch (sadly), and Guilleâs fix cause my image to deadlock for 3-5 minutes when I see it (which might actually be helpful - is it could conform a specific type of problem)

April 19, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by ducasse

We will certainly back port the font glitches in P7.0 because it is important. Stef > On 18 Apr 2019, at 14:54, Tim Mackinnon <tim(a)testit.works> wrote: > > >> On 17 Apr 2019, at 23:43, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: >> >> Somebody should just decide that new version needs to be to back ported. > > Who is the somebody that would decide? If we have to live with Pharo 7.x for the next year (possibly a bit less) - some of the UI fixes would be much appreciated, particularly if its easy to do. > > Perhaps if we do a 7.0.4 we might do that? > > Tim > > p.s. 7.0.3 definitely doesnât fix the font glitch (sadly), and Guilleâs fix cause my image to deadlock for 3-5 minutes when I see it (which might actually be helpful - is it could conform a specific type of problem)

April 19, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by phil＠highoctane.be

Question: Can't we use some platform facility for renderering text on a surface instead of using FreeType? e.g. Windows https://docs.microsoft.com/en-us/windows/desktop/direct2d/direct2d-and-dire… Phil <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Garanti sans virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Fri, Apr 19, 2019 at 12:12 PM Tim Mackinnon <tim(a)testit.works> wrote: > > On 17 Apr 2019, at 23:43, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Somebody should just decide that new version needs to be to back ported. > > > Who is the somebody that would decide? If we have to live with Pharo 7.x > for the next year (possibly a bit less) - some of the UI fixes would be > much appreciated, particularly if its easy to do. > > Perhaps if we do a 7.0.4 we might do that? > > Tim > > p.s. 7.0.3 definitely doesnât fix the font glitch (sadly), and Guilleâs > fix cause my image to deadlock for 3-5 minutes when I see it (which might > actually be helpful - is it could conform a specific type of problem) >

April 19, 2019

Re: [Pharo-dev] Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"

by Serge Stinckwich

done : https://github.com/pillar-markup/pillar/issues/368 On Thu, Apr 18, 2019 at 4:15 PM ducasse <stepharo(a)netcourrier.com> wrote: > Hi serge > > I cannot check now but Pillar should be running in P7 64 bits without > problem. > I see many warnings too. > Can you open a bug entry? > Stef > > > On 18 Apr 2019, at 15:48, Serge Stinckwich <serge.stinckwich(a)gmail.com> > wrote: > > Any news on this ? This is only a 32 bits VM problem ? > Why when I install Pillar on MacOS, the 32bits VM is used and not 64bits > VM ? > > > On Fri, May 11, 2018 at 11:37 AM <serge.stinckwich(a)gmail.com> wrote: > >> Yes this is just a little bit annoying when you use Pillar because you >> have a lot of noise ;-) >> >> EnvoyÃ© de mon iPhone >> >> > Le 11 mai 2018 Ã 17:17, Esteban Lorenzano <estebanlm(a)gmail.com> a >> Ã©crit : >> > >> > This is a problem since more than one year. >> > Apple changed something on their apis and nobody knows how to fix it. >> > >> > but it is just a warning and you can work normally anyway :) >> > >> > cheers, >> > Esteban >> > >> >> On 11 May 2018, at 00:14, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >> >> Yeah, I saw that for a while too, but my 64bit P7 VMs from the last >> couple of days don't do this anymore. >> >> I don't know why. >> >> >> >>> On 10 May 2018, at 23:53, Tim Mackinnon <tim(a)testit.works> wrote: >> >>> >> >>> I noticed that recent Pharo 6.1 zero conf downloads show lots of >> these errors when you run the image in the terminal. Previous versions >> didnât do this - is this something to do with the latest vm upgrade? >> >>> >> >>> ./pharo-ui PagerDuty.image >> >>> >> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: >> Error: unsupported compressor 8 >> >>> >> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: >> Error: Unknown compression scheme encountered for file >> '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' >> >>> >> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: >> Error: unsupported compressor 8 >> >>> >> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: >> Error: Unknown compression scheme encountered for file >> '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' >> >>> >> >>> >> >>> Tim >> >> >> >> >> > >> > >> > > > -- > Serge Stinckwic > h > > Int. Research Unit > on Modelling/Simulation of Complex Systems (UMMISCO) > Sorbonne University > (SU) > French National Research Institute for Sustainable Development (IRD) > U > niversity of YaoundÃ© I, Cameroun > "Programs must be written for people to read, and only incidentally for > machines to execute." > https://twitter.com/SergeStinckwich > > > -- Serge Stinckwic âhâ Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) âSorbonne University (SU) French National Research Institute for Sustainable Development (IRD)â U âniversity of YaoundÃ© Iâ, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich â

April 19, 2019

Re: [Pharo-dev] Handling of deprecation packages

by Stephan Eggermont

Torsten Bergmann <astares(a)gmx.de> wrote: > The problem with the new vs. old streams seems to be that migration is > unfinished even for the base image. > Development already switched quickly to newer construction sites instead > of finishing these old ones. There are indeed several open issues with the new streams usage. I posted one on the handling of filing in fileouts by drag and drop. The issue I see with existing code is mostly that an object is used as a stream but is actually an information holder which understands much more than the stream protocol. Rewriting that code to use a streamHolder can be non-trivial. The fallback behavior of a readWriteStream opened on a read-only file is also not easy to get right. Stephan

April 19, 2019

Re: [Pharo-dev] Any experts on using path in app bundles willing to help me?

by Esteban Lorenzano

yep. The Pharo distribution uses install_name_tool to deal with it, if you want an example already in osvm code: https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/build.macos64x64… <https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/build.macos64x64…> Esteban > On 18 Apr 2019, at 19:35, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Thu, Apr 18, 2019 at 10:08 AM Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: > Hi All, > > I have a plugin dependent on several support libraries that may be shared with other plugins. So I want the support libraries in a common place (TheVm.app/Contents/Frameworks) while the plugins themselves are bundles in TheVM.app/Contents/Resources. In allowing one to install plugin support libraries in TheVM.app/Contents/Frameworks I have to use the linker's -rpath feature to specify where dlopen may find the search libraries. The question i don't see an answer to in Apple's documentation is whether one uses -rpath when linking the plugin, or when linking the VM into which the plugin will be loaded, or both. Anybody ever done this and know definitively what to do? > > Never mind. I think I've found what I need: > https://medium.com/@donblas/fun-with-rpath-otool-and-install-name-tool-e3e4… <https://medium.com/@donblas/fun-with-rpath-otool-and-install-name-tool-e3e4…> > https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath <https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath> > > _,,,^..^,,,_ > best, Eliot

April 19, 2019

Re: [Pharo-dev] Handling of deprecation packages

by Christopher Fuhrman

Hello all, Apologies if I am on the wrong page.... On Thu, Apr 18, 2019, 09:26 Torsten Bergmann <astares(a)gmx.de> wrote: > That's why also "Deprecated70" could not easily get removed. And there is > no guide in how to migrate to the new stream. > At least I do not know of something that could quickly explain on how to > convert. > The following guide was useful to me: https://github.com/pharo-open-documentation/pharo-wiki/blob/master/Migratio…

April 19, 2019

Re: [Pharo-dev] [squeak-dev] Any experts on using path in app bundles willing to help me?

by Ben Coman

On Fri, 19 Apr 2019 at 01:35, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Thu, Apr 18, 2019 at 10:08 AM Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi All, >> >> I have a plugin dependent on several support libraries that may be shared with other plugins. So I want the support libraries in a common place (TheVm.app/Contents/Frameworks) while the plugins themselves are bundles in TheVM.app/Contents/Resources. In allowing one to install plugin support libraries in TheVM.app/Contents/Frameworks I have to use the linker's -rpath feature to specify where dlopen may find the search libraries. The question i don't see an answer to in Apple's documentation is whether one uses -rpath when linking the plugin, or when linking the VM into which the plugin will be loaded, or both. Anybody ever done this and know definitively what to do? > > > Never mind. I think I've found what I need: > https://medium.com/@donblas/fun-with-rpath-otool-and-install-name-tool-e3e4… > https://wincent.com/wiki/@executable_path,_@load_path_and_@rpath Interesting reading. thx for the links. cheers -ben

April 19, 2019