IDA has a notepad, but it's not the greatest.
Instead, have a notepad that can (optionally) be correlated to certain code bounds. Any user with a cursor in these bounds (remember multiplayer support) can see notes for that given chunk of disassembly. Ideally, this would be the reverser's attempt to generate C or pseudocode. Yes, this could be handled with a bunch of comments, but that's dirty and difficult to follow.
Vague use case:
User right-clicks on a function label and hits "add code note". A notebook window appears on the right side of the screen. The user is prompted for the range that they want this note to entail (auto-populated with the bounds of the current function). User selects their bounds and is then able to type away with pseudocode. This note is synced with all other PyDA-ers.
IDA has a notepad, but it's not the greatest. Instead, have a notepad that can (optionally) be correlated to certain code bounds. Any user with a cursor in these bounds (remember multiplayer support) can see notes for that given chunk of disassembly. Ideally, this would be the reverser's attempt to generate C or pseudocode. Yes, this could be handled with a bunch of comments, but that's dirty and difficult to follow. Vague use case: User right-clicks on a function label and hits "add code note". A notebook window appears on the right side of the screen. The user is prompted for the range that they want this note to entail (auto-populated with the bounds of the current function). User selects their bounds and is then able to type away with pseudocode. This note is synced with all other PyDA-ers.