Return-Path: X-Original-To: apmail-roller-user-archive@www.apache.org Delivered-To: apmail-roller-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F0817102D4 for ; Tue, 10 Dec 2013 17:49:26 +0000 (UTC) Received: (qmail 33035 invoked by uid 500); 10 Dec 2013 17:49:25 -0000 Delivered-To: apmail-roller-user-archive@roller.apache.org Received: (qmail 32955 invoked by uid 500); 10 Dec 2013 17:49:20 -0000 Mailing-List: contact user-help@roller.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@roller.apache.org Delivered-To: mailing list user@roller.apache.org Received: (qmail 32930 invoked by uid 99); 10 Dec 2013 17:49:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Dec 2013 17:49:19 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [15.193.32.61] (HELO g6t0184.atlanta.hp.com) (15.193.32.61) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Dec 2013 17:49:12 +0000 Received: from G9W0364.americas.hpqcorp.net (g9w0364.houston.hp.com [16.216.193.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t0184.atlanta.hp.com (Postfix) with ESMTPS id CED7BC005 for ; Tue, 10 Dec 2013 17:48:50 +0000 (UTC) Received: from G9W3616.americas.hpqcorp.net (16.216.186.51) by G9W0364.americas.hpqcorp.net (16.216.193.45) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 10 Dec 2013 17:48:01 +0000 Received: from G9W0764.americas.hpqcorp.net ([169.254.11.46]) by G9W3616.americas.hpqcorp.net ([16.216.186.51]) with mapi id 14.03.0123.003; Tue, 10 Dec 2013 17:48:01 +0000 From: "Hertling, William E" To: "user@roller.apache.org" Subject: Re: Bug in tag cloud in fauxcoly Thread-Topic: Bug in tag cloud in fauxcoly Thread-Index: AQHO9bWq41/BuAz2tEeQoqHJoF3az5pNioGAgAAIEACAABd/AP//hFUA Date: Tue, 10 Dec 2013 17:48:01 +0000 Message-ID: In-Reply-To: <52A74B0C.6040000@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [16.216.12.38] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org How do I get off this mailing list? On 12/10/13, 9:10 AM, "Glen Mazza" wrote: >I meant the template guide, not the user guide. > >Glen > >On 12/10/2013 10:46 AM, Gaurav wrote: >> Hello Glen, >> >> I looked into user guide at >> https://svn.apache.org/repos/asf/roller/trunk/docs/roller-user-guide.odt >> This user guide did not have Section 7.7. If I am mistaken Can you >> please provide me correct url to the latest doc >> >> Thanks >> Gaurav >> >> >> On Tuesday 10 December 2013 08:47 PM, Glen Mazza wrote: >>> I haven't looked into tag clouds yet. How to build them is described >>> in Section 7.7 of the latest (5.1.0-SNAPSHOT) Roller guide. If >>> there's a bug in the template (or the guide), please enter a JIRA for >>> it, and if you can supply a patch to fix it that would be great. >>> >>> Thanks, >>> Glen >>> >>> On 12/10/2013 09:39 AM, Gaurav wrote: >>>> Hello, >>>> >>>> The tag cloud did not increase the size of text with the intensity >>>> of tags used. >>>> >>>> Velocity Code (In this the tags which have count > 5 will be shown) >>>> >>>> #set($mytags =3D $model.weblog.getPopularTags(-1, 30)) >>>> #foreach ($tag in $mytags) >>>> #if ($tag.count > 5) >>>> >>> title=3D"$tag.count">$tag.name 3232 >>>> #end >>>> #end >>>> >>>> The class used for increasing the tags size are s1,s2,s3,s4,s5. As >>>> the tag intensity is between (1-5) and tag with 1 count has >>>> intensity 1 and similarly untill 5. Tags with count greater than 5 >>>> has intensity 5. >>>> So as the #if condition says tags with count > 5 will be shown, then >>>> all the will have same class s5 and there will be no difference in >>>> font size. >>>> >>>> I think, I was able to communicate what I want to explain. Can >>>> anyone please look into this ? >>>> >>> >> >> >