Home | Reviews | GUIpedia | Forum | Fun500


jasonwoodlandNext Navaska
I'm starting Navaska, AGAIN. I've added some things to the list that I will share. I will write a compiler, not like GIMIs though, lol. While its compiling it will convert strings to numbers, like EXEs, im all for speed B) Please may I have suggestions towards programs, styles for the client-server guis, icon themes? It will be much appreciated. Program list i already have: Abacus - like ms calc Pro Suite - from old Cobra 2K9 WordPro - like ms word - improved from Cobra 2K9 EncorePro - like ms powerpoint PixelPerfect - like any old icon editor **may i please have a name** - edits colors, contrast, etc.. i'll update when i need to update :laugh:
2010-01-298:34 PM

BrandonRe:Next Navaska
You don't really have any games in the list, a game or two is aways nice.
2010-01-308:13 AM

jasonwoodlandRe:Next Navaska
got any suggestions?
2010-01-306:10 PM

BrandonRe:Next Navaska
Yeah a game or two :P
2010-01-306:51 PM

jasonwoodlandRe:Next Navaska
any suggestions for a game? or two?
2010-01-307:19 PM

pharoahRe:Next Navaska
How about this, it's simple and kind of fun: http://www.labpixies.com/gadget_page.php?id=10
2010-01-3010:15 PM

jasonwoodlandRe:Next Navaska
Yeah, that looks awesome, easy enough for my lang too B) Does anyone know a good fill technique, like the one in paint, or gimp? not the paint in QBasic, im using future.
2010-01-3010:49 PM

agumaRe:Next Navaska
thats what she said...lolz
2010-01-3112:16 AM

jasonwoodlandRe:Next Navaska
yarr :angry:
2010-01-311:06 AM

jasonwoodlandRe:Next Navaska
finished te compiler now B) works well, makes files bigger :ohmy: :huh: :dry: :S :laugh: i had mixed emotions
2010-02-041:09 AM

BrandonRe:Next Navaska
Compiling shouldn't make the file bigger! More optimal files should be smaller.
2010-02-0411:01 AM

pharoahRe:Next Navaska
Compiling always makes your files bigger, Brandon. It turns an instruction like LINE into a whole mess of included machine code and a subroutine call. As the instructions go from abstract to more clearly defined, granular steps, there will be more steps. Compiling is "optimal" because it runs faster since all the steps are already spelled out, not because it makes for smaller file sizes.
2010-02-0412:02 PM

BrandonRe:Next Navaska
I see, I would have expected a smaller file because things like PRINT "TEXT" could be something like 1,"text" but I suppose that converting to binary would be larger
2010-02-041:33 PM

bongomenoRe:Next Navaska
Just to throw out an idea... One thing I rarely see in a GUI is the ability to program/create applications for the GUI - within the GUI. By this I mean It would be cool if I could write code in you language while actually using the GUI using its text editor or something. If not then something like a tinybasic interpreter would be cool. A command prompt style thinggy would be nice as well. The ability to manage files is important as well, so if your GUI cant already manage files via the desktop or something, an 'explorer' type program would be useful.
2010-02-049:22 PM

jasonwoodlandRe:Next Navaska
Thankyou pharoah, i guess i could replace print,@,hello with 23,@,hello. To bongomeno, thankyou and sure! i'll be honored to see someone using my language, its much like XGUIs syntax. but instead of left a$,b$+c$,10 it would have to be left a$, b$ + c$, 10. this is because i use opperators xor, or, and etc... its gonna have tonnes of documentation so i'll send a copy when im done :)
2010-02-0512:05 AM

SonicBritRe:Next Navaska
Ok so heres a paint fill routine, its slow under qbasic, (its based on some code I wrote back in the 90's, I even wrote an asm version, but sadly I dont have a copy of that), I can rewrite it into asm if need be. You may need to run it a few times to get a fill (hehe) for how it works I think its one of the nicer fill routines :) [code] DECLARE SUB fill (x AS INTEGER, y AS INTEGER, c AS INTEGER) SCREEN 12 RANDOMIZE TIMER FOR tmp = 1 TO 20 LINE (RND(1) * 320, RND(1) * 240)-(RND(1) * 640, RND(1) * 480), 15 NEXT CALL fill(320, 240, 3) SUB fill (x AS INTEGER, y AS INTEGER, c AS INTEGER) DIM sx(2, 320) AS INTEGER DIM sy(2, 320) AS INTEGER DIM max(2) AS INTEGER cur = 1 nextcur = 2 max(cur) = 1 s = POINT(x, y) sx(1, 1) = x sy(1, 1) = y WHILE max(cur) > 0 max(nextcur) = 0 FOR tmp = 1 TO max(cur) x = sx(cur, tmp) y = sy(cur, tmp) oktop = 0 okbot = 0 startx = 0 FOR tmpx = x - 1 TO 0 STEP -1 IF POINT(tmpx, y) s THEN startx = tmpx + 1 EXIT FOR END IF IF POINT(tmpx, y - 1) = s THEN IF oktop = 0 THEN max(nextcur) = max(nextcur) + 1 sx(nextcur, max(nextcur)) = tmpx sy(nextcur, max(nextcur)) = y - 1 oktop = 1 END IF ELSE oktop = 0 END IF IF POINT(tmpx, y + 1) = s THEN IF okbot = 0 THEN max(nextcur) = max(nextcur) + 1 sx(nextcur, max(nextcur)) = tmpx sy(nextcur, max(nextcur)) = y + 1 okbot = 1 END IF ELSE okbot = 0 END IF NEXT oktop = 0 okbot = 0 endx = 639 FOR tmpx = x + 1 TO 639 IF POINT(tmpx, y) s THEN endx = tmpx - 1 EXIT FOR END IF IF POINT(tmpx, y - 1) = s THEN IF oktop = 0 THEN max(nextcur) = max(nextcur) + 1 sx(nextcur, max(nextcur)) = tmpx sy(nextcur, max(nextcur)) = y - 1 oktop = 1 END IF ELSE oktop = 0 END IF IF POINT(tmpx, y + 1) = s THEN IF okbot = 0 THEN max(nextcur) = max(nextcur) + 1 sx(nextcur, max(nextcur)) = tmpx sy(nextcur, max(nextcur)) = y + 1 okbot = 1 END IF ELSE okbot = 0 END IF NEXT LINE (startx, y)-(endx, y), c NEXT temp = nextcur nextcur = cur cur = temp WEND END SUB [/code]
2010-02-056:15 PM

pharoahRe:Next Navaska
If you're looking to create a decent, usable language, here are a few things that you absolutely need: - The ability to define functions and pass arguments to them otherwise nobody will be able to write anything useful - The ability to EITHER have variable scoping (so that you don't "run out" when you write function definitions) OR to use a stack for local variables, thus eliminating the problem - The ability to construct some kind of extensible data structure like an array - The ability to load and save data from within a script and, arguably - The ability to create an error handler within a script that will handle errors caused by that script and will get some information about the error type AND/OR something that reports where errors are found at runtime and what they are
2010-02-057:14 PM

jasonwoodlandRe:Next Navaska
Thankyou everyone for your help :) I really really appreciate all the help! I will rewrite the compiler again because i found a few bugs :silly: Now that school weekends have begun I think I will be able to do alot of work!
2010-02-057:26 PM

GUIs


2021 Brandon Cornell


Fatal error: Uncaught Error: Call to a member function close() on null in /homepages/11/d157582457/htdocs/mblog/footer.php:20 Stack trace: #0 /homepages/11/d157582457/htdocs/mblog/forum.php(88): include() #1 {main} thrown in /homepages/11/d157582457/htdocs/mblog/footer.php on line 20