I'm working on a simple NESDEV-homebrew-environment I'd like to show you guys. It's pretty basic and is currently aimed at smaller projects. I have alot more tweaks to do and is still pretty early in development but I'm getting pretty proud of it.
It's basically a frontend for a command-line assembler (currently DASM).
When you start the program you can create a new project. You currently select from templates depending on what kind of project (PRG-size, mirroring etc.) and a new main-assemblyfile is created based on your settings.
A unique thing is that you work with alot of different files instead of one massive .asm file (or perhaps a few includes-aswell).
One subroutine = one file.
To the right in the GUI, there's a list of all available subroutines. Clicking on them immediately brings you to it. Hovering the list also brings you a tooltip for each subroutine (which could be: "Clear RAM, uses X and A" for example).
All these subroutines are then linked when compiled.
The GUI is a little bit intelligent and it's checking for a newer version on disk when you want to edit a specific subroutine (all subroutines are loaded to memory when you open an existing project).
It's designed with Dropbox in mind. Imagine having your friend remotely coding new subroutines and you get them instantly visible in your project.
Check out the (super-early-alfa)-screenshot below. What do you think of my ideas?
[/img]
It's basically a frontend for a command-line assembler (currently DASM).
When you start the program you can create a new project. You currently select from templates depending on what kind of project (PRG-size, mirroring etc.) and a new main-assemblyfile is created based on your settings.
A unique thing is that you work with alot of different files instead of one massive .asm file (or perhaps a few includes-aswell).
One subroutine = one file.
To the right in the GUI, there's a list of all available subroutines. Clicking on them immediately brings you to it. Hovering the list also brings you a tooltip for each subroutine (which could be: "Clear RAM, uses X and A" for example).
All these subroutines are then linked when compiled.
The GUI is a little bit intelligent and it's checking for a newer version on disk when you want to edit a specific subroutine (all subroutines are loaded to memory when you open an existing project).
It's designed with Dropbox in mind. Imagine having your friend remotely coding new subroutines and you get them instantly visible in your project.
Check out the (super-early-alfa)-screenshot below. What do you think of my ideas?
[/img]