Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1377AC7B6 for ; Tue, 18 Jun 2013 12:17:40 +0000 (UTC) Received: (qmail 91898 invoked by uid 500); 18 Jun 2013 12:17:38 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 91819 invoked by uid 500); 18 Jun 2013 12:17:36 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 91811 invoked by uid 99); 18 Jun 2013 12:17:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jun 2013 12:17:35 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of orwittmann@googlemail.com designates 74.125.83.50 as permitted sender) Received: from [74.125.83.50] (HELO mail-ee0-f50.google.com) (74.125.83.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jun 2013 12:17:30 +0000 Received: by mail-ee0-f50.google.com with SMTP id d49so2430691eek.37 for ; Tue, 18 Jun 2013 05:17:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=cQ5hug6Ox9qq4Qf5XwAXud5Qen71QRMz4THPxfc/MuU=; b=K68esCsj49YpT4/e8UkN9AxDooSeFwjGykn2Q6JsTby6hoVMAK3/9qqUiY7ZgRuUFg YiD1SQuU/TpAEY3eiMX47qk61/fMW43hxr4fH5QCkYLcTnI6+VkYoh3Y0VgnKK9SRpJJ PNuX34n0PTEcQHjevBGFTB4Zj+94Pf3qWj9u5mGzcEyyqAqKXa4orL4GCjTtxbcjg5iI h8CjTp5POT3rtZ09HjBoOjtcwwCPOypmJfJLEYONil5q3Bun1eVXpFQP/zgOnkxgYZxU Uvy42yDPGcBe0EWVkRmQfvGXZtxXiT2/UYMlSB7VdrQTmqjDl7qf+mr0HOVVjtVuDask +ZOw== X-Received: by 10.14.210.134 with SMTP id u6mr22221766eeo.62.1371557828931; Tue, 18 Jun 2013 05:17:08 -0700 (PDT) Received: from [9.155.131.48] (deibp9eh1--blueice1n1.emea.ibm.com. [195.212.29.163]) by mx.google.com with ESMTPSA id y10sm30177172eev.3.2013.06.18.05.17.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Jun 2013 05:17:08 -0700 (PDT) Message-ID: <51C04FC3.8010706@googlemail.com> Date: Tue, 18 Jun 2013 14:17:07 +0200 From: Oliver-Rainer Wittmann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: dev@openoffice.apache.org Subject: Re: [AOO 4.0]: migration of AOO 3.4.x/OOo 3.x user profile data - help needed References: <51A4C8D8.5000406@googlemail.com> <51A6159B.80403@googlemail.com> <51AB29D9.6020108@apache.org> <51AC5806.9000004@googlemail.com> <000c01ce6148$a23ab8a0$e6b029e0$@zybura.com> <1D35A2254CFC4DD3B23B9725BEA40777@gmail.com> <51AE4768.7070001@laposte.net> <95B5D6E9B67E4D4591709E8F00B32200@gmail.com> <51AE5C0E.7070401@laposte.net> <51AF3C35.8060309@googlemail.com> <51AF9B1D.90804@laposte.net> <51BA3D50.2070705@apache.org> <51BEC0F0.3010600@googlemail.com> <51C00BBB.6090406@apache.org> <51C01192.3030203@googlemail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 18.06.2013 13:36, Rob Weir wrote: > On Tue, Jun 18, 2013 at 3:51 AM, Oliver-Rainer Wittmann > wrote: >> Hi, >> >> >> On 18.06.2013 09:26, Andrea Pescetti wrote: >>> >>> On 17/06/2013 Oliver-Rainer Wittmann wrote: >>>> >>>> I want to let you know that I am currently working on the migration of >>>> AOO 3.4.x/OOo 3.x user profiles to AOO 4.0. I am also including the >>>> migration of extensions. >>>> I am currently not planning to adjust any of the mentioned strings as I >>>> think it is too late for its translation. >>> >>> >>> Is this safe? In a typical scenario, then, a user would have some >>> extensions installed and he would see them imported in 4.0 without being >>> warned about possible compatibility problems. Most of the extensions do >>> not have a maxversion indication, so OpenOffice 4.0 will try and install >>> them anyway, but some might be broken. And then the user is left alone >>> in updating his extensions (which in theory he should be prompted to do >>> after installation, assuming this mechanism is restored), but he >>> wouldn't have a way to go back before it's too late. >>> >> >> I had a close look at the functionality to 'migrate the extensions from a >> former user profile' and from my point of view we should give it a try. >> >> The function did the following: >> It looks for the extensions which are installed for the user. These are >> found in the former user profile. No shared-installed, bundled or >> pre-registered extensions are considered. The found user-installed >> extensions which are not on the blacklist are installed with the same >> mechanism which is used when the users triggers in the installation. >> I am activating an user interaction in case that an extension is already >> installed - the same user interaction which is used when the user triggers >> the installation of an already installed extension. >> >> On the blacklist will be the Presenter Screen and the Presentation Minimizer >> as they are now integrated into OpenOffice. >> > > Is the blacklist a static list? Or is it something that can be > retried/updated from the website? > The blacklist is part of our source code. These are corresponding entries in a XCU file - namely main/officecfg/registry/data/org/openoffice/Setup.xcu Have a look at my commit - revision 1494066 [1]. Search for 'ExcludedExtensions' [1] http://svn.apache.org/r1494066 > If we can make the blacklist be "live" in a document that we can > update, this is like maintaining our own max version field for the > cases where the extension author neglected to do so. > Such a feature is possible. It could be corresponding XML feed which OpenOffice could be accessed via the Internet - like the XML feed for the update service. Best regards, Oliver. > -Rob > > >> >> >>>> If my tests work fine, I will check-in the changes this week. If we will >>>> include these changes into our AOO 4.0 release, I will help to update >>>> the above wiki page. >>> >>> >>> Let's keep them documented and see. Remember that we learned so far that >>> a random user will manage to reinstall but not to do anything more >>> elaborated, so if uninstallation/installation does not bring up a "Do >>> you want to reset your profile?" dialog we still have a usability >>> problem (which of course is not a regression, it's been there forever). >>> >> >> Agreed. >> >> >> Best regards, Oliver. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org >> For additional commands, e-mail: dev-help@openoffice.apache.org >> > > > > -- > Opinions expressed in this communication reflect the author's > individual personal view, not necessarily that of an amorphous > collective. The above statements do not reflect an official position > of any organization, corporation, religion (organized or disorganized) > or national football association. The contents of said note are not > guaranteed to have been spell checked, grammar checked or reviewed for > metrical infelicities. The contents of this post may not be suitable > for those whose native language is not logic. Caution should be > exercised when operating heavy machinery when reading this note, or > even when not reading it. Seriously, heavy machinery is dangerous. > Be careful. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org > For additional commands, e-mail: dev-help@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org For additional commands, e-mail: dev-help@openoffice.apache.org