Hey, check http://www.voipsipsdk.com to incorporate voice communication
On May 21, 12:33 pm, Sean Hodges <[email protected]> wrote: > Actually, I just found those instructions yesterday: > > http://source.android.com/using-eclipse > > I particularly like this bit: > > "Now start Eclipse: > eclipse # or you can click some clicky thing instead, if you prefer" > > On Thu, May 21, 2009 at 6:26 AM, Raphael <[email protected]> wrote: > > > Some apps are designed to be build using the platform makefiles and > > not theSDKfor historical reasons. You can still edit the code in > > Eclipse (some people have posted instructions on how to set it > > correctly on android-platform iirc). You just need to type make at > > some point to build it. Don't let that stop you from contributing. > > > R/ > > > On Wed, May 20, 2009 at 5:13 AM, Al <[email protected]> wrote: > > >> It's fine to encourage people to make contributions to Android but the > >> problem is some of the apps have package dependencies not available in > >> theSDK, so it's not possible to make changes and test them. For > >> example, in the Browser, I found a couple of problems which I reckon > >> would be pretty simple to fix. I'd be happy to submit patches for them > >> but when I open the project in Eclipse, it can't find: > > >> - android.os.ServiceManager > >> - android.os.SystemProperties > >> - android.provider.Downloads > >> - android.text.IClipboard > >> - android.text.util.Regex > >> - android.net.WebAddress > >> - android.net.http.EventHandler > >> - android.net.http.SslError > > >> and that's only in BrowserActivity.java! > > >> And I'm sure I'm not the only one who eagerly opened a project, ready > >> to contribute, only to find the app can't be built using the public > >>sdk. > > >> On May 20, 5:31 am, "Mark Murphy" <[email protected]> wrote: > > >>> If you have engineering talent, visit: > > >>>http://source.android.com > > >>> There are those who follow these lists who think I'm a broken record on > >>> this point, and they're probably correct. But the solution to getting more > >>> capabilities in Android is not likely to come in the form of beating up > >>> the core Android team, or even beating up Android management. Since > >>> Android is an open source project, we need to figure out how to get more > >>> people contributing on the open source level. The military likes to toss > >>> around terms like "force multipliers" for this sort of thing -- open > >>> source contributions are force multipliers towards the objective of having > >>> Android "be all it can be". > > >>> I long for the day when the core Android team needs to add headcount > >>> simply because they are reviewing and processing too many contributions. > > >>> -- > >>> Mark Murphy (a Commons Guy)http://commonsware.com > >>> _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
