Squeak-dev October 2017

squeak-dev@lists.squeakfoundation.org

40 participants
132 discussions

Re: [squeak-dev] Ideas for web hosting for squeak.org?
by Bruce O'Neel 16 Oct '17

16 Oct '17

Hi, Thanks to Stephan's pointer to the eugdpr.org website. I've spent some time with this and have some comments below. First, the GDPR will apply if we let EU residents go to the Squeak websites. Given the popularity of Squeak in the EU that means GDPR regardless of where we physically host it. Second I think we're going to run into a computer geek view of the world not agreeing with the EU view of the world. Ie, you sent an email to a public mailing list with your full contact info that is archived forever. What words in that last sentence did you not understand? The things I think we have to comply with are: 1. Consent. The users have to know what they are giving us. Cookie notifications on the main webpage and some sort of page that describes what we log for access like IP addresses, etc. We also have to make clear how long info is stored. So if the webserver keeps that last 30 days of IP address logs than that has to be clear. We also have an age problem. We will need parental consent if there are users under 16. For the wiki, mailing lists etc we need to be clear what additional info is gathered. This is probably the easy one. 2. Breach notification, Right to Access, and Right to be forgotten are going to be harder. The places where we collect more personal info than just IP address are for the Wiki, the Mailing lists, and the bug tracker. In all three cases we would need to have enough info that: 1. For breach notification we can actually notify folks. We would need to collect email addresses in all cases for that to work. 2. For right to access we would have to be able to show ALL the info we've kept on a particular user. All posts to the email lists, all swiki entries, etc. 3. And for right to be forgotten we would have to allow users to delete ALL the data we've captured. All swiki entries, all archived email, etc. This is probably the hardest. For number 2, the right to access, would all be easiest if the wiki, email and bug trackers had a unified account, but, it probably would be ok if one had three accounts. None the less you have to be able to see all your entries in all three. Number 3 is the trickiest especially with the mailing list archive. People's postings and signatures get copied into other threads and other's emails. It might be hard to keep the archives in that case. Getting this one right starts sounding like an AI research problem. Someone asked about the DPO (Data Protection Officer). The way I read [http://www.eugdpr.org/gdpr-faqs.html](http://www.eugdpr.org/gdpr-faqs.html) is no, we do not need this.There are other issues but I think these are the most important. NB: I am not an expert, though I do spend some time professionally on this, and, will be spending more time in the future. This advice is worth every centime you've paid for it as well. cheers bruce

6 6

Re: [squeak-dev] Source lookup in .changes file fails in headless mode on Linux
by Max Leske 15 Oct '17

15 Oct '17

Hi Levente, I finally got around testing your fix and it does indeed fix the exception from being signalled. Please let me know once you've ported it back to 5.1. Cheers, Max On 11 October 2017 at 14:00:05, squeak-dev-request(a)lists.squeakfoundation.org ( squeak-dev-request(a)lists.squeakfoundation.org) wrote: Thanks Dave and Marcel for your feedback. Levente, I'll test it and let you know. Thanks! Cheers, Max On 10 October 2017 at 14:00:04 <http://airmail.calendar/2017-10-10 14:00:04 CEST>, squeak-dev-request(a)lists.squeakfoundation.org ( squeak-dev-request(a)lists.squeakfoundation.org) wrote: Hi Max, I just pushed Files-ul.172 to the Trunk, which contains a fix for this. If it turns out to be a good fix, I'll backport it to 5.1. Levente

2 1

Re: [squeak-dev] Ideas for web hosting for squeak.org?
by Bruce O'Neel 15 Oct '17

15 Oct '17

Hi, Thanks. All excellent points. cheers bruce

1 0

The Trunk: EToys-dtl.310.mcz
by commits＠source.squeak.org 15 Oct '17

15 Oct '17

David T. Lewis uploaded a new version of EToys to project The Trunk: http://source.squeak.org/trunk/EToys-dtl.310.mcz ==================== Summary ==================== Name: EToys-dtl.310 Author: dtl Time: 14 October 2017, 7:25:17.542836 pm UUID: 29e207b2-1345-4fce-9f27-1a372728536e Ancestors: EToys-mt.309 Follow up for EToys-tfel.266 The default environment should be "Smalltalk environment" rather than "Smalltalk" =============== Diff against EToys-mt.309 =============== Item was changed: ----- Method: ScriptEncoder>>init:context:notifying: (in category 'as yet unclassified') ----- init: class context: ctxt notifying: parser super init: (CompilationCue source: nil context: ctxt receiver: nil class: class + environment: Smalltalk environment - environment: Smalltalk requestor: nil) notifying: parser!

1 0

ASN.1 Floats
by Bert Freudenberg 14 Oct '17

14 Oct '17

On Thu, Oct 12, 2017 at 11:36 AM, Alan Pinch <alan.c.pinch(a)gmail.com> wrote: > The same issue exists in ASN1 support, none for float type tag 9. I would > love to add this support but I am unsure how to breakdown a float into > mantissa, base and exponent. Here is a description of how ASN1 formats a > REAL into the stream of bytes: > > Type REAL takes values that are the machine representation of a real > number, namely the triplet (m, b, e), where m is the mantissa (a signed > number), b the base (2 or 10), and e the exponent (a signed number). For > example, the representation of the value 3.14 for the variable Pi, declared > as Pi ::= REAL, can be (314, 10, -2). Three special values, PLUS-INFINITY, > 0, and MINUS-INFINITY, are also allowed. > > Here are some sample values: > > > - 09 00 = 0 (zero) > - 09 01 40 = +INF (infinity) > - 09 01 41 = -INF > - 09 08 03 2b 31 2e 30 65 2b 30 = "+1.0e+0" = 1.0 (exact decimal) > - 09 05 80 fe 55 55 55 = 1398101.25 (binary, 0x555555 * 2^-2) > - 09 06 83 00 fc 00 00 01 = 0.0625 (binary, 0x000001 * 2^-4) > > I have not parsed out these samples into these components so it's greek. > Well it's not the same issue as ASN.1 float representation is different from IEEE 754 format. To convert a Squeak Float into an IEEE 64 bit pattern we simply access its underlying representation, because the VM uses IEEE internally. It sounds like ASN.1 stores mantissa, base, and exponent separately. IEEE calls the mantissa "significand" and that's the name of the corresponding Squeak method. The exponent is called "exponent", and the base is implicitly 2: 1398101.25 significand => 1.3333332538604736 1398101.25 exponent => 20 1.3333332538604736 timesTwoPower: 20 => 1.39810125e6 1398101.25 = 1.39810125e6 => true The IEEE significand/mantissa is normalized to a fractional number 1 <= m < 2. ASN wants integral numbers, so you could convert it to an integer like this: x := 1398101.25. mantissa := x significand. exponent := x exponent. base := 2. [mantissa fractionPart isZero] whileFalse: [mantissa := mantissa * base. exponent := exponent - 1]. {mantissa asInteger hex. base. exponent} #('16r555555' 2 -2) ... which matches your example. I'm sure Nicolas will have a much more efficient formula, but this would work :) - Bert -

4 6

The Trunk: MorphicExtras-dtl.212.mcz
by commits＠source.squeak.org 14 Oct '17

14 Oct '17

David T. Lewis uploaded a new version of MorphicExtras to project The Trunk: http://source.squeak.org/trunk/MorphicExtras-dtl.212.mcz ==================== Summary ==================== Name: MorphicExtras-dtl.212 Author: dtl Time: 14 October 2017, 5:16:39.597724 pm UUID: aa647724-2bdf-4bc6-8d0a-7dd23a8ecd13 Ancestors: MorphicExtras-pre.211, MorphicExtras-dtl.210 Merge MorphicExtras-dtl.210 to fix system window layout when flaps are enabled =============== Diff against MorphicExtras-pre.211 =============== Item was changed: ----- Method: RealEstateAgent class>>reduceByFlaps: (in category '*MorphicExtras-utilities') ----- reduceByFlaps: aScreenRect "Return a rectangle that won't interfere with default shared flaps" + | top bottom left right | Flaps sharedFlapsAllowed ifFalse: [^ aScreenRect copy]. + + top := bottom := left := right := 0. + Flaps globalFlapTabs do: [ :ft | | w h | + w := ft width. + h := ft height. + ft edgeToAdhereTo + caseOf: { + [ #top ] -> [ top := top max: h ]. + [ #bottom ] -> [ bottom := bottom max: h ] . + [ #left ] -> [ left := left max: w ] . + [ #right ] -> [ right := right max: w ] . + } + otherwise: [] ]. + ^ Rectangle + origin: aScreenRect origin + (left @ top) + extent: aScreenRect extent - (bottom @ right). + ! - (Flaps globalFlapTabsIfAny allSatisfy: - [:ft | ft flapID = 'Painting' translated or: [ft edgeToAdhereTo == #bottom]]) - ifTrue: [^ aScreenRect withHeight: aScreenRect height - 18] - ifFalse: [^ aScreenRect insetBy: 64]!

1 0

The Inbox: System-hjh.969.mcz
by commits＠source.squeak.org 14 Oct '17

14 Oct '17

A new version of System was added to project The Inbox: http://source.squeak.org/inbox/System-hjh.969.mcz ==================== Summary ==================== Name: System-hjh.969 Author: hjh Time: 14 October 2017, 11:14:48.026934 pm UUID: d5fb0777-04f0-48f5-b86f-c985ff265bc1 Ancestors: System-dtl.968 Preferences implicitSelfInTiles taken from Squeak6.0a Etoys image of Tim Felgentreff. =============== Diff against System-dtl.968 =============== Item was added: + ----- Method: Preferences class>>implicitSelfInTiles (in category 'standard queries') ----- + implicitSelfInTiles + ^ self + valueOfFlag: #implicitSelfInTiles + ifAbsent: [false]!

1 0

The Trunk: MorphicExtras-dtl.210.mcz
by commits＠source.squeak.org 14 Oct '17

14 Oct '17

David T. Lewis uploaded a new version of MorphicExtras to project The Trunk: http://source.squeak.org/trunk/MorphicExtras-dtl.210.mcz ==================== Summary ==================== Name: MorphicExtras-dtl.210 Author: dtl Time: 30 September 2017, 11:00:57.627669 am UUID: 4c13263d-1a0c-4857-8906-4ea09598f70b Ancestors: MorphicExtras-tpr.209 Reimplement RealEstateAgent class>>reduceByFlaps: to protect margins for size of flap handles, but no special case logic for 'Painting' flap, and do not reduce margins by 64 in any case. This affects placement of SystemWindows, which avoids covering top flaps with a repositioned window. The previous implementation prevented placement of windows at the top portion of the display area if flaps were enabled in a project. =============== Diff against MorphicExtras-tpr.209 =============== Item was changed: ----- Method: RealEstateAgent class>>reduceByFlaps: (in category '*MorphicExtras-utilities') ----- reduceByFlaps: aScreenRect "Return a rectangle that won't interfere with default shared flaps" + | top bottom left right | Flaps sharedFlapsAllowed ifFalse: [^ aScreenRect copy]. + + top := bottom := left := right := 0. + Flaps globalFlapTabs do: [ :ft | | w h | + w := ft width. + h := ft height. + ft edgeToAdhereTo + caseOf: { + [ #top ] -> [ top := top max: h ]. + [ #bottom ] -> [ bottom := bottom max: h ] . + [ #left ] -> [ left := left max: w ] . + [ #right ] -> [ right := right max: w ] . + } + otherwise: [] ]. + ^ Rectangle + origin: aScreenRect origin + (left @ top) + extent: aScreenRect extent - (bottom @ right). + ! - (Flaps globalFlapTabsIfAny allSatisfy: - [:ft | ft flapID = 'Painting' translated or: [ft edgeToAdhereTo == #bottom]]) - ifTrue: [^ aScreenRect withHeight: aScreenRect height - 18] - ifFalse: [^ aScreenRect insetBy: 64]!

1 0

The Trunk: System-dtl.968.mcz
by commits＠source.squeak.org 14 Oct '17

14 Oct '17

David T. Lewis uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-dtl.968.mcz ==================== Summary ==================== Name: System-dtl.968 Author: dtl Time: 14 October 2017, 2:45:35.676806 pm UUID: 764236d5-e9b8-4e24-9b9c-fa609210822a Ancestors: System-hjh.967 Use a pragma rather than #flag: to identify senders of methods dispatched through #dispatchTo:addPrefixAndSend:withArguments: Inspired by System-bf.966 =============== Diff against System-hjh.967 =============== Item was added: + ----- Method: Project class>>baseSelectors (in category 'dispatching') ----- + baseSelectors + "The list of known base selectors that may be dispatched to project specific + implementations. For example, #OpenLabel:in: will be dispatched to #mvcOpenLabel:in: + for its MVC specific implementation. Add new base selectors here if additional methods + are added as targets of the dispatchTo:addPrefixAndSend:withArguments: mechanism." + + ^ { + #StartUpLeftFlush . + #StartUpWithCaption:icon:at:allowKeyboard: . + #OpenLabel:in: . + #Open: . + #Open . + #OpenOn:context:label:contents:fullView: . + #ResumeProcess: + } + ! Item was added: + ----- Method: Project class>>dispatchSelectors (in category 'dispatching') ----- + dispatchSelectors + "All known targets of the dispatch mechanism" + + "Project dispatchSelectors" + + | selectors dispatchPrefixes | + selectors := OrderedCollection new. + dispatchPrefixes := Set withAll: (Project allSubclasses collect: [ :e | e basicNew selectorPrefixForDispatch ]). + self baseSelectors do: [ :base | + dispatchPrefixes do: [ :prefix | + selectors add: (prefix, base) asSymbol ] ]. + ^ selectors + + ! Item was added: + ----- Method: Project class>>isDispatchSelector: (in category 'dispatching') ----- + isDispatchSelector: aSelector + "In support of package modularity, some method selectors are generated based + on project type and dispatched to the appropriate implementation for that project. + For methods with these selectors, let dispatchTo:addPrefixAndSend:withArguments: + be found as a sender." + + ^ self dispatchSelectors includes: aSelector. + ! Item was changed: ----- Method: Project>>dispatchTo:addPrefixAndSend:withArguments: (in category 'dispatching') ----- dispatchTo: requestor addPrefixAndSend: baseSelector withArguments: arguments "Sender wants to perform a method with dependencies on the type of project. Dispatch to an appropriate method for the current project. + + If additional base selectors are added for dispatching, the list of base selectors + in Project class>>baseSelectors should be updated. This method is a workaround for lack of proper ToolBuilder support in the sender, and should be eliminated when possible (dtl Feb 2010)" + <hasLiteralTest: #isDispatchSelector:> | selector | - "Flag target selectors to help identify senders" - true ifFalse: [ - self flag: #mvcOpenLabel:in: . - self flag: #morphicOpenLabel:in: . - self flag: #mvcStartUpLeftFlush . - self flag: #morphicStartUpLeftFlush . - self flag: #mvcStartUpWithCaption:icon:at:allowKeyboard: . - self flag: #morphicStartUpWithCaption:icon:at:allowKeyboard: . - self flag: #mvcOpen: . - self flag: #morphicOpen: . - self flag: #mvcOpen . - self flag: #morphicOpen . - self flag: #mvcOpenOn:context:label:contents:fullView: . - self flag: #morphicOpenOn:context:label:contents:fullView: . - self flag: #mvcResumeProcess: . - self flag: #morphicResumeProcess: - ]. selector := (self selectorPrefixForDispatch, baseSelector) asSymbol. ^ requestor perform: selector withArguments: arguments!

1 0

The Trunk: System-hjh.967.mcz
by commits＠source.squeak.org 14 Oct '17

14 Oct '17

Bert Freudenberg uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-hjh.967.mcz ==================== Summary ==================== Name: System-hjh.967 Author: hjh Time: 14 October 2017, 4:33:41.102157 pm UUID: ba832c58-398d-431e-b40c-fb01421606cf Ancestors: System-bf.966 Update class comment with note how '*Morphic-conversion' methods are constructed. =============== Diff against System-bf.966 =============== Item was changed: ReferenceStream subclass: #SmartRefStream instanceVariableNames: 'structures steady reshaped renamed renamedConv superclasses progressBar objCount classInstVars' classVariableNames: 'ScannedObject' poolDictionaries: '' category: 'System-Object Storage'! + !SmartRefStream commentStamp: 'hjh 10/14/2017 16:30' prior: 0! - !SmartRefStream commentStamp: 'nice 3/25/2010 23:03' prior: 0! Ordinary ReferenceStreams assume that the names and order of instance variables is exactly the same when an object file is written and read. SmartRefStream allows object files to be read even after instance variables have changed or the entire class has been renamed. When an object file is written, no one knows how the classes will change in the future. Therefore, all conversion must be done when the file is read. The key is to store enough information in the file about the names of the instance variables of all outgoing classes. SmartRefStream works best with only one tree of objects per file. You can nextPut: more than once, but each object tree gets its own class structure description, which is big. + Conversion of old objects is done by a method in each class called (convertToCurrentVersion: varDict refStream: smartRefStrm). At fileOut time, ChangeSet>>checkForConversionMethods creates a prototype of this method (if Preference #conversionMethodsAtFileOut is true). The programmer must edit this method to + (1) test if the incoming object needs conversion, + (2) put non-nil values into any new inst vars that need them, and + (3) save the data of any inst vars that are being deleted. - Conversion of old objects is done by a method in each class called (convertToCurrentVersion: varDict refStream: smartRefStrm). At fileOut time, ChangeSet>>checkForConversionMethods creates a prototype of this method (if Preference #conversionMethodsAtFileOut is true). The programmer must edit this method to (1) test if the incoming object needs conversion, (2) put non-nil values into any new inst vars that need them, and (3) save the data of any inst vars that are being deleted. + Determining which old version is represented by the incoming object can be done in several ways: + - noticing that a current inst var is nil when it should have data, + - noticing that there is an older inst var name in the variable dictionary (varDict), + - checking kinds of objects in one or more inst vars, or + - retrieving the classVersion of the incoming object from the ref stream. - Determining which old version is represented by the incoming object can be done in several ways: noticing that a current inst var is nil when it should have data, noticing that there is an older inst var name in the variable dictionary (varDict), checking kinds of objects in one or more inst vars, or retrieving the classVersion of the incoming object from the ref stream. + If a class is renamed, a method goes into SmartRefStream telling the new name. - If a class is renamed, a method goes into SmartRefStream telling the new name. The conversion method of the new class must be prepared to accept instances of the old class also. If no inst var names have changed, the conversion method does nothing. + The conversion method of the new class must be prepared to accept instances of the old class also. If no inst var names have changed, the conversion method does nothing. + + + + An example: + Suppose we change the representation of class Rectangle from ('origin' 'corner') to ('origin' 'extent'). Suppose lots of Rectangle instances are already out on files (in .pr project files, especially). - Suppose we change the representation of class Rectangle from ('origin' 'corner') to ('origin' 'extent'). Suppose lots of Rectangle instances are already out on files (in .pr project files, especially). - The programmer changes the class definition, modifies all the methods, and filesOut. A series of dialogs appear, asking if instances Rectangle might be in an object file, if 'extent' needs to be non-nil (yes), and if the info in 'corner' needs to be preserved (yes). This method appears: + The programmer changes the class definition, modifies all the methods, and filesOut. A series of dialogs appear, asking if instances Rectangle might be in an object file, if 'extent' needs to be non-nil (yes), and if the info in 'corner' needs to be preserved (yes). This method appears: + Rectangle >> convertToCurrentVersion: varDict refStream: smartRefStrm "These variables are automatically stored into the new instance: #('origin'). Test for this particular conversion. Get values using expressions like (varDict at: 'foo')." "New variables: #('extent'). If a non-nil value is needed, please assign it." "These are going away #('corner'). Possibly store their info in some other variable?" "Move your code above the ^ super... Delete extra comments." ^ super convertToCurrentVersion: varDict refStream: smartRefStrm The programmer modifies it to be: Rectangle >> convertToCurrentVersion: varDict refStream: smartRefStrm (varDict includesKey: 'extent') ifFalse: ["old version!!" "Create the new extent, and preserve the info from the old corner" extent := (varDict at: 'corner') - origin. ]. ^ super convertToCurrentVersion: varDict refStream: smartRefStrm This conversion method stays in the system and is ready to convert the old format of Rectangle whenever one is encountered in an object file. Note that the subclasses of Rectangle, (B3DViewport, CharacterBlock, and Quadrangle) do not need conversion methods. Their instances will be converted by the code in Rectangle. + Files written by SmartRefStream are in standard fileout format. You can mix raw objects with code to be filed in. The file starts out in the normal fileOut format. Definitions of new classes on the front. structures Dictionary of (#Rectangle -> #(<classVersionInteger> 'origin' 'corner')). Inst var names are strings. steady Set of Classes who have the same structure now as on the incoming file. Includes classes with same inst vars except for new ones added on the end. reshaped Dictionary of Classes who have a different structure now from the incoming file. Includes those with same inst vars but new version number. (old class name -> method selector to fill in data for version to version) renamed Dictionary of Classes who have a different name. Make an instance of the new class, and send it the conversion call. (old class name symbol -> new class name). renamedConv Dictionary of conversion selector for Classes who have a different name. (old class name symbol -> conversion selector). topCall Tells if next or nextPut: are working on the top object in the tree. nil if outside, the top object if deep inside. See DataStream.typeIDFor: for where the tangle of objects is clipped, so the whole system will not be written on the file. No object that is written on the file is ever a class. All class definitions are filed in. A class may be stored inside an ImageSegment that itself is stored in a SmartRefStream. + + + UniClasses are classes for the instance specific behavior of just one instance. Subclasses of Player are an example. When a UniClass is read in, and a class of the same name already exists, the incoming one is renamed. ObjectScanner converts the filed-in code. Values in instance variables of UniClasses are stored in the array that tells the class structure. It is the fourth of the four top level objects. #(version (class-structure) the-object ((#Player25 scripts slotInfo costumeDictionary) (#Player26 scripts slotInfo costumeDictionary))). There is a separate subclass for doing veryDeepCopy (in memory). Currently, any object for which objectToStoreOnDataStream return an object other than self, does this: The new object (a DiskProxy) is traced. When it comes time to go through the fields of the old object, they are not found as keys in references (DiskProxies are there instead). So the old field value is left in the new object. That is OK for StrikeFont, Class, MetaClass, DisplayScreen. But the DiskProxies are evaluated, which takes a lot of time. Some metaclasses are put into the structures table. This is for when a block has a receiver that is a class. See checkFatalReshape:. ImageSegments: A ReferenceStream is used to enumerate objects to put inside an ImageSegment. If an instance of a UniClass is seen, the class is put in also. A SmartRefStream is used to store the ImageSegment. Roots are nil, and the segment is a wordArray. We are encoding the outPointers. Structures contains all classes from both places. Must filter out UniClasses for some things, and do include them for putting source code at end of file. Do not write any class inst vars in file. + --Ted Kaehler and Bob Arning. + + + + How are the selectors in the '*Morphic-conversion' protocol ending with something like + + ttfclpomsswfpp0 + + constructed and what does it mean? + + + Answer: + It is the initials of all instance variables followed by the class version integer. The initials allow to detect most changes to the instance variables, but if this is not sufficient (perhaps because the new var had the same initial, or the vars did not change in name at all) we still have the class version. + + Most classes are still at version 0, but if you check implementers of classVersion you can find a few that were incremented to force a conversion on load.! - !

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
14
Older →

Jump to page: