- If the user tries to execute source code, automatically compile the program if it has not yet been compiled. (Or ask the user)
basically, a Compile+Run option

But ... I already did it look carefully at the fourth tab when I'm switching views

-You can store source code to appvars and still be able to compile them

Why not

Hi guys !  Using Axe (both the language and the app) and ASM, I'm making something looking like a shell, but specialized in Axe programming !

It searches through the VAT for Axe sources, displays them and provides several functions and informations on them : you can lock sources, so people can't edit them ; you can delete sources ; it displays if the source is locked or not, its size, the output program, and most of all ...

You can open the Axe app, enable Axe token hook and compile sources directly from the shell ! (yeah, these aren't Axe but ASM ) And you also can compile sources in Noshell without opening the Axe app

The program also recognizes libraries (programs starting with two dots), making them impossible to compile

The program isn't finished at all, I planned to add more functionalities like hiding sources, launch an executable program resulting of a compilation just by clicking on his source ...  Here is a list of available functionalities :

• 17/09/2012
•       Main menu
•       Axe app opens from the shell
•       Compilation of an input from the shell
•       Token hook enabling from the shell
• 18/09/2012
•       Updated ! Direct compilation of the selected program
•       Complete listing of Axe sources, including libraries
•       Detects libraries and make them non-compilable
•       Source locking
•       Source deleting
•       Source size display
•       Output name display
•       Lock state display
• 19/09/2012
•       Switch between sources and executables views !
•       Run a nostub ASM program from the shell ! The "Run" command replace the "Comp" one in executable view.

And here is the latest screenshot (I'll update it with the program) :



The logo is quite ugly, but it's only for me having the shapes for text, I'll update it later.

Hi all !

As you maybe know, I'm working on porting DoorsCS7 GUI API to Axe programming (see the topic here), and with the current progress, I had the idea to do a proof concept program

So, here is PassWord, the first Axe program using the DCS7 GUI API !



You don't see it on the screenshot, but the screen turns off each time the GUI is drawn ? when launching the prgm and when you type a wrong password ; it explains the delay when I run the prgm and when I close the alert.

I'll release the axiom when I had documented it (I'm discussing it with KermMartian).

If you have any question on how the program works, feel free to ask me

Executable : http://mattias.refeyton.fr/espace-ti/AxeDCS/PASSWORD.8xp

The current password is 9001. You can't modify it yet because you can't compile the source without the axiom

Update !

Now I have a bunch of widgets (and funcs) that you can use for your GUI using DCS ! Just check it out :

Ho waw, it's working \o/ but you'll have to explain it slowly

Hi guys !

I finally aborted AxiomGui to work on another project : add DCS GUI funcs to Axe. I know that several people tried to do this, but it never ended, so I try myself too.

For now, I only have one command, and it's not working properly -_-' So I also need help for this one (it's mostly due to Axe replacements, I think).

Here is the actual code (I'm using Mimas) :dw $C0DE

; Alert(
; Displays a modal msg box with custom text

dw AlertEnd+2                       ; I use REP_NEXT twice
db %00001000                      ; only for DoorsCS
db $BB,$1B                            ; normalpdf(
db 0                                       ; inline
db 1                                       ; 1 arg

rorg 0
 push hl
 inc hl
 inc hl
 inc hl
 call sub_Length
 ex de,hl
 push de
 call OpenGUIStack

 REP_NEXT                            ; db $7F \ rorg $-1

 ld hl,SmallWin
 ld de,WinButtons-SmallWin
 ld a,GUIRSmallWin
 call PushGUIStack
 
 REP_NEXT

 ld hl,WinButtons
 ld de,AlertEnd-WinButtons
 ld a,GUIRWinButtons
 call PushGUIStack
 
 pop de
 pop hl
 inc de
 inc de
 inc de
 ld a,GUIRText
 call PushGUIStack

 ld hl,0
 call GUIMouse
 ret

exitAx1:
 call ResetAppPage
 ret

SmallWin:
db 7,7
db $E0,$B0,$90,$90,$F0
db " ",0

WinButtons:
db %00100000
dw 0
dw 0
dw exitAx1

AlertEnd:

dw 0                                     ; AXM_END

; token hook
dw $03E0                             ; hnormalpdf
db 6
db "Alert("
The only arg of this func is a data containing a GUIRText datas ::.AXEDCS
:#Axiom(AXIOMDCS)
:Data(0,0,0)"Bonjour"→GDB1
:Alert(GDB1

Here is a screen of it running :



Once the mouse freezed, I resetted manually Wabbitemu ; on my real calc it freezes, and that's all.

If someone can help me ..?

Yeah, I know the method, but I don't see how to apply it maybe I'll do it, but much later, since there are many widgets simpler to code (and mostly I still haven't done the mouse() command )