[Chandler-dev] Removing plugins and what else for Preview?
Katie Capps Parlante
capps at osafoundation.org
Wed Feb 7 11:48:46 PST 2007
D John Anderson wrote:
> I'm not sure it makes sense to remove all the code that is used in the
> test menu for Preview. For example, do we want to remove the "Check
> repository" code? And removing just the menu items provides only a
> trivial savings in space. I suspect that long term it may be better to
> conditionally compile out the code in the test menu so we can make it
> available to the debug version.
> However, it might be worth a pass through the items in the test menu,
> removing those that are clearly not useful for development.
I agree with John, there are a set of menu items currently in the Test
menuthat we'll want to keep around for end users -- "Check repository"
is a prime example. I don't think we need to "hide" these -- they should
be easily available for us to ask users to try out if we are in some
sort of problem situation.
John, can you list out others that you'd like to see available for
debugging/problem solving purposes?
I'll send a follow up message after the Cosmo QA session with my list.
I have an alpha5 bug to move "test" code into a plugin. I think that
factoring out certain menu items and making them available in the
regular release should be part of that task.
More information about the chandler-dev