Home | Reviews | GUIpedia | Forum | Fun500

MPNQBEXEs a bad idea for GUI programs
I will never use DOS MZ executables for my GUI's applications. Why are EXEs a bad idea to use for your GUI's applications? Simple. EXEs cannot be multitasked. At least not unless you know the format inside and out and have an advanced knowledge of assembly. Because when you multitask EXEs, you need to give each their own "space". Each application's memory must be seperate from each other. This is NOT easy and has NOT been done in Qbasic before and it probably will never be. The only place for EXEs are the kernel and whatever modules you have. But not for the applications. I strongly suggest you use a scripter in your GUI for its applications. It takes a bit more time since you are essentially building a virtual machine in BASIC, but it's possible in a shorter timeframe and has been tested and worked.		2008-07-1010:10 AM
BrandonRe:EXEs a bad idea for GUI programs
Well, Todd seems to think hes up to the challenge, If he fails then I'll work on Fun500 4 with my new scripter.		2008-07-1010:35 AM
ToddRe:EXEs a bad idea for GUI programs
It's possible to multitask EXEs by providing a multitasking-capable framework library for the EXEs made in it. GOPOS had something like that and I think I might be able to emulate it.		2008-07-1010:46 AM
BrandonRe:EXEs a bad idea for GUI programs
LOL GOPOS cheaps and uses temp files on the HDD, I don't want to use my HDD as a SWAP area, thats what RAMs for!		2008-07-1011:28 AM
jasonwoodlandRe:EXEs a bad idea for GUI programs
So you're saying Cobra cheaps?:unsure:		2008-07-1011:30 AM
ToddRe:EXEs a bad idea for GUI programs
Okay then you tell me how to pass data from one EXE to another via RAM?		2008-07-1011:47 AM
BrandonRe:EXEs a bad idea for GUI programs
I assumed you had that covered. Weres that ASM guy?? Maybe he could help?		2008-07-1012:01 PM
ToddRe:EXEs a bad idea for GUI programs
If QB wasn't so over-simplified, I could probably find a way but ASM would be needed. RCX knows ASM. It's just with using SWAP files, it would be quicker and efficient. Think about it. How does a file lister generate a file list? It uses the "DIR" command to generate a list file and then reads the file and removes it when done.		2008-07-1012:07 PM
BrandonRe:EXEs a bad idea for GUI programs
You realise a GUI will most likely be run from a floppy, and If we make a Good GUI I will want to run it but I cannot burn up floppies! ASM is the only way, and the best way to do it! QBasic lets you have very little ram, with 8MB RAM in my 486 I should be able to run MANY APPS! Why waste it?		2008-07-1012:24 PM
ToddRe:EXEs a bad idea for GUI programs
But I mean there is no way to pass data from one EXE to another using RAM. QB erases the RAM it uses when a program is closed. C++ could do the job since you can set where you want data to be stored in RAM.		2008-07-1012:26 PM
BrandonRe:EXEs a bad idea for GUI programs
Well use FreeBASIC with a C library to do the dirty work?		2008-07-102:48 PM
ToddRe:EXEs a bad idea for GUI programs
FreeBASIC isn't great in DOS. Things I do in QB that I do in FB end up causing it to crash with a Segment Fault.		2008-07-103:52 PM
BrandonRe:EXEs a bad idea for GUI programs
Well freeBASIC is saving you time, all your apps would crash eventually. :P		2008-07-104:18 PM
ToddRe:EXEs a bad idea for GUI programs
Even the "Hello World" apps? :(		2008-07-104:38 PM
BrandonRe:EXEs a bad idea for GUI programs
Dude FreeBASIC isn't bad you just are lazy.		2008-07-104:40 PM
MPNQBRe:EXEs a bad idea for GUI programs
Since the merger of Neon, EnSpireMe Professional, and EnSpireMe I've used FreeBASIC in DOS. I was even able to port the Qbasic Future.Library window system over to FreeBASIC and it still worked. Ice will be in FreeBASIC as well. QB is kinda sorta dead to me, but I still may use it for another GUI I have in the idea pipeline. I was pondering something simple and floppy-based.		2008-07-109:02 PM
ToddRe:EXEs a bad idea for GUI programs
All I remember is compiling a program in FB and having it spit Segment Fault errors in my face. It converts BASIC to Assembly and it's not easy for it to convert the code to 100% carbon-copied Assembly.		2008-07-109:04 PM
BrandonRe:EXEs a bad idea for GUI programs
Well In my opinion the only GUI that challenges Fun500 is EnSpireMe, so Todd you gonna make a monster scripting GUI to beat us?		2008-07-109:14 PM
ToddRe:EXEs a bad idea for GUI programs
I don't know. Maybe...		2008-07-109:16 PM
BrandonRe:EXEs a bad idea for GUI programs
You couldn't even beat Fun500 GUI 2!		2008-07-109:21 PM
ToddRe:EXEs a bad idea for GUI programs
That's what you think, not the rest of us.		2008-07-109:22 PM
BrandonRe:EXEs a bad idea for GUI programs
LOL I challenge you to a code-off		2008-07-109:27 PM
ToddRe:EXEs a bad idea for GUI programs
What's the program then?		2008-07-109:29 PM
BrandonRe:EXEs a bad idea for GUI programs
Scripting GUI		2008-07-109:41 PM
MPNQBRe:EXEs a bad idea for GUI programs
[b]Brandon wrote:[/b] [quote]Well In my opinion the only GUI that challenges Fun500 is EnSpireMe...[/quote] Well, graphically it wouldn't. At least EnSpireMe version 0.5.0 will only be 256-color and lacks window transparency and other stuff I saw implemented in Fun500. In fact, the windows are still ENDAZe-like in appearance. I'm focusing more than anything currently on things under-the-hood. The last thing that gets done with any modern OS or GUI is appearance polish. Look at Windows 7: at this point it looks like Vista with loose ends and unfinished new features.		2008-07-109:42 PM
ToddRe:EXEs a bad idea for GUI programs
How did I guess?		2008-07-109:43 PM
rCXRe:EXEs a bad idea for GUI programs
[b]tlsuess wrote:[/b] [quote] Think about it. How does a file lister generate a file list? It uses the "DIR" command to generate a list file and then reads the file and removes it when done.[/quote] I think the DOS actually uses [url=http://lrs.uni-passau.de/support/doc/interrupt-57/RB-2902.HTM]int 21/AH=4E[/url] and [url=http://lrs.uni-passau.de/support/doc/interrupt-57/RB-2904.HTM]int 21 AH = 4F[/url] instead of generating a file. I've played arond with these before and they could probably be used to write a dir command. Of corse there's always the dir command in FreeBASIC. B) [b]mpnqb wrote:[/b] [quote] Simple. EXEs cannot be multitasked. At least not unless you know the format inside and out and have an advanced knowledge of assembly.[/quote] I knew someone who wrote a "multitasking" gui in using an EXE. He wrote a scripting language for it. To run two programs at a time he would run a line of code from one program and then run a line from the other one and so on...		2008-07-1010:55 PM
BrandonRe:EXEs a bad idea for GUI programs
My GUI does that.		2008-07-1010:59 PM
ToddRe:EXEs a bad idea for GUI programs
I mean in QB apps, people typically use "DIR" commands through the "SHELL" call. "INT 24 AH = 4F"? I need to brush up on my Assembly. I had a book that listed all the Assembly hardware command IDs and their descriptions. So essentially the guy ran programs like TSRs?		2008-07-1011:01 PM

GUIs

2021 Brandon Cornell