Squeak-dev June 2016

squeak-dev@lists.squeakfoundation.org

39 participants
202 discussions

Daily Commit Log
by commits＠source.squeak.org 21 Jun '16

21 Jun '16

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2016-June/068231.html Name: Morphic-mt.1183 Ancestors: Morphic-mt.1182 Fixes regression in docking bar. A simple click now keeps the menu open again. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2016-June/068232.html Name: Morphic-mt.1184 Ancestors: Morphic-mt.1183 Fixes regression (?) to make opening sub-sub menus -- not to the right but to the left due to limited screen space -- work again. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2016-June/068233.html Name: SMLoader-tpr.87 Ancestors: SMLoader-mt.86 Improve (hopefully) the SM release browser so that a) when hitting the save button it automatically accepts changed text in the name/version/script etc views, thus avoiding the need to accept each one individually. b) instead of a blank script view we provide some examples to offer a clue to the user =============================================

1 0

SqueakMap server stuck?
by tim Rowledge 21 Jun '16

21 Jun '16

I’ve been trying to set up a coupe of packages and it isn’t working very nicely right now. I uploaded to squeaksource ok and even (eventually) worked out how to make first releases. I added two projects to my squeakmap account, and they even appear in the in-image catalogue. But any attempt to get to the SM ‘edit releases’ page just times out with a 504. Is this me doing wrong things, or the server getting stuck or…? tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Strange OpCodes: ESR: Emulate Slide Rule

4 5

The Trunk: SMLoader-tpr.87.mcz
by commits＠source.squeak.org 21 Jun '16

21 Jun '16

tim Rowledge uploaded a new version of SMLoader to project The Trunk: http://source.squeak.org/trunk/SMLoader-tpr.87.mcz ==================== Summary ==================== Name: SMLoader-tpr.87 Author: tpr Time: 21 June 2016, 1:29:19.632444 pm UUID: e1857350-474a-4c4d-a5af-f8d6226c3f79 Ancestors: SMLoader-mt.86 Improve (hopefully) the SM release browser so that a) when hitting the save button it automatically accepts changed text in the name/version/script etc views, thus avoiding the need to accept each one individually. b) instead of a blank script view we provide some examples to offer a clue to the user =============== Diff against SMLoader-mt.86 =============== Item was added: + ----- Method: SMReleaseBrowser>>exampleLoadScript (in category 'private') ----- + exampleLoadScript + "this is an example load script to offer the user rather than a blank view" + + ^'"This is where you need to provide an install script; you may need to handle prerequisites first and then load the actual package(s) Take a look at http://wiki.squeak.org/squeak/6182 for more info, especially about creating a ''load latest version'' script" + "Example to load a prerequisite package - " + SMSqueakMap default + installPackageNamed: ''myPackage'' + version: ''release name''. + "Example to load myPackage if a certain class is not already in the image -" + (Smalltalk hasClassNamed: #MyPackage) + ifFalse:[SMSqueakMap default + installPackageNamed: ''myPackage'' + version: ''release name'']. + "Or load several specifc mcz files -" + #( ''MyPackagePartA-abc.1.mcz'' ''MyPackagePartB-abc.42.mcz'' ) do: + [:each| (Installer repository: ''http://www.squeaksource.com/MyPackages'') install: each]'! Item was changed: ----- Method: SMReleaseBrowser>>loadScript (in category 'model access') ----- loadScript "The Smalltalk code needed to install this release of this package." + ^ loadScript + ifNil: [| scriptName | + scriptName := release downloadFileName. + loadScript := scriptName isEmptyOrNil + ifFalse: [(scriptName asLowercase endsWith: '.st') + ifTrue: [release contents]] + ifTrue: [self exampleLoadScript]]! - ^ loadScript ifNil: - [ | scriptName | - scriptName := release downloadFileName. - loadScript := scriptName isEmptyOrNil ifFalse: - [ (scriptName asLowercase endsWith: '.st') ifTrue: [ release contents ] ] ]! Item was changed: ----- Method: SMReleaseBrowser>>validateCanSave (in category 'private') ----- validateCanSave + "accept any changes in the text field morphs etc, then validate the input as best we can" + self changed: #acceptChanges. self username isEmptyOrNil ifTrue: [ self userError: 'username required' ]. self note isEmptyOrNil ifTrue: [ self userError: 'note required' ]. self version isEmptyOrNil ifTrue: [ self userError: 'version required' ] ifFalse: [ (self version includes: $+) ifTrue: [ self userError: 'Plus sign not allowed in version name because it is reserved by HTTP.' ] ]!

1 0

Re: System and user processe
by Max Leske 21 Jun '16

21 Jun '16

>> On 06/19/2016 05:03 AM, Max Leske wrote: >> Hi, >> >> In Pharo and Squeak we have no separation between processes that >> belong to the IDE, tools etc. and processes that are spawned as part >> of an application. I’d like to know your opinion on the following >> (rough) idea: >> >> 1. We introduce two subclasses of Process: SystemProcess and >> UserProcess 2. We define #isSystemProcess and #isUserProcess 3. We >> introduce #newSystemProcess and #newUserProcess 4. We deprecate >> #newProcess and delegate to #newUserProcess (thereby modifying all >> users of #forkXXX to yield instances of UserProcess) >> >> Of the following I’m less sure: 5. We introduce #forkSystemProcess >> et. al >> >> I’ve tried this out in Pharo 6 and there seem to be no problems with >> the VM. The benefit would be improved separation between system and >> user space. It would allow us to implement stuff for processes in >> general (e.g. for the debugger) which we do not want to affect system >> processes like the UI process or the background process. One concrete >> example: the process browser could hide all system processes and make >> them visible on demand (that would greatly improve the view because >> you can now better find your own processes). >> >> >> I’m looking forward to your comments. >> >> Cheers, Max >> >> >> >> On Tue, Jun 21, 2016 at 3:32 AM, Tony Garnock-Jones <tonyg(a)ccs.neu.edu> wrote: >> Hi Max, >> >> Perhaps a notion of process grouping might make sense? Following the >> zero-one-infinity principle, having exactly two kinds of process seems a >> bit odd. >> >> Having process grouping would lead to a tree of processes. >> >> For example, the outermost level could be "system" processes, of which >> one was a group containing all "user" processes. >> >> Or, the outermost level could have two children, one group of "system" >> procs, one of "user" procs; or, ... >> >> The "current process group" would be a kind of dynamic parameter, and >> newly-forked processes would by default become siblings of the forker in >> the current group. >> >> Regards, >> Tony > > This sounds like a good idea. It would make it easier for a user of > multiple applications in one image to properly kill one. For this > reason, perhaps there should be some impediment on apps adding > processes adding the System Process group(??) > > cheers -ben Yes. That’s why in my proposal the default is to create a user process. Cheers, Max

1 0

Re: System and user processe
by Max Leske 21 Jun '16

21 Jun '16

> Hi Max, > > Perhaps a notion of process grouping might make sense? Following the > zero-one-infinity principle, having exactly two kinds of process seems a > bit odd. I agree. I just wanted to get the idea out there without proposing a complete POSIX process model. And I found it interesting that we actually could use subclasses without needing special support from the VM. > > Having process grouping would lead to a tree of processes. > > For example, the outermost level could be "system" processes, of which > one was a group containing all "user" processes. > > Or, the outermost level could have two children, one group of "system" > procs, one of "user" procs; or, ... > > The "current process group" would be a kind of dynamic parameter, and > newly-forked processes would by default become siblings of the forker in > the current group. > > Regards, > Tony I think that grouping makes a lot of sense. However, the current model has also served us well, maybe exactly because it is simple. Adding a lot of complexity will not necessarily make things better (especially for newcomers). Maybe there’s a middle ground where high level processes maintain a very simple API (like Chris proposed) and where you don’t have to know about process groups (those processes might just go into a default group, essentially what you describe with “current process group"). Really not sure… Cheers, Max > > > > On 06/19/2016 05:03 AM, Max Leske wrote: > Hi, > > In Pharo and Squeak we have no separation between processes that > belong to the IDE, tools etc. and processes that are spawned as part > of an application. I’d like to know your opinion on the following > (rough) idea: > > 1. We introduce two subclasses of Process: SystemProcess and > UserProcess 2. We define #isSystemProcess and #isUserProcess 3. We > introduce #newSystemProcess and #newUserProcess 4. We deprecate > #newProcess and delegate to #newUserProcess (thereby modifying all > users of #forkXXX to yield instances of UserProcess) > > Of the following I’m less sure: 5. We introduce #forkSystemProcess > et. al > > I’ve tried this out in Pharo 6 and there seem to be no problems with > the VM. The benefit would be improved separation between system and > user space. It would allow us to implement stuff for processes in > general (e.g. for the debugger) which we do not want to affect system > processes like the UI process or the background process. One concrete > example: the process browser could hide all system processes and make > them visible on demand (that would greatly improve the view because > you can now better find your own processes). > > > I’m looking forward to your comments. > > Cheers, Max

1 0

Re: System and user processe
by Max Leske 21 Jun '16

21 Jun '16

> Max Leske wrote >> Hi, >> >> In Pharo and Squeak we have no separation between processes that belong to >> the IDE, tools etc. and processes that are spawned as part of an >> application. I’d like to know your opinion on the following (rough) idea: >> >> 1. We introduce two subclasses of Process: SystemProcess and UserProcess >> 2. We define #isSystemProcess and #isUserProcess >> 3. We introduce #newSystemProcess and #newUserProcess >> 4. We deprecate #newProcess and delegate to #newUserProcess (thereby >> modifying all users of #forkXXX to yield instances of UserProcess) >> >> Of the following I’m less sure: >> 5. We introduce #forkSystemProcess et. al >> >> I’ve tried this out in Pharo 6 and there seem to be no problems with the >> VM. The benefit would be improved separation between system and user >> space. It would allow us to implement stuff for processes in general (e.g. >> for the debugger) which we do not want to affect system processes like the >> UI process or the background process. One concrete example: the process >> browser could hide all system processes and make them visible on demand >> (that would greatly improve the view because you can now better find your >> own processes). >> >> >> I’m looking forward to your comments. >> >> Cheers, >> Max > > Hi Max, > > I like the idea. Let's see... > > System processes in Squeak could be: > - the timer interrupt watcher > - the event tickler > - the low space watcher > - the user interrupt watcher > - the idle process > > I am not so sure about: > - the WeakArray finalization process (still needed for Ephemerons?) > > Then we have the UI framework(s). The frameworks' processes could be user > processes or system processes, too? Hmm... for Morphic, there is only one. > Stepping is implemented with the same UI process. Applications that spawn > other (user) processes work around Morphic anyway. > > Tweak uses (or used) many processes to execute scripts. So, the Tweak UI has > a set of related processes, not just a single UI process. > > MVC has only one process running but creates/terminates processes when > switching controllers. > > If you play a MIDI or a Sound, should that process also be a system process, > right? Hmm... > > Interactive debugging is tricky only with respect to the current UI > framework because you want to be able to also debug that frameworks code and > its applications. While writing the debugger in that framework, too. So, it > is above the level of processes but at the level of the UI framework (resp. > projects). At least in Squeak. > > Hmm... for a filter in the process browser, a simple flag would be enough. > No need to add subclasses. So, whout be the benefits of distinguishing > between UserProcess and SystemProcess at process creation time? How to > decide? Might it be related to additional warnings? Calling "Smalltalk > snapshot: true andQuit: true" from a process in an endless loop might be > detected if you do that from within a UserProcess. :-D > > Maybe introduce restrictions/warnings at the level of message dispatch for > UserProcesses? Hmm… You essentially get my point. For the process browser a flag would be enough, yes, but that’s not really OO, is it… :) Anyway, I see a couple of “direct” benefits: - better implementation of user interrupt handling (user processes can always be interrupted) - kill all user processes (system will keep running) - different low space settings for system and user processes (yes, that would probably require a VM change, but still…) - system processes could be prevented from starving (e.g. a user process must yield at least every n milliseconds) ... > > Best, > Marcel > >

1 0

The Trunk: Morphic-mt.1184.mcz
by commits＠source.squeak.org 21 Jun '16

21 Jun '16

Marcel Taeumel uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-mt.1184.mcz ==================== Summary ==================== Name: Morphic-mt.1184 Author: mt Time: 21 June 2016, 2:12:23.053974 pm UUID: 6dad4a60-1b46-d049-a8af-afaae6989874 Ancestors: Morphic-mt.1183 Fixes regression (?) to make opening sub-sub menus -- not to the right but to the left due to limited screen space -- work again. =============== Diff against Morphic-mt.1183 =============== Item was changed: ----- Method: MenuMorph>>mouseMove: (in category 'events') ----- mouseMove: evt " If the mouse moves over an item not selected, we try to set it as selected. If this happens depends on that the current selected item wants to release its selection. " + self selectedItem ifNil: [ + self + selectItem: ( + self items + detect: [ :each | each containsPoint: evt position ] + ifNone: [ nil ]) + event: evt]. - "Note: The following does not traverse upwards but it's the best I can do for now" - popUpOwner ifNotNil:[(popUpOwner activateOwnerMenu: evt) ifTrue: [^ self]]. - self selectedItem ifNil: [ ^ self ]. - (self selectedItem containsPoint: evt position) ifTrue: [ ^ self ]. - self - selectItem: ( - self items - detect: [ :each | each containsPoint: evt position ] - ifNone: [ nil ]) - event: evt. - "Transfer control to *either* the currently active submenu or the pop up owner, if any. Since the active sub menu is always displayed upfront check it first." + self selectedItem ifNotNil: [ + (self selectedItem activateSubmenu: evt) - selectedItem ifNotNil: [ - (selectedItem activateSubmenu: evt) ifTrue: [ ^self ] ifFalse: [ (self containsPoint: evt position) ifFalse: [ + self selectItem: nil event: evt ] ] ]. + + "Note: The following does not traverse upwards but it's the best I can do for now" + popUpOwner ifNotNil:[(popUpOwner activateOwnerMenu: evt) ifTrue: [^ self]]. + ! - self selectItem: nil event: evt ] ] ].!

1 0

The Trunk: Morphic-mt.1183.mcz
by commits＠source.squeak.org 21 Jun '16

21 Jun '16

Marcel Taeumel uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-mt.1183.mcz ==================== Summary ==================== Name: Morphic-mt.1183 Author: mt Time: 21 June 2016, 2:05:38.378974 pm UUID: 56a07e0a-08c1-6d4b-8275-9c6a2affdba7 Ancestors: Morphic-mt.1182 Fixes regression in docking bar. A simple click now keeps the menu open again. =============== Diff against Morphic-mt.1182 =============== Item was changed: ----- Method: DockingBarItemMorph>>mouseDown: (in category 'events') ----- mouseDown: evt "Handle a mouse down event. Menu items get activated when the mouse is over them." (evt shiftPressed and:[self wantsKeyboardFocusOnShiftClick]) ifTrue: [ ^super mouseDown: evt ]. "enable label editing" isSelected ifTrue: [ - evt hand newMouseFocus: nil. owner selectItem: nil event: evt. ] ifFalse: [ - (self containsPoint: evt position) ifFalse: [ self halt ]. owner activate: evt. "Redirect to menu for valid transitions" owner selectItem: self event: evt. ] ! Item was changed: ----- Method: DockingBarItemMorph>>mouseUp: (in category 'events') ----- mouseUp: evt "Handle a mouse up event. Menu items get activated when the mouse is over them. Do nothing if we're not in a 'valid menu transition', meaning that the current hand focus must be aimed at the owning menu." evt hand mouseFocus == owner ifFalse: [ ^self ]. self contentString ifNotNil: [ self contents: self contentString withMarkers: true inverse: true. self refreshWorld. + (Delay forMilliseconds: 200) wait ].! - (Delay forMilliseconds: 200) wait ]. - owner rootMenu selectItem: nil event: evt. - self invokeWithEvent: evt! Item was added: + ----- Method: DockingBarMorph>>indicateKeyboardFocus (in category 'testing') ----- + indicateKeyboardFocus + ^ false! Item was changed: ----- Method: DockingBarMorph>>mouseDown: (in category 'events-processing') ----- mouseDown: evt (self fullContainsPoint: evt position) ifFalse: [ self selectItem: nil event: evt. + self deleteIfPopUp: evt ]! - evt hand releaseMouseFocus: self ]! Item was added: + ----- Method: DockingBarMorph>>mouseUp: (in category 'events-processing') ----- + mouseUp: evt + + evt hand newMouseFocus: self.! Item was changed: ----- Method: MenuMorph>>mouseMove: (in category 'events') ----- mouseMove: evt " If the mouse moves over an item not selected, we try to set it as selected. If this happens depends on that the current selected item wants to release its selection. " + "Note: The following does not traverse upwards but it's the best I can do for now" + popUpOwner ifNotNil:[(popUpOwner activateOwnerMenu: evt) ifTrue: [^ self]]. + self selectedItem ifNil: [ ^ self ]. (self selectedItem containsPoint: evt position) ifTrue: [ ^ self ]. self selectItem: ( self items detect: [ :each | each containsPoint: evt position ] ifNone: [ nil ]) event: evt. "Transfer control to *either* the currently active submenu or the pop up owner, if any. Since the active sub menu is always displayed upfront check it first." selectedItem ifNotNil: [ (selectedItem activateSubmenu: evt) ifTrue: [ ^self ] ifFalse: [ (self containsPoint: evt position) ifFalse: [ + self selectItem: nil event: evt ] ] ].! - self selectItem: nil event: evt ] ] ]. - - "Note: The following does not traverse upwards but it's the best I can do for now" - popUpOwner ifNotNil:[popUpOwner activateOwnerMenu: evt]! Item was changed: ----- Method: MenuMorph>>mouseUp: (in category 'events') ----- mouseUp: evt "Handle a mouse up event. Note: This might be sent from a modal shell." (self fullContainsPoint: evt position) ifFalse:[ + ^ self deleteIfPopUp: evt]. - "Mouse up outside. Release eventual focus and delete if pop up." - evt hand releaseMouseFocus: self. - ^self deleteIfPopUp: evt]. stayUp ifFalse:[ "Still in pop-up transition; keep focus" evt hand newMouseFocus: self].!

1 0

System and user processes
by Max Leske 21 Jun '16

21 Jun '16

Hi, In Pharo and Squeak we have no separation between processes that belong to the IDE, tools etc. and processes that are spawned as part of an application. I’d like to know your opinion on the following (rough) idea: 1. We introduce two subclasses of Process: SystemProcess and UserProcess 2. We define #isSystemProcess and #isUserProcess 3. We introduce #newSystemProcess and #newUserProcess 4. We deprecate #newProcess and delegate to #newUserProcess (thereby modifying all users of #forkXXX to yield instances of UserProcess) Of the following I’m less sure: 5. We introduce #forkSystemProcess et. al I’ve tried this out in Pharo 6 and there seem to be no problems with the VM. The benefit would be improved separation between system and user space. It would allow us to implement stuff for processes in general (e.g. for the debugger) which we do not want to affect system processes like the UI process or the background process. One concrete example: the process browser could hide all system processes and make them visible on demand (that would greatly improve the view because you can now better find your own processes). I’m looking forward to your comments. Cheers, Max

5 6

Daily Commit Log
by commits＠source.squeak.org 20 Jun '16

20 Jun '16

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2016-June/068229.html Name: Morphic-mt.1182 Ancestors: Morphic-mt.1181 Moves implementation of focus event dispatching from various places into MorphicEventDispatcher. This will ensure consistency in the future because MorphicEventDispatcher encode the tree iteration with capturing and bubbling. Doing a focus event is just a shortcut into the tree. TextMorphs use that. Pop-up menus use that. Modal dialogs use that. Fixes missing coordinate transformations when capturing and bubbling for focus events. Simplify focus-related code in MenuMorph, UserDialogBoxMorph, and DockingBarMorph. At the time of writing, there seems to be no need anymore for Morph >> #handleFocusEvent:. Still, keep it for compatibility to other projects. ============================================= http://lists.squeakfoundation.org/pipermail/packages/2016-June/068230.html Name: MorphicTests-mt.33 Ancestors: MorphicTests-mt.32 More tests for Morphic event dispatchs. Use custom hand morph for these tests. =============================================

1 0

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

Jump to page: