Hi. Is it possible to replace the soft keyboard by writing just an
Activity, or is it hardwired into the framework?
I probably think the latter from looking at various stuff, but I
thought Id double check.
thanks
--~--~-~--~~~---~--~~
You received this message be
Hi, Im currently trying to put together an idea of how
WindowManagerService works - who it works with and how it works.
WindowManagerService is a system service - running in the system
process I suppose. So it needs IPC to interact with applications. On
the application side we have ViewRoot whi
how?
On Jul 9, 5:51 pm, hackbod <[EMAIL PROTECTED]> wrote:
> > if I want to take a window (with a dialog in it) and do some
> > transformations on it (which will have to be done in s/w since android
> > doesnt yet support h/w accleleration of its 2D animations) how do I
> > do that?
>
> Window a
I think we are talking about two different things.
if I want to take a window (with a dialog in it) and do some
transformations on it (which will have to be done in s/w since android
doesnt yet support h/w accleleration of its 2D animations) how do I
do that?
lets say I want to rotate the windo
"The Android compositing engine is actually much more like
MacOS X than X-Windows, supporting full 3d hardware acceleration of
window compositing and transformation. "
huh? since when? compositing engine?
On Jul 8, 9:00 pm, hackbod <[EMAIL PROTECTED]> wrote:
> On Jul 8
t; create an application, it has to be prepared to run on all processor
> speeds, all screen sizes, etc.
this is your assumption (as an application developer?) As a handset
manufacturer, your viewpoint is different. You want to produce
something with specific capabilities. If Android cant cater
On Jul 5, 10:30 am, "Romain Guy" <[EMAIL PROTECTED]> wrote:
> Vector graphics are not magical. First of all, a vector graphics
> engine require expensive rendering if you want to be able to create
> results that have as much details and effects as traditional raster
> graphics.
Looking forward,
ook pretty shabby by comparison as early as the next year or two.
better start thinking about it now rather than be reactive.
> JBQ (Android Engineer)
>
> On Jul 4, 4:22 am,stefoid<[EMAIL PROTECTED]> wrote:
>
>
>
> > etc...
>
> > this quote from this bl
etc...
this quote from this blog says it clearly. the lack of hardware
acceleration for androids 2D graphics API, oand for any resolution
independent way of defining your UI is a showstopper.
http://unqualified-reservations.blogspot.com/2007/11/five-problems-with-google-android.html
"Third, An
2, 12:35 pm, stefoid <[EMAIL PROTECTED]> wrote:
> Specifically:
>
> I have two views, A and B
>
> I want to set the background of view A with a snapshot of the current
> state/image of view B
>
> Possible?
--~--~-~--~~~---~--~~
You re
Specifically:
I have two views, A and B
I want to set the background of view A with a snapshot of the current
state/image of view B
Possible?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" grou
OK, it does work, disregard this babble. My bad.
On May 9, 10:55 am, stefoid <[EMAIL PROTECTED]> wrote:
> OK, I think I understand whats going on - an ImageView displays the
> image by:view.setBackground(imageyouwanttosee);
>
> this is not want I would want or expect,
ImageView is flawed.
see
http://groups.google.com/group/android-developers/browse_thread/thread/f3c8fbab234ba10d/fdaf67174a7ad81d?lnk=gst&q=stefoid#fdaf67174a7ad81d
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Gr
background, then I will call
setbackground ON ANY TYPE OF VIEW. thats not what ImageView
specifically should do in my opinion - it should set the image in the
foreground so that view operations can be done on it.
Im calling 'bug' on this.
On May 8, 5:45 pm, stefoid <[EMAIL PROT
Example code below is my attempt to clip an ImageView with a non-
rectangular shape. It doesnt work, I see the full rectangle.
Obviously I am misunderstanding some basic thing about the way android
graphics works.
any help appreciated.
also another question - why dont I have to call super.onDr
Or does an application necessarily have to be full screen?
For example, Lets say I want to write an application starter widget
that is always visible onscreen (with tabs say). When I click on a
tab, that application runs, but I can still see the tabs which I use
to switch to other applications.
? blerg! :(
On Apr 28, 5:12 pm, stefoid <[EMAIL PROTECTED]> wrote:
> No, actually Im still confused.
>
> What I want to do is scroll the contents of a LinearLayout within its
> boundaries. i.e. I want the LinerLayout to be a viewport that scrolls
> its contents horizontally.
&g
No, actually Im still confused.
What I want to do is scroll the contents of a LinearLayout within its
boundaries. i.e. I want the LinerLayout to be a viewport that scrolls
its contents horizontally.
I cant make it work.
On Apr 28, 4:26 pm, stefoid <[EMAIL PROTECTED]> wrote:
> OK, so
OK, so I worked it out myself, sort of - Im still having issues with
it, but at least I can get it to move.
answer lies here:
http://code.google.com/android/reference/android/view/animation/package-descr.html
On Apr 28, 3:17 pm, stefoid <[EMAIL PROTECTED]> wrote:
> I want to use
I want to use 'kinetic' horizontal scrolling on an a LinearLayout
area.
I did a quick search and found this widget called a Scroller that
seemed to have an API that fit the bill - flings, interpolaters,
etc... but then Scroller is only of use to a TextView?
ScrollView seems like it is only a v
20 matches
Mail list logo
