Squeak-dev October 2007

squeak-dev@lists.squeakfoundation.org

151 participants
195 discussions

Re: [OT] An artifact of possible interest...
by Laurence Rozier 06 Oct '07

06 Oct '07

This is great - thanks Dan! On 10/4/07, Dan Ingalls <Dan(a)squeakland.org> wrote: > > Folks - > > As many of you know, I and a couple of friends at Sun have been > playing around with JavaScript, and we've finally figured out out how > to have fun with a browser. > > You can find out all about it at... > > http://research.sun.com/projects/lively/ > > ...and if you have a very recent build of Safari (preferably Webkit > nightly builds) or FireFox (preferably latest Gran Paradiso build), > then you can probably have fun with it too! > > It's not at all polished, but it should look strangely familiar ;-) > > Enjoy > - Dan > >

1 0

Where's the WatchMorph in 3.10?
by Simon Guest 06 Oct '07

06 Oct '07

Hi, PDAMorph from SqueakMap loads fine in 3.9, but in 3.10 it fails, because the WatchMorph has been removed from the image. Oh, in both cases I mean the squeak-dev images. Did it go to SqueakMap, or was it simply discarded? Can I get it back from somewhere? cheers, Simon

12 14

running class methods directly from OmniBrowser menu?
by Petr Fischer 05 Oct '07

05 Oct '07

Hi, now... I am thinking about "class methods" side in OmniBrowser - is possible to add menu item "run it" (at the first place in menu) for direct run given class method (without typing in workspace, ideal for example methods, setup and config utility methods etc.)? Is it usefull for others? Any volunteer from OmniBroser team? Thanks, pf

2 1

DeltaStreams again
by Göran Krampe 05 Oct '07

05 Oct '07

Hi! After yet another night of hacking I have come a bit further. I started working on #apply and #revert. #revert is implemented like: self asAntiDelta apply ...and asAntiDelta is more or less done by: changes reverseDo: [:each | antiDelta addChange: each asAntiChange] ...modulo my memory. ;) I came as far as a test case where I create a DSDelta with three changes: - Create class - Change its comment - Add two ivars ..and then can nuke the class, apply delta (Johnny is back!) and revert delta (Johnny is gone again!). Well, apart from some buglet in SystemEditor regarding class comment - this works. DSDelta>>apply looks something like: ^self class applier apply: self Which means the actual apply code is broken out into an "applier" object which uses double dispatch on all change instances to do the work. I am implementing a DSSystemEditorApplier. Well, that is it for now. :) Note though that I am doing a bit of "spiking" here - all kinds of changes are not working yet and so on. regards, Göran

3 4

[ANN] OSC (Open Sound Control
by Simon Holland 05 Oct '07

05 Oct '07

Hi All I have just uploaded a new version of OSC (Open Sound Control) which adds a number of enhancements and fixes. It tests all green, but please let us know if you find any problems. Open Sound Control is • used in music and sound applications (e.g. SuperCollider), • used in tangible user interaction using video tracking (e.g. Tuio for Squeak), • a fast, flexible, light, easy to use, general purpose connector in cases where you would otherwise need to write a plugin. Changes in this version OSC has been enhanced to deal with bundles, intensive input, and the Tuio protocol. Various bug fixes and new unit tests have been added. No changes are required for clients. New features are as follows. 1 Bundles processed fully When several incoming messages arrive in a single bundle, or more than one bundle arrives at once, all messages are now parsed. This involved changes to the OSCParser method parse: and to the OSCServer message receive: This necessitated changes to three parser unit tests, and one new unit test. 2 Word boundaries treated correctly in string arguments. The method parseString in OSCParser now only consumes trailing nulls (after the null that terminates the string) if this is needed to reach a 32-bit word boundary, as per the OSC specification. This avoids problems where subsequent integers, floats etc in messages could be corrupted. A second new unit test was added. 3 Incoming OSC buffers resized to cope with high volume input. Incoming OSC packets of 940 bytes and larger are routinely sent by Reactivision. The incoming String and RWBinaryOrTextStream buffers in OSCServer listenOnPort: have been resized to cope with high volume incoming traffic. 4 OSCServer processing balanced. In some circumstances, the looping background UDP read thread in OSCServer listenOnPort: can monopolise the processor, preventing other threads from processing the input in timely fashion. The method receive: in OSCServer has been given a delay to allow upstream processes to get adequate processor time. An instance variable responsePeriod measured in milliseconds has been added to OSCServer, and initialised in initialize to allow this delay to be tuned conveniently for different applications. In the case of applications of Reactivision, a 10 millisecond delay is a suggested starting point. This delay can be set to zero where not needed. 5 Bug fix to prevent exception in parseHeader in OSCParser OSCParser was erroneously testing for a character in a binary stream and throwing an exception. The method parseHeader in OSCParser has been amended to put the stream into ascii mode at the crucial point. 6 Minimal measure to ignore blobs more gracefully. A dummy method has been added to ignore blobs, rather than throwing an exception. If a blob message is spuriously recognised as a result of a glitch (which occasionally happens), it is very likely to be the last or only message in the bundle, so that this rudimentary measure will allow it to be discarded without causing an exception. A future version could be coded to handle blobs properly, or raise and handle an appropriate custom-designed exception. Summary of changes a) One new, and two revised, instance methods for OSCParser parseHeader parseString parseBlob b) One revised class method for the OSCParser parse: c) Three revised instance methods for OSCServer. initialize listenOnPort: receive: d) Five revised unit tests OSCParserTest testParseIncreaseVolumeMessage OSCParserTest testParseExampleBerkely3Message OSCParserTest testParse OSCMessageTest testByteArrayDecreaseVolume OSCServerTest testSendAndReceive The first three tests are required by the representation change introduced by (1) above. In the fourth test, the literal array used to represent 0.2 using an IEEE32Bit Float representation has been corrected. In the fifth test (which fails only intermittently as it involves a timing delay), the wait period before reading has been changed from 1 millisecond to 30 milliseconds. e) Two new unit tests OSCParserTest2 and OSCParserTest3 test the integrity of enhancements/fixes 1-3 and 5. These tests would benefit from being split into several smaller tests, but they are adequate to identify the presence or absence of the relevant behaviours. Simon Holland -- View this message in context: http://www.nabble.com/-ANN--OSC-%28Open-Sound-Control-tf4568812.html#a13039… Sent from the Squeak - Dev mailing list archive at Nabble.com.

2 1

[OT] An artifact of possible interest...
by Torsten Bergmann 05 Oct '07

05 Oct '07

>> Cool! Does it support namespaces? >I'm sure that's the first thing it needs. > >SCNR > >- Bert - I'm sure it needs namespaces. Otherwise you get lot's of proposals and discussion later on the livekernel-dev list ;) SCNR Bye Torsten -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

1 0

[ANN] Tuio - Tangible User Interaction by video tracking physical objects.
by Simon Holland 05 Oct '07

05 Oct '07

Hi All I have just uploaded the first version of Tuio for Squeak. Tuio allows Squeak to use the reacTIVision computer vision system to track physical objects in real time. The package includes a Tuio client and demonstration application program. To make practical use of Tuio for Squeak you will need a webcam or other camera, and should download the free Reactivision application for your operating system. To learn more, see http://mcs.open.ac.uk/sh2/squeakmusic.html). Tuio for Squeak makes it easy to build tangible user interfaces using fiducial markers on physical objects. Tuio for Squeak allows the rapid development of table-based tangible user interfaces (TUI) and multi-touch interactive surfaces. Prerequisite Package - OSC 5.1 or later Please let me know if you find any problems. Thanks Simon Holland -- View this message in context: http://www.nabble.com/-ANN--Tuio---Tangible-User-Interaction-by-video-track… Sent from the Squeak - Dev mailing list archive at Nabble.com.

5 7

old menu bug (still here)
by Petr Fischer 05 Oct '07

05 Oct '07

Hi, I reported menu bug in mantis (May 2006 - bug number 5608). There is a hardwired menu title border width at the end of method MenuMorph>>addTitle: aString icon: aForm updatingSelector: aSelector updateTarget: aTarget Why? For menu title border width, there is a attribute in squeak theme classes (look at ColorTheme>>menuTitleBorderWidth). Is possible to fix this old issue in 3.10? (Fix is attached in mantis bug report) Thanks, pf

2 1

Quick comparison of two Namespaces proposals
by Göran Krampe 05 Oct '07

05 Oct '07

Hi folks! I just read through Michael van der Gulik's page: http://gulik.pbwiki.com/Namespaces Just stumbled over it btw, and I have only read it once and wrote down some notes compared to my own little "venture" in this area: http://swiki.krampe.se/gohu/32 Which I like to call "Prefixes Improved" perhaps. Anyway, here goes and this is mainly addressed to Michael btw. Namespace comments: - I personally think hierarchical namespaces is "too much". I opted for single level namespaces and still think that is enough. - I personally don't like the "." notation for namespaces, especially since we already use "." for statement separation. I still think "::" is the best I have seen, although granted - this is a tiny, tiny detail. - Imports are done in your code "per Namespace" which is immensely better than like for example in Java where it is per class (well, per file, but anyway). It is still though the major difference with my proposal in which there are *no* explicit imports at all. - I agree that shared pools theoretically could be replaced with Namespaces, but then we actually have imports *per class*, which I really don't like. You may argue, "but we already have them!" - yes, I agree, but I don't like them anyway and in my proposal I opted out by simply ignoring/not touching them. :) - Your Namespaces are linked to a Package scheme, I personally would like to keep these concepts separate. So... to sum it all up: - You also bind at compile time just like globals are bound now (and just as in my code). No difference. - You also reify the namespaces as instances of Namespace, as I do. No difference, though you intend to nuke SystemDictionary - I don't. - You also have a Dictionary protocol on the Namespaces enabling normal dynamic lookup just as I have. Kinda normal if you reify them as objects of course. But... - You go hierarchical, I stayed simple and kept it on one level. - You use ".", I use "::". - Your code use *both* qualified names (long with dot-notation) and non qualified names (short), I *always* use qualified names in the source and only let the tools "render" them short (or accept writing them short) when they are indeed unique or when the user has a policy that allows a lookup - like for example resolving by default to "local names" (in the same Namespace). - You added an explicit import list per Namespace, I opted to not have imports at all. - You coupled Namespaces with Packages, I did not at all go there. So the big differences are the two last ones - Explicit import lists vs my approach of no-imports-render-and-accept-short-names and mixing it with a package concept vs not doing that. :) regards, Göran

24 81

[OT] An artifact of possible interest...
by astares＠gmx.de 05 Oct '07

05 Oct '07

Hi Dan, Cool! Does it support namespaces? If not see code below. Would be interesting to see lively on the client and Squeak seaside on the server side... Cheers Torsten ------------------------------------------------------------------------- /* * Define a new global namespace * * @param {Object} namespace */ function Namespace(namespaceName) { var nsParts = namespaceName.split("."); var root = window; for(var i=0; i<nsParts.length; i++) { if(typeof root[nsParts[i]] == "undefined") root[nsParts[i]] = new Object(); root = root[nsParts[i]]; } } /*Lets define the namespace */ Namespace('org.squeak.domain'); /* Class constructor */ org.squeak.domain.Person = function(firstName, lastName) { this.name = lastName; this.firstName = firstName; } org.squeak.domain.Person.prototype = { fullName: function () { return this.firstName + " " + this.name; } } /* Create an instance of person and call a method/function*/ var person = new org.squeak.domain.Person('Dan','Ingalls'); alert(person.fullName()); -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

2 1

Jump to page: