
IAM
====
Name:		Command Assistant
Submitter:	Pu Chen
Owner:		James Carlson
Intern:		Mark Martin <storycrafter@gmail.com>
Interest:	gto-ext@sun.com, pu.chen@sun.com
Status:		commitment scheduled 02/25/2009
Comment:	inception scheduled 01/21/2009
Comment:        waiting need spec
Exposure:	open
Comment:	Derailed by James Carlson; was sponsored by Yong Sun

SUMMARY
=======



ISSUES
=======

 PSARC/2008/772:	Command Assistant
 Submitter:	Pu Chen
 Owner:		James Carlson
 Intern:	Mark Martin <storycrafter@gmail.com>
 Exposure:	open
  
 Issues for commitment (02/25/2009):
 
 seb-1	Your application is running in the background and displaying
 	an icon in the notification area of the Gnome panel.  Why did
 	you decide to implement the UI this way rather than have an
 	applet directly on the panel (e.g. like the deskbar applet)?
 
 seb-2	The fact that there's an icon in the notification area implies
 	that someone had to somehow enable or start this UI before
 	being able to interact with the search popup.  What is the
 	interface through which this was done, and how can it later be
 	disabled?
 
 seb-3	When this is enabled, what's the impact on the overall system?
 	Is there a giant JVM constantly running in the background that
 	does nothing 99.9% of the time just in case someone might type
 	something in the dialog?  Or is the impact less severe where
 	something is launched only when someone clicks on an icon?  In
 	general, users are not very keen on having large memory
 	intensive processes running that are effectively doing
 	nothing.
 
 ram-2	I thought we had discussed in the inception meeting means
 	of adding to the population of documents Command Assistant
 	could use (in the format understood by Command Assistant).
 	This problem could be attacked from several fronts:
 	1) require FOSS projects with appropriatly formed documentation
 	   expose that documentation.
 	2) encourage OpenSolaris projects to use this form of documentation
 	3) encourage a project to convert any existing man pages to be
 	   in suitable format.
 	I'm not suggesting the project undertake any of these steps, but
 	perhaps develop a best practice for any or all of the three fronts
 	described.
 
VOTE
====
Approve - 
Deny - 
Abstain - 
Not Participating (NP) - 



THE NEXT STEP
=============
The way the UI interacts with the toolbox.
The team is going to reimplement the UI and the applet mechanism.
Christoph's explanation resolved the issues above.

ARC is happy with change of direction. 
Project team needs to update the documentation to note the change of direction.

Update spec to include GUI changes.
Add xx info as part of interface spec as external file.

Mark to work with Garrett/Jim on opinion fodder.

Follow up for a vote for when project team is ready.
