Squeak-dev May 2018

squeak-dev@lists.squeakfoundation.org

44 participants
189 discussions

Re: [squeak-dev] [Pharo-users] Personal Programming onPharo
by H. Hirzel 09 May '18

09 May '18

On 5/6/18, Trygve Reenskaug <trygver(a)ifi.uio.no> wrote: > I'm working on a programing paradigm and IDE for the personal programmer > who wants to control his or her IoT. The size of the target audience I > have in mind is >100 million. I gave up Squeak long ago as a platform > because they obsolete my code faster than I can write it. I have now > frozen Squeak 3.10.2 and hope its runtime will survive until I find a > better foundation. My hope is that Pharo has a stable kernel that I can > build on. Hello Tryge Good to see that you reconsider to use Smalltalk in 2018, this time Pharo. Am I assuming correctly that you want to continue to work on your IDE which the supports the DCI (Data-Context-Interaction) programming style [1]? The IDE was called "BabyIDE" [2]. In 2015 you wrote to the Squeak mailing list that you are abandoning Squeak (Squeak 3.8, 4.5 or 4.6 at that time and Smalltalk as a whole) in favour of JavaScript, a mainstream language. That you now at least reconsider to use Smalltalk (Pharo) is an interesting result as it reinforces the idea that doing things the Smalltalk way is more promising than going for JavaScript directly [6]. As for loading the BabyIDE into Squeak: It is noteworthy that after 10 years (done around Squeak version 3.8) of maintaining a fork the Squeakland (Etoys) image has been merged back into Squeak 6.0a trunk. [5] I could actually load some of your tools last year into Squeak 6.0a with very modest fixes last year. [2]. It seems that splitting your IDE enhancements into different parts which can be treated independently will probably help. And in addition helpful would be IMHO to write HOW you construct these tools and WHY you do it. These will help people to maintain your code even if the underlying system changes. It seems worthwhile to try out how it goes with the most recent Squeak version, Squeak 6.0a trunk [8]. Another option is to wait a few months and look for the bootstrap version of Pharo 7. All the code is in readable format on github and various types of image files may be built build from it [7]. And the third option is to check out if Cuis (the third Smalltalk which runs on the OpenSmalltalk [3] VM) suits your needs. [4] Kind regards Hannes Hirzel ------------------- [1] Data-Context-Interaction http://wiki.squeak.org/squeak/6048 [2] BabySRE http://wiki.squeak.org/squeak/2550 [3] http://www.opensmalltalk.org/ [4] Cuis Smalltalk https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev ; there is a Cuis mailing list. [5] Etoys in 2017 http://wiki.squeak.org/squeak/6531 [6] Of course these days JavaScript cannot be avoided. But it is preferable to generate it with a Smalltalk tool. [7] The file format used in Pharo 7 is called Tonel (no exclamation marks!) [8] Squeak 6.0a trunk download http://files.squeak.org/6.0alpha/

3 2

Re: [squeak-dev] [Pharo-users] Personal Programming onPharo
by H. Hirzel 09 May '18

09 May '18

On 5/9/18, Trygve Reenskaug <trygver(a)ifi.uio.no> wrote: > Of course not. But one of my goals is that future dynabooks will be > backwards compatible. Recent discussions have shown me that this goal is > a research project. > --Trygve Indeed [1]. And a very interesting one! Found and read your overview http://folk.uio.no/trygver/themes/Personal/PP-NIK.pdf And also the more elaborate draft of a description (50 pages) [2] http://folk.uio.no/trygver/themes/Personal/pp-index.html links to http://folk.uio.no/trygver/themes/Personal/PersonalProgramming.233.zip For my personal programming needs in Squeak so far I realized that the 'data' part is the easiest one to tackle in terms of backward compatibility. And some success in converting data to code forth and back to ease compatibility. It would be nicer of course to have a homoiconic notation [3] but still very doable. In particular as the new VMs have lifted the size constraint for the source code of in methods. --Hannes [1] An example is about the work involved to get a 17 year old 'Dynamic essay' from Squeak 3.2 to read in properly into a Squeak 6.0a trunk image http://forum.world.st/Dynamic-essay-project-MorphLayoutArticle-on-Bob-s-Sup… Quite some effort and not a full result yet... Though Squeak has some mechanisms to update classes and objects. In that thread Edgar de Cleene outlined the idea of a recursive DNU mechanism to check out earlier messages from the web http://forum.world.st/Dynamic-essay-project-MorphLayoutArticle-on-Bob-s-Sup… Needs much more elaboration ... ------------------- [2] Abstract Computer programming celebrates its platinum jubilee on the 21st of June, 2018. Exactly 70 years ago, the world's first programmer wrote the world's first program and then stored and executed it in the world's first stored program computer; affectionately known as Baby. The solitary Baby has morphed into billions of computers that are loosely connected into a single, global machine. Baby's control panel has morphed into graphical user interfaces (GUI) that empower everybody to augment their intellect. The consequences are deeply radical for individuals and society alike. A significant side effect of the GUI is that the computer has faded into the background and the user focuses on the immediate needs. We present DCI, a new programming paradigm that targets structures of communicating computers. Its goal is readable code that is so intuitive that everybody can grok it and so comprehensive that expert programmers will enjoy using it. DCI programming has been tested on real-life problems. A set of controlled experiments showed that DCI code is more readable than Java code. A new programming environment, BabyIDE, targets the single, global machine. Different GUIs support programmers having different mental models depending on their interests and proficiency. An MVC system architecture makes the program fade into the background and lets the user concentrate on satisfying his or her immediate needs. My approach is experimental. Smalltalk's universe of objects imitates the single, global machine and is my proving ground.We give two examples: one for experts and another for novices. A video1 illustrates the novice IDE. Our approach is experimental. The universe of objects found in Smalltalk's image imitates a computer network and is our proving ground. Squeak 3.10.2 is our laboratory where we experiment with various versions of BabyIDE. A great deal of work remains to make BabyIDE generally available and we are searching for a trailblazer who will take charge of it and take it out into the world. Keywords: Personal Programming, Novice Programming, Single Global Machine, IOT, Smart Home, MVC, DCI, BabyIDE, Smalltalk, Object Orientation [3] http://goran.krampe.se/2016/07/19/spry-is-a-smalltalk/ > On 09.05.2018 12:19, Marcus Denker wrote: >>> >>> >>>> I go back to Alan Kay's vision of a Dynabook: A/personal/computer >>>> for children of all ages. It should contain all its owner's >>>> /personal/data, including his or her/personal/programs, as they >>>> evolve through the years. Continuity is a must; the owner shall >>>> never loose data. >>>> >>> >> >> Do you really expect that the dynabook will be 100% backward >> compatible to Smalltalk-80? >> >> Marcus > > -- > > /The essence of object orientation is that objects collaborateto achieve > a goal. / > Trygve Reenskaug mailto: trygver(a)ifi.uio.no <mailto:%20trygver@ifi.uio.no> > Morgedalsvn. 5A http://folk.uio.no/trygver/ > N-0378 Oslo http://fullOO.info > Norway Tel: (+47) 22 49 57 27 > >

1 0

The Trunk: System-mt.1024.mcz
by commits＠source.squeak.org 09 May '18

09 May '18

Marcel Taeumel uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-mt.1024.mcz ==================== Summary ==================== Name: System-mt.1024 Author: mt Time: 9 May 2018, 8:36:00.223271 am UUID: 74d2ef0a-9d9a-2847-a108-68482bd91da4 Ancestors: System-mt.1023 Updates code comments and some code formatting. =============== Diff against System-mt.1023 =============== Item was changed: UserInterfaceTheme subclass: #CommunityTheme instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'System-Support'! + !CommunityTheme commentStamp: 'rhi 5/5/2018 09:27' prior: 0! + A dark theme designed by members of the Squeak community.! - !CommunityTheme commentStamp: 'mt 7/26/2016 16:22' prior: 0! - A dark theme designed by members the Squeak community such as Karl Ramberg, Chris Muller, and Marcel Taeumel.! Item was changed: Object subclass: #UserInterfaceTheme instanceVariableNames: 'properties name next ignoreApply lastScaleFactor' classVariableNames: 'All Current Default' poolDictionaries: '' category: 'System-Support'! + !UserInterfaceTheme commentStamp: 'rhi 5/5/2018 09:18' prior: 0! + A UserInterfaceTheme is a dictionary of preferred visual properties; colors, borderStyles, borderWidths, fonts, forms, etc. used to color and style the IDE. - !UserInterfaceTheme commentStamp: 'tpr 9/25/2017 11:59' prior: 0! - A UserInterfaceTheme is a dictionary of preferred visual-properties; colors, borderStyles, borderWidths, fonts, forms, etc. used to color and style the IDE. + Accessing the Theme + To access the proper UserInterfaceTheme instance for an object, send it #userInterfaceTheme. The default implementation on Object returns an instance of UserInterfaceThemeRequest that provides a lightweight, clean proxy of the actual theme in use by the IDE at the current time. To do anything more sophisticated than basic queryinh and setting of properties, you must ask the proxy for the actual theme by sending #theme. - Accessing The Theme - To access the proper UserInterfaceTheme instance for an object, send it #userInterfaceTheme. The default implementation on Object provides the an instance of UserInterfaceThemeRequest that provides a lightweight, clean proxy of the actual theme in-use by the IDE at the current time. To do anything more sophisticated than basic query and setting of properties you must ask the proxy for the actual theme by sending #theme. + Customizing the Theme + We can ask the #userInterfaceTheme for the value of any visual property by name: - Customizing The Theme - We can ask the userInterfaceTheme for the value of any visual-property, by name: mySystemWindow userInterfaceTheme closeBoxImage + Initially that would answer nil, which causes the legacy code to use whatever default it used so far. To override various visual properties of any kind of object, the #set:for:to: message can be used, for example: - Initially that would answer nil, which causes the legacy code to use whatever default it's always used. To override various visual-properties of any kind of object, the #set: for: to: message can be used. For example, myUserInterfaceTheme set: #closeBoxImage for: SystemWindow to: MenuIcons smallCancelIcon Now the closeBoxImage message will answer the MenuIcons icon instead of nil. Alternatively, values may be derived based on other values in the theme, as in: myUserInterfaceTheme set: #color for: FillInTheBlankMorph + to: { MenuMorph->#color. #twiceDarker } - to: { MenuMorph->#color. #twiceDarker } + This makes FillInTheBlankMorph use the same color as a MenuMorph but #twiceDarker, providing a clean way to build coherent sets of colors within a theme. SystemWindow's code can be changed to use the expression above to access elements of the theme. - This would make FillInTheBlankMorph use the same color as a MenuMorph but twiceDarker, providing a clean way to build coherent seets of colors within a theme. SystemWindow's code can be changed to use the expression above to access elements of the theme. Upgrading Legacy Code + Following the introduction of this class, various client code all around the system must be modified to access it. This variety of legacy code uses a variety of methods to specify their visual properties: - Following the introduction of this class, various client code all around the system must be modified to access it. This variety of legacy code uses a variety of methods to specify their visual properties: 1) a hard-coded values. 2) a values derived from some other value. 3) providing local storage for a settable value which can be nil. 4) providing local storage for a settable value which is expected to always have a particular valid value (never nil). + The requirement, for each case, is to let the value be overridden. - The requirement, for each case, is to let the value be overridden. The solution for each of the above should be handled respectively to the above list, as follows: + 1) Check the #userInterfaceTheme, if that property returns nil, use the legacy hard-coded value. (see example: SystemWindow>>#createCloseBox). - 1) Check the userInterfaceTheme, if that property returns nil, use the legacy hard-coded value. (see example: SystemWindow>>#createCloseBox). 2) Nothing to do -- simply perform the same derivation on the result of (1). + 3) Check the local storage, if present, use it. If nil, then check the #userInterfaceTheme, if it has this property present, use it, else return nil. + 4) Check the #userInterfaceTheme, if the property is not nil, use it, otherwise use the local value. - 3) Check the local storage, if present, use it. If nil, then check the userInterfaceTheme, if it has this property present, use it, else return nil. - 4) Check the userInterfaceTheme, if the property is not nil, use it, otherwise use the local value. Tool Support + If a new access to #userInterfaceTheme is added to the code, be sure to add the property and its description to the #themeSettings for that class. See implementors of #themeSettings for examples.! - If a new access to #userInterfaceTheme is added to the code, be sure to add the property and its description to the #themeSettings for that class. See implementors of #themeSettings for examples.! Item was changed: ----- Method: UserInterfaceTheme class>>allThemeProperties (in category 'tools') ----- allThemeProperties + "Answer an Array of 3-element Arrays. Each inner Array holds the information needed to present a theme editor tool; the property name, category, and description." + + "self allThemeProperties" + + ^ Array streamContents: [:stream | + self allThemePropertiesDo: [:cls :prop | + stream nextPut: {cls}, prop]]! - "Answer an Array of 3-element Array's. Each inner Array are the information needed to present a Theme editor tool; the property name, category, and description. - - self allThemeProperties" - - ^ Array streamContents: - [ : stream | self allThemePropertiesDo: [ : cls : prop | stream nextPut: {cls}, prop ]]! Item was changed: ----- Method: UserInterfaceTheme class>>allThemes (in category 'accessing') ----- allThemes + ^ All ifNil: [All := IdentitySet new]! Item was changed: ----- Method: UserInterfaceTheme class>>cleanUp: (in category 'initialize-release') ----- cleanUp: aggressive aggressive ifTrue: [ All := nil. + SqueakTheme + create; + createDuller. + SolarizedTheme + createDark; + createLight. - SqueakTheme create; createDuller. - SolarizedTheme createDark; createLight. MonokaiTheme createDark. CommunityTheme createDark. TrimTheme create].! Item was changed: ----- Method: UserInterfaceTheme class>>clientClassesToReapply (in category 'private') ----- clientClassesToReapply "All client classes plus their unique subclasses." + ^ IdentitySet new in: [:result | + self clientClasses do: [:cc | + cc withAllSubclassesDo: [:sc | + result add: sc]]. + result]! - ^ IdentitySet new in: [:result | self clientClasses do: [:cc | cc withAllSubclassesDo: [:sc | - result add: sc]]. result] - ! Item was changed: ----- Method: UserInterfaceTheme class>>current: (in category 'accessing') ----- current: aUserInterfaceTheme "Replace the current system theme with aUserInterfaceTheme." + + Current := aUserInterfaceTheme. + "Notify?"! - Current := aUserInterfaceTheme - "Notify?"! Item was changed: ----- Method: UserInterfaceTheme class>>default (in category 'accessing') ----- default + ^ Default ifNil: [Default := self new + name: 'Autogenerated Default'; + yourself]! - ^ Default ifNil: [Default := self new name: 'Autogenerated Default'; yourself]! Item was changed: ----- Method: UserInterfaceTheme class>>default: (in category 'accessing') ----- default: aUserInterfaceTheme + Default := aUserInterfaceTheme.! Item was changed: ----- Method: UserInterfaceTheme class>>named: (in category 'initialize-release') ----- named: aString + ^ self allThemes detect: [:ea | ea name = aString] + ifNone: [self new + name: aString; + register]! - ifNone: [self new name: aString; register]! Item was changed: ----- Method: UserInterfaceTheme class>>propertiesForCategory: (in category 'tools') ----- propertiesForCategory: categoryName + + ^ self allThemeProperties select: [:each | each third = categoryName]! - ^ self allThemeProperties select: [ : each | each third = categoryName ]! Item was changed: ----- Method: UserInterfaceTheme class>>propertiesForClass: (in category 'tools') ----- propertiesForClass: aClass + + ^ self allThemeProperties select: [:each | each first == aClass]! - ^ self allThemeProperties select: [ : each | each first = aClass ]! Item was changed: Object subclass: #UserInterfaceThemeRequest instanceVariableNames: 'target theme' classVariableNames: '' poolDictionaries: '' category: 'System-Support'! + !UserInterfaceThemeRequest commentStamp: 'rhi 5/5/2018 09:30' prior: 0! + To be able to use a UserInterfaceTheme as a container of fairly arbitrary properties whilst making it seem like we are sending regular messages as a way of accessing those properties, we can handle #doesNotUnderstand: and check the name of the message not understood against our property list. This is clever, devious, interesting, and may confuse users until they get to see an explanation like this. - !UserInterfaceThemeRequest commentStamp: 'mt 9/23/2017 10:37' prior: 0! - In order to be able to use a UserInterfaceTheme as a container of fairly arbitrary properties whilst making it seem like we are sending regular messages as a way of accessing those properties we can handle the dNU: and check the not understood message name against our property list. This is clever, devious, interesting and may confuse users until they get to see an explanation like this. Answer nil or a value for the property specified by aMessage's #selector. Searching for the property proceeds by + a) searching my dictionary for a key made up of an Association with a key of the class of the 'client' and a value of the message name. For example SimpleButtonMorph->#borderColor + b) searching again for a key made from the superclass(es) of the client - e.g. RectangleMorph->borderColor and then if required BorderedMorph->#borderColor etc. - a) searching my dictionary for a key made up of an Association with a key of the class of the 'client' and a value of the message name. For example SimpleButtonMorph->borderColor - b) searching again for a key made from the superclass(es) of the client - e.g. RectangleMorph->borderColor and then if required BorderedMorph->borderColor etc. c) if there is a linked theme, search it in the same manner. + As an extreme example, consider a basic theme with a linked theme specific to buttons: - As an extreme example, consider a basic theme with a linked theme specifically for buttons. mySimpleButtonMorph borderColor + ... would search the basic theme for SimpleButtonMorph->#borderColor, the superclass equivalents as in b) above, then search the linked theme for SimpleButtonMorph->#borderColor and (hopefully) find something meaningful.! - ... would search the basic theme for SimpleButtonMorph->borderColor, the superclass equivalents as in b) above, then search the linked theme for SimpleButtonMorph->borderColor and, we hope, find something meaningful.! Item was changed: ----- Method: UserInterfaceThemeRequest>>doesNotUnderstand: (in category 'lookup') ----- doesNotUnderstand: aMessage + "Look up the visual attribute specified by aMessage's #selector in the current theme for the current target object." - "Look up the visual-attribute specified by aMessage's #selector in the current theme for the current target object." aMessage numArgs = 0 ifTrue: [ ^ (self theme get: self target class -> aMessage selector) ifNil: [(self theme respondsTo: aMessage selector) ifTrue: [self theme perform: aMessage selector] + ifFalse: [nil "unset property"]]]. - ifFalse: [nil "means unset property"]]]. ^ self theme perform: aMessage selector withArguments: aMessage arguments.!

2 2

The Trunk: System-mt.1025.mcz
by commits＠source.squeak.org 09 May '18

09 May '18

Marcel Taeumel uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-mt.1025.mcz ==================== Summary ==================== Name: System-mt.1025 Author: mt Time: 9 May 2018, 9:23:01.362554 am UUID: 061ddb0a-c159-884b-8964-3f3c2f74e7c7 Ancestors: System-mt.1024 Fixes typo. =============== Diff against System-mt.1024 =============== Item was changed: Object subclass: #UserInterfaceTheme instanceVariableNames: 'properties name next ignoreApply lastScaleFactor' classVariableNames: 'All Current Default' poolDictionaries: '' category: 'System-Support'! + !UserInterfaceTheme commentStamp: 'mt 5/9/2018 09:22' prior: 0! - !UserInterfaceTheme commentStamp: 'rhi 5/5/2018 09:18' prior: 0! A UserInterfaceTheme is a dictionary of preferred visual properties; colors, borderStyles, borderWidths, fonts, forms, etc. used to color and style the IDE. Accessing the Theme + To access the proper UserInterfaceTheme instance for an object, send it #userInterfaceTheme. The default implementation on Object returns an instance of UserInterfaceThemeRequest that provides a lightweight, clean proxy of the actual theme in use by the IDE at the current time. To do anything more sophisticated than basic querying and setting of properties, you must ask the proxy for the actual theme by sending #theme. - To access the proper UserInterfaceTheme instance for an object, send it #userInterfaceTheme. The default implementation on Object returns an instance of UserInterfaceThemeRequest that provides a lightweight, clean proxy of the actual theme in use by the IDE at the current time. To do anything more sophisticated than basic queryinh and setting of properties, you must ask the proxy for the actual theme by sending #theme. Customizing the Theme We can ask the #userInterfaceTheme for the value of any visual property by name: mySystemWindow userInterfaceTheme closeBoxImage Initially that would answer nil, which causes the legacy code to use whatever default it used so far. To override various visual properties of any kind of object, the #set:for:to: message can be used, for example: myUserInterfaceTheme set: #closeBoxImage for: SystemWindow to: MenuIcons smallCancelIcon Now the closeBoxImage message will answer the MenuIcons icon instead of nil. Alternatively, values may be derived based on other values in the theme, as in: myUserInterfaceTheme set: #color for: FillInTheBlankMorph to: { MenuMorph->#color. #twiceDarker } This makes FillInTheBlankMorph use the same color as a MenuMorph but #twiceDarker, providing a clean way to build coherent sets of colors within a theme. SystemWindow's code can be changed to use the expression above to access elements of the theme. Upgrading Legacy Code Following the introduction of this class, various client code all around the system must be modified to access it. This variety of legacy code uses a variety of methods to specify their visual properties: 1) a hard-coded values. 2) a values derived from some other value. 3) providing local storage for a settable value which can be nil. 4) providing local storage for a settable value which is expected to always have a particular valid value (never nil). The requirement, for each case, is to let the value be overridden. The solution for each of the above should be handled respectively to the above list, as follows: 1) Check the #userInterfaceTheme, if that property returns nil, use the legacy hard-coded value. (see example: SystemWindow>>#createCloseBox). 2) Nothing to do -- simply perform the same derivation on the result of (1). 3) Check the local storage, if present, use it. If nil, then check the #userInterfaceTheme, if it has this property present, use it, else return nil. 4) Check the #userInterfaceTheme, if the property is not nil, use it, otherwise use the local value. Tool Support If a new access to #userInterfaceTheme is added to the code, be sure to add the property and its description to the #themeSettings for that class. See implementors of #themeSettings for examples.!

1 0

Collapsed windows not quite so collapsed
by Bob Arning 09 May '18

09 May '18

Inspired by a comment earlier today: Change Set: minimorphs Date: 8 May 2018 Author: Bob Arning You can have tons of SystemWindows open or collapsed. Sometimes it can be difficult to find what you really want. This is a compromise: partial thumbnails for collapsed windows. Auto-tiling for neatness. Squeak 5.1

1 0

The Inbox: Morphic-dtl.1360.mcz
by commits＠source.squeak.org 08 May '18

08 May '18

David T. Lewis uploaded a new version of Morphic to project The Inbox: http://source.squeak.org/inbox/Morphic-dtl.1360.mcz ==================== Summary ==================== Name: Morphic-dtl.1360 Author: dtl Time: 11 November 2017, 4:04:34.153784 pm UUID: 0e1f3870-5f57-4dc6-a1e7-5d8ce68b71b5 Ancestors: Morphic-dtl.1359 World global elimination. Once the current project has been entered, Project current world == World. Begin eliminating references to the global variable World in cases where it is not required. =============== Diff against Morphic-dtl.1359 =============== Item was changed: ----- Method: ComplexProgressIndicator>>backgroundWorldDisplay (in category 'as yet unclassified') ----- backgroundWorldDisplay self flag: #bob. "really need a better way to do this" "World displayWorldSafely." "ugliness to try to track down a possible error" + [Project current world displayWorld] ifError: [ :a :b | - [World displayWorld] ifError: [ :a :b | | f | stageCompleted := 999. f := FileDirectory default fileNamed: 'bob.errors'. f nextPutAll: a printString,' ',b printString; cr; cr. f nextPutAll: 'worlds equal ',(formerWorld == World) printString; cr; cr. f nextPutAll: thisContext longStack; cr; cr. f nextPutAll: formerProcess suspendedContext longStack; cr; cr. f close. Beeper beep. ]. ! Item was changed: ----- Method: Debugger class>>morphicOpenInterrupt:onProcess: (in category '*Morphic-opening') ----- morphicOpenInterrupt: aString onProcess: interruptedProcess "Open a notifier in response to an interrupt. An interrupt occurs when the user types the interrupt key (cmd-. on Macs, ctrl-c or alt-. on other systems) or when the low-space watcher detects that memory is low." | debugger | <primitive: 19> "Simulation guard" debugger := self new. debugger process: interruptedProcess controller: nil context: interruptedProcess suspendedContext. debugger externalInterrupt: true. Preferences logDebuggerStackToFile ifTrue: [(aString includesSubstring: 'Space') & (aString includesSubstring: 'low') ifTrue: [Smalltalk logError: aString inContext: debugger interruptedContext to: 'LowSpaceDebug.log'] "logging disabled for 4.3 release, see http://lists.squeak.org/pipermail/squeak-dev/2011-December/162503.html" "ifFalse: [Smalltalk logSqueakError: aString inContext: debugger interruptedContext]"]. + Preferences eToyFriendly ifTrue: [Project current world stopRunningAll]. - Preferences eToyFriendly ifTrue: [World stopRunningAll]. ^debugger openNotifierContents: nil label: aString; yourself ! Item was changed: ----- Method: Morph>>updateFromResource (in category 'fileIn/out') ----- updateFromResource | pathName newMorph f | (pathName := self valueOfProperty: #resourceFilePath) ifNil: [^self]. (pathName asLowercase endsWith: '.morph') ifTrue: [newMorph := (FileStream readOnlyFileNamed: pathName) fileInObjectAndCode. (newMorph isMorph) ifFalse: [^self error: 'Resource not a single morph']] ifFalse: [f := Form fromFileNamed: pathName. f ifNil: [^self error: 'unrecognized image file format']. + newMorph := Project current world drawingClass withForm: f]. - newMorph := World drawingClass withForm: f]. newMorph setProperty: #resourceFilePath toValue: pathName. self owner replaceSubmorph: self by: newMorph! Item was changed: ----- Method: MorphHierarchyListMorph>>createContainer (in category 'private') ----- createContainer "Private - Create a container" | container | container := BorderedMorph new. + container extent: (Project current world extent * (1 / 4 @ (2 / 3))) rounded. - container extent: (World extent * (1 / 4 @ (2 / 3))) rounded. container layoutPolicy: TableLayout new. container hResizing: #rigid. container vResizing: #rigid. container setColor: (Color gray: 0.9) borderWidth: 1 borderColor: Color gray. container layoutInset: 0. "container useRoundedCorners." "" container setProperty: #morphHierarchy toValue: true. container setNameTo: 'Objects Hierarchy' translated. "" ^ container! Item was changed: ----- Method: MorphicProject>>storeSegment (in category 'file in/out') ----- storeSegment "Store my project out on the disk as an ImageSegment. Keep the outPointers in memory. Name it <project name>.seg. *** Caller must be holding (Project alInstances) to keep subprojects from going out. ***" | is sizeHint | + (Project current world == world) ifTrue: [^ false]. - (World == world) ifTrue: [^ false]. "self inform: 'Can''t send the current world out'." world isInMemory ifFalse: [^ false]. "already done" world ifNil: [^ false]. world presenter ifNil: [^ false]. ScrapBook default emptyScrapBook. World checkCurrentHandForObjectToPaste. world releaseSqueakPages. sizeHint := self projectParameters at: #segmentSize ifAbsent: [0]. is := ImageSegment copyFromRootsLocalFileFor: {world presenter. world} "world, and all Players" sizeHint: sizeHint. is state = #tooBig ifTrue: [^ false]. is segment size < 2000 ifTrue: ["debugging" Transcript show: self name, ' only ', is segment size printString, 'bytes in Segment.'; cr]. self projectParameters at: #segmentSize put: is segment size. is extract; writeToFile: self name. ^ true! Item was changed: ----- Method: MorphicProject>>storeSegmentNoFile (in category 'file in/out') ----- storeSegmentNoFile "For testing. Make an ImageSegment. Keep the outPointers in memory. Also useful if you want to enumerate the objects in the segment afterwards (allObjectsDo:)" | is | + (Project current world == world) ifTrue: [^ self]. " inform: 'Can''t send the current world out'." - (World == world) ifTrue: [^ self]. " inform: 'Can''t send the current world out'." world isInMemory ifFalse: [^ self]. "already done" world ifNil: [^ self]. world presenter ifNil: [^ self]. "Do this on project enter" World flapTabs do: [:ft | ft referent adaptToWorld: World]. "Hack to keep the Menu flap from pointing at my project" "Preferences setPreference: #useGlobalFlaps toValue: false." "Utilities globalFlapTabsIfAny do: [:aFlapTab | Utilities removeFlapTab: aFlapTab keepInList: false]. Utilities clobberFlapTabList. " "project world deleteAllFlapArtifacts." "self currentWorld deleteAllFlapArtifacts. " ScrapBook default emptyScrapBook. World checkCurrentHandForObjectToPaste2. is := ImageSegment copyFromRootsLocalFileFor: {world presenter. world} "world, and all Players" sizeHint: 0. is segment size < 800 ifTrue: ["debugging" Transcript show: self name, ' did not get enough objects'; cr. ^ Beeper beep]. is extract. "is instVarAt: 2 put: is segment clone." "different memory"! Item was changed: ----- Method: TheWorldMainDockingBar>>startMessageTally (in category 'menu actions') ----- startMessageTally + | world | + world := Project current world. (self confirm: 'MessageTally will start now, and stop when the cursor goes to the top of the screen') ifTrue: [MessageTally spyOn: + [[Sensor peekPosition y > 0] whileTrue: [world doOneCycle]]]! - [[Sensor peekPosition y > 0] whileTrue: [World doOneCycle]]]! Item was changed: ----- Method: TheWorldMenu>>startMessageTally (in category 'commands') ----- startMessageTally + | world | + world := Project current world. - (self confirm: 'MessageTally will start now, and stop when the cursor goes to the top of the screen') ifTrue: [MessageTally spyOn: + [[Sensor peekPosition y > 0] whileTrue: [world doOneCycle]]]! - [[Sensor peekPosition y > 0] whileTrue: [World doOneCycle]]]!

11 38

[ANN] Boadebui, a simple MIDI sequencer
by Stéphane Rollandin 08 May '18

08 May '18

Hello, I have made a simple and easy to use MIDI sequencer for loop-based music: http://www.zogotounga.net/comp/boadebui.htm Stef

4 4

The Trunk: Collections-eem.792.mcz
by commits＠source.squeak.org 08 May '18

08 May '18

Eliot Miranda uploaded a new version of Collections to project The Trunk: http://source.squeak.org/trunk/Collections-eem.792.mcz ==================== Summary ==================== Name: Collections-eem.792 Author: eem Time: 3 May 2018, 12:55:52.175146 am UUID: 7d8995ed-835e-44b0-bf4c-0b0780f5c96f Ancestors: Collections-pre.791 Four times faster implementation of isAsciiString. =============== Diff against Collections-pre.791 =============== Item was changed: ----- Method: String>>isAsciiString (in category 'testing') ----- isAsciiString + "Answer if the receiver contains only ascii characters. + Inline ^self allSatisfy: [ :each | each asciiValue <= 127 ] for speed." + 1 to: self basicSize do: [:i| (self basicAt: i) > 127 ifTrue: [^false]]. + ^true! - - ^self allSatisfy: [ :each | each asciiValue <= 127 ]!

13 32

High-level docs for ToolBuilder?
by Daniel Passaro 07 May '18

07 May '18

I'm trying to build a pet GUI project in Squeak but I'm finding it very confusing to trace through the code that actually builds, for example, a Workspace or SystemBrowser. Is there an up-to-date, high-level overview of how ToolBuilder works and the intended/best-practice way of creating an actual application with it? I am also a Squeak and Smalltalk newbie so if ToolBuilder only makes sense if, say, you're familiar with MVC, please let me know as ToolBuilder is the first framework I've tried to use in Squeak. For the record, I have skimmed some of the other Morphic tutorials but they seem to generally involve custom widgets that don't scale with the parent window. I want to create a plain-Jane business-y GUI with scrollbars and expandable windwos, but most of the tutorials I found seemed geared towards more playful and exploratory projects (laser games and bouncing balls and etc).

3 3

<Programming> 2019: Call for Papers & Call for Workshop Proposals
by Fabio Niephaus 07 May '18

07 May '18

<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. <Programming> seeks for papers that advance knowledge of programming on any relevant topic, including programming practice and experience. Paper submissions and publications are handled by the the Art, Science, and Engineering of Programming journal (http://programming-journal.org). Accepted papers must be presented at the conference. ******************************************************** CALL FOR PAPERS ******************************************************** <Programming> 2019 accepts scholarly papers that advance knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. PAPER SUBMISSIONS: June 1, 2018 URL FOR SUBMISSIONS: http://programming-journal.org/submission/ Submissions covering several areas of expertise are accepted, including but not limited to: • General-purpose programming • Distributed systems programming • Parallel and multi-core programming • Graphics and GPU programming • Security programming • User interface programming • Database programming • Visual and live programming • Data mining and machine learning programming • Interpreters, virtual machines and compilers • Modularity and separation of concerns • Model-based development • Metaprogramming and reflection • Testing and debugging • Program verification • Programming education • Programming environments • Social coding ******************************************************** CALL FOR WORKSHOP PROPOSALS ******************************************************** To build a community and to foster an environment where participants can exchange ideas and experiences related to practical software development, <Programming> will host a number of workshops, during the days before the main conference. The workshops will provide a collaborative forum to exchange recent and/or preliminary results, to conduct intensive discussions on a particular topic, or to coordinate efforts between representatives of a technical community. They are intended as a forum for lively discussion of innovative ideas, recent progress, or practical experience on programming and applied software development in general for specific aspects, specific problems, or domain-specific needs. We also encourage practical, hands-on workshops in which participants actually experience one or several aspects of practical software development. WORKSHOP PROPOSAL SUBMISSIONS: First Deadline: July 1st, 2018 Second Deadline: September 1st, 2018 The duration of workshops is in general one day, but we encourage the submission of half-day workshop proposals on focused topics as well. In exceptional situations, e.g., for workshops that involve actual practice of programming-related activities, workshop organizers can request a 2 day workshop slot. If desired, the workshop proceedings can be published in the ACM Digital Library. ******************************************************** IMPORTANT DATES ******************************************************** Research paper submissions: June 1, 2019 Research paper first notifications: August 1, 2018 Research paper final notifications: September 7, 2018 Workshop proposals: July 1st, 2018 (first deadline) Workshop proposals: September 1st, 2018 (second deadline) ******************************************************** 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 Stefan Marr (Workshops Co-Chair), University of Kent Fabio Niephaus (Publicity Co-Chair), Hasso Plattner Institute, University of Potsdam Tobias Pape (Web Technology Chair), Hasso Plattner Institute, University of Potsdam Program Committee: 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

← Newer
1
...
12
13
14
15
16
17
18
19
Older →

Jump to page: