Hi farrier
No worry. You ´ll get over it soon :t
Do I understand that dialog code would not be included in a RosAsm program? Only the digital data required for the .exe to display the graphics?
No...dialog is included in RosAsm. But, so far it is created with RosAsm itself internally (under rosasm resource editor), using CreateDialogIndirectParam. The dialogs are mapped from DLGTEMPLATE internally. I mean it don´t parse any rsrc file. The user creates his resources from RosAsm resources editor. So far, it can export/import a text and binary representation of the resources (bin or text DLGTEMPLATE data)
I´m working on a resource editor to alow parsing rsrc, res, dfm files as well (probably VB resources too, using a proper converter for VB files). Once i finish this new upgrade, RosAsm will be able to import and export rsrc/res/dfm or other types of resources files. (I plan to allow converting also from 16bit resources - I know, too old...But...i would like to see the resources inside the 16bit dlls inside winXP as well).
There are several updates i plan for RosAsm, but, now..i´m working almost alone (JE made good upgrades too, that i´l take a look after i upgrade some tools for the debugger)...But since i´m working pratically alone it will take a long time for me to implement all updates i have in mind like:
* New resources editor:
- New GUI editor for teh resource (I like the looks of visual studio resource editor. i`ll try to make it more similar to it)
- It will allow parsing and exporting rsrc, res and other resource files.
- It will create full windows apps (their skeletons at least) based on the resources
- Allow the edition of all windows resources types
- Allow exporting resource obj files
* Disassembler:
- Update some internall functions
- FInish the DIS system (Data identifying system). A sort of a digital DNA to identify functions based on teh original libraries
- Enable ability to import and export pdb, dbg files
* LibScanner
- Finish the libscanner enabling it to import and export all kind of lib files to create the proper DNA (DIS) data files for usage on the disassembler
* Debugger
- Finish the ability to dump and fix the loaded modules on user choice
- Make a dialog to display properly the disasembled files while you are debuggin. (Now it display only a single line on the debugger caption)
- Try to make a real time log file to the user analysis the different flags of the code flow that is being debugged
* General upgrade
- Separate the assembler, disasembler, debugger, resources editor and make they works standalone or integrated with the whole RosAsm pack. (Isolating the different parts of the project is good for a matter of development)
- Enable the hability to users create plugins for RosAsm
- Enable the hability to users import and export lib/obj files in RosAsm
- Perhaps i´ll enable the hability to import and export linux elf files (For usage under wine)
- Enable a light script engine for the disassembler structures, equates etc
As you see, i have lots of projects planned, but working quite alone is a hard task to accomplish soon. So, new developers are welcome to help