On Mon, 28 Sep 2009 20:08:41 +1000 Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> On Mon, 28 Sep 2009 19:54:47 +1000 David Seikel <onef...@gmail.com> > said: > > > I'll be developing an embedded game, and I want to use EFL for it. > > Actually, already working on an older game developed by someone > > else, but this new one I can start from scratch for some aspects. > > I'd like to see some discussion about the pro and cons of the > > various choices available to me when using EFL for this project. > > So I can benefit from the experiences of others. > > > > I do want to use edje for the graphics, with lua in the edje if it's > > ready enough. The main development language is C though. > > > > Probably most important is which type of display to use. X is > > likely to be overkill. The previous game used a combination of > > svgalib and ncurses. The method used to build svgalib from scratch > > sent shivers of horror up my spine. I don't want to use svgalib. > > Mixing a graphics and text environments seemed wrong to me to, and > > has caused some problems. So, what else other than X, svgalib, and > > ncurses, that does use EFL, and lets us use edje, do people suggest > > and why? > > svgalib? then its moving far from embedded. you have a bios.. and a > vga bios.. and vga... and .. why not just use fbcon? kernel has done > vesa fb gfx for a long time... Looks good. > but in reality if its x86 - x works > and isnt bad in that it provide u with a sane display env and even if > all u do is open a window fullscrene in x and dont even run a wm.. > it's lean and wont really get in the way much. it will create less > pain - like input device support etc. Less pain maybe, but taking up more space. Input device support is not an issue, our "input devices" are nothing that X or anything else supports. lol > > At some point a version of linux I build from the ground up will be > > used. Currently DSL that has been cut down is being used. The > > problem with that is that it still carries too much crap we don't > > use. Uses too much storage space. It gets harder and harder to > > trim out the unused crap, so building a linux up to only have what > > we need is a better solution. > > openembedded can make small targets... but what is your target? it's > x86? where is your os stored? how? i'm going to assume for now its > something like a small hdd or compact flash, sd-card etc... which > means you have space to burn. My preferred target was ARM, but we ended up with a 486 based SOC last time I checked. The storage is whatever is on the SOC, plus CF if we need more space. The CF will be via an external IDE converter. shrugs BUT, we want to move away from having this external IDE converter, which means that sooner or later, we will have to put up with the limited storage of the SOC. I don't think of this project as having space to burn. That's why we are changing from a cut down DSL to a roll your own linux. Just plain fbcon+EFL will probably be the go.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
