Consider changing property name schema for list tags

[maraf]

When introduced Listing tag lib in #245, we used naming convention to access fields of list model item as {model}-{field}. Also, we found that it is confusing, or "not designed", to name properties on libraries, where not only list tag exists.

Good example is a new templated menu. We have web:menu and than web:menuItemDisplay, web:menuItemUrl etc.

What I'm suggesting is to change to web:menu with web:menu-display, web:menu-url etc.

Pros

• Current naming is confusing. In libs like language, there isn't any prefix and list sets lang:id which is weird.

Cons

• Properties of list and edit tags where shared and used to compose URLs. Example is article id, where list and edit use the same property. This property is also used to compose detail URL.

List of changed tags and properties

• fa:browser
• lang:list
• loc:edit
  • loc:editItemIndex
• pg:search
• u:list
• val:message
• web:menu

Sub tasks

• [ ] Create support for prefixed properties?

[maraf]

Lets leave it for now. Rethink it when property references will be a think. There is a problem properties in URL.