ok that's good...
On Tue, Mar 24, 2009 at 12:28 AM, Dianne Hackborn wrote:
> On Mon, Mar 23, 2009 at 12:39 PM, Rajendrakumar Chinnaiyan <
> rajendran.b...@gmail.com> wrote:
>
>> I need a help from you... can I send a mail to you mail ID...
>
>
> I need to keep discussions on the list; I don't hav
On Mon, Mar 23, 2009 at 12:39 PM, Rajendrakumar Chinnaiyan <
rajendran.b...@gmail.com> wrote:
> I need a help from you... can I send a mail to you mail ID...
I need to keep discussions on the list; I don't have time to provide private
support.
--
Dianne Hackborn
Android framework engineer
hack
ok
Dianne
I need a help from you... can I send a mail to you mail ID...
On Tue, Mar 24, 2009 at 12:06 AM, Dianne Hackborn wrote:
> On Mon, Mar 23, 2009 at 12:16 PM, Rajendrakumar Chinnaiyan <
> rajendran.b...@gmail.com> wrote:
>
>> If they won't change the internal API's.. Our applicati
On Mon, Mar 23, 2009 at 12:16 PM, Rajendrakumar Chinnaiyan <
rajendran.b...@gmail.com> wrote:
> If they won't change the internal API's.. Our application also won't get
> any problem..
The very reason APIs are internal is because they can change.
--
Dianne Hackborn
Android framework engine
And that's a BIIIGG 'if'. :-)
Trust Dianne on this. Do not use any API that is private. If you do,
at some point in time you will (and that's a 100% sure) break your
application and you will get a lot of angry customers.
On Mar 23, 3:16 pm, Rajendrakumar Chinnaiyan
wrote:
> If they won't c
If they won't change the internal API's.. Our application also won't get any
problem..
On Mon, Mar 23, 2009 at 11:42 PM, Dianne Hackborn wrote:
> On Mon, Mar 23, 2009 at 11:42 AM, AndRaj wrote:
>
>> oh... Good.. So it will change only if they change in new release
>
>
> They will. You w
On Mon, Mar 23, 2009 at 11:42 AM, AndRaj wrote:
> oh... Good.. So it will change only if they change in new release
They will. You will break. Plus, you are linking against a special build
of a part of the Android platform that was designed to run on the desktop
for the UI editor. There
oh... Good.. So it will change only if they change in new release
i fthey won't change that it also won't change rt...
On Mar 23, 9:40 pm, Dianne Hackborn wrote:
> On Mon, Mar 23, 2009 at 3:05 AM, Lars wrote:
> > Could you please explain why?
>
> You are using this to bypass the SDK and ac
On Mon, Mar 23, 2009 at 3:05 AM, Lars wrote:
> Could you please explain why?
You are using this to bypass the SDK and access various internal APIs and
data structures. Worse, what is probably happening is that you are bundling
the internal IPC interfaces into your app, which will break pretty
Could you please explain why?
On Mar 20, 6:13 pm, Dianne Hackborn wrote:
> On Thu, Mar 19, 2009 at 7:29 AM, Lars wrote:
> > Actually you can use some of them. Just add tools\lib\layoutlib.jar to
> > the build path (Eclipse: right click the project, select Build Path/
> > Add Libraries. Click U
On Thu, Mar 19, 2009 at 7:29 AM, Lars wrote:
> Actually you can use some of them. Just add tools\lib\layoutlib.jar to
> the build path (Eclipse: right click the project, select Build Path/
> Add Libraries. Click User Libraries, select Android libs, click Add
> JARs, browse to layoutlib.jar, click
Thank you Lars for your quick reply,
> Just add tools\lib\layoutlib.jar to the build path
I am not getting you... can you explain the steps little bit deep.. I
am not geting about the laoutlib.jar.
Reagrds,
andraj
On Mar 19, 7:29 pm, Lars wrote:
> Actually you can use some of them. Just add
Actually you can use some of them. Just add tools\lib\layoutlib.jar to
the build path (Eclipse: right click the project, select Build Path/
Add Libraries. Click User Libraries, select Android libs, click Add
JARs, browse to layoutlib.jar, click OK, Finish etc.)
BR
Lars Brange
/ User Library
On M
Thanks for the reply...
On Mar 19, 1:10 pm, Dianne Hackborn wrote:
> Just because you can browse through the source and find something doesn't
> mean it is supported for application development. You can use the APIs in
> the SDK. Things that are not in the SDK were deliberately removed becau
Just because you can browse through the source and find something doesn't
mean it is supported for application development. You can use the APIs in
the SDK. Things that are not in the SDK were deliberately removed because
they can change in arbitrary ways across versions of the platform.
On Thu,
Really... Is it, as an application developer I can only use the ADK
API's.
But I can able to see the source of those API's, then I can use those
classes in my applicaition right
On Mar 19, 12:18 pm, Dianne Hackborn wrote:
> No, you can't. It is internal implementation details of the platfo
No, you can't. It is internal implementation details of the platform.
On Wed, Mar 18, 2009 at 11:59 PM, AndRaj wrote:
>
> If I want to use those thing into my application. How can I use. Is
> there any way to do that. I want to create a object for the
> Iwindowmanager class. Ho can I do this...
If I want to use those thing into my application. How can I use. Is
there any way to do that. I want to create a object for the
Iwindowmanager class. Ho can I do this...
On Mar 19, 12:38 am, Dianne Hackborn wrote:
> Those are not part of the SDK.
>
> On Wed, Mar 18, 2009 at 6:53 AM, Rajendrakuma
Those are not part of the SDK.
On Wed, Mar 18, 2009 at 6:53 AM, Rajendrakumar C
wrote:
>
> Hi All,
>
>
> I downloaded the Android Source to my machine, I have seen the source
> code. In that I found Iwindowmanager, I activity manager and etc I
> managers...
>
> But when I try to use those things
19 matches
Mail list logo
