[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] p2 update
- From: "Alex Blewitt" <alex.blewitt@xxxxxxxxx>
- Date: Thu, 27 Mar 2008 17:28:49 +0000
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cVZFoNyiSAlHZUlNCUHdSLRQhgtF19njfOeOhHiSlH6zzqAXXF66CCt9OHgAteElgmGgRAOIwqrVGo2KdjzbrV0ROuoTfEkPS6GUU0F9x6StpJPPika6mWvq1hs4sGnfHR7ypawnwKjzq5pqsVmQ1yeWyPxAubzaZYFtp4SAu/8=
On Thu, Mar 27, 2008 at 5:18 PM, Pascal Rapicault
> It is technically possible but we don't have a UI to add such locations and
> will not get to it for 3.4.
> That, said, since one of the goal p2 is to get people out of the file
> system, therefore I would highly suggest to d&d the plugins directly on the
> p2 UI.
Given that Mac apps normally put extensions in these locations, it's
fairly standard places to look. Can they not be coded in by default,
even if the UI isn't there?
I thought that the point of P2 was to have less explicit dependencies
on hard-coded names like 'plugins' and 'features'. If you've got to
have another directory called 'dropins' then it's basically just
exchanged one problem for another.