Code libraries for AMO pages: Difference between revisions

The locators are defined as simple string 'constants' in classes. The arrangement is intended to take advantage of autocomplete features in IDEs allowing someone to build a "path" to a locator. The highest level classes are page types. Within them are classes for types of pages. These classes have locators for individual elements or nodes, and classes for groups of elements which themselves contain locators. <br>

Class names are capitalized. Locator names are all lowercase. The autocomplete feature in IDEs generally differentiate classes from variables with different icons.&nbsp; If an autocomplete feature isn't available or isn't responding the AMOlocators module can be viewed in an editor that can collapse classes to show only the detail of classes (pages) of interest.

An example of using autocomplete in an IDE that's aware of classes: <br>

#While editing a script after typing "AMOlocators." (or local instance) a list classes appears containing Collections, Personas, Categories. <br>

#After selecting a class and typing '.' another list appears for the classes within it, perhaps LandingPage, BrowsePage, SearchResults. <br>

#After selecting one of these classes a longer list appears.&nbsp; Names in all lowercase define a string that's a locator.&nbsp; Capitalized names indicate another class, perhaps for an item in a list or cluster of elements.<br>