On 10/01/07, Frank Mantek <[EMAIL PROTECTED]> wrote:
What I would like to know, is, what features to prioritize in the coming months. There are a couple of areas I can envisioning working on, some are predetermined by changes happening internally in the future. But what i would like to know is what you, the users of the library, need and want: and if so, in what areas? what languages?
Another useful thing i just thought of is a client library in C/C++. On WIndows Mobile devices there are some things you juts can't do in managed, CLR code (i.e. VB.net, C#). One is writing plugin DLLs for the Today screen, the "desktop" on a Windows Mobile device. Another is that calling code from non-managed DLLs is a pain unless you have the right IDL files to make import libraries from. Without that you have to futz about with the DllImport attribute, marshalling and all that which becomes even more frustrating if your C/C++ parameters are pointers. Also, I believe (but not 100% sure) that going the other way (non-managed app calling managed DLL) is a complete no go as well. Unfortunately C++ is not a CLR language on Windows Mobile like it can be for PC apps. Add standard argumens for leveraging existing code, etc., etc... Oh, and if someone feels like he has spare time to help, I am not deaf. Send
me an email, and I am more than happy to discuss how this could work.
I'd like to help with this. :-) -- Cory C. Albrecht --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
