### Author Topic: Solar89 SDK  (Read 25621 times)

0 Members and 1 Guest are viewing this topic.

#### TC01

• LV6 Super Member (Next: 500)
• Posts: 344
• Rating: +9/-0
##### Re: Solar89 SDK
« Reply #45 on: August 26, 2010, 10:16:41 am »
I think their ASCII code is available in ASM in 28 days near the end.

Nice to see new updates ^^ I also like how you can do programs for multiple calc models. It should make porting much easier.

Ah- found it. But it's not the ASCII code I need, it's the token code I need. The two are different. (ASCII characters are used as part of tokens, and some are tokens, but their codes won't necessarily match up).

And yeah, I'm looking forward to the Omnimaga downloads section. I'm also going to upload it to ticalc.org, of course, but I wanted to wait for that until I had all the 83+ tokens supported and there were no obvious bugs (but for that, I need other people to test it).

And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).

#### DJ Omnimaga

• Clacualters are teh gr33t
• CoT Emeritus
• LV15 Omnimagician (Next: --)
• Posts: 55931
• Rating: +3153/-232
• CodeWalrus founder & retired Omnimaga founder
##### Re: Solar89 SDK
« Reply #46 on: August 26, 2010, 04:15:18 pm »
Ah ok I see. I'm not sure how to help, then (I'm not tech savy when it comes to that stuff)
« Last Edit: August 26, 2010, 04:15:36 pm by DJ Omnimaga »

#### TC01

• LV6 Super Member (Next: 500)
• Posts: 344
• Rating: +9/-0
##### Re: Solar89 SDK
« Reply #47 on: August 26, 2010, 04:26:12 pm »
Well, the Omega symbol, the \$ symbol, and probably others of those hard-to-reach tokens are all documented on the Misc Tokens page on TI|BD.

I can't seem to find the arrow there, though. So if you want to help, you could put that token in a program, maybe format it like this (_ = the token):

Code: [Select]
:ARROW:_
And then just send it to a computer and upload it. Using a hex editor, I could look at it to see what the token code is.

I could do this myself if I had a z80 with a working link port, but even then I don't know how to access that token, so...

And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).

#### TC01

• LV6 Super Member (Next: 500)
• Posts: 344
• Rating: +9/-0
##### Re: Solar89 SDK
« Reply #48 on: September 08, 2010, 10:39:38 pm »
After some time (during which I've been busy, primarily with getting back to school...), another update. Window, finance, and graph format tokens have now been added. I just need to add the miscellaneous and the TI-84+ tokens (again, as defined by TI|BD, and then I'll release 0.3, which I plan on posting on ticalc.org as well.

Unfortunately, with such a large token file, the program will continue to get slower, which is why my goal for the version after that is to perform some optimizations. Slowness will be a result of three things:

-Parsing the token file (dependent on size of token file)
-My reverse-substring process to parse the input file (not dependent on token file size)
-Searching for a token in the collection of token infos (dependent on token file size).

I know I can make the first somewhat faster. The other two probably can be made faster, but I lack the knowledge to do it.

I've also decided I would like to eventually have the option to detokenize, to convert an *.8xp file into an *.89z file that can then be detokenized on the calculator. That gave me the idea for another project... with the assistance of X-Link and a z80 assembly program on the other end, it would become possible to use a 68k calculator to transfer z80 programs around! I don't think anything like this already exists- X-Link is the closest to it that I know of.

And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).

#### qazz42

• LV9 Veteran (Next: 1337)
• Posts: 1130
• Rating: +30/-12
• hiiiiiiiii
##### Re: Solar89 SDK
« Reply #49 on: September 08, 2010, 11:16:14 pm »
ok, it is official

this is really pushing me to get a TI-89T

you rock

(is Solar interprited or compiled?)

#### DJ Omnimaga

• Clacualters are teh gr33t
• CoT Emeritus
• LV15 Omnimagician (Next: --)
• Posts: 55931
• Rating: +3153/-232
• CodeWalrus founder & retired Omnimaga founder
##### Re: Solar89 SDK
« Reply #50 on: September 08, 2010, 11:41:33 pm »
I like the ideas you got. It would be nice with the help of X-Link if there was a converter. Would the converter be on the 89 or the 83+? In the later case, would it have to be something in Axe/ASM?

I'm glad this is still progressing, btw

#### TC01

• LV6 Super Member (Next: 500)
• Posts: 344
• Rating: +9/-0
##### Re: Solar89 SDK
« Reply #51 on: September 09, 2010, 08:04:14 am »
ok, it is official

this is really pushing me to get a TI-89T

you rock

(is Solar interprited or compiled?)

It's written in 68k C, so it's compiled.

I like the ideas you got. It would be nice with the help of X-Link if there was a converter. Would the converter be on the 89 or the 83+? In the later case, would it have to be something in Axe/ASM?

I'm glad this is still progressing, btw

Well, the converter from X-Link appvar to 83+ program would have to be on the 83+ because of the way X-Link works, and it would have to be either in Axe or Assembly.

And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).

#### DJ Omnimaga

• Clacualters are teh gr33t
• CoT Emeritus
• LV15 Omnimagician (Next: --)
• Posts: 55931
• Rating: +3153/-232
• CodeWalrus founder & retired Omnimaga founder
##### Re: Solar89 SDK
« Reply #52 on: September 09, 2010, 05:13:27 pm »
Well, due to the ability of Axe to manipulate data in memory, I guess it could very be possible to convert the 89 file to 83+ program format in Axe. Otherwise, ASM is another good option since it allows even more freedom

#### TC01

• LV6 Super Member (Next: 500)
• Posts: 344
• Rating: +9/-0
##### Re: Solar89 SDK
« Reply #53 on: September 12, 2010, 04:40:45 pm »
I've uploaded 0.21 to Cemetech and ticalc.org (will add it to Omnimaga once the database is fully operational!). This does not add the miscellaneous or the TI-84+ only tokens yet... I really didn't feel like doing that. And I realized that it made no sense to keep bloating the size of the token file before I did some optimizations, otherwise things would get really slow. I just wanted to release a version on ticalc.org, and decided to include what I had so far.

Won't be able to download until it goes through, of course, so attached is a zipped copy.

And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).

#### DJ Omnimaga

• Clacualters are teh gr33t
• CoT Emeritus
• LV15 Omnimagician (Next: --)
• Posts: 55931
• Rating: +3153/-232
• CodeWalrus founder & retired Omnimaga founder
##### Re: Solar89 SDK
« Reply #54 on: September 12, 2010, 04:58:26 pm »
Cool to see new version out

As for the special tokens, are you planning to add them in future versions or are they out of the question?

#### TC01

• LV6 Super Member (Next: 500)
• Posts: 344
• Rating: +9/-0
##### Re: Solar89 SDK
« Reply #55 on: September 12, 2010, 05:31:48 pm »
Cool to see new version out

As for the special tokens, are you planning to add them in future versions or are they out of the question?
Yeah, I'm going to add them (as I said, most are listed on Misc. Tokens). I just was too lazy to do it now.

« Last Edit: September 12, 2010, 05:33:37 pm by TC01 »

And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).

#### TC01

• LV6 Super Member (Next: 500)
• Posts: 344
• Rating: +9/-0
##### Re: Solar89 SDK
« Reply #56 on: September 27, 2010, 07:34:47 pm »
So, another update. I've gotten the "compiled token files" working. The interface for the seperate program is shown in the screenshot.

I decided it might be a good idea to define the file type in each token file (that's what "File type" is), so a file compiled for, say, the 85 could say "85P" in the VAR-LINK menu instead of 8XP. But I haven't implemented that in code yet.

This causes token initialization times to be near instantaneous- under a second. The downside? The size of a compiled token file is about double the size of the text file. So I left the code to parse text files in Solar89, giving users a choice between the larger and faster files or the slower and smaller files.

The actual tokenization process is still slow- hopefully that can be rectified with additional optimizations.

And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).

#### DJ Omnimaga

• Clacualters are teh gr33t
• CoT Emeritus
• LV15 Omnimagician (Next: --)
• Posts: 55931
• Rating: +3153/-232
• CodeWalrus founder & retired Omnimaga founder
##### Re: Solar89 SDK
« Reply #57 on: September 27, 2010, 09:28:33 pm »
nice update! In the VAR-LINK menu will the 85P part be .85P at the end of the program or just be part of the file name, not the extension? I'm glad this is still progressing

I wonder if this will make it much easier to port games accross calcs?

#### TC01

• LV6 Super Member (Next: 500)
• Posts: 344
• Rating: +9/-0
##### Re: Solar89 SDK
« Reply #58 on: September 27, 2010, 09:59:05 pm »
nice update! In the VAR-LINK menu will the 85P part be .85P at the end of the program or just be part of the file name, not the extension? I'm glad this is still progressing

I wonder if this will make it much easier to port games accross calcs?

It will be the text in the second column- that says ASM, PRGM, TEXT, EXPR, STR, MATR, etc. I'm calling that the extension- not sure exactly what the technical term is.

Porting eventually might become easier using Solar89, but I'll need to write some other tools first (like an on-calc detokenizer and an on-comp 8xp-89y converter, not to mention a complete set of token files).

And in addition to calculator (and Python!) stuff, I mod Civilization 4 (frequently with Python).

#### DJ Omnimaga

• Clacualters are teh gr33t
• CoT Emeritus
• LV15 Omnimagician (Next: --)
• Posts: 55931
• Rating: +3153/-232
• CodeWalrus founder & retired Omnimaga founder
##### Re: Solar89 SDK
« Reply #59 on: September 27, 2010, 10:45:18 pm »
Ah ok, I guess it would be the extension then, or file type.