Smalltalk › Pharo › Pharo Smalltalk Developers

install GitFileTree from catalog --> missing class

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

11 messages Options

EstebanLM

install GitFileTree from catalog --> missing class

this class is not there anymore :

MCFileTreeJsonParser

(Pharo 6.0 version)

Sven Van Caekenberghe-2

Re: install GitFileTree from catalog --> missing class

STON is now (in 6.0) used as JSON parser.

> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>
> this class is not there anymore :
>
> MCFileTreeJsonParser
>
> (Pharo 6.0 version)

EstebanLM

Re: install GitFileTree from catalog --> missing class

yes, but then GitFileTree from catalog is downloading a wrong version :)

> On 03 Jun 2016, at 13:28, Sven Van Caekenberghe <[hidden email]> wrote:
>
> STON is now (in 6.0) used as JSON parser.
>
>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>>
>> this class is not there anymore :
>>
>> MCFileTreeJsonParser
>>
>> (Pharo 6.0 version)
>
>

Thierry Goubier

Re: install GitFileTree from catalog --> missing class

2016-06-03 13:38 GMT+02:00 Esteban Lorenzano <[hidden email]>:

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 <[hidden email]> wrote:
>
> STON is now (in 6.0) used as JSON parser.
>
>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>>
>> this class is not there anymore :
>>
>> MCFileTreeJsonParser
>>
>> (Pharo 6.0 version)
>
>

Thierry Goubier

Re: install GitFileTree from catalog --> missing class

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 new

baseline: '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:

Regards,

Thierry

2016-06-03 13:50 GMT+02:00 Thierry Goubier <[hidden email]>:

2016-06-03 13:38 GMT+02:00 Esteban Lorenzano <[hidden email]>:
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 <[hidden email]> wrote:
>
> STON is now (in 6.0) used as JSON parser.
>
>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>>
>> this class is not there anymore :
>>
>> MCFileTreeJsonParser
>>
>> (Pharo 6.0 version)
>
>

Dale Henrichs-3

Re: install GitFileTree from catalog --> missing class

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 new

baseline: '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:

Regards,

Thierry

2016-06-03 13:50 GMT+02:00 Thierry Goubier <[hidden email]>:

2016-06-03 13:38 GMT+02:00 Esteban Lorenzano <[hidden email]>:

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 <[hidden email]> wrote:
>
> STON is now (in 6.0) used as JSON parser.
>
>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>>
>> this class is not there anymore :
>>
>> MCFileTreeJsonParser
>>
>> (Pharo 6.0 version)
>
>

EstebanLM

Re: install GitFileTree from catalog --> missing class

https://pharo.fogbugz.com/f/cases/resolve/18400

On 03 Jun 2016, at 15:18, Dale Henrichs <[hidden email]> 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 new

baseline: 'FileTree';

repository: '<a href="github://dalehenrich/filetree:pharo6.0_dev/repository'" class="">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 <[hidden email]>:

2016-06-03 13:38 GMT+02:00 Esteban Lorenzano <[hidden email][hidden email]>:

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 <[hidden email]> wrote:
>
> STON is now (in 6.0) used as JSON parser.
>
>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>>
>> this class is not there anymore :
>>
>> MCFileTreeJsonParser
>>
>> (Pharo 6.0 version)
>
>

Thierry Goubier

Re: install GitFileTree from catalog --> missing class

Thanks.

2016-06-03 15:32 GMT+02:00 Esteban Lorenzano <[hidden email]>:

https://pharo.fogbugz.com/f/cases/resolve/18400

Would that impact configurations which have only a #pharo5.x or lower version?

Thierry

:)

On 03 Jun 2016, at 15:18, Dale Henrichs <[hidden email]> 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 new

baseline: '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 <[hidden email]>:

2016-06-03 13:38 GMT+02:00 Esteban Lorenzano <[hidden email][hidden email]>:

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 <[hidden email]> wrote:
>
> STON is now (in 6.0) used as JSON parser.
>
>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>>
>> this class is not there anymore :
>>
>> MCFileTreeJsonParser
>>
>> (Pharo 6.0 version)
>
>

EstebanLM

Re: install GitFileTree from catalog --> missing class

not for now

On 03 Jun 2016, at 16:03, Thierry Goubier <[hidden email]> wrote:

Thanks.

2016-06-03 15:32 GMT+02:00 Esteban Lorenzano <[hidden email]>:
https://pharo.fogbugz.com/f/cases/resolve/18400

Would that impact configurations which have only a #pharo5.x or lower version?

Thierry

:)

On 03 Jun 2016, at 15:18, Dale Henrichs <[hidden email]> 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 new

baseline: '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 <[hidden email]>:

2016-06-03 13:38 GMT+02:00 Esteban Lorenzano <[hidden email][hidden email]>:

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 <[hidden email]> wrote:
>
> STON is now (in 6.0) used as JSON parser.
>
>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>>
>> this class is not there anymore :
>>
>> MCFileTreeJsonParser
>>
>> (Pharo 6.0 version)
>
>

stepharo

Re: install GitFileTree from catalog --> missing class

In reply to this post by EstebanLM

This is why we need to have metadata of loaded packages inside the image.

Because right now the maintainer of the package is forced to remove
information from his configuration :(

Been there with RB.

Setf

Le 3/6/16 à 13:38, Esteban Lorenzano a écrit :

> yes, but then GitFileTree from catalog is downloading a wrong version :)
>
>> On 03 Jun 2016, at 13:28, Sven Van Caekenberghe <[hidden email]> wrote:
>>
>> STON is now (in 6.0) used as JSON parser.
>>
>>> On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:
>>>
>>> this class is not there anymore :
>>>
>>> MCFileTreeJsonParser
>>>
>>> (Pharo 6.0 version)
>>
>
>

Damien Pollet

Re: install GitFileTree from catalog --> missing class

Is it normal that a clean 60178 image is still missing the class after loading GitFileTree from the catalog?

On 4 June 2016 at 09:37, stepharo <[hidden email]> wrote:

This is why we need to have metadata of loaded packages inside the image.

Because right now the maintainer of the package is forced to remove information from his configuration :(

Been there with RB.

Setf

Le 3/6/16 à 13:38, Esteban Lorenzano a écrit :

yes, but then GitFileTree from catalog is downloading a wrong version :)

On 03 Jun 2016, at 13:28, Sven Van Caekenberghe <[hidden email]> wrote:

STON is now (in 6.0) used as JSON parser.

On 03 Jun 2016, at 13:24, Esteban Lorenzano <[hidden email]> wrote:

this class is not there anymore :

MCFileTreeJsonParser

(Pharo 6.0 version)

Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet