Squeak-dev October 2006

squeak-dev@lists.squeakfoundation.org

175 participants
305 discussions

re: 3.9 underscore still there?
by Bill Schwab 27 Oct '06

27 Oct '06

Tim, =================== I *thought* I had read that the use of the underscore for assign symbol had been expunged and all the code converted to use := but whilst looking at the compiled method source pointer stuff I noticed an awful lot of underscores still around. Is this a mistake or an unexpected reversion ? =================== I don't know that I ever caught a final statement on it, but there appeared to be problems with the removal. First, there were troubles identifying comments and literals[*], and either related to the first snag or independently troublesome, I thought I read of widespread badness after the "fix". My interest in underscores is mostly to enable them to appear within selectors. There is a fix for underscores at all but the first slot (which almost completely fixes the problem for me), and I would like to see it in the mainstream image if we can't fix the real problem. I had hoped that the fix would no longer be needed courtesy of m17n, but that appears not to have happened yet. [*] Could the RB help? Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bills(a)anest4.anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029

2 1

[OFF TOPIC] Thanks for ESUG 2006 DVD
by Edgar J. De Cleene 27 Oct '06

27 Oct '06

In this moment I viewing the ESUG 2006 DVD on my Mac. Almost I write a short story telling the journey of the DVD from Praga to Rosario with odd stops at Madison GA and Mar del Plata. So, very, very thanks to all what made this possible and special thanks to Francisco Lizarralde , one of thousand anonymous Squeaker what was nice enough to buy and send Edgar __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam �gratis! �Abr� tu cuenta ya! - http://correo.yahoo.com.ar

1 0

[ANN]Two 1-hour movie torrents from the BOF!
by goran＠krampe.se 27 Oct '06

27 Oct '06

Hi folks! http://goran.krampe.se/blog/Squeak/OOPSLA2006-1.rdoc regards, Göran

1 0

A process proposal for 3.10
by Giovanni Corriga 27 Oct '06

27 Oct '06

Hi all, since we've started discussing 3.10/4.0, I'd like to relay some thoughts that I've expressed some times ago on #squeak about a possible development process for Squeak 3.10. This proposal is based on two points: - decentralization of development - fixed duration of iterations ("timeboxing") "Decentralization of development" means moving most of the responsibility of development from the release team to the single package mantainers (stewards). The release team should just be an integrator of the code blessed by the stewards, and should facilitate coordination between the stewards of different packages. "Timeboxing" means having a fixed length release cycle, at the end of which a new stable version is released. This means that if there are some problems with a new feature, the deadline doesn't get postponed; instead it's the feature that gets dropped from the current development release and rescheduled for the next release. How would this work? Here's a more detailed description. ----------------------------------------------------------------------- PHASE 0: RELEASE TEAM FORMATION The SqF board will appoint a release team for 3.10. This team will have 3-7 members; 5 would be the sweet spot. The first task for the release team will be to find a mantainer for each one of the packages currently in the image. If they can't find a mantainer for a package, than said package _will get dropped from the image_ without any further discussion. PHASE 1: RELEASE PLAN After having found mantainers for every package, there's a package selection phase, during which the team and the maintainers: - decide which packages currently in the image should get removed from the image and turned into SqueakMap-loadable packages. - decide which new packages can be added to the image or replace other packages currently in the image. Input from the community and the stakeholders will be taken into account. After deciding which packages will be in the 3.10 image, the release team, the mantainers and the community will work on creating the release plan. Each package mantainer will announce what it plans to do for 3.10. The release team will integrate these proposals into a coherent release plan, solving possible conflicts and coordination problems. The community will be able to make comments and/or requests. After all these steps, which shouldn't take more than a month, the development of 3.10 can start. PHASE 2: DEVELOPMENT Development will have three stages: - a 3 months alpha stage - a 2 months beta stage - a 1 month gamma/RC stage. The deadline for each stage will be decided at the beginning of the iteration. Every week during each stage the release team will integrate the new releases of each package blessed by the package mantainers. Package mantainers will be the main responsible for development of their package and they'll be free to manage development as they like; ideally they should create a development team. If at the end of the alpha stage some of the work items of the plan aren't near completion, _these items and the corresponding code will get dropped_. If this is not possible, the code will be kept in the image, but it will have not to break the other code in the image. During the beta and gamma stages, no new features will get added to the image; only bug fixes can go in. During the gamma stage, only showstopper bugs will be fixed; other bug fixes (eg. cosmetical fixes) will be scheduled for 3.10.1. During the gamma stage of 3.10, the release team for 3.11 (or 4.1 or whatever) will get appointed and will work with the package mantainers to form the release plan for the next version. EXAMPLE Here's a an example of how things could possibly work. Release plan: During phase 1, the various package mantainers propose work items. So let's pretend that... - VMMaker team will want to: * integrate the async event patches useful for SqueakGtk. * integrate the Ffenestri code in all VMs, including the Unix one. * work with the Kernel team/maintainer on CompiledMethod cleanup. - Nebraska team will work on removing it from the image. - Pavel will want to work with various mantainers to integrate his patches for his KernelImage system. - Tools team will want to: * better integrate AST and the Refactoring services. * make Omnibrowser the default browser. Now let's pretend that at the end of the alpha stage, the Tools team still hasn't produced an Omnibrowser based debugger. Since it's the end of the alpha stage, the OBDebugger will be punted to the next release, and 3.10 will have a class browser based on OB but still the old debugger. ----------------------------------------------------------------------- I believe a process such as the one I'm proposing can work and help produce good quality releases. I'd like to hear comments on this, even if they just say that my proposal sucks. Ciao, Giovanni

43 124

[Fwd: [Webteam] squeak interview]
by Brad Fuller 27 Oct '06

27 Oct '06

-------- Original Message -------- Subject: [Webteam] squeak interview Date: Tue, 24 Oct 2006 13:01:40 -0700 From: alexhandy <alexhandy(a)gmail.com> To: webteam(a)lists.squeakfoundation.org I'd like to interview one of the developers of squeak for the software development times. _______________________________________________ Webteam mailing list Webteam(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/webteam

7 11

OSProcess path?
by Brian Brown 27 Oct '06

27 Oct '06

Hello all, Is there a way to set the path that OSProcess/CommandShell will use by default? For example, the path present in my login environment doesn't seem to be used. I'm using MacOSX and OSProcess 4.0.1 Thanks! Brian

2 1

Who is admin for source.squeakfoundation.org?
by tim Rowledge 27 Oct '06

27 Oct '06

I tried using the 'mail admin' link to no effect better than an email server telling me to forget it. We'd like a 'VM' project please so that the VMMaker package(s) can be more flexibly accessible. tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Every bug you find is the last one.

2 1

ChangeSet question
by Roel Wuyts 27 Oct '06

27 Oct '06

Hello, I am fixing a bug in the ClassBuilder/ChangeSet/ChangeNotifier triade, and stumbled across the following method: ChangeSet>>#changeClass:from: The last line of this method is: self noteClassStructure: oldClass Could anybody tell me what this last line is needed for ? In case you wonder why I'd like to know: the oldClass is currently an old class which is passed around, which is not healthy (as Andreas mentioned a couple of days before). I now rewrote most of the code to use a class definition instead, but the argument to #noteClassStructure really needs a behavior. When stumbling upon this I started to wonder what the #noteClassStructure is used for, after all. It would seem that it is simply superflouos, but I dare not just remove it.... Any help is appreciated... --Roel

1 0

Roadmap proposal for 3.10/4.0
by Stéphane Ducasse 26 Oct '06

26 Oct '06

Hi all I have been thinking about the next steps. Here are a list of propositions for 3.10/4.0 that I would like to work on and welcome company. Ideally I would like to build a group of people that have fun to work on these items. We could even try to have some regular chats one day a week and FUN. I think that Squeak 10/4 should not be compatible to free us but at the same time it should prepare the coming of new assets (sophie/tweak). Here are the main actions I would like to see happening: - be able to load Tweak - be able to load Sophie infrastructural elements (ressource location...) => even substitute current Squeak ones with sophie ones (Rome renderer) - curve/remove Etoy/projects (without having to reload them) - remove nebraska and others/ remove packages early in the process - new compile method format if available else klaus fix for source limits - may be newcompiler if ready - aggressive cleans in a lot of areas - look at Pavel overrides problems => ideally be able to use Pavel image as a basis for 10/4 - Use tool builder (looking at the tool plus) and change the current tools (the ones that deserve migration) - more tests - may be using MC2 if ready - better integration of AST and refactoring support So if you want to help there on a regular basis or on specific items please say it Stef

16 28

More on Bounties
by Ron Teitelbaum 26 Oct '06

26 Oct '06

http://www.eweek.com/article2/0,1895,2036174,00.asp?kc=EWLINEMNL102406EOAD Ron Teitelbaum

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
31
Older →

Jump to page: