thanks for the reply.
but i may think differently.
javascript runtime can be shared, and no new memory allocation and memory
copying required, only the apps require new memories when running.
but the android vm is not, at least you should allocation memory for
inter-media code files like .class
On Sat, May 10, 2014 at 6:57 PM, dashman wrote:
> Shouldn't the width of the button be 60dp -
> since i've set the width of the button to match-parent - and it's set to
> 60dp in the layout.
>
> It's actually taking up the full width of the parent view - not layout.
>
You'd think, right?
To ach
I've got a layout (that's a listitem) and want to set a fixed width.
(it's a horizontal listview)
http://schemas.android.com/apk/res/android";
android:layout_width="60dp"
android:layout_height="wrap_content"
>
(i've removed items above to the bare minimum)
Shouldn't the width of
I have no idea why you think that using Java is "slow and memory
consuming:" especially when so many apps are being complied to native
code and the framework is getting better by the month.
FYI anything on JavaScript is going to require even *more* memory,
since the runtime of a JavaScript library
Java-based Android is very slow and memory consuming.
and the XML based UI components are far from flexible.
if Android sdk provides an html5 + javascript alternative, it would
greatly improve the android app possibilities.
as we have seen more and more popular apps are written by html, css an
Is it when the target context does not share the user id with the calling
context?
Appreciate your insight
Satya
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To un
6 matches
Mail list logo
