Return-Path: Delivered-To: apmail-incubator-pivot-user-archive@minotaur.apache.org Received: (qmail 88534 invoked from network); 24 Jul 2009 15:00:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Jul 2009 15:00:27 -0000 Received: (qmail 69463 invoked by uid 500); 24 Jul 2009 15:01:32 -0000 Delivered-To: apmail-incubator-pivot-user-archive@incubator.apache.org Received: (qmail 69444 invoked by uid 500); 24 Jul 2009 15:01:32 -0000 Mailing-List: contact pivot-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: pivot-user@incubator.apache.org Delivered-To: mailing list pivot-user@incubator.apache.org Received: (qmail 69435 invoked by uid 99); 24 Jul 2009 15:01:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2009 15:01:32 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sandro.martini@gmail.com designates 209.85.219.207 as permitted sender) Received: from [209.85.219.207] (HELO mail-ew0-f207.google.com) (209.85.219.207) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2009 15:01:24 +0000 Received: by ewy3 with SMTP id 3so1398866ewy.12 for ; Fri, 24 Jul 2009 08:01:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=+eHNmUtW5UDskJ+6hOrfqhToE1njULLi0gSAAiRdVjw=; b=voGlupeNQ4FRZBCvpgdHFWeqSe0dSR6gbamnRCO6dH7yP/Y9IZmeE2FslN/k6Gs5B7 PUNdkBXTww167w/ODYL/9YMmqteqvUDN9EnYFGZfkOzPtKN5Iz+SfpSnXpPXo8EaSCxt 3KKTciHMP354twxSKf/jIpinZlGBxfSue5MVY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Y+i7j7iQBTdDNtynIAQz/kkq2C2HzPABbco5Agm1BTBIbPotwijNGcsp2zZHCaWvda VKnanrsFI2Yz0mIWudhCuBVccwOB2eBUs8dLfraTOiAHnXkrsPYwJNuipjrU0MoujUuZ WhMtHd9qgdpXhMbMJPI2jxWGOVfmqKkLmvBl0= MIME-Version: 1.0 Received: by 10.210.86.1 with SMTP id j1mr1121484ebb.61.1248447663134; Fri, 24 Jul 2009 08:01:03 -0700 (PDT) In-Reply-To: References: <63761693289438436711870497881942453783-Webmail@me.com> Date: Fri, 24 Jul 2009 17:01:03 +0200 Message-ID: Subject: Re: Usability in Pivot Applications for Data Entry From: Sandro Martini To: pivot-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, >> And to apply also to first field in any form can i define in the >> "global" space ? > > Not sure what you mean by this. Instead of defining shortcuts for these elements in "local" spaces (inside the related screen) at this point I think it's possible to define them inside the "global" space, but using different shortcuts) ... also if they aren't main application elements. > Spinner already handles key events. After thinking about it more, I'm not > sure if we would want to add platform support for keyboard-navigating tab > panes and accordions, since a) I'm not sure what the right generalization > might be and b) it's easy enough to do in application code. Either way, you > can do this pretty easily. Ok, if available it's better, otherwise no problem. My trouble here is to ensure that all Pivot Components are ready to work in this way (as an optional behavior), so developers can only use existing functions or attach their code to standard framework events. And on the focus passing between components (like fields in the same form) for example after writing a code in a field, pressing or when the data inside the field has been automatically validated, will it be possible with an event to trigger, right ? And the same for example also writing data in a Table ... where for example goes to the next cell or row in the table (after optional validation of cell contents). > You could always display the shortcut next to the field, or as a tooltip, or > when the user presses some key combination that means "show me the shortcut > keystrokes"... Yes, I like this idea. Thanks again, Sandro