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

Katie Capps Parlante capps at osafoundation.org
Wed Feb 7 12:23:13 PST 2007


Katie Capps Parlante wrote:
> 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.
> https://bugzilla.osafoundation.org/show_bug.cgi?id=4617

I think we want to make these items available as debugging/dogfooding 
tools, out-of-the-box:

Repository -> (check, repair, compact and index)
Logging -> show log window, logging level
Start Logging (event logger)

i18n -> show i18n manager debug window?

Cheers,
Katie


More information about the chandler-dev mailing list