Return-Path: Delivered-To: apmail-incubator-jspwiki-dev-archive@locus.apache.org Received: (qmail 42255 invoked from network); 31 Jan 2008 21:39:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Jan 2008 21:39:00 -0000 Received: (qmail 3512 invoked by uid 500); 31 Jan 2008 21:38:51 -0000 Delivered-To: apmail-incubator-jspwiki-dev-archive@incubator.apache.org Received: (qmail 3459 invoked by uid 500); 31 Jan 2008 21:38:51 -0000 Mailing-List: contact jspwiki-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jspwiki-dev@incubator.apache.org Delivered-To: mailing list jspwiki-dev@incubator.apache.org Received: (qmail 3434 invoked by uid 99); 31 Jan 2008 21:38:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2008 13:38:51 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Janne.Jalkanen@ecyrd.com designates 193.64.5.122 as permitted sender) Received: from [193.64.5.122] (HELO mail.ecyrd.com) (193.64.5.122) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2008 21:38:34 +0000 Received: from [192.168.0.12] (cs181005170.pp.htv.fi [82.181.5.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.ecyrd.com (Postfix) with ESMTP id A9CF7483DC for ; Thu, 31 Jan 2008 23:38:10 +0200 (EET) Mime-Version: 1.0 (Apple Message framework v753) In-Reply-To: <47A23DFC.5040609@altheim.com> References: <47A124A2.4030300@altheim.com> <15cc92000801302241k6a037137rde92fd170b95669f@mail.gmail.com> <47A18AB5.5070209@altheim.com> <47A19A55.8060303@altheim.com> <15cc92000801311150l23077fbfk357add578d700ed1@mail.gmail.com> <47A23DFC.5040609@altheim.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Janne Jalkanen Subject: Re: What happened to TitleBlock.jsp? Date: Thu, 31 Jan 2008 23:37:49 +0200 To: jspwiki-dev@incubator.apache.org X-Mailer: Apple Mail (2.753) X-Virus-Checked: Checked by ClamAV on apache.org Let's discuss this in the 2.8 scope. I don't want to confuse 2.6.1 with a major change like this. Murray, the templating system should take care of this for you. Just create your own ViewTemplate.jsp and add a TitleBlock there. Or create your own Header.jsp. I don't see this as something which should be added to the default template, since we already have a nice extensibility mechanism for exactly these kinds of proprietary needs. /Janne On 31 Jan 2008, at 23:30, Murray Altheim wrote: > Dirk Frederickx wrote: >> Murray, >> What are the things you can do with the TitleBlock.jsp and can't do >> with a wiki page ? > > Well, there's at least two things: > > 1. You can do anything a JSP can do that a wiki page can't do, which > as you know is quite a lot. This is about a lot more than simply > formatting. Via use of markup and JSP-based code it's certainly > possible to design more complicated text and graphics for a site > header, which is by far the most common design component of a > corporate (e.g., government, commercial, education) web site. > Most > corporate entities want to be able to distinctly brand their > sites, > and this is by far the best means to guarantee site branding. > > 2. You can set a title block with complex formatting and information > that you DON'T want edited by anyone and is likely designed by an > outside design contractor, since it is part of corporate > identity. > For example, for one of my projects I'll be handing over the > complete design of the title block to a design firm. We don't > want either site admins or wiki users to be able to edit the JSP > after the design is complete. So this is also about having > control > over the title block. > >> When you need to go and change your jsp's , just to be able to have a >> new newsmessage on your site, is not very practical. > > Once a site is up I *never* need to change the title block JSP. That's > the entire point of having it. If I want a news message to occur in > the title block I can include a news page or code to incorporate a > news feed (ala The Guardian's scrolling text) via JSP, something I > can't do via wiki text. I'd generally want that news information to > be processed and/or formatted especially for a very specific part of > the header, not simply be wiki text that is mixed in with the brand > information. > >> There has never been a TitleBlock.jsp in cvs. I opted to go for a >> wiki-page from the start. Sorry that this was not clear to you. > > In the discussions from last year that did not seem to be the case. I > was under the impression (confirmed by reading the emails again) that > there was agreement that the title block was a good idea, and that it > was only due to my failure that it's not currently in CVS. Is this to > your mind a closed issue? I thought that this was a team effort and > that we all had input. > > Given that when the title block is by default hidden this has > literally > no impact in the existing design, could we please add it to the > design? > It's the addition of one very simple JSP to the package, one line in > Header.jsp to include it, and a single CSS statement to hide it. The > wiki page approach does not work for any site that requires strong > branding or requires JSP features, i.e., beyond what a wiki page and > CSS alone can provide (which is for all of my clients minimal). > > Murray > > ...................................................................... > ..... > Murray Altheim > === = = > http://www.altheim.com/murray/ > = = === > SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk > = = = = > > Boundless wind and moon - the eye within eyes, > Inexhaustible heaven and earth - the light beyond light, > The willow dark, the flower bright - ten thousand houses, > Knock at any door - there's one who will respond. > -- The Blue Cliff Record