Smalltalk › Pharo › Pharo Smalltalk Developers

Pillar configuration bug ?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

7 messages Options

EstebanLM

Pillar configuration bug ?

Hi,

I’m installing pillar like this:

pillar: spec
spec project: 'Pillar' with: [
spec
className: 'ConfigurationOfPillar';
loads: #('html exporter');
repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]

who, according to me, should give me elements to parse pillar and to export to html… but when I finish, my installation is lacking a parser.
… and PRDocumentItem class>>#parser is having an undeclared behaviour (PRPillarParserMain is not in the system).

cheers,
Esteban

Damien Cassou-2

Re: Pillar configuration bug ?

On June 1, 2016 6:31:29 PM GMT+02:00, Esteban Lorenzano <[hidden email]> wrote:

>I’m installing pillar like this:
>
>pillar: spec
> spec project: 'Pillar' with: [
> spec
> className: 'ConfigurationOfPillar';
> loads: #('html exporter');
> repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]
>
>who, according to me, should give me elements to parse pillar

I don't have the code at hand but this not what I expect : the parser is not necessary to export html, you just need a document model (which you could get through a Markdown parser for example).

>export to html… but when I finish, my installation is lacking a parser.
>
>… and PRDocumentItem class>>#parser is having an undeclared behaviour
>(PRPillarParserMain is not in the system).

This has probably been fixed by Yann already in the development version.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

EstebanLM

Re: Pillar configuration bug ?

> On 01 Jun 2016, at 20:44, Damien Cassou <[hidden email]> wrote:
>
> On June 1, 2016 6:31:29 PM GMT+02:00, Esteban Lorenzano <[hidden email]> wrote:
>> I’m installing pillar like this:
>>
>> pillar: spec
>> spec project: 'Pillar' with: [
>> spec
>> className: 'ConfigurationOfPillar';
>> loads: #('html exporter');
>> repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]
>>
>> who, according to me, should give me elements to parse pillar
>
> I don't have the code at hand but this not what I expect : the parser is not necessary to export html, you just need a document model (which you could get through a Markdown parser for example).

Without the parser you can’t do anything so I would expect the parser to be a core part.
But anyway, even agreeing with your PoV, if I load #(html exporter), then I have unreferenced pillar classes in the resulting image (PRDocumentItem class>>#parser has a strong reference… and even that method should not be there according with your statement).

but anyway, for me the important part is: what do I need to load to have the parser? there is no group “parser” in ConfigurationOfPillar.

cheers!
Esteban

>
>
>> export to html… but when I finish, my installation is lacking a parser.
>>
>> … and PRDocumentItem class>>#parser is having an undeclared behaviour
>> (PRPillarParserMain is not in the system).
>
> This has probably been fixed by Yann already in the development version.
>
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill

stepharo

Re: Pillar configuration bug ?

>> On 01 Jun 2016, at 20:44, Damien Cassou <[hidden email]> wrote:
>>
>> On June 1, 2016 6:31:29 PM GMT+02:00, Esteban Lorenzano <[hidden email]> wrote:
>>> I’m installing pillar like this:
>>>
>>> pillar: spec
>>> spec project: 'Pillar' with: [
>>> spec
>>> className: 'ConfigurationOfPillar';
>>> loads: #('html exporter');
>>> repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]
>>>
>>> who, according to me, should give me elements to parse pillar
>> I don't have the code at hand but this not what I expect : the parser is not necessary to export html, you just need a document model (which you could get through a Markdown parser for example).
> Without the parser you can’t do anything so I would expect the parser to be a core part.
> But anyway, even agreeing with your PoV, if I load #(html exporter), then I have unreferenced pillar classes in the resulting image (PRDocumentItem class>>#parser has a strong reference… and even that method should not be there according with your statement).

Esteban this is not really true. I manupilate citezen objects and want
to export them as html and I was wondering:
should I emit pillar -> parser -> model -> html or model -> html and
this is what I will do.

>
> but anyway, for me the important part is: what do I need to load to have the parser? there is no group “parser” in ConfigurationOfPillar.
>
> cheers!
> Esteban
>
>>
>>> export to html… but when I finish, my installation is lacking a parser.
>>>
>>> … and PRDocumentItem class>>#parser is having an undeclared behaviour
>>> (PRPillarParserMain is not in the system).
>> This has probably been fixed by Yann already in the development version.
>>
>>
>> --
>> Damien Cassou
>> http://damiencassou.seasidehosting.st
>>
>> "Success is the ability to go from one failure to another without
>> losing enthusiasm." --Winston Churchill
>
>

EstebanLM

Re: Pillar configuration bug ?

On 04 Jun 2016, at 09:35, stepharo <[hidden email]> wrote:

On 01 Jun 2016, at 20:44, Damien Cassou <[hidden email]> wrote:

On June 1, 2016 6:31:29 PM GMT+02:00, Esteban Lorenzano <[hidden email]> wrote:
I’m installing pillar like this:

pillar: spec
spec project: 'Pillar' with: [
spec
className: 'ConfigurationOfPillar';
loads: #('html exporter');
repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main' ]

who, according to me, should give me elements to parse pillar
I don't have the code at hand but this not what I expect : the parser is not necessary to export html, you just need a document model (which you could get through a Markdown parser for example).
Without the parser you can’t do anything so I would expect the parser to be a core part.
But anyway, even agreeing with your PoV, if I load #(html exporter), then I have unreferenced pillar classes in the resulting image (PRDocumentItem class>>#parser has a strong reference… and even that method should not be there according with your statement).

Esteban this is not really true. I manupilate citezen objects and want to export them as html and I was wondering:
should I emit pillar -> parser -> model -> html or model -> html and this is what I will do.

whatever… my point is that if it is not intended to be there, I should not see a strong (and undefined) reference in what I inject to the system.

and my other point is that I still need a pointer to “what I need to load to have the parser”. Some group like “parser”, for example. Right now the only way I have to load it would be to load all… and that’s not the purpose of having groups, I think (no point on having them if I need to load all anyway), so there is a problem with the configuration.

Esteban

but anyway, for me the important part is: what do I need to load to have the parser? there is no group “parser” in ConfigurationOfPillar.

cheers!
Esteban

export to html… but when I finish, my installation is lacking a parser.

… and PRDocumentItem class>>#parser is having an undeclared behaviour
(PRPillarParserMain is not in the system).
This has probably been fixed by Yann already in the development version.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

CyrilFerlicot

Re: Pillar configuration bug ?

In reply to this post by EstebanLM

Le 03/06/2016 14:51, Esteban Lorenzano a écrit :

> Without the parser you can’t do anything so I would expect the parser to be a core part.
> But anyway, even agreeing with your PoV, if I load #(html exporter), then I have unreferenced pillar classes in the resulting image (PRDocumentItem class>>#parser has a strong reference… and even that method should not be there according with your statement).
>
> but anyway, for me the important part is: what do I need to load to have the parser? there is no group “parser” in ConfigurationOfPillar.
>
> cheers!
> Esteban
>
>
>

Hi Esteban,

I agree with Damien that we might want the Model and exporter without
the parser.

If the parser is missing as a group, this is a problem. The strong
reference was removed already in the development version.

I wall open an issue to let Yann and Thibault see the problem and
correct it :)

--
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France

signature.asc (836 bytes) Download Attachment

Yann Dubois

Re: Pillar configuration bug ?

I add two groups :

- parser : To load the Pillar parser

- parser tests : To testing the parser

Yann

2016-06-04 11:45 GMT+02:00 Cyril Ferlicot D. <[hidden email]>:

Le 03/06/2016 14:51, Esteban Lorenzano a écrit :
> Without the parser you can’t do anything so I would expect the parser to be a core part.
> But anyway, even agreeing with your PoV, if I load #(html exporter), then I have unreferenced pillar classes in the resulting image (PRDocumentItem class>>#parser has a strong reference… and even that method should not be there according with your statement).
>
> but anyway, for me the important part is: what do I need to load to have the parser? there is no group “parser” in ConfigurationOfPillar.
>
> cheers!
> Esteban
>
>
>

Hi Esteban,

I agree with Damien that we might want the Model and exporter without
the parser.

If the parser is missing as a group, this is a problem. The strong
reference was removed already in the development version.

I wall open an issue to let Yann and Thibault see the problem and
correct it :)

--
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France