Cyril Ferlicot
wrote:
>
> I'm not a big fan of limiting the language on composition because the
> choice between composition and inheritance should be conceptual and
> not technical.
>
> I read in an article this way to choose between inheritance and composition:
An alternative (Smalltalk) vie
Hi,
Where is it possible to get a working OS X VM for Pharo7 ?
Accoring to my test, the VM linked at http://pharo.org/download as error
with a libgit plugin (same for linux VM btw)
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
Hi Hilaire,
On Thu, 14 Feb 2019 at 09:09, Hilaire wrote:
>
> Hi,
>
> Where is it possible to get a working OS X VM for Pharo7 ?
>
> Accoring to my test, the VM linked at http://pharo.org/download as error
> with a libgit plugin (same for linux VM btw)
I've been using both the stable and latest V
I downloaded again the 32bits linux VM, and I can't reproduce this error
with a stock P7 image.
Now I am still wondering with os x vm because I tried two days ago on a
computer at school, and get this libgit plugin error, same error
mentionned as well by a Pharoer.
Hilaire
Le 14/02/2019 à 09:14
Good morning,
Last week I had a problem with a conflicting version of libgit installed
by brew. In my case, brew had updated the version making it incompatible
with the bindings in FFi.
Could you check the execution of:
DYLD_PRINT_LIBRARIES_POST_LAUNCH=1
./pharo-vm/Pharo.app/Contents/MacOS/Pharo
Hopefully I may have access to a mac tomorrow to test your request, or
it will be in 10 days.
On the other hand, is not libgit integrated in the VM, so I don't
understand how it can be related to system update? Or is libgit a
binding to a system git or something like that?
Thanks
PS: I did an up
Haha, I didn't pay enough attention to see the difference between
#workingDirectory and #home.
Thanks for the clarification !
BTW, what I also wanted to add is that independent of the precise type you can
always use the instances to do your job (open it, move it, etc ...).
> On 14 Feb 2019, at
On Thu., 14 Feb. 2019, 10:07 Hilaire, wrote:
> Hopefully I may have access to a mac tomorrow to test your request, or
> it will be in 10 days.
>
> On the other hand, is not libgit integrated in the VM, so I don't
> understand how it can be related to system update? Or is libgit a
> binding to a s
I know what you are describing, for example cairo can be impacted.
My self questioning was: Does the VM rely on the host git library or is
the one shipped with the vm sufficient?
Best,
Hilaire
Le 14/02/2019 à 10:33, Alistair Grant a écrit :
> On Linux it is almost always:
>
> - A library isn't
Hi
How to turn off the quality assitant in the calypso browser?
I don't find anymore the option in the settings browser.
Hilaire
--
Dr. Geo
http://drgeo.eu
Hi Sven,
Your second example expression fails for 'workingDirectory':
FileLocator workingDirectory resolve pathSegments
==> #()
It works fine for FileLocator home but not for FileLocator workingDirectory
.
Your first expression will produce the desired result, if en*source*lled
with syntactiman
> On 14 Feb 2019, at 13:55, David Richards
> wrote:
>
> Hi Sven,
>
> Your second example expression fails for 'workingDirectory':
>
> FileLocator workingDirectory resolve pathSegments
> ==> #()
>
> It works fine for FileLocator home but not for FileLocator workingDirectory .
>
> Your firs
I’m trying to understand how RPackage and RPackageTag work in Pharo7? It seems
different than Pharo6 at least with Nautilus (vs Calypso) - as previously the
Nautilus UI gave me the RPacakgeTag, and I could just work with that. Calypso
doesn’t seem to give me the tag object, but if I have a known
Actually - I’ve realised that Calypso can give me the tag name from its context
- (aToolContext lastSelectedClassGroup).
However it does highlight a very strange package/tag design. Are you not
supposed to be easily able to derive RPacakgeTags?
Tim
> On 14 Feb 2019, at 13:19, Tim Mackinnon wr
Hi again,
> On 10 Jan 2019, at 16:31, Sven Van Caekenberghe wrote:
>
> Hi,
>
> What is the status of XML Support's move to GitHub ?
> Many people were pro, has anything been done ?
> It would be very nice.
>
> Sven
I did https://github.com/svenvc/XML-Support-Pharo as a direct copy of the code
Perfect.
Many thanks.
On Thu, 14 Feb 2019 at 05:14, Sven Van Caekenberghe wrote:
>
>
> > On 14 Feb 2019, at 13:55, David Richards
> wrote:
> >
> > Hi Sven,
> >
> > Your second example expression fails for 'workingDirectory':
> >
> > FileLocator workingDirectory resolve pathSegments
> > ==> #()
Hi Sven,
Can we use filetree/cypress for this for now? IF the intention is for your
copy to become the canonical github one at least. Squeak and GemStone
don't yet have tonel and the smalltalkhub/PharoExtras repo is where code is
currently loaded from for those platforms.
Thanks for giving
Paul,
Like I said, this is just a simple first POC for Pharo only.
Of course, the real version should probably not use Tonel, and include the
history.
I just do not want to take this on, I have already too many public things to
support.
It is however my opinion that supporting multiple archit
Hi,
but Tonel allows to use the package also on Windows platform as Tonel is more
compact. Otherwise we will run into long filename git
trouble again. This would limit it's use.
A filetree/cypress might make sense for other dialects - but due to the above
would it be possibly to have these form
> On 14 Feb 2019, at 19:02, Torsten Bergmann wrote:
>
> Hi,
>
> but Tonel allows to use the package also on Windows platform as Tonel is more
> compact. Otherwise we will run into long filename git
> trouble again. This would limit it's use.
>
> A filetree/cypress might make sense for other
Isn’t tonel an open format? Would this not encourage other dialects to adopt it
as well? The sooner the better?
We know that filetree wasn’t really a great idea as a format (as Windows issues
show).
I’d say in this case move to it and let’s move forward. Hopefully all together.
Tim
Sent from
Thank you Sven.
The timing is perfect.
https://blog.digitalocean.com/announcing-managed-databases-for-postgresql/
:)
Esteban A. Maringolo
El mar., 12 feb. 2019 a las 11:23, Sven Van Caekenberghe
() escribió:
>
> Hi,
>
> There is a new release of P3, the modern, lean and mean PostgreSQL client
> On 14 Feb 2019, at 22:44, Esteban Maringolo wrote:
>
> Thank you Sven.
>
> The timing is perfect.
> https://blog.digitalocean.com/announcing-managed-databases-for-postgresql/
>
> :)
Interesting & cool; thanks for sharing.
> Esteban A. Maringolo
>
>
> El mar., 12 feb. 2019 a las 11:23,
23 matches
Mail list logo
