Squeak-dev February 2008

squeak-dev@lists.squeakfoundation.org

159 participants
219 discussions

Re: [squeak-dev] Re: Re: A better looking text caret (IMO)
by Ken G. Brown 25 Feb '08

25 Feb '08

Just curious - why won't Preferences>>caretWidth: do the setting? Ken G. Brown <> > > "Igor Stasenko" <siguctua(a)gmail.com> wrote in message > > news:4a5f5f320802240915g11780490i9ab393b5ed605da0@mail.gmail.com... >> >> > http://bugs.squeak.org/view.php?id=6948 >> >> > > I've added an implementation for a blinking caret to this mantis entry. > <>

1 0

Re: [squeak-dev] 3.10 image
by Ken G. Brown 25 Feb '08

25 Feb '08

I've noticed that sq3.10-7159dev08.02.1 right out of the zip is 65.2 MB but after executing Keith's level playing field script and a few other things, then doing as Esteban Lorenzano <estebanlm(a)gmail.com> did in his sample script recently posted here on Mon, 11 Feb 2008. "******************************" "Cleanups" "******************************" MCFileBasedRepository flushAllCaches. Smalltalk garbageCollect. then: "*** Save as a new version ***************************" SmalltalkImage current saveAsNewVersion. the image is then only 20.2 MB. By the way, I'm finding that Keith's Installer <http://installer.pbwiki.com/Installer> is great! Ken G. Brown At 2:23 AM -0800 2/25/08, squeak-dev-request(a)lists.squeakfoundation.org apparently wrote: >Date: Mon, 25 Feb 2008 00:02:10 -0600 >From: Miguel Enrique Cob? Mart?nez <m.coba.m(a)gmail.com> >Subject: Re: [squeak-dev] 3.10 image >To: The general-purpose Squeak developers list > <squeak-dev(a)lists.squeakfoundation.org> >Message-ID: <47C259E2.4040906(a)gmail.com> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >itsme213 wrote: >> I the damien-3.10-web image size is quite large (129M) compared to a >> comparably (not identical) loaded 3.9 Ramon's image (42M). Is that expected, >> or is it because as a beta it has not been trimmed etc.? >> >> Thanks - Sophie >> >> >> >> >> >I noted this too. But if you save the original image from Damien to a >new image (for your everyday work, so you have the original image >intact) the new saved image is trimmed to about 34MB. > >Cheers

2 1

Re: [squeak-dev] 3.10 image
by Gary Chambers 25 Feb '08

25 Feb '08

+1 from me ----- Original message ----- From: Igor Stasenko <siguctua(a)gmail.com> To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> Sent: Mon, 25 Feb 2008, 19:57:14 GMT Subject: Re: [squeak-dev] 3.10 image It's really time to think about what Keith proposed a while ago: I am all for it, to include #cleanUp message to standard Behavior protocol. So people shouldn't write own sophisticated cleanUp scripts, and do just: Smalltalk cleanUp. And package authors implement own #cleanUp in classes, where they think it needs to. (Sorry i can't find this mail in archives, so i putting it as text here) ------------------- Dear All, If possible I would like to encourage package developers to support two conventions for cleaning up images Firstly to remember to adopt the memory hogs convention (which is rarely used) of implementing #freeSomeSpace. Although the lowspace watcher currently requires potential memory hogs to register themselves, I propose implementing the methods anyway, with a utility method available via 'SmalltalkImage current freeSpace' to invoke an image wide belt tightening. #freeSomeSpace would be for cleaning out caches and so forth that would not imped normal functioning. examples: Utilities-class-#freeSomeSpace self cleanseOtherworldlySteppers Secondly to formalize #cleanUp as a message that users will send in order to try and tidy up an image as much as possible before saving or deploying. examples: In Seaside this would require: WACachedDocument class-#cleanUp self clearCache WAHalo-class-#cleanUp self initialize WAKom-class-#cleanUp self stop WARegistry class-#cleanUp self clearAllHandlers In DynamicProtocols this would require DynamicProtocols-#cleanUp self invalidateCache I am sure there are many other instances where this would be useful. how about it? Keith ------------------- -- Best regards, Igor Stasenko AKA sig.

2 1

Re: [squeak-dev] 3.10 image
by Igor Stasenko 25 Feb '08

25 Feb '08

It's really time to think about what Keith proposed a while ago: I am all for it, to include #cleanUp message to standard Behavior protocol. So people shouldn't write own sophisticated cleanUp scripts, and do just: Smalltalk cleanUp. And package authors implement own #cleanUp in classes, where they think it needs to. (Sorry i can't find this mail in archives, so i putting it as text here) ------------------- Dear All, If possible I would like to encourage package developers to support two conventions for cleaning up images Firstly to remember to adopt the memory hogs convention (which is rarely used) of implementing #freeSomeSpace. Although the lowspace watcher currently requires potential memory hogs to register themselves, I propose implementing the methods anyway, with a utility method available via 'SmalltalkImage current freeSpace' to invoke an image wide belt tightening. #freeSomeSpace would be for cleaning out caches and so forth that would not imped normal functioning. examples: Utilities-class-#freeSomeSpace self cleanseOtherworldlySteppers Secondly to formalize #cleanUp as a message that users will send in order to try and tidy up an image as much as possible before saving or deploying. examples: In Seaside this would require: WACachedDocument class-#cleanUp self clearCache WAHalo-class-#cleanUp self initialize WAKom-class-#cleanUp self stop WARegistry class-#cleanUp self clearAllHandlers In DynamicProtocols this would require DynamicProtocols-#cleanUp self invalidateCache I am sure there are many other instances where this would be useful. how about it? Keith ------------------- -- Best regards, Igor Stasenko AKA sig.

1 0

HydraStream implementation , pull or push scheme?
by Igor Stasenko 25 Feb '08

25 Feb '08

Hi all, there is two ways how to reliable communication can be implemented over non-reliable one. (maybe there is much more, but lets consider following ones). The push scheme is: when user writes to stream, stream collects data in small cache, and when cache is full or user flushes stream, it sends packet immediately to remote side. As variant, stream can flush itself periodically (each 5 ms or so) to not make receiving side starving if user sending small amounts of data, not enough to fill write cache. A receiving side tracking a sequence of packets arrived, and if sequence breaks, due to some packet lost, then it sends request to resend all packets from last valid sequence number. So, a sending stream should keep data sent lately, until remote side will confirm that it received it and resend packets in case if some data was lost. The pull scheme is: when user writes to stream, stream is just collecting a data. Flushing stream not causing data being sent. A sender may block when it's cache is full, and will unblock only when receiving side will confirm that it's received packets, which now can be discarded from write cache buffer. Data is sent only when remote side places request on receiving next packet. So, when user calls #read, a receiving side sends 'request next data packet #N' and when it's received, returns from method. Both schemes having own cos and pros, and is mainly about which operation takes preference: reading or writing. Or, maybe i should think to add options to let user choose which scheme to use? So, Side A, can choose which scheme to use for writing (and notify Side B about it), as well as Side B, can choose which scheme to use for writing. -- Best regards, Igor Stasenko AKA sig.

3 2

RE: [squeak-dev] WeakArray and use of weak collections.
by Bill Schwab 25 Feb '08

25 Feb '08

Gary, My simple-minded view of this is that anything with Shared or Weak in the name must be thread-safe. The weak collections are manipulated by at least two threads, the caller and the weakling cleanup thread. Thanks for stress testing this! Bill Gary Chambers <gazzaguru2@...> wrote: If you can think of a better way of blocking if finalization is in progress... only WeakRegistry has its own protection semaphore at present. (uses WeakKeyDictionary, rather than Identity, oddly). Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029

3 2

Set cursor position primitive does not work
by Hong Yi 25 Feb '08

25 Feb '08

Sent the following message before I subscribed to the squeak-dev list and got a pending approval message back. So just subscribed the list and resend this email to reach squeak-dev community. Thanks for any response to this question in advance. Hong _____ From: Hong Yi [mailto:hongyi@renci.org] Sent: Monday, February 25, 2008 11:54 AM To: croquet-dev(a)duke.edu Cc: squeak-dev(a)lists.squeakfoundation.org Subject: [croquet-dev] Set cursor position primitive does not work Hello, I have been trying to set cursor position to the touch position in an effort to integrate multi-touch library into a Croquet world I have developed. Basically, I wrote a listener that can receive multi-touch events and then map the events to corresponding mouse events which has worked so far, but I cannot set the cursor position to the touch position by setting cursorPoint on the Sensor. Then I found this bug filed against Squeak VM that states "Set cursor position primitive does not work" http://bugs.squeak.org/view.php?id=2406 Does anybody know the current status of this bug? It appears it does not work on the Croquet version I am currently using (i.e., pre-built/patched version of the current state of the Croquet SDK - Croquet.1.0.25.image). Does anybody have any experiences with this or any suggestions on how to make it work? Thanks, Hong

1 0

Moving HydraVM discussions to other list(s)?
by Igor Stasenko 25 Feb '08

25 Feb '08

Hello there, To all users of this list: - do you think that this list is wrong place for discussions around HydraVM? - if so, where you think it would be better, at vm-dev list, or at separate list? Currently i'm very active in this area and understand, that not all people in this list, interesting in it. So, maybe it's time to move to another place? -- Best regards, Igor Stasenko AKA sig.

8 8

[Election 2008] No extra questions were added
by goran＠krampe.se 25 Feb '08

25 Feb '08

Hi all! Forgot to mention that no extra questions were sent to me to be added to the questionnaire. Hopefully not due to lack of interest but due to the fact that the 10 existing questions are superb ;) regards, Göran

1 0

[Election 2008] Campaigning period is on!
by goran＠krampe.se 25 Feb '08

25 Feb '08

Hi all! The nomination period for this years election of the Squeak Foundation board has ended. We have 12 candidates for the board! Superb! Now we are in the so called "Campaigning period" until the 29th february. During this period the candidates are of course free to do whatever they like :) but the following two activities have been used earlier years and I hope that the candidates will participate in them: 1. Post a "campaigning statement" (or whatever) as an article on http://people.squeakfoundation.org. People can then reply and ask questions etc without drowning in squeak-dev. It also makes a nice "persistent" record. Of course people can follow up on squeak-dev too. 2. Answer the 10 questions we have cooked up for the candidates by a post to squeak-dev: http://wiki.squeak.org/squeak/6029 That page is locked (only I can edit) so the idea is that the candidates answer by writing a post to squeak-dev starting from today. All should feel free to discuss on squeak-dev at length of course. The initial posts (with the answers) will be collected by me ASAP and filled in on the the Q&A page mentioned above so that all answers can be seen in one place. All details of the Election can be found at: http://wiki.squeak.org/squeak/6025 regards, Göran (Election leader) PS. In order to vote - be sure to confirm that you have an account on http://people.squeakfoundation.org and that your email address is up to date. If you are not already registered on the site do so as soon as possible. Include information about your participation in the Squeak community to aid everyone in determining your appropriate certification. If you have misplaced your people.squeakfoundation.org password there is a link on the login page to allow you to reset it. When the voting period starts all voters will receive an email with instructions and a link to the voting website.

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
22
Older →

Jump to page: