shawnleblanc wrote:
Where is Nesicide2 in terms of feature parity with Nesicide1?
The build and debug capabilities of Nesicide2 are far better than those of Nesicide1. Nesicide1 still used the in-built ASM6-like assembler written by myself.
Nesicide1's debugger was contained all in the same dialog and was cluttered! Nesicide2 splits the "debugger" into several (25+) dockable widgets that represent some aspect of the NES system: Breakpoints, Symbol watching, CPU execution trace (log and graphical view), CPU code/data graphical view, CPU disassembly view, CPU registers, CPU memory, PPU registers, PPU internal state, PPU OAM (binary and graphical view), PPU NameTable (binary and graphical view), PPU palette, APU registers, APU internal state, Cartridge mapper registers, Cartridge internal mapper state, Cartridge CHR viewer (binary and graphical view), Cartridge EXRAM memory, Cartridge SRAM memory.
Nesicide2 supports source-level debugging and symbol inspection; Nesicide1 did not.
Nesicide2 uses a Scintilla text editor component ported to Qt which is much more feature rich (margins, syntax highlighting, etc.) than the default text edit controls in MFC or Qt. Nesicide2 will soon support call-tips.
The emulator in Nesicide2 is far more accurate than the emulator in Nesicide1. However, the abundance of debug hooks has resulted in performance issues on some users machines. I don't know what Mac performance is like...
The project file format of Nesicide2 is XML-based and thus mostly human readable. The project file format of Nesicide1 is binary.
Nesicide2 does not (yet) have any of Nesicide1's "designers" ported over, stuff like the Palette Editor, Tile Editor, NameTable Editor, Music Tracker (this was only half working anyway). I've started down this porting path but have not made much progress. We'd been talking about a plugin interface to support whatever output formats people dream up.
At one point the plan was to port FamiTracker to Qt and bundle it with Nesicide2. That's still the plan but hasn't been worked.
I haven't maintained Nesicide1 since the switch from MFC to Qt (for Nesicide2).
In other words, Nesicide2 is superior even though it's currently lacking some of the Nesicide1 pieces.