Disable the Web 0.2 UI available in Quickr Themes
Category Quickr
When QuickPlace 1.0 shipped in 1999, there was no concept of a custom theme. That came with 2.0 in June 2000. IBM also shipped some themes that were fine then but pretty awful by today's standards. Some are so bad that they break functionality, or hide it. In Quickr 8.0, they hid the old themes (finally!) but they came back in 8.1. You can even select QuickPlace 1.0 "Classic" as a theme.
By "You", I mean place managers, who are most of the time plain old end users - not developers or designers or administrators, not tech savvy people who know a good Web 2.0 design when they see it.
I've been advocating for IBM to retire for GOOD the old themes for several years now. Since they're still there, here are two ways you - administrator, server jockey, developer with access - can rid your server of the offensive UI choices.
Method 1: In Quickr 8.1, modify qpconfig.xml to unblock the following, then allow and block themes as you desire (including custom themes):
<themes restrict_choices="true">
<allowed>"Quickr 8.0", "Quickr 8.0 (with classic navigation)"</allowed>
<blocked>"Quickplace Classic","Quickplace Classic 3.0","Quickplace Organized","Quickplace Simple","Quickplace Clean Space","Quickplace Shapes","Quickplace Banner","Quickplace Classic 1.0"</blocked>
</themes>
Method 2: For all versions, a simple method:
1. Using a Notes client, open the database Data\LotusQuickr\resources.nsf on the Quickr server.
2. Open the view Skin Groups
3. Sort the view by the h_Position column.
4. Select the themes with values 70 through the first 10000 (screenshot below). Delete these documents. This will leave the standard theme, the Quickr Entry theme only used by that template, and the accessible themes only used when a user enables accessible mode.
When QuickPlace 1.0 shipped in 1999, there was no concept of a custom theme. That came with 2.0 in June 2000. IBM also shipped some themes that were fine then but pretty awful by today's standards. Some are so bad that they break functionality, or hide it. In Quickr 8.0, they hid the old themes (finally!) but they came back in 8.1. You can even select QuickPlace 1.0 "Classic" as a theme.
By "You", I mean place managers, who are most of the time plain old end users - not developers or designers or administrators, not tech savvy people who know a good Web 2.0 design when they see it.
I've been advocating for IBM to retire for GOOD the old themes for several years now. Since they're still there, here are two ways you - administrator, server jockey, developer with access - can rid your server of the offensive UI choices.
Method 1: In Quickr 8.1, modify qpconfig.xml to unblock the following, then allow and block themes as you desire (including custom themes):
<themes restrict_choices="true">
<allowed>"Quickr 8.0", "Quickr 8.0 (with classic navigation)"</allowed>
<blocked>"Quickplace Classic","Quickplace Classic 3.0","Quickplace Organized","Quickplace Simple","Quickplace Clean Space","Quickplace Shapes","Quickplace Banner","Quickplace Classic 1.0"</blocked>
</themes>
Method 2: For all versions, a simple method:
1. Using a Notes client, open the database Data\LotusQuickr\resources.nsf on the Quickr server.
2. Open the view Skin Groups
3. Sort the view by the h_Position column.
4. Select the themes with values 70 through the first 10000 (screenshot below). Delete these documents. This will leave the standard theme, the Quickr Entry theme only used by that template, and the accessible themes only used when a user enables accessible mode.
