Juan,

I can't reproduce the issues on FF w.r.t. to the sidebar and more-menu.
On my FF (v27.0.1) this is running ok.

Can you try and clear the browser cookies, to see if that has any effect.
 (I would expect not, but you never know)

***
Currently, the HADDOCK template has no skins.  However, it is my intention
to still support skins, and support the use of 3rd-party skins for
BOOTSTRAP.  (eg http://bootswatch.com)
Still need to figure out a way to build these skins by maven.

***
JSPWiki has 2 "special templates", which you can invoke by adding
&skin=<template> to the url.  (note -- these are *not* skins, but
templates) :
- "&skin=raw" : displays the raw markup of a wiki page
- (new) "&skin=reader" : display the 'naked' page without any clutter. So
no header, footer, sidebar, menu bar;  just the rendered page content.

The haddock template uses the '&skin=reader' to display the help pages
built into the template, like EditPageHelp,LoginHelp or SearchPageHelp.
 These help-pages are displayed as overlay screens, using the %%slimbox
style.



dirk



On Thu, Feb 20, 2014 at 12:35 AM, Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi,
>
> checked haddock template with latest trunk, looks really nice! I especially
> like the fluid layout :-D
>
> regarding the issues found: the sidebar doesn't hide when clicking on the x
> with latest Firefox, but nothing shows up on console. Same happens with
> "More Menu" and "Sidebar" links on the upper-right corner, and I'm also
> unable to upload files
>
> will there be skin (as in default template) support? Related to this
> question, don't know how, but I stumbled upon &skin=reader parameter which
> also was a nice surprise
>
>
> cheers,
> juan pablo
>
>
>
> On Mon, Feb 17, 2014 at 10:58 PM, Dirk Frederickx <
> dirk.frederi...@gmail.com
> > wrote:
>
> > Harry,
> >
> > Tx for testing the new template.
> >
> > - I also noticed some glitches in FF.  (eg sortable tables are not
> working
> > in FF)  I'll do some extra testing.
> >   However, I do not have any issues with the sidebar.
> >   Which version of FF are you using ?  Could you check the js console if
> > any error is shown?
> >
> > - I'll double check the Preferences on FF
> >
> > - As stated, Editor is not really implemented yet, so sneak preview and
> the
> > toolbar are not functional yet.
> >   I'm working on this as the first next thing.
> >
> >
> > Good to get some feedback on look&feel too - although it is a bit more
> > subjective !
> >
> > - 'little space for the content'
> >   Different from the previous template, I adopted the "fixed width" model
> > of bootstrap rather then the fluid.
> >   The result is the large left and right white margins are visible, and a
> > 'jumping' page-width when you resize your window.
> >   A "fluid" page-width (like in the current template) will use the
> maximal
> > screen-width available.
> >   => may be this should become a new user-preference option.
> >
> > - The header & footer size are not much bigger then in the current
> > template, but the darker background tint make
> >   it feel more heavier on the page.
> >   Reducing their size is not obvious as the header also acts as container
> > for the pagename, breadcrumbs, quick-navigation.
> >
> >   I'm still working to reduce some of the header 'clutter': removing the
> > "G'day XYZ" message, reducing the size of the buttons...
> >
> >
> >
> > dirk
> >
> >
> >
> > On Mon, Feb 17, 2014 at 8:54 PM, Harry Metske <harry.met...@gmail.com
> > >wrote:
> >
> > > Dirk,
> > >
> > > (good to see a burst of longstanding JIRA issues being resolved)
> > > I had a look and did some testing with the new template (FF and
> Chromium
> > on
> > > Linux) .
> > > You already stated that we should expect things to be broken, but
> > > nevertheless here are some things I found (and you probably already
> know
> > > of) :
> > >
> > > * on FF the leftMenu (sidebar) cannot be clicked away, not the
> "Sidebar"
> > > link nor the cross in the leftmenu, Chromium works fine here
> > > * Preferences cannot be saved
> > > * when editing a page, all the buttons are not visible (inside the
> yellow
> > > area)
> > > * sneak preview does not work
> > >
> > > About the looks of the template, it's a matter of personal preference
> :-)
> > > In general I think there is too little space left for content:
> > > * it doesn't take the full width of the screen
> > > * the top and bottom blue area's are too large (high)
> > > * the left menu too wide (but it can be clicked away).
> > >
> > >
> > > Thanks for all your efforts.
> > > kind regards,
> > > Harry
> > >
> > >
> > >
> > >
> > > On 14 February 2014 18:27, Dirk Frederickx <dirk.frederi...@gmail.com
> > > >wrote:
> > >
> > > > All,
> > > >
> > > > I've just committed a new Apache JSPWiki Template/UI, "haddock". It
> is
> > > > partly a back-port of various v3.0 template changes, resolving a
> number
> > > of
> > > > long-outstanding JIRA's.  But most visible, it provides a complete
> new
> > > > look&feel, build on top of the popular BOOTSTRAP css framework.
> > > >
> > > > To activate this new template, add following line to your
> > > > jspwiki-custom.properties:
> > > >
> > > >               jspwiki.templateDir = haddock
> > > >
> > > >
> > > > From the change-note:
> > > >          This template contains various UI improvements and JSP
> > > > simplifications,
> > > >          a major redesign of the JSPWiki CSS stylesheet based on
> > > BOOTSTRAP
> > > >          (now modularly build with LESS) and a rework of the
> javascript
> > > > routines
> > > >          based on mootools v1.4.x. (also the js is now split into
> > modular
> > > > class files)
> > > >
> > > >          Be aware: this is a first commit -- expect things to be
> > broken.
> > > >          More work is ongoing on the plain editor; the Group UI is to
> > be
> > > > fixed.
> > > >
> > > >          Validation has been done against Safari, Chrome & FF;  IE
> > > testing
> > > > is left
> > > >          to the adventurous user.
> > > >
> > > >
> > > > I hope you'll like the new looks as much as I do ;-)
> > > >
> > > >
> > > > dirk
> > > >
> > >
> >
>

Reply via email to