Squeak-dev February 2000

squeak-dev@lists.squeakfoundation.org

163 participants
655 discussions

RE: MVC is Dead?
by John Buffington 02 Feb '00

02 Feb '00

At 02:03 PM 2/2/00 -0500, you wrote: > > From: Jarvis, Robert P. (Contingent) [mailto:Jarvisb@timken.com] > > Sent: Wednesday, February 02, 2000 1:19 PM > > To: 'squeak(a)cs.uiuc.edu' > > Subject: RE: MVC is Dead? > > > > It's not pining! It has passed on! It is no more! It has ceased to be! > > It's expired and gone to meet its maker! It's a stiff! Bereft > > of life, it > > rests in peace! If it hadn't been nailed down it'd be pushing up the > > daisies! Its metabolic processes are now history! It's off the > > twig! It's > > kicked the bucket, shuffled off its mortal coil, run down the curtain and > > joined the bleeding choir invisible!! > > > > Well, someone had to say it... :-) > >Wow! Was that all from memory? Nothing particularly amazing here, many of us with misspent youths can quote long passages from Monty Python and Firesign Theater. Often at quite inappropriate times. ;^) Buff

1 0

Re: Type Safety (was Re: fun and empowerment)
by Doug Way 02 Feb '00

02 Feb '00

On Tue, 1 Feb 2000, Duane Maxwell wrote: > Perhaps SqC will someday see fit to set the file types of these files to > something a little less likely to provoke's UnStuffIt's friskiness. Assuming this works, maybe our good friend (and download curator) Bruce O'Neel might be able to do this? (Does setting the file type to something other than 'TEXT' actually prevent this problem?) Bruce? :-} Of course, some sort of automatic Squeak-based check would be even better (as Les suggested), but at least short-term, fixing the file type in the Mac download would be easy. Ultimately, I think this is mostly Squeak's problem, and we should do something about it one way or the other... downloading & starting Squeak should be a worry-free operation. (People will download Squeak before they ever sign up for this list, or check the Swiki, so the fix needs to be at the source...) - Doug Way dway(a)mat.net

2 1

Re: "explain" in code panes now broken in 2.8a
by merlyn＠stonehenge.com 02 Feb '00

02 Feb '00

Nope. Here's a walkback. Got this by selecting some token in a change sorter, then selecting "explain" from a popup. Nothing explains, even after your patch. 2 February 2000 12:10:45 pm MessageNotUnderstood: selectedMessage ChangeSorter(Object)>>doesNotUnderstand: PluggableTextController(ParagraphEditor)>>explainTemp: [] in PluggableTextController(ParagraphEditor)>>explain UndefinedObject>>ifNil: [] in PluggableTextController(ParagraphEditor)>>explain BlockContext>>on:do: [] in BlockContext>>valueUninterruptably BlockContext>>on:do: [] in BlockContext>>valueUninterruptably BlockContext>>on:do: BlockContext>>valueUninterruptably BlockContext>>ensure: CursorWithMask(Cursor)>>showWhile: PluggableTextController(ParagraphEditor)>>explain ChangeSorter(StringHolder)>>perform:orSendTo: [] in PluggableTextController(ScrollController)>>pluggableYellowButtonActivity: PluggableTextController(Controller)>>terminateAndInitializeAround: PluggableTextController(ScrollController)>>pluggableYellowButtonActivity: PluggableTextController>>yellowButtonActivity PluggableTextController(ParagraphEditor)>>processYellowButton PluggableTextController(ParagraphEditor)>>processMouseButtons PluggableTextController(ParagraphEditor)>>controlActivity PluggableTextController(Controller)>>controlLoop PluggableTextController(Controller)>>startUp StandardSystemController(Controller)>>controlToNextLevel StandardSystemController(Controller)>>controlActivity StandardSystemController(MouseMenuController)>>controlActivity StandardSystemController>>controlActivity StandardSystemController(Controller)>>controlLoop StandardSystemController(Controller)>>startUp [] in ControlManager>>activeController: [] in BlockContext>>newProcess -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

1 0

Re: MVC is Dead?
by Stephen Travis Pope 02 Feb '00

02 Feb '00

"R. A. Harmon" wrote: > > At 09:34 PM 2/1/00 -0600, Les Tyrrell wrote: > >John-Reed Maffeo wrote: > >> > >> Is MVC really dead? > > > >Is anything in an open-source environment ever truly dead? > > No in Monty Python terms "Its sleeping." Oh, gee, I thought it was "pining for the fjords." -- stp Stephen Travis Pope http://www.create.ucsb.edu/~stp

1 0

RE: Generating source code from Morphs [was: RE: More Widgets for Squeak....]
by Norton, Chris 02 Feb '00

02 Feb '00

Hi Chris & friends. On Tuesday, February 01, 2000, Chris Reuter [cgreuter(a)calum.csclub.uwaterloo.ca] wrote: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I've written something along those lines already. I've got a collection of about 10 morphs that support a common protocol to create source code that recreates the layout. They're also fully pluggable and provide a simple API so that you can use them without having to understand their internals. I'm in the process of cleaning up the code right now. I was planning on releasing it in a couple of weeks, but if anyone's interested in playing with what I have now, send me email. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sounds great! I don't have the bandwidth to work on this right now, but I am very interested in what you've come up with. I am a firm believer in having a GUI builder to help with the mundane chores of constructing UIs and this is the first step towards that goal. Take this code, tie in the recent work that folks have been doing with "skins", leverage the traditional power of ST and we've got a pretty powerful development environment! [OK -- I admit it's fun too!] Each baby step in this direction takes us further and further away from every having to program in any other language! ---==> Chris

1 0

Re: Standard Squeak Font Encodings
by Andrew C. Greenberg 02 Feb '00

02 Feb '00

>I'd vote for switching to ISO Latin-1 because it is one of the >best-documented encodings (it's almost impossible to find a Mac encoding >chart on the web). Besides, codes from 128 to 159 are "free" so we can put >special characters there. I'm not married to the status quo, but this reasoning seems to me problematic. It was trivial for me to find the MacRoman chart on web, which is available from many sources, not the least of which is, ahem, the Apple web site (look under Technical publications: Text): http://developer.apple.com/techpubs/mac/Text/graphics/EX_L-04.jpg Nor do I find the use of a "standard" particularly compelling, since we will likely be moving a few glyphs around for programming purposes (caret to return glyph, underbar to assignment glyph). To the contrary, I found it disconcerting to discover both the Tex and ISO Latin-1 fonts "break" existing displays that depended upon the Mac encoding. If we do change encodings, some machine-independent facility will need to be implemented across platforms to assure that keycodes/screen glyphs conform to expectations uniformly, or we need to be willing to adopt a different approach. In short, perhaps we should worry about this another day, and simply modify these fonts to conform to the present "modified" MacRoman format. They can later be changed once a "purer" encoding is found. The repertoires are not identical (MacOS supports several diacriticals not in ISO Latin-1). On the other hand, do we really want to continue supporting what may become a dionsaur? (Does anyone know what encodings are primarily used in OS X?) At any rate, some decisions should be made as to a Squeak standard repertoire and encoding, so that new fonts can be used seamlessly and without compromising existing code (or identifying where changes might need to be made). Where shall we put the "replaced" glyphs? Shouldn't we place a Euro symbol in all of our fonts?

2 3

Re: Standard Squeak Font Encodings
by Richard A. O'Keefe 02 Feb '00

02 Feb '00

-Bert- wrote I'd vote for switching to ISO Latin-1 because it is one of the best-documented encodings (it's almost impossible to find a Mac encoding chart on the web). Besides, codes from 128 to 159 are "free" so we can put special characters there. Codes 128..159 are only "sort of" free. The ISO 6429 standard defines a whole lot of so-called "C1 controls", and guess where they go? In particular, the whole CR, LF, CRLF mess is (belatedly) solved by the NEw-Line (NEL) code, 16r85 (actually, if you read the original papers about ASCII in the CACM, you discover that LF *was* intended to serve as NL if you wanted an NL character). You can also find out about these control characters in ECMA 48, which has the advantage of being free. Here's a list I typed up some years ago. /* The C0 controls */ #define NUL '\000' /* ^@ null character */ #define SOH '\001' /* ^A Start Of Heading, start of message */ #define STX '\002' /* ^B Start Of Text, end of address */ #define ETX '\003' /* ^C End of TeXt, end of message */ #define EOT '\004' /* ^D End Of Transmission */ #define ENQ '\005' /* ^E ENQuiry "who are you" */ #define ACK '\006' /* ^F (positive) ACKnowledge */ #define BEL '\007' /* ^G ring the BELl */ #define BS '\010' /* ^H BackSpace */ #define HT '\011' /* ^I character (Horizontal) Tab */ #define TAB '\011' /* ^I an unofficial name for HT */ #define LF '\012' /* ^J Line Feed (does not imply cr) */ #define VT '\013' /* ^K line (Vertical) Tab */ #define FF '\014' /* ^L Form Feed (new page starts AFTER this) */ #define CR '\015' /* ^M Carriage Return */ #define SO '\016' /* ^N Shift Out; select alternate character set */ #define SI '\017' /* ^O Shift In; select ASCII again */ #define DLE '\020' /* ^P Data Link Escape */ #define DC1 '\021' /* ^Q Device Control 1 */ #define XON '\021' /* ^Q transmitter on, resume output */ #define DC2 '\022' /* ^R Device Control 2 (auxiliary on) */ #define DC3 '\023' /* ^S Device Control 3 */ #define XOFF '\023' /* ^S transmitter off, suspend output */ #define DC4 '\024' /* ^T Device Control 4 (auxiliary off) */ #define NAK '\025' /* ^U Negative AcKnowledge (signal error) */ #define SYN '\026' /* ^V SYNchronous idle */ #define ETB '\027' /* ^W End of Transmission Block, logical end of medium */ #define CAN '\030' /* ^X CANcel */ #define EM '\031' /* ^Y End of Medium */ #define SUB '\032' /* ^Z SUBstitute */ #define ESC '\033' /* ^[ ESCape */ #define FS '\034' /* ^\ File Separator */ #define IS4 '\034' /* ^\ Information Separator 4 */ #define GS '\035' /* ^] Group Separator */ #define IS3 '\035' /& ^] Information Separator 3 */ #define RS '\036' /* ^^ Record Separator */ #define IS2 '\036' /* ^^ Information Separator 2 */ #define US '\037' /* ^_ Unit Separator */ #define IS1 '\037' /* ^_ Information Separator 1 */ #define SP '\040' /* SPace */ #define DEL '\177' /* ^? DELete, rubout */ /* Here are the C1 controls from ECMA 48 */ #define PAD '\200' /* PADding character */ #define HOP '\201' /* High Order Preset */ #define BPH '\202' /* Break Permitted Here */ #define NBH '\203' /* No Break Here */ #define IND '\204' /* INDex */ #define NEL '\205' /* NExt Line */ #define SSA '\206' /* Start of Selected Area */ #define ESA '\207' /* End of Selected Area */ #define HTS '\210' /* character (Horizontal) Tabulation Set */ #define HTJ '\211' /* character Tabulation with Justification */ #define VTS '\212' /* line (Vertical) Tabulation Set */ #define PLD '\213' /* Partial Line forward (Down) */ #define PLU '\214' /* Partial Line backward (Up) */ #define RI '\215' /* Reverse line feed (Index) */ #define SS2 '\216' /* Single Shift 2 */ #define SS3 '\217' /* Single Shift 3 */ #define DCS '\220' /* Device Control String */ #define PU1 '\221' /* Private Use 1 */ #define PU2 '\222' /* Private Use 2 */ #define STS '\223' /* Set Transmit State */ #define CCH '\224' /* Cancel CHaracter */ #define MW '\225' /* Message Waiting */ #define SPA '\226' /* Start of guarded (Protected) Area */ #define EPA '\227' /* End of guarded (Protected) Area */ #define SOS '\230' /* Start Of String */ #define SGCI '\231' /* Single Graphic Character Introducer */ #define SCI '\232' /* Single Character Introducer */ #define CSI '\233' /* Control Sequence Introducer */ #define ST '\234' /* String Terminator */ #define OSC '\235' /* Operating System Command */ #define PM '\236' /* Privacy Message */ #define APC '\237' /* Application Program Command */ #define NBS '\240' /* No-Break Space */

3 2

New TeXFileOut 20000201
by Andres Valloud 02 Feb '00

02 Feb '00

Hi. This new release of TeXFileOut has class comments (ouch!... and I saw the preamble of the previous one said there were class comments...), fixes typesetting of class comments, and has a few minor modifications including the addition of a new Class comments banner, one deleted method (hehe <G>), some others that were factored, and the replacement of \ss with \sf. Thanks go to Mark Guzdial for reporting problems with TeXFileOut. Andres.

2 1

Re: Generating source code from Morphs [was: RE: More Widgets for Squeak....]
by Marcel Weiher 02 Feb '00

02 Feb '00

> From: "Norton, Chris" <chrisn(a)Kronos.com> > You know, I have often wished that this mechanism were more robust, as it is > much easier to drag-n-drop widgets together than it is to wire them up the > old fashioned way. Perhaps the top level morph should have a standard > selector that can generate a method definition that can later be used to > rebuild the whole thing programmatically. Thus you could hook morphs > together, embed them into a SystemWindow or playfield and then ask the > SystemWindow to generate code that can reproduce the whole mess... I > suppose the first thing to do is to implement Morph>>asSourceCode. Or > something like it. What there should be is a textual representation of the relationships that have been created, something that is only implicitly supported in Smalltalk. One way of doing this is to create Smalltalk source code, but that doesn't really capture the (static) relationships, but rather the (somewhat ad-hoc) instructions used for building it. Such a representation cannot be easily manipulated in a semantically consistent fashion, because the only way to find out its "meaning" is to execute it. Another method is to simply dump the object-graph, which is for example what the NeXT/Apple interface-builder does. This has many advantages, but loses in that dumped object-graphs are typically not very human-readable/understandable/editable. One method that seems promising is architectural description languages (ADLs) such as ACME from CMU. They have direct support for things like "component A is connected to component B via connector C on (respective) ports D and E". One of my (far too plentyful) goals is to embed message-sending within the conceptual framework of architectural connection and the language for specifying architectural connection within something close to present Smalltalk syntax. Marcel

1 0

Re: Irregularly shaped main window
by Marcel Weiher 02 Feb '00

02 Feb '00

On MacOS-X(-Server), this functionality can be had using a path instead of a bitmap. > From: "Lex Spoon" <lex(a)cc.gatech.edu> > It's doable on Unix as well. So the big three are covered. We just > need a primitive to specify where the shape bitmap is.

1 0

← Newer
1
...
59
60
61
62
63
64
65
66
Older →

Jump to page: