Re: [Pharo-users] Smalltalk Security Landscape - survey for ESUG 2018

[Ben Coman]

On 14 August 2018 at 01:50, Jerry Kott  wrote:

> Dear Smalltalkers and friends,
>
> I am planning to have a presentation titled ‘Smalltalk Security Landscape’
> at this year’s ESUG conference. In my presentation I hope to increase
> cybersecurity awareness within the Smalltalk community and help shape the
> evolution of the language and its ecosystem.
>
> I have put together a survey to help me research the topic. I ask for your
> kind help to get a picture of where Smalltalk stands in the area of
> cybersecurity. The survey is completely anonymous, and should take less
> than 15 minutes to complete. I appreciate your time and participation.
>
> If you are in a management role, I would like your help by forwarding this
> to your team members to help reach the broad Smalltalk community.
>
> Here is a link: https://www.surveymonkey.com/r/esug2018
>
> Thank you for your help, and hope to see you in Cagliari!
>
> *Jerry Kott*
> This message has been digitally signed.
> PGP Fingerprint:
> A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5
>
>
>
>
I was going to say it is not clear which way the scale runs in "Rank
Smalltalk dialect(s) you use"
but I see its coded in as a constraint.

I rather liked your term "Citizen Developer"

cheers -ben

[Pharo-users] Smalltalk Security Landscape - survey for ESUG 2018

[Jerry Kott]

Dear Smalltalkers and friends,

I am planning to have a presentation titled ‘Smalltalk Security Landscape’ at 
this year’s ESUG conference. In my presentation I hope to increase 
cybersecurity awareness within the Smalltalk community and help shape the 
evolution of the language and its ecosystem.

I have put together a survey to help me research the topic. I ask for your kind 
help to get a picture of where Smalltalk stands in the area of cybersecurity. 
The survey is completely anonymous, and should take less than 15 minutes to 
complete. I appreciate your time and participation.

If you are in a management role, I would like your help by forwarding this to 
your team members to help reach the broad Smalltalk community.

Here is a link: https://www.surveymonkey.com/r/esug2018 


Thank you for your help, and hope to see you in Cagliari!

Jerry Kott
This message has been digitally signed.
PGP Fingerprint:
A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5





signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [Pharo-users] code completion - order classes suggested by match then package reference count?

[Sean P. DeNigris]

Paul DeBruicker wrote
> I'm using the default E completion if it matters.  

I thought this was the very issue o-completion solves



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

[Pharo-users] code completion - order classes suggested by match then package reference count?

[PAUL DEBRUICKER]

Hi - 

When I want to use an OrderedCollection in Pharo 6.1 the code completion has me 
write "Ordere" before it is the one selected.  If I have ever used an 
OrderPreservingDictionary (which comes up first) I've forgotten, but daily use 
OrderedCollections.  

Is there a way now to change the sort order of classes so that they sort by # 
of uses/references in the image or package I'm developing in? 

I'm using the default E completion if it matters.  

Thanks

Paul

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

[Jesús Marí]

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

[Jesús Marí]

I found it...you just have to add the subdirectory to the repository path

Metacello new 
baseline: 'JupyterTalk';
repository: 'github://jmari/JupyterTalk/repository/';
load:#all





--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

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

[Jesús Marí]

Hi Hannes,
I did not find a nice way to solve the problem but you will be able to load
jupytertalk following these simple steps:
- Try to load it executing 
Metacello new 
baseline: 'JupyterTalk';
repository: 'github://jmari/JupyterTalk';
load:'all'
- It will fail...open Iceberg, there must be a new repository "JupyterTalk"
in.
- Edit the repository (cmd+E) and add "repository" to the code subdirectory
field.
- Try to execute this again,
Metacello new 
baseline: 'JupyterTalk';
repository: 'github://jmari/JupyterTalk';
load:'all'
--
Befor installing Jupytertalk, you need ZeroMQ and Jupyter installed in your
system and you must create a the folder
'/usr/local/share/jupyter/kernels/pharo'.  and a file   'kernel.json' with the
contents like that...

'{
  "argv": [
"/Applications/Pharo6.1-64_ZeroMQ.app/Contents/MacOS/Pharo",
   
"/Applications/Pharo6.1-64_ZeroMQ.app/Contents/Resources/Pharo6.1-64.image",
"ipharo",
"{connection_file}"
  ],
  "display_name": "Pharo Smalltalk",
  "language": "smalltalk"
}' 
 
feel free to ask more questions, I'll be glad to help!



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Deprecation rewrite introduces infinite recursion… how to prevent that?

[Damien Pollet]

Turns out it was pretty easy to implement:
https://github.com/pharo-project/pharo/pull/1683

On Sat, 11 Aug 2018 at 15:59, Damien Pollet  wrote:

> I have a double-dispatch chain:
> x generic: y → y firstDispatch: x → x secondDispatchFromY: y
>
> However this has been added after the fact, so there are direct uses of
> the secondDispatchFromY:  layer, which I'd like to deprecate/rewrite to use
> the generic: one. But if I do so, the intermediate firstDispatch: gets
> rewritten in the process, and this results in an infinite recursion.
>
> Is there a way to formulate the rewrite rule to avoid that?
>
> I could make a whole new set of secondDispatchFromYbis: methods, change
> the firstDispatch: ones to use those, and then the rewrite would be ok, but
> it seems like a lot of noise in the code for a small deprecation…
>
> Thinking of it, this is not really a deprecation, more like an advice on
> proper use…
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet
>


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

Re: [Pharo-users] mustache bug?

[Norbert Hartl]

Hmmm. To easy for me to figure out :) 

https://github.com/noha/mustache/issues/2 


Norbert

> Am 13.08.2018 um 14:06 schrieb Sven Van Caekenberghe :
> 
> 
> 
>> On 13 Aug 2018, at 13:59, Norbert Hartl  wrote:
>> 
>> Where did you read this about the parent context? Maybe I’m blind to see it. 
>> That would explain why I didn’t see it when implementing it :)
> 
> Search for parent in http://mustache.github.io/mustache.5.html
> 
> Variables
> The most basic tag type is the variable. A {{name}} tag in a basic template 
> will try to find the name key in the current context. If there is no name 
> key, the parent contexts will be checked recursively. If the top context is 
> reached and the name key is still not found, nothing will be rendered.
> 
>> Norbert
>> 
>>> Am 13.08.2018 um 10:24 schrieb Peter Uhnák :
>>> 
>>> Hi,
>>> 
>>> I'm using Mustache for Pharo, and according to mustache docs ( 
>>> https://mustache.github.io/mustache.5.html ), when a key is not found, it 
>>> should look into parents contexts.
>>> 
>>> However that does not seem to be the case:
>>> 
>>> str := '{{root}}
>>> {{#items}}
>>> {{root}}.{{name}}
>>> {{/items}}'.
>>> 
>>> data := {
>>> 'root' -> 'ROOT'.
>>> 'items' -> {
>>> { 'name' -> 'first' } asDictionary.
>>> { 'name' -> 'second' } asDictionary.
>>> }
>>> } asDictionary.
>>> 
>>> (MustacheTemplate on: str) value: data.
>>> 
>>> I should get "ROOT.first", etc., but instead I get ".first", ".second".
>>> 
>>> Thanks,
>>> Peter
>>> 
>> 
> 
> 

Re: [Pharo-users] mustache bug?

[Sven Van Caekenberghe]

> On 13 Aug 2018, at 13:59, Norbert Hartl  wrote:
> 
> Where did you read this about the parent context? Maybe I’m blind to see it. 
> That would explain why I didn’t see it when implementing it :)

Search for parent in http://mustache.github.io/mustache.5.html

Variables
The most basic tag type is the variable. A {{name}} tag in a basic template 
will try to find the name key in the current context. If there is no name key, 
the parent contexts will be checked recursively. If the top context is reached 
and the name key is still not found, nothing will be rendered.

> Norbert
> 
>> Am 13.08.2018 um 10:24 schrieb Peter Uhnák :
>> 
>> Hi,
>> 
>> I'm using Mustache for Pharo, and according to mustache docs ( 
>> https://mustache.github.io/mustache.5.html ), when a key is not found, it 
>> should look into parents contexts.
>> 
>> However that does not seem to be the case:
>> 
>> str := '{{root}}
>> {{#items}}
>> {{root}}.{{name}}
>> {{/items}}'.
>> 
>> data := {
>>  'root' -> 'ROOT'.
>>  'items' -> {
>>  { 'name' -> 'first' } asDictionary.
>>  { 'name' -> 'second' } asDictionary.
>>  }
>> } asDictionary.
>> 
>> (MustacheTemplate on: str) value: data.
>> 
>> I should get "ROOT.first", etc., but instead I get ".first", ".second".
>> 
>> Thanks,
>> Peter
>> 
> 

Re: [Pharo-users] mustache bug?

[Norbert Hartl]

Where did you read this about the parent context? Maybe I’m blind to see it. 
That would explain why I didn’t see it when implementing it :)

Norbert

> Am 13.08.2018 um 10:24 schrieb Peter Uhnák :
> 
> Hi,
> 
> I'm using Mustache for Pharo, and according to mustache docs ( 
> https://mustache.github.io/mustache.5.html 
>  ), when a key is not found, it 
> should look into parents contexts.
> 
> However that does not seem to be the case:
> 
> str := '{{root}}
> {{#items}}
> {{root}}.{{name}}
> {{/items}}'.
> 
> data := {
>   'root' -> 'ROOT'.
>   'items' -> {
>   { 'name' -> 'first' } asDictionary.
>   { 'name' -> 'second' } asDictionary.
>   }
> } asDictionary.
> 
> (MustacheTemplate on: str) value: data.
> 
> I should get "ROOT.first", etc., but instead I get ".first", ".second".
> 
> Thanks,
> Peter
> 

[Pharo-users] mustache bug?

[Peter Uhnák]

Hi,

I'm using Mustache for Pharo, and according to mustache docs (
https://mustache.github.io/mustache.5.html ), when a key is not found, it
should look into parents contexts.

However that does not seem to be the case:

str := '{{root}}
{{#items}}
{{root}}.{{name}}
{{/items}}'.

data := {
'root' -> 'ROOT'.
'items' -> {
{ 'name' -> 'first' } asDictionary.
{ 'name' -> 'second' } asDictionary.
}
} asDictionary.

(MustacheTemplate on: str) value: data.

I should get "ROOT.first", etc., but instead I get ".first", ".second".

Thanks,
Peter