Re: [Pharo-users] [Pharo-dev] Pharo6 server deployment and no home directory

> On 9. Jun 2017, at 13:26, Sven Van Caekenberghe wrote: Hey, > Why would $HOME not be set ? In this specific case runit doesn't export HOME when starting my service but looking at systemd and picking a random service like exim4.service I see: $ strings /proc/946/environ PATH=/usr/local/sb

Re: [Pharo-users] [Pharo-dev] Pharo6 server deployment and no home directory

Why would $HOME not be set ? And if it is not set / seems like a reasonable default. > On 9 Jun 2017, at 06:06, Holger Freyther wrote: > > >> On 9. Jun 2017, at 11:09, Holger Freyther wrote: >> >> > > >> a.) Behave like unix and resolve $HOME to '' >> >> $ unset HOME >> $ echo $HOME/.con

Re: [Pharo-users] PharoCloud drops VM hosting and focuses on Ephemeric Cloud

On Fri, Jun 9, 2017 at 6:59 AM, mikefilonov wrote: > Hello, > > I just wanted to make some clarifications on what is going on with > PharoCloud and how I see the future of the project. > > PharoCloud is not closing, but just dropping VM hosting support. We will > continue to develop and maintain

[Pharo-users] crash.dmp of OSSubProcess on Pharo 6.0

I got a seg fault when I tried to execute some OSSubProcess code in Pharo 6.0. Namely, | process | process := OSSUnixSubprocess new command: '/bin/cat'; redirectStdin; redirectStdout; run. process stdinStream nextPutAll: 'we

Re: [Pharo-users] Pharo6 server deployment and no home directory

> On 9. Jun 2017, at 11:09, Holger Freyther wrote: > > > a.) Behave like unix and resolve $HOME to '' > > $ unset HOME > $ echo $HOME/.config > /.config > > self home / '.config' => '/.config' Implementing UnixResolver>>#home as home ^ self directoryFromEnvVariableNamed: 'HOME' o

Re: [Pharo-users] Pharo6 server deployment and no home directory

> On 8. Jun 2017, at 23:16, Holger Freyther wrote: > > Hey Juraj! Hey! this will most likely block more people trying to deploy a headless Pharo6 image but I am not so sure how to properly fix it. > $ unset HOME > $ pharo ... > Error: Can't find the requested origin ... > UnixResolver(Pla

[Pharo-users] PharoCloud drops VM hosting and focuses on Ephemeric Cloud

Hello, I just wanted to make some clarifications on what is going on with PharoCloud and how I see the future of the project. PharoCloud is not closing, but just dropping VM hosting support. We will continue to develop and maintain Ephemeric Cloud which allows you to publish Pharo web application

[Pharo-users] Teapot: Managing authentication by a third party (Fossil)

Hi, I'm trying to make some test on a distributed wiki provided by Fossil as a backend for storage/auth, Mustache + Material Design Lite for the frontend and Teapot using as middleware for logic and connecting frontend and backend. Teapot is connected with Fossil via JSON and domain objects are st

Re: [Pharo-users] Wiring objects, IoC and Service Locator

Peter Uhnak wrote > Scale can make all the difference. I don't think it should. If you have a small cluster of objects where you can manage the dependencies yourself, you can compose larger objects from them and manage the dependencies the same way. By doing so, you'll get an object that is simp

Re: [Pharo-users] Wiring objects, IoC and Service Locator

On Thu, Jun 08, 2017 at 08:02:04AM -0700, Attila Magyar wrote: > Vitor Medina Cruz wrote > > This is exactly my concern! Sure, for small stuff that is not a problem, > > but what if you have a big app? > > I don't think it makes any difference. Scale can make all the difference. Imagine the compl

Re: [Pharo-users] Traits, method flatten

Yes, Nicolai proposed a fix, and it worked well enough. So it should make you happy. Hilaire Le 08/06/2017 à 06:00, Sean P. DeNigris a écrit : > HilaireFernandes wrote >> I made another attempt to >> persist this time with filetree://. The net result is the same, the >> Traits logic is lost in t

Re: [Pharo-users] Wiring objects, IoC and Service Locator

On Thu, Jun 08, 2017 at 08:46:15AM -0300, Vitor Medina Cruz wrote: > This is true for IoC DI containers, but I don't think it applies for > service locator, which, I think, could not be considered a framework > approach. Actually, I think being a framework is the big problem of the of > the former

Re: [Pharo-users] is it related to Freetype or Athens?

Another good reason to migrate Dr. Geo to Pharo 6 ;) Le 07/06/2017 à 21:53, Peter Uhnak a écrit : > There were couple GC/memory related issues in the VM's plugin, that were > fixed or worked around in the Pharo 6 VM that apparently were present for a > long time... so maybe that's also part of w

Re: [Pharo-users] ZnClient: how to emulate a curl command

Hi Sven, I was making a silly mistake in the server URL. I just forgot the extra "/" after servers port number, so it was "8081/json" instead of "8081json". I imagine that maybe is a test for validating properly form urls, but also I will have a more trained eye for such errors next time. Now is w

Re: [Pharo-users] Bloc/Brick/Spec

Hi Marc, It would be so cool but no, it's not planned. Like SDL and Morphic, Gtk is only used as a backend for windowing. This means that only primitives related to windowing are currently implemented (i.e GtkWindow related apis). Working on widget binding with Gtk or Qt is something i would like

Re: [Pharo-users] Wiring objects, IoC and Service Locator

Vitor Medina Cruz wrote > This is exactly my concern! Sure, for small stuff that is not a problem, > but what if you have a big app? I don't think it makes any difference. You have to decide in each case whether an object is an internal (implementation detail) and therefore it must be created from

Re: [Pharo-users] Pharo6 server deployment and no home directory

> On 17. Apr 2017, at 21:30, Juraj Kubelka wrote: > > Hi Holger, Hey Juraj! > Basically it tests `FileLocator home exists`, if false, it does not touch > disk. We could also add a #disablePersistence method if necessary. I thought I tested it but somehow it is broken (again)? Looks like Fi

Re: [Pharo-users] Porting Transducers to Pharo

2017-06-08 15:37 GMT+02:00 Steffen Märcker : > In fact, I moved from Mocketry to DoubleAgents quite some time ago... =) It was greatly updated from VW version. (look for details here http://dionisiydk.blogspot.fr/2016/04/new-version-of-mocketry-30.html)

Re: [Pharo-users] Porting Transducers to Pharo

In fact, I moved from Mocketry to DoubleAgents quite some time ago... =) Am .06.2017, 23:04 Uhr, schrieb Denis Kudriashov : 2017-06-07 22:04 GMT+02:00 p...@highoctane.be : I read your note about DoubleAgents for the tests, well, yeah this one we do not have. I read about it on the blog of it

Re: [Pharo-users] Porting Transducers to Pharo

Hi Phil, thanks a lot for your effort and valuable input. I am having a look at STIG for VW in the hope that I can set up a common repository for the VW and Pharo version. Though, the next days I won't work on the port, because I am quite busy at the moment. Tell me how it goes for you.

Re: [Pharo-users] Bloc/Brick/Spec

--- Begin Message --- Hi Glenn, does this mean, that in the future we can build GTK applications via Bloc/Brick/Spec? Best regards, Marc 2017-06-08 14:46 GMT+02:00 Glenn Cavarlé : > Hi all, > As well described by Peter, Bloc is a low level graphics library which > mainly manages multi-windowin

Re: [Pharo-users] Wiring objects, IoC and Service Locator

Also realize the Smalltalk image is a container... No need for fancy XML externalization because you can do that with code. I have an app where I wire all kinds of things together in a configuration file which is Smalltalk code and I just compile a method like "wireEverything" that as source has

Re: [Pharo-users] Bloc/Brick/Spec

Hi all, As well described by Peter, Bloc is a low level graphics library which mainly manages multi-windowing (Morphic, SDL, Gtk soon), user interaction (events) and drawing (using Sparta). Brick is a widget framework on top of Bloc (button, inputField, ...) and Spec is a "multi-backend" UI Build

Re: [Pharo-users] Wiring objects, IoC and Service Locator

> It seems to be broken. Here is an archived version. http://archive.li/GCbEY#selection-755.0-755.38 -- View this message in context: http://forum.world.st/Wiring-objects-IoC-and-Service-Locator-tp4949280p4950480.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] No need to move to Application folder for Pharo 6 32 and 64 bit versions

On Thu, Jun 8, 2017 at 5:59 PM, Dimitris Chloupis wrote: > Nope the whole thing is a standalone, everything is included in the ".app" > folder, I use no external image or sources . Is just the typical mac app > which is a folder masquerading as a single application executable. > > This is not the

Re: [Pharo-users] Wiring objects, IoC and Service Locator

Thanks for the links Attila, do you have an alternative one to the http://higherorderlogic.com/2011/07/is-dependency-injection-like-facebook? It seems to be broken. I also started to also think containers don't worth the effort, but I am still concerned with problems faced with hand wiring everyth

Re: [Pharo-users] No need to move to Application folder for Pharo 6 32 and 64 bit versions

Nope the whole thing is a standalone, everything is included in the ".app" folder, I use no external image or sources . Is just the typical mac app which is a folder masquerading as a single application executable. This is not the first time, in the past also some people reported this problem, I a

Re: [Pharo-users] Traits, method flatten

2017-06-08 6:00 GMT+02:00 Sean P. DeNigris : > HilaireFernandes wrote > > I made another attempt to > > persist this time with filetree://. The net result is the same, the > > Traits logic is lost in the classes using the Traits: all traits methods > > are duplicated !! > > I just got burned by th

Re: [Pharo-users] No need to move to Application folder for Pharo 6 32 and 64 bit versions

Hi, The whole “path randomisation” feature of macOS is very odd.. what they do is to set an extended attribute to enable tranlocation (copy the whole app to a random path, start it there). This seems to be enabled when you look at a mounted .dmg file *and* when you uncompress a .zip. The flag

Re: [Pharo-users] [Pharo-dev] PharoDays17 Slides and some Videos

> On 7 Jun 2017, at 20:08, Ben Coman wrote: > > > > On Wed, Jun 7, 2017 at 10:24 PM, Marcus Denker > wrote: > Hi, > > I have uploaded the Slides and Videos of PharoDays2017. Slides are complete > (minus those > talks that were due demos). For the Videos we hav

[Pharo-users] No need to move to Application folder for Pharo 6 32 and 64 bit versions

I have latest macos sierra , dowload , opened and saved image for both pharo 6 (32 and 64 bit) and I see no problem doing that from the dowload folder without moving the apps to the Application folder. Am I missing something here ? Because when I dowloaded them there was a warning dialog that said

Re: [Pharo-users] Some Metacello issue

> On 08 Jun 2017, at 09:36, Diego Lont wrote: > > Hi all, > > To keep the common projects in smalltalkhub stable, we agreed that those > should use symbolic versions like release3 // release3.5 etc. This way we can > add bug fixes and avoiding loading of different versions through different

Re: [Pharo-users] Some Metacello issue

Hi all, To keep the common projects in smalltalkhub stable, we agreed that those should use symbolic versions like release3 // release3.5 etc. This way we can add bug fixes and avoiding loading of different versions through different projects. But I might have done something stupid to the confi

Re: [Pharo-users] About patterns, UML and documentation

> > with the tool and layout and stuff rather than concentrate on what is Well there are tools such as PlantUML that generate it for you, you can provide some hints, but generally it tends to be good enough to not be worried about layout. I have a Pharo -> PlantUML generator for class, object,