If this does become of interest to anyone, I had a quick look at the workflow
landscape in Pharo and found it rather unfathomable - Netsyle seems very
comprehensive but complicated and lacking syntactic sugar to make it easy to
just pick up and run with. It’s reified up the hilt, so simple stuff
--- Begin Message ---
Hi Guys,
The evaluation of
Metacello new
repository: 'github://svenvc/NeoJSON/repository';
baseline: 'NeoJSON';
load.
returns: Could not resolve: BaselineOfNeoJSON [BaselineOfNeoJSON] in
/Users/myName/Development/MyProject/package-cache
github://svenvc/NeoJSON:master/
When loading from Git(Hub) you have to use BaselineOf...
Installation instructions at https://github.com/svenvc/NeoJSON
> On 27 Sep 2019, at 11:54, Davide Varvello via Pharo-users
> wrote:
>
>
> From: Davide Varvello
> Subject: Could not resolve: BaselineOfNeoJSON
> Date: 27 September 2019 a
> Am 27.09.2019 um 10:10 schrieb Tim Mackinnon :
>
> If this does become of interest to anyone, I had a quick look at the workflow
> landscape in Pharo and found it rather unfathomable - Netsyle seems very
> comprehensive but complicated and lacking syntactic sugar to make it easy to
> just
--- Begin Message ---
Hi Sven,
I don't quite understand. At https://github.com/svenvc/NeoJSON it shows "to
load NeoJSON using Metacello"
Metacello new
repository: 'github://svenvc/NeoJSON/repository';
baseline: 'NeoJSON';
load.
That's the step I did and I suppose it was enough. I don't kno
Davide,
I don't know what you are doing, exactly.
If I download a fresh Pharo 7.0.4 (64bit on macOS), and I execute the expression
Metacello new
repository: 'github://svenvc/NeoJSON/repository';
baseline: 'NeoJSON';
load.
it loads as expected, with the following in the Transcript
Fetched
--- Begin Message ---
Sven,
You are right, I've just downloaded Pharo 7 and everything is fine. The
issue is showing on Pharo 5 (I'm working on it)
Davide
Sven Van Caekenberghe-2 wrote
> Davide,
>
> I don't know what you are doing, exactly.
>
> If I download a fresh Pharo 7.0.4 (64bit on macOS)
Hi Pablo,
Before doing Invoke() in COMDispatchInstance>>#dispatch, the array of
parameters for a COM method call is currently prepared under the assumption
that the parameter types reported by COM for a particular method should be
used directly, i. e. if a COM method reports VT_BSTR as its paramet
On Thu, 26 Sep 2019 at 04:27, Tim Mackinnon wrote:
>
> Anyone have any thoughts or directions to explore?
>
My contribution is very academic, and not really my field of expertise (we
evaluated a BPML/BPMN tool about 10 years ago which I think is dead now).
The conference paper from 2016 at
https
