MaxCoderz

dysfunction wrote:

CoBB wrote:Has anyone thought of integrating an assembler into PTI? I've been playing with the thought myself. Just imagine, the whole building cycle would consist of nothing but sending your main source file to the emulator. No stupid dependencies and directory structures or whatever, just a single independent standalone taking care of everything. Mmmm...

Do you mean the ability to just hit "Build" then "Run" and it sends your file straight to PTI (with Ion or Mirage if they are dependencies) and executes it? Because that would be awesome. Perhaps such a thing could be integrated into Latenite?

I think you should just drop your source into the PTI window and have at it.

Yeah, even better.

That's what I thought you guys meant.

that would be cool, ETP studio for 68k calcs has this I think. I dunno if TIGCC has this feature tho

dysfunction wrote:Do you mean the ability to just hit "Build" then "Run" and it sends your file straight to PTI (with Ion or Mirage if they are dependencies) and executes it? Because that would be awesome. Perhaps such a thing could be integrated into Latenite?

It already does that. I haven't released it yet, though, as I was hoping to get breakpoints operating correctly (which I haven't managed). Maybe I'll package up a basic, incomplete non-debugging version in the meanwhile to show that I am actually working on it.

How soon can we expect that ben?

I've gotten to an assembler version that is pretty much complete. Decent errors, clearer list files than TASM, in my opinion, and pretty nice mnemonic sorting. Opcode searching is always a bit tedious -- take LD A,* for example. Here's an excerpt from the stat file generated from page one of Zelda:Even though the LDs with numeric args are much more common, all of the other symbolic LDs must be searched first, since they fulfill the requirements for the * wildcard, yet are distinct commands. This is the reason behind the longstanding bug in TASM where this occurs:TASM takes a little shortcut where it ignores internal parenthesis when searching. The search order, defined by the table file was a,(*) then a,*, so line one's result was a,(*). Had a,* been first, all a,(*) commands would be lumped into it -- complete chaos and loss of the use of a,(*). Though table order is still important for my assembler, the +0 at the end is no longer necessary since internal parenthesis are noted.Cool, huh?

Very nice indeed. If these new assemblers had of been written 25 years ago, you could have been in some serious bu$$iness .

So when can we expect a realese date?

How much percentage of work is done so far?

Now that Zelda assembles instantly, development's a lot easier. How long it'll take to finish depends on how long of game it needs to be! Right now there is certainly enough to release, more than any other Zelda attempt (granted, mine's the first APP version). But I'd like to make it a bit longer than forty minutes.

I'll release the assembler to whomever is tired of waiting for slow assemblies. (It should be entirely compatible with TASM, except for my interpretation of .org being very different -- imo you write null bytes to the IP with .fill or .block, not with .org). Recently I added support into the #include preprocess for binary and bitmap files. It'll figure out file type. This is beneficial since reading straight from a bitmap or binary is faster than parsing text data. However, I don't have any plans for supporting grayscale or compression, since that depends on the programmer's implementation.

How 'bout a demo with some random map from another zelda? Zelda's Link Awakening maybe...

Spencer wrote:Now that Zelda assembles instantly, development's a lot easier. How long it'll take to finish depends on how long of game it needs to be! Right now there is certainly enough to release, more than any other Zelda attempt (granted, mine's the first APP version). But I'd like to make it a bit longer than forty minutes.

You could release a public beta, or a demo. We're all waiting eagerly to try it out.

Spencer you take your time, we have been waiting for it and we can wait a little longer. It is great to hear that it's basically done, and I can't wait to try this out!

Have you implemented a way of creating multipaged apps without relying on a batch to make all the passes?

Please don't release a demo, make these guys wait, be the tease that you are and stick to screenies.