Squeak-dev July 2006

squeak-dev@lists.squeakfoundation.org

132 participants
241 discussions

Start a nNew thread

bugs on mantis: who assigns them ?
by Dan Corneanu 05 Sep '06

05 Sep '06

Hi, how do bugs on mantis get assigned to someone? Who is responsible for this?

15 25

Experimental Fedora Core 5 packages
by Giovanni Corriga 10 Aug '06

10 Aug '06

Hi all, I've created some Squeak 3.9b RPM packages for the Fedora Core 5 Linux distribution. These packages are experimental, so I need some help in testing them and in fixing them according to the packaging rules of Fedora. Once they are reasonably bug-free, I want to submit them to a package repository (Fedora Extras if possible, otherwise a third-party one like rpm.livna.org). The packages maybe found at http://smalltalkit.seasidehosting.st/seaside/pier/RPMPackages . I'd like to thank Ian Piumarta, who kindly provided the templates I used for the .spec files, and also nasrat on the #rpm IRC channel, who helped me fix some bugs in my vm package. Giovanni

2 2

Condensed Sources vs. Squeak Maintainence
by Peace Jerome 02 Aug '06

02 Aug '06

Hi all, I've noticed that condensing sources is on the todo list of the 3dot9 gamma push. One of the deliverables with 3dot9 final should be a 3.10 with all changes from 3.0. As one who looks into squeak code for understanding I have found that the full version history really speeds tracking down bugs. Often it is the only good way to discover the programers intent. It is also important to know how many have mucked in a particular piece of code. A large number of cooks is one of the smell tests for troubled code. So I am very concerned that 3.9 gamma might lose all this information when the sources get created anew. It seems to me poor timing to do it at the end of the development cycle. A better plan IMHO would be to bring out 3.9 without compressing the sources. Then compress sources as the first (and possibly last step) of a 3.10. If you choose to do only source compression for 3.10 you would have an adoptable squeak; and a fall back to 3.9 with the full history around for maintainence sake. With both 3.9 and 3.10 representing the same point of development you would not have to do 3.9 full. You would do 3.10 full. And if you ran into problems you could check it against 3.9 full and get your insights that way. That makes more sense. The numbering even suggest a major point. (Or you could call the compressed source version 4.0 and let the spoon version be 5.0). I believe a great deal of code will rot and squeak will become a lot more fragile than it already is if you compress sources now before 3.9 is finalized. Thank you for your attention to these concerns. Yours in service, -- Jerome Peace "Version numbers are cheap. It is patience that is precious." __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

7 29

Kernel.image update for 7052 and my vision of the next development
by Pavel Krivanek 02 Aug '06

02 Aug '06

Hi all, There's the new update for my kernel image for Squeak 3.9 (without next packages) http://www.comtalk.net/Squeak/uploads/20/bootstrap7052.zip If you run "Bootstrap new browseOverrides", you can see list of all changed methods. This image overrides only 122 methods so I hope that it will be quite easy to begin with refactoring of full Squeak (3.10) to minimize the amount of necessary overrides and publish it on Mantis. We should use some special mark (e.g. [KERNELIMAGE]) for such patches or create new project. The most important refactorings: ======================= - ChangesOrganizer that picks general changes manipulations from the ChangeSorter tool and makes that operations independent on it. Andreas already published similar patch some time ago but it was not accepted. This invokes overriding of very small set of methods in the kernel but the impact on the full image will be much bigger (but in most cases it will be only renaming from ChangeSorter to ChangesOrganizer) XxxChangeSetCategory >> reconstituteList XxxChangeSetCategory >> changeSetList XxxChangeSetCategory >> includesChangeSet: XxxChangeSetCategoryWithParameters >> reconstituteList XxxChangeSetCategoryWithParameters >> includesChangeSet: XxxFileStream >> fileIntoNewChangeSet - extend UIManager to make the kernel independent on UI. It's about 30 methods it means to take the current source and create the corresponding code in the MorphicUIManager or MVCUIManager XxxAbort >> defaultAction XxxBlockCannotReturn >> defaultAction XxxChangeSet class >> promptForDefaultChangeSetDirectoryIfNecessary XxxContextPart >> doPrimitive:method:receiver:args: XxxDisplayScreen >> restoreAfter: XxxDisplayScreen >> restore XxxDisplayScreen >> newDepthNoRestore: XxxDisplayScreen class >> checkForNewScreenSize XxxDisplayText >> composeForm XxxError >> defaultAction XxxEventSensor >> startUp XxxFileDirectory >> rename:toBe: XxxFileDoesNotExistException >> defaultAction XxxFileExistsException >> defaultAction XxxHalt >> defaultAction XxxMethodContext >> cannotReturn: XxxObject >> primitiveError: XxxProcess >> debug:title:full: XxxProgressInitiationException >> defaultAction XxxSmalltalkImage >> snapshot:andQuit:embedded: XxxStandardFileStream class >> fileExistsUserHandling: XxxStrikeFont class >> fromUser: XxxSyntaxErrorNotification >> defaultAction XxxSystemDictionary >> lowSpaceWatcher XxxSystemDictionary >> handleUserInterrupt XxxTextStyle class >> replaceFontsIn:with: XxxUnhandledError >> defaultAction XxxUtilities class >> informUserDuring: XxxUtilities class >> informUser:during: XxxWarning >> defaultAction So if anybody wants to help with Squeak modularization, this is the right sand to play. The next step is to discuss the rest of overrides (maybe we should create Mantis record for each). Then we should create clean package The Rest of Squeak. The phase of its loading is simple because that means only to authomatically create the set of new classes, methods and very small set of overrides. We will need small basic image without all packages that can be safely removed (FFI etc.) for that. The biggest problem is to initialize fully working Morphic world (but we are already able to do that partly). I expect that then we will be able to create script that will shrink the image to the kernel without self-bootstrapping process. So as the result we may have "our" (not only "my") kernel image. The final basic image will be almost the same as the current image so we will burn no important bridges but we will have well described process of Morphic initialization and (still little messy but usable) kernel (maybe not official for end-users but important part of Squeak development and modularization). I would like to see it as the main goal for Squeak 3.10. I expect that it may take about two or three months. Your comments? Cheers, -- Pavel

5 15

[SqNOS] New release: RTL8139 support, TCP/IP "working", native improvements
by Gerardo Richarte 02 Aug '06

02 Aug '06

Download: http://sourceforge.net/project/showfiles.php?group_id=3891&package_id=3865 swiki: http://minnow.cc.gatech.edu/squeak/1762 This release includes two NetworkingDevices: LancePCIDevice and Realtek8139PCIDevice, the former implementing support, at least, for VMWare virtual cards, and the latter for a very common real network card. We have partially integrated NetSqueak (http://www.squeaksource.com/Net.html), which gives SqueakNOS support for most of the TCP/IP protocol suite, including basic, but working, TCP. The native part has changed a little bit too, specially a bug fix to allow bigger images to be booted (27MB was the old limit, now phisical memory should be it). Also the timer interrupt frequency is increased to 2KHz and ioRelinquishProcessor... effectively halts ('hlt') the processor. This decreases the power consumption, and introduced a few interactivity glitches that we should solve. gera

3 3

Audio File playing without echo
by radouane el marjani 01 Aug '06

01 Aug '06

Hi, I writte a code like that : /------------------------------------------------------------------------------------------------------------------------------ tonMenu := StreamingMP3Sound onFileNamed: 'toene\LektionenToene\Lektion5\ton7.mp3'. tonCurrent := tonMenu. tonCurrent volume: (self volumeTon: volumeCurrent). tonCurrent play. tonCurrent repeat: true. -------------------------------------------------------------------------------------------------------------------------------- /My Problem is, my ton come not like I have recorded, he come with "echo". Have someone an idea so that, my Ton without echo coming. is there a Methode, which allow a audi file playing without echo or Hall?. I don't find anyone im Bibliothek. Thanks for Help, Radouane. ___________________________________________________________________________ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com

4 3

Suggestions for C++ or DLL code
by Ron Teitelbaum 01 Aug '06

01 Aug '06

Hello all, I'm currently working on a TLS / SSL implementation and on windows I am planning to support the Certificate Store that is built in. This requires me to use the CryptoAPI dlls. The code is complex and it uses a number of header files and many steps. I built some C++ code that does what I'm looking for so now I would like to incorporate this into Squeak. I'd assumed that FFI was like DDL/C connect in VW but that's not what I'm seeing. So my question is: What is the best way to get this working? Should I hack away at FFI and support the api directly, and is that even possible? Should I create DLL's to call and use them with FFI, or should I compile some sort of plugins? My preference would be to call the api directly without having to create dll's, duplicating my C++ code in Smalltalk if possible. Some direction and comparisons of different options would be very helpful. Thank you for your help! Ron Teitelbaum

11 31

SIXX troubles and advanced use
by florent trolat 01 Aug '06

01 Aug '06

Hi, 1/ I'm playing with SIXX and I call upon your memory about troubles with it. I've already seen some troubles in mailing list archives... 2/ Have you big (critic) applications using sixx? 3/ The SiXX description says: > Advanced users can implement custom serialization/deserialization > format by overriding only a few hook methods Maybe someone have tried to do something like this? Thanks FLO

4 16

Icons in Unix
by Keith Hodges 01 Aug '06

01 Aug '06

I know that when developing a server one should not be interested in such trivialities, but, does squeak have any icons in the KDE/Linux world? At the moment on my installation squeak is a X11 logo which just feels so wrong. Keith ___________________________________________________________ Try the all-new Yahoo! Mail. "The New Version is radically easier to use" The Wall Street Journal http://uk.docs.yahoo.com/nowyoucan.html

6 6

Seaside Meeting on the Leftshore
by Boris Popov 31 Jul '06

31 Jul '06

What: Informal Seaside/Squeak/VisualWorks/Smalltalk Meet Up When: Friday, August 18, 2006 @ 6:00PM PST Where: Stamp's Landing Neighborhood Pub - 610 Stamps Landing, Vancouver, BC Who: Everyone with interests in Seaside, Squeak, VisualWorks and anything else to do with Smalltalk is welcomed to join us for a beer (coffee, milk, coke, juice, water) or two and informal chat about state of things in the Seaside world and whatever else people choose to catch up on. There is no agenda, simply because putting a bunch of passionate Smalltalkers in the same room seems to turn into a good thing on its own, so why ruin it? ;) So far we have myself from DeepCove as well as folks from Smallthought confirmed in attendance, please comment or email if you are planning on coming, or simply drop by the pub if you wish to stay anonymous. More people, the merrier, so pass this message on. http://leftshore.wordpress.com/2006/07/31/seaside-meeting-on-the-leftshore/ Cheers! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 boris(a)deepcovelabs.com CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you.

4 4

Jump to page: