[Chandler-dev] Removing plugins and what else for Preview?

D John Anderson john at osafoundation.org
Wed Feb 7 11:18:30 PST 2007


On Feb 7, 2007, at 10:26 AM, Heikki Toivonen wrote:

> Philippe Bossut wrote:
>> The issue is the extra workload to package the tools and plug-ins.  
>> Kind
>> of tight to get that done for Preview but may be not critical to get
>> done by then (the ones who want those tools are likely devs and  
>> can sync
>> up with svn and build... I might be a little optimistic/cavalier here
>> though...).
>
> It's actually less work than you'd think, and I've offered to do it
> myself. It is just manually selecting the files and building zip  
> files -
> not hard, and can be done in a couple of hours. It can be done  
> after the
> Preview is out (we'll just add some links to the files later).

Would it be easy for developers to unzip the files, or download them  
and have the parcels appear? I think having some way for developers  
to use the parcels is important.

>
> Removing the Test and Experimental menus would be a little bit more
> work. Ideally the Experimental menu appeared automatically if there  
> are
> any plugins. The test menu would also need some special handling. I'd
> say this can be done in 3 days.

I think I could implement showing or hiding the test menu with a  
command key in much less than a day



More information about the chandler-dev mailing list