Manual CCSPS IRON 3.0.0

this acts as both a user and developer manual/guide for CCSPS Iron 3.0.0

==File Formats==
-txt
Text document, all users have access to this file, permissions are decided by details in folders directory
-sys
System File, only developers can access this file, used to store important information such as boot file directories, lists, etc
-os
Operating system Script, can only be ran by other operating scripts
-lua
Lua executable
-prg
program executable, ran off included emulator
==prg format==
It is highly recommended for you to start off with the example program included with every installation
>Window
Windows are what the visual side of a program is ran on. Windows visuals are handled by Graphics system. Only thing you need to worry about is giving it commands
>Callbacks
-onCreation(minimizable,fullScreen,title,)
When ever application is first ran, this callback will be searched for and used as reference, if it is not found then it will resort to defaults(true,false,"example.txt"). It will also run all Functions below until it reaches a “end” statement
-onStart(background,entitypath,)
Ran when ever program is called or read
-onInteraction(id,action,path/command,arg,)
Apon a entity being interacted with, will search for this callback with id of desired entity. Will then run the desired command.
> Entity Format
id,type,text,path,w,h,wX,wY
-Types:
Text: Displays text, can also act as button
Image: Displays Image at given path
Video: Displays Video at given path
>functions
Functions requires a lot of explaining. First place the call, it can be in any of the mentioned callbacks in Section [Callbacks]. Should be in the “path” section of any call back that supports path/command.

The call should look like this
<Function*>
*name of function

Example. onInteraction("id","click",<Function>,arg,)

now to have it do stuff!
-function call
funct.Function*1(formula*2,event*3,)
1* name of function
2* formula/requirements for function to continue, if you want it to happen without requirements, replace with "n". Check formula section for more.
3* event called if specifications are meet. See Events Section for more.
-formulas
Supported args:
//file explorer//
[[fe.exists<target*1>]]
Returns true if file exists, else it returns false
1* path of file
//installer//
[[in.version<target*1+req*2>]]
Checks online if target file supports given version
1* code
2* version required
//system//
[[sys.user]]
returns current user
//operating system//
[[os.version]]
returns current os version
[[os.package<target*1>]]
returns if os has target api
1* api call

//general
See Arguments

-Events
Events are used to request console to run a command or action
Following are supported at time of writing:
/file Explorer/
[[fe.open<target*1>]]
opens target file in a new window
1* path
[[fe.delete<target*1>]]
requests deletion of chosen file. if file isn’t within same directory as program file and isnt listed on admin applications list, will prompt user if it’s okay to delete given files.
/installer/
[[in.dwld<code*1+path*2>]]
Installs target file at given path, if path is outside programs directionary and isn’t a admin file, will prompt user if they are okay with downloading file
1* pastebin code
2* path to download to
> Arguments
When ever you see “arg”, you follow this
Layout: {a.b.c.d.e.}*
*letters used in place of variables

Call backs will give following args depending on what activists them:
x - x position of mouse at call
y - y position of mouse at call
t - time of call
d - day at call, from January 1970
f - frame at call
i - key input at call

==Operating System==
> Console System
To allow simultaneous operations of many tasks, and Windows, OS runs primarily off a dual system, Console and Graphics. Console receives all updates/events and creates/edits files. While graphics opens those files and displays the results on the screen.

-Events
/application/
Used by applications to request changes/data/actions from console. This is what allows multiple Windows to be up at once, working together
/security/
Highest priority Event category. Only files allowed to run with this event type contained inside are ones with the .os tag, this event is used for crashes, updates, alerts, etc
/installer/
Used to let console and user know how installation of new files is going
/network/
Used by local network features
/general/
See CC Tweaked wiki, events for information on basic events