Weasel on 23/3/2005 at 21:02
Quote Posted by dracflamloc
When saving the settings, it must create the fmi file and repack it back into the archive for the FM.
I didn't realize Fleshloader would be modifying and repacking the fmi files. I figured the "finished" and "rating" info would all be in a central file.
Quote Posted by dracflamloc
Also when installing to the Thief directory, it makes copies of the fmi, icon, description into it since they are in this single archive.
I also assumed Fleshloader would be installing specific types of files individually, not doing a mass extraction. I guess that assumption was wrong.
Anyway, I'm sorry if I sounded ungrateful. I'm extremely grateful. I'm just trying to give you feedback.
dracflamloc on 23/3/2005 at 21:02
Quote Posted by ZylonBane
Why can't your loader extract the archive itself? The entire POINT of a loader is maximum convenience.
It could extract it by itself... with the result being two copies of the desired FM being on your hard drive, unless I have it automatically delete the original zip file. Thats actually not a bad idea though.
dracflamloc on 23/3/2005 at 21:04
I do appreciate the feedback guys, despite how annoyed I may sound sometimes. I just prefer to code as opposed to arguing over design decisions. I'd rather feedback about bugs you find or maybe interface tweaks, etc...
Weasel on 23/3/2005 at 21:06
Quote Posted by dracflamloc
It could extract it by itself... with the result being two copies of the desired FM being on your hard drive, unless I have it automatically delete the original zip file. Thats actually not a bad idea though.
I don't know about completely automatic deletion, but in general this an interesting idea to explore.
ZylonBane on 23/3/2005 at 21:13
Quote Posted by dracflamloc
It could extract it by itself... with the result being two copies of the desired FM being on your hard drive, unless I have it automatically delete the original zip file. Thats actually not a bad idea though.
If I'm understanding the justification behind this correctly, why don't you release a separate tool for FM authors to package Fleshloader(
ugh)-compliant archives themselves?
I still don't see how the original archive is supposed to differ from the generated archive.
dracflamloc on 23/3/2005 at 21:17
Quote Posted by ZylonBane
If I'm understanding the justification behind this correctly, why don't you release a separate tool for FM authors to package Fleshloader(
ugh)-compliant archives themselves?
I still don't see how the original archive is supposed to differ from the generated archive.
Theres no need. To be a "compliant archive" it just needs to be a zip file that has the Thief3 Directory structure necessary to play the FM.
That archive is then put in another archive with the fmi file. Thats all there is to it.
Be patient. Programming is not an instantaneous process.
SneaksieDave on 23/3/2005 at 21:17
I must not be getting what you're saying. So, the files are on the hard drive twice? Once, in the folder we created ourselves, when we extracted it ourselves :erg:, and then again, when the loader copies them to the correct place to play them? Unless, you're planning to try to run the mission from a custom folder (can that even be done)? Either the description, or the implementation, is not making sense. Again though, it might be me not getting what you're describing. The master ini record file belongs to the app, not the FM. The FM has its infos, but the Loader keeps track of all the FMs that are and have ever been installed for play. And yes, what is the point in a loader if it doesn't extract?
The folder structure for T3 can be a million layers deep - that doesn't change the fact that the job to be done to install an FM is basically the same in principle as it is for T1&2:
On selecting an FM archive:
1. Open an archive and get all the info
2. Write that info out to the master record file for the loader, and display it to the user
If the user wants to install:
1. Dump all files where they belong
2. In case of file collision, backup the original then overwrite it with the new
If the user wants to uninstall:
1. Blow away all assets from this mission (this information is stored in a database file)
2. Restore old versions which were overwritten
I don't understand the contention here.
OrbWeaver on 23/3/2005 at 21:21
Quote Posted by dracflamloc
I do appreciate the feedback guys, despite how annoyed I may sound sometimes. I just prefer to code as opposed to arguing over design decisions. I'd rather feedback about bugs you find or maybe interface tweaks, etc...
From reading these forums you should know that design decisions will always be the most contentious part of any software product. Just do a search for "loot glint"...
dracflamloc on 23/3/2005 at 21:33
Quote Posted by SneaksieDave
I must not be getting what you're saying. So, the files are on the hard drive twice? Once, in the folder we created ourselves, when we extracted it ourselves :erg:, and then again, when the loader copies them to the correct place to play them? Unless, you're planning to try to run the mission from a custom folder (can that even be done)? Either the description, or the implementation, is not making sense. Again though, it might be me not getting what you're describing. The master ini record file belongs to the app, not the FM. The FM has its infos, but the Loader keeps track of all the FMs that are and have ever been installed for play. And yes, what is the point in a loader if it doesn't extract?
Okay look. I won't bother explaining. Everyone here is just confusing themselves. In a nutshell... AGAIN:
You download a zip with the mission and fmi.
You extract it to your FM folder. (or maybe the loader does it automatically later on)
You run the loader and activate whatever mission you want to play.
The loader deploys the files where they need to go.
You do not have two copies on your harddrive except for the active one.
If you still dont get it theres nothing I can do but say wait and see. It'll be fine.
ZylonBane on 23/3/2005 at 21:33
Quote Posted by dracflamloc
Theres no need. To be a "compliant archive" it just needs to be a zip file that has the Thief3 Directory structure necessary to play the FM.
That archive is then put in another archive with the fmi file. Thats all there is to it.
So when FleshLoader is displaying the list of FMs, it has to pull the title info from every individual ZIP file every time it runs, instead of from a consolidated database?
