Self-interest December 1995

self-interest@lists.selflanguage.org

9 participants
10 discussions

Re: Mango parser for Self?
by Jecel Mattos de Assumpcao Jr. 20 Dec '95

20 Dec '95

On Tue, 19 Dec 1995 16:05:46 -0500, Cameron Elliott <cam(a)indy.mvbms.com> wrote: > Has anyone written a Mango grammer description for Self ? I don't think so, but I started to do it a long time ago. I never finished or tested it, but here is what I wrote: ------------------------ start of s3.grm ---------------------- Name: 's3' Behavior: 's3.behavior.self' Syntax: SLR(1) <exprssion> ::= <keyMess>; <keyMess> ::| <binkey> <rkey>; <binkey> ::= <binMess> <keyopt>; <rkey> ::= <resend> <kMess>; <keyopt> ::? <kMess>; <kMess> ::= {smallKey} <argList>; <argList> ::+ <keyMess> {capKey}; <binMess> ::| <unbin> <rbin>; <unbin> ::= <unaryMess> <bList>; <rbin> ::= <resend> <bMess> <bList>; <bList> ::* <bMess>; <bMess> ::= {operator} <expression>; <unaryMess> ::| <primun> <run>; <primun> ::= <primary> <uopt>; <run> ::= <resend> <uMess>; <uMess> ::+ {identifier}; <resend> ::| <ropt> <directed>; <ropt> ::? 'resend.'; <directed> ::= {identifier} '.'; <primary> ::| 'self' {number} {string} <method> <block> <annotation>; <method> ::= '(' <slotList> <code> ')'; <block> ::= '[' <slotList> <code> ']'; <anootation> ::= '{' {string} <primary> '}'; <code> ::? <codes> <codes> ::| <codeList> <codeBoth> <return>; <codeBoth> ::= <codeList> '.' <return>; <codeList> ::+ <expression> '.'; <return> ::= '^' <expression> <dotopt>; <dotopt> ::? '.'; <slotList> ::? <sList>; <sList> ::= '|' <sList2> '|'; <sList2> ::* <slotDefs>; <slotDefs> ::| <annotSlots> <slotDef>; <slotDef> ::+ <slot> '.'; <annotSlots> ::= '{' {string} <sList2> '}'; <slot> ::| <privDecl> <simpleDecl>; <privDecl> ::= <privacy> <simpleDecl>; <privacy> ::| '^' '_' '^_' '_^'; <simpleDecl> ::| <argSlot> <dataSlot> <bSlot> <kSlot>; <argSlot> ::= ':' <slotName>; <dataSlot> ::= <slotName> <initopt>; <initopt> ::? <datainit>; <datainit> ::| <varinit> <constinit>; <varinit> ::= '<-' <expression>; <constinit> ::= '=' <expression>; <bSlot> ::= {operator} <bDef>; <bDef> ::| <bDef1> <bDef2>; <bDef1> ::= '=' <method>; <bDef2> ::= {identifier} '=' <method>; <kSlot> ::= {smallKeyword} <kDef>; <kDef> ::| <kDef1> <kDef2>; <kDef1> ::= <ceList> '=' <method>; <kDef2> ::= <cList> '=' <method>; <ceList> ::* {identifier} {capKeyword}; <cList> ::* {capKeyword}; <slotName> ::= {identifier} <paropt>; <paropt> ::? '*'; Lex: SLR(1) {digit} = [0-9]; {smallLetter}= [a-z]; {capLetter} = [A-Z]; {letter} = [a-zA-Z]; {opChar} = [!@#$%^&*-+=~/?<>,;|`\\]; {smallstart} = {smallLetter} | '_'; {indentChars}= {digit} | {letter} | '_'; {delimChar} = [()\[\]{}.:]; {blank} = [ \t\n] | {comment} {comment} = '"' {commentStuff}* '"'; {whitespace} -> {blank}+; {op} -> {opChar}+; {capKeyword} -> {capLetter}{identChars}+ ':'; {smallKeyword}-> {smallstart}{identChars}+ ':'; {identifier} -> {smallLetter}{identChars}+; ------------------------ end of s3.grm ------------------------ Notes: I doubt very much that the grammar is SRL(1) - I just put that done until I figure out what it should be. The lexical part is very incomplete (mostly missing comments, numbers and strings). The "-" is rather nasty and this mango file doesn't handle it correctly. The "." char isn't taken care of here either. One element that showed up in Self 4.0 is a new syntax for object annotation declaration - it isn't handled here. I hope this isn't worse than nothing ;-) -- Jecel

1 0

Mango parser for Self?
by Cameron Elliott 19 Dec '95

19 Dec '95

Has anyone written a Mango grammer description for Self ? Cameron. Cam(a)indy.mvbms.com

1 0

unsubscribe daniel@parcplace.com
by daniel＠parcplace.com 15 Dec '95

15 Dec '95

unsubscribe daniel(a)parcplace.com

1 0

test: go ahead and DELETE
by Randall.Smith＠Eng.Sun.COM 15 Dec '95

15 Dec '95

This is a test of the self-interest(a)self.sunlabs.com mailing list.

1 0

parent slots implemented as methods
by Ivan Moore 06 Dec '95

06 Dec '95

Hello, sorry this posting is so long ... A while ago I asked if it was inconsistent that parent slots cannot be methods. There were questions about what this would mean, and why it might be useful, and also Mario Wolczko pointed out that it can already be done in the VM - with the behavior that if an object with a parent slot 'parent' was sent the message 'parent' then it would evaluate the method, and the object would inherit from the _method_object_ (*not* the object resulting from the evaluation of the method). I 'stumbled' across a 'simply delightful' use of having parent slots as methods such that the inheritance is from the result of the method evaluation (OK - there are problems about what this might mean - but I'll try to explain what I mean) If you are familiar with the use of 'data parents' then skip this paragraph. A useful 'pattern' in Self programming is using sort of 'wrapper' objects to add state/behavior to an object - e.g. if you have a point and want to give it a color and associated behavior, you could have a 'color wrapper' which has an instance specific assignable slot for the color, some suitable methods, and an assignable parent slot which is set to the point to which you want to add color. A real problem with using 'data parents' is what to do with the slots that you would like to share between all 'wrappers'. If you put them in the 'wrapper' itself then there are problems of inconsistencies if you want to change them, and conceptually you have lots of copies of things that you really wanted to be shared, which is not a good thing (although maybe copyDown slots could be used to solve this problem). If you try to put them in a parent object of all wrappers (a different parent slot to the assignable one whose value is the wrapped object) then there are problems of ambiguous selectors and not being able to override slots of the wrapped object (unless you put lots of disambiguating methods in the wrapper object or modify 'ambiguousSelector:...') The proposed solution to the above problem is to have a non-parent assignable slot in the wrapper to refer to the wrapped object, and a parent object shared by all wrappers, which itself has a parent slot which is a method which evaluates as the wrapped object. Therefore, all wrappers would share the same parent object, which could have methods overriding ones in the wrapped object; and there would be no ambigity problems, as the parent of the parent of each wrapper would be the wrapped object specific to each wrapper. Madness? Maybe; but in case you don't understand/believe that such a thing is possible/useful, please try the example self code at the end of this mail. In this example there is a wrapper called 'wrapperExample' and an object to be wrapped called 'exampleWrappedObject'. Create a wrapped version of this object by evaluating 'wrapperExample copyFor: exampleWrappedObject'. Try sending this object messages 'aMethod' and 'aNonOverriddenMethod' and have a look at the code to see what's going on. Having a parent slot implemented as a method is faked by the parent of the parent of 'wrapperExample' by using delegation and 'undefinedSelector:...'. If parent slots could be implemented using methods then the method 'myParentWillBe' in the parent of 'wrapperExample' would be a parent slot. Ivan (obfuskating on thin ice towards madness). ------------ '$Revision:$' ' Copyright 1992, 1993, 1994, 1995 Sun Microsystems, Inc. and Stanford University. See the LICENSE file for license information. ' '-- Module body' bootstrap addSlotsTo: bootstrap stub -> 'globals' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' exampleWrappedObject = bootstrap setObjectAnnotationOf: bootstrap stub -> 'globals' -> 'exampleWrappedObject' -> () From: ( | {} = 'ModuleInfo: Creator: globals exampleWrappedObject. '. | ) . } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'exampleWrappedObject' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' aMethod = 'the result of some method'. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'exampleWrappedObject' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' aNonOverriddenMethod = 'aNonOverriddenMethod'. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'exampleWrappedObject' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: InitializeToExpression: (nil)' someAssignableSlot. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'modules' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' wrapperExample = bootstrap define: bootstrap stub -> 'globals' -> 'modules' -> 'wrapperExample' -> () ToBe: bootstrap addSlotsTo: ( bootstrap remove: 'comment' From: bootstrap remove: 'directory' From: bootstrap remove: 'fileInTimeString' From: bootstrap remove: 'postFileIn' From: bootstrap remove: 'revision' From: bootstrap remove: 'subpartNames' From: globals modules init copy ) From: bootstrap setObjectAnnotationOf: bootstrap stub -> 'globals' -> 'modules' -> 'wrapperExample' -> () From: ( | {} = 'ModuleInfo: Creator: globals modules wrapperExample. CopyDowns: globals modules init. copy SlotsToOmit: comment directory fileInTimeString postFileIn revision subpartNames. \x7fIsComplete: '. | ) . } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'modules' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot\x7fVisibility: public' comment <- ''. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'modules' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot\x7fVisibility: public' directory <- 'applications'. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'modules' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: InitializeToExpression: (_CurrentTimeString)\x7fVisibility: public' fileInTimeString <- _CurrentTimeString. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'modules' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' postFileIn = ( | | transporter moduleDictionary resetFillingSemaphore. snapshotAction addSchedulerInitialMessage: message copy receiver: transporter moduleDictionary Selector: 'resetFillingSemaphore'. resend.postFileIn). } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'modules' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot\x7fVisibility: public' revision <- '$Revision:$'. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'modules' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot\x7fVisibility: public' subpartNames <- ''. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' wrapperExample = bootstrap setObjectAnnotationOf: bootstrap stub -> 'globals' -> 'wrapperExample' -> () From: ( | {} = 'ModuleInfo: Creator: globals wrapperExample. '. | ) . } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' parent* = bootstrap setObjectAnnotationOf: bootstrap stub -> 'globals' -> 'wrapperExample' -> 'parent' -> () From: ( | {} = 'ModuleInfo: Creator: globals wrapperExample parent. '. | ) . } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'wrapperExample' -> 'parent' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' aMethod = ( | | resend.aMethod,' with something added'). } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'wrapperExample' -> 'parent' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' copyFor: x = ( | c. | c: _Clone. c wrappedObject: x. c). } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'wrapperExample' -> 'parent' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' myParentWillBe = ( | | wrappedObject). } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'wrapperExample' -> 'parent' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' parent* = bootstrap setObjectAnnotationOf: bootstrap stub -> 'globals' -> 'wrapperExample' -> 'parent' -> 'parent' -> () From: ( | {} = 'ModuleInfo: Creator: globals wrapperExample parent parent. '. | ) . } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'wrapperExample' -> 'parent' -> 'parent' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: FollowSlot' undefinedSelector: s Type: t Delegatee: d MethodHolder: m Arguments: a = ( | | s sendTo: self DelegatingTo: myParentWillBe WithArguments: a). } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: InitializeToExpression: (nil)' someWrapperAssignableSlot. } | ) bootstrap addSlotsTo: bootstrap stub -> 'globals' -> 'wrapperExample' -> () From: ( | { 'ModuleInfo: Module: wrapperExample InitialContents: InitializeToExpression: (nil)' wrappedObject. } | ) '-- Side effects' globals modules wrapperExample postFileIn

1 0

teaching material for Self
by Mario.Wolczko＠Eng.Sun.COM 05 Dec '95

05 Dec '95

I've added a Web page to the Self site about the various courses that I know of that teach Self (http://self.sunlabs.com/teaching.html). Robert Duvall at Brown University has recently made his course notes available, and I have also included the notes from a course taught at Manchester University. Mario Wolczko

1 0

Re: Drag&Drop for argument setting
by Ivan Moore 01 Dec '95

01 Dec '95

Michael, > A very nice thing would be the facility to set the value > of an argument by drag&drop (akin to pointer grabbing). > [further explanation deleted] Agreed. I don't have any code for doing that - however I've included some code (gzipped and uuencoded) which will tell you the object ID of the object that you want to refer to, so you can refer to it using 'NUMBER as' where NUMBER is the appropriate object ID. After '_RunScript'ing the file, have a look at the comment of 'oidSamplerMorph'. Please let me know if you have any problems loading this, I tried it on a fresh new image and it worked for me. (Please dont look at the actual code - it's not my best - but nevertheless does work) My apologies to those who think this is a horrible way of doing this, but it does work. Ivan. -------------- begin 644 sampling.self.gz M'XL(""\EOS W-A;7!L:6YG+G-E;&8 [5S_;]NV$O]=?\6A&*"X2 QL>\4P M87U XS;O&5B6H<[VRSP\4!)E<T\B#9**ZZW[WW<D)5N6Y2]U%-MQ:Q1I9)+' MN\\=C\?C*>!_]9X^,,4$#[[R/?"]GIC,)!N--7S]_???7)J?W]J?_[(_7\$@ MYW#+(BG43&F:J4OH\Z@+A,<PT(0G0L;P"V</5"JF9UUO0"GH,84?^[UW/PW> M0<)2"M@+4A91KB@P,R8C&GGH>K[G(1=75W KXAP[AB*>X7?XO]!*2S(!$L># M%!_N15#Y5ND\A*M_@S]*14A2Y9N'BP[<2)$%< $?X2\/RH_?(YJ.A)P%D#$I MD1=%LDF*' \_?)>XF?O(55!P$;AVQD<H*].,I#W!->5:!7 CTE1,#4?^?(+% M3!&B>9UK+?BMD)/QC9 !$/OK3R2C\-IPMNB-GX^P]'B1LV_<>$L*4A+2%.6I MT%"4QP8+1=.D YKIE'9 19)-= ^?4 V08E<1O2_1D=$:Q*-L>5R0>/2M]3] M3G<^^=_(20>>+_!4$D6M@ CR@MN8)HS3K?S[B^&E//?B>FE<%8V+)9U5.DF: MB0<<YD^(1*Y]A\KVWE)HH6<3VCB@8!02B:IS(AKMO;>CWZ2I_4I!J8**J%3? MA7_02+_A7&B[X.Z2?;"8ZW:9L;_^1JS]JA9[DA)M;+[D>4&KZUE7\U9,N0J\ M59FZC4)Y!>9W&4/K=JC"'"ZD:>RHKWK"6)4V6'9KRZL#;1GY)F"6C'Y?NS:R M_(J^.60I>E(45[('7#]-YCY&CYT:KWTM/IRX?,47[$]Z+]Y]F$BJ[.X#%YRE MG2;9G*=0=XDS7G67QB<NX@85YB%N>XU2&B;NT8B+C:'*6FOB"A8/G,,]"9G= M^GVYY*'W=%)-DLV][F.]5HUXP3<&*^?D7#Y-2WLJX>#P+ (.C#L-)"+7CXDU M/@&V<E?:'N4MA#D\0&T&73;XG/NN]MS6"6VT^23&%HSC!WEH7382RGYD2L,O M"F?!!S5J4'BYB=4=AM?0QX3RVD8_R[WE<BRTW(APWAOTE[]UG,4(QV\?(<AP MP(a)Q#8!,9]9.[7",N5,+ORV/L.:(UU656#5M.!6W:X'S</F%_E5N_I-3."2 2 M6?8)1X"82=P#T7'M.L <J_O\GF5TH*7E>L>SAE#ZQH[==80L$@:[]E=YB'N M-G&-VGB@*= 'AAIWQ]W6SC ;%;M_8%!R7%)L/M14Y7+'FMHYIK -F"L=ZMJ$ MA9J@Q!^JP![XZ+,;G@<.5$H8?[@"O[W-YR1%75B*$99,D'1D%X-Z1H*O/0G^ MKY=+$S0N[+^S.S0K2P<16B7X?%#:O-U5_,+6,!.EX&HBI,9-W[']ED7&: C: M$:)/#27#Q(!F9#(6LA9-*$XF:BST&SO(HA2-J:$C"ZYO485DA.(L3XR!B&MP MS@]-EYK\<+"1HQJ%I<\ 8YC(>F*_D6^_'CF9)&EW@=73Q#<GXQWF.X1Q#M4$ M_WF+7=T/V]T$]LMGKVMTN9[64]X\ST(J[Q(KU%*^8I]0>"VU+PGQK=#L'U"N M)7T&Z?+=83N+[/E!Q&TCF6Y<Y59A6-IV!N_8YG"(K/1F&5O+3Z_W_(?(5.\G MY+&O5]9S?0[ -$(P*\+S5?%=QNA)KYE.Q X.>.7TQ-=/7];V1IVVH+)S0''C M-8WC"T0"RG!V*,_WO"_KULIVY.JI Y\VZTYIGS/FFG*$S_=DN:T^HVGKZ+FL M=P#W8Z8 _Q&G<9B.630&35,48"9R6X0I+%/0?UN8,7BF$K/2DO.82HX;T!@8 M[BT78:Y!\'2&#!.I%4R%_+]=F3RBV /&1$%(*8=8BLF$QK:AX]TWS141CGTA M5]A-"]1!@E_B+X1[1=]P9LL9S01(V[!5)@Z'/E%#=% WR"[]8#&ZK/(]9<CQ MRHROX957S&IG<Q/GYJ86*;X"1_,.Z4CLD.(*P@YC;&443]G#%XN+Y^&+XN)4 M;4!K^&*M<\#QRYJ8^UZC4^M^\6NBUU(W2*,^K@4^81]% :U&0"SXT-=..W/E MY%RSU/2:X:@':A7D+2OH C4D3?$HS93!!!$B8$R3CTQ_',80:984<WU;>!%T M +B\G JO *5#?,R361:(F3,5;+!HDQ ?'-@>PMU0"SOT404(K"E7#9%D2-'C M=+PK\_'>X,I948S12E-1[;!2)##TAR^\*4M3X];C/#*BA:Z(UJV)Z1@-UAZ6 M:5D02\VZX73J50I'$1;4ED3:8\)CM!3P>FA,%O?2CLWR&=;7K1&+QW-G.5R_ M'QKS*Z1-K<: A.A:+,@740?Z#SCAK1#X:(JO+YT^N8 ID:@K/0//%O5B^TN$ MZV6Y-I39U$TRE$5Y2B3J821$;/+F":HJIMWZ=K MZ#R#_--QBM\.G'5Z0B&? M<:[IA ^D*XF).J_/%X2M20C<)<P]'J7]MS]+QO6A\Q G8@)'RDD<)C]QD#1% M&V(_F<F7I7F-1\M(I ;*"4'S!XXN(,9-T.X*_Y%D5L,,*5GY O<>T.) 4KX7 MY-[^^3Q@M7(W05K<]MOV$OLSQ*2E_!@^,5W(%F&<V1 ]? ;8K8_25%GG>TNT M>6_.E=3N6N%KC#%/]6/*?AMJ>-T SV&VLC22J35?T\G=AGH>G6OXR=HC,U> M-\O0T#5H[NF(GZ&]?%HE^-84XO8B\C)*.D,LCU5L#R0+V2A'ONBCRO K9/:J MU&]W/:^I^R\HSF=Q&>&/5>87TR&(Y4O$1<?52>;"&$.H4C'2WQ*36;I&9?Z& M<P1E\ZRNES6?-<',@LSOG65^VGU%X;1."<_OU9-#&'3= LL9&JROM/7'F%[3 MDCBJ#1[V7G">1S_2FZ?/XAZP)M&C;*$:A!>F[1Y(:'I&^M9^N2MJN+*TS".= MV_IWG"5)FFX("_:;.BA6:WJZ0E57I+\5;L7^I,8[EEFB+WCOC'=SFFT[Y)5Q M3X/\8=].77GQ<;O-/=;'/ZFT:_/QY1Z^4U*^LA._;MC]'R>SVTA*P$],U:Y3 M:_H]EJP;%;HJ=:EB(UKIF!HP*/X*TX#%%&B2&,+FSS"M>_&Q\AZ2]P^O67*( $5$H *P; end

1 0

trace of Self changes
by Michael.Huebner＠PrakInf.TU-Ilmenau.DE 01 Dec '95

01 Dec '95

While thinking about the consequences of my proposal to use shift-click to get references to objects I got the idea that it would be useful to write all changes to the Self world to a log file so you can later use this information to create module information, return to earlier stages by using only the part before some error occured, ... To do this you have to store all top messages send by the user to objects, i.e. only that from an evaluator or triggered by a menu or a button, not the resulting messages. For this you need the references to the receiver objects of all the top messages. Here you can use the global names of the well-known objects. The problem is how to refer to not-well-known objects. As you can only send messages to those not-well-known objects which are visible in your GUI you can maintain symbolic references to all those objects e.g in an appropriate dictionary or in that one already used by the GUI system. In order to be independent from the absolut value of the object reference you have to use symbolic references in the log file. Every time you show an object (morph or arbitrary outliner) you register under an unique symbolic reference 1) the message that led to this grafical appearance 2) the concrete object-reference(s) of the created morph object (and of the object that receives messages through this morph object in the case of an outliner). You have to distinguish between messages sent to the outliner and messages sent to the object that the outliner stands for. I think if you enlarge the functionality of the evaluator or other GUI specific stuff that starts sending of messages to the object behind it you get it very easy. When you dismiss the grafical object than you remove the object-references of both outliner and reflectee and they may rest in peace if not longer needed. Pointer grabbing and argument picking (great word!) make no problems because the referenced object are handled in absolute the same way as the receiver objects. Michael

1 0

Latin-1 Caracters
by Thierry.Goubier＠enst-bretagne.fr 01 Dec '95

01 Dec '95

That probably sound stupid, but why is there a limit on printables characters that forbid the user to enter a caracter with an accent (or any composed character) ? If you change this limit to 255, all accentuated characters work correctly. Or am I missing something ? The slot is lastPrintableCharacter in traits string, and it's standard value is 127. I'll try to check if I break something by changing the value. Thierry. ___________________Thierry.Goubier(a)enst-bretagne.fr__________________ <Am I dreaming the dream, or is the dream dreaming me ?> [Corwainer Smith] http://www-info.enst-bretagne.fr/~goubier/

1 0

Re: Drag&Drop for argument setting
by randy＠gemma.Eng.Sun.COM 01 Dec '95

01 Dec '95

This is a nice idea. It is like an idea we never got around to doing, which was to put a reference object inline with the text: control-shift-R (or whatever) creates the refernce object where you are typing. You grab the reference object, and drag out a pointer over to the object you want to refer to. Your method solves the problem of having to grab the reference object to drag out the pointer. So it saves the acquisition of a small target. Either of the above may require extensions to the parser if it is to be used for methods (we would want to save the method, and read it in again to recreate the method with the reference in place.) Still, even if it were not used in methods, it would be useful just during expression evaluation. Adding sprouted pointers to buttons (a la the Alternate Reality Kit) to specify arguments is also useful. Thanks, --Randy > From Michael.Huebner(a)PrakInf.TU-Ilmenau.DE Thu Nov 30 18:57 PST 1995 > To: self-interest(a)self.smli.com > Subject: Drag&Drop for argument setting > X-Sun-Charset: US-ASCII > Content-Type: text > Content-Length: 900 > X-Lines: 28 > > A very nice thing would be the facility to set the value > of an argument by drag&drop (akin to pointer grabbing). > > Assume you are writing an expression in an evaluator and > you want to use an (e.g. not-well-known) object as the value > for an actual argument or as the righthand side of an assignment > than you only have to shift-click on the desired object. > The reference to this object is inserted on the point where > your input focus was, indicated by a sprouted pointer > and the focus is behind the reference sign (=) so you can > go on writing your expression. > > > +---------------+ +---------------+ > | an object | ------> | an object | > +---------------+ / +---------------+ > | do: a | / | ... | > +===============+ / +---------------+ > |do: (=)------------/ | ... | > | | | | > +---------------+ +---------------+ > |evaluate|dismis| | | > +---------------+ +---------------+ > > > > > Michael >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

Self-interest December 1995