Squeak-dev February 2019

squeak-dev@lists.squeakfoundation.org

37 participants
92 discussions

Re: [squeak-dev] [Pharo-dev] Squeak and Tonel
by Eliot Miranda 17 Feb '19

17 Feb '19

On Sun, Feb 17, 2019 at 1:00 PM ducasse <stepharo(a)netcourrier.com> wrote: > Hi eliot > > What is common in your thread is that we always look like the super > emotional, or bad guys. > You never ask yourselves why Esteban left the VM mailing-list. > What is common is that I discuss technical matters (difficulties in using Tonel/git, architectural issues with developing the VM) and organizational issues (Estebans' unhelpful response regarding an option in Tonel) and you immediately personalize, do not bring up a single technical issue, and then make grand pronouncements like :this is the last email I'll send you". Laughable and sad. > > And I do not see why you cannot fork Tonel to produce your own version. > Git is about distributed projects. People do that all the time. You can > take Tonel and hack it to death > without having your hacks pushed back into Pharo and this is perfectly ok > for us. > So Esteban has the right to say no and you have the right to hack your own > version. > > If you want to have some support for porting Scorch/Sista to github and > loading you should ask > but asking it more nicely. > > About the simulation of the UI, if you do not talk to us we cannot pay > attention. > I do not see why we cannot keep a package with the image level UI for the > simulator. > Now again you are talking about collaboration but you do not talk to us > and you do not > listen to us so do not expect that people are willing to spend their free > time to help. > > > I had deep concerns that the pursuit of git integration would end up > splitting the Pharo and Squeak communities and indeed this is now in > progress. I am utterly unmotivated by the lack of cooperation, the sheer > arrogance and bullying of those that say "you will move to git/tonel or > else”, > > > This is fun to ask Pharo not to grow up to use modern technology to manage > source code under the > premisses that Squeak cannot or will not. > This is so funny how you state it. I will not comment more than that. > People around are adults and they will be able to judge by themselves. > > and considering leaving VMMaker altogether. > > > If you leave VMMaker, let us know because we will port it to Github and > make it work in Pharo. > Esteban did it several times in the past. At least this will have the > benefit to clarify the situation. > > I think that this is good that you tell us that you do not want to > cooperate with us. > This will have at least the impact to kick our ass and pay attention to > us. > > The only things that are keeping me interested are Ron Teitelbaum's Terf > and me pursuing a PhD on register allocation in the context of Sista/Scorch > with Robert Hirshfeld's group at HPI. > > Here's the kind of crap people like Ducasse throw at me: > > "Eliot > > At the end of the day I will probably ask the two phds that should work on language > design to use truffle or pypy > because let us face it we cannot work with the Pharo VM. Else we will > simply have to fork it (because we do not want to have > to jump over cuis, newspeak, squeak code constraints and I do not what) > and it will be another drama is in the pico world > of the “open” smalltalk VM. " > > I am so over this crap. > > > This is not a crap. I can restate what I said. Because of responsibility > of a research team and creating a future for students. You know I’m not > alone, I have quite some responsibility towards PhD students > of my group and yes I cannot make them fail by construction (or produce > unadequate results) > just by imposing them to use a system with far too many constraints. > > I will not ask them to work on the openSmalltalk vm directly because this > is not their responsibilities > to have to jump over newspeak ifdef and others. A job of a PhD is to be > able to brainstorm and create new ideas. Look at Stefan Marr (He is working > on SOM or Truffle). > > Now you can think that I’m an asshole, arrogant, or I do not know pick > what you want. > ***I do not care***. I do not have Diva syndrome I have responsibilities > towards people. > > I was discussing with some truffle experts and they told me that this is > can be complex. I believe it. > I would like to avoid pypy for obvious reasons. So what we will probably > do for their PhD is to see if we can use a light version of opensmalltalk. > I do not want to ask them to jump over many things that are totally useless > for them all the time. > > > PS: personnally I do not get why VMMaker would be the only project on > earth that cannot be managed using git and Pharo. > But for us the future is Git and we will continue to build on this > infrastructure. > > > Stef > > > _,,,^..^,,,_ > best, Eliot > > > -- _,,,^..^,,,_ best, Eliot

2 2

Re: [squeak-dev] [Pharo-dev] Squeak and Tonel
by Eliot Miranda 17 Feb '19

17 Feb '19

On Sun, Feb 17, 2019 at 1:22 PM ducasse <stepharo(a)netcourrier.com> wrote: > BTW Eliot, I just discovered by accident emails you sent me last week > there are full on insults . I will not forward them in this mailing-list > because it does not help. > This is not the first that you do that to me. The first time I went over > them and supported > Clément to work with you. Now I will not consider your mails anymore. > > Sorry but you cannot talk publicly about collaboration and privately > insult people that way. > > Now if you believe that I do pharo about ego then you do not understand > anything :) > And I will not try to convince you otherwise. This is my last email sent > to you. > Thank god for that. > > Stef > > On 17 Feb 2019, at 21:59, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi eliot > > What is common in your thread is that we always look like the super > emotional, or bad guys. > You never ask yourselves why Esteban left the VM mailing-list. > > And I do not see why you cannot fork Tonel to produce your own version. > Git is about distributed projects. People do that all the time. You can > take Tonel and hack it to death > without having your hacks pushed back into Pharo and this is perfectly ok > for us. > So Esteban has the right to say no and you have the right to hack your own > version. > > If you want to have some support for porting Scorch/Sista to github and > loading you should ask > but asking it more nicely. > > About the simulation of the UI, if you do not talk to us we cannot pay > attention. > I do not see why we cannot keep a package with the image level UI for the > simulator. > Now again you are talking about collaboration but you do not talk to us > and you do not > listen to us so do not expect that people are willing to spend their free > time to help. > > > I had deep concerns that the pursuit of git integration would end up > splitting the Pharo and Squeak communities and indeed this is now in > progress. I am utterly unmotivated by the lack of cooperation, the sheer > arrogance and bullying of those that say "you will move to git/tonel or > else”, > > > This is fun to ask Pharo not to grow up to use modern technology to manage > source code under the > premisses that Squeak cannot or will not. > This is so funny how you state it. I will not comment more than that. > People around are adults and they will be able to judge by themselves. > > and considering leaving VMMaker altogether. > > > If you leave VMMaker, let us know because we will port it to Github and > make it work in Pharo. > Esteban did it several times in the past. At least this will have the > benefit to clarify the situation. > > I think that this is good that you tell us that you do not want to > cooperate with us. > This will have at least the impact to kick our ass and pay attention to > us. > > The only things that are keeping me interested are Ron Teitelbaum's Terf > and me pursuing a PhD on register allocation in the context of Sista/Scorch > with Robert Hirshfeld's group at HPI. > > Here's the kind of crap people like Ducasse throw at me: > > "Eliot > > At the end of the day I will probably ask the two phds that should work on language > design to use truffle or pypy > because let us face it we cannot work with the Pharo VM. Else we will > simply have to fork it (because we do not want to have > to jump over cuis, newspeak, squeak code constraints and I do not what) > and it will be another drama is in the pico world > of the “open” smalltalk VM. " > > I am so over this crap. > > > This is not a crap. I can restate what I said. Because of responsibility > of a research team and creating a future for students. You know I’m not > alone, I have quite some responsibility towards PhD students > of my group and yes I cannot make them fail by construction (or produce > unadequate results) > just by imposing them to use a system with far too many constraints. > > I will not ask them to work on the openSmalltalk vm directly because this > is not their responsibilities > to have to jump over newspeak ifdef and others. A job of a PhD is to be > able to brainstorm and create new ideas. Look at Stefan Marr (He is working > on SOM or Truffle). > > Now you can think that I’m an asshole, arrogant, or I do not know pick > what you want. > ***I do not care***. I do not have Diva syndrome I have responsibilities > towards people. > > I was discussing with some truffle experts and they told me that this is > can be complex. I believe it. > I would like to avoid pypy for obvious reasons. So what we will probably > do for their PhD is to see if we can use a light version of opensmalltalk. > I do not want to ask them to jump over many things that are totally useless > for them all the time. > > > PS: personnally I do not get why VMMaker would be the only project on > earth that cannot be managed using git and Pharo. > But for us the future is Git and we will continue to build on this > infrastructure. > > > Stef > > > _,,,^..^,,,_ > best, Eliot > > > -- _,,,^..^,,,_ best, Eliot

1 0

The Trunk: Collections-dtl.821.mcz
by commits＠source.squeak.org 17 Feb '19

17 Feb '19

David T. Lewis uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-dtl.821.mcz ==================== Summary ==================== Name: Collections-dtl.821 Author: dtl Time: 16 February 2019, 6:18:27.925895 pm UUID: 9bfa29b3-5e9f-4c61-b19b-e0bb05403589 Ancestors: Collections-nice.820 Classes are expected to be unique in the system, but in some cases (e.g. Magma) it is also useful to expect a proxy for a class to test equivalent to the actual class. Therefore, in SequenceableCollection>>= use #= rather than #== for the class comparison. =============== Diff against Collections-nice.820 =============== Item was changed: ----- Method: SequenceableCollection>>= (in category 'comparing') ----- = otherCollection "Answer true if the receiver is equivalent to the otherCollection. First test for identity, then rule out different class and sizes of collections. As a last resort, examine each element of the receiver and the otherCollection." self == otherCollection ifTrue: [^ true]. + self class = otherCollection class ifFalse: [^ false]. - self class == otherCollection class ifFalse: [^ false]. ^ self hasEqualElements: otherCollection!

1 0

The Inbox: Collections-dtl.821.mcz
by commits＠source.squeak.org 17 Feb '19

17 Feb '19

David T. Lewis uploaded a new version of Collections to project The Inbox: http://source.squeak.org/inbox/Collections-dtl.821.mcz ==================== Summary ==================== Name: Collections-dtl.821 Author: dtl Time: 16 February 2019, 6:18:27.925895 pm UUID: 9bfa29b3-5e9f-4c61-b19b-e0bb05403589 Ancestors: Collections-nice.820 Classes are expected to be unique in the system, but in some cases (e.g. Magma) it is also useful to expect a proxy for a class to test equivalent to the actual class. Therefore, in SequenceableCollection>>= use #= rather than #== for the class comparison. =============== Diff against Collections-nice.820 =============== Item was changed: ----- Method: SequenceableCollection>>= (in category 'comparing') ----- = otherCollection "Answer true if the receiver is equivalent to the otherCollection. First test for identity, then rule out different class and sizes of collections. As a last resort, examine each element of the receiver and the otherCollection." self == otherCollection ifTrue: [^ true]. + self class = otherCollection class ifFalse: [^ false]. - self class == otherCollection class ifFalse: [^ false]. ^ self hasEqualElements: otherCollection!

3 2

The Trunk: Collections-nice.820.mcz
by commits＠source.squeak.org 17 Feb '19

17 Feb '19

Nicolas Cellier uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-nice.820.mcz ==================== Summary ==================== Name: Collections-nice.820 Author: nice Time: 12 February 2019, 11:56:35.262017 pm UUID: bb383133-067c-4133-987b-c481a7de69c7 Ancestors: Collections-ul.819, Collections-cbc.813 Definitively abandon SequenceableCollection equality tests based on equal species. Old behaviour can still be obtained thru hasEqualElements: but the default is to not try to support such trans-class equality feature because it is much too complex. Particularly Interval are no more equal to Arrays with same sequence. We can thus optimize hash a bit more and fix the old bugs of equa objects with different hashes. Merge Collections-cbc.813 for this and rehashAll in postscript. There are not so many classes concerned by this change, mainly RunArray, Interval and LinkedList: Collection withAllSubclasses select: [:e | [e basicNew species ~= e] on: Error do: [false]] -> an OrderedCollection(WeakRegistry LinkedList Interval ByteCharacterSet CharacterSetComplement LazyCharacterSet WideCharacterSet ShortRunArray Semaphore Mutex TextLineInterval WeakArray Monitor MCVersionName ByteSymbol WideSymbol) We will have to change the tests that rely on such equality. =============== Diff against Collections-ul.819 =============== Item was changed: ----- Method: FloatArray>>= (in category 'comparing') ----- = aFloatArray - | length | <primitive: 'primitiveEqual' module: 'FloatArrayPlugin'> + ^super = aFloatArray! - aFloatArray class = self class ifFalse: [^ false]. - length := self size. - length = aFloatArray size ifFalse: [^ false]. - 1 to: self size do: [:i | (self at: i) - = (aFloatArray at: i) ifFalse: [^ false]]. - ^ true! Item was changed: ----- Method: Interval>>= (in category 'comparing') ----- = anObject - ^ self == anObject + or: [anObject isInterval + ifFalse: [super = anObject] + ifTrue: + [start = anObject first + and: [step = anObject increment + and: [self last = anObject last]]]]! - ifTrue: [true] - ifFalse: [anObject isInterval - ifTrue: [start = anObject first - and: [step = anObject increment - and: [self last = anObject last]]] - ifFalse: [super = anObject]]! Item was changed: ----- Method: Interval>>hash (in category 'comparing') ----- hash "Hash is reimplemented because = is implemented." + ^((start hash hashMultiply bitXor: self last hash) hashMultiply + bitXor: self size)! - - ^(((start hash bitShift: 2) - bitOr: stop hash) - bitShift: 1) - bitOr: self size! Item was changed: ----- Method: RunArray>>= (in category 'comparing') ----- = anObject + self == anObject ifTrue: [^ true]. - "Test if all my elements are equal to those of anObject" - ^anObject class == self class + and: - ifTrue: "Faster test between two RunArrays" [(runs hasEqualElements: anObject runs) + and: [values hasEqualElements: anObject values]]! - and: [values hasEqualElements: anObject values]] - ifFalse: - [anObject isCollection and: [self hasEqualElements: anObject]]! Item was changed: ----- Method: SequenceableCollection>>= (in category 'comparing') ----- = otherCollection "Answer true if the receiver is equivalent to the otherCollection. + First test for identity, then rule out different class and sizes of - First test for identity, then rule out different species and sizes of collections. As a last resort, examine each element of the receiver and the otherCollection." self == otherCollection ifTrue: [^ true]. + self class == otherCollection class ifFalse: [^ false]. - self species == otherCollection species ifFalse: [^ false]. ^ self hasEqualElements: otherCollection! Item was changed: ----- Method: Symbol>>= (in category 'comparing') ----- = aSymbol "Compare the receiver and aSymbol." self == aSymbol ifTrue: [^ true]. + aSymbol isSymbol ifTrue: [^ false]. - self class == aSymbol class ifTrue: [^ false]. "Use String comparison otherwise" ^ super = aSymbol! Item was changed: + (PackageInfo named: 'Collections') postscript: 'Character initializeClassificationTable. + HashedCollection rehashAll.'! - (PackageInfo named: 'Collections') postscript: 'Character initializeClassificationTable'!

7 7

Logarithmic interval ?
by karl ramberg 15 Feb '19

15 Feb '19

Hi, Does anybody know of a logarithmic interval implementation in Squeak where the steps in the interval go by logarithmic scale instead of linear ? Best, Karl

2 8

Call for Participation: <Programming> 2019
by Fabio Niephaus 15 Feb '19

15 Feb '19

<Programming> 2019 : The Art, Science, and Engineering of Programming April 1-4, 2019, Genova, Italy http://2019.programming-conference.org The International Conference on the Art, Science, and Engineering of Programming is a new conference focused on programming topics including the experience of programming. We have named it <Programming> for short. The conference is co located with the 12th European Lisp Symposium, several workshops, a poster and a demo session and the student research competition. Registration: February 25, 2019 (Early Registration Deadline) Register: https://2019.programming-conference.org/attending/Registration Venue: Hotel Bristol Palace, Genova https://2018.splashcon.org/venue/splash-2018-venue Keynotes: Heather Miller (Carnegie Mellon University) Lars Bak (Toitware Aps) Workshops PX/19 ProWeb’19 MiniPLOP ICW: Interconnecting Code Workshop MoreVMs’19 Salon des Refusés CoCoDo VPT Co-located Symposia 12th European Lisp Symposium (ELS) Invited Talks MoreVMs’19: Guilherme Ottoni (Facebook) ELS: Matthew Flatt (University of Utah) ELS: Stefan Monnier (Université de Montréal) ELS: Christophe Rhodes (Goldsmiths, University of London) ******************************************************** ORGANIZATION ******************************************************** General Chair: Davide Ancona, University of Genova Local Organizing Chair: Elena Zucca, University of Genova Program Chair: Matthew Flatt, University of Utah Organizing Committee: Walter Cazzola (Workshops Co-Chair), Università degli Studi di Milano Luca Franceschini (Student Volunteer Co-Chair), DIBRIS, University of Genova, Italy Philipp Haller (Student Research Competition Co-chair), KTH Royal Institute of Technology, Sweden Maurizio Leotta (Poster Co-Chair), DIBRIS, University of Genova, Italy Stefan Marr (Workshops Co-Chair), University of Kent Toni Mattis (Student Volunteer Co-Chair), Hasso Plattner Institute, University of Potsdam, Germany Ana Milanova (Student Research Competition Co-Chair), Rensselaer Polytechnic Institute Fabio Niephaus (Publicity Co-Chair), Hasso Plattner Institute, University of Potsdam Tobias Pape (Web Technology Chair), Hasso Plattner Institute, University of Potsdam Manuel Rigger (Demo Chair), Johannes Kepler University Linz, Austria Coen De Roover (Poster Co-Chair), Vrije Universiteit Brussel, Belgium Guido Salvaneschi (Publicity Co-Chair), TU Darmstadt, Germany Program Committee: Anya Helene Bagge, University of Bergen Mehdi Bagherzadeh, Oakland University Walter Cazzola, Università degli Studi di Milano Ravi Chugh, University of Chicago Joeri De Koster, Vrije Universiteit Brussel Christos Dimoulas, Northwestern University Susan Eisenbach, Imperial College London Richard P. Gabriel, Dream Songs, Inc. & HPI Jeremy Gibbons, University of Oxford Michael Greenberg, Pomona College Philipp Haller, KTH Royal Institute of Technology Robert Hirschfeld, HPI, University of Potsdam Eunsuk Kang, Carnegie Mellon University Stephen Kell, University of Cambridge Stefan Marr, University of Kent Tamara Rezk, Inria Joshua Sunshine, Carnegie Mellon University Steffen Zschaler, King's College London ******************************************************** <Programming> 2019 is kindly supported by AOSA ******************************************************** For more information, visit http://2019.programming-conference.org

1 0

The Inbox: FFI-Tests-KenD.12.mcz
by commits＠source.squeak.org 14 Feb '19

14 Feb '19

A new version of FFI-Tests was added to project The Inbox: http://source.squeak.org/inbox/FFI-Tests-KenD.12.mcz ==================== Summary ==================== Name: FFI-Tests-KenD.12 Author: KenD Time: 14 February 2019, 10:12:49.844066 am UUID: 6fc0c2f7-6dc8-42ca-b1af-c567ba756a07 Ancestors: FFI-Tests-KenD.11 Float comparison refinement: testGenericDoubleCall2 =============== Diff against FFI-Tests-KenD.11 =============== Item was changed: ----- Method: FFIPluginTests>>testGenericDoubleCall2 (in category 'simple tests') ----- testGenericDoubleCall2 "Test using generic FFI spec" | result | + result := FFITestLibrary + ffiTestDoubles9: 1.0 + d: 2.0 + d: 3.0 + d: 4.0 + d: 5.0 + d: 6.0 + d: 7.0 + d: 8.0 + d: 9.0. + self assert: (result closeTo: 45.0)! - result := FFITestLibrary ffiTestDoubles9: 1.0 d: 2.0 d: 3.0 d: 4.0 d: 5.0 d: 6.0 d: 7.0 d: 8.0 d: 9.0. - self assert: result = 45.0!

1 0

The Trunk: Monticello-nice.695.mcz
by commits＠source.squeak.org 14 Feb '19

14 Feb '19

Nicolas Cellier uploaded a new version of Monticello to project The Trunk: http://source.squeak.org/trunk/Monticello-nice.695.mcz ==================== Summary ==================== Name: Monticello-nice.695 Author: nice Time: 14 February 2019, 1:46:52.89164 pm UUID: 1933b192-0ab2-bc46-af47-b06f031516b9 Ancestors: Monticello-nice.694 Add a utility for finding last merge of two versions. A use case: | mcw allBF540 | mcw := (MCPackage named: 'Monticello') workingCopy ancestry. allBF540 := (mcw allAncestors select: [:e | e versionName = 'Monticello-bf.540' ]) asArray. ^mcw lastMergeOf: allBF540 first and: allBF540 last. Note: implementation is sub-optimal but just works =============== Diff against Monticello-nice.694 =============== Item was added: + ----- Method: MCAncestry>>lastMergeOf:and: (in category 'progeny') ----- + lastMergeOf: aNode and: anotherNode + "Find the last merge of two Nodes starting from myself. + Answer nil if there is none. + Note: there might have been several merges, in which case we take the common merge of merges. + Example: if c is a merge of a and b, d is also a merge of a and b, and e is a merge of c and d, then asnwer e." + + | common | + (self hasAncestor: aNode) ifFalse: [^nil]. + (self hasAncestor: anotherNode) ifFalse: [^nil]. + common := ancestors collect: [:e | e lastMergeOf: aNode and: anotherNode] as: Set. + common remove: nil ifAbsent: []. + common size = 1 ifTrue: [^common anyOne]. + ^self + !

1 0

The Trunk: Monticello-nice.694.mcz
by commits＠source.squeak.org 14 Feb '19

14 Feb '19

Nicolas Cellier uploaded a new version of Monticello to project The Trunk: http://source.squeak.org/trunk/Monticello-nice.694.mcz ==================== Summary ==================== Name: Monticello-nice.694 Author: nice Time: 13 February 2019, 5:10:42.293481 pm UUID: 32251c33-6f20-4c4f-8e6b-b0bb32019731 Ancestors: Monticello-tpr.693 Warn about false ancestors thru bold-red-UI A false ancestor is a package that has same name-author.versionNumber than a true ancestor, but not the same id (UUID). Generally, its contents will be different from the true ancestor. It is vital to know this information, particularly when browsing an inbox, otherwise we could override a true ancestor when moving/copying this package to repository that already contains the true one. Right now, the warning is only for selected version in the versionList. It's because the list is built from version names only and ignore ids. Most actions will operate on selected version though, so it's better than nothing. =============== Diff against Monticello-tpr.693 =============== Item was changed: MCVersionInspector subclass: #MCRepositoryInspector + instanceVariableNames: 'repository packageNames versionNames selectedPackage selectedVersion order versionInfo loaded newer inherited inheritedId' - instanceVariableNames: 'repository packageNames versionNames selectedPackage selectedVersion order versionInfo loaded newer inherited' classVariableNames: 'BrowseBranchedVersionsSeparately Order' poolDictionaries: '' category: 'Monticello-UI'! Item was changed: ----- Method: MCRepositoryInspector>>identifyLoadedAndInherited: (in category 'morphic ui') ----- identifyLoadedAndInherited: aMCWorkingCopy | seen | seen := Set new. aMCWorkingCopy ancestors do: [ : ancestor | loaded add: ancestor versionName. seen add: ancestor. ancestor ancestorsDoWhileTrue: [ : heir | (seen includes: heir) ifTrue: [ false ] ifFalse: [ inherited add: heir versionName. + inheritedId add: heir id. seen add: heir. true ] ] ]! Item was changed: ----- Method: MCRepositoryInspector>>initializeEmphasis (in category 'initialize-release') ----- initializeEmphasis inherited := Set new. + inheritedId := Set new. loaded := Set new! Item was added: + ----- Method: MCRepositoryInspector>>selectedVersionIsFalseAncestor (in category 'testing') ----- + selectedVersionIsFalseAncestor + "Answer true if selectedVersion is a false ancestor of working copy. + An ancestor of working copy that has same name, but not same id is a false ancestor!!" + ^(selectedVersion notNil + and: [(inherited includes: selectedVersion versionName) + and: [(inheritedId includes: self versionInfo id) not]])! Item was added: + ----- Method: MCRepositoryInspector>>summary (in category 'morphic ui') ----- + summary + self selectedVersionIsFalseAncestor + ifTrue: [^ (Text string: 'Beware, this is a false ancestor whose name conflicts with a true one\' withCRs attributes: {TextColor red. TextEmphasis bold}) + , super summary]. + ^ super summary! Item was changed: ----- Method: MCRepositoryInspector>>versionHighlight: (in category 'morphic ui') ----- + versionHighlight: aMCVersionName - versionHighlight: aMCVersionName inherited ifNil: [inherited := #()]. + inheritedId ifNil: [inheritedId := #()]. + (selectedVersion notNil + and: [selectedVersion = aMCVersionName + and: [self selectedVersionIsFalseAncestor]]) + ifTrue: ["False ancestor might be dangerous, signal them in red" + ^ Text string: aMCVersionName attributes: {TextColor red. TextEmphasis bold}]. + ^ Text - ^Text string: aMCVersionName + attribute: (TextEmphasis new + emphasisCode: ((loaded includes: aMCVersionName) + ifTrue: ["underlined" 4] + ifFalse: [(inherited includes: aMCVersionName) + ifTrue: [0] + ifFalse: ["bold" 1]]))! - attribute: (TextEmphasis new emphasisCode: ( - ((loaded includes: aMCVersionName) ifTrue: [ 4 "underlined" ] - ifFalse: [ (inherited includes: aMCVersionName) - ifTrue: [ 0 ] - ifFalse: [ 1 "bold" ] ])))! Item was changed: ----- Method: MCRepositoryInspector>>versionSelection: (in category 'morphic ui') ----- versionSelection: aNumber selectedVersion := version := nil. aNumber isZero ifFalse: [ selectedVersion := (self versionList at: aNumber) asString ]. + self selectedVersionIsFalseAncestor ifTrue: [self changed: #versionList]. self changed: #versionSelection ; changed: #summary ; changed: #hasVersion!

3 3

← Newer
1
2
3
4
5
6
7
8
9
10
Older →