This is an archived, read-only copy of the United-TI subforum , including posts and topic from May 2003 to April 2012. If you would like to discuss any of the topics in this forum, you can visit Cemetech's Your Projects subforum. Some of these topics may also be directly-linked to active Cemetech topics. If you are a Cemetech member with a linked United-TI account, you can link United-TI topics here with your current Cemetech topics.

This forum is locked: you cannot post, reply to, or edit topics. Project Ideas/Start New Projects => Your Projects
Author Message
WikiGuru
ADOS (Attention deficit... Oh! Shiny!)


Elite


Joined: 15 Sep 2005
Posts: 923

Posted: 15 Oct 2006 09:20:24 am    Post subject:

old stuff wrote:
I'm starting a project to document all the TI-83+ rom calls to .xml format. Any help would be appreciated. If you wish to help, please post the rom call here in this format:

Group:                           ;(so I know where to put it)
        <item highlight="Function Name" colour="routine" name="Function Name" description="Description of What Function Does">
         <input name="Registers: Register Inputs" />
         <input name="flags: Flag Inputs" />
         <input name="Other: Other Inputs" />
            <output name="Registers: Register Outputs" />
            <output name="Flags: Flag Outputs" />
            <output name="Other: Other Outputs" />
            <output name="Registers Destroyed: Registers destroyed by calling this function " />
        </item>
All the xml stuff is so I can just easily copy it over. Please get your info from "TI-83 Plus System Routines".


Edit:

below is where all the finished rom calls will be posted.


Last edited by Guest on 05 Nov 2006 02:13:26 pm; edited 1 time in total
Back to top
Fallen Ghost


Elite


Joined: 15 Jun 2006
Posts: 955

Posted: 15 Oct 2006 12:30:03 pm    Post subject:

Isn't WikiTI already having that?

Or 83psysroutine.pdf?


Last edited by Guest on 15 Oct 2006 12:30:45 pm; edited 1 time in total
Back to top
WikiGuru
ADOS (Attention deficit... Oh! Shiny!)


Elite


Joined: 15 Sep 2005
Posts: 923

Posted: 16 Oct 2006 12:06:30 pm    Post subject:

Fallen Ghost wrote:
Isn't WikiTI already having that?

Or 83psysroutine.pdf?


I'm trying to document Rom Calls in an XML format so that I can quickly access them by pressing 'F1' while using LateNite.

Oops... that might take a long time.

Instead, what I'm trying to do now is finding a format that can be easily converted from a .txt file (I've got all the text from 83psysroutine.pdf) to fit into the right format for LateNite.

The format above I guess doesn't work, so what I want now is a format (if you know how to write help files for LateNite) that can make it easy to read and includes all (or almost all) of the info that is present for each rom call in 83psysroutine.pdf


Last edited by Guest on 16 Oct 2006 12:10:18 pm; edited 1 time in total
Back to top
WikiGuru
ADOS (Attention deficit... Oh! Shiny!)


Elite


Joined: 15 Sep 2005
Posts: 923

Posted: 30 Oct 2006 08:14:32 pm    Post subject:

Here's the first part. I can't seem to figure out why it screws up when you click on 'see also: ...', though. It displays some weird text instead of what it should be. If some one can help me fix this, that would be great. Also please check for errors, as I did write a program to create this file, so there must be more errors (besides bad formating). Another thing is that I need a better way to organize the groups (instead of having all the functions grouped into ~18 different groups).

So, without further delay...

Tada!
Back to top
Fallen Ghost


Elite


Joined: 15 Jun 2006
Posts: 955

Posted: 31 Oct 2006 06:24:56 am    Post subject:

Really looks good... If it helps you, why not?
Back to top
sgm


Calc Guru


Joined: 04 Sep 2003
Posts: 1265

Posted: 31 Oct 2006 01:34:26 pm    Post subject:

I'm not a fan of the structure. In fact, I think it downright sucks. For one thing, I don't see why you would have one tag for input descriptions but two for outputs. And then there's the putting of descriptive text in attributes (!).

I would do it something more along these lines:


Code:
<helpfile>
    <title>TI-83+ Display ROM Calls</title>
    <group>
        <title>Display Function</title>
        <routine>
            <title>_Bit_VertSplit</title>
            <highlight color="routine">_Bit_VertSplit</highlight>
            <description>Tests if the TI-83 Plus is set to G-T (graph-table)
            display mode.</description>
            <input>
                <entry>
                    <title>Registers</title>
                    <itemlist></itemlist>
                </entry>
                <entry>
                    <title>Flags</title>
                    <itemlist></itemlist>
                </entry>
                <entry>
                    <title>Other</title>
                    <itemlist></itemlist>
                </entry>
            </input>
            <output>
                <entry>
                    <title>Registers</title>
                    <itemlist></itemlist>
                </entry>
                <entry>
                    <title>Flags</title>
                    <itemlist>
                        <item>
                            <entity type="flag">Z</entity>
                            <description>= 0 if G-T mode is set.</description>
                        </item>
                    </itemlist>
                </entry>
                <entry>
                    <title>Registers Destroyed</title>
                    <itemlist></itemlist>
                </entry>
                <entry>
                    <title>RAM used</title>
                    <itemlist></itemlist>
                </entry>
            </output>
            <note>
                <para>Applications may want to reset the 83+ to full
                screen mode if graphing functionality is used. In G-T mode the
                screen is split vertically with 1/2 being the graph screen and
                the other the table display.</para>
            </note>
            <example>
                <programlisting>
bcall(_Bit_VertSplit); test for G-T mode
JR NZ,Screen_is_Split; jump if G-T mode
                </programlisting>
            </example>
        </routine>
    </group>
</helpfile>


(haha, except for me everyone in this thread has a similar avatar.)


Last edited by Guest on 31 Oct 2006 01:39:09 pm; edited 1 time in total
Back to top
Weregoose
Authentic INTJ


Super Elite (Last Title)


Joined: 25 Nov 2004
Posts: 3976

Posted: 31 Oct 2006 03:22:24 pm    Post subject:

Sigma's reply shares the same thoughts I had when I saw that code.
It's rather handy to have someone else raise the bar, so be thankful. Wink


Last edited by Guest on 31 Oct 2006 03:44:54 pm; edited 1 time in total
Back to top
Fallen Ghost


Elite


Joined: 15 Jun 2006
Posts: 955

Posted: 31 Oct 2006 08:07:19 pm    Post subject:

sigma wrote:
I'm not a fan of the structure. In fact, I think it downright sucks. For one thing, I don't see why you would have one tag for input descriptions but two for outputs. And then there's the putting of descriptive text in attributes (!).

(haha, except for me everyone in this thread has a similar avatar.)
[post="90464"]<{POST_SNAPBACK}>[/post]


I'm no fan at all of this XML structure. In fact, each time something pops out in that format I tend to close it immediately. But if it looks good for him, then good, I'll let him have fun. I prefer the old Win.pdf/Wiki format. Also, maybe some notes or comments like in WikiTI (added to what the pdf includes). Also, there are some Undocumented ones documented, which could prove useful sometimes (ExecuteApps, DeleteApps, and other ones not related to Apps).

What's the problem with turbo-prop planes avatar?
Back to top
benryves


Active Member


Joined: 23 Feb 2006
Posts: 564

Posted: 01 Nov 2006 06:55:57 am    Post subject:

The structure needs to be so convoluted as that how Latenite expects to read them.

That said, I'm not sure why there are two elements for inputs/outputs... here's a snippet from the MirageOS one:


Code:
<item name="multhe" highlight="multhe" colour="routine" description="Multiplies h*e quickly.">
    <input name="First operand" register="h" />
    <input name="Second operand" register="e" />
    <output name="Result (h*e)" register="hl" />
</item>


The new version of Latenite will take a rather different approach to all this, with a much-improved document browser. Syntax highlighting will be done via the assembler (and hence any labels declared in include files will be automatically highlighted) and looking up a symbol will end up looking up and pointing you at the correct page in the official PDF.
Back to top
WikiGuru
ADOS (Attention deficit... Oh! Shiny!)


Elite


Joined: 15 Sep 2005
Posts: 923

Posted: 01 Nov 2006 04:54:04 pm    Post subject:

Is there some way to fix this error:


Code:
;press PutC (or any other function) in the 'see also'
;display:
lnh_PutC (or other function)


If you go to the function, the data is right & displays correctly, but for some reason the 'see also' section is screwed up. Is this a bug with LateNite, or am I just doing something wrong?

BTW, here's some more documented calls. I also need a better way to organize the groups (so you don't have ~50 different display functions in the 'see also' section :sick: ). If anyone has suggestions, pls tell me.


Last edited by Guest on 01 Nov 2006 05:14:09 pm; edited 1 time in total
Back to top
Display posts from previous:   
Register to Join the Conversation
Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.

» Go to Registration page
    »
» View previous topic :: View next topic  
Page 1 of 1 » All times are UTC - 5 Hours

 

Advertisement