Opinion on service UI?
Opinion on service UI?
- Subject: Opinion on service UI?
- From: "Guy Umbright" <email@hidden>
- Date: Tue, 6 Apr 2004 11:41:59 -0500
- Thread-topic: Opinion on service UI?
I am writing a service, targeted mostly at XCode, that requires
a UI and thus the service is an app rather than a tool and am
in a quandry.
When the service is selected, a window is put up to allow the
user to select an entry. My problem is what to do after that.
1) After making the selection (and the date transfer that goes
along with it) should the service continue running and just
close the window or should the app quit? When idle it wouldn't
really do anything so it wouldn't be much of a resource drain.
2) In theory, if you are going to use the service once, you are
probably going to use it more than once. Is there any requirement
on the lifespan of a service? Single atomic action, or can it be
an extended action?
3) As there may be the need to access the service repeatedly, am
I wrong going with a service? I wanted to use a service so that
I could define a hotkey to facilitate accessing it.
Opinions?
Guy
This electronic mail message and any attached files contain information
intended for the exclusive use of the individual or entity to whom it is
addressed and may contain information that is proprietary, privileged,
confidential and/or exempt from disclosure under applicable law. If you are
not the intended recipient, you are hereby notified that any viewing, copying,
disclosure or distribution of this information may be subject to legal
restriction or sanction. Please notify the sender, by electronic mail or
telephone, of any unintended recipients and delete the original message
without making any copies.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.