home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ARM Club 3
/
TheARMClub_PDCD3.iso
/
mag_discs
/
14
/
programs
/
banner
/
!BanEd
/
Documents
/
Banner
/
Help
< prev
Wrap
Text File
|
1994-06-22
|
3KB
|
66 lines
!Banner Vsn 0.10 - Documentation
--------------------------------
Index
-----
Section A: Introduction
B: Getting !Banner to work
C: Problems and further ideas
A: Introduction
---------------
!Banner is inspired by a plea in the DataFile catalogue for a program that will
display banners for a predetermined time just like Impression does. The brief
stated the need to display a sprite on the desktop with the ability to overlay
text in any font and at any size upon the sprite. !Banner is designed to be
placed within the directory of an application that needs a banner displayed.
!Banner acheives this using a script 'Language' which allows all these
paramters to be changed easily and quickly in a seperate Text file whose name
can be specified by the user and is placed within !Banner's directory. The
sprite to be displayed is contained within a file whose name can be user-defined
as can the name of the sprite to be displayed. The size of this sprite is
determined and a window is created to fit the sprite and centred upon the screen
and displayed for a period of time defined in the script file.
!Banner nominally claims 32K for itself and claims more memory depending on the
size of the sprite file that contains the sprite to be displayed. Also please
note that large hi-res sprites will lead to over 300K being claimed by the
application. The application works as a seperate task and quits itself as soon
as the window is closed.
B: Getting !Banner to work
--------------------------
It is expected that !Banner is run from another appliaction's !Run file using
the following command:
Run <App$Dir>.!Banner Script
where <App$Dir> is the system variable containing the parent application's
filepath and Script is the name of the text file containing the script itself.
In this way, !Banner can have more than one script file in its directory and the
parent application can run a different script under different conditions.
Please note that !Banner must remain intact at all times - you must not dissect
up !RunImage to include within your own application.
C: Problems and further ideas
-----------------------------
Problems at the moment:
- The whole program is not at all secure - people could easily change the script
file and ruin the whole display. Need some security somehow.
- Command script is very limited. But I'm loathed to add things at the moment
until I hear from people and am told what is really needed.
Ideas for possible inclusion in next release
- Allow the system font to be scaled
- Allow rotation and translation of text
- Allow rotation and translation of sprite
- Include option for OK buttons to remove window rather than a time delay
© Brian Marsden 22/6/94