I think we covered a few of these on IRC, but for everybody else:

If Uses everything on the line, regardless of what the token is, even if it is a colon. Colons will separate commands, but does not work exactly like a newline. This allows more complicated math formulas in the conditional.

To draw Text( on another buffer, you will need to make that buffer the main buffer. To set it back to the main buffer afterwards, use Disp pi9340.

Recallpic has the following syntax: RecallPic #[,Method[,Buffer
So to use a different type of logic, change Method:
0=Overwrite
1=AND
2=XOR
3=OR
5=Erase

The developers version has been uploaded to the Google project page for Scope OS for anybody that wants to try it in WabbitEmu. I doubt it is error free, but you can get an idea of how it works.

Download
Documentation is included, naturally, as well as the mangled source.

I added the GETD() function and CD(). CD() simply changes the default path and GETD() returns a string with information on the files in the given directory, such as the file names, types, and sizes. Now I can play with the included BatLib commands to try to get a simple GUI started


If you want the parser hook installed, you have to NOT let the program finish when executing a program from the app(I just press ON or try to run an assembly program).

Hey everybody, I believe this is my next big project while I take a break from Grammer. In fact, this program used some code from my current progress on GrammerOS, but I will probably end up using this project for GrammerOS later. Anyways, what is it?

FileSyst provides some core routines for handling a filesystem on the TI-83+/84+/SE calculators and in the plans are a full folder system support, along with navigation, naming of the variables, icons, and a slew of other abilities. Currently, progress is in the planning stage. A few days ago I made a program and last night I turned it into an App. I basically took BatLib, hollowed it out except for about 50 BatLib commands, then I inserted what I had done with the program version and it is an undocumented mess at the moment. However, it has this much completed:

-Run the app and select the program to run (this is only for the developers version)
-The program will be executed using the FileSyst parser hook (hooks are restored when the program finishes)
-The dim() token is used to execute the included BatLib routines or the FileSyst routines.
-FileSyst takes arguments as a string. For example, "BASIC(Zeda:Doc Prog)" .
-FileSyst can open folders and files and automatically creates folder/files if you try to access them and they don't exist.
-There are only two commands at the moment:

BASIC() will open a file and try to execute it as a BASIC program
VPTR() will make a shortcut to an OS variable (the var doesn't actually need to exist)

An example might be:
dim("VPTR(prgmTEST,Zeda:Doc Test) BASIC(Zeda:Doc Test)
However, once I add in the CD command (which is basically only three bytes of code at this point):
dim("CD(Zeda:Doc) VPTR(prgmTEST, Test) BASIC( Test)
Anyways, since the program isn't very presentable, I won't release a program yet. Currently, there are two other projects that are already in the works to use this program-- ScopeOS by Codebender (with help from myself and Roguebantha) and Linux which is being done by Roguebantha (originally using BatLib, but that is why we have included certain BatLib commands in this app).

ScopeOS will hopefully provide a nice GUI to view the files and folders as well as all of the OS variables. I plan to add the following commands shortly:
CD(path)         This will open a folder (or use ".." to go up one folder level)
CF(filepath,field,data)     This will change a field in the header data of a file. Fields could be for passwords, descriptions, or specifying what programs to open the file with.
CI(filepath,icon#|icondata) This will change the icon number, or if you supply hex data, it will change the icon to a custom icon.
CN(filepath,newname)            This will change the name of a file.
COMP(filepath)              This will compress a file
COPY(filepath,newpath|newfilepath) This will copy a file from one location to another
DADD()                      Returns a string with the current directory
DEL(path) or DEL(filepath)   This will delete a folder or file.
GETD(path,#)                 Returns info aboutt he nth item in the directory (so you can create a list of variables or whatnot)
HIDE(filepath)              This will mark a file or folder as hidden
LOCK(filepath)              This will mark a file or folder as locked
MOVE(filepath,newpath)       Moves a file to another directory
ND(loc)                     This adds a new directory
SCUT(lfilepath,newloc)       This creates a shortcut of a file.
VPTR(VarName,filepath)      This will create a file that points to an OS variable

It currently supports relative paths where it starts from the current directory and absolute paths where it starts from the main directory. It also allows you to navigate back through directories by using ".." (or navigate back another directory for every additional period).

I wish it looked prettier so that I could supply some cool screenshots, but really, you don't see much happening. I've spent many hours over the past three days working on this working out any potential bugs. I hope the new years brings success because I had a really cool thought about how to use this when I first started.

Say you were making an RPG and you wanted to use a folder to store or retrieve monster data, player data, or anything else like that. You could use this program to make a directory in the main folder (named after your game or something), then in that folder you could put all of the other data you need. Then, to retrieve the data, you can use the FileSyst program to access the data through paths. Since the app has a bunch of graphics and data manipulating commands, I can make commands like SPRITE() so that you can make a script for certain parts of your program.

Here is a screenie from yesterday's version:

Because Slova is supposed to be an educational game -- a fun one, but an educational one nonetheless -- I'm adding "shields" to the game.  You can hit gruzzles up to 4 times without dying in a level.

I think that is a good idea, since the main challenge of the game should be memorizing the words as opposed to defeating or escaping from monsters.

Good luck on that venture, tr1p

What do you mean by rules? If you mean using previously-made games in the contest, then in fact the contest theme is ports, meaning porting existing games to new calcs, along with a game occuring around a ferry or cables being plugged in ports.

I mean rules relating to getting help from somebody else.

Also how good is the 4 level grayscale in grammer?

Runer or thepenguin77 could probably make it better using interrupts or something, but otherwise it is pretty good, I think. There are 12 grayscale modes, but it is all 4-level gray using different saturations. Even black/white and 3-level uses the four-level grayscale routine when you do DispGraph. Its just with 3-level gray, it uses 100-50-50-0 for the colors, so the grayscales have the same color.

Here is a quick screenie

Interesting, so basically it lets you ungroup stuff within BASIC programs so RPGs, for example, can be kept in as few files as possible?

Yes, precisely! I was also thinking of having a function to execute programs from a group. That would save you from having to manually copy it to RAM and execute it.
I also won't be adding the ability to group files, so I won't have to worry about causing that kind of a problem

Finally, I attached the download to the first post, as well as the readme/documentation so you can read about it