
New Interface for KCall
Various KDE 1.-4. Improvements
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
As part of a university assignment we have designed a new interface for KCall. We have posted a prototype of KCall using our new interface which you may test and try.
Remember it's still a prototype, and not all functionality is implemented yet. During the design phases we have also received numerous suggestions and feature requests which we believed were very useful though we did not have the time yet to implement all of them yet. Please be patient as more functionality will be made available.
We will try to integrate our results back into KCall as good as possible.
Thanks,
Arend van Beelen and Thijs Vermeulen.
University of Leiden, Netherlands.
KCall Homepage: http://www.basyskom.de/index.pl/kcall
WHAT SHOULD WORK:
- Outgoing and incoming calls.
- Caller ID recognition.
- Address book integration.
- Most of the interface.
WHAT DOESN'T WORK:
- Actual sound during a call (at least I wasn't able to get it to work, using SUSE 10, hopefully someone can report better experiences).
- Transfers.
- Call List / History.
- Be prepared for plenty of bugs.
15 years ago
- Added Final Paper
- Added Prototype
15 years ago
- Added Final Paper
- Added Prototype
hullbr3ach
15 years ago
Report
pembo13
15 years ago
Report
asdex
15 years ago
Report
arendjr2
15 years ago
Report
l1nux
15 years ago
cat kcall_interface.patch |patch -p0
patching file kcall_part.rc
patching file kcallgui.h
patching file main.cpp
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file main.cpp.rej
patching file kcallgui_part.h
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kcallgui_part.h.rej
patching file kcallgui.cpp
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kcallgui.cpp.rej
patching file kcall.desktop
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 17.
2 out of 2 hunks FAILED -- saving rejects to file kcall.desktop.rej
patching file kcallgui_part.cpp
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file kcallgui_part.cpp.rej
patching file Makefile.am
whats version of kcall should use ?
whay you dont add "full patched kcall src" in download ?
why README not found in kcall_interface tarball ?
any one get success with this patch ?
Report
arendjr2
15 years ago
Greets,
Arend jr.
Report
athleston
15 years ago
X Contact
V Contact
is misplaced; it should either stay in the main toolbar or be located just below the main list of contacts.
Its not clear how the Numpad is got to, but the overall layout is very nice... what is that, a dash or underline beneath the 0 key?
A customizable image for the contact is very nice, even nicer if it could be shared that is I may want to transmit my image with my contact info to someone else?
Report
arendjr2
15 years ago
Report
arendjr2
15 years ago
Greets,
Arend jr.
Report
r2pi
15 years ago
Looks very good. Hope you release alpha versions as early as possible as sugestions are kind of hard until you have it right in front of you.
What kind of database are you going to use? Perhaps SQLite and Mysql should be considered as SQLite will be useful for those working as stand alone, but for others working in a team, a real SQL server might be best.
Report
m3g4crux
15 years ago
Report
arendjr2
15 years ago
Thanks for your suggestions. I'm afraid though they won't make it in our design anymore, as I feel they're a bit beyond the scope of this project. However, I suggest you take a look at the Asterisk project (http://www.asterisk.org). It sounds like many things you suggest could be better implemented at the server-side (I would even be surprised if Asterisk doesn't already provide some recording functionality). Of course then some hooks to that functionality could be implemented in the end-user interface, like the way we want to provide support for voicemails at some point.
Greets,
Arend jr.
Report
arendjr2
15 years ago
Thanks for your suggestions. I'm afraid though they won't make it in our design anymore, as I feel they're a bit beyond the scope of this project. However, I suggest you take a look at the Asterisk project (http://www.asterisk.org). It sounds like many things you suggest could be better implemented at the server-side (I would even be surprised if Asterisk doesn't already provide some recording functionality). Of course then some hooks to that functionality could be implemented in the end-user interface, like the way we want to provide support for voicemails at some point.
Greets,
Arend jr.
Report
vide
15 years ago
If you are going to do a new work after KCall, may I suggest you the KDE printing system? It has got all the power but definitely needs a hard work on UI as you are able to provide.
Again, great work!
Report
guppetto
15 years ago
Report
arendjr2
15 years ago
thanks a lot for your suggestions!
I do wonder, what exactly do you have in mind for such a dropdown panel for the numpad? Would it be a panel that floats over the phone book panel when expanded? Or would just the entire window become bigger when it expands? Maybe you can show a simple drawing to illustrate it :)
I'm also curious as to what extent left or right handedness influences the direction in which you operate an interface... isn't it more dependend on the direction in which you read?
About the icons, probably we will just need a few of them. But an open call to the icon designers might be a good idea :)
Greets,
Arend jr.
Report
guppetto
15 years ago
Report
athleston
15 years ago
Report
arendjr2
15 years ago
thanks for your reaction. I can assure you that we provide all our work during all stages to the KCall developers. We also get useful feedback from them, and we try our best to meet up to their standards :)
Greets,
Arend jr.
Report