Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 31759 invoked from network); 19 Sep 2007 21:52:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Sep 2007 21:52:27 -0000 Received: (qmail 37002 invoked by uid 500); 19 Sep 2007 21:52:18 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 36955 invoked by uid 500); 19 Sep 2007 21:52:18 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 36944 invoked by uid 99); 19 Sep 2007 21:52:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 14:52:18 -0700 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 andrew.rw.robinson@gmail.com designates 64.233.166.177 as permitted sender) Received: from [64.233.166.177] (HELO py-out-1112.google.com) (64.233.166.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2007 21:54:12 +0000 Received: by py-out-1112.google.com with SMTP id u77so701500pyb for ; Wed, 19 Sep 2007 14:51:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=vyab/k4rlEFBtOBVikF+bNqkWll5djbrBPqCCo2zjbw=; b=JrCU7hKFJ0tCpPMP4ZcscPsh7O+aQefKGjdTyTognPt5xm5JdO3WzzjBU8daNhs/vhsxToTJ/lUAwyLFb9SD5Q+pWbvCoIR+/KFjKtXOreWBBZI6J6pN5Tyo3iEyTMzde8YEUfB2sDkL8nGUX0OVPoTGi9MMZmNGx3el4drnVeE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Qz2k5/rrj2ExQvf8D5RbCBiDA0uIc7yTXidIbdWOxe40nV5fPMfKbldYHzYAE/6fs+y6SI9exG6r2e4pKq5mpg/sTq0PeyxiBUa6NZvFA+4I+UHUI7hOJYEE5o4SUJ4ypiK+2I9yAcwhx8kjBbdhF8doSVWgQpCmninbcrU/VC0= Received: by 10.35.115.18 with SMTP id s18mr1322996pym.1190238712576; Wed, 19 Sep 2007 14:51:52 -0700 (PDT) Received: by 10.35.65.16 with HTTP; Wed, 19 Sep 2007 14:51:52 -0700 (PDT) Message-ID: Date: Wed, 19 Sep 2007 15:51:52 -0600 From: "Andrew Robinson" To: "MyFaces Development" Subject: Re: svn commit: r576576 [1/3] - in /myfaces/trinidad/trunk/trinidad: trinidad-build/src/main/resources/META-INF/maven-faces-plugin/components/trinidad/core/ trinidad-impl/src/main/java/org/apache/myfaces/trinidadinternal/renderkit/core/xhtml/ trinida In-Reply-To: <6dac79b90709191424x6f4cc35bia30d012fd189d0f2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <71235db40709180756x7b355570sf28f7dfa117a58d7@mail.gmail.com> <71235db40709180954s39856756hc33cb213d6ae3892@mail.gmail.com> <254acf980709180958m2b080a9l807776565c553b01@mail.gmail.com> <254acf980709181018o497c4a96vf9820c7f84fd3458@mail.gmail.com> <6dac79b90709181517g424c5b75vb547172e01126550@mail.gmail.com> <254acf980709190913i6dce9618w95bfa4e7a2d39e85@mail.gmail.com> <6dac79b90709190922v4d3663d5t3e72830ba858856b@mail.gmail.com> <6dac79b90709190924jfe2b476oe3cccdf058937daf@mail.gmail.com> <103ac640000067ad@gdc4s.com> <6dac79b90709191424x6f4cc35bia30d012fd189d0f2@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On the vote for set a facet = no icons, someone could easily: This way they can sill use the icon. Just requires more typing On 9/19/07, Adam Winer wrote: > On 9/19/07, Perkins, Nate-P63196 wrote: > > Yes, but why pollute the page unnecessarily with an empty outputText? > > Indeed. (I'd probably use a tr:group, but same deal). > > The flip side is wondering how much of a pain it'd be to > implement "I want to change the ready icon, but not the busy icon" > if we go with "set either facet, both icons are gone". Either design > makes someone's life hard... which do we think is more common? > > > If I approach the subject from a maintainability perspective, I think > > its more intuitive for the documentation to state why the icon is gone > > then to have to figure out why some developer stuck an empty outputText > > into a facet. > > Anyone hacking in either case does have the option of > including a comment in the page, ya know! > > -- Adam > > > > > I've been watching this thread, so I hope you don't mind my 2 cents.... > > > > > > Nate Perkins > > General Dynamics C4 Systems > > > > >This email message is for the sole use of the intended recipient(s) and > > may contain GDC4S > > > confidential or privileged information. Any unauthorized review, use, > > disclosure or distribution > > > is prohibited. If you are not an intended recipient, please contact > > the sender by reply email and > > > destroy all copies of the original message. > > > > > > > -----Original Message----- > > From: Adam Winer [mailto:awiner@gmail.com] > > Sent: Wednesday, September 19, 2007 9:24 AM > > To: MyFaces Development > > Subject: Re: svn commit: r576576 [1/3] - in > > /myfaces/trinidad/trunk/trinidad: > > trinidad-build/src/main/resources/META-INF/maven-faces-plugin/components > > /trinidad/core/ > > trinidad-impl/src/main/java/org/apache/myfaces/trinidadinternal/renderki > > t/core/xhtml/ trinida > > > > OK, five seconds more consideration, and now I'm torn. > > It's easy enough to write: > > > > > > Loading... > > > > > > > > ... which would have the same effect. So I could really > > go either way. > > > > -- Adam > > > > On 9/19/07, Adam Winer wrote: > > > I see what you're saying... I think I'd be OK then with a rule > > > where specifying either facet gets rid of both icons. Especially > > > with a bit of doc explaining why it does that (exactly the example > > > you give). > > > > > > -- Adam > > > > > > > > > > > > On 9/19/07, Simon Lessard wrote: > > > > Hello Adam, > > > > > > > > On 9/18/07, Adam Winer wrote: > > > > > I think it should be as simple as for each of "busy" and > > > > > "ready", render the facet if it's present, the icon if it's not. > > > > > > > > The only issue with that behavior is most common usage. I think the > > most > > > > common usage with facets is going to be a "busy" facet and no > > "ready" (to > > > > mimic GMail behavior for example). Personally, that's the way I > > would use > > > > it. If that's really the most common case, then it should be "as > > soon as a > > > > facet is specified, rendered or not, no icon will be rendered". But, > > if we > > > > think the most common case is going to be with both facets, then I > > agree > > > > with your suggestion. > > > > > > > > ~ Simon > > > > > > > > > > > > > -- Adam > > > > > > > > > > > > > > > On 9/18/07, Simon Lessard < simon.lessard.3@gmail.com> wrote: > > > > > > Hmm not as simple as I though. Before pushing a patch let decide > > on the > > > > > > behavior for every use case: > > > > > > > > > > > > Both facets are specified and rendered --> Don't render any icon > > > > > > Both facets are specified but only one is rendered --> ? > > > > > > Both facets are specified but neither are rendered --> ? > > > > > > Only one facet is specified and rendered --> Don't render any > > icon or > > > > > > render the icon of the missing facet? > > > > > > Only one facet is specified but not rendered --> ? > > > > > > No facet is specified --> Render both icons > > > > > > > > > > > > ~ Simon > > > > > > > > > > > > > > > > > > On 9/18/07, Simon Lessard < simon.lessard.3@gmail.com> wrote: > > > > > > > Or put tr:icon in the facet. Yeah, that sound good too. > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 9/18/07, Matthias Wessendorf < matzew@apache.org> wrote: > > > > > > > > that sounds like the best solution. > > > > > > > > > > > > > > > > On 9/18/07, Adam Winer < awiner@gmail.com > wrote: > > > > > > > > > IMO, if we have a facet, we don't render the icon. No > > need > > > > > > > > > for an attribute at all. > > > > > > > > > > > > > > > > > > Anyone that desperately needs both the facet and the icon > > > > > > > > > can render two statusIndicators. > > > > > > > > > > > > > > > > > > -- Adam > > > > > > > > > > > > > > > > > > > > > > > > > > > On 9/18/07, Matthias Wessendorf < matzew@apache.org> > > wrote: > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > On 9/18/07, Simon Lessard < simon.lessard.3@gmail.com > > > wrote: > > > > > > > > > > > Speaking of which, I forgot to add skin documentation. > > I'll do > > > > > > that right > > > > > > > > > > > away. > > > > > > > > > > > > > > > > > > > > > > I would also like to add a new attribute to skip the > > icon > > > > > > rendering. If it > > > > > > > > > > > hasn't been of backward compatibility, I would have > > simply > > > > removed > > > > > > them > > > > > > > > > > > > > > > > > > > > I added a demo usage of the facet's, I was thinking, > > that it > > > > > > shouldn't > > > > > > > > > > render the "default" icon, > > > > > > > > > > glad you pointed it out now. > > > > > > > > > > > > > > > > > > > > > since it's easily doable with a combination of facet > > and > > > > tr:icon, > > > > > > but since > > > > > > > > > > > we had a release with the statusIndicator already, > > that's out > > > > of > > > > > > question. > > > > > > > > > > > So, what I need now is a decent attribute name. What > > do you > > > > think > > > > > > of > > > > > > > > > > > "renderIcon" or "renderFacetsOnly"? > > > > > > > > > > > > > > > > > > > > I tend to like renderFacetsOnly, because that what you > > added > > > > where > > > > > > facets. > > > > > > > > > > > > > > > > > > > > Perhaps, we can change that soon, that when facet's are > > > > specified, > > > > > > we > > > > > > > > > > don't render the "default" icon. > > > > > > > > > > > > > > > > > > > > -Matthias > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ~ Simon > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > Matthias Wessendorf > > > > > > > > > > > > > > > > > > > > further stuff: > > > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > > > > > > mail: matzew-at-apache-dot-org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Matthias Wessendorf > > > > > > > > > > > > > > > > further stuff: > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > > > > > mail: matzew-at-apache-dot-org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >