Converting Native Style to Element Templates - Detailed explanations needed.

This is sort of a follow up to a post I made over 3 months ago. http://communities.bentley.com/products/road___site_design/f/5922/t/126169

I am looking into re-configuring some Example Civil Cells to use a Client Supplied Level convention. The initial results are quite promising. Here are my steps:

1. Open copies of one of the delivered Civil Cell DGNLIB files.
2. In the Project Explorer locate the Feature Definitions of the active file.
3. In the Element Templates dialog box locate the element templates of the active file.
4. Make a Temporary New Template Group
5. Copy the necessary client Element Templates from their DGNLIB into the temporary group just created.
6. Rename Element Templates and change their levels to match the client element template names. The copied temporary make this step easier as you can copy the names from the temporary versions by putting them into Rename mode.
7. Rename the Feature Definitions to match the Element Template Names and change the Plan and 3D element templates to match those used in Step 1
8. In the Project Explorer, locate the Civil Cells and Locate and Template Drops under and Dependent Elements. Most will be in Element Templates. Edit the points, changing their styles to your Element Templates. Alternatively, if you can find the template library, edit them there and use the synchronize option. If you can't locate the library, use the template library organizer to copy one of each template to another template library, edit them and use the element info dialog box with each linear template selected, to expand the tree in the element info dialog until you can select the template drop, Then, in the Template Name field, click so the Select Template dialog box opens and select the new version of the same template.

This process can result in components and features being migrated to a different client.

But, most of these use element templates and not Native Styles. What is needed is a detailed explanation of what is needed to replicate native style behavior in element templates.

For example, InRoads XIN supports from o to 9 different display modes for one style. There is a Default setting which can define Linear, Points and Text and these are 100% independent of each other. When a Default is defined, Plan Profile or Cross Section display can use the settings if requested. Optionally, one can define a Plan, Profile or Cross Section specific setting again for the three types - Linear, Point or Text.

So if using element templates and a Feature Definition for a Linear element is being setup, There is a Plan, Profile, Intersecting Profile, Projected Profile, Cross Section and 3D area which need settings. When setting up Intersecting Profile or Cross Section, do these need a Point Element Template? And if we need different levels then will we need more than one element template?