am i overkilling it?
any missing features?
and please ignore the two "???" buttons, im not sure what functionality to put behind these buttons!

Yeah, cool.

Generate the boring boilerplate so we can concentrate on the meat of the coding.

because im bored
Me too.

We need easy write big code. And not write hands all variables names and put in differents places in code.

And no need see all big asm code, it impairs code reading.
Need small easy reading blocks code.
We need asm generator !

I think you are advocating for HLLs.

Cool.

Roman, don`t look at assembly from HLL point of view:
first of all intermixing stages is unallowed.
so split vars of preprocessor vars (EQU) & assembler vars (all rest)
if thou don`t split them in initial state thou will feel problems in future with evolving tool.

then in assembly no types in HLL matter.

but type in assembly could be tractated as set of definitions related to memory cell and size of that cell.
float dword & int dword in assembly is single unsplitterable type.
float qword & int qword too.

but
a: db 'hello'
&
a db 'hello'
&
a db 'hello'
sizeof.a = $-a
are 3 completely different types because these constructions declare different set of labels and constants related to same memory cells.

some tipes I wouldn`t suggest to realize as stndalone types, much better to realize them as flags(checkbox) of more common types.
so in 32bit ppAddr is variant of dword(dd), and interface is variant of ppAddr, such nesting will better demonstrate internal nature of types.

in case of interfaces if thou declare some var as comobject of some common interface & will want to realize via it child interface thou will have to share same memory whithin 2 interfaces.

so vars should not only occupy their own cell, but share it with other vars.

to Ali.Z: better PE as property sheet, subsystem as combobox, sections as something with uneditable editbox with summary info about section & with single button EDIT.
moreover property sheet is weak demonstrated by fasm (so it would be interesting) - just remember property sheets structures differs from one version of COMCTL32.DLL to another, initialy requested proper version of comctl and only after created appropriate propertysheet. structs of property sheet are only expanded from version to version so could be defined lastmost variant, and only its first member struct size will be affected by comctl version.

prominick, i like compact design like property sheet, however it does not worth spending time on it as i just want make everything done as quickly as possible.

i liked the idea of combobox, its not cool to have radio buttons for everything.

currently im still editing the user interface and writing minimal control handling and logic so still not everything is functional. once done i will move on coding the logic / functionality behind the control.

more on property sheets:
property sheets are basically tab control, however another control is also involved, which is MDI.

the logic behind property sheets can be done by subclassing tab control and making a borderless popup window for each tab.
the borderless popup window will have child controls in it client area.

i can do that, but im not much interested in graphical part.

but yes property sheet is very good, and personally i like it because i can have a very small window/dialog with several pages to cover anything i want. (but again it takes time)

another idea to have compact design is to make it like installations setup where we can navigate thru pages by clicking "Next" and creating/destroying each dialog as we hit next or back buttons.
but its not ideal, there are better ways to implement such logic .. but i have to think a lot.

i will update the first post shortly to include another image of the progress. (after completing the wizard and the functionality of it, then i can focus on the gui part and more compact design)

i also added a way to create custom section, includes, how to construct import section and what resource do you want to use.

maybe we can add stuff for fasmarm too, but not now.

ok here is more progress, ui is done .. need to focus on logic.

https://board.flatassembler.net/topic.php?p=213435#213435 (first post)

it will take few days, as i cant spend all my free time working on this.

believe or not, while editing the order of control creation i used ctrl-x to cut so i can paste somewhere else, and i copied a large chunk of controls then accidentally i copy something else and save the file (((((((((((((((:

im not going to work on this anymore, fuck this luck.

Sorry to hear about your pain.

Backups?

i have an old backup that have less than 50% of the controls and 0 logic code. (before messing up i had over 170 controls)

one might be wondering why the order of creation matter, well it doesnt normally, but when you want to have ws_group and tabstop style to navigate using tab and arrow keys it doest matter. (because after creating 1 control with ws_group, every control follows that control will be assigned to the same group until it find another control with ws_group style, which is stupid implementation, i blame windows)

Order always matters IMO. Not everyone uses the mouse. The keyboard navigation is awful when dialogs don't have the controls in any order.

yes, i dont use the mouse a lot, thats why i wanted to reorder so i can use group and tabstop styles.

all what i wanted is to create something that aid development when using fasm by generating the basic requirements by few clicks nothing fancy - a simple utility not a real project.

maybe i need to create something else, ehm on top of my head:
- source level flow analyzer, that create flow graphs.

IDA Pro/demo are disassembly level flow analyzing tool, imagine same functionality for source level, that would be super great project.

but its near impossible without implementing your own custom classes, or at least subclassing many different controls. (lets say minimum 5)
and of course use GDI for drawing, and implement a zoom-in/out mechanism.

then basically analyze Jcc and call instructions.
but thats little bit to much for 1 person, all this extensive work should be split across a small team. or otherwise that single person should work several months before seeing actual product and testing it.

Should have used Git or something

Seems like a great tool!
I could help to code something like that -- using custom property pages -- not the ones from ComCtl32.
Except I don't get all the things specified in UI: NX!? I know NX-01, but that is not it.
What is "Native"? Is it a DLL project?
"Control Panel"? -- You mean Windows Control Panel? I don't follow this one too.
Oh, I see -- you have DLL there -- good.

Ali.Z , is it possible to see the source code of your program ? It seems very useful and interesting in terms of automation. Many thanks in advance. Vladimir

It is "Device drivers and native Windows processes".

Native would be no OS.