Re: [Pharo-dev] Pillar 0.56 : New features, new syntax

[Norbert Hartl]

Cyril,

> Am 22.05.2015 um 23:12 schrieb Cyril Ferlicot :
> 
> The second main change is the Internal Links.
> Now when you want to reefer to an anchor, a figure or a script you'll
> need to use *@anchor* instead of *anchor*.
> I'm sorry for that but that's the easiest way to implement the
> inter-files links.

why @? It is about links and how to point to a fragment inside a resource. This 
already exists and is called fragment identifier

http://en.wikipedia.org/wiki/Fragment_identifier 


You do it by using # the separate the resource and the fragment in an URI. 

'../chapters/chapter1.pillar#section1'

is complete valid URI and the way to go. Can you change that?

Norbert

Re: [Pharo-dev] Main pillar web site?

[H. Hirzel]

Hello Cyril

I just saw your announcement about Pillar 0.56 : New features, new syntax

My suggestion is to the main pillar web site the information which
version of Pillar you describe there?

https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/PillarChap/Pillar.html

And  that you post the news about updates somewhere and refer to them
from the main pillar documentation website.

--Hannes

On 5/18/15, H. Hirzel  wrote:
> Luc,
>
> Thanks for the nice diagram showing Pillar in action.
>
> I suggest to include it on the pillar web site.
>
> And maybe you have some additional documentation. For example about the
> parser.
>
> --Hannes
>
> On 5/18/15, Luc Fabresse  wrote:
>> Hi all,
>>
>> As a teacher, I wrote a little Lab subject to introduce the Visitor
>> design
>> pattern to students using Pillar.
>> And I used the following fig to describe it.
>>
>> HIH,
>>
>> #Luc
>>
>> 2015-05-18 20:16 GMT+02:00 H. Hirzel :
>>
>>> Thank you.
>>>
>>> Is it possible to add a short paragraph about the
>>>
>>>  Rational
>>>
>>> for Pillar?
>>>
>>> It seems to be a text format for the PRnnn classes which is easy to
>>> parse.
>>>
>>> Which formats does the Pillar documentation tool chain read and which
>>> ones are generated?
>>>
>>> --Hannes
>>>
>>> On 5/4/15, Cyril Ferlicot  wrote:
>>> > Hi.
>>> > The documentation is now here:
>>> >
>>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/PillarChap/Pillar.html
>>> >
>>> > We're still updating the documentation so that still can change.
>>> >
>>> > On 4 May 2015 at 16:14, H. Hirzel  wrote:
>>> >> Thank you!
>>> >>
>>> >> Here is the summary
>>> >>
>>> >>
>>> >>
>>> >> Pillar documentation
>>> >> 
>>> >>
>>> >> Start page
>>> >> http://www.smalltalkhub.com/#!/~Pier/Pillar
>>> >>
>>> >>
>>> >> Documentation
>>> >> https://github.com/pillar-markup/pillar-documentation
>>> >>
>>> >>
>>> >>
>>> >> First Google hit
>>> >>
>>> https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/Pillar.html
>>> >>
>>> >> Leads to Pharo contribution CI server  (Confirm security exception,
>>> >> it
>>> is
>>> >> safe).
>>> >>
>>> >>
>>> >>
>>> >> Pillar tool chain repositories
>>> >> ---
>>> >>
>>> >> https://github.com/pillar-markup
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Cheers
>>> > Cyril Ferlicot
>>> >
>>> >
>>>
>>>
>>
>

Re: [Pharo-dev] Cross platform key modifiers

[Nicolai Hess]

Hi ben,

2015-05-22 17:28 GMT+02:00 Ben Coman :

> Not sure what past history we inherited, but I am questioning the
> semantics of our key modifiers.  My understanding is that the following is
> industry standard...
> OSX Windows   Linux
> option   altalt
> cmd  ctrl   ctrl
>

Yes, this is what I expected too.
And I thought this is for what KMCommandModifier is used for.
With that, I would expect "Character arrowLeft command" maps to
Ctrl+Left for windows/linux
Meta+Left for Mac (If Meta is the Command-Key on a Mac keyboard).




>
> with Copy being the simplest example of this...
> cmd-c   ctrl-cctrl-c
>
> Supporting this view:
> * "option" and "alternative" are synonyms
> * "command" and "control" have similar meaning (e.g. in the army if you
> command someone, you control them)
> * Microsoft say so (https://support.microsoft.com/en-us/kb/970299)
> * Apple say so (https://support.apple.com/kb/PH18812?locale=en_US) and
> indeed marks its keyboards with "alt" and "option" on the same key (
> http://www.apple.com/au/keyboard/)
>
> So examining this with
> KMLog setDebug.Transcript open.
>
> On OSX Pharo 50044 I get...
> option+arrowLeft --> [keystroke '']
> cmd+arrowLeft --> [keystroke '']
> ctrl+arrowLeft --> OS changes screens
>
> but I am told that Windows gives...
> alt+arrowLeft --> [keystroke '']
> ctrl+arrowLeft --> [keystroke '']
>
> when I believe Windows should be...
> alt+arrowLeft --> [keystroke '']
> ctrl+arrowLeft --> [keystroke '']
>
>
> Part of the issue I think is that our keystroke mapping should be more
> abstract.
>
> When I was using Pharo on Windows, sometimes it felt like a second class
> citizen wrt key mappings, mapping ctrl-c to an apple-named .
> Perhaps what we should see is:
>
> OSX...
> option+arrowLeft --> [keystroke '']
> cmd+arrowLeft --> [keystroke '']
>
> Windows...
> alt+arrowLeft --> [keystroke '']
> ctrl+arrowLeft --> [keystroke '']
>
> Otherwise there will always be the tension on windows that ctrl-c should
> generate [] and we end up with definitions repetitively
> formed like...
> PharoShortcuts>>acceptShortcut
> ^ $s ctrl win | $s ctrl unix | $s command mac
>
> which opens the door for inconsistencies.  We should only need to do
> something like...
> PharoShortcuts>>acceptShortcut
> ^ $s hotkey
>


Isn't OSXs Command-key like MS-Windows "Window" or Linux "Meta" -key?



>
> and leave it to the platform default or user preference the define what
> the hotkey actually is.   A status line in the Keymap Browser could display
> which actual real keys map to  and .
>
>
> What are you thoughts?
> cheers -ben
>
>

[Pharo-dev] Fwd: FogBugz (Case [Issue]13315) Morphic - NewList without icons

[Nicolai Hess]

Is there some more information about this?

I opened that issue and I asks quesions about the NewList implementation on
the mailing
list and commented on some other issues about NewList (for example 13554
 Red cross in
EyeDateAndTimeInspector).
(With not so much feedback).
And making NewListRender working with athens caused quite some headache to
me.
But this is the first time I hear someone is working on a new list.

I would like to encourage people to make more comments on the bugtracker.

And, as we have already quite some mess in our widget libraries, because we
have all kinds of
list/tree-morph-nomorph-pluggable-or-simple-with-or-without-icons-things,
I would like some more discussion/background info about this.

Especially how we prevent to not have  "just-another-list" in the image, but
a way/plan to migrate or exchange the current list class to use the
new/better one.

thanks
nicolai





-- Forwarded message --
From: Pharo Issue Tracker 
Date: 2015-05-22 11:23 GMT+02:00
Subject: FogBugz (Case [Issue]13315) Morphic - NewList without icons
To: "nicolaih...@web.de" 


 [image: avatar]
*Marcus Denker* resolved *Case 13315*: NewList without icons
 and assigned it to you:
 *Bug* in [image: Project:] Morphic: 1. Pharo Image
We have a better list done by esteban soon
 *Status* changed:
Work Needed  [image: changed to]  Resolved (Invalid)

 *Assigned To* changed:
Everyone  [image: changed to]  Nicolai Hess

[image: Priority]  *Priority*: 3 – Must Fix  [image: Status]  *Status*:
Resolved (Invalid)   [image: Assigned To]  *Assigned to*: Nicolai Hess  [image:
Milestone]  *Milestone*: Pharo5.0

Go to Case
  
Don't want FogBugz notifications anymore? Update your preferences.


[image: FogBugz]   A case which you opened has been resolved ( Resolved
(Invalid) ) by Marcus Denker in FogBugz. It is your responsibility to
verify the resolution and close or reactivate the case. Case ID: 13315
Title: NewList without icons Status: Resolved (Invalid) Category: Bug
Project: Morphic Area: 1. Pharo Image Priority: 3 - Must Fix Milestone:
Pharo5.0: 4/1/2016 Assigned To: Nicolai Hess URL:
https://pharo.fogbugz.com/default.asp?13315 Changes: Status changed from
'Work Needed' to 'Resolved (Invalid)'. Last message: We have a better list
done by esteban soon If you do not want to receive automatic notifications
anymore, change your preferences in the Options screen.
(https://pharo.fogbugz.com/f/userPrefs)

[Pharo-dev] Pillar 0.56 : New features, new syntax

[Cyril Ferlicot]

Hello,
today I created the version 0.56 of Pillar and with this version we'll
need to do some changes, sorry.

The first change is the numerator. The old numerator was too limited,
so i changed it. Now if you put different files into the pillar.conf
the numerator will not be reset at each files.
The parameters 'startNumberingAtHeaderLevel:' and
'stopNumberingAtHeaderLevel:' are replace by 'level1:', 'level2:',
'level3:', 'level4:', 'level5:'.
For now they can take 3 sub-parameters: 'numbering', 'size' and 'renderAs'.

numbering: a boolean that say if this header level need to be take in
account by the numerator.
size: the number of level we want to render. You can put numbering at
true and size at 0 if you want your numerator to be reset at a level
without rendering the number of this level.
renderAs: can be number, roman, letter or upperLetter.

Example:

pillar.conf:
{
'level1': {
'numbering': true,
'size': 1,
'renderAs': 'roman'
},
'level2': {
'numbering': true,
'size': 2,
'renderAs': 'number'
},
'level3': {
'numbering': true,
'size': 1,
'renderAs': 'upperLetter'
},
'level4': {
'numbering': true,
'size': 2,
'renderAs': letter
},
'level5': {
'numbering': false
},

}

document.pillar:

! Example
!! Introduction
!!! Beginning
!!! Example - Intro
 Example 1
 Example 2
! With X
! With Y
!! Explanation

Result:
I. Example
I.1. Introduction
A. Beginning
B. Example - Intro
B.a. Example 1
B.b. Example 2
With X
With Y
I.2. Explanation


In the future we could also add feature like 'delimiter'.

The second main change is the Internal Links.
Now when you want to reefer to an anchor, a figure or a script you'll
need to use *@anchor* instead of *anchor*.
I'm sorry for that but that's the easiest way to implement the
inter-files links.

And so the last main change is the Inter-files links !
Imagine you're writing a book.
You have a directory 'Chapter1' which contains the file
'chapter1.pillar' and a directory 'Chapter2' with a file
'chapter2.pillar'.

If you want to make a reference to the chapter 1 in the chapter 2 you
can create an interfile link you can now use the syntax:

*../Chapter1/chapter1.pillar*

But be careful ! Remember that pillar can export in different format.
And you can export a group of file as separate output files or as one
file.
So if you don't use an Alias your link will not be render if you
export as one output file in LaTeX. And if you export in LaTeX or HTML
or Markdown as one output file and you don't have an anchor on your
link, the link will be vanish.

So I recommend to use inter file links like this:

*Chapter 1>../Chapter1/chapter1.pillar@cha:chapter1*

when cha:chapter1 is an anchor you need to create at the beginning of
the chapter 1.

I already changed the links on Enterprise Pharo (you can find a table
with the list of the inter-files links on the README.md)

On last thing for the people who write book for SquareBracketAssociates:
It would be good to have some conventions, so if you create anchors
use this form :
@sec:nameOfSection for a section
@cha:nameOfTheChapter for a title of chapter
@fig:nameOfFigure for a figure
@spt:nameOfTheScript for a script

-- 
Cheers
Cyril Ferlicot

Re: [Pharo-dev] [Reflectivity] Progress for Breakpoints

[stepharo]

Marcus

with franck and alain we worked on using Rubric instead of 
pluggableTextMorph in Nautilus.

so you will be able to display icons or other for the breakpoints.

Stef

Le 22/5/15 11:53, Marcus Denker a écrit :


https://pharo.fogbugz.com/f/cases/15516/add-suggestion-for-breakpoint

this is of course completely untested… it works only when there is 
no unaccepted

text in the editor and maybe only within Nautilus.

And of course existing breakpoints are not yet in any form 
visualised in the editor.


This is in 50041. Please use with care… still needs work to be really 
usable.




I now finished to add everything from Clara’s original 
SmartBreakpoints project.


There are still lots of things that need to be done

-> Something goes wrong when re-adding a one-shot breakpoint again.
-> Adding should be disabled when the editor has non-submitted code.
-> The experience in the debugger is not that nice
 (need to think about using the  trick and
 explore the filtering capabilities of the debugger)

I am now continuing to flesh out the Reflectivity features:

-> hook AST generation is now done by HookGenerator
-> correct hooks are already generated for the case that a link passes
arguments to the meta object (see the RFReification hierarchy, for now
we have only #object *and* actual compiling does not yet work due 
to missing

semantic analysis of the AST snippets for the hooks)
-> We have support for “virtual” meta objects. Any valid reification 
can be the metaObject

(this is fun for #node).

TODO
- add all reifications for all nodes (#arguments, #node, #context, 
#value #name, #arg1…)

- do semantic analysis correctly and add test for links with arguments
- add conditions with parameters (e.g. for object specific links: 
[:object | object == myObject])
- handle primitives: when putting a link on a primitive method, wrap 
the compiledMethod instead

  of AST manipulation.
- ….

I will continue to flesh it out and send examples to the list as these 
things start to work for real.



Marcus

Re: [Pharo-dev] New Collections for Pharo

[stepharo]

Hi

did you write tests?
did your implementation propose APIs that are compatible with the 
Collection API?


Stef

Re: [Pharo-dev] Opportunity to steal good ideas from dad ;)

[stepharo]

If people wants to harvest some changes from Squeak, please do it.

Collections
Speed up testing different sized strings.
Interval >> #sum is now O(1) instead of O(n).
Introduction of Set>>#addNewElement: optimizes graph-traversal.
Slightly faster SequenceableCollection >> #copyUpT (for 
ByteString receivers).

Stricter and faster implementation of String >> #format:.
Optimized Interval >> #sum, OrderedCollection >> #at: and 
OrderedCollection >> #at:put:.

Simpler and faster Character >> #tokenish.
Speed-up #endsWith: for strings.

Morphic
Sped up #valueOfProperty:ifAbsent: and friends.

Symbol table improvements such as thread-safety and consistent 
enumeration.

Threadsafe random.

Squeak 4.6 "Spur" Release Notes
http://wiki.squeak.org/squeak/6192



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Opportunity-to-steal-good-ideas-from-dad-tp4827836.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Morphic menus

[stepharo]

Hi mathieu

can you open a bug entry?
and publish your solution.
Tx


Le 21/5/15 14:50, Matthieu Lacaton a écrit :

Hello everyone,

I had to understand how menus work in Morphic lately and I noticed 
some things :


1) When a menu has strictly more than 1 submenu active it cannot 
regain the focus if the mouse doesn't pass over the submenus first. It 
is a bit hard for me to explain so I will give you an example :
Open a Nautilus browser on any package and right click on a class. Now 
browse "Refactoring => Code Rewriting => Rewrite Code but don't click 
on any of these items. You will have 3 menus. Now if you exit the last 
menu without returning to the previous one (make a loop from the right 
for example if you have enough place) and go back directly to the 
first one you'll see that it doesn't respond (it is like frozen).


I don't know if it is a bug or if it is intended but I find it strange 
as it is not how it is working on Windows nor Ubuntu for example.


So if it is indeed a bug, what I propose as a "fix" would be this:

Replace *:

*

*MenuItemMorph >>* /activateOwner Menu: evt/
"Activate our owner menu; e.g., pass control to it"
owner ifNil:[^false]. "not applicable"
(owner fullContainsPoint: evt position) ifFalse:[^false].
owner activate: evt.
^true


by:

*MenuItemMorph >>* /activateOwner Menu: evt/

/
/

/| popUpOwner |

/
/owner ifNil: [^false].
/
/(owner fullContainsPoint: evt position) ifTrue: [
/
/owner activate: evt.
/
/^true.
].

/
/popUpOwner := owner popUpOwner.
/
/[ popUpOwner ] whileNotNil: [
/
/(popUpOwner owner fullContainsPoint: evt position) ifTrue: [
/
/popUpOwner owner activate: evt.
/
/^true.
]
/
/ifFalse: [
/
/popUpOwner := popUpOwner owner popUpOwner.
].
].
/
/^false.
/


It should work with any number of submenus but i couldn't find 
anywhere in Pharo with more than 3 menus so i couldn't test it further.


2) When you leave a submenu and quickly come back to its popUpOwner, 
the item in the submenu won't be deselected. So if you navigate a bit 
in the menu and then want to come back to this submenu, you won't be 
able to select the item by passing your mouse over it. It is not a big 
deal in 99.9% of the time as you will still be able to click on it but 
when this item is supposed to open a submenu it won't. You need to go 
to another item in the submenu and to come back.


I noticed that it happened because if you are leaving the submenu too 
quickly there is no "mouseLeave" event generated so the itemMenu is 
not deselected. Thus, as it is considered as selected, if you come 
back to it later a "mouseEnter" event will not trigger anything.


It is quite easy to reproduce with the same menu than for the 1) :
Right click on a class in a Nautilus browser then browse Refactoring 
=> Code Rewriting.
Now if you quickly come back to Refactoring sometimes you'll see that 
Code Rewriting won't be deselected (it will still be blue after the 
500ms time out). If it is the case you can go back on "Rename..." and 
then if you quickly come back to Refactoring => Code Rewriting, you 
won't be able to get the 3rd submenu.


I can reproduce this very easily but it is not really a problem 
because it only happens if you are fast with your mouse.


I did not try to fix it but I guess that reinitializing all the 
itemMenus to unselected when poping a menu could do the trick.


3) This one is mostly insignificant because it is quite hard to 
reproduce and doesn't trigger often at all. But sometimes when you 
quickly navigate between 3 menus (I have not been able to reproduce it 
with only 2 menus) when you want to go back to the first one it 
freezes and it doesn't handle the mouseOver events anymore (you can 
still click though).
This is not the same thing than the first point because here you 
correctly pass through the previous submenus to go to the first one.
I don't really know why this happens sometimes but I think it may be 
because the focus was not passed quickly enough between windows and 
one on the submenus gets deactivated and removed from the world wheras 
it still had the focus on him.


Anyway these 3 things are not really important but I just wanted to 
share what i found with you in case you think it is valid.


Cheers,

Matthieu
/
/

Re: [Pharo-dev] Opportunity to steal good ideas from dad ;)

[stepharo]

http://www.smalltalkhub.com/#!/~emaringolo/SortFunctions

I use them extensively.

Esteban A. Maringolo


I had a look.

Apart from the fact that for some reason, the extensions on MAElement are in 
the Core package, hence loading just Core gave errors, things looked OK.

This is generally useful, small and a very good example of super cool OO design.

I would vote to integrate this (<=> and all).


Why? Can we rewrite a large part of the system with it?
If not why people cannot just load a package?
We should stop to think monolithic.

Stef

Re: [Pharo-dev] Opportunity to steal good ideas from dad ;)

[stepharo]

What is <=> because I found it quite not intention revealing.



Le 22/5/15 11:19, p...@highoctane.be a écrit :

Thinking of the <=> operator, this can be useful for things like this:

dataset := #(1 3 4 5 7 8 5 2 3 0).
mean := dataset average.
dataset collect: [ :each |  mean <=> each ]

-->  #(1 1 -1 -1 -1 -1 -1 1 1 1)

This we can also do with

coll := #(1 3 4 5 7 8 5 2 3 0).
mean := coll average.
coll collect: [ :each |  (mean - each) sign ]

but still.

Other use cases for <=> ?

Phil


On Fri, May 22, 2015 at 11:43 AM, Sven Van Caekenberghe > wrote:



> On 21 May 2015, at 16:50, Esteban A. Maringolo
mailto:emaring...@gmail.com>> wrote:
>
> 2015-05-21 10:01 GMT-03:00 p...@highoctane.be
 mailto:p...@highoctane.be>>:
>>
>>
>> On Thu, May 21, 2015 at 2:19 PM, Sean P. DeNigris
mailto:s...@clipperadams.com>>
>> wrote:
>>>
>>> Squeak 4.6 "Spur" Release Notes
>>> http://wiki.squeak.org/squeak/6192
>>
>>
>> Tag sort functions looks great to have around.
>>
>> About the spaceship operator (<=>), is this something  we'd
like to have
>> around? (I like it).
http://en.wikipedia.org/wiki/Three-way_comparison
>
> http://www.smalltalkhub.com/#!/~emaringolo/SortFunctions

>
> I use them extensively.
>
> Esteban A. Maringolo

I had a look.

Apart from the fact that for some reason, the extensions on
MAElement are in the Core package, hence loading just Core gave
errors, things looked OK.

This is generally useful, small and a very good example of super
cool OO design.

I would vote to integrate this (<=> and all).

Sven

Re: [Pharo-dev] Format shortcut.

[Damien Cassou]

Cyril Ferlicot  writes:

> I propose to keep ctrl + shift + f (like in Eclipse).

makes sense

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

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

[Pharo-dev] [pharo-project/pharo-core] 947163: 50060

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 947163790b1294d8502473a0c56b1a0bddbdac8e
  
https://github.com/pharo-project/pharo-core/commit/947163790b1294d8502473a0c56b1a0bddbdac8e
  Author: Jenkins Build Server 
  Date:   2015-05-22 (Fri, 22 May 2015)

  Changed paths:
R Graphics-Fonts.package/FontSet.class/class/as yet 
unclassified/convertFontsNamed_.st
R Graphics-Fonts.package/FontSet.class/class/compiling/compileFont_.st
R 
Graphics-Fonts.package/FontSet.class/class/converting/convertFontsNamed_inDirectoryNamed_.st
R 
Graphics-Fonts.package/FontSet.class/class/converting/convertTextStyleNamed_.st
R 
Graphics-Fonts.package/StrikeFont.class/class/examples/convertFontsNamed_.st
R Graphics-Fonts.package/StrikeFont.class/instance/file 
in%2Fout/writeAsStrike2On_.st
R Graphics-Fonts.package/StrikeFont.class/instance/file 
in%2Fout/writeAsStrike2named_.st
A Reflectivity-Tests.package/HookGeneratorTest.class/instance/tests - 
hooks/testConditionWithArguments.st
M Reflectivity.package/HookGenerator.class/instance/ast 
manipulation/wrapCondition_.st
A Reflectivity.package/ManifestReflectivity.class/README.md
A Reflectivity.package/ManifestReflectivity.class/definition.st
A 
Reflectivity.package/ManifestReflectivity.class/instance/code-critics/ruleRBBadMessageRuleV1FalsePositive.st
A Reflectivity.package/RFCondition.class/instance/accessing/valueSelector.st
A Reflectivity.package/extension/BlockClosure/instance/valueSelector.st
A Reflectivity.package/extension/Boolean/instance/valueSelector.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50059.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50060.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50059.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50060.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
R SmartSuggestions.package/SugsAbstractContext.class/instance/tools/tools.st
M SmartSuggestions.package/SugsAccessesToInstVar.class/instance/as yet 
unclassified/execute.st
M SmartSuggestions.package/SugsBrowseClassReferences.class/instance/as yet 
unclassified/execute.st
M SmartSuggestions.package/SugsFindImplementors.class/instance/as yet 
unclassified/execute.st
M SmartSuggestions.package/SugsFindSenders.class/instance/as yet 
unclassified/execute.st
M SmartSuggestions.package/SugsStoresIntoInstVar.class/instance/as yet 
unclassified/execute.st
R 
SmartSuggestions.package/extension/AbstractTool/instance/browseAllAccessesTo_from_.st
R 
SmartSuggestions.package/extension/AbstractTool/instance/browseSendersOf_name_autoSelect_.st

  Log Message:
  ---
  50060
10120 StrikeFont default writeAsStrike2On: strikefont.bin fails - DNU
https://pharo.fogbugz.com/f/cases/10120

15587 clean up SugAbstractContext>>#tools
https://pharo.fogbugz.com/f/cases/15587

15591 Generate Hooks for links with conditions that get arguments passed in
https://pharo.fogbugz.com/f/cases/15591

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

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

[GitHub]

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

Re: [Pharo-dev] Opportunity to steal good ideas from dad ;)

[Esteban A. Maringolo]

2015-05-22 6:43 GMT-03:00 Sven Van Caekenberghe :
>> On 21 May 2015, at 16:50, Esteban A. Maringolo  wrote:
>>> About the spaceship operator (<=>), is this something  we'd like to have
>>> around? (I like it). http://en.wikipedia.org/wiki/Three-way_comparison

>> http://www.smalltalkhub.com/#!/~emaringolo/SortFunctions
>> I use them extensively.

> I had a look.
>
> Apart from the fact that for some reason, the extensions on MAElement are in 
> the Core package, hence loading just Core gave errors, things looked OK.
>
> This is generally useful, small and a very good example of super cool OO 
> design.
>
> I would vote to integrate this (<=> and all).

For some reason the extensions of MAElementDescription where both in
SortFunctions-Core and SortFunctions-Magritte.
Also the dependency to Magritte in the Metacello config was wrong.

Now it works as expected (please test :)). And a new stable version
was uploaded to the smalltalkhub repo.

Please notice my port includes the option to collate the undefined
elements at the beginning or the end, in a similar fashion to ORDER BY
[column] NULLS [LAST|FIRST] in SQL (Oracle/PostgreSQL at least).

I would also vote to have this in the base image. It is my base image
at least :)


Regards!

--
Esteban A. Maringolo

Re: [Pharo-dev] can someone explain me this?

[Alejandro Infante]

If you remove the Traits you get exactly the double (at least in my moose 
image).

As far as I remember, Traits are not subclasses of Objects and they do not have 
a metaclass for each Trait.

Cheers,
Alejandro

> On May 22, 2015, at 12:39 PM, Eliot Miranda  wrote:
> 
> Oops, my math was wrong and so I got it wrong way round.  But you know what I 
> mean...
> 
> Eliot (phone)
> 
> On May 22, 2015, at 8:37 AM, Eliot Miranda  wrote:
> 
>> Hi All,
>> 
>> On May 21, 2015, at 1:14 PM, Esteban Lorenzano  wrote:
>> 
>>> Smalltalk allClassesAndTraits size. "5057"
>>> Object withAllSubclasses size. “9900"
>> 
>> As others have said, meta classes account for many of these, but I would 
>> have expect something closer to twice as many.  What does this tell you?
>> 
>> (IdentitySet withAll: (Object withAllSubclasses reject: [:b| b isMeta])
>>   removeAll: Smalltalk allClassesAndTraits;
>>   yourself
>> 
>> Are there perhaps lots of obsolete classes that need cleaning up?
>> 
>> 
>>> I really do not understand :)
>>> 
>>> Esteban
> 

Re: [Pharo-dev] can someone explain me this?

[Eliot Miranda]

Oops, my math was wrong and so I got it wrong way round.  But you know what I 
mean...

Eliot (phone)

On May 22, 2015, at 8:37 AM, Eliot Miranda  wrote:

> Hi All,
> 
> On May 21, 2015, at 1:14 PM, Esteban Lorenzano  wrote:
> 
>> Smalltalk allClassesAndTraits size. "5057"
>> Object withAllSubclasses size. “9900"
> 
> As others have said, meta classes account for many of these, but I would have 
> expect something closer to twice as many.  What does this tell you?
> 
> (IdentitySet withAll: (Object withAllSubclasses reject: [:b| b isMeta])
>removeAll: Smalltalk allClassesAndTraits;
>yourself
> 
> Are there perhaps lots of obsolete classes that need cleaning up?
> 
> 
>> I really do not understand :)
>> 
>> Esteban

Re: [Pharo-dev] can someone explain me this?

[Eliot Miranda]

Hi All,

On May 21, 2015, at 1:14 PM, Esteban Lorenzano  wrote:

> Smalltalk allClassesAndTraits size. "5057"
> Object withAllSubclasses size. “9900"

As others have said, meta classes account for many of these, but I would have 
expect something closer to twice as many.  What does this tell you?

(IdentitySet withAll: (Object withAllSubclasses reject: [:b| b isMeta])
removeAll: Smalltalk allClassesAndTraits;
yourself

Are there perhaps lots of obsolete classes that need cleaning up?


> I really do not understand :)
> 
> Esteban

[Pharo-dev] Cross platform key modifiers

[Ben Coman]

Not sure what past history we inherited, but I am questioning the semantics
of our key modifiers.  My understanding is that the following is industry
standard...
OSX Windows   Linux
option   altalt
cmd  ctrl   ctrl

with Copy being the simplest example of this...
cmd-c   ctrl-cctrl-c

Supporting this view:
* "option" and "alternative" are synonyms
* "command" and "control" have similar meaning (e.g. in the army if you
command someone, you control them)
* Microsoft say so (https://support.microsoft.com/en-us/kb/970299)
* Apple say so (https://support.apple.com/kb/PH18812?locale=en_US) and
indeed marks its keyboards with "alt" and "option" on the same key (
http://www.apple.com/au/keyboard/)

So examining this with
KMLog setDebug.Transcript open.

On OSX Pharo 50044 I get...
option+arrowLeft --> [keystroke '']
cmd+arrowLeft --> [keystroke '']
ctrl+arrowLeft --> OS changes screens

but I am told that Windows gives...
alt+arrowLeft --> [keystroke '']
ctrl+arrowLeft --> [keystroke '']

when I believe Windows should be...
alt+arrowLeft --> [keystroke '']
ctrl+arrowLeft --> [keystroke '']


Part of the issue I think is that our keystroke mapping should be more
abstract.

When I was using Pharo on Windows, sometimes it felt like a second class
citizen wrt key mappings, mapping ctrl-c to an apple-named .
Perhaps what we should see is:

OSX...
option+arrowLeft --> [keystroke '']
cmd+arrowLeft --> [keystroke '']

Windows...
alt+arrowLeft --> [keystroke '']
ctrl+arrowLeft --> [keystroke '']

Otherwise there will always be the tension on windows that ctrl-c should
generate [] and we end up with definitions repetitively
formed like...
PharoShortcuts>>acceptShortcut
^ $s ctrl win | $s ctrl unix | $s command mac

which opens the door for inconsistencies.  We should only need to do
something like...
PharoShortcuts>>acceptShortcut
^ $s hotkey

and leave it to the platform default or user preference the define what the
hotkey actually is.   A status line in the Keymap Browser could display
which actual real keys map to  and .


What are you thoughts?
cheers -ben

Re: [Pharo-dev] UI Design

[Dimitris Chloupis]

I am looking into implementing a futuristic GUI for Pharo  but will be a
very long term project since I am still quite unfamiliar with Morphic. The
effort has started with my Blue theme but will expand the theme to make it
customise Pharo a lot deeper.

My goal is to also make the theme as dynamic as I can, currently this
already possible with the small wizard I offer for customizing the colors.
The project is called Nireas and is available through the Configuration
Browser. Its very basic right now but will slowly grow larger and more
sophisticated.

On Fri, May 22, 2015 at 4:23 PM Torsten Bergmann  wrote:

> Is there something new planned for Pharo 5 regarding the UI look?
> New theme or integration of an animation framework to support better
> looking Pharo apps?
>
> Looks like material design is the next fashionable UI hype:
>
> https://www.youtube.com/watch?v=7xH26aGqHDM
> https://www.youtube.com/watch?v=6XSyBV0h2n4
> https://www.youtube.com/watch?v=6XSyBV0h2n4
>
> Anyone working on something for rich client apps in Pharo?
>
> Thanks
> T.
>
>

[Pharo-dev] UI Design

[Torsten Bergmann]

Is there something new planned for Pharo 5 regarding the UI look?
New theme or integration of an animation framework to support better
looking Pharo apps?

Looks like material design is the next fashionable UI hype:

https://www.youtube.com/watch?v=7xH26aGqHDM
https://www.youtube.com/watch?v=6XSyBV0h2n4
https://www.youtube.com/watch?v=6XSyBV0h2n4

Anyone working on something for rich client apps in Pharo?

Thanks
T.

Re: [Pharo-dev] [Reflectivity] Progress for Breakpoints

[Clara Allende]

2015-05-22 8:53 GMT-03:00 Marcus Denker :

>
> https://pharo.fogbugz.com/f/cases/15516/add-suggestion-for-breakpoint
>
> this is of course completely untested… it works only when there is no
> unaccepted
> text in the editor and maybe only within Nautilus.
>
> And of course existing breakpoints are not yet in any form visualised in
> the editor.
>
>
> This is in 50041. Please use with care… still needs work to be really
> usable.
>
>
> I now finished to add everything from Clara’s original SmartBreakpoints
> project.
>
> There are still lots of things that need to be done
>
> -> Something goes wrong when re-adding a one-shot breakpoint again.
>

Yep, I'm aware of that bug, I couldn't figure out why it does it happen :/
At one point I got it work and randomly fail, so it was difficult to debug
:( If right now it fails consistently, I would like to take a look.


> -> Adding should be disabled when the editor has non-submitted code.
> -> The experience in the debugger is not that nice
>  (need to think about using the  trick and
>  explore the filtering capabilities of the debugger)
>

I'm aware of this one too. I did add a filter for the
Reflectivity/breakpoints contexts, but in my experience, the top most of
those contexts remained on the debugger stack (because we need it in case
we want to go back to that point after a lot of step into/out etc), making
it a little bit confusing... I mean, when I saw it, I put myself in the
place of the user, and could imagine him/her wondering wtf does that mean.
I agree we need to re-think it :/

>
> I am now continuing to flesh out the Reflectivity features:
>
> -> hook AST generation is now done by HookGenerator
> -> correct hooks are already generated for the case that a link passes
> arguments to the meta object (see the RFReification hierarchy, for now
> we have only #object *and* actual compiling does not yet work due to
> missing
> semantic analysis of the AST snippets for the hooks)
> -> We have support for “virtual” meta objects. Any valid reification can
> be the metaObject
> (this is fun for #node).
>
> TODO
> - add all reifications for all nodes (#arguments, #node, #context, #value
> #name, #arg1…)
> - do semantic analysis correctly and add test for links with arguments
> - add conditions with parameters (e.g. for object specific links: [:object
> | object == myObject])
> - handle primitives: when putting a link on a primitive method, wrap the
> compiledMethod instead
>   of AST manipulation.
> - ….
>
> I will continue to flesh it out and send examples to the list as these
> things start to work for real.
>
>
> Marcus
>
>

Re: [Pharo-dev] Best practice for overwriting methods in other classes

[Ben Coman]

On Fri, May 22, 2015 at 1:08 PM, Kasper Osterbye  wrote:

> I have now twice in two different situations felt a need to "steal" a
> method
> in Nautilus and make that method an extension method in my own package.
>
> In situation A, I wanted to steal the #buildCommentPane to use a different
> Morph for class comments,
>

I've not encountered this myself, but I guess the approach would be to get
a change integrated into Pharo that allows an external package to configure
it to use a different Morph -- though I'm not sure of the best approach to
do that.


> In situation B, Sergio and I needed to redefine #getComments and
> #addComments:notifying: to fill out behaviour for package comments.
>
>
In this case, I thought the aim of your package-comments work was to
integrate it into Pharo, so actually you should be redefining the built-in
methods as needed (??)
cheers -ben

What is the kosher way to work and contribute in such situations? I guess it
> will also pop up in situations outside of Nautilus.
>
>

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

[GitHub]

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

[Pharo-dev] [pharo-project/pharo-core] 93ae2a: 50059

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 93ae2a76e4cae1e04906a07c81771312d9ba39e1
  
https://github.com/pharo-project/pharo-core/commit/93ae2a76e4cae1e04906a07c81771312d9ba39e1
  Author: Jenkins Build Server 
  Date:   2015-05-22 (Fri, 22 May 2015)

  Changed paths:
M Collections-Unordered.package/Set.class/instance/enumerating/collect_.st
M CollectionsTests.package/SetTest.class/instance/tests - 
iterating/testCollect.st
M 
NautilusRefactoring.package/NautilusRefactoring.class/class/shortcuts/buildSourceCodeShortcutsOn_.st
A OpalCompiler-Core.package/OCKeyedSet.class/instance/copying/collect_.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50058.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50059.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50058.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50059.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  ---
  50059
14535  IdentitySet>>collect: answers a Set, not an IdentitySet.
https://pharo.fogbugz.com/f/cases/14535

15584 TClassDescription>>#sourceCodeRefactoringMenu:  and 
NautilusRefactoring>>#buildSourceCodeShortcutsOn: need review
https://pharo.fogbugz.com/f/cases/15584

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

Re: [Pharo-dev] [Reflectivity] Progress for Breakpoints

[Marcus Denker]

>> 
>> https://pharo.fogbugz.com/f/cases/15516/add-suggestion-for-breakpoint 
>> 
>> 
>> this is of course completely untested… it works only when there is no 
>> unaccepted
>> text in the editor and maybe only within Nautilus.
>> 
>> And of course existing breakpoints are not yet in any form visualised in the 
>> editor.
> 
> This is in 50041. Please use with care… still needs work to be really usable.
> 

I now finished to add everything from Clara’s original SmartBreakpoints project.

There are still lots of things that need to be done

-> Something goes wrong when re-adding a one-shot breakpoint again.
-> Adding should be disabled when the editor has non-submitted code.
-> The experience in the debugger is not that nice
 (need to think about using the  trick and
 explore the filtering capabilities of the debugger)

I am now continuing to flesh out the Reflectivity features:

-> hook AST generation is now done by HookGenerator
-> correct hooks are already generated for the case that a link passes
arguments to the meta object (see the RFReification hierarchy, for now
we have only #object *and* actual compiling does not yet work due to 
missing 
semantic analysis of the AST snippets for the hooks)
-> We have support for “virtual” meta objects. Any valid reification can be the 
metaObject
(this is fun for #node).

TODO
- add all reifications for all nodes (#arguments, #node, #context, #value 
#name, #arg1…)
- do semantic analysis correctly and add test for links with arguments
- add conditions with parameters (e.g. for object specific links: [:object | 
object == myObject])
- handle primitives: when putting a link on a primitive method, wrap the 
compiledMethod instead
  of AST manipulation.
- ….

I will continue to flesh it out and send examples to the list as these things 
start to work for real.


Marcus

pharo-dev@lists.pharo.org

[Marcus Denker]

Hi,

No job posting yet as we are seeing what exact kind of person we can hire. 
There is a certain
chance that this will not be constrained to “two years after university”.

Job posting will be finalised next week, if you are interested (or now someone 
who might)
 ==> please contact me already now.

Marcus

> On 19 May 2015, at 17:10, Marcus Denker  wrote:
> 
> Hi,
> 
> We will put the official announce online later this week… we are looking to 
> fill a  a “young engineer position”.
> This is for recent graduates who finished their degree 2013/2014/2015.
> 
> The topic is to work for 2 years on improving “remote” debugging for cases 
> like server deployment, typical
> cloud scenarios and when using embedded Pharo images (e.g. for robotics).
> 
> If you are interested (or know someone who might), please contact me.
> (official announcement will be online later this week).
> 
>   Marcus
> 

Re: [Pharo-dev] Opportunity to steal good ideas from dad ;)

[p...@highoctane.be]

Thinking of the <=> operator, this can be useful for things like this:

dataset := #(1 3 4 5 7 8 5 2 3 0).
mean := dataset average.
dataset collect: [ :each |  mean <=> each ]

-->  #(1 1 -1 -1 -1 -1 -1 1 1 1)

This we can also do with

coll := #(1 3 4 5 7 8 5 2 3 0).
mean := coll average.
coll collect: [ :each |  (mean - each) sign ]

but still.

Other use cases for <=> ?

Phil


On Fri, May 22, 2015 at 11:43 AM, Sven Van Caekenberghe 
wrote:

>
> > On 21 May 2015, at 16:50, Esteban A. Maringolo 
> wrote:
> >
> > 2015-05-21 10:01 GMT-03:00 p...@highoctane.be :
> >>
> >>
> >> On Thu, May 21, 2015 at 2:19 PM, Sean P. DeNigris <
> s...@clipperadams.com>
> >> wrote:
> >>>
> >>> Squeak 4.6 "Spur" Release Notes
> >>> http://wiki.squeak.org/squeak/6192
> >>
> >>
> >> Tag sort functions looks great to have around.
> >>
> >> About the spaceship operator (<=>), is this something  we'd like to have
> >> around? (I like it). http://en.wikipedia.org/wiki/Three-way_comparison
> >
> > http://www.smalltalkhub.com/#!/~emaringolo/SortFunctions
> >
> > I use them extensively.
> >
> > Esteban A. Maringolo
>
> I had a look.
>
> Apart from the fact that for some reason, the extensions on MAElement are
> in the Core package, hence loading just Core gave errors, things looked OK.
>
> This is generally useful, small and a very good example of super cool OO
> design.
>
> I would vote to integrate this (<=> and all).
>
> Sven
>
>
>

Re: [Pharo-dev] Opportunity to steal good ideas from dad ;)

[Sven Van Caekenberghe]

> On 21 May 2015, at 16:50, Esteban A. Maringolo  wrote:
> 
> 2015-05-21 10:01 GMT-03:00 p...@highoctane.be :
>> 
>> 
>> On Thu, May 21, 2015 at 2:19 PM, Sean P. DeNigris 
>> wrote:
>>> 
>>> Squeak 4.6 "Spur" Release Notes
>>> http://wiki.squeak.org/squeak/6192
>> 
>> 
>> Tag sort functions looks great to have around.
>> 
>> About the spaceship operator (<=>), is this something  we'd like to have
>> around? (I like it). http://en.wikipedia.org/wiki/Three-way_comparison
> 
> http://www.smalltalkhub.com/#!/~emaringolo/SortFunctions
> 
> I use them extensively.
> 
> Esteban A. Maringolo

I had a look.

Apart from the fact that for some reason, the extensions on MAElement are in 
the Core package, hence loading just Core gave errors, things looked OK.

This is generally useful, small and a very good example of super cool OO design.

I would vote to integrate this (<=> and all).

Sven

Re: [Pharo-dev] Best practice for overwriting methods in other classes

[Marcus Denker]

> On 22 May 2015, at 07:08, Kasper Osterbye  wrote:
> 
> I have now twice in two different situations felt a need to "steal" a method
> in Nautilus and make that method an extension method in my own package. 
> 
> In situation A, I wanted to steal the #buildCommentPane to use a different
> Morph for class comments,
> In situation B, Sergio and I needed to redefine #getComments and
> #addComments:notifying: to fill out behaviour for package comments.
> 
> What is the kosher way to work and contribute in such situations? I guess it
> will also pop up in situations outside of Nautilus.
> 

Semantically, overrides are never “save” as they do not compose: two packages
overriding, which version is the correct one?

In the past people tried to e.g. add support to monticello to install the 
original method
when an override gets unloaded. But this all breaks down as soon as two packages
override the same method.

Overrides therefore should be used just for experimental code… what i do is to 
put it
on *mypackage-override so I do not forget to find a solution later that does 
not need it.

Marcus

[Pharo-dev] Format shortcut.

[Cyril Ferlicot]

Hi,

for now we have 2 different shortcuts in hard code on Pharo to format
methods: alt + shift + u and ctrl + shift + f.
I opened an issue to correct that :
https://pharo.fogbugz.com/f/cases/15584/TClassDescription-sourceCodeRefactoringMenu-and-NautilusRefactoring-buildSourceCodeShortcutsOn-need-review

I propose to keep ctrl + shift + f (like in Eclipse).

-- 
Cheers
Cyril Ferlicot

[Pharo-dev] [pharo-project/pharo-core] f3f543: 50058

[GitHub]

  Branch: refs/heads/5.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: f3f543ad9776f63e533fe3bbc8dd6bd5eb27fa86
  
https://github.com/pharo-project/pharo-core/commit/f3f543ad9776f63e533fe3bbc8dd6bd5eb27fa86
  Author: Jenkins Build Server 
  Date:   2015-05-22 (Fri, 22 May 2015)

  Changed paths:
M 
ConfigurationOfTxText.package/ConfigurationOfTxText.class/instance/symbolic 
versions/stable_.st
A 
ConfigurationOfTxText.package/ConfigurationOfTxText.class/instance/versions/version210_.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50057.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
scripts/script50058.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50057.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - 
updates/update50058.st
M 
ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
M TxText-Athens.package/TxApplicationWithToolbar.class/instance/as yet 
unclassified/openWithSpec.st
M 
TxText-Athens.package/TxAthensLayout.class/instance/geometry/textPositionAt_.st
M 
TxText-Athens.package/TxAthensLayoutLine.class/instance/accessing/commandForPosition_ifOutside_.st
M 
TxText-Athens.package/TxTextEditor.class/instance/private/recordSelectionChange_.st
M TxText-Model.package/TxBasicSpan.class/instance/accessing/lineEndSpan.st
M TxText-Model.package/TxBasicSpan.class/instance/operation/at_insert_.st
M 
TxText-Model.package/TxBasicTextPosition.class/instance/converting/selectTo_.st
M 
TxText-Model.package/TxBasicTextPosition.class/instance/private/timesToMoveRightTo_.st
M 
TxText-Model.package/TxCharacterSpan.class/instance/operation/applyAttribute_from_to_.st
M TxText-Model.package/TxCharacterStream.class/README.md
R TxText-Model.package/TxModel.class/instance/accessing/characterStream.st
R TxText-Model.package/TxModel.class/instance/accessing/cursor.st
A TxText-Model.package/TxModel.class/instance/factory 
methods/characterStream.st
A TxText-Model.package/TxModel.class/instance/factory methods/newCursor.st
A TxText-Model.package/TxModel.class/instance/factory 
methods/newSelection.st
R TxText-Model.package/TxModel.class/instance/factory-selection 
/newSelection.st
R TxText-Model.package/TxModel.class/instance/factory-selection /select.st
R TxText-Model.package/TxModel.class/instance/factory-selection 
/selectAll.st
R TxText-Model.package/TxModel.class/instance/factory-selection 
/selection.st
R TxText-Model.package/TxModel.class/instance/private/deleteFrom_to_.st
R TxText-Model.package/TxModel.class/instance/private/mergeFrom_.st
R TxText-Model.package/TxModel.class/instance/private/mergeFrom_to_.st
R TxText-Model.package/TxModel.class/instance/private/normalize.st
M TxText-Model.package/TxTextCursor.class/README.md
M 
TxText-Model.package/TxTextPosition.class/instance/accessing/linePosition_.st
M 
TxText-Styler.package/TxTextStyler.class/instance/visiting/visitMessageNode_.st
M 
TxText-Styler.package/TxTextStyler.class/instance/visiting/visitSelfNode_.st
M 
TxText-Styler.package/TxTextStyler.class/instance/visiting/visitVariableNode_.st
M 
TxText-Styler.package/extension/OCAbstractMethodScope/instance/findVariable_ifNone_.st
M TxTextTests-Model.package/TxModelTest.class/instance/running/setUp.st
M 
TxTextTests-Model.package/TxModelTest.class/instance/test-attribute/testApplyFontWithOneSplitAtEnd.st
M 
TxTextTests-Model.package/TxModelTest.class/instance/test-attribute/testApplyFontWithOneSplitAtStart.st

  Log Message:
  ---
  50058
15567 TxText Cleanup for Pharo 5.0 #4
https://pharo.fogbugz.com/f/cases/15567

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

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

[GitHub]

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