It might attract a commercial developer (well, it might!). We're lucky so relatively few have done so Motivate more people to contribute in some fashion to theĭevelopment of Logo. Help people find current versions best suited to their interest. Implementations, we can never find the common in them) UCBLogo, but because of NetLogo - if we never compare (You see, in the example above I've included SET not because of So, the standard may fix that every implementatioh shoud have at least one of these two commands:īut any implementation is free to add other out-of-standard forms. Show designers of new Logo dialects what designsĪdditionally we may include dead Logos in the Atlas,īut there might be a problem to find trusted source of Serve as a cross-reference of available features Make learning other implementaiton easier Make Logo source translation from one implementation Show similarities/differences between implementations This is not a specification, but can be used to: The Atlas will enumerate *and*Ĭompare features of all non-dead Logo implementations. The idea is simple (it hovered in LogoForum/ Subject: Logo Atlast (A Logo Spec Alternative) Logoatlas-AT-frindsbury-DOT-force9-DOT-org-DOT-uk When the project is mature- I am guided by the will of the forum. I only envisage 10 or so active contributers so I think this restriction is acceptable. This is a single editor system- so you need to check the Last Update time to see if anyone else is active. Contributers will log on and change the text directly.ģ. I will establish a 'white list' of contributor to whom I will email the editing password.Ģ. I am logging the changes on my local host, and will FTP the new file across regularly. Any immediate changes- email the changes to me via the mailform. I don't want to establish another 'backwater'. I need- comments posted to the forum to establish that this is a good idea. Designers and authors are encouraged to participate. If you claim copyright for some thing you find here- email me and credit will be given or it can be removed. I believe that this fulfils all the requirements posted and can become the source document needed- or eventually easily modded.Įverything on these pages is changeable. Then cut and pasted from my cut and pastes. I have mercilessly cut and pasted from sources on the web.In addition to provide a place to deposit the urls of manuals, which was mentioned by many.Also it can document how primitives are implemented- A primitives glossary.Primary Sources- putting on line the evidence urls/articles that for others to use later. Analysis- How it differs from Apple II, and Berkeley:.I have implemented this methodolgy as a hierarchically flat file that is displayed in a Content Management System.Describes each Implementation formally and in free text.I have Identified a methodology that is.I have Distilled down aims of the project.The missing Apple II Manual.Īll discussion of these pages will take place on the Logo Forum While we are waiting for one I have scanned the appendices of a couple of books I have borrowed. One of the hanging points was we all agreed to use Apple Logo as a standard- but no one had a copy of the manual. Another requirement of the project.ĬMSimple uses formatting templates so appearance is independant of text- and can be changes at will. Text submitted is easiest to use if it is in 'Semantic HTML'- ie without Ĭmsimple has a search box- allowing the user search for say 'multimedia'. The author is left with for on page formatting. The content is stored in one html file, so it can be uploaded on request and viewed as a single document, which was one of the requirements of the project.Ĭmsimple allows the full range of HTML4.01 tags, with one neat twist, The tags are used to force page breaks-and the page titles you see in the left panel menu. This site is powered by a PHP content management system (cmsimple) written in Denmark under a AGPL licence.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |