Search
Font Size:
You're here: Resources » Forums
Forum
HomeHomeBeta Discussion...Beta Discussion...5.0 Skinning5.0 SkinningHow Many UI Files Are Needed?How Many UI Files Are Needed?
Previous
 
Next
New Post
2/6/2008 9:34 AM
 
On average, the basic DotNetNuke skin consists of a Portal.ascx, Admin.ascx, and some other we will refer to as Home.ascx. This means that almost every skin out there has at least 3 user interface files plus any related images and a css file. While we want to provide the ultimately flexibility to designers for creating forum skins, we do not want to require them to make too many UI files otherwise they will not bother creating skins for the forums.

For the forums, I figure we need the following at a minimum (and perhaps maximum):
  • GroupView - The initial view when navigating to a forum page (in most cases), shows groups with forums within the groups.
  • ThreadView - This view lists all threads within a specific forum. It is also used for search results and "My Posts" (which is thread view).
  • PostView - The details view that shows multiple posts within a single thread.

The problem I see with the above approach is that aggregated views and the search results view generally use slightly different items in them. For example, a typical thread view shows the title then "by" user alias. In aggregated or search results view, it shows title then "in" forum name. Outside of this, the items are identical. Do we just create a skin object (token) that is smart enough to handle the difference and name it appropriately?

Any additional thoughts/concerns?

 
New Post
2/10/2008 2:22 PM
 
I think the issue I outlined can be handled in a way just like we handle the User skin object in DNN core (display name logged in, "Register" otherwise).

In reference to the above 3 skin types, I was thinking this requirements for all 3 views:
  • Require 2 Groups, Threads, Posts in design, using same tokens in each group but this allows designer most flexibility to 'alternate' and have proper spacing.
  • Require "Header" area with tokens.
  • Require "Footer" area with tokens.

Validation will need to be done by each type (ie. thread, group, post) to see if a token is acceptable. The xml file can define the role of each html file.

 
New Post
3/11/2008 10:15 AM
 
I have a requirement that might fall in between multiple skins or a new TOKEN to help make it seem like there are more skins going on...

When adding other instances of the forum it's possible to use slightly different skins.  I've done this on the iKon theme (see samples.)

The main forum is on the parent menu called "Community".  Underneath are pages with different sections of the same forum installed.  When you click on any of those forums (ProTools Forums for example) the backgropund image of the module skin is used to show that we are in a different category of the forum.  This works very nicely when we go to the Pro Tools forum through the menu.  However,  if we get there through the main forum (Community) link, we don't get this.

It might be a nice to figure out a way to accomplish this through the forum skinning system instead... could we have a skinning Token for the category that could have some attributes applied ot a backround image?

Perhaps I'm thinking about the approach in the wrong way, but the gneral idea of what I'm looking for is there...


Rob Poretti - Poretti Productions - skin3 Team ● X:Skins ● Cubist ● KrystalWare ● Gamer ● iKon

 
Previous
 
Next
HomeHomeBeta Discussion...Beta Discussion...5.0 Skinning5.0 SkinningHow Many UI Files Are Needed?How Many UI Files Are Needed?


Top Discussions
All time, we have 601 new thread(s) and 1981 new post(s)
The most popular thread has been 4.5.0 Release Posted
The most active thread has been 4.5.2 Bug
Users Online
Membership Membership:
Latest New User Latest: daniel.almond
New Today New Today: 0
New Yesterday New Yesterday: 1
User Count Overall: 1556

People Online People Online:
Visitors Visitors: 5
Members Members: 0
Total Total: 5

Online Now Online Now: