I am currently working on a new framework to use on top of CF, that allows for fingerfriendly development on Windows Mobile phones, and would like to hear your thoughts and ideas (of cause this is a really early version).
The idea is to mimic the way that you create winform applications, but since it is based on the GDI+, you have the possibility to use it all the way from throwing a few buttons in an application, all the way down to just using the graphical manager to take care of load balancing.
Have a bit more details on my blog along with the first sample video showing the scroll feature, and the transistion effect between panels (basicly the same as forms).
The video
The blog
So if there are any features that you would like, please write me.
Related
Now that bal666's awesome utility gives us the ability to decrypt/encrypt the NBF file, we can view and/or extract the ROM files that are normally not available to us otherwise.
One big hoopla that Windows Mobile 5.0 was supposed to have was the native ability to access the camera through their APIs, so that third-party developers could create applications without having to deal with each and every different type of camera technology in different Pocket PC and Smartphone devices.
Of course, it's apparent that HTC has still used their own software and drivers and has not given access to anyone outside of HTC. Not like Microsoft had their own Camera application (I don't know if there ever was one, but there isn't a Microsoft one on the Universal).
Developers such as ComVu with their neat PocketCaster software, are having such a difficult time making a single Windows Mobile 5.0-ready application, and have resorted to making different versions for different devices.
So... where am I going with this? Simple. Let's dump out the contents of the NK.NBF file and see if we can make our own applications with the APIs and drivers that HTC has embedded in the ROM.
I, for one, am looking forward to a internet-based videoconferencing application, much like Microsoft Portrait. Skype also announced video calls on PCs with the new version 2.0. Perhaps someone could send them some code to get video capability on the Universal?
That front-facing camera is beckoning to be used...
On a sidenote, PPL: Pocket Programming Language, allows you to easily create applications (self-contained EXE files, as a matter of fact), and also allows direct access to DLLs and APIs...
Put these two concepts together, and you can see the potential.
Create an application to...
... toggle the camera flashlight.
... do internet videoconferencing.
... do face recognition security.
Create your own camera app, phone app, game using images from the camera, etc. etc.
Another thing, though I'm not sure, but perhaps it's possible to rebuild your own ROM... remove Voice Speed Dial? Embed Voice Command, Resco Explorer, remove stupid applications or unused portions? etc. etc.
What does anyone else think about this?
BtT,
This sounds great, even having only a magician which will likely not being supported in projects like this. I still want to create my own rom with at least all the patches installed in rom. Camera & Album are taking at least 1Mb from my precious storage & apps like resco explorer are indeed must haves.
So I'm looking rorward to progress & tips in this thread & when I succeed with simple magician rom cooking I'll let you know. Don't expect any new camera apps from me, no time & no development for anymore .
Regards, M
http://research.microsoft.com/workshops/FS2005/presentations/FacultySummit_2005_Lieberman.ppt
I just realized that Windows Mobile 5 SDK contains a "common camera API" which is likely the method that third-party developers will take (or have taken) to access the camera. I have emailed Skype to see if their new 2.0 desktop version that has Video Calling can be somehow implemented on the Pocket PC, now that it is technically feasible.
I'm surprised the guys behind Microsoft Portrait haven't jumped on this yet.
Hi guys. I see a lot of "finger friendly" contact managers apps theese days.
Which API are you using ? I'm planning to work on it for sms reading and any help would be great.
Hi,
Personally, for contact manager, I'm working on ... my own framework, but that's mostly to allow decent performance and animation effects.
Basically it's a composite pattern, every control is based on LightControl base class which provide basic interraction and drawing.
The drawback of this approach is that text input control are rather complex to do, the big advantage is that layout, drawing are free are control aren't tight in a specific shape.
What are your requirements?
Hi, I'm working on .NET 2005 (usually VB but I also have knowledges of C) and I'm developing for a Prophet and a Trinity
yes.. but what are your requirement regarding the framework? what do you want to do that classic winforms won't provide you?
I am trying to do some custom controls, I've done some mobile work lately, but just typically using standard controls and an owner draw list. I want to try to do more "custom" drawn stuff.
In this project I'm trying to somewhat mimic the htc random access that will support multiple "lists" for this new project.
I'm new to the graphics (2d) stuff and need a bit of help. In this sample project I want to be able to draw the letter in the center of the screen, I will have a box behind it (gradient eventually I hope) so I need to be able to draw to the screen since its outside of the controls bounds. Thats no problem, but how do I clear what I've drawn?
here is a link to my code, if someone could please take a look.
where you should look is in the RandomAccess class, in DrawStringbox
http://createdevcode.com/code
thanks a million!
been trying to find some examples on the web, found one in full .net that sorta does what I want but of course I don't have access to all the PMEs in compact framework.
again, any help would be apprecidated on how I can draw to a "layer" on top of my form and have the form paint properly once I want to get rid of that layer and not have any left over graphics on top of any controls.
I am currently writing an application for my WM6.1 device (HTC TouchHD), and wondered if anyone had come across a site, or if someone could point me in the right direction for finding a nice way of writing 'finger friendly' applications. By finger friendly, i mean being able to scroll with my fingers and so on. Or if there are any open source applications that I can use as a reference?
I don't particularly want to say what application I'm writing just in case it falls to pieces, but rest assured once it's written it will be put up on here!
Thanks,
evorgevol
I have just found this page which does me for scrolling parts of my application. The main thing I'm having issues with is that I want the main menu interface to resemble windows 7 media center, see here for a video of what effect I'm trying to achieve.
I know it's quite complicated, and I'm not the best programmer in the world, but hopefully I should be able to do it??
Any help will be appreciated. Thanks,
evorgevol
If I understand, you're trying to create an UI with a scrolling list useable with fingers.
Each item in the list, once selected, let appears different choices about this item (IE : a "Appointment" item in the list, when you select it, you have the next appointment displayed....). It that right ?
Doesn't it look like the new WM6.5 today plugin ? If that's you're idea, I'm 100% on your side to develop a today plugin looking like these menus (WM6.5 / WM7 MC) !
(In fact, I'm already searching if somebody could develop something like this : http://forum.xda-developers.com/showthread.php?p=3375478)
The one I'm doing is not necessarily for a today page, more for my own application, tho it should be able to be easily used in any other application once the code has been written. I just need a push in the right direction for me to be able to write the code in the first place. I'm also deliberating what format to write my application in, and which ones are available. I will only be supporting from WM6 onwards, tho it could potentially be backwards compatible with 5. Ideal would be silverlight being able to be used, but unfortunately that hasnt been released for mobile yet (it would mean that my application should run on any platform that supports Silverlight).
Try iContact. I suppose the code is open. Also try PockeTwit from google code. Install these apps and if that is the effect you want to achieve, I suggest you grab the code and understand it (that's what I would do if I was in your position)
Hi there
not THAT much threads here related to development questions. Now it's absolutly ironic that I ASK this, cause Im no dev and coded the last small tools in C some 10 yrs ago. I'm a complete and definite noob in C++ ... bada SDK is my first contact with C++. I though it's interesting to try some first steps in bada.
Started in SDK 2.0.2. I found out that code examples in Internet relate to bada SDK 1.x and things seem to have changed here and there. After 3 days I was able to understand structurally what I collected together or found in help.
Question: What did you guys face as difference in 2.0 compared to 1.x?
I wasn't able to invoke the app "terminate()" command. What do I need to include/declare? I'm puzzled. this is the most difficult exit function of all languages I know
I had trouble to insert a photo as the splash screen. You guys have difficulties too?
More philosophic question: What do you think of Samsung, that they gave you SDK 2.0 and even started a competition, while there's STILL NO bada 2.0 device ready? So you can only test in Emulator or Remote ... is it normal in this industry that you don't have access to the target platform while creating an app?
Oh, just want to mention: I'm no competition - I'm too uneducated to code - and no time for a serious app.
Ray
Its simple, alot of things gone easier.
CustomList, GroupedList, SllidableList, IconList, ... all collected to two types
ListView and GroupedListView, they both are using SimpleItems (Image, Text, Option) or a CustomItem as we devs them wish. GroupedItems are in GroupedListView and saying itself what they does, both lists have a fast scroll option and automatically relocating on need their items. The best autoscroll for bigger text in elements and of cousre the behind Context menu for each item which can be changed in different ways if user slides left or right and so on. Finally to update the list, only UpdateList() is needet not after every change every item as i used in badaSI before.
Than we have the powerfull Gallery that provides all featuers to show pictures as you all saw it in badas Gallary App.
Then header and footer, very nice, devs can so made a good basci gui that looks good integreted to the os, the best function of them are the back button option with its listener, it reduces a lot of time.
My pesonal favorit is the extension for animation class, there you can make every thinkable animation for forms, panels, controls and other stuff, with some code lines. So the UIx is improved and no extra code is needet.
I would rather say that the 2.0 sdk makes c++ a lot of easier to use also for beginners, the api itself is self explaining for what it stands, so it is not like old c++ stuff bada SDK makes many things alot of easier than people think. And of course it has more oportunities than other ... and so on.
Push Notifications and some old unaccessable System Privilegs are now free to use for every developer. Auto resolution takes a lot of work from us all devs.
PThread is addet so porting applications from other oses like ios are much easier, in my oppinion useless cause i am not porting i am writing from scratch.
In a whole overview of the new sdk, a lot of new stuff that makes everything easier, and the old stuff is still in there to support older applications. so no visible changes are there if you see an custom list or a listview in voluntas as example, but the behind things made it a lot of easier and better for memory.
And so on....................
ah, so push noti was there before, but only to priviledged partner dev's right?
Lari, you list is your favourites? What of them will help most often? Header/Footer? Auto Resolution to unite higher and lower lever Waves? Let's see if there's still two separate bada versions for the 2 familys.
Ray
So finally I got the Terminate() function up and running ...
In the form.cpp I had to add these:
#include "<myappname>.h"
... to get declaration of my app name
using namespace Osp::App;
... to enable the Terminate function (don't know if the include makes this unnecessary now ... in "<myappname>.h the public Osp::App::Application,
is used as class
<myappname>::GetInstance()->Terminate();
... only with this the function worked.
Is this standard in C++? Help didn't show me this way, and it seems quite complicated for me as a former ANSI C amateur
Ray
hello? zehn zoicha kaesdreck!