Squeak-dev April 2004

squeak-dev@lists.squeakfoundation.org

172 participants
488 discussions

resend of lost mail > Re: morphs and submorphs as class files
by Gary McGovern 01 Apr '04

01 Apr '04

This mail seems to have been lost from a couple of days ago with a couple of others.I hope they were lost and not moderated. >I made a bookmorph, i could save it file .morph no problem. But... >I wanted to save it as a class, with all its submorphs. I think I mentioned >this a while ago. > >So instead of filing in the morph file I could just type in the workspace >TestBook new openInWorld. > >It is a big problem the dirs. They move from object pattern. But still >there needs to be storage of objects, so the image doesn't bloat. > >What about it ? > >Just remembered, I'm surprised there hasn't been speech put into the tile >scripting. Any plans ? > >Thanks, >Gary > > > >

2 1

[ANN] Refactoring services 0.5 on SM
by Romain Robbes 01 Apr '04

01 Apr '04

Hi again, This package depends on the squeak services and on the RB, and provides definition of services for the refactorings, effectively decoupling the Refactorings from the RB UI. Moreover, the refactorings are now available in most browsers, including the hierarchy browsers, protocol browsers, message list browsers. This services could also be easily used by other browsers such as Whisker and OmniBrowser. Thanks for feedback, Romain

1 0

[ANN] Squeak Services 0.5 on squeakmap
by Romain Robbes 01 Apr '04

01 Apr '04

Hi all, I made a release of the proposal about services I talked about a while ago. This release adds the support classes, and defines a few services already, most of them being in the alternative world menu (right or middle-click). If you have the keymapper installed, the defined services will be bound to keyboard shortcuts when a TextMorph is focused. More info is available in the help window which will we displayed after installation. Feedback is as always greatly appreciated. Cheers, Romain

1 0

VM for FreeBSD?
by Colin Putney 01 Apr '04

01 Apr '04

Hi folks, I'm trying to install Squeak on a headless FreeBSD box and I'm not sure what voodoo is currently required, if any. The key thing is that I want to be able to run a 3.7 image, which is problematic with the current Unix VM. So as far as I can see, my options are: 1) Install the stock 3.4 VM Ian's site and do without the improvements he's made since then - in theory I shouldn't need ephemerons etc. 2) Use the current VMMaker to generate a source tree, patch it as necessary to run the 3.7 image, copy it over to the FreeBSD box and build a VM from scratch. I've been unsuccessful when trying to do this on my Mac OS X box, but FreeBSD might be easier. My gut says #2 is the better option, but is likely to be tricky. Any hints from the VM gurus out there? Colin

4 3

[ENH] DefaultProgressBar
by Alexander＠Lazarevic.de 01 Apr '04

01 Apr '04

How about this as a starter? Alex from preamble: "Change Set: DefaultProgressBar Date: 1 April 2004 Author: Alexander(a)Lazarevic.de A different progress bar will be displayed for MVC and Morphic. This also ensures that a progress bar gets removed."!

1 0

[GTK] Status report
by goran.krampe＠bluefish.se 01 Apr '04

01 Apr '04

Hi all! There are a few people interested in native UIs from Squeak so I thought I could write a short report from what I know. Ragnar is plumbing away with a Socket based protocol to drive Gtk, exactly what he can do right now with it I am not sure. We are chatting and exchanging experiences on IRC. I have worked on getting some form of callback working and I am pleased to say that I have gotten something together! There are a bunch of constraints with it (like for example only working currently with signals that have two specific arguments - I hardcoded that to get moving) but it actually works! Some sample code: | gtk xml win1 win2 button1 button2 button3 button4 | gtk _ Gtk default. "Start a background process calling the plugin every 5 ms to drive the Gtk event loop and get callbacks back" gtk startEventProcessIfNotRunning. xml _ Gtk simple2ButtonsXML. win1 _ GladeXML fromXMLString: xml. xml _ xml copyReplaceAll: 'button1' with: 'button3'. xml _ xml copyReplaceAll: 'button2' with: 'button4'. win2 _ GladeXML fromXMLString: xml. "Creates and opens the windows" win1 load. win2 load. "Hooks up the named handlers in Gtk" win1 signalConnectData: 'on_button1_clicked'; signalConnectData: 'on_button2_clicked'. win2 signalConnectData: 'on_button3_clicked'; signalConnectData: 'on_button4_clicked'. button1 _ win1 widgetNamed: 'button1'. button2 _ win1 widgetNamed: 'button2'. button3 _ win2 widgetNamed: 'button3'. button4 _ win2 widgetNamed: 'button4'. "Register event handlers on the Squeak side" button1 when: 'on_button1_clicked' asSymbol send: #show: to: Transcript with: 'Button1 clicked!'. button2 when: 'on_button2_clicked' asSymbol send: #show: to: Transcript with: 'Button2 clicked!'. button3 when: 'on_button3_clicked' asSymbol send: #show: to: Transcript with: 'Button3 clicked!'. button4 when: 'on_button4_clicked' asSymbol send: #show: to: Transcript with: 'Button4 clicked!' ----- The above will open two native win32 windows with Gtk painting the UI inside. The UI is 2 buttons in each window. Pressing any of the four buttons will cause a printout in Transcript. As you can see above you first need to "activate" the handlers named in the Glade source using #signalConnectData:. Then you simply get an instance of GtkWidget (using #widgetNamed:) and use the new event protocol to register a message send on that same handler name. Avi mentioned that this the event registering (last 4 lines) is not necessarily how you would use Glade - but that is all on the Squeak side so we can easily change it or have multiple approaches. Anyway, just wanted to show some progress. Demo zip and plugin source is available at: http://anakin.bluefish.se/gohu/25 regards, Göran PS. Getting this to build properly on win32 is an exercise in itself. Don't try it if you don't really want to do it. Among other things I had to rename library files to other extensions etc. Phew.

1 0

Re:[UPDATES] 52 for Squeak3.7alpha, advance to 3.7beta
by Martin Wirblat 01 Apr '04

01 Apr '04

dway(a)mailcan.com wrote on 01.04.2004 08:30:14: > >Here is the last batch of updates for 3.7alpha, plus an update to >advance to 3.7beta. Quite a bit of stuff here! Now that we're in >beta, further updates for 3.7 will just be fixes (and possibly things >like preferences tweaks, etc). Like e.g. this one: [ENH] Additional preference for menus of Diego's New look http://lists.squeakfoundation.org/pipermail/squeak-dev/2004- March/075242.html BFAV 20713 Adds a Preference to Diego's new menu look. You can switch back to the classic version of the selection coloring: background darker vs. background and foreground negated. It just needs to get a review. Regards, Martin

1 0

Re: Report from a novice VM h4x0r.
by Richard A. O'Keefe 01 Apr '04

01 Apr '04

Alan Grimes <alangrimes(a)starpower.net> wrote: Also, the C compiler does not follow the C idiom of making all constants ALLCAPS. Since the C code is the moral equivalent of assembly code, and since said idiom is more honoured in the breach than the observance (and was a bad idea in the first place), why care? 4. A great many computations involve extracting bit-fields. In many cases these bit fields include important scalar information such as "sizeBits". A useful improvment would be to make these either bytes or short-ints and then let the C compiler figure out how best to extract them from the words... Years ago I had my fingers burned with C bitfields to the point where I *never* use them. If the compiler optimises, code that does explicit shifts and masks will be quite as efficient as bitfields. if it doesn't, you have worse things to worry about. Bitfields are a portability minefield, even between compilers on the same machine, even sometimes between different options for the *same* compiler on the same machine. 16. C99 adds block contexts. Eh? C99 has exactly the same "blocks" as C89; the only change is that array sizes can be dynamic expressions, not just constant expressions. The current cCompiler will take all inlined methods as well as loop variables and put them at the beginning of the generated function. Since any current C and even older C++ compilers will support for (int i; i < x ; i ++ ), it would be much better form to use this instead of heaping all variables at the beginning of the block. Oh, you mean NON-block declarations. There is absolutely no point in worrying about this one. I've seen a Scheme compiler which generated a separate variable for each subexpression in a function, so that some of the generated C had hundreds of variables. Any C compiler worth having these days will do lifetime analysis. Declarations in loop headers are nice for programmers, but for (int i; i < x; i++) ---stmt--- doesn't do anything that {int i; for (i = 0; i < x; i++) ---stmt---} doesn't do (except, of course, for using an uninitialised variable. (:-)) With an optimising compiler, putting the variable at the function-level block doesn't make any difference; what matters is where it is mentioned.

1 0

Jump to page: