Descriptions could be a useful tool for adding to specific triggers, or an entire object. This is true in my department as when working on a joint project we have to spend time explaining the triggers.
Two improvements I'd like to suggest would be:
Separate each trigger with a line so they're easier to read.
Option to collapse a set of triggers belonging to one object to reduce scrolling and clutter.
The following mockup isn't perfect but includes all of the above. Descriptions would be added in the trigger editor and could be displayed in a popup when hovering over, or clicking on, the information icon.
Edit - It may also be beneficial for each trigger to be automatically numbered. This would help to quickly recognise a particular trigger during discussion or support, and make the ordering of triggers even clearer.
I also think this is a much needed feature. In projects with many triggers and execution of javascript, it would help to be able to add brief comments to identify what that trigger is supposed to accomplish or the intent behind the javascript code is being executed. Otherwise, the designer must remember where along the trigger panel each segment of code is if it needs to modified later.
In fact, I would welcome a feature that allows designers to save Javascript snippets on a per project basis (like a local list/database of snippets per-project), and one would merely need to write the snippet, give it a name, brief comment, and select it when it needs to be called/executed on a trigger.
For example, for the line "Execute javascript" in the trigger panel, clicking on the word "javascript" would give the user the option to either open a new window to write custom javascript or select from a snippet that has already been saved to the project.
That way, there is only one place to edit each snippet (if needed) and things would be more organized - and offer a much better workflow.
4 Replies
Descriptions could be a useful tool for adding to specific triggers, or an entire object. This is true in my department as when working on a joint project we have to spend time explaining the triggers.
Two improvements I'd like to suggest would be:
The following mockup isn't perfect but includes all of the above. Descriptions would be added in the trigger editor and could be displayed in a popup when hovering over, or clicking on, the information icon.
Edit - It may also be beneficial for each trigger to be automatically numbered. This would help to quickly recognise a particular trigger during discussion or support, and make the ordering of triggers even clearer.
Hey Doug,
I always like to ask users for a use-case when requesting features to help us better understand.
A use-case and a mock-up make it super easy for me to pass this on to the team.
You are always welcome to share your ideas here.
I second Doug's great requests, especially the ability to collapse.
Hello everyone,
I also think this is a much needed feature. In projects with many triggers and execution of javascript, it would help to be able to add brief comments to identify what that trigger is supposed to accomplish or the intent behind the javascript code is being executed. Otherwise, the designer must remember where along the trigger panel each segment of code is if it needs to modified later.
In fact, I would welcome a feature that allows designers to save Javascript snippets on a per project basis (like a local list/database of snippets per-project), and one would merely need to write the snippet, give it a name, brief comment, and select it when it needs to be called/executed on a trigger.
For example, for the line "Execute javascript" in the trigger panel, clicking on the word "javascript" would give the user the option to either open a new window to write custom javascript or select from a snippet that has already been saved to the project.
That way, there is only one place to edit each snippet (if needed) and things would be more organized - and offer a much better workflow.
Best regards,
- Belal
This discussion is closed. You can start a new discussion or contact Articulate Support.