I'm tellin ya, I'm stuck in an infinite loop with many nested loops and conditions.
A while back I spent a bunch of time making the radiant build menu work for q1 mapping (because it didn't). I even took it further and started exploiting the build menu in order to introduce more features (like my 32 point compass for sunlight).
Well, now I am building a thing that will eliminate that build menu. Let's follow my logic for a second.
in the beginning:
I wanted the radiant build menu to work because it is supposed to
now:
I want to make a way way better build menu then the one radiant provides us with.
Let's face it. The radiant build menu is total junk. It isn't user friendly in the least and it only knows as much about a quake compile as you tell it. The current alternative to this is a .bat file... BOOOOO! That is garbage too. I have a better way and I have figured out some things as well as remembered some things.
1) I remembered how to make standalone exe's in flash that do not need any form of installation of anything. Completely portable. This is important for a bunch of reasons. the alternative to my method is to use air but everyone that uses my build menus would have to install that, no good. If I went the straight flash method everyone that uses my build menu would have to have flash installed, they would also have to have a standalone player on their system because I can't invoke an swf in the way I need to without it. Browser flash will not work. None of that is any good. By remembering the lil projector trick though, there is no dependencies on anything.
Now here comes the real cool part. Flash is my thing. AS3 is my language and I've programming in it for a very long time. So now we get a radiant build menu in standalone exe form, with all of the visual and functional power of flash, programmed by a no-bullshit AS3 programmer.
Can you wait? I barely can.
I intend to use the exact same system for my QC editor compile menu. Then I intend other things but I've already told you way too much.
EDIT: hah, I never got to 2) lol...whatever I got shit to do. I've said plenty.
Quick quiz:
a) Do you think I am going to make you remember and type a bunch of stuff
or
b) Do you think I am going to organize every single possibility for every included compiler into an array of checkbox selections which, appear dynamically based on the support of the compiler while also providing features to save build profiles, open corresponding docs, and of course, build?
A while back I spent a bunch of time making the radiant build menu work for q1 mapping (because it didn't). I even took it further and started exploiting the build menu in order to introduce more features (like my 32 point compass for sunlight).
Well, now I am building a thing that will eliminate that build menu. Let's follow my logic for a second.
in the beginning:
I wanted the radiant build menu to work because it is supposed to
now:
I want to make a way way better build menu then the one radiant provides us with.
Let's face it. The radiant build menu is total junk. It isn't user friendly in the least and it only knows as much about a quake compile as you tell it. The current alternative to this is a .bat file... BOOOOO! That is garbage too. I have a better way and I have figured out some things as well as remembered some things.
1) I remembered how to make standalone exe's in flash that do not need any form of installation of anything. Completely portable. This is important for a bunch of reasons. the alternative to my method is to use air but everyone that uses my build menus would have to install that, no good. If I went the straight flash method everyone that uses my build menu would have to have flash installed, they would also have to have a standalone player on their system because I can't invoke an swf in the way I need to without it. Browser flash will not work. None of that is any good. By remembering the lil projector trick though, there is no dependencies on anything.
Now here comes the real cool part. Flash is my thing. AS3 is my language and I've programming in it for a very long time. So now we get a radiant build menu in standalone exe form, with all of the visual and functional power of flash, programmed by a no-bullshit AS3 programmer.
Can you wait? I barely can.
I intend to use the exact same system for my QC editor compile menu. Then I intend other things but I've already told you way too much.
EDIT: hah, I never got to 2) lol...whatever I got shit to do. I've said plenty.
Quick quiz:
a) Do you think I am going to make you remember and type a bunch of stuff
or
b) Do you think I am going to organize every single possibility for every included compiler into an array of checkbox selections which, appear dynamically based on the support of the compiler while also providing features to save build profiles, open corresponding docs, and of course, build?
Comment