Feedback on NuSkin

-- DavidPatterson - 03 Sep 2008

Thank you very much David for sharing this skin with the TWikiCommunity!

-- PeterThoeny - 03 Sep 2008

A quick note: The office toolbar button for Creating a new topic is incorrect for 4.2.3 It should point to WebCreateNewTopic

Also would it be possible that you could add a dropdown menu like Quickmenu does for navigating to different webs?

-- GilbertJones - 21 Oct 2008

Hi Gilbert, yes, I need to update the skin with that and other improvements/fixes that I've been gradually implementing at work.

In NuMenuBarWebs.txt you already have the option that you ask for, you just need to remove the

subwebs=Groups

But I really would recommend not throwing all the available webs at the user in one go. Use the NuMenuBar to provide a structured navigation model to the user.

-- DavidPatterson - 22 Oct 2008

Thanks, for the reply. I just figured that out this morning. Can you explain why your original version does not work? I like the idea of only showing the webs a person has view access, for an intranet it makes a lot of sense.

-- GilbertJones - 22 Oct 2008

Is there anyway to reduce the number of CSS templates used with Twiki when this skin is enabled?

-- GilbertJones - 23 Oct 2008

Any sort of timeline for a new release?

-- GilbertJones - 29 Oct 2008

I was thinking that skin developers should have a tool to "compress/compact" all cssinto one big file for distribution.. a lot easier to work with, and a lot easier on the server connection.

-- RafaelAlvarez - 29 Oct 2008

When a user clicks on create a new topic from the office toolbar the wysiwyg editor is loaded inside of help box, and the office toolbar disappears along with the rest of the skin. Is this a problem with the skin or a side effect of the wysiwyg editor settings?

-- GilbertJones - 30 Oct 2008

There are indeed a lot of JS and CSS files on an extended TWiki. On my version at work I have 12 JS and 13 CSS on Main.!WebHome alone. A good practice is, with your web server, to set expires headers (as described here, http://developer.yahoo.com/performance/rules.html#expires) on .js, .css and image files served from your skin related sub-directories in Pub. This tells the web browser to cache those files for future use so they don't have to be resent from the server.

NuSkin itself has "only" 1 js and 2 css files plus the required jquery js and css files. With the JQueryPlugin, MichaelDaum provided minifier scripts for js and css which you'll find in the tools directory. Just put the core css together in one file (and in the right order ) and minify it. But, the hard work is to replace all the places in the PatternSkin where the individual css files (and js files, if you like) are @imported or linked with a single call to your newly created single file.

The NuSkin is (currently) only a view template (view.nu.tmpl) so what you describe sounds to be correct (though I'm not sure I understand what you mean by "loaded inside of help box").

-- DavidPatterson - 30 Oct 2008

I am not sure where to post this as it could be a bug or a configuration error with either pattern skin or TinyMCE? . On my installation I have Nuskin loaded which only adds a custom view template while mostly using the pattern skin. I upgraded to the latest version of the pattern skin and now have the following problems. If a user initiates the creation of a new topic a post is made which calls WebCreateNewTopic?parent=WebHome at this point the TinyMCE? editor is loaded within the twikiHelp div class within a list that exists within td class primaryTextcolumn this produces an ugly result as the closing of the help hides the editor. In addition the help information is broken as the help content after the word Wraps is showing up as literal content and not being parsed. Where should I look to correct this problem. It does not appear to me to be a CSS problem but then again I am a system administrator and not a web developer.

-- GilbertJones - 31 Oct 2008

After a little searching, I decided to review the TinyMCEQuickHelp.txt I found that for some reason on my installation that the list item <verbatim> was being process as verbatim no matter what I did. Finally I added a space between the verbatim and &gt tag. This fixed the issue of the help box, however the question now is why was verbatim still being picked up no matter what I did. I tried all the usual tricks for getting twiki to ignore the word verbatim but none of them are working.

-- GilbertJones - 03 Nov 2008