Hi, > that's why I explicitly removed Edje. Edje pulls too much, and will not aggregate that much value for the BIOS case (show menu and similar). Of course it would be nice to have a complete environment with Elementary and all, > but I don't think it's doable without LOTS of effort, so stick with Evas first -- particularly pre-Eina Evas.
Maybe I misunderstood about Edje, I thought that was some kind of C like meta-language layer to seperate UI and code. I'll try to use pre-Eina Evas though I still couldn't get my Win7 + MinGW right (lots of autotool error) >If you need to strip the libraries, I'd recommend to remove the following chunks from Evas: > - Gradients: it was removed in current Evas, but the pre-Eina still contained it with lots of useless code; > - Textblock: if you don't need text markup or multi-line text, you can remove this and lots of code. I'l need Textblock for further usage. > And of course choose the minimum set of engines and options, I'm not sure the bootloader can use MMX/SSE, then you can compile out those with ./configure flags. Yes, we have SSE2, which is for security check, grab them libs to use will be okay. In UEFI environment we have events and notify, basic Bit blit function to access raw framebuffer, timers..etc. Not much like the OS but will do some good. > NOTE: which hardware are you using this? It seems like a nice hobby project I'd help on weekends, but I'd need to have a way to test :-) I use coreboot or UDK2010 ( http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=UDK2010) , the later has some NT32 simulation, which can use as a basic test on host machines. But if you are talking about real platform, I almost have everything because I work in a vendor. Not familiar to all of this (toolchain, environment and I don't know how to find E17's writing guide) I have to apologize :( , so t is hard for me to catch up all the information. But my target is to port a open-sourced UI lib for BIOS to use, not only in setup menus, but also some UEFI shell applications, it will magically reduce a lot of working hour, for BIOS / Driver developers to work only on the function, not to take care the unawareness of the UI. On Tue, Apr 30, 2013 at 8:31 PM, Gustavo Sverzut Barbieri < barbi...@profusion.mobi> wrote: > Hi, > > > On Tue, Apr 30, 2013 at 8:57 AM, Carsten Haitzler <ras...@rasterman.com>wrote: > >> On Tue, 30 Apr 2013 18:03:21 +0800 hYde <hyde....@gmail.com> said: >> >> > Since my BIOS has only about 8MB of space, I take Evas + Edje. >> >> you'll need ecore, eet and eina too then. (well some of ecore). > > > that's why I explicitly removed Edje. Edje pulls too much, and will not > aggregate that much value for the BIOS case (show menu and similar). Of > course it would be nice to have a complete environment with Elementary and > all, but I don't think it's doable without LOTS of effort, so stick with > Evas first -- particularly pre-Eina Evas. > > > > > >> > May I ask what is pre-merge? >> >> efl 1.7.x ... from efl 1.8 we have a single build tree and we have upped >> our >> dependencies. 1.8 is not out yet.. but release is scheduled for end of >> may. > > > Yes, but I'd strongly encourage to find out the Evas version before Eina > was introduced. Then you don't need Eina, just Evas types that were built > in (saves a lib to care and some Kb in the final image). > > With Evas all you need is to create an engine similar to "FB", give Evas > the framebuffer (pixels) to paint and that's it. If you can configure your > FB, then it should be pretty simple to get it running. You can copy > Expedite's model, that is basically a loop: > while (1) { > event = get_event(); > if (event) process_event(event); > evas_render_updates(evas); > } > > from process_event() you can arrange your objects as you wish (create, > move, resize...), evas_render_updates() will take care to draw them to > output. Eventually you'd have to ask the FB to update itself, depends on > your setup. > > If you need to strip the libraries, I'd recommend to remove the following > chunks from Evas: > - Gradients: it was removed in current Evas, but the pre-Eina still > contained it with lots of useless code; > - Textblock: if you don't need text markup or multi-line text, you can > remove this and lots of code. > > And of course choose the minimum set of engines and options, I'm not sure > the bootloader can use MMX/SSE, then you can compile out those with > ./configure flags. > > > NOTE: which hardware are you using this? It seems like a nice hobby > project I'd help on weekends, but I'd need to have a way to test :-) > > > -- > Gustavo Sverzut Barbieri > http://profusion.mobi embedded systems > -------------------------------------- > MSN: barbi...@gmail.com > Skype: gsbarbieri > Mobile: +55 (19) 9225-2202 > ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
