M
mark
FrontPage Is Not Handling Themes and Style Sheets Properly
The Problem
Method
Procedure
Review
Results
Conclusion
=====
THE PROBLEM
FrontPage has difficulty managing style sheet and theme customizations
depending on the environment where FrontPage is used.
=====
METHOD
The FrontPage Format menu commands for Theme... and Style... are used to
effect changes to page appearance. It is not relevant if the changes are
applied in Design View or in Code View. The results are the same. The
operating environment housing the FrontPage installation is being tested. Two
design features are tested: theme dialogs and style sheet style settings.
Theme/style approaches are applied in three environments, desktop alone,
desktop and Windows Server 2003 HTML site, desktop and Windows SharePoint
Services 2.0 site.
The three test environments are isolated by creating each environment in a
separate system installation of Windows XP and Microsoft Office 2003
including FrontPage 2003. Software and Hardware are either Microsoft or at
the top of the Microsoft Recmmended list, whichever is best - an "optimal
Windows" system.
=====
PROCEDURE
Two appraoches are considered: theme dialogs and style sheet editing.
a) I create a new site and apply a style sheet and then a apply a theme.
b) I create a new site and apply a theme and then apply a style sheet.
Comparing the two approaches does not isolate any distinction between order
of approach and FrontPage performance in design. Thus the report below does
not isoalate this design approach.
Theme and style approaches are applied to new sites in new environments (see
above) using the step-by-step proceedures recommended in FrontPage Help and
in current Microsoft pulications by Jim Buyens.
A) Style Sheet - I open a style sheet and apply changes to some attributes.
I go back to design view and review page appearance. I return to edit the
style sheet and apply a few more changes to some elements. I re-open design
view and again review page appearance.
B) Theme Dialog - I open the theme dialog and apply changes to some
attributes. I go back to design view and review page appearance. I return to
the theme dialog and apply a few more changes to some elements. I re-open
design view and again review page appearance.
=====
TESTING REVIEW
(i) I create a new themeless site and pointed an empty style sheet to the
index file. I created a few elements in the style sheet and WOW! the site
page responds well, displaying things just the way I had asked for them to be
displayed. Then I go back to my style sheet and added a few more elements.
Next, I open my page in design view. The second style sheet edit has randomly
(?) swapped 1st edit and 2nd edit changes to font appearance and returned
some elements to default appearance (no style application. This result we
will just call "messed up" customization. Attempts to correct the style sheet
tangle were usless. Though we always make at least three attempts to resolve
the issue. FrontPage remembers the site so attempts imply creating a new site
and starting over.
(ii) I create a new empty site and add a new theme (bottom of theme task
pane) and in the theme dialog add some attributes to elements. Of course,
returning to design view my style choices are gorgeous and display just like
I like 'em! Now, I want to tweak a few things and so I go back to the theme
dialog and change a few attributes. When I return to design view [groan] the
attributes are messed up.
(iii) I create a new site with an empty theme and open and edit theme style
sheets, honoring the proccedures applied within the various style sheets: for
example in the color1.css sheet only color attributes are set. When i
returned to design view of index htm, none of me changes are displayed. But
FrontPage remembered my changes from the preceeding example and applied about
half of the junk settings that appeared in the previous example when I tryed
to tweak a few things.
I created a new site and applied a theme. I opened the theme dialog and
edited a few element attributes and applied them and displayed fine. I opened
the theme dialog again and FrontPage screwed my attributes around.
=====
RESULTS
Three environments are tested.
1) desktop only
2) desktop and Windows 2003 server HTML site
3) desktop and Windows SharePoint Services 2.0
1a) desktop style - does not work period
1b) desktop theme - works
2a) desktop style - mess up
2b) desktop theme - works
2c) site style - mess up
2d) site theme - works
3a) desktop style - mess up
3b) desktop theme - mess up
3c) site style - mess up
3d) site theme - mess up
CONCLUSION
This is an end user client based conclusion.
There are likely registry keys that need to be reset/created and product
files in the Documents and Settings folder that need to be edited to correct
the shortcoming.
One can only hope that FrontPPage Product Development, FrontPage
Programming, Windows Server Programming, and Microsoft Office Programming
will put theiuir heads together and finally complete the FrontPage GUI for
style design.
Many product suggestions are no doubt in circulation. My top wish is a dialog
box that lists Styles in a scroll box as is presently the case; but also,
provides a description of the particual style selector that is highlighted in
the Styles scrolling list. When "a:active" is selected. or ".a-active" is
typed in the Styles list selection box, then in the description field a
description of the style attribute is provided. For the "a:active" selector,
the description might be "Modifies the appearance of a hyperlink the visitor
has just clicked."
The Problem
Method
Procedure
Review
Results
Conclusion
=====
THE PROBLEM
FrontPage has difficulty managing style sheet and theme customizations
depending on the environment where FrontPage is used.
=====
METHOD
The FrontPage Format menu commands for Theme... and Style... are used to
effect changes to page appearance. It is not relevant if the changes are
applied in Design View or in Code View. The results are the same. The
operating environment housing the FrontPage installation is being tested. Two
design features are tested: theme dialogs and style sheet style settings.
Theme/style approaches are applied in three environments, desktop alone,
desktop and Windows Server 2003 HTML site, desktop and Windows SharePoint
Services 2.0 site.
The three test environments are isolated by creating each environment in a
separate system installation of Windows XP and Microsoft Office 2003
including FrontPage 2003. Software and Hardware are either Microsoft or at
the top of the Microsoft Recmmended list, whichever is best - an "optimal
Windows" system.
=====
PROCEDURE
Two appraoches are considered: theme dialogs and style sheet editing.
a) I create a new site and apply a style sheet and then a apply a theme.
b) I create a new site and apply a theme and then apply a style sheet.
Comparing the two approaches does not isolate any distinction between order
of approach and FrontPage performance in design. Thus the report below does
not isoalate this design approach.
Theme and style approaches are applied to new sites in new environments (see
above) using the step-by-step proceedures recommended in FrontPage Help and
in current Microsoft pulications by Jim Buyens.
A) Style Sheet - I open a style sheet and apply changes to some attributes.
I go back to design view and review page appearance. I return to edit the
style sheet and apply a few more changes to some elements. I re-open design
view and again review page appearance.
B) Theme Dialog - I open the theme dialog and apply changes to some
attributes. I go back to design view and review page appearance. I return to
the theme dialog and apply a few more changes to some elements. I re-open
design view and again review page appearance.
=====
TESTING REVIEW
(i) I create a new themeless site and pointed an empty style sheet to the
index file. I created a few elements in the style sheet and WOW! the site
page responds well, displaying things just the way I had asked for them to be
displayed. Then I go back to my style sheet and added a few more elements.
Next, I open my page in design view. The second style sheet edit has randomly
(?) swapped 1st edit and 2nd edit changes to font appearance and returned
some elements to default appearance (no style application. This result we
will just call "messed up" customization. Attempts to correct the style sheet
tangle were usless. Though we always make at least three attempts to resolve
the issue. FrontPage remembers the site so attempts imply creating a new site
and starting over.
(ii) I create a new empty site and add a new theme (bottom of theme task
pane) and in the theme dialog add some attributes to elements. Of course,
returning to design view my style choices are gorgeous and display just like
I like 'em! Now, I want to tweak a few things and so I go back to the theme
dialog and change a few attributes. When I return to design view [groan] the
attributes are messed up.
(iii) I create a new site with an empty theme and open and edit theme style
sheets, honoring the proccedures applied within the various style sheets: for
example in the color1.css sheet only color attributes are set. When i
returned to design view of index htm, none of me changes are displayed. But
FrontPage remembered my changes from the preceeding example and applied about
half of the junk settings that appeared in the previous example when I tryed
to tweak a few things.
I created a new site and applied a theme. I opened the theme dialog and
edited a few element attributes and applied them and displayed fine. I opened
the theme dialog again and FrontPage screwed my attributes around.
=====
RESULTS
Three environments are tested.
1) desktop only
2) desktop and Windows 2003 server HTML site
3) desktop and Windows SharePoint Services 2.0
1a) desktop style - does not work period
1b) desktop theme - works
2a) desktop style - mess up
2b) desktop theme - works
2c) site style - mess up
2d) site theme - works
3a) desktop style - mess up
3b) desktop theme - mess up
3c) site style - mess up
3d) site theme - mess up
CONCLUSION
This is an end user client based conclusion.
There are likely registry keys that need to be reset/created and product
files in the Documents and Settings folder that need to be edited to correct
the shortcoming.
One can only hope that FrontPPage Product Development, FrontPage
Programming, Windows Server Programming, and Microsoft Office Programming
will put theiuir heads together and finally complete the FrontPage GUI for
style design.
Many product suggestions are no doubt in circulation. My top wish is a dialog
box that lists Styles in a scroll box as is presently the case; but also,
provides a description of the particual style selector that is highlighted in
the Styles scrolling list. When "a:active" is selected. or ".a-active" is
typed in the Styles list selection box, then in the description field a
description of the style attribute is provided. For the "a:active" selector,
the description might be "Modifies the appearance of a hyperlink the visitor
has just clicked."