Re: [Moblin Dev] Google's Open Source Mobile Platform
On Nov 10, 2007 1:11 PM, Steve Paine <[EMAIL PROTECTED]> wrote: > I have a feeling that Android will be available for arm and x86 and > that programmers will only have access to the SDK. It would make sense > if it's java as google already has apps running on java. > I'm no java expert but similar projects i've seen running like this > have been fairly memory intensive. Pepper's desktop, for example. A > very similar project to Google's but with no SDK!! Maybe that's why > they're in trouble. > > Anyone know what browser core will be used? Mozilla? It's a webkit-based one. They're going to unleash their patches/source for webkit soon. > > Maybe this isn't the right place to discuss Android but i'm sure there > are going to be connections between the projects. Maybe the Moblin > guys are already building the x86 version of the core for Intel > hardware. > > Steve. > UMPCportal > > We'll see next week when the SDK is released > > > On Nov 10, 2007 9:22 AM, Kwon, Owen <[EMAIL PROTECTED]> wrote: > > Is Android just a middleware and Google application set? If then could we > > port Android to moblin stack and run simultaneously with native Linux > > application? Or run Android in separate virtual console? > > > > Thanks, > > Owen > > > > Owen Kwon (Ohkeun Kwon) > > Technical Marketing Engineer > > +82 2 767 2428 (Office) > > +82 10 9034 4820 (Mobile) > > > > From: Paul Bartell [mailto:[EMAIL PROTECTED] > > Sent: Thursday, November 08, 2007 9:55 AM > > To: Kwon, Owen > > Cc: Naveen Verma; Amit Karpe; Ubuntu India Local Community; > > ubuntu-mobile@lists.ubuntu.com; [EMAIL PROTECTED]; [EMAIL PROTECTED] > > > > Subject: Re: [Moblin Dev] Google's Open Source Mobile Platform > > > > I would think not... Depending on what JVM they are using, it could be good > > for expandability, and not needing a different binary for each type of > > device. I know sun's JVM is fairly memory intensive. > > On Nov 7, 2007 4:43 PM, Kwon, Owen <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I heard that Android is strongly based on Linux/Java. Is Java a good > > middleware for linux device? > > > > Thanks, > > Owen > > > > Owen Kwon (Ohkeun Kwon) > > Technical Marketing Engineer > > +82 2 767 2428 (Office) > > +82 10 9034 4820 (Mobile) > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > > Of Naveen Verma > > Sent: Wednesday, November 07, 2007 3:28 PM > > To: Amit Karpe > > Cc: Ubuntu India Local Community; ubuntu-mobile@lists.ubuntu.com; > > [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: Re: [Moblin Dev] Google's Open Source Mobile Platform > > > > Hi, > > > > Yes, this is interesting, somehow I feel that distribution may be like > > we > > have with different version of linux, Fedora, Ubuntu, Suze etc. > > > > -Be > > Naveen > > > > On Nov 6, 2007 10:09 PM, Amit Karpe <[EMAIL PROTECTED] > wrote: > > > > > Hi all, > > > Google's Open Source Mobile Platform : > > > As expected, today Google took the wraps off of the gPhone (as the > > > media have for months been referring to the rumored project). Google > > > is "leading a broad industry alliance to transform mobile phones into > > > powerful mobile computers," and will be licensing its software to all > > > comers on an open source basis under the Apache license. (The Wall > > > Street Journal's Ben Worthen demonstrates a miserable grasp of what > > > "open source" means.) Google's US partners include Nextel and Sprint, > > > but not AT&T nor Verizon. Phones will be available in the second half > > > of 2008 - not the spring as earlier reports had speculated. News.com's > > > analysis warns that Google won't take over the mobile market > > > overnight, though they quote Forrester in the opinion that Google may > > > be one of the three biggest mobile players after several years of > > > shakeout. > > > > > > >From : http://linux.slashdot.org/linux/07/11/06/0223211.shtml > > > > > > Also for more info > > > http://www.openhandsetalliance.com/press_releases.html > > > http://www.openhandsetalliance.com/press_110507.html > > > http://googleblog.blogspot.com/2007/11/wheres-my-gphone.html > > > http://googlesystem.blogspot.com/search/label/Google%20Phone > > > > > > > > http://googlesystem.blogspot.com/2007/09/10-questions-about-google-phone > > .html > > > http://hardware.slashdot.org/article.pl?sid=07/11/05/139210&from=rss > > > > > > > > http://www.pcworld.com/article/id,139293-c,pdacellphonehybrids/article.h > > tml > > > > > > > > http://www.hindustantimes.com/StoryPage/StoryPage.aspx?id=e2c539e8-524a- > > 418f-aee2-22578a0f6b65&&Headline=Bharti+to+partner+Google+Phone > > > > > > http://www.openhandsetalliance.com/android_overview.htm > > > > > > Interesting stuff !!! > > > Now I just want to know who will win ??? > > > Qutopia , Open Moko , Moblin or Andriod ??? > > > > > > I think FOSS will win !!! > > > > > > > > > -- > > > Regards > > > Amit. > > > > > > ___
Re: graphical themeing in UME
On 8/23/07, Kyle Nitzsche <[EMAIL PROTECTED]> wrote:
>
> The background is two or three IRC chats about firming up UME graphical
> themeing.
>
> Goals may include making it easy for third parties to develop themes,
> identifying exactly what themes are and what directories are used, defining
> how to write themeable apps, possibly allowing user-settable themes, etc.
>
> Here are my notes from the most recent chat (8/21) that I previously
> emailed to individuals.
>
> OVERALL
> * progress towards defining what a UME theme consists of and
> corresponding directory structure and tools
> * idea to create a theme sdk pacakge that would simplify theme design
> for third-parties
> * would contain all themeable images and tools
> * tools would include slicer and possibly make files or scripts to
> install theme in image-creator target
> * goal is to enable non-programmer theme designer to iteratively test
> theme during development
> * does sdk theme package result also in installable deb theme package
> ('myTheme.deb')? (Create user settable theme support in UI?)
> * how does theme sdk package support developing themed icons?
> * theme sdk would include: themeing for desktop and for "ume standard
> applications"
> * need to define/document how to write/port applications to ume such
> that they fit the theme model (define where to put icons, images,
> splashes)
> * need to check implementation of icon theme code and document how icon
> theme is set and verify it works as expected
> * need to remove all extraneous/unused graphics from repository
> * Support themed desktop home area backgrounds (currently is set in home
> plugin)
>
> THEME MODEL
> * there are two themes: icon, and general (Do they necessarily have the
> same name at any given moment or are they truly independent?)
> * /usr/share/icons/(theme) contains subfolders for themed icons with
> "hicolor" the default
> * /usr/share/theme/(theme) contains everything else, including gtkrc files,
> matchbox's theme.xml and desktop + standard ume application set non-icon
> images
> referred to in gtkrc and matchbox theme.xml
> * discontinue use of /usr/share/pixmaps as it is not themeable
> * splash images (three) are branding, not themeing, so this is excluded
>
> SLICER
> * the template.png file can contain all non-icon themeable graphics
> * includes matchbox images
> * can include gtkrc images, in which case they replace
> default images
> * need to verify tool is suitable for graphical designers (does it need
> to be simplified?)
> * How do designers know where to put each image: do they read the config
> file? Suppose they add images (gtkrc), do they modify config
> file?
> * what documentation is required? List of basic theme graphics? List of
> optional/additional themed graphics (gtkrc, matchbox)? User Guide?
>
> Kyle
I just updated our (hildon) theming documentation on live.gnome.org:
http://live.gnome.org/Hildon
(theming section). You might find it helpful.
--
Michael.
--
Ubuntu-mobile mailing list
Ubuntu-mobile@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: A patch for libhildon -- for auto-launch keyboard
On 8/14/07, Johan Bilien <[EMAIL PROTECTED]> wrote: > On Tue, Aug 14, 2007, Tollef Fog Heen wrote: > > * "Han, Jian" > > > > | Hi, all > > | I write a patch for libhildon. It add the feature of auto-launch > > | keyboard. > > > > How is upstream hildon doing this? Is there any reason we can't be > > doing it the same way? > > > > I'd like us to avoid deviating from upstream behaviour as much as > > possible and rather adopt upstream's approach than invent our own. > > I include the hildon mailing list hildon-input-methods guys should be > able to answer this. > > -- > Johan Bilien > <[EMAIL PROTECTED]> > > -- > Ubuntu-mobile mailing list > Ubuntu-mobile@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile > Hey, hildon maintainer here. Perhaps I'm not fully getting it, but how is that different than standard gtk input methods stuff? -- Michael. -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Question about supported hardware/processor
On 6/22/07, Rusty Lynch <[EMAIL PROTECTED]> wrote: > On Thu, 2007-06-21 at 15:07 -0700, James Sparenberg wrote: > > On Wednesday 20 June 2007 11:26:05 Mathias Uebelacker wrote: > > > wiki.ubuntu ist a good place but whats with a good structure? > > > > > Just trying to understand the goals of the project. The Q1 would run > > regular > > Ubuntu just fine. (Xubuntu perhaps better) so why a special project for > > this. It's a standard PIII Celeron. with 512MB ram and a 40GB hdd... > > It's all about getting a device with a similar form factor to enable > application framework and application development. The samsung screen > is a bit big, but not too big, and you have a lot of the other elements > (like a touchscreen) that allow us to start working on this stack and > enable some creative elements before better suited hardware arrives. > > BTW, even with target hardware, you will have (relative to traditional > mobile devices) loads of resources so you absolutely can run normal > ubuntu. The problem is that a normal full desktop is horribly unusable > for this kind of form factor... not because the device will run too > slow, but that the usage model for full desktop makes all kinds of > assumptions that kill the experience on a small form factor device. Makes perfect sense. BTW, are you planning to investigate/use hildon-widgets (hildon-1 library) too? What's the preferred method of developing applications for your platform? It's a long discussion we carried on several times here at nokia. Mobile applications need a different UI. Running desktop applications on a small screen, even if possible technically, doesn't make much sense. Some interaction methods don't make much sense on the mobile and vice versa. I think it's logically impossible to have a UI system that automagically scales up and down (I don't mean here graphical scaling but rather functionality scaling). Therefore, a better bet is to write applications in such a way, that the engine is cleanly separated from the UI (which can have many variants). Unfortunately, gtk-apps development model doesn't encourage this kind of separation, and with most applications the UI-flow code is heavily mixed up with the core application logic code. Anyways, coming back to my original question -- are you planning to adopt gtk + hildon widgets as the base development toolkit? > > I tried using a full GNOME desktop on the original Samsung Q1. At best > it was a painful experience. > > --rusty > > -- > Ubuntu-mobile mailing list > Ubuntu-mobile@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile > -- Michael Dominic K. -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
