Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 37852 invoked from network); 14 Aug 2009 16:36:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Aug 2009 16:36:19 -0000 Received: (qmail 4547 invoked by uid 500); 14 Aug 2009 16:36:25 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 4456 invoked by uid 500); 14 Aug 2009 16:36:25 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 4440 invoked by uid 99); 14 Aug 2009 16:36:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 16:36:25 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates 209.85.220.222 as permitted sender) Received: from [209.85.220.222] (HELO mail-fx0-f222.google.com) (209.85.220.222) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 16:36:15 +0000 Received: by fxm22 with SMTP id 22so1397450fxm.9 for ; Fri, 14 Aug 2009 09:35:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=OQ+t4vpC0kMJrNPlmy/ZKA7BW6mkWHWRkH5WMC1ARzg=; b=hc2buJUZ/zNafzS64bVp0t6kIkhCtbp3KzKVD5Ncc10u/wsrdHfZuGBc2EzdpLAZIf KXaELRbtBvxi7ZZ6Y4C186yOYzu9EL/vUGKuIIKpNbWrI/cI86wXjfLkwZdR8uqRFIy1 Y2MZ+QMijwUF6mYtCGHKKkJt8bDkQDvMhZCeg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=QFEcnFC7g1iM498w5q4pOYr2xeZaqoZHTKXEjnyLjKD9Pv7aY2D24zJofTHicCoh6y 8zCwlmbkhJWwIwef1wZ4KYmsTVhsV1AYi/CrfyJ2y/6wWLvcpVXUFuqH9f1uWHOoDn2D lVliTJua1EN7fAak+CUEd9a9eICIaqWSJt6e4= MIME-Version: 1.0 Sender: pajbam@gmail.com Received: by 10.204.102.16 with SMTP id e16mr421861bko.187.1250267755353; Fri, 14 Aug 2009 09:35:55 -0700 (PDT) In-Reply-To: <4A858DC9.8000102@gmail.com> References: <98d8c0860908140854r383035d6na9b88029591c5822@mail.gmail.com> <4A858DC9.8000102@gmail.com> Date: Fri, 14 Aug 2009 18:35:55 +0200 X-Google-Sender-Auth: e728eb2d402dcedb Message-ID: <98d8c0860908140935s5a55a564h19ca046a278041ef@mail.gmail.com> Subject: Re: [Studio] Cruel dilemma with Editor Open Mode in Studio From: Pierre-Arnaud Marcelot To: Apache Directory Developers List Cc: Apache Directory Users List Content-Type: multipart/alternative; boundary=001636c5a3dd6e968304711ca593 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5a3dd6e968304711ca593 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Kiran, Thanks for this feedback. :) More inline. On Fri, Aug 14, 2009 at 6:16 PM, ayyagarikiran wrote: > > I like to have the double-click mode as default (remembering how many times > entry editor got opened when I accidentally selected an entry in the DIT) Same thing here. And it's even worse if you're using the arrow keys to navigate in the tree. > coming to the consistency, I would prefer to leave the existing behavior as > default if that is possible (may be based on other users' choice too) > Now, here's the hard of the business... Because we're modifying this setting across the whole Eclipse. When you're using the Apache Directory Studio RCP Application, that's not an issue, but when you're in a standard Eclipse distribution, if we modify this setting, this will also affect the other perspective (Java perspective for example). I'm sure it will make our users upset. Maybe what we could propose is a little popup window that is launched when the LDAP, or Schema Editor perspectives are opened. This popup would explain that we're now using this setting and ask the user if he wants to keep its current setting. > thanks for including this feature and other EntryEditor stuff( that I > didn't understand completely ;) ) The Entry Editors stuff is the ability to have multiple editors to choose from for opening entries, like our standard editor, or an LDIF editor which opens the entry as an ldif record you can edit. Or something else... As it is an extension point, anyone will be able to add a new entry editor. Regards, Pierre-Arnaud --001636c5a3dd6e968304711ca593 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Kiran,

Thanks for this feedback. :)

More inline.

On Fri, Aug 14, 2009= at 6:16 PM, ayyagarikiran <ayyagarikiran@gmail.com> wrote:
I like to have the double-click mode as default (remembering how many times= entry editor got opened when I accidentally selected an entry in the DIT)<= /blockquote>

Same thing here. And it's even worse if= you're using the arrow keys to navigate in the tree.
=A0
coming to the consistency, I = would prefer to leave the existing behavior as default if that is possible = (may be based on other users' choice too)

Now, here's the hard of the business..= . Because we're modifying this setting across the whole Eclipse.
<= div>When you're using the Apache Directory Studio RCP Application, that= 's not an issue, but when you're in a standard Eclipse distribution= , if we modify this setting, this will also affect the other perspective (J= ava perspective for example). I'm sure it will make our users upset.

Maybe what we could propose is a little popup window th= at is launched when the LDAP, or Schema Editor perspectives are opened. Thi= s popup would explain that we're now using this setting and ask the use= r if he wants to keep its current setting.
=A0
thanks for including this fea= ture and other EntryEditor stuff( that I didn't understand completely ;= ) )

The Entry Editors stuff is the ability to have multiple= editors to choose from for opening entries, like our standard editor, or a= n LDIF editor which opens the entry as an ldif record you can edit. Or some= thing else... As it is an extension point, anyone will be able to add a new= entry editor.

Regards,
Pierre-Arnaud
--001636c5a3dd6e968304711ca593--