---SMILETOOL CHALLENGE---

Deadlines ;_; Does it just need to be a 'smile tool' type program or can it be anything?

Deadlines ;_; Does it just need to be a 'smile tool' type program or can it be anything?

It needs to be a SmileTool type program that is better than the initial SmileTool.

Are we allowed to modify the existing one, or do we need to write the whole thing from scratch? Because making an image editor better than the existing one would be very hard. (though there are some bugs to fix)

Are we allowed to modify the existing one, or do we need to write the whole thing from scratch? Because making an image editor better than the existing one would be very hard. (though there are some bugs to fix)

The image editor isn't technically part of the SmileTool. Soooo...

well, it sort of is When you exit it, it sends you to SYS/SBSMILE, so you would need to edit it.

You may use the original as a base.

Are we allowed to modify the existing one?

Yes.

I can finally make the OS of my dreams.

This can't be uploaded as a participant to the contest (It's not even mine, it's RRRQ's) but this would be a good SmileTool base for anyone confused: VK2KE4JS

Another problem. Programs are only allowed to access files inside their own project. (unless the program is inside SYS, when it can only modify files in the active project) this means that things like the paint tool will only work inside the SYS folder, and since the smiletool tools send you to SBSMILE when you exit, this entire challenge is pointless

I think you can access programs out of their own project by loading them like LOAD"PRG0:FOLDER/PROGRAM"

I think you can access programs out of their own project by loading them like LOAD"PRG0:FOLDER/PROGRAM"

No, that doesn't work :( The only time you can do that is with SYS/file

I'm working on a full fledged MML Tracker, which is sorely missing in the SBSmile tool, but I can't imagine building a whole, feature complete, smile tool. Doing that well is a huge undertaking. I think the way the smile tool currently connects programs together is the right goal. Maybe if we focus on components that could be improved individually, we'll end up with a better product. It's more realistic too.

The problem is that we can't make a custom smiletool that can modify files within the current project. This means no SAVEing or LOADing

The problem is that we can't make a custom smiletool that can modify files within the current project. This means no SAVEing or LOADing

We most definitely can.

This means no SAVEing or LOADing

There are some hacky ways around this. I was beta testing someone's project, which oddly enough didn't contain a project folder. When I saved progress in their application, it wrote the save data into my other project directory, since I hadn't changed it to run their code. I don't think it's reasonable to organize a smile tool this way, but it's one way around that restriction.

The problem is that we can't make a custom smiletool that can modify files within the current project. This means no SAVEing or LOADing

We most definitely can.

how?

The problem is that we can't make a custom smiletool that can modify files within the current project. This means no SAVEing or LOADing

We most definitely can.

how?

Running a program as a SmileTool , you can provide a folder name in the path you pass to SAVE and LOAD. (option tool doesn't change anything) You can also do FILES "//" and get ALL the projects. When you do file operations, you'll have to ask for the project name however. Doing SAVE or LOAD without a folder name, it will use the current project folder. This folder is set whenever you run a program, including the SmileTool program itself, so it will not be your active project. The built-in editors get around this by living in SYS, which can't be the current project folder.