jnh@ece-csc.UUCP (Joseph Nathan Hall) (03/18/89)
OK, judging from the responses thus far, I am confident that this thing CAN fly ... I've heard from several people who are willing to contribute and a larger number who are willing (eager?) to "test" the material. I would like to solicit draft submissions. Here are the proposed terms: The UMPG will be PUBLIC DOMAIN. There will be no copyrights and any and all material may be reprinted or reused for any purpose whatsoever. Authors agree to relinquish all rights to the material submitted upon the final distribution of the UMPG to the net. (Until that time, they will retain all rights to their text and source code.) All authors will be credited as accurately as possible. We will do this project as a public service to Macintosh programmers, whether they be amateurs or professionals. If anyone disagrees with these proposed terms, or would care to comment on them, PLEASE E-MAIL your remarks to me. I will dutifully summarize and post them. For now, though, please include any appropriate copyright notice in your submissions. I will respect them and include them in any distribution of the material for review. Particular areas of interest are: * a basic event loop structure (Pascal and "C" source is a must!) * "C" vs. Pascal, particularly declarations of callback routines (scroll tracking, etc.) and code resources (?DEF functions and others) * how to do Mac file I/O, including startup files, file save/load, examples of how to set file creator, type, etc. * how to set up application and document icons * how to print something * how to methodically handle menu highlighting/dimming/item replacement when windows are activated/deactivated--a general- purpose approach is greatly needed here * source code for popup menus * source code for hierarchical menus (this one isn't too hard) * source code (including an INIT) for tearoff menus, if anyone has this * source code for a WDEF (does anyone have that circular window WDEF around still? is it public domain?) * source code for a modular text editor that is more powerful than TextEdit--including tab support, multiple styles, etc. Wouldn't have to be as complex as even old MacWrite but should be enough to support, say, an editor for program text. Maybe we could rewrite and/or extend the LightSpeed MiniEdit example. * event loop programming in general as it relates to both the Mac environment and other environments (X, for example) * any resource editing/building tools that are really effective * a set of meaningful programming standards--NOT just a set of rules for indenting and capitalizing programs. Ideally everything will be written/re-written to comply with this. * comparisons between the different "C" environments (mainly MPW and LSC) and the different Pascal environments (ditto). * notes for BASIC programmers (yes, there are a bunch of these!) * a set of useful MIDI drivers/low-level code and documentation ...and I'm sure there's more that would be useful. I would envision distributing the Guide (whenever it's in a more-or-less final draft form) in binhexed MS Word format. MacWrite is a possiblity, too, but it seems to me that Word has probably become an acceptable lowest common denominator. Again, email your comments to me. Perhaps a plain text version could be distributed as well. E-MAIL submissions and comments to me. I will summarize and post comments, and will note submissions. I will be preparing two mailing lists, one for submitters and one for reviewers. Please indicate which you would like to be on. Submitters will get everything sent to reviewers, so it will make no sense to be on both. I would anticipate a delay of about one-two weeks before I start mailing out stuff. This was posted to comp.sys.mac so that everyone could see it. Please send followups (if you can't e-mail instead) to comp.sys.mac.programmer, so we can spare the users and hardware guys. I look forward to working on and submitting to this project, and I appreciate the support I have gotten so far. -- v v sssss|| joseph hall || 201-1D Hampton Lee Court v v s s || jnh@ece-csc.ncsu.edu (Internet) || Cary, NC 27511 v sss || the opinions expressed herein are not necessarily those of my -----------|| employer, north carolina state university . . . . . . . . . . .
mfi@beach.cis.ufl.edu (Mark Interrante) (03/18/89)
In article <3966@ece-csc.UUCP> jnh@ece-csc.UUCP (Joseph Nathan Hall) writes: >Particular areas of interest are: > > * a basic event loop structure (Pascal and "C" source is a must!) [...] > * a set of useful MIDI drivers/low-level code and documentation > >...and I'm sure there's more that would be useful. I think we should begin talking about other interesting pieces of code that would belong in such a system. In addition to a simple text editor, I would like to see a simple drawing program. Nothing special just draw, drag, select,modify rectangles and a simple pallete. Also some information on writing serial drivers. The proper use of regions. These are just a few ideas. ----------------------------------------------------------------------------- Mark Interrante Software Engineering Research Center mfi@beach.cis.ufl.edu CIS Department, University of Florida 32611 ----------------------------------------------------------------------------- "X is just raster-op on wheels" - Bill Joy, January 1987
zuhn@umn-cs.CS.UMN.EDU (David D "Zoo" Zuhn) (03/18/89)
In article <3966@ece-csc.UUCP> jnh@ece-csc.UUCP (Joseph Nathan Hall) writes: > >I would envision distributing the Guide (whenever it's in a more-or-less >final draft form) in binhexed MS Word format. MacWrite is a possiblity, >too, but it seems to me that Word has probably become an acceptable lowest >common denominator. Again, email your comments to me. Perhaps a plain >text version could be distributed as well. > >-- >v v sssss|| joseph hall || 201-1D Hampton Lee Court > v v s s || jnh@ece-csc.ncsu.edu (Internet) || Cary, NC 27511 > v sss || the opinions expressed herein are not necessarily those of my >-----------|| employer, north carolina state university . . . . . . . . . . . The common denominator among all programmers is TEXT files. Many people do NOT like to use MS word for many reasons. Let plain ascii text files be the major medium here. That way it is accessible in any of the popular packages (just open up McSink or a edit window in MPW/LS[PC] etc). David D "Zoo" Zuhn // University of Minnesota \\ Twin Cities Computer Science Systems Consultant, EE/CS 4-204 zuhn@umn-cs.cs.umn.edu, zuhn@umn-cs.UUCP, ..rutgers!umn-cs!zuhn
-Cheshire-@cup.portal.com (Gary Edward Learned) (03/19/89)
As long as we are throwing things out here, what has been really lacking
are examples of data entry methods, including both modeless dialogs,
and scrolling windows, which have entry points scattered throughout (i.e.
the filling in of a form).
-- And remember the old adage...Everything you know is wrong
Gary-Cheshire-@cup.portal.com (Gary Edward Learned) (03/19/89)
If there is interest, I would be willing to develop alongside a Hypercard version of the guide. There would be several advantages to having this format as well, especially if it is done right. Anyone have thoughts?
arwall@athena.mit.edu (Chumley Wood) (03/19/89)
I would add to the list of useful topics: Example code for VBL tasks. ------------------------------------------------------------------------- | Anders Wallgren Back by popular demand: | | arwall@athena.mit.edu Bush-Noriega '88 - A Crack Team! |
arwall@athena.mit.edu (Chumley Wood) (03/19/89)
In article <11647@umn-cs.CS.UMN.EDU>, zuhn@umn-cs (David D "Zoo" Zuhn) writes: > >The common denominator among all programmers is TEXT files. Many people do >NOT like to use MS word for many reasons. Let plain ascii text files be >the major medium here. That way it is accessible in any of the popular >packages (just open up McSink or a edit window in MPW/LS[PC] etc). > I agree that the most used medium is text files, but in the interest of readability and presentation some more aesthetic format is desirable. For those not fortunate enough to have MS-Word or access to laser printers, it would be nice to maintain a plain version, as stipulated in earlier postings. It might be a good idea to have the code segments available for ftp on the major archives. anders ------------------------------------------------------------------------- | Anders Wallgren Back by popular demand: | | arwall@athena.mit.edu Bush-Noriega '88 - A Crack Team! |