Hi Marcel,
Those are some worthwhile criticisms. If you post them on the webteam list, then there will be a record of them in a place where they can be of some use.
Thanks,
Chris
Tobias Pape uploaded a new version of Collections to project The Trunk:
http://source.squeak.org/trunk/Collections-topa.565.mcz
==================== Summary ====================
Name: Collections-topa.565
Author: topa
Time: 25 March 2014, 2:28:36.459 pm
UUID: b7c264b3-1e69-494d-8979-6f71bc9b846d
Ancestors: Collections-ul.564
When a stream is created on a collection, it tries to keep
using that collection instead of copying, even in the case
of mutation of the original collection.
The code removed prevented this.
=============== Diff against Collections-ul.564 ===============
Item was changed:
----- Method: WriteStream>>nextPut: (in category 'accessing') -----
nextPut: anObject
"Primitive. Insert the argument at the next position in the Stream
represented by the receiver. Fail if the collection of this stream is not an
Array or a String. Fail if the stream is positioned at its end, or if the
position is out of bounds in the collection. Fail if the argument is not
of the right type for the collection. Optional. See Object documentation
whatIsAPrimitive."
<primitive: 66>
- ((collection class == ByteString) and: [
- anObject isCharacter and:[anObject isOctetCharacter not]]) ifTrue: [
- collection := (WideString from: collection).
- ^self nextPut: anObject.
- ].
position >= writeLimit
ifTrue: [^ self pastEndPut: anObject]
ifFalse:
[position := position + 1.
^collection at: position put: anObject]!
Tobias Pape uploaded a new version of CollectionsTests to project The Trunk:
http://source.squeak.org/trunk/CollectionsTests-topa.215.mcz
==================== Summary ====================
Name: CollectionsTests-topa.215
Author: topa
Time: 25 March 2014, 2:27:43.108 pm
UUID: cb44512a-51f4-4cef-8d33-336b520e113f
Ancestors: CollectionsTests-dtl.214
When a stream is created on a collection, it tries to keep
using that collection instead of copying, even in the case
of mutation of the original collection.
=============== Diff against CollectionsTests-dtl.214 ===============
Item was added:
+ ----- Method: WriteStreamTest>>testStreamAlwasyUseGivenCollection (in category 'tests - instance creation') -----
+ testStreamAlwasyUseGivenCollection
+ "self debug: #testStreamUseGivenCollection"
+
+ "When a stream is created on a collection, it tries to keep using that collection instead of copying,
+ even in the case of mutation of the original collection."
+
+ |string stream|
+
+ string := String withAll: 'xy'.
+ stream := WriteStream on: string.
+
+ stream nextPut: $a.
+ stream nextPut: (Character codePoint: 269). "wide."
+ self assert: string = (String with: $a with: (Character codePoint: 269)).!
Hey Johan,
On 23.03.2014, at 10:59, Johan Brichau <johan(a)inceptive.be> wrote:
> Hi all,
>
> Currently, both Grease-1.1.6 and Seaside-3.1 have failing tests on Squeak.
> The github repository has automated Travis CI builds setup for Squeak [1,2], so we can easily monitor this:
>
> [1] https://travis-ci.org/glassdb/Grease
> [2] https://travis-ci.org/glassdb/Seaside31
>
I am on it.
Sadly builder-ci needs a small patch to cope for the fact that
the released 4.4 image still hast a redirect bug...
> It would be good if someone can fix them or tell me to mark some parts as non-loadable on Squeak (e.g. Slime in Squeak).
> Otherwise, I will disable the automated builds as they are now always reporting a failure.
GREASE:
I have fixed the only one Test that failed for me in Squeak 4.4 and Squeak 4.5.
The fix is in Grease-Slime-topa.26.
SEASIDE:
Also here, only one test failed.
The fix is in Seaside-Core-topa.811.
>
> The github repo's master branch is a mirror of the smalltalkhub one:
> https://github.com/glassdb/Seaside31
>
> The Travis CI build for that is here:
> https://travis-ci.org/glassdb/Seaside31
>
> You just need to make sure you check the build for the master branch, e.g.: https://travis-ci.org/glassdb/Seaside31/builds/19433103
>
> Similar for Grease, but here is only one branch for all platforms:
> https://github.com/glassdb/Grease
> https://travis-ci.org/glassdb/Grease
>
> If you have fixes, you can immediately commit them to Smalltalkhub, or you can create a fork of the github repo and submit a pull request.
> Either way, I will pick up the changes and make sure to sync the repositories.
:) Ok Fixes are in the STHub repo
Should https://github.com/dalehenrich/builderCI/pull/59 be accepted, please
add Squeak-4.5 to the test matrix :)
Thanks for taking care!
Best
-Tobias
> ----- Original Message -----
> From: Bert Freudenberg
> Sent: 03/24/14 05:56 AM
> To: The general-purpose Squeak developers list
> Subject: Re: [squeak-dev] SqueakNOS on Raspberry Pi
>
> On 24.03.2014, at 13:50, askoh <askoh(a)askoh.com> wrote:
>
> > http://tessel.io/
> > is building a microcontroller running pure JavaScript - no OS.
> >
> > Can we have pure Smalltalk running on Raspberry Pi or equivalent? How hard
> > would it be? Is SqueakNOS a candidate for that?
>
> https://github.com/pablomarx/RaspberrySqueak
>
> - Bert -
Does MicroSqueak fit into this discussion?
http://web.media.mit.edu/~jmaloney/microsqueak/readme.txthttp://lists.squeakfoundation.org/pipermail/vm-beginners/2011-January/00004…
Is the RPi more suitable to an MVC gui than a Morphic one?
What does one do with a SqueakNOS. My instinct is that the answer is, "A lot!".
It has been a long time since I have mucked around with hardware, but I have an
RPi running Squeak and dream of it's potential.
-jrm
http://tessel.io/
is building a microcontroller running pure JavaScript - no OS.
Can we have pure Smalltalk running on Raspberry Pi or equivalent? How hard
would it be? Is SqueakNOS a candidate for that?
Thanks,
Aik-Siong Koh
--
View this message in context: http://forum.world.st/SqueakNOS-on-Raspberry-Pi-tp4750488.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.
Back in the Old Days of squeak… um, 3-ish?, we used to have an event named #mouseHold: that was triggered if the mouse button was held do for longer than 6650mS without being released. The old Scratch code has been using that to provide one way of popping up a menu.
T’ain’t there no more. There *is* #doubleClickTimeout: but that relies upon the button being released or there not being a drag selector in use. I’m more than a bit conflicted about even trying to replicate the functionality since you have to not move the mouse during the time interval, and mixing the gestures for select and menu makes me squirm a bit. On the other hand, it’s what’s expected in this case and I don’t want to disappoint users.
Generally I’m also little surprised to see how many cases in MouseClickState>handleEvent:from: actually send the double click timeout event - it’s hard to see what it is expected to be used for with no exemplars or comments to hand.
Does anyone recall any reasoning behind the changes?
tim
--
tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: RPSW: Randomize Program Status Word
Should class comments be separated from source code?
I think it should be separated into two files, the reasons are,
1. current comment not enough for understood (less or nothing)
2. if I added new comment , it is not convenient when update or load new
packages
3. comment is knowledge about how to use, how to change the application, it
could be shared and accumulated
4. comment should be stand alone as knowledge base with different local
languages
I hope Squeak 4.6 gives a new comment tool in system browser
Three files: Soure file, Changes and Comments file,
Hope Squeak better!
Liang Bing
--
View this message in context: http://forum.world.st/Should-class-comments-be-separated-from-source-code-t…
Sent from the Squeak - Dev mailing list archive at Nabble.com.