Dependency management in SB? I wrote a program to scan for and include libraries you've downloaded. I think this is the beginning of something beautiful... How often and what for do peeps use the smile button? What common shortcuts should be available? I'll include a button to go to the default program.

I made something like that. However, I quit when I found out I could only load SYS files...

Thats what I thought too, but SBS chat had me try a few things. This should be running at higher privileges than a normal program.

How did you get it to work? I always get Illegal Function Calls anytime I try to load a file outside of the SYS folder.

Nevermind. I got it working. Another thing, I found out whatever you execute next retains its elevated privileges.

Yep, its basically an elevated user. Exec should work that way. I'm working on a standardized metadata format and looking to release this soon. How far along is your project? We could collaborate on a staandard format

I created SmileShop, which is sort of like a shop, storing name, publisher, release date, logo data, and actual program data into 1 file if that is the kind of thing you are talking about. I also created a file system which searches thru all your programs and lists them. I created a LogoCreator that uses the elevated privileges to load files and uses SBGED to create them. Can you specify a bit?

I hadn't seen much on SmileShop. Ill take a look at it now. Having a launcher for our downloaded games is awesome! But I think it makes to have my own package file. The purpose of our tools isn't the same. For programming libraries, release date and box art are irrelevant. Also I want to go with a more programmer editable file.

With metadata

Also Im concerned that your launcher could start random games with elevated privileges

I see what you mean. My original version of SmileShop excluded the release date and box art. I could implement support for whatever your planning. It would be relatively easy.

About my launcher and elevated privileges, I do not believe that would necessarily be an issue. The way SmileShop's apps are compiled, only apps that have a specific signature can be downloaded, making eliminating that issue. I could definitely implement support for yours, the support is already there. We just need to be able to read each other's format.

Isn't the SSE compiler available to anyone? A malicious program can still reach a few people before people realize not to download it. I still have 3 "issues" keeping me from switching: 1. Downloads need to be usable w/o the tool 2. Downloads need to be able to list requirements and specify exact version/DLC. 3. I also don't want updates waiting on me.

I think it would be pretty cool to get these to mesh up still; I just think it'll take a lot of rethinking. Imagine an installer for games that picks up the dependencies!

The downloads are usable without the tool, you just need to save it. I planned on making it easier to do that with the next update. Another thing, the compiler isn't available to everyone (or anyone for that matter), unless someone reverse engineered my unpacking process AND released it (haven't seen one yet, so I think we are good with that).

About your second issue, can elaborate on that?

Can I have metadata without a compiled SSE? Would a download have to include uncompiled AND SSE, doubling the size? To clarify 2: I have requirements as e.g "RAYCAST.LIB : 0.1" in a list. If they've downloaded v0.1, it'll be copied. if not it'll prompt the user.

When the user saves the downloaded program, the .SSE is no longer needed (it and its metadata will still exist). The way .SSEs work is by packaging all the data into 1 file. The metadata and program are in the same file. You would just need to unpack it to run the program, so I don't believe you need both.

But to unpack that file the user needs the tool...