Elements panel expanded at startup http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=12406680 2013-05-24T07:08:20Z 2013-05-24T07:08:20Z GEOFFREY THOMPSON http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12441047 2013-02-27T17:18:03Z 2013-02-27T17:18:03Z

>>>>Do you follow the same rule I do of not letting pages need scrollbars unless absolutely necessary? I do. And I try to keep the functionality appropriate. So sometimes the pages are quite small – like 020_AcctNum – to get the account number from a caller. I try to think about reentry points. But sometimes (processing database results) ends up with quite a complex page. I use Classic view for elements, not Studio5 view (I just hate those huge adorned boxes that all look the same) so I can pack the elements a lot tighter together if needed. So yes – no scroll bars. I want to run Documenter at the end and get all the screen shots into the .rtf file – convert to Word and edit so each diagram starts on a new page. I sound quite anal about all this – probably true. ;-) >>>>Curious… you said you don’t see how someone would use the element view. How do you add elements to your callflow? Sorry, we are not talking about the element pane on the left hand side under the project pane. We are talking about the outline pane on the right hand side. Regards, Geoff

GEOFFREY THOMPSON 2013-02-27T17:18:03Z Asher Schweigart http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12440450 2013-02-27T16:47:03Z 2013-02-27T16:47:03Z

Also, how big are your pages? Do you follow the same rule I do of not letting pages need scrollbars unless absolutely necessary?

Asher Schweigart 2013-02-27T16:47:03Z Asher Schweigart http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12439720 2013-02-27T16:45:18Z 2013-02-27T16:45:18Z

Curious… you said you don’t see how someone would use the element view. How do you add elements to your callflow? Also, wow, I thought my applications were getting big at 20 pages, but 200 is just insane. Many props to you for figuring out how to keep that manageable!

Asher Schweigart 2013-02-27T16:45:18Z Janine Graves http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12409210 2013-02-26T20:54:03Z 2013-02-26T20:54:03Z

Geoff, this is all great info! Please share more of your naming conventions/best practices when you have the time!

Janine Graves 2013-02-26T20:54:03Z GEOFFREY THOMPSON http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12408766 2013-02-26T20:32:03Z 2013-02-26T20:32:03Z

Regarding: >>>>>>>>> Window > Preferences - Call Studio / uncheck Expand elements in Elements View I always uncheck this. When you build big applications (I have made some with over 200 pages), the element expansion in the outline pane is the most annoying thing you can imagine. (I never really grasped how someone would use the element view anyway.) The outline pane then becomes really useful in an application with a large number of pages for navigating to pages. What this does bring to mind is a naming convention for pages, because the list in the outline pane sorted alphabetically – and if this matches the layout of the pages across the bottom, it becomes REALLY useful for navigation. My convention is to name pages like 001_Entry, 002_Initalize, 003_Welcome, . .999_Exit – you get the idea. I leave large holes in the numbering because I know I will come back later and sometimes insert pages – so it’s good to have big gaps (based on functionality) and keep all the numbers in order. I also name the page entry element EXACTLY the same as the page (except for 001_Entry where Cisco called it “Start”), which makes Page Connectors easy to align. With this convention, the layout in the outline pane matches the tabs across the bottom. Yes, sometimes I get caught out and have to do a bit of renaming, but it’s totally worth it. The page “numbers” get applied in lots of ways to the elements on the page – all designed to make those long and convoluted activity logs useful when debugging complex call flows. Regards, Geoff

GEOFFREY THOMPSON 2013-02-26T20:32:03Z Asher Schweigart http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12405886 2013-02-26T19:48:03Z 2013-02-26T19:48:03Z

Perfect, thanks!

Asher Schweigart 2013-02-26T19:48:03Z Janine Graves http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12405794 2013-02-26T19:42:03Z 2013-02-26T19:42:03Z

Asher - In Studio, go to Window > Preferences and select Call Studio / General - and deselect the first check box: Expand elements in Elements View. Then restart Studio.

Janine Graves 2013-02-26T19:42:03Z Asher Schweigart http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12406679 2013-02-26T19:33:07Z 2013-02-26T19:33:07Z

This is a trivial issue, but I thought I'd see if anyone on here has figured out a workaround.  Whenever Studio is opened, in the elements pane all the folders are expanded, no matter what state they were in upon closing. All the other view changes are remebered, such as what projects are open and what folders in the navigation pane are expanded, but not this pane. Has anyone figured out a way to fix this? I'd be ok with a solution that has them all colapsed upon startup. 

Asher Schweigart 2013-02-26T19:33:07Z