home *** CD-ROM | disk | FTP | other *** search
- Path: goliath.apana.org.au!amioz!spinnedev
- From: spinnedev@amioz.apana.org.au (Terence Nichols)
- Message-ID: <31114c58@amioz.apana.org.au>
- Newsgroups: comp.sys.amiga.programmer
- Subject: UASAS 1.2 (Discussion Document for public comment)
- Date: 01 Feb 96 17:49:37 GMT
- Organization: AmiOZ BBS Australia <UUCP<->Fido gateway>
- X-GateSoftware: AmiGate 1.3a (24.3.95)
-
- $VER: UASAS 1.2 (01-02-96) (c) Terence Nichols 1996
-
- THE ULTIMATE AMIGA SOFTWARE AUTHORING SYSTEM
-
- by Terence Nichols
-
- INTRODUCTION.
- -------------
-
- This document is presented to encourage Amiga developers and
- programmers to consider the development of a new programming interface
- for the Amiga range of computers. UASAS at this stage has not been
- developed by the author beyond this discussion document and the
- document at this stage is less than complete. The author has released
- this document for comment and discussion by the development and
- programming community.
-
- The author requests that no modifications be made to this document and
- that all suggestions Etc. be directed to him. It is envisioned that
- after due discussion by the development and programming community and
- due consideration by the author, the author will update this document
- and ensure that the revised document will be made available for
- further discussion Etc.
-
- Full credit will be given to those people who's suggestions Etc. are
- included in future revisions.
-
- The author retains the copyrights to his intellectual property and
- recognises the rights and patents of all products Etc. mentioned in
- this document.
-
-
- 0.0 : UASAS Basics.
- -------------------
-
- UASAS is an icon based software authoring system for the Amiga range
- of computers. It will allow non and novice programmers to write
- compiled programs using a graphical user interface (1.1). Programmers
- will have the option of writing code at a level below the GUI (1.2)
- and if desired write or add assembly code to the program (1.3), if
- supported by the parent language, before final compilation. The
- compiled program will be fully independent of any specific special
- libraries with the exception of standard Amiga shared libraries
- (reqtools, bgui, Xpr's, triton, Etc.).
-
- UASAS will not require it's own shared library once compiled.
-
-
- 1.0 : UASAS User Levels.
- ------------------------
-
- 1.1 : Non / Novice Programmer.
- ------------------------------
-
- At the highest level UASAS will have a point and click graphical user
- interface, with full access to all the Amiga operating systems
- libraries and external shared libraries Etc. The UASAS will generate
- commented code in the form of a user editable text file in either the
- languages native code, or Assembly language. UASAS will use the
- comments in the native code to rebuild manually edited source files
- for the UASAS GUI.
-
- 1.2 : Programmer.
- -----------------
-
- At the Mid level the programmer may use any text editor to write the
- code or modify the UASAS commented code without using the UASAS GUI.
- Correctly written code may be loaded into the UASAS GUI to be amended
- or modified. UASAS will use the comments in the native code to rebuild
- manually edited source files for the UASAS GUI if the programmer
- requires.
-
- 1.3 : Wizard. ( If parent language permits. )
- -------------
-
- At the lowest level UASAS will support assembly language as linkable
- modules to allow the programmer the option of writing optimized
- assembly code routines for those areas the programmer requires. UASAS
- will use the comments in the native code to rebuild manually edited
- source files for the UASAS GUI.
-
-
- 2.0 : UASAS Graphic User Interface System.
- ----------------
-
- 2.1 : UASAS Editor Screen.
- -------------------------
-
- UASAS will open either it's own Amiga Public Screen or optionally use
- any other public screen.
-
- 2.2 : UASAS Editor Window.
- --------------------------
-
- The heart of the UASAS system is the Editor Window. The window will be
- resizable and depth arrangable with a scroller bar at the right hand
- side and at the bottom of the window. Alternately the scrollers will
- be at the left and top or any legal combination of the two. More than
- one UASAS window may be open at the one time, although memory
- requirements may have to be taken into consideration for the maximum
- number of windows open. It is in the Editor window that the programmer
- will lay out the program icons in a similar style to drawing a program
- flow chart.
-
- 2.3 : UASAS Icons.
- ------------------
-
- Each command of the source language will have a UASAS icon.
-
- 2.3.1 : Special Icons.
- ----------------------
-
- UASAS will use special icons to represent program flow direction and
- control.
-
- 2.3.2 : Group Icons.
- --------------------
-
- The group statements, such as IF THEN END IF, CASE END CASE,
- SUBPROGRAMS, PROCEDURES, Etc. will open their own window. Thus
- allowing UASAS to fold the program into smaller groups. Alternately
- UASAS will display the icons on the main window. The programmer will
- be required to initially build the groups in the main window to allow
- linking to other areas of the program prior to folding.
-
- 2.3.3 : User Configurable Icons.
- --------------------------------
-
- UASAS will support user configurable icons for external shared
- libraries and assembly code routines Etc.
-
- 2.3.4 : UASAS Icon Parameters.
- -----------------------------
-
- Icons requiring parameters will when placed into the UASAS window open
- a requester that the programmer will be required to fill with the
- necessary details.
-
- For example if an icon was used to specify a variable, the programmer
- will be required to put the variable name into the requester. The
- requester will display in a listview all currently used variables.
-
- 2.3.5 : UASAS Icon Display.
- ---------------------------
-
- The icons will be displayed in user configurable banks in their own
- borderless movable window that will be placed at either the top or
- bottom horizontally or at the left or right vertically. Optionally the
- icon bank will be of the floating type, to allow the programmer to
- move the icon bank around the screen. The number of icons that are
- displayed will depend on the size of the icons and or the screen
- resolution. Ideally there will be two or more icon sets to allow for
- either high resolution (interlaced) or low resolution (non interlaced)
- screens. The icons that are placed on the UASAS window will display
- relevant information under the icon as per icons displayed on the
- Amiga Workbench.
-
- 2.4 : Building User Defined Graphic User Interfaces.
- ----------------------------------------------------
-
- UASAS will have support for current Amiga Operating Systems WIMP
- interface and allow the programmer to quickly and easily create
- Screens, Windows, Menus, Requesters, Etc.
-
- 2.4.1 : External GUI Libraries.
- -------------------------------
-
- UASAS will support external GUI's such as reqtools, triton, Bgui, Etc.
- These external GUI libraries will be plug in modules that seamlessly
- integrate into UASAS. Complete with custom icons.
-
- 3.0 : UASAS Programming.
- ------------------------
-
- The first window opened will be the program base. On the base window
- the programmer will place the UASAS program icons and then connect
- them using the flow direction icons. The programmer will place the
- icons in the same manner as writing a program flow chart.
-
- 3.1 : Placing UASAS icons.
- --------------------------
-
- The icons will be selected from the icon bank by clicking on the
- required icon with the left mouse button. The cursor will then change
- to an image of the selected icon which the programmer shall place into
- the UASAS program window by again clicking with the left mouse button.
- Icons may be placed together to represent a program flow.
-
- 3.2 : Flow direction precedence.
- ---------------------------------
-
- Program flow will be limited to only one direction change per program
- step. This is to ensure readability and logical control are
- maintained. Icons may be placed to the left, right, above or below the
- preceding icon. Any one icon cannot be adjacent to more than two other
- icons.
-
-
-
- 99.0 : Revision History.
- ------------------------
-
- Version 1.1
- ------------
-
- First limited release for comment by selected programmers.
-
-
- Version 1.2
- -------------
-
- Public release into selected programming conferences for comment by
- interested parties and prospective developers.
-
- References to possible base languages were removed so as to not
- polarize the discussion on any particular language as a UASAS base.
-
- Sections 3.0 > 3.2 were added.
-
- Thank you to David Benn for encouraging me to make the 1.2 release
- available for comment.
-
-
- About the Author.
- -----------------
-
- Terence Nichols has been an Amiga user and sometime programmer since
- the introduction of the Amiga A500 and 1.3 operating system. He may be
- contacted,
-
- Internet Email : - Terence Nichols spinnedev@amioz.apana.org.au
- Fidonet Netmail : - Terence Nichols 3:713/817.2
-
- Voice : (091) 841313
- Fax : (091) 841119
-
- Postal Address :
-
- Terence M. Nichols
-
- PO Box 228
- Pannawonica
- Western Australia
- 6716
-
- ---8<--------------------------------------------------------------------
-
- YOUR SHOUT
-
- From Terence Nichols in THE DESERT, Pannawonica, Western Australia
-
- +------------------------------------------------------------------------+
- | Spinne Developments Australia Spinne Developments |
- | Desert Software Utilities The Worlds most isolated |
- | for the Amiga Computer. Software Development |
- | TERENCE NICHOLS Company |
- | |
- | spinnedev@amioz.apana.org.au |
- | |
- | FIDONET 3:713/817.2 AMIGANET 41:200/817.2 |
- +------------------------------------------------------------------------+
-