On 03 Jun 2016, at 16:03, Thierry Goubier <thierry.goubier@gmail.com> wrote:Thanks.2016-06-03 15:32 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:Would that impact configurations which have only a #pharo5.x or lower version?Thierry:)On 03 Jun 2016, at 15:18, Dale Henrichs <dale.henrichs@gemtalksystems.com> wrote:Take a look at SmalltalkImage>metacelloPlatformAttributes ... that's where Metacello picks up the platform attributes.
Dale
On 6/3/16 5:28 AM, Thierry Goubier wrote:
Done, but now I have a problem.
Pharo6 is not identified as #pharo6 in the platform, so I can't trigger loading a dedicated version of GitFileTree for Pharo 6.
In short, I have a GitFileTree for Pharo 6, but then you'll have to write:
Metacello newbaseline: 'FileTree';repository: 'github://dalehenrich/filetree:pharo6.0_dev/repository';load: 'Git'.
Could someone ensure that Pharo 6 identifies as #pharo6 at one point? For now, MetacelloToolBox>>#platformAttributes answer this:
<Mail Attachment.png>
Regards,
Thierry
2016-06-03 13:50 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:
2016-06-03 13:38 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
yes, but then GitFileTree from catalog is downloading a wrong version :)
I'll update and see if this change was pushed upstream (in the FileTree repository).
Thierry
> On 03 Jun 2016, at 13:28, Sven Van Caekenberghe <sven@stfx.eu> wrote:
>
> STON is now (in 6.0) used as JSON parser.
>
>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <estebanlm@gmail.com> wrote:
>>
>> this class is not there anymore :
>>
>> MCFileTreeJsonParser
>>
>> (Pharo 6.0 version)
>
>