Re: [Pharo-dev] Question about attribution under the MIT License

[Sven Van Caekenberghe]

This might be relevant too:

http://meta.stackexchange.com/questions/272956/a-new-code-license-the-mit-this-time-with-attribution-required

Somewhere in the text they say:

<<
You are also welcome to use the MIT License as it is traditionally interpreted: 
by preserving the full license with relevant fields (copyright year and 
copyright holder) completed.
>>

Literally this would not be very practical, but somehow preserving names should 
be doable.

> On 08 Jan 2016, at 19:55, monty  wrote:
> 
> This line form the text of the license suggests we should really be bundling 
> the full license text with our code, not just stating "this code is MIT" on 
> the STH project page:
> 
> "The above copyright notice and this permission notice shall be included in 
> all copies or substantial portions of the Software."
> 
> Because of this, I've started adding #catalogLicense methods to STH Configs I 
> manage that return the entire MIT license text with a copyright statement. I 
> think everyone should do the same.
> 
>> Sent: Friday, January 08, 2016 at 11:08 AM
>> From: "Sven Van Caekenberghe" 
>> To: "Pharo Development List" 
>> Subject: [Pharo-dev] Question about attribution under the MIT License
>> 
>> Hi,
>> 
>> I have a been wondering recently about attribution under the MIT License.
>> 
>> Code in Pharo and code contributed to Pharo is and should be licensed under 
>> the MIT License.
>> 
>>  https://en.wikipedia.org/wiki/MIT_License
>> 
>> Contributors sign an extra agreement. 
>> 
>>  http://files.pharo.org/media/PharoSoftwareDistributionAgreement.pdf
>> 
>> Here, contributors give a license so Pharo can include their code.
>> 
>> As I read the MIT license the original author keeps the copyright and about 
>> the only requirement is that that copyright shall be included when the code 
>> is used. The extra agreement does not transfer copyright.
>> 
>> So, all authors should be mentioned in the general Pharo MIT license.
>> 
>> The reason I was thinking about this is that many people on the list seems 
>> to be under the impression that MIT licensed code means that you can freely 
>> copy it, like most recently in the discussions about Dophin Smalltalk. I 
>> think copying MIT licensed code requires proper attribution.
>> 
>> If people copy (my, someone else's) code from Pharo to somewhere else, I 
>> want them to at least acknowledge that fact, preferably include a general 
>> Pharo (contributors) copyright, but ideally (my, their) copyright.
>> 
>> But that would also mean that Pharo has to do the same. I think we should 
>> list and update the official contributor list, including the historical list 
>> of original authors going back.
>> 
>> Am I right or wrong ?
>> 
>> How do other people feel about this ?
>> 
>> Sven
>> 
>> 
>> 
> 

Re: [Pharo-dev] [Pharo-users] [ANN] OSSubprocess first milestone

[Damien Cassou]

On January 14, 2016 7:33:56 PM GMT+01:00, Mariano Martinez Peck 
 wrote:
>Dear all,
>
>I am happy to tell you I have a first prototype of the tool for
>executing
>OS processes:
>
>https://github.com/marianopeck/OSSubprocess
>
> As I said many times, the main idea was to be as much as possible
>FFI-based, only for executing OS commands and, from my point of view, a
>better end-user API. Also, as for the first step, I had to focus on
>Linux/OSX.
>
>I would like to thank Pharo Consortium for the sponsor of this
>development
>effort. Here is the first milestone!
>
>There are many things on my to-do but I think the code is ready for
>some
>usage, testing, code review and feedback!
>
>All classes and all methods have comments and I have quite some unit
>tests.
>All tests are green in my OSX and a CentOS box.
>
>*Important: you CANNOT have OSProcess installed in the same image as
>OSSubprocess. This is because I am reusing his SIGCHLD handler and for
>the
>time being both cannot coexist.  *
>
>Keep in mind that the tool may be unstable and that MAY mean a VM
>crash. So
>use with care, mostly the first time. If all tests passes, then there
>are
>much less chances of something going bad.
>
>Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY
>influenced by a subset of the OSProcess project. There are parts which
>I
>even simply copied and adapted them (OSSPipe, OSSAttachableStream,
>OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the
>idea of ThisOSProcess representing the VM process, the child watcher,
>and
>many others). In addition, I AM STILL USING (maybe as a first step?)
>some
>of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD
>handler or the creation of pipes.
>
>In github url you have all the documentation of the project, included
>how
>to install it and use it.
>
>*Finally, if you test it in a OS different than OSX and CentOS please
>share
>with me the results (about the tests).* Tomorrow the ConfigurationOf
>should
>also appear in the Catalog of Pharo 5.0.
>
>Any feedback is appreciated.
>
>Best,

Quick feedback:

- the API seems great
- thank you very much for the documentation
- I wonder why you pass strings for stdout and stderr instead of streams
- it would be nice to be able to subclass OSSUnixProcessExitStatus for some 
commands. E.g., GitProcessExitStatus could have a method isMergeConflict
- how can I implement something like tail --follow
-- 
Damien Cassou
http://damiencassou.seasidehosting.st

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

[Pharo-dev] Powerful ARM server

[Ben Coman]

This might make a good CI server for ARM, or ARM based Pharo cloud.

http://hothardware.com/news/amd-unveils-64-bit-arm-based-opteron-a1100-soc-with-integrated-10gbe-for-the-datacenter

cheers -ben

Re: [Pharo-dev] [ANN] OSSubprocess first milestone

[David T. Lewis]

On Thu, Jan 14, 2016 at 03:33:56PM -0300, Mariano Martinez Peck wrote:
> Dear all,
> 
> I am happy to tell you I have a first prototype of the tool for executing
> OS processes:
> 
> https://github.com/marianopeck/OSSubprocess
> 
>  As I said many times, the main idea was to be as much as possible
> FFI-based, only for executing OS commands and, from my point of view, a
> better end-user API. Also, as for the first step, I had to focus on
> Linux/OSX.
> 
> I would like to thank Pharo Consortium for the sponsor of this development
> effort. Here is the first milestone!

Bravo Mariano!

Dave

Re: [Pharo-dev] [ANN] OSSubprocess first milestone

[Mariano Martinez Peck]

On Thu, Jan 14, 2016 at 4:43 PM, Dimitris Chloupis 
wrote:

> Awesome work Mariano , I love the documentation.
>
> Question : Does your library use the new FFI (Unified FFi) ?
>
>
It does use the new FFI which is in latest Pharo 5.0.
The Unified FFI as far as I understand in a simple rename of a couple of
things. I will have to update my code for it, yes, but should be trivial.

But..as far as I know, it has not been yet integrated into the image the
changes, right?



> On Thu, Jan 14, 2016 at 9:36 PM stepharo  wrote:
>
>> Thanks Mariano!
>>
>> Stef
>>
>> Le 14/1/16 19:33, Mariano Martinez Peck a écrit :
>>
>> Dear all,
>>
>> I am happy to tell you I have a first prototype of the tool for executing
>> OS processes:
>>
>> 
>> https://github.com/marianopeck/OSSubprocess
>>
>>  As I said many times, the main idea was to be as much as possible
>> FFI-based, only for executing OS commands and, from my point of view, a
>> better end-user API. Also, as for the first step, I had to focus on
>> Linux/OSX.
>>
>> I would like to thank Pharo Consortium for the sponsor of this
>> development effort. Here is the first milestone!
>>
>> There are many things on my to-do but I think the code is ready for some
>> usage, testing, code review and feedback!
>>
>> All classes and all methods have comments and I have quite some unit
>> tests. All tests are green in my OSX and a CentOS box.
>>
>> *Important: you CANNOT have OSProcess installed in the same image as
>> OSSubprocess. This is because I am reusing his SIGCHLD handler and for the
>> time being both cannot coexist.  *
>>
>> Keep in mind that the tool may be unstable and that MAY mean a VM crash.
>> So use with care, mostly the first time. If all tests passes, then there
>> are much less chances of something going bad.
>>
>> Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY
>> influenced by a subset of the OSProcess project. There are parts which I
>> even simply copied and adapted them (OSSPipe, OSSAttachableStream,
>> OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the
>> idea of ThisOSProcess representing the VM process, the child watcher, and
>> many others). In addition, I AM STILL USING (maybe as a first step?) some
>> of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD
>> handler or the creation of pipes.
>>
>> In github url you have all the documentation of the project, included how
>> to install it and use it.
>>
>> *Finally, if you test it in a OS different than OSX and CentOS please
>> share with me the results (about the tests).* Tomorrow the
>> ConfigurationOf should also appear in the Catalog of Pharo 5.0.
>>
>> Any feedback is appreciated.
>>
>> Best,
>>
>>
>>


-- 
Mariano
http://marianopeck.wordpress.com

Re: [Pharo-dev] [ANN] OSSubprocess first milestone

[Dimitris Chloupis]

Awesome work Mariano , I love the documentation.

Question : Does your library use the new FFI (Unified FFi) ?

On Thu, Jan 14, 2016 at 9:36 PM stepharo  wrote:

> Thanks Mariano!
>
> Stef
>
> Le 14/1/16 19:33, Mariano Martinez Peck a écrit :
>
> Dear all,
>
> I am happy to tell you I have a first prototype of the tool for executing
> OS processes:
>
> https://github.com/marianopeck/OSSubprocess
>
>  As I said many times, the main idea was to be as much as possible
> FFI-based, only for executing OS commands and, from my point of view, a
> better end-user API. Also, as for the first step, I had to focus on
> Linux/OSX.
>
> I would like to thank Pharo Consortium for the sponsor of this development
> effort. Here is the first milestone!
>
> There are many things on my to-do but I think the code is ready for some
> usage, testing, code review and feedback!
>
> All classes and all methods have comments and I have quite some unit
> tests. All tests are green in my OSX and a CentOS box.
>
> *Important: you CANNOT have OSProcess installed in the same image as
> OSSubprocess. This is because I am reusing his SIGCHLD handler and for the
> time being both cannot coexist.  *
>
> Keep in mind that the tool may be unstable and that MAY mean a VM crash.
> So use with care, mostly the first time. If all tests passes, then there
> are much less chances of something going bad.
>
> Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY
> influenced by a subset of the OSProcess project. There are parts which I
> even simply copied and adapted them (OSSPipe, OSSAttachableStream,
> OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the
> idea of ThisOSProcess representing the VM process, the child watcher, and
> many others). In addition, I AM STILL USING (maybe as a first step?) some
> of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD
> handler or the creation of pipes.
>
> In github url you have all the documentation of the project, included how
> to install it and use it.
>
> *Finally, if you test it in a OS different than OSX and CentOS please
> share with me the results (about the tests).* Tomorrow the
> ConfigurationOf should also appear in the Catalog of Pharo 5.0.
>
> Any feedback is appreciated.
>
> Best,
>
>
>

Re: [Pharo-dev] [ANN] OSSubprocess first milestone

[stepharo]

Thanks Mariano!

Stef

Le 14/1/16 19:33, Mariano Martinez Peck a écrit :

Dear all,

I am happy to tell you I have a first prototype of the tool for 
executing OS processes:


https://github.com/marianopeck/OSSubprocess

 As I said many times, the main idea was to be as much as possible 
FFI-based, only for executing OS commands and, from my point of view, 
a better end-user API. Also, as for the first step, I had to focus on 
Linux/OSX.


I would like to thank Pharo Consortium for the sponsor of this 
development effort. Here is the first milestone!


There are many things on my to-do but I think the code is ready for 
some usage, testing, code review and feedback!


All classes and all methods have comments and I have quite some unit 
tests. All tests are green in my OSX and a CentOS box.


*Important: you CANNOT have OSProcess installed in the same image as 
OSSubprocess. This is because I am reusing his SIGCHLD handler and for 
the time being both cannot coexist. *


Keep in mind that the tool may be unstable and that MAY mean a VM 
crash. So use with care, mostly the first time. If all tests passes, 
then there are much less chances of something going bad.


Important disclaimer: my tool (OSSubproccess from now onward) is 
HIGHLY influenced by a subset of the OSProcess project. There are 
parts which I even simply copied and adapted them (OSSPipe, 
OSSAttachableStream, OSSUnixProcessExitStatus). Other parts, I took 
them as inspiration (the idea of ThisOSProcess representing the VM 
process, the child watcher, and many others). In addition, I AM STILL 
USING (maybe as a first step?) some of the OSProcess PLUGIN (not 
OSProcess image side), such as the SIGCHLD handler or the creation of 
pipes.


In github url you have all the documentation of the project, included 
how to install it and use it.


*Finally, if you test it in a OS different than OSX and CentOS please 
share with me the results (about the tests).* Tomorrow the 
ConfigurationOf should also appear in the Catalog of Pharo 5.0.


Any feedback is appreciated.

Best,

Re: [Pharo-dev] [pharo-project/pharo-core] 0d016b: 50527

[stepharo]

Thanks guys
I will be able to start producing the new version of the videos for the 
mooc.


Stef

Le 14/1/16 19:50, GitHub a écrit :

   Branch: refs/heads/5.0
   Home:   https://github.com/pharo-project/pharo-core
   Commit: 0d016b26ee0e42f8c1960fefefde84d9f1444739
   
https://github.com/pharo-project/pharo-core/commit/0d016b26ee0e42f8c1960fefefde84d9f1444739
   Author: Jenkins Build Server 
   Date:   2016-01-14 (Thu, 14 Jan 2016)

   Changed paths:
 M 
ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/symbolic
 versions/stable_.st
 A 
ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/versions/version083_.st
 M 
Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/drawOn_.st
 R 
Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/toSelectionRow_primary_.st
 M 
Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/updating/updateExposedRows.st
 A Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/accessing 
colors/colorForSelection_.st
 M 
Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/private/selectRowIndex_event_.st
 M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/definition.st
 A 
Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/accessing/selectionColor_.st
 M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event 
handling/mouseEnter_.st
 M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event 
handling/mouseLeave_.st
 M 
Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialization/initialize.st
 M 
Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/defaultColor.st
 A 
Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/selectionColor.st
 R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/README.md
 R 
Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance 
creation/new.st
 R 
Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance 
creation/table_row_primary_.st
 R 
Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/definition.st
 R 
Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/instance/initialization/initializeTable_row_primary_.st
 M 
Nautilus.package/AbstractNautilusUI.class/instance/private/runTestsOfClass_notifying_.st
 R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50526.st
 A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50527.st
 R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50526.st
 A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50527.st
 M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

   Log Message:
   ---
   50527
17379 FastTable mouse over on highlighted item
https://pharo.fogbugz.com/f/cases/17379

17386 Nautilus test notification should show test results
https://pharo.fogbugz.com/f/cases/17386

http://files.pharo.org/image/50/50527.zip

[Pharo-dev] [pharo-project/pharo-core] 0d016b: 50527

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 0d016b26ee0e42f8c1960fefefde84d9f1444739
  
https://github.com/pharo-project/pharo-core/commit/0d016b26ee0e42f8c1960fefefde84d9f1444739
  Author: Jenkins Build Server 
  Date:   2016-01-14 (Thu, 14 Jan 2016)

  Changed paths:
M 
ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/symbolic
 versions/stable_.st
A 
ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/versions/version083_.st
M 
Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/drawOn_.st
R 
Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/toSelectionRow_primary_.st
M 
Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/updating/updateExposedRows.st
A Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/accessing 
colors/colorForSelection_.st
M 
Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/private/selectRowIndex_event_.st
M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/definition.st
A 
Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/accessing/selectionColor_.st
M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event 
handling/mouseEnter_.st
M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event 
handling/mouseLeave_.st
M 
Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialization/initialize.st
M 
Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/defaultColor.st
A 
Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/selectionColor.st
R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/README.md
R 
Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance 
creation/new.st
R 
Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance 
creation/table_row_primary_.st
R 
Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/definition.st
R 
Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/instance/initialization/initializeTable_row_primary_.st
M 
Nautilus.package/AbstractNautilusUI.class/instance/private/runTestsOfClass_notifying_.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50526.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50527.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50526.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50527.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  50527
17379 FastTable mouse over on highlighted item
https://pharo.fogbugz.com/f/cases/17379

17386 Nautilus test notification should show test results
https://pharo.fogbugz.com/f/cases/17386

http://files.pharo.org/image/50/50527.zip

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50527
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [ANN] OSSubprocess first milestone

[Mariano Martinez Peck]

Dear all,

I am happy to tell you I have a first prototype of the tool for executing
OS processes:

https://github.com/marianopeck/OSSubprocess

 As I said many times, the main idea was to be as much as possible
FFI-based, only for executing OS commands and, from my point of view, a
better end-user API. Also, as for the first step, I had to focus on
Linux/OSX.

I would like to thank Pharo Consortium for the sponsor of this development
effort. Here is the first milestone!

There are many things on my to-do but I think the code is ready for some
usage, testing, code review and feedback!

All classes and all methods have comments and I have quite some unit tests.
All tests are green in my OSX and a CentOS box.

*Important: you CANNOT have OSProcess installed in the same image as
OSSubprocess. This is because I am reusing his SIGCHLD handler and for the
time being both cannot coexist.  *

Keep in mind that the tool may be unstable and that MAY mean a VM crash. So
use with care, mostly the first time. If all tests passes, then there are
much less chances of something going bad.

Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY
influenced by a subset of the OSProcess project. There are parts which I
even simply copied and adapted them (OSSPipe, OSSAttachableStream,
OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the
idea of ThisOSProcess representing the VM process, the child watcher, and
many others). In addition, I AM STILL USING (maybe as a first step?) some
of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD
handler or the creation of pipes.

In github url you have all the documentation of the project, included how
to install it and use it.

*Finally, if you test it in a OS different than OSX and CentOS please share
with me the results (about the tests).* Tomorrow the ConfigurationOf should
also appear in the Catalog of Pharo 5.0.

Any feedback is appreciated.

Best,

-- 
Mariano
http://marianopeck.wordpress.com

[Pharo-dev] Launcher 0.2.9 opens Spur images

[Damien Cassou]

Hi list,

thanks to the awesome work of Vincent Blondeau, Stephan Eggermont and
Cyril Ferlicot, Pharo Launcher 0.2.9 can be configured to open both spur
and pre-spur Pharo images.

You can download this version from
http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher.

You can safely replace your existing Launcher installation with the new
one. Your images won't be affected and you will still be able to launch
them.

The VM coming with these builds is a pre-spur VM because Launcher is
based on Pharo 4. If you want to launch Pharo 5 spur images, you need to
separately download a Pharo 5 Spur VM from http://get.pharo.org/vm50 and
configure the location of this VM in the Launcher settings (icon at the
bottom left of the Launcher window).

What I like about this release is that I didn't do anything but changing
the version number in https://ci.inria.fr/pharo/view/all/job/Launcher :-).

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

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

Re: [Pharo-dev] Bug in protocol and method selection

[stepharo]

Hi Henrik

Did you create a bug entry so that we integrate it?

Stef

Le 14/1/16 14:57, Henrik Nergaard a écrit :

Hi Stef,

Do the error still happen if you merge:

Name: Morphic-Widgets-FastTable-HenrikNergaard.148
Author: HenrikNergaard
Time: 13 January 2016, 3:40:48.807358 pm
UUID: b807ebde-ad62-ce41-977a-e6cdce230e93
Ancestors: Morphic-Widgets-FastTable-CyrilFerlicot.147

?

Best regards,
Henrik

-Original Message-
From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Yuriy 
Tymchuk
Sent: Thursday, January 14, 2016 1:43 PM
To: Pharo Development List 
Subject: Re: [Pharo-dev] Bug in protocol and method selection

Stef,

I cannot see the issue, moreover there were no changes in QA that touch 
Nautilus.

Maybe this is because of FastTable highlighting: when you hover over a selected 
list item, it changes color to the hover color, so when you select an item you 
cannot see the you selected it because you see the tower color. This was 
already fixed, but not yes integrated.

Uko


On 14 Jan 2016, at 13:33, Yuriy Tymchuk  wrote:

I will take a look. Just to make sure: this is not the FT coloring thing, right?

Uko


On 14 Jan 2016, at 13:06, stepharo  wrote:

Hi

There is a problem in latest Pharo. I cannot select (and keep the
selection selected) of a method and method protocol.
To me it looks like QA is interferring but I do not know.
This is the kind of glitches that can kill our effort doing videos.
We have a strong deadline for producing such videos. beginning of
march but we want to get done before any help is welcome.

Stef

Re: [Pharo-dev] About LayoutFrame>>fractions:offsets:

[stepharo]

Yes fullFrame would be better.
Now we should rewrite all the senders and I do not have cycles now for that.
But if people want to do a pass go ahead.


better LayoutFrame identity :)


Well, maybe the comment could say that the 0@0 corner: 1@1 rectangle is the 
identity ;)


No because we do not want to have rectangle anymore.



That this is the identity is not obvious in fact, unless you consider what 
algorithm is used to compute layouts. I tend to think that this (0@0 corner: 
1@1) rectangle is the full area (the max area?)... not the identity of 
something.

Why not LayoutFrame fullFrame ?

Indeed, this sounds better.

Doru


Thierry

--
www.tudorgirba.com
www.feenk.com

"Be rather willing to give than demanding to get."

[Pharo-dev] ANN - Pre-compiled Pharo Spur32 VM for Debian Stable

[Jan Vrany]

Hi there, 

the Pharo Spur VM provided by the Pharo team does not run 
Debian Stable and possibly on other more conservative Linux
distributions. 

You may find a pre-compiled Spur32 Pharo VM that runs on 
Debian Stable (and possibly on other distros) at: 

https://swing.fit.cvut.cz/jenkins/job/pharo-vm-spur-swing/

Zeroconf for those is also available: 

curl http://swing.fit.cvut.cz/download/pharo/vm-spur-swing | bash
wget -O- http://swing.fit.cvut.cz/download/pharo/vm-spur-swing | bash

Thanks a lot to Esteban and Damien for their help!

Have fun! 
Jan

Re: [Pharo-dev] Menus are broken in diff tools pane

[stepharo]

Alain told me that he can help.
We should give him a list of problems.

Stef

menus are broken almost everywhere:

I thnk, responsible for these issues are only two changes for Rubric 
and the Suggestions-Menu


http://forum.world.st/fixing-our-tools-tp4864859.html




2016-01-14 12:54 GMT+01:00 stepharo >:

Re: [Pharo-dev] Bad layoutFrame>>#hash

[stepharo]

I hope that will not upset Stef too much ;-)
No do not worry!
We finished to shot the first lectures of the mooc. Now we should go 
over the environment

and this is also a difficult and tedious job.

Stef

Re: [Pharo-dev] Bad layoutFrame>>#hash

[stepharo]

Le 13/1/16 22:45, David Allouche a écrit :

On 13 Jan 2016, at 20:32, stepharo  wrote:

Hi david

I would like to turn your post into a chapter for a forthcoming book so that 
people can read and get the idea.

Yes I would be glad :-) Please just remember to credit the author.

Always



Is there a recommended license for Pharo documentation? If not, I am happy to 
release that text under the MIT License.

We release all the books under CreativeCommons (the most liberal one)



I would also like to review your derived work. But that is not a requirement.


Ok I will push it under git in Pharo Progress and you can edit it (for 
now I archive it in my Limbo notes).


Stef



I did not think about the same object. Is it ok for you?

Stef

PS: May be this was obviosu for you that we should all get this out of your 
previous mail but it was not my case
and not after 8 hours on intense work.

Sorry, I do not understand what you are saying here. I do not want to read 
between the lines, because I would probably misunderstand your intention.

Regards.

Re: [Pharo-dev] Bug in protocol and method selection

[stepharo]

Hi henrik

It works because the selection is alpha blent and we can see the 
selection color behind.
It would be good to have the selection getting stronger than the mouse 
cursor


Stef

Le 14/1/16 14:57, Henrik Nergaard a écrit :

Hi Stef,

Do the error still happen if you merge:

Name: Morphic-Widgets-FastTable-HenrikNergaard.148
Author: HenrikNergaard
Time: 13 January 2016, 3:40:48.807358 pm
UUID: b807ebde-ad62-ce41-977a-e6cdce230e93
Ancestors: Morphic-Widgets-FastTable-CyrilFerlicot.147

?

Best regards,
Henrik

-Original Message-
From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Yuriy 
Tymchuk
Sent: Thursday, January 14, 2016 1:43 PM
To: Pharo Development List 
Subject: Re: [Pharo-dev] Bug in protocol and method selection

Stef,

I cannot see the issue, moreover there were no changes in QA that touch 
Nautilus.

Maybe this is because of FastTable highlighting: when you hover over a selected 
list item, it changes color to the hover color, so when you select an item you 
cannot see the you selected it because you see the tower color. This was 
already fixed, but not yes integrated.

Uko


On 14 Jan 2016, at 13:33, Yuriy Tymchuk  wrote:

I will take a look. Just to make sure: this is not the FT coloring thing, right?

Uko


On 14 Jan 2016, at 13:06, stepharo  wrote:

Hi

There is a problem in latest Pharo. I cannot select (and keep the
selection selected) of a method and method protocol.
To me it looks like QA is interferring but I do not know.
This is the kind of glitches that can kill our effort doing videos.
We have a strong deadline for producing such videos. beginning of
march but we want to get done before any help is welcome.

Stef

Re: [Pharo-dev] Bug in protocol and method selection

[stepharo]

In fact the over is taking over the selection so we select and see a 
lightblue selection and it gets greyed

because of the mouse over.
When we move the mouse we see the selection again and the grey.

Stef

Le 14/1/16 13:06, stepharo a écrit :

Hi

There is a problem in latest Pharo. I cannot select (and keep the 
selection selected)

of a method and method protocol.
To me it looks like QA is interferring but I do not know.
This is the kind of glitches that can kill our effort doing videos. We 
have a strong deadline
for producing such videos. beginning of march but we want to get done 
before

any help is welcome.

Stef

[Pharo-dev] poor first Monticello experience (was Fwd: (off list) Bad layoutFrame>>#hash)

[Ben Coman]

On Thu, Jan 14, 2016 at 7:59 PM, David Allouche  wrote:
> On 14 Jan 2016, at 04:26, Ben Coman  wrote:
> hi David,
> Since you seem keen to jump into some code reviews, just
> a prompt you might like to make this your first one...
> https://pharo.fogbugz.com/default.asp?17363
>
>> -- Forwarded message --
>> From: Stephan Eggermont 
>> Date: Thu, Jan 14, 2016 at 1:09 AM
>> Subject: Re: [Pharo-dev] Bad layoutFrame>>#hash
>> To: pharo-dev@lists.pharo.org
>>
>> SLICE-Issue-17363-LayoutFrame-fractions-0--0-corner-1--1--LayoutFrame-identity-should-be-true-and-it-is-not-StephanEggermont.2
>>
>> Better hash both in distribution and in working with Float coordinates
>>
>
> Thank you. That should be easy, since it was a change I suggested and which
> was already reviewed informally on the ML :-)
>
> I think I figured out how it's supposed to work. Can you confirm?

First let me say ouch! and secondly I'm impressed you typed that all
out in detail. It portrays a much better picture than a general
comment.
So it seems we have some tuning to do.

> From the issue page, copy the slice name:
> SLICE-Issue-17363-LayoutFrame-fractions-0--0-corner-1--1--LayoutFrame-identity-should-be-true-and-it-is-not-StephanEggermont.2
> Go to the image. Open Monticello Browser.
> In right (repositories) pane, select
> http://smalltalkhub.com/mc/Pharo/Pharo50Inbox/main
> Try double clicking, see that it does not work

This is probably a good idea to have.  Give a chance for others to
comment, then could you open an issue for it on Fogbugz
(Milestone=Pharo5, Category=Enhancement,  Project=Monticello)

> Guess that one should click the Open button in the top right of the
> Monticello Browser window.

> Come back to the web browser to copy the slice name again, because, I used
> the clipboard to paste the repository name in this email.
> Paste the slice name in the search pane on the right.
> See no result, because there was a trailing newline in the clipboard.

I guess this field should exclude returns and even all trailing
whitespace.  Maybe this should be the default for all such controls
(?) Could you open another issue (or actually search a bit first see
if its already been noted)

> Click on the search pane. Notice it selected all. Click again to put the
> caret at the end.
> Backspace, okay, one result, that should hopefully be it, but it's too long
> to fit in the window.

I guess its not intuitive, but I only ever type the Issue Number of
the slice, since that is unique and there is usually only a couple of
items

> Double click on it, nothing happens.

Choosing a default double-click action would need some community
discussion. Maybe  ??

> Remember that thing appears to think double clicks do not matter.
> Right click on it, see only sorting options, nothing relevant.

I don't think I have ever used the sort options.  Does anyone else use
them so often they couldn't be a submenu of a context menu?

> Look at the buttons on the top of the window. Browse, maybe?
> Get confused by a class browser that somehow does not have syntax
> highlighting, and also shows a lot of things that have nothing to do with
> the code I want to review. That was probably not the right button. Close the
> window.

I never use .   I'm no sure of its value but note however that
Monticello is a general tool for loading packages, which has been
pressed into service to load slices (which is just a package binding a
set of dependent packages together.)   might be good for
exploring a completely new package before its loaded the first time.

> Click on History. Get a window with only the description of the selected
> slice, what use could that possibly have?

Not so much for reviewing slices which have a shallow history.  But
again Monticello is a general package management tool.  For this,
search on 'strings' , then select package Collections-Strings.
Observe how  version Lorenzano.385  is underlined. This version is the
one currently loaded in the image. Observe also Polito.383 is bolded.
This is not an an ancestor of the currently loaded package version.
You can see Lorenzano.385 has ancestor Lorenzano.384 which has
ancestor Lorenzano.383.  Select Lorenzano.385 and click  and
you will see Polito.383 missing from the list.

> Click on Changes. Stuff blinks on screen for a couple seconds, to fast to
> read.

Lucky you ;)  it takes a while from Australia.

I'm not sure of best practice, but personally, to review slices I only
ever use  in the repository window since this provides a
three-way diff.  I'm not sure... but I don't think  does (?)
Back when I started with Pharo using this repository  button
gave different results depending on factors I couldn't track down.
I've never had a problem with  and  is what the CI
monkey uses.

Now I regularly use the  button back in the first Monticello
window.  It compares to the selected repository, so as Stef mentioned
on Fogbugz, when you do come to submit your first slice select to
compare Pharo50/main ra

[Pharo-dev] [pharo-project/pharo-core] ca18da: 50526

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: ca18daca6b4fc435595f7c31d87a312ec67af251
  
https://github.com/pharo-project/pharo-core/commit/ca18daca6b4fc435595f7c31d87a312ec67af251
  Author: Jenkins Build Server 
  Date:   2016-01-14 (Thu, 14 Jan 2016)

  Changed paths:
M 
Collections-Sequenceable.package/OrderedDictionary.class/instance/comparing/=.st
M 
Collections-Sequenceable.package/OrderedDictionary.class/instance/enumerating/associationsSelect_.st
M 
Collections-Sequenceable.package/OrderedDictionary.class/instance/enumerating/collect_.st
M 
Collections-Sequenceable.package/OrderedDictionary.class/instance/enumerating/select_.st
R 
Collections-Sequenceable.package/OrderedDictionary.class/instance/private/speciesNewFrom_.st
M 
Collections-Tests.package/OrderedDictionaryTest.class/instance/tests/testHash.st
M 
MonticelloFileTree-Core.package/MCFileTreeAbstractReader.class/instance/testing/hasMonticelloMetadata.st
M Morphic-Base.package/LayoutFrame.class/instance/comparing/hash.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50525.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50526.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50525.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50526.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  50526
17125 Metadata-less compatibility with FileTree
https://pharo.fogbugz.com/f/cases/17125

17363 (LayoutFrame fractions: (0 @ 0 corner: 1 @ 1)) = LayoutFrame identity 
should be true and it is not.
https://pharo.fogbugz.com/f/cases/17363

17380 OrderedDictionary and OrderedDictionaryTest refactoring
https://pharo.fogbugz.com/f/cases/17380

http://files.pharo.org/image/50/50526.zip

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/50526
  Home:   https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Bug in protocol and method selection

[Henrik Nergaard]

Hi Stef,

Do the error still happen if you merge:

Name: Morphic-Widgets-FastTable-HenrikNergaard.148
Author: HenrikNergaard
Time: 13 January 2016, 3:40:48.807358 pm
UUID: b807ebde-ad62-ce41-977a-e6cdce230e93
Ancestors: Morphic-Widgets-FastTable-CyrilFerlicot.147

?

Best regards,
Henrik

-Original Message-
From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Yuriy 
Tymchuk
Sent: Thursday, January 14, 2016 1:43 PM
To: Pharo Development List 
Subject: Re: [Pharo-dev] Bug in protocol and method selection

Stef,

I cannot see the issue, moreover there were no changes in QA that touch 
Nautilus.

Maybe this is because of FastTable highlighting: when you hover over a selected 
list item, it changes color to the hover color, so when you select an item you 
cannot see the you selected it because you see the tower color. This was 
already fixed, but not yes integrated.

Uko

> On 14 Jan 2016, at 13:33, Yuriy Tymchuk  wrote:
> 
> I will take a look. Just to make sure: this is not the FT coloring thing, 
> right?
> 
> Uko
> 
>> On 14 Jan 2016, at 13:06, stepharo  wrote:
>> 
>> Hi
>> 
>> There is a problem in latest Pharo. I cannot select (and keep the 
>> selection selected) of a method and method protocol.
>> To me it looks like QA is interferring but I do not know.
>> This is the kind of glitches that can kill our effort doing videos. 
>> We have a strong deadline for producing such videos. beginning of 
>> march but we want to get done before any help is welcome.
>> 
>> Stef
>> 
> 
> 

Re: [Pharo-dev] Bug in protocol and method selection

[Yuriy Tymchuk]

Stef,

I cannot see the issue, moreover there were no changes in QA that touch 
Nautilus.

Maybe this is because of FastTable highlighting: when you hover over a selected 
list item, it changes color to the hover color, so when you select an item you 
cannot see the you selected it because you see the tower color. This was 
already fixed, but not yes integrated.

Uko

> On 14 Jan 2016, at 13:33, Yuriy Tymchuk  wrote:
> 
> I will take a look. Just to make sure: this is not the FT coloring thing, 
> right?
> 
> Uko
> 
>> On 14 Jan 2016, at 13:06, stepharo  wrote:
>> 
>> Hi
>> 
>> There is a problem in latest Pharo. I cannot select (and keep the selection 
>> selected)
>> of a method and method protocol.
>> To me it looks like QA is interferring but I do not know.
>> This is the kind of glitches that can kill our effort doing videos. We have 
>> a strong deadline
>> for producing such videos. beginning of march but we want to get done before
>> any help is welcome.
>> 
>> Stef
>> 
> 
> 

Re: [Pharo-dev] Bad layoutFrame>>#hash

[David Allouche]

> On 14 Jan 2016, at 13:31, David Allouche  wrote:
> 
>> 
>> On 14 Jan 2016, at 01:55, Ben Coman  wrote:
>> 
>> On Thu, Jan 14, 2016 at 5:45 AM, David Allouche  wrote:
>>> 
 On 13 Jan 2016, at 20:32, stepharo  wrote:
 
 Hi david
 
 I would like to turn your post into a chapter for a forthcoming book so 
 that people can read and get the idea.
>>> 
>>> Yes I would be glad :-) Please just remember to credit the author.
>>> 
>>> Is there a recommended license for Pharo documentation? If not, I am happy 
>>> to release that text under the MIT License.
>>> 
>>> I would also like to review your derived work. But that is not a 
>>> requirement.
>>> 
 I did not think about the same object. Is it ok for you?
 
 Stef
 
 PS: May be this was obvious for you that we should all get this out of 
 your previous mail but it was not my case
 and not after 8 hours on intense work.
>>> 
>>> Sorry, I do not understand what you are saying here. I do not want to read 
>>> between the lines, because I would probably misunderstand your intention.
>>> 
>>> Regards.
>> 
>> I hope its okay if I jump in and read between the lines when I see to
>> two French people trying to sort out the subtle meanings of english
>> over email.
>> 
>> On any given day anyone can be overworked/stressed/worn out, and they
>> don't have much time to reason deeply on things.  I read "obvious" as
>> an acknowledgement that there was further implicit background
>> knowledge you likely had to "apply" the info from wikipedia. I notice
>> lately Stef's posts have been much shorter than usual, even terse -
>> from which I infer he is flat out.  I think Stef's english suffers
>> when he is in a hurry - only a tiny bit, but email amplifies this.
>> 
>> Don't worry David. When our fiery Stef is upset at you, you won't miss it ;)
> 
> Thank you for the reassurance.
> 
> But that was fine. Stubbing some toes on the rougher personalities in a 
> community, that is part of the process of figuring out the social context of 
> any project :-)
> 
> In any case, his initial reaction did prompt me to include a couple of 
> passive aggressive sentence in my reply. I did remove some :-) but temptation 
> was too strong and I left some in. And he picked them up. Combative 
> temperament.
> 
> When you say "upset", you mean like in the thread that announced the 
> integration of GTDebugger, or was that an example of his baseline? That's an 
> honest question...

Hm. Oops. That was not supposed to go to the mailing list. :-(

I hope that will not upset Stef too much ;-)

Re: [Pharo-dev] Bug in protocol and method selection

[Yuriy Tymchuk]

I will take a look. Just to make sure: this is not the FT coloring thing, right?

Uko

> On 14 Jan 2016, at 13:06, stepharo  wrote:
> 
> Hi
> 
> There is a problem in latest Pharo. I cannot select (and keep the selection 
> selected)
> of a method and method protocol.
> To me it looks like QA is interferring but I do not know.
> This is the kind of glitches that can kill our effort doing videos. We have a 
> strong deadline
> for producing such videos. beginning of march but we want to get done before
> any help is welcome.
> 
> Stef
> 

Re: [Pharo-dev] Bad layoutFrame>>#hash

[David Allouche]

> On 14 Jan 2016, at 01:55, Ben Coman  wrote:
> 
> On Thu, Jan 14, 2016 at 5:45 AM, David Allouche  wrote:
>> 
>>> On 13 Jan 2016, at 20:32, stepharo  wrote:
>>> 
>>> Hi david
>>> 
>>> I would like to turn your post into a chapter for a forthcoming book so 
>>> that people can read and get the idea.
>> 
>> Yes I would be glad :-) Please just remember to credit the author.
>> 
>> Is there a recommended license for Pharo documentation? If not, I am happy 
>> to release that text under the MIT License.
>> 
>> I would also like to review your derived work. But that is not a requirement.
>> 
>>> I did not think about the same object. Is it ok for you?
>>> 
>>> Stef
>>> 
>>> PS: May be this was obvious for you that we should all get this out of your 
>>> previous mail but it was not my case
>>> and not after 8 hours on intense work.
>> 
>> Sorry, I do not understand what you are saying here. I do not want to read 
>> between the lines, because I would probably misunderstand your intention.
>> 
>> Regards.
> 
> I hope its okay if I jump in and read between the lines when I see to
> two French people trying to sort out the subtle meanings of english
> over email.
> 
> On any given day anyone can be overworked/stressed/worn out, and they
> don't have much time to reason deeply on things.  I read "obvious" as
> an acknowledgement that there was further implicit background
> knowledge you likely had to "apply" the info from wikipedia. I notice
> lately Stef's posts have been much shorter than usual, even terse -
> from which I infer he is flat out.  I think Stef's english suffers
> when he is in a hurry - only a tiny bit, but email amplifies this.
> 
> Don't worry David. When our fiery Stef is upset at you, you won't miss it ;)

Thank you for the reassurance.

But that was fine. Stubbing some toes on the rougher personalities in a 
community, that is part of the process of figuring out the social context of 
any project :-)

In any case, his initial reaction did prompt me to include a couple of passive 
aggressive sentence in my reply. I did remove some :-) but temptation was too 
strong and I left some in. And he picked them up. Combative temperament.

When you say "upset", you mean like in the thread that announced the 
integration of GTDebugger, or was that an example of his baseline? That's an 
honest question...

[Pharo-dev] Bug in protocol and method selection

[stepharo]

Hi

There is a problem in latest Pharo. I cannot select (and keep the 
selection selected)

of a method and method protocol.
To me it looks like QA is interferring but I do not know.
This is the kind of glitches that can kill our effort doing videos. We 
have a strong deadline

for producing such videos. beginning of march but we want to get done before
any help is welcome.

Stef

Re: [Pharo-dev] Menus are broken in diff tools pane

[Nicolai Hess]

menus are broken almost everywhere:

I thnk, responsible for these issues are only two changes for Rubric and
the Suggestions-Menu

http://forum.world.st/fixing-our-tools-tp4864859.html




2016-01-14 12:54 GMT+01:00 stepharo :

>
>
>

Re: [Pharo-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

[Andrei Chis]

Hi Nicolai,

Thanks for reporting these issues. They are indeed bugs and we are working
on fixing them.

Cheers,
Andrei

On Tue, Jan 12, 2016 at 11:24 PM, Nicolai Hess 
wrote:

>
>
> 2016-01-08 11:24 GMT+01:00 Tudor Girba :
>
>> Hi,
>>
>> We are about to integrate in Pharo a new member of the Glamorous Toolkit:
>> the GTDebugger. As this is a significant change that might affect your
>> workflow, here is some background information to help you deal with the
>> change.
>>
>> First, you should know that the change is not irreversible and it is
>> easily possible to disabled the new debugger through a setting. However,
>> please do take the time to provide us feedback if something does not work
>> out for you. We want to know what can be improved and we try to react as
>> fast as we can.
>>
>> A practical change comes from the fact that the variables are manipulated
>> through a GTInspector, which makes it cheaper to maintain in the longer run.
>>
>
> Accept and Cancel buttons shouldn't be there
> or should not act on if the codepane hasn't changed.
> (every press on "accept" writes a new method version, although the
> contents didn't changed - tested on
> Latest update: #50524 )
>
> Most (all?) other tools don't have Accept/Cancel buttons.
>
> - I really miss the "List Methods using 'varname'/List Methods storing
> into 'varname'
> - is "stackTop" now gone ? I thought you wanted to add it to the stack ?
> - thisContext is gone as well ?
> - the Bytecode/GT button is badly placed, it looks like the "downarrow"
> window menu icon
>   is a dropdown menu with label "Bytecode" (since when do we put buttons
> in the title pane?
> - the evaluator pane is shown as "dirty", as it does not make a difference
> if we
>   accept the text in this pane, there shouldn't be a dirty indicator.
> - you can not use the inspector pane to change inst var values
> - there is no way to refresh the inspector pane
>
> I don't open bugtracker entries now, I 'll wait maybe this issues aren't
> bugs but
> features.
>
>
> nicolai
>
>
>

Re: [Pharo-dev] PluggableButtonMorph does not respect font size :(

[stepharo]

Thanks nicolai
I changed the font right now. I will check because after we will do 
around 20 videos

showing pharo tools.


Le 14/1/16 11:33, Nicolai Hess a écrit :



2016-01-14 11:19 GMT+01:00 stepharo >:


For the Pharo Mooc we need to use large font and we end up with
this visual glitch :(
I tried to dive into PluggableButtonMorph and I failed to found
how to make sure it computes the bound correctly.
Any help is welcome.



I think this issue is related:
13376 
 
Wrong TextMorph extent for ButtonMorphs

The problem:
UITheme buttonLabelFor: creates a TextMorph with an extent
computed by TextMorph>>optimalExtent (in buttonLabelForText:),
which relies on its TextStyle (from the default font).
After that, the TextMorphs font is changed to the buttons
default font:



label :=selfbuttonLabelForText:aButton label.label enabled:aButton 
enabled.label font:selfbuttonFont.



but the "label font:" does not recomputed the extent.



I really think that in Brick we should really be picky on such
problems.

Stef

Re: [Pharo-dev] Add a package to Manifest?

[stepharo]

Sure!


Le 14/1/16 12:03, Yuriy Tymchuk a écrit :

Hi,

is it possible to add a package into CodeCritics manifest?


Cheers.
Uko

[Pharo-dev] Menus are broken in diff tools pane

[stepharo]

[Pharo-dev] Add a package to Manifest?

[Yuriy Tymchuk]

Hi,

is it possible to add a package into CodeCritics manifest?


Cheers.
Uko

Re: [Pharo-dev] How to get launcher launching Spur images?

[Stephan Eggermont]

On 14-01-16 10:57, Blondeau Vincent wrote:

I just solved the bug that appears on Pharo 5, updated the configuration
and uploaded it to the catalogs.

It should work now.


Thanks Vincent.

It would be better if the problem were fixed in 
ConfigurationOfXMLParser. It misses the #'pharo4.x' and #common parts 
(or possibly #'pharo5.x') and the #release based versioning is not up to 
date.


I would expect to be able to depend on #'release-2' in 
ConfigurationOfPharoLauncher. I would expect #'release-2' to point to
#'release-2.5' which would point to 2.5.6 for #'pharo4.x' and 2.5.7 for 
#'pharo5.x'


The dependency on Ston, JSON and OSProcess would be safe to be on #stable

Stephan

Re: [Pharo-dev] PluggableButtonMorph does not respect font size :(

[Nicolai Hess]

2016-01-14 11:19 GMT+01:00 stepharo :

> For the Pharo Mooc we need to use large font and we end up with this
> visual glitch :(
> I tried to dive into PluggableButtonMorph and I failed to found how to
> make sure it computes the bound correctly.
> Any help is welcome.
>


I think this issue is related:
13376

Wrong TextMorph extent for ButtonMorphs
The problem:
UITheme buttonLabelFor: creates a TextMorph with an extent
computed by TextMorph>>optimalExtent (in buttonLabelForText:),
which relies on its TextStyle (from the default font).
After that, the TextMorphs font is changed to the buttons
default font:


label := self buttonLabelForText: aButton label.
label enabled: aButton enabled.
label font: self buttonFont.


but the "label font:" does not recomputed the extent.





> I really think that in Brick we should really be picky on such problems.
>
> Stef
>
>
>
>

[Pharo-dev] PluggableButtonMorph does not respect font size :(

[stepharo]

For the Pharo Mooc we need to use large font and we end up with this 
visual glitch :(
I tried to dive into PluggableButtonMorph and I failed to found how to 
make sure it computes the bound correctly.

Any help is welcome.
I really think that in Brick we should really be picky on such problems.

Stef

Re: [Pharo-dev] How to get launcher launching Spur images?

[stepharo]

Thanks vincent!!!
I will try later!


Le 14/1/16 10:57, Blondeau Vincent a écrit :


I just solved the bug that appears on Pharo 5, updated the 
configuration and uploaded it to the catalogs.


It should work now.

Vincent

Ps: I was using a Pharo 4.0 image

*De :*Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] *De la part 
de* stepharo

*Envoyé :* jeudi 14 janvier 2016 10:44
*À :* Pharo Development List
*Objet :* Re: [Pharo-dev] How to get launcher launching Spur images?

I got it.
I was trying to use Launcher in Pharo 50.
I do not why I was trying it.
Now it works in Pharo 40.

Le 10/1/16 18:49, stepharo a écrit :

Hi

I changed the setting to be the following but I cannot get a spur
image started on mac.
Does anybody succeed?

Stef





Ce message et les pièces jointes sont confidentiels et réservés à 
l'usage exclusif de ses destinataires. Il peut également être protégé 
par le secret professionnel. Si vous recevez ce message par erreur, 
merci d'en avertir immédiatement l'expéditeur et de le détruire. 
L'intégrité du message ne pouvant être assurée sur Internet, la 
responsabilité de Worldline ne pourra être recherchée quant au contenu 
de ce message. Bien que les meilleurs efforts soient faits pour 
maintenir cette transmission exempte de tout virus, l'expéditeur ne 
donne aucune garantie à cet égard et sa responsabilité ne saurait être 
recherchée pour tout dommage résultant d'un virus transmis.


This e-mail and the documents attached are confidential and intended 
solely for the addressee; it may also be privileged. If you receive 
this e-mail in error, please notify the sender immediately and destroy 
it. As its integrity cannot be secured on the Internet, the Worldline 
liability cannot be triggered for the message content. Although the 
sender endeavours to maintain a computer virus-free network, the 
sender does not warrant that this transmission is virus-free and will 
not be liable for any damages resulting from any virus transmitted.

Re: [Pharo-dev] How to get launcher launching Spur images?

[Blondeau Vincent]

I just solved the bug that appears on Pharo 5, updated the configuration and 
uploaded it to the catalogs.
It should work now.

Vincent

Ps: I was using a Pharo 4.0 image

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de stepharo
Envoyé : jeudi 14 janvier 2016 10:44
À : Pharo Development List
Objet : Re: [Pharo-dev] How to get launcher launching Spur images?

I got it.
I was trying to use Launcher in Pharo 50.
I do not why I was trying it.
Now it works in Pharo 40.
Le 10/1/16 18:49, stepharo a écrit :
Hi

I changed the setting to be the following but I cannot get a spur image started 
on mac.
Does anybody succeed?

Stef


[cid:image001.png@01D14EBA.4FCBB990]




Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: [Pharo-dev] How to get launcher launching Spur images?

[stepharo]

I got it.
I was trying to use Launcher in Pharo 50.
I do not why I was trying it.
Now it works in Pharo 40.

Le 10/1/16 18:49, stepharo a écrit :

Hi

I changed the setting to be the following but I cannot get a spur 
image started on mac.

Does anybody succeed?

Stef

Re: [Pharo-dev] Sounds like Goodies

[olivier auverlot]

yes, the project is on SmalltalkHub (
http://smalltalkhub.com/mc/olivierauverlot/Phonetix/main). It's work in
progress for french & english languages.

Phonetix contains:
* Flesh Indicator,
* Gunning Fog Indicator,
* Hamming Distance,
* Levenshtein Distance
* Syllabes counter,
* Soundex (French & English),
* Soundex2 (French & English),
* Phonex,
* Nysiis

Olivier



2016-01-14 9:48 GMT+01:00 Guillaume Larcheveque <
guillaume.larcheve...@gmail.com>:

> For Soundex, I am quite sure that Olivier Auverlot implemented it in
> Pharo, maybe also the other ones.
>
> 2016-01-13 16:50 GMT+01:00 Torsten Bergmann :
>
>> The dolphin 7 open source repo includes some contributions from Udo
>> including
>> an implementation for Levenshtein distance [1]. It's a single method +
>> test case and easy to
>> port.
>>
>> The algorithm [2] is useful to find out how close two strings are
>> (approximate string matching).
>>
>> There is also SoundEx [4] and SoundsLike [5] (Soundex, Double Metaphone
>> and NYSIIS algorithms)
>> for Pharo available.
>>
>> I just want to let anyone know - just in case someone works on a more
>> "robust" autocompletion
>> that is also typo aware. ;)
>> Having custom templates [6] like in Eclipse would also be good to have in
>> future Pharo code editor.
>>
>> More to add to the wishlist? Damn ... Santa already passed by...
>>
>> Have fun
>> T.
>>
>> [1]
>> https://github.com/dolphinsmalltalk/Contributions/tree/master/Udo%20Schneider/Levenshtein%20Distance
>> [2] https://en.wikipedia.org/wiki/Levenshtein_distance
>> [3]
>> https://github.com/dolphinsmalltalk/Contributions/tree/master/Udo%20Schneider/Soundex
>> [4] http://smalltalkhub.com/#!/~riverdusty/SXSoundEx
>> [5] http://www.smalltalkhub.com/#!/~UdoSchneider/SoundsLike
>> [6] http://www.tutorialspoint.com/eclipse/eclipse_code_templates.htm
>>
>>
>
>
> --
> *Guillaume Larcheveque*
>
>

Re: [Pharo-dev] Sounds like Goodies

[Guillaume Larcheveque]

For Soundex, I am quite sure that Olivier Auverlot implemented it in Pharo,
maybe also the other ones.

2016-01-13 16:50 GMT+01:00 Torsten Bergmann :

> The dolphin 7 open source repo includes some contributions from Udo
> including
> an implementation for Levenshtein distance [1]. It's a single method +
> test case and easy to
> port.
>
> The algorithm [2] is useful to find out how close two strings are
> (approximate string matching).
>
> There is also SoundEx [4] and SoundsLike [5] (Soundex, Double Metaphone
> and NYSIIS algorithms)
> for Pharo available.
>
> I just want to let anyone know - just in case someone works on a more
> "robust" autocompletion
> that is also typo aware. ;)
> Having custom templates [6] like in Eclipse would also be good to have in
> future Pharo code editor.
>
> More to add to the wishlist? Damn ... Santa already passed by...
>
> Have fun
> T.
>
> [1]
> https://github.com/dolphinsmalltalk/Contributions/tree/master/Udo%20Schneider/Levenshtein%20Distance
> [2] https://en.wikipedia.org/wiki/Levenshtein_distance
> [3]
> https://github.com/dolphinsmalltalk/Contributions/tree/master/Udo%20Schneider/Soundex
> [4] http://smalltalkhub.com/#!/~riverdusty/SXSoundEx
> [5] http://www.smalltalkhub.com/#!/~UdoSchneider/SoundsLike
> [6] http://www.tutorialspoint.com/eclipse/eclipse_code_templates.htm
>
>


-- 
*Guillaume Larcheveque*

Re: [Pharo-dev] How to get launcher launching Spur images?

[stepharo]

I executed the expression in the class comment:

ConfigurationOfPharoLauncher load

Stef


Le 14/1/16 09:25, stepharo a écrit :

Sorry to be that stupid but I cannot make launcher work. :(
This is just the third time I try.
I took latest Spur I loaded the latest configuration from the Launcher 
repository

and when I do that I get a DNU when I open it.

So which version in which repository is working?

Stef

Re: [Pharo-dev] How to get launcher launching Spur images?

[stepharo]

Sorry to be that stupid but I cannot make launcher work. :(
This is just the third time I try.
I took latest Spur I loaded the latest configuration from the Launcher 
repository

and when I do that I get a DNU when I open it.

So which version in which repository is working?

Stef

Re: [Pharo-dev] How to get launcher launching Spur images?

[stepharo]

What this experience shows to me is that just having the distribution 
repository is a pain because
Now I have to find where the PharoLauncher is stored to be able to see 
and compare the contents of both repository.
In addition a browse configuration menu item is missing (especially when 
you just load the configuration to read it).


Stef

Le 14/1/16 08:58, stepharo a écrit :

Has the configuration in the catalog been updated?

Stef

Le 13/1/16 20:38, Damien Cassou a écrit :
On January 13, 2016 8:27:10 PM GMT+01:00, "Esteban A. Maringolo" 
 wrote:

Is the Ubuntu PPA updated automatically by the CI?

No. Markus, on CC, is responsible for that.