From cynthia.haynes@gmail.com Tue Jul 5 10:25:54 2005 Received: with ECARTIS (v1.0.0; list encore); Tue, 05 Jul 2005 10:25:54 -0500 (CDT) Return-Path: X-Original-To: encore@nobel.utdallas.edu Delivered-To: encore@nobel.utdallas.edu Received: from iq1.utdallas.edu (iq1-pmn.utdallas.edu [192.168.1.7]) by nobel.utdallas.edu (Postfix) with ESMTP id 538BD5BAD for ; Tue, 5 Jul 2005 10:25:54 -0500 (CDT) Received: from localhost (mf1-pmn.utdallas.edu [192.168.1.8]) by iq1.utdallas.edu (Postfix) with ESMTP id 3DD811166 for ; Tue, 5 Jul 2005 10:25:54 -0500 (CDT) Received: from mx2.utdallas.edu ([129.110.10.17]) by localhost (mf1 [10.110.10.13]) (amavisd-new, port 10024) with LMTP id 11010-01-65 for ; Tue, 5 Jul 2005 10:25:45 -0500 (CDT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx2.utdallas.edu (Postfix) with ESMTP id 679993577 for ; Tue, 5 Jul 2005 10:15:17 -0500 (CDT) Received: by rproxy.gmail.com with SMTP id r35so889989rna for ; Tue, 05 Jul 2005 08:15:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:user-agent:date:subject:from:to:message-id:in-reply-to:mime-version:content-type:content-transfer-encoding; b=hGDA1t329UrjNyy8W5rqUZFMNWB8kOprb0jSujhzhuJPSZMH7kRerj8yL+motCvr3+a5EXNIAc3QWqYSyE5HZX5rFhO5kBzzMKdhKMiub1ewjs1HdylcIDslZFODZmIgwK5/MlY3TOHgw1AXOU7GYQ8xCq0zHgOoQmxEjrXRmVk= Received: by 10.38.98.62 with SMTP id v62mr4061089rnb; Tue, 05 Jul 2005 08:15:16 -0700 (PDT) Received: from ?10.0.1.3? ([80.162.1.238]) by mx.gmail.com with ESMTP id 59sm2537620rnb.2005.07.05.08.15.14; Tue, 05 Jul 2005 08:15:16 -0700 (PDT) User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Tue, 05 Jul 2005 17:15:01 +0200 Subject: [encore] **ANNOUNCING enCore Symposium August 12-13 From: Cynthia Haynes To: , Message-ID: In-Reply-To: <6.2.0.14.0.20050629083410.01d50008@accdvm.accd.edu> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Scanned: amavisd-new at utdallas.edu X-archive-position: 1440 X-ecartis-version: Ecartis v1.0.0 Sender: encore-bounce@utdallas.edu Errors-to: encore-bounce@utdallas.edu X-original-sender: cynthia.haynes@gmail.com Precedence: bulk Reply-to: cynthia.haynes@gmail.com List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: X-list: encore Folks, We are now ready to announce the opening of registration for the enCore Symposium, a face-to-face gathering of enCore users and Consortium members taking place on Friday and Saturday, August 12-13, 2005, at the University of Texas at Dallas in Richardson, Texas. As Lennie explained earlier, this gathering is meant to strengthen the mutually supportive relationship that we hope the enCore Consortium will develop between itself and its members. What that means is to find and build ways in which the Consortium can support what you do with enCore at your school/location and to find and build ways in which you can support the larger work of the Consortium. We would like to highlight an online event on Saturday morning, August 13, that will the first yearly meeting of the entire enCore Consortium online. Details about logging in to this event will be forthcoming, and we hope as many of you who cannot attend the F2F symposium will be able to attend this online event. We will have reports from the Steering Committee as well as Daniel Jung's presentation about the new enCore v5. We also hope at this meeting to elect a Board of Directors for our official "incorporated" status. For registration instructions, hotel info, maps, and the program, see: http://www.encore-consortium.org/symposium2005.htm We hope as many of you as possible can attend, and we look forward to seeing you in Dallas! Best wishes, Cynthia Haynes (on behalf of the entire enCore Consortium Steering Committee: Lennie Irvin, Cynthia Haynes, Jeff Schneider, Daniel Jung, Rhonna Robbins-Sponaas, and Barbara McManus) __Cynthia Haynes, Director of Rhetoric and Writing___________________ University of Texas at Dallas cynthiah@utdallas.edu School of Arts & Humanities http://www.utdallas.edu/~cynthiah PO Box 830688-JO 31 http://lingua.utdallas.edu:7000 Richardson, TX 75083-0688 (O)972-883-6340 (F)972-883-2989 From kevijeps@telusplanet.net Mon Jul 18 23:57:10 2005 Received: with ECARTIS (v1.0.0; list encore); Mon, 18 Jul 2005 23:57:11 -0500 (CDT) Return-Path: X-Original-To: encore@nobel.utdallas.edu Delivered-To: encore@nobel.utdallas.edu Received: from iq1.utdallas.edu (iq1-pmn.utdallas.edu [192.168.1.7]) by nobel.utdallas.edu (Postfix) with ESMTP id CC9975BC4 for ; Mon, 18 Jul 2005 23:57:10 -0500 (CDT) Received: from localhost (mf1-pmn.utdallas.edu [192.168.1.8]) by iq1.utdallas.edu (Postfix) with ESMTP id 7E890DAD for ; Mon, 18 Jul 2005 23:57:10 -0500 (CDT) Received: from mx2.utdallas.edu ([129.110.10.17]) by localhost (mf1 [10.110.10.13]) (amavisd-new, port 10024) with LMTP id 05391-01-100 for ; Mon, 18 Jul 2005 23:57:04 -0500 (CDT) Received: from priv-edtnes46.telusplanet.net (defout.telus.net [199.185.220.240]) by mx2.utdallas.edu (Postfix) with ESMTP id 9C5013392 for ; Mon, 18 Jul 2005 23:57:04 -0500 (CDT) Received: from lilith ([209.89.30.219]) by priv-edtnes46.telusplanet.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050719045703.RZKQ3486.priv-edtnes46.telusplanet.net@lilith>; Mon, 18 Jul 2005 22:57:03 -0600 From: "Kevin Jepson" To: , Cc: "'Lennie Irvin'" Subject: [encore] An interesting article on UNIX programming vs WINDOWS programming Date: Mon, 18 Jul 2005 22:56:49 -0600 Message-ID: <000501c58c1e$45cda620$640119ac@lilith> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: amavisd-new at utdallas.edu X-archive-position: 1441 X-ecartis-version: Ecartis v1.0.0 Sender: encore-bounce@utdallas.edu Errors-to: encore-bounce@utdallas.edu X-original-sender: kevijeps@telusplanet.net Precedence: bulk Reply-to: kevijeps@telusplanet.net List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: X-list: encore Hi Gang This article has some interesting things to say about the differences between UNIX and WINDOWS programming. They apply equally well to the WEB/MOO issue I think. http://www.joelonsoftware.com/articles/Biculturalism.html Ciao KJ -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.0/50 - Release Date: 16/07/2005 From kevijeps@telusplanet.net Tue Jul 19 21:33:23 2005 Received: with ECARTIS (v1.0.0; list encore); Tue, 19 Jul 2005 21:33:24 -0500 (CDT) Return-Path: X-Original-To: encore@nobel.utdallas.edu Delivered-To: encore@nobel.utdallas.edu Received: from iq1.utdallas.edu (iq1-pmn.utdallas.edu [192.168.1.7]) by nobel.utdallas.edu (Postfix) with ESMTP id C7FBC5BC4 for ; Tue, 19 Jul 2005 21:33:23 -0500 (CDT) Received: from localhost (mf1-pmn.utdallas.edu [192.168.1.8]) by iq1.utdallas.edu (Postfix) with ESMTP id 7A3F710E2 for ; Tue, 19 Jul 2005 21:33:23 -0500 (CDT) Received: from mx2.utdallas.edu ([129.110.10.17]) by localhost (mf1 [10.110.10.13]) (amavisd-new, port 10024) with LMTP id 16723-01-95 for ; Tue, 19 Jul 2005 21:33:19 -0500 (CDT) Received: from priv-edtnes51.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx2.utdallas.edu (Postfix) with ESMTP id AA813344E for ; Tue, 19 Jul 2005 21:33:15 -0500 (CDT) Received: from lilith ([209.89.30.219]) by priv-edtnes51.telusplanet.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050720023314.RMCT13703.priv-edtnes51.telusplanet.net@lilith>; Tue, 19 Jul 2005 20:33:14 -0600 From: "Kevin Jepson" To: , Subject: [encore] More on Philosophy of Design (Unix but applicable to Moo as well) Date: Tue, 19 Jul 2005 20:33:11 -0600 Message-ID: <000001c58cd3$5f9cb220$640119ac@lilith> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: amavisd-new at utdallas.edu X-archive-position: 1442 X-ecartis-version: Ecartis v1.0.0 Sender: encore-bounce@utdallas.edu Errors-to: encore-bounce@utdallas.edu X-original-sender: kevijeps@telusplanet.net Precedence: bulk Reply-to: kevijeps@telusplanet.net List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: X-list: encore Good Evening All The following is a link to the "basics of Unix philosophy" from the book reviewed in the article I linked to yesterday. I found it quite illuminating. Much of what is discussed is directly applicable to moo programs in = general and moo client design in particular. I have quoted the summary below. Enjoy Ciao. KJ http://www.faqs.org/docs/artu/ch01s06.html =20 The Unix philosophy (like successful folk traditions in other = engineering disciplines) is bottom-up, not top-down. It is pragmatic and grounded in experience. It is not to be found in official methods and standards, but rather in the implicit half-reflexive knowledge, the expertise that the = Unix culture transmits. It encourages a sense of proportion and skepticism = =97 and shows both by having a sense of (often subversive) humor. Doug McIlroy, the inventor of Unix pipes and one of the founders of the = Unix tradition, had this to say at the time [McIlroy78]: (i) Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new features. (ii) Expect the output of every program to become the input to another, = as yet unknown, program. Don't clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don't insist on interactive input. (iii) Design and build software, even operating systems, to be tried = early, ideally within weeks. Don't hesitate to throw away the clumsy parts and rebuild them. (iv) Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw = some of them out after you've finished using them. He later summarized it this way (quoted in A Quarter Century of Unix [Salus]): This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface. Rob Pike, who became one of the great masters of C, offers a slightly different angle in Notes on C Programming [Pike]: Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try to second guess and = put in a speed hack until you've proven that's where the bottleneck is. Rule 2. Measure. Don't tune for speed until you've measured, and even = then don't unless one part of the code overwhelms the rest. Rule 3. Fancy algorithms are slow when n is small, and n is usually = small. Fancy algorithms have big constants. Until you know that n is frequently going to be big, don't get fancy. (Even if n does get big, use Rule 2 first.) Rule 4. Fancy algorithms are buggier than simple ones, and they're much harder to implement. Use simple algorithms as well as simple data structures. Rule 5. Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be = self-evident. Data structures, not algorithms, are central to programming.[9] Rule 6. There is no Rule 6. Ken Thompson, the man who designed and implemented the first Unix, reinforced Pike's rule 4 with a gnomic maxim worthy of a Zen patriarch: When in doubt, use brute force. More of the Unix philosophy was implied not by what these elders said = but by what they did and the example Unix itself set. Looking at the whole, we = can abstract the following ideas: Rule of Modularity: Write simple parts connected by clean interfaces. Rule of Clarity: Clarity is better than cleverness. Rule of Composition: Design programs to be connected to other programs. Rule of Separation: Separate policy from mechanism; separate interfaces = from engines. Rule of Simplicity: Design for simplicity; add complexity only where you must. Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do. Rule of Transparency: Design for visibility to make inspection and = debugging easier. Rule of Robustness: Robustness is the child of transparency and = simplicity. Rule of Representation: Fold knowledge into data so program logic can be stupid and robust. Rule of Least Surprise: In interface design, always do the least = surprising thing. Rule of Silence: When a program has nothing surprising to say, it should = say nothing. Rule of Repair: When you must fail, fail noisily and as soon as = possible. Rule of Economy: Programmer time is expensive; conserve it in preference = to machine time. Rule of Generation: Avoid hand-hacking; write programs to write programs when you can. Rule of Optimization: Prototype before polishing. Get it working before = you optimize it. Rule of Diversity: Distrust all claims for =93one true way=94. Rule of Extensibility: Design for the future, because it will be here = sooner than you think. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D- Kevin Jepson R.E.T. President 4K Consulting Inc. =20 An't nanum hearm deth, doth hwaet ye willath. Email: kevijeps@telus-Nospam-planet.net =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =20 --=20 No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.1/51 - Release Date: 18/07/2005 =20 From Lirvin@accdvm.accd.edu Thu Jul 28 06:04:58 2005 Received: with ECARTIS (v1.0.0; list encore); Thu, 28 Jul 2005 06:04:58 -0500 (CDT) Return-Path: X-Original-To: encore@nobel.utdallas.edu Delivered-To: encore@nobel.utdallas.edu Received: from iq1.utdallas.edu (iq1-pmn.utdallas.edu [192.168.1.7]) by nobel.utdallas.edu (Postfix) with ESMTP id 8CA055BB0 for ; Thu, 28 Jul 2005 06:04:58 -0500 (CDT) Received: from localhost (mf1-pmn.utdallas.edu [192.168.1.8]) by iq1.utdallas.edu (Postfix) with ESMTP id 5034919F6 for ; Thu, 28 Jul 2005 06:04:58 -0500 (CDT) Received: from mx2.utdallas.edu ([129.110.10.17]) by localhost (mf1 [10.110.10.13]) (amavisd-new, port 10024) with LMTP id 25277-01-88 for ; Thu, 28 Jul 2005 06:04:52 -0500 (CDT) Received: from ACCDVM.ACCD.EDU (accdvm.accd.edu [209.184.119.1]) by mx2.utdallas.edu (Postfix) with SMTP id 7B1413430 for ; Thu, 28 Jul 2005 06:04:52 -0500 (CDT) Received: from Gilgamesh.accdvm.accd.edu [10.1.11.27] by ACCDVM.ACCD.EDU (IBM VM SMTP V2R4a) via TCP with SMTP ; Thu, 28 Jul 2005 06:03:56 CDT Message-Id: <6.2.0.14.0.20050728055417.01cf4dc8@accdvm.accd.edu> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Thu, 28 Jul 2005 06:04:47 -0500 To: encore@utdallas.edu From: Lennie Irvin Subject: [encore] Final version of Usability Report Cc: development@encore-consortium.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: amavisd-new at utdallas.edu X-archive-position: 1443 X-ecartis-version: Ecartis v1.0.0 Sender: encore-bounce@utdallas.edu Errors-to: encore-bounce@utdallas.edu X-original-sender: Lirvin@accdvm.accd.edu Precedence: bulk Reply-to: Lirvin@accdvm.accd.edu List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: X-List-ID: X-list: encore Hi Everyone, I pleased to announce the Final and official draft of the May 2005 Usability Study of enCore beta v5 is complete. The report can be viewed at http://www.encore-consortium.org/reports/5388_frodo_report_final.pdf This report also includes video clips of some of the actual usability tests. Most revealing are the clips dealing with dropping an object. I encourage you, if you haven't already, to take a look at this report. We are in the midst of working on a new verion of enCore, so now is the time to discuss the results of this report and come to some consensus about how best to address some of the fundamental problems enCore has with usability right now. Yours, Lennie