Community
Participate
Working Groups
Created attachment 76139 [details] Call View The Call API is in need of user interface elements for notification about incoming calls, as well as to edit volume etc. of an ongoing call. This bug should gather ideas surrounding that topic. I have created a preliminary CallView which sketches a possible solution. Additional ideas might be a popup window, a preference page and there a like.
I don't really like 'Output Volume' myself although 'Speakers' isn't that great either. And yeah, you probably want this to be configurable from the preference page.
(In reply to comment #1) > I don't really like 'Output Volume' myself although 'Speakers' isn't that great > either. And yeah, you probably want this to be configurable from the preference > page. > I think there are three categories of call parameters/controls needing/requiring UI 1) parameters that are relevant to a specific call/session (e.g. initiator/receiver/Call Details as in https://bugs.eclipse.org/bugs/attachment.cgi?id=76139 an) 2) parameters that are applicable to all calls that are only changed rarely/never (e.g. default speaker/microphone volume levels, sound device setup/testing, ring tones, etc) 3) parameters that are applicable to all calls that are changed on a regular basis (current speaker/microphone volume/gain levels) For 1, we'll need UI that allows the presentation of info from any ICallSession (no matter what provider), that a) allows/gracefully shows multiple simultaneous instances (for multiple calls) b) does not take up too much space on screen/make things too cluttered c) is visually appealing d) provides sufficient notification/input to allow users to understand what is going on with multiple call sessions e) has as few UI dependencies as possible (so that it can be run in as many environments as possible (e.g. RCP, Eclipse, others) f) ideally supports/allows subclassing, service, and/or extension points, so that others can easily build upon it I think the hard UI issues are the requirement for 'a', 'b', 'c', combined with 'd'. I like Moritz' form interface in this regard, although I'm not sure whether the 'tab' in a view is the best way to handle 'a'...as if one tab is occluded, there is not much ui mechanism available to give the user notifications (e.g. of call being dropped, or activity from remote participant) For 2, I suspect that these parameters are most appropriately handled through preferences (under ECF Communications category...probably a new preference category for 'VOIP', or 'Telephony') For 3, I think that we'll probably need preference pages, but *also* some way to either link the UI from 1 to the preference page, or perhaps controls on both the UI for 1 and for the preference pages for 2. Well, that's my $0.03. I think Moritz has a good start, but I would like to jointly think a little bit about 'a' in particular, because in one sense this is very similar to the problems of presenting multiple text chats/IM dialogs and merging them into a single UI (i.e. bug #183027 and bug #195752) ...they are all conversations with 1 or more others...using different media (text and/or voice). Also adding Boris Bokowski and zx to this thread...hopefully they will also have some thoughts and input.
Assigning to Moritz. Moritz has a simple call view as shown in attachment. This code can/should be contributed to org.eclipse.ecf.telephony.ui bundle.
Setting to possible target milestone given cq/ipzilla needs for time, moritz availability, etc.
Would still like to see this happen with contributions, but given lack of committer resources and change in ECF project emphasis (to OSGi remote services) it seems unlikely to happen.
