From adffaces-user-return-454-apmail-incubator-adffaces-user-archive=incubator.apache.org@incubator.apache.org Tue Jul 11 23:49:06 2006 Return-Path: Delivered-To: apmail-incubator-adffaces-user-archive@locus.apache.org Received: (qmail 22850 invoked from network); 11 Jul 2006 23:49:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Jul 2006 23:49:06 -0000 Received: (qmail 64067 invoked by uid 500); 11 Jul 2006 23:49:05 -0000 Delivered-To: apmail-incubator-adffaces-user-archive@incubator.apache.org Received: (qmail 64044 invoked by uid 500); 11 Jul 2006 23:49:05 -0000 Mailing-List: contact adffaces-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: adffaces-user@incubator.apache.org Delivered-To: mailing list adffaces-user@incubator.apache.org Received: (qmail 64032 invoked by uid 99); 11 Jul 2006 23:49:05 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 16:49:05 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mwessendorf@gmail.com designates 66.249.92.173 as permitted sender) Received: from [66.249.92.173] (HELO ug-out-1314.google.com) (66.249.92.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 16:49:03 -0700 Received: by ug-out-1314.google.com with SMTP id u40so54958ugc for ; Tue, 11 Jul 2006 16:48:42 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=VlPGbLjxNcJOwtNQg9wxVNvZudR0jtkMU6NpdrS9WS163yx2a5TaRxL76reuEAvvAQz7APHpsIOiza2JsKF+TPjqdGHUy0iYNbNtFyIesyKO706zDFlXIAXVpzOKllIr79Rs82/75DX6YwqDVm+lJrufoXum4oz77voaYI0A6LE= Received: by 10.67.101.8 with SMTP id d8mr63512ugm; Tue, 11 Jul 2006 16:48:41 -0700 (PDT) Received: by 10.66.240.9 with HTTP; Tue, 11 Jul 2006 16:48:41 -0700 (PDT) Message-ID: <71235db40607111648o30403707l56d2aa242d02dd7f@mail.gmail.com> Date: Tue, 11 Jul 2006 16:48:41 -0700 From: "Matthias Wessendorf" Sender: mwessendorf@gmail.com To: adffaces-user@incubator.apache.org Subject: Re: Re: Tag renaming proposal In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 22529f9bf1e6bf79 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N inputLOV is shorter ... ;) On 7/11/06, Benj Fayle wrote: > I agree that inputListOfValues is better than inputLOV. > > -----Original Message----- > From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of > Matthias Wessendorf > Sent: Monday, July 10, 2006 12:40 PM > To: adffaces-user@incubator.apache.org > Subject: Re: Re: Tag renaming proposal > > Thanks Adam, > > I found this page > > http://www.webdesignpractices.com/ > > and it contains some interesting stuff. > > -Matt > > On 7/9/06, Adam Winer wrote: > > On 7/9/06, Mike Kienenberger wrote: > > > > > > On 7/8/06, Adam Winer wrote: > > > > separator =
, more or less. > > > > spacer takes up some space (horizontal, vertical, or both) with a > blank > > > > area. > > > > > > > > Make sense? > > > > > > Yeah, I would have guessed the same thing if pressed. > > > > > > I'd suggest calling separator horizontalRule (or horizontalLine -- > > > never quite understood the rule part since a rule is for making a > > > line, not the line itself) if that's what it is. > > > > > > It's not - not necessarily.
happens to be the representation > right > > now, and it could be skinned differently. And we might end up > > offering an "orientation" attribute to provide a vertical separator - > so > > "horizontal" is too limiting, at which point I think "separator" is > > better than just "rule" or "line". > > > > > > For reference, the name changes that had some concerns were: > > > > > > navigationPath breadCrumbs > > > > > > navigationTrain train > > > > > > > > > > I haven't used adffaces, so I don't know what either of these > do. > > > > > However, the first set of names seem to imply it's something to > do > > > > > with navigation (menus?). > > > > > > > > > > > > Page navigation, yes. > > > > > > > > BreadCrumbs makes me think it's something > > > > > to do with cookies. Train just draws a blank. I have no > idea what > > > > > a "train" component would be doing. > > > > > > > > > > > > Both of these are, in my experience at least, common names for > > > > two page navigation components; the first commonly looking like: > > > > > > > > Home > Shopping > Computers > MacBook Pro > > > > > > > > ... and the latter for multi-page wizards, like: > > > > > > > > Shipping --- Billing --- Payment -- Verify > > > > > > > > I don't know of other terms for these widgets. > > > > > > I think you're saying that the navigationPath is a multilevel menu. > > > I'd stick with calling it a menu or menuPage or menuItem. > > > > > > > No, it's not a multilevel menu. Check out this page: > > > > http://www.emusic.com/browse/0/b/-dbm/a/0-0/1200000354+546/0.html > > > > ... and the "Home >> Browse >> Jazz" etc.. thing in there. > > > > Breadcrumbs is an extremely common term for this UI piece; check: > > http://www.google.com/search?q=breadcrumbs%20navigation > > ... for an example of how often it comes up. > > > > multipage Wizard makes perfect sense to me. I think that's better > than > > > train. > > > > > > But it's not a wizard in and of itself, so calling it that would be > > a problem. It's merely an indicator of progress through a multipage > > flow. (Train is not nearly as standard a term for this UI). > > > > > > > > > > selectInputText inputLOV > > > > > > > > > > inputListOfValues would be better than inputLOV. > > > > > > > > > > > > I could go either way. > > > > > > > > What's the difference between adf:inputText and adf:inputLOV? > > > > > > > > > > > > > It lets you pop up a dialog window (using the dialog framework) to > pick > > > a > > > > value, > > > > and have that value automatically entered into the field. That > requires > > > a > > > > different base component class - more than just > EditableValueHolder. > > > > > > In that case, it'd probably make sense to stick popup in the name > > > somewhere. inputTextPopup? inputTextPopupList? inputPopupList? > > > > > > > The fact that it put up a popup isn't a rendering detail, it's a > component > > typing > > detail, so putting it at the end of the name goes against the grain. > We > > used > > to have all of these > "components-that-interact-with-the-dialog-framework" > > called "selectInput". InputDialogText comes closer. (And perhaps we > should > > rename the "UIXSelectInput" base class to "UIXInputDialog"?) > > > > -- Adam > > > > > > > -- > Matthias Wessendorf > > futher stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com > -- Matthias Wessendorf futher stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com