Maybe it's just me, but i feel like you need a bit more detail before I could actually answer, it seems a bit ambiguous... But to answer your question, probably, yes.

There is no "code editor inside of the app." People writing Axe programs use the usual TI-BASIC editor (the one you get when you press PRGM and go to EDIT or NEW).

I don't know what you mean by "write out the commands," but here's a quick rundown of the types of variables Axe uses:

• Source - program
  
  All Axe projects have a source program (the program with the code in it). These are what Axe looks for when it lists out the projects when compiling.
  
  You can edit source programs in the TI-BASIC editor.
  
  
• Library - program
  
  Source programs can include code from libraries with the prgm token. It basically works like #include in C or import in other languages, if you know what either of those mean.
  
  You can edit libraries in the TI-BASIC editor. Libraries work like source programs except that they can't be compiled on their own—they need to be included into the source program.
  
  
• Axiom - appvar
  
  Axioms are like extensions to the Axe language written in assembly. They're like libraries but in assembly instead of Axe language.
  
  You can't edit them with the TI-BASIC editor because they're assembly code (they're made for Axe, not with Axe).
  
  
• Backup - appvar
  
  Backups are just archived appvar copies of Axe source programs. You can create, restore, and delete them from the Axe Parser app.
  
  
• Executable - program
  
  The executable is what the user actually runs. It's the program produced by compiling a source program, and it's what people publish for others to download.
  
  You can't edit executables, and there's no way to get the original source or library programs used from them.

See Documentation.pdf in the Axe download for more info.

Zedd is a library—you can just get the 8XP files from the download and open the programs in the TI-BASIC editor.

Does that answer your question?

XDE didn't "have" a code editor—it was (supposed to be) a code editor and nothing else.

You can make editors just like anything else in Axe.

the commands ARE put in an appvar, but only for program backups, like he said. the programs that axe compiles are, and have to be, completely in the BASIC program format, with the exception of code inserted from axiom libraries.

Forgive me for putting you through all this trouble. I was was experimenting with an idea I had in my head and I just wanted to know if it was possible. Sorry.

^{*Yes, assembly programmers can come up with dozens of ways to get around that. None of them will integrate cleanly with Axe.}

That honestly stopped me from writing like 5 different examples he could use. But I agree with DrDnar, you'll have to call external programs.



But the real reason I'm posting is to clarify his question. I'm fairly certain he wants to use an appVar like a .dll. Basically, he wants so be able to use runtime libraries to that he can simply call them at will from his program.

So, to answer that question, no, you can't easily do that, and here's why:

• Where the appvars are stored, they are not executable
• The appvar would have to be pulled out of flash and stuck in ram (this is similar to what simply running it does)
• To be able to call the right routine in the appvar would absolutely require asm (and a lot of code counting)

While a runtime library axiom could in theory be created, you're best just to use libraries that go into the compiler (or just copy/paste the code). Also, you'll notice that in the past, all runtime libraries on the 84+ have been apps (xLib, Mirage, Doors, Celtic3) because apps can execute in place.

thanks you all for your responses. and the penguin77, yes that was what I was thinking about but I couldn't think of a decent explanation atm. what if instead the dll was inside of the app instead of it being an external var, would that be possible? or would I need asm for that as well?