Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 76700 invoked from network); 12 Aug 2009 20:23:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Aug 2009 20:23:57 -0000 Received: (qmail 38230 invoked by uid 500); 12 Aug 2009 20:24:04 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 38139 invoked by uid 500); 12 Aug 2009 20:24:03 -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 38131 invoked by uid 99); 12 Aug 2009 20:24:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Aug 2009 20:24:03 +0000 X-ASF-Spam-Status: No, hits=4.6 required=10.0 tests=FH_HELO_EQ_D_D_D_D,HELO_DYNAMIC_IPADDR,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [92.51.130.250] (HELO lvps92-51-130-250.dedicated.hosteurope.de) (92.51.130.250) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Aug 2009 20:23:54 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by lvps92-51-130-250.dedicated.hosteurope.de (Postfix) with ESMTP id B1CFC11744006 for ; Wed, 12 Aug 2009 20:23:33 +0000 (UTC) Message-ID: <4A8324C4.1050806@apache.org> Date: Wed, 12 Aug 2009 22:23:32 +0200 From: Stefan Seelmann User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [Studio] Adding extensibility to Entry Editor References: <98d8c0860908100900r68b51701n73c92afddc8a63ac@mail.gmail.com> <98d8c0860908120530x5aaf123fwfafc08c4fb6502f8@mail.gmail.com> In-Reply-To: <98d8c0860908120530x5aaf123fwfafc08c4fb6502f8@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Pierre-Arnaud Marcelot wrote: > Let's say the user has re-organized the Entry Editors and he adds a new > plugin that has a new entry editor. > At the next launch of Apache Directory Studio, we'll notice that a new > Entry Editor is available, but what should we do with it ? Where should > we place it in the Entry Editors order ? > > I think we should discard the priority information since the user has > defined his own order and that this new editor should be placed at the > end of the list. > Yes, I agree. Perhaps we could prompt the user about the new available Entry Editor and ask him/her to check the order in the prefernce page? Kind Regards, Stefan