Perhaps I should write a few tutorials, one on using the API in your programs and one on adding routines/internal structure of the API..?Timendus wrote:Just take a look at the template that the website generates when you try to add a routine. If you don't understand it, feel free to ask.Jim e wrote:I'm gonna try add things personally but could you give me quick rundown on precisely the format.
[Featured][Beta] API - Why hasn't this been done yet?!
Moderator: MaxCoderz Staff
That's the spirit
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
You think it's clear enough as it is? I guess it should be, but the community seems to be getting so spoiled with tutorials for every possible subject that people seem to forget how to figure things out for themselves
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
Well for me I have a little java in my background, just the basic really. So what your API does is you just call the routine (method in java) and set in the varibles if needed.Timendus wrote:You think it's clear enough as it is? I guess it should be, but the community seems to be getting so spoiled with tutorials for every possible subject that people seem to forget how to figure things out for themselves
Yup, very true. But I guess that could be confusing to people who've never worked with macro's and include files much before. And I need a place to write things down like preferred label naming, use of routines that you depend on, etc...
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
-
- Regular Member
- Posts: 82
- Joined: Sat 18 Jun, 2005 9:15 pm
- Contact:
-
- MCF Legend
- Posts: 1601
- Joined: Mon 20 Dec, 2004 8:45 am
- Location: Budapest, Absurdistan
- Contact:
Those who have trouble with registers will not be able to code in assembly, no matter how much help they get. It's like saying you've got 'problems with variables'. There are some things you simply can't avoid learning.
For those who don't get it, the API takes care of the mechanical part of programming by providing a simple invocation interface for various routines, partly romcalls. That's all. It will never encompass individual program logic.
For those who don't get it, the API takes care of the mechanical part of programming by providing a simple invocation interface for various routines, partly romcalls. That's all. It will never encompass individual program logic.
I'm afraid CoBB is right. It's not a new programming language, it's just a (rather large) set of routines that you'll always have handy when you include the API. Of course that's not my marketing speech, but I'm afraid it's true
The implications can be big though, because it also brings some standardization and abstraction in the process, but that's a boring story that you're not going to be interested in I think
Anyway, it certainly simplifies things for beginners, it helps advanced users to test and develop software faster, and it is actually pretty useful for people who want to write hybrid programs because all they'd have to do is link the routines they wish to use to some input and output OS vars. I know I wished I had something like this when I was still making hybrid programs, about 5 years ago So:
Edit: Nice, 600th post since the last forum wipe
The implications can be big though, because it also brings some standardization and abstraction in the process, but that's a boring story that you're not going to be interested in I think
Anyway, it certainly simplifies things for beginners, it helps advanced users to test and develop software faster, and it is actually pretty useful for people who want to write hybrid programs because all they'd have to do is link the routines they wish to use to some input and output OS vars. I know I wished I had something like this when I was still making hybrid programs, about 5 years ago So:
Yes, I think it could be. That depends on what you'd require your AI to do. Most AI's are a heap of complicated calculations and conditions though, and it's going to be a lot tuffer to do that in asm than in Basic.dragon__lance wrote:do u think API is a good choice for people that have no asm knoledge(like me) and want to have a asm/basic hybred prgm. For instance, the main prgm is in BASIC, but AI is made in asm so its faster.
Edit: Nice, 600th post since the last forum wipe
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
- Jim e
- Calc King
- Posts: 2457
- Joined: Sun 26 Dec, 2004 5:27 am
- Location: SXIOPO = Infinite lives for both players
- Contact:
I really like the idea behind a standard for graphics and such. It could make creating and using graphics easier.The implications can be big though, because it also brings some standardization and abstraction in the process, but that's a boring story that you're not going to be interested in I think Smile
Like sprites would also get width, height, method for drawing(or, xor, and, grey). Tiles would have something similar except only once since we assume that they are all alike. And maps could include dimensions, word size, masked indicator bits, and compression used. Maybe we could come to a consensus on this and try to get others to support it, like early morning.
why would you want to? It wouldn't be worth it.necro wrote:yay Jim! Realy quick question, can a hook be triggered inside of a asm program...as in can you use xlib real statemnets in a asm prog?
@jim e: perhaps not for you, but can it none the less? One man's trash is another man's way of survival...
@timendus/cobb: err, sorry, wrong terming...I mean messing around with dozens of lines of code just to devide something, obviously there is a minimuim you must know (at least unless you did take it to the level of simplifying)
<off topic edit> browsing the api has helped my understnading a lot though, I think I'll try picking it up again over break.
@timendus/cobb: err, sorry, wrong terming...I mean messing around with dozens of lines of code just to devide something, obviously there is a minimuim you must know (at least unless you did take it to the level of simplifying)
<off topic edit> browsing the api has helped my understnading a lot though, I think I'll try picking it up again over break.
Well, we're working on that then, aren't we?necro wrote:@timendus/cobb: err, sorry, wrong terming...I mean messing around with dozens of lines of code just to devide something, obviously there is a minimuim you must know (at least unless you did take it to the level of simplifying)
Hey, that's actually a really good idea So do you suggest that all the data is put in the sprites, and have only one sprite/mappingroutine that autodetects what it should do? That way designing grapical programs would almost be just a matter of drawing the right tiles in EarlyMorning. It wouldn't be optimized for people who just want a xor routine for example thoughJim e wrote:I really like the idea behind a standard for graphics and such. It could make creating and using graphics easier.
Like sprites would also get width, height, method for drawing(or, xor, and, grey). Tiles would have something similar except only once since we assume that they are all alike. And maps could include dimensions, word size, masked indicator bits, and compression used. Maybe we could come to a consensus on this and try to get others to support it, like early morning.
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
- Jim e
- Calc King
- Posts: 2457
- Joined: Sun 26 Dec, 2004 5:27 am
- Location: SXIOPO = Infinite lives for both players
- Contact:
Sure if you just want to draw one sprite any old method this would be overkill...but if you actually intend to make something useful and/or pretty this maybe the best way to go. Let me see if I could code something useful.Timendus wrote:Hey, that's actually a really good idea So do you suggest that all the data is put in the sprites, and have only one sprite/mappingroutine that autodetects what it should do? That way designing grapical programs would almost be just a matter of drawing the right tiles in EarlyMorning. It wouldn't be optimized for people who just want a xor routine for example though
Also I'm noticing a problem, a routine I uploaded, mul16, isn't very useful in it's format. Since most people don't use constants, requiring to load register for every macro that uses inputs looks like it's gonna cause problems.
Nice additions Jim Thanks for taking the math stuff off my back
Anyone have some good ideas?
Yes, that's something I have no solution for. There are two ways to work around it; one is to use single registers and hl in the macros as much as possible, because you can load any other register in them. That way things like math.mul8(c,e) will work properly, but they can give redundant code. The other way is to have the user #define api_use_math_mul16, and call api_math_mul16 with the proper registers loaded, completely bypassing the macro...Jim e wrote:Also I'm noticing a problem, a routine I uploaded, mul16, isn't very useful in it's format. Since most people don't use constants, requiring to load register for every macro that uses inputs looks like it's gonna cause problems.
Anyone have some good ideas?
http://clap.timendus.com/ - The Calculator Link Alternative Protocol
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS
http://api.timendus.com/ - Make your life easier, leave the coding to the API
http://vera.timendus.com/ - The calc lover's OS