|
|
What functionality do you create over and over again?
| Sun, 2005-11-27 23:33 | |
|
Hello there,
If you've done a number of projects on Symbian OS, you've probably ended up developing some application components a few times -- the type of stuff that you'd hope that existed as ready-made components that you could simply drag-and-drop into your project, and continue with your work. And for the sake of this discussion, I mean non-UI components. A good example of a useful non-visual component would be a component that, when included in a project, allowed you to use a Bluetooth connection, and the component would automatically handle all the dialogs required to turn Bluetooth on, search for devices, display the list of devices, and manage pairing. Here's the question... What components would save you the most work? What components would you like to see? UIQ or S60. Thanks, //markus |
|
Forum posts: 2006
That looks exciting.... I hope the beta version of Carbide.c++ will be available soon!
My wishes (I do not mention bluetooth as it is obvious and already listed in your post):
- a basic tcp socket connection
- a picture/bitmap loading and manipulation component
- a access to mobile configuration (IMSI, IMEI, OS version, screen resolution and depth)
- a simple http get/put component
- a simple SMS sending component
- a audio input/output component
- a generic wrapper for the publish/subscribe API
Eric Bustarret
NewLC Founder & CEO / Professional Symbian OS Consultant
Forum posts: 3
- SMS receiving in addition to sending
- access to camera(s) with both viewfinder and image capture
- simple XML DOM parsing (read-only)
- simple general purpose scripting language for controlling the app
HePora
Forum posts: 78
- A debugging library with printing Filename and Linenumber to the traces and/or file. Preferebly in a forms of macros that can be included or excluded. And when included, can be switched on/off
- A testing framework with a wizard and/or template for a new testcases. Test script language with events is a must
Compilable Symbian Code Examples
Forum posts: 4
-----------
MTM component:
- utility application that registers the MTM with the Message Server
- resource file that provides information to register the MTM with the messaging server
- repository initialisation file
- skeleton client-side MTM implementation
- skeleton UI data MTM implementation
- skeleton user interface MTM implementation
- skeleton server-side MTM implementation
- basic UI resources and icons for the MTM
- basic utilities classes
- basic editor/viewer
MTM implementation is considered really difficult by most of the developers, so it would be really useful if they could use this kind of code as a basis for experimenting with the MTM architecture and for adapting the code for their own MTM project.
//markus
Forum posts: 2006
So such kind of module will definitely help, but this won't be my primary request if I just have to choose one.
Eric Bustarret
NewLC Founder & CEO / Professional Symbian OS Consultant
Forum posts: 4
- Bluetooth connection (discovery, selection, handshake, exit; Includes required UI elements
- View mobile configuration (Find out IMSI, IMEI, OS version, screen resolution and depth)
- SMS, MMS Send/Receive
- Easy access to Camera/cameras (image capture, viewfinder)
- TCP/UDP socket connection + simple http get/put
- Picture loader (load, modify, convert, other manipulations, close)
- Audio input/output
- Wrapper for publish/subscribe API
- Splash screen component for application startup, optional progress indicator
- Conversion methods between 8 & 16 bit descriptors
- Simple XML DOM parser
- MTM component (registers MTM w/Msg Server, server-side MTM implementation, basic utility classes, basic UI, etc)
Is this list complete? Does it have the 20% of possible components that would solve 80% of your problems? If you could only have 5, which would you choose?
//markus