Re: [Pharo-users] Is there a project Label for packages

2018-08-14 Thread Alidra Abdelghani via Pharo-users 
--- Begin Message ---
Thanks a lot guys for your help.

Cheers
Abdelghani

> On 12 Aug 2018, at 10:50 am, Peter Uhnák  wrote:
> 
> BaselineOf/ConfigurationOf is the only place that contains this information, 
> e.g.
> 
> (BaselineOfCalypso project version packages collect: #name) asSet
> 
> Peter
> 
> On Sat, Aug 11, 2018 at 7:41 PM, Eric Gade  > wrote:
> Unless I'm mistaken, the `BaselineOfXXX` is, in part, a description of all 
> the packages used by a given project.
> 
> On Sat, Aug 11, 2018 at 1:18 PM, Alidra Abdelghani via Pharo-users 
> mailto:pharo-users@lists.pharo.org>> wrote:
> 
> 
> -- Forwarded message --
> From: Alidra Abdelghani mailto:alidran...@yahoo.fr>>
> To: pharo-users@lists.pharo.org 
> Cc: 
> Bcc: 
> Date: Sat, 11 Aug 2018 18:18:17 +0100
> Subject: Is there a project Label for packages
> Hi,
> 
> I would like to filter Packages according to the project they have been 
> developed in (For instance, the Roassal packages, the Seaside packages, the 
> Moose packages,…)
> 
> 
> So I am wondering if there is any way to question a package about the 
> project(s) it belong to?
> If not in Pharo, maybe there such a thing in Famix?
> If not, is there a way to reach this information (a repo, a web site, ….)
> NB.
> I could use the prefix of the name of the package, but this does not seem to 
> be always accurate (for the Pharo project for instance)
> 
> Thanks a lot in advance
> Abdelghani
> 
> 
> 
> 
> 
> 
> -- 
> Eric
> 

Dr. Abdelghani Alidra 
Enseignant-chercheur
Université 20 août 1955
SKIKDA-ALGÉRIE 
Mob:+ 213 550 453 391

--- End Message ---

[Pharo-users] XML Writer not pretty printing

2018-08-14 Thread Peter Uhnak 
Hi,

I am trying to output a pretty printed document, but it seems that the
configuration is being ignored

doc := '

  

' parseXML.

String << [ :stream |
doc
printOn: stream
beforeWritingDo: [ :writer |
writer
enablePrettyPrinting;
enablePlatformSpecificLineBreak.
writer formatter indentString: '  '. ] ]


produces

 "'

  

'"

I thought that maybe #preservesIgnorableWhitespace: has something to do
with it, but whether it is true or false, the output is not pretty printed
(not to mention, that pretty printing should ignore any preserved
whitespaces anyway).

Is this a bug? Should I print it in a different way?

Thanks,
Peter

Re: [Pharo-users] XML Writer not pretty printing

2018-08-14 Thread Carlo 
Hi Peter

It seems that #preservesIgnorableWhitespace: is only adhered to "...When 
validation is enabled and a DTD with element declarations is present..." (See 
comment in SAX2ContentHandler>>ignorableWhitespace:) The actual parsing code is 
in SAXParserDriver>>handleWhitespace:

What you could do is use #removeAllFormattingNodes but your-mileage-may-vary...

parser := XMLDOMParser
on:'

  

'.

(parser parseDocument)
removeAllFormattingNodes;
prettyPrinted.

Regards
Carlo

On 14 Aug 2018, at 13:08, Peter Uhnak  wrote:

Hi,

I am trying to output a pretty printed document, but it seems that the 
configuration is being ignored

doc := '

  

' parseXML.

String << [ :stream |
doc 
printOn: stream
beforeWritingDo: [ :writer | 
writer
enablePrettyPrinting;
enablePlatformSpecificLineBreak.
writer formatter indentString: '  '. ] ]


produces

 "'

  

'"

I thought that maybe #preservesIgnorableWhitespace: has something to do with 
it, but whether it is true or false, the output is not pretty printed (not to 
mention, that pretty printing should ignore any preserved whitespaces anyway).

Is this a bug? Should I print it in a different way?

Thanks,
Peter

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

2018-08-14 Thread H. Hirzel 
P.S. I see that the Metacello script installs a lot in one go.

I might be easier to identify the problem if the installation can be
done in steps, i.e. several load scripts in sequence.

On 8/15/18, H. Hirzel  wrote:
> Hello Jesús Marí and others
>
> Thank you for the updated Metacello script. This brings some steps forward.
>
>
> The use case:
>
> 1. I started with http://pharo.org/web/download
>
> curl https://get.pharo.org/64/ | bash
>
>
> 2. Open pharo with
> ./pharo-ui
>
>
> 3. JupyterTalk installation
> I pasted
>
>
>Metacello new
> baseline: 'JupyterTalk';
> repository: 'github://jmari/JupyterTalk:master/repository';
> load:'all'
>
> 4. A problem came up, see screen shot JupyterTalk_Installation
> I hit 'proceed'
>
>
> 5. I wanted to save the image and did 'save and quit'. Then an
> additional error popped up
> See screen shot 'Error_after_choosing_save_and_quit'
>
> Help is appreciated.
>
> Regards
> Hannes
>
>
>
>
>
> On 8/13/18, Jesús Marí  wrote:
>> That worked for me
>>
>> Metacello new
>>  baseline: 'JupyterTalk';
>>  repository: 'github://jmari/JupyterTalk:master/repository';
>>  load:'all'
>>
>> I will correct the github readme page.
>>
>>
>>
>>
>> --
>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>
>>
>

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

2018-08-14 Thread H. Hirzel 
Also useful would be a catalog entry.

On 8/15/18, H. Hirzel  wrote:
> P.S. I see that the Metacello script installs a lot in one go.
>
> I might be easier to identify the problem if the installation can be
> done in steps, i.e. several load scripts in sequence.
>
> On 8/15/18, H. Hirzel  wrote:
>> Hello Jesús Marí and others
>>
>> Thank you for the updated Metacello script. This brings some steps
>> forward.
>>
>>
>> The use case:
>>
>> 1. I started with http://pharo.org/web/download
>>
>> curl https://get.pharo.org/64/ | bash
>>
>>
>> 2. Open pharo with
>> ./pharo-ui
>>
>>
>> 3. JupyterTalk installation
>> I pasted
>>
>>
>>Metacello new
>> baseline: 'JupyterTalk';
>> repository: 'github://jmari/JupyterTalk:master/repository';
>> load:'all'
>>
>> 4. A problem came up, see screen shot JupyterTalk_Installation
>> I hit 'proceed'
>>
>>
>> 5. I wanted to save the image and did 'save and quit'. Then an
>> additional error popped up
>> See screen shot 'Error_after_choosing_save_and_quit'
>>
>> Help is appreciated.
>>
>> Regards
>> Hannes
>>
>>
>>
>>
>>
>> On 8/13/18, Jesús Marí  wrote:
>>> That worked for me
>>>
>>> Metacello new
>>> baseline: 'JupyterTalk';
>>> repository: 'github://jmari/JupyterTalk:master/repository';
>>> load:'all'
>>>
>>> I will correct the github readme page.
>>>
>>>
>>>
>>>
>>> --
>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>>
>>>
>>
>