Hi Brett,
Thanks for the suggestion, we’ll take it on board.
In the meantime, have you considered whether or not you can use FinalBuilder’s other organizational techniques to organize your build. Some ideas are:
- Action Groups : Use the parent/child hierarchy to create nested groups which perform each sub-function of your process. Rename the Action Groups to identify them.
- Action Lists : Move larger blocks of related actions to different Action Lists (create new lists by right-clicking the Main action list header and choosing ‘Create Action List…’)
- Subprojects : Move even larger blocks of related actions to different projects, and include them by using the Include Project action.
(Some customers have found it helpful to put all the major modules of their application into separate build projects, and call each of these from a “Master” project.)
Regards,
Angus
I have to agree with Angus. I use all of his suggestions. I use colours sparingly, mostly to indicate whether an action uses javascript (the icon is too subtle), whether it’s a hack and needs updating in the future, whether it does something critical… Maybe being able to bold an action name would be helpful, dunno about changing the typeface or size though. I can’t really picture it looking like anything other than postmodern art…
Steve