This is the goodies download central for form@fix 0.2 F.
This software is beta, under construction. The value is in running the new examples.
One glaring omission of this beta is that, the \f facility, that is, forming, of "form"@fix is temporarily off.
Note that, by using form@fix, you are consenting that,
FIX.EXE (WHETHER FOR MSDOS, OR FOR WIN32), AND OTHER FILES/CONTENT FROM MID80.NET, IS/ARE PROVIDED AS IS, WITHOUT ANY GUARANTEES. THAT IS THE USER'S RESPONSIBILITY (AS WELL AS CHOICE) TO ENSURE CORRECT OPERATION (TO HIS/HER/THEIR SATISFACTION LEVEL), ON THE SET OF PROBLEMS HE/SHE/THEY MIGHT ENCOUNTER.
IN JURISDICTIONS, OR CONDITIONS, WHERE SUCH NOTICES LIKE THIS, WOULD STILL LEAVE THE (PUBLISHER/AUTHOR OF THIS) SOFTWARE/CONTENT LIABLE FOR ANY DAMAGES, OR IN ANY WAY, WOULD LET LITIGATION TO EXIST, PERMISSION FOR USE IS NOT GIVEN.
In other words, legally speaking, I am not taking any responsibility about your uses of form@fix.
You may still contact me, and I would like to help. But generally, form@fix is for my own usage, yet. Let me decide later, at some later releases, whether I would like to support some stronger claims of safety. Currently, for a byte-editing techie-tool, even this much of a "guarantee" may be too much. Instead, I should guarantee that, while tinkering with your own code, you would probably hang the system a few times.
For hacks targeting a specific platform, the include files may work well. The two, fixDX.htm (for crafting MSDOS .exe files), or fixWin.htm (for crafting Win32 .exe files), are there.
form@fix is a freeware, for personal as well as business purposes. Developing specifically for integrating into Media-tangle is not modifying the freeware status of form@fix. The togetherness is just inspiring the development path of form@fix, the needs of Media-tangle having the priority when I think what to code next.
For example, to allow a form@fix session to crash, is not permissible -- in the case of Media-tangle that may run hundreds of sessions (request/response) concurrently. Allowing single process that goes wrong, to crash all of a web server, is unlikely. While single, running as a hack-tool, that was no [big] problem. At worst, just terminating the session was all right. The person working with that would keep hacking, terminating, hacking.
Mainly, the trouble is in the cases of illegal pointers passed to frag, or wrongly-defined net. These resemble the well-known pointer-problems of C/C++. One has to bound-check the pointers, as well as reflect about all the data, to terminate the single session that is making the trouble.
The problem of form@fix is that you are expected to tell what, as well as where, your frag is, unlike the list of available frags of frozen@mid80, that I had coded as well as categorized.
I work toward getting rid of the problem both intensively, as well as extensively. Intensively, fortifying form@fix to reflect, to spot out all absurd pointers. Bounds-checks, & data-asserting.
Extensively/extensibly, by allowing the nets as XML files, designable by graphical external tools fashioned after frozen@mid80, or CroNoe75. Inputting external files, is getting rid of the false-pointer issues caused by careless users (the risk when hard-wiring the pointers, manually).
Trivial, but potentially tedious work-list, mostly.