On Mon, Feb 23, 2015 at 4:27 PM, Cedric BAIL <cedric.b...@free.fr> wrote:
> On Mon, Feb 23, 2015 at 4:56 PM, Daniel Kolesa <dan...@octaforge.org> > wrote: > > On Mon, Feb 23, 2015 at 3:55 PM, Daniel Kolesa <dan...@octaforge.org> > wrote: > >> On Mon, Feb 23, 2015 at 3:50 PM, Oleksandr Shcherbina < > >> o.shcherb...@samsung.com> wrote: > >>> Sorry guys, > >>> > >>> capital letters will be changed asap. > >>> > >>> Also we plan reduce quality of resources. > >>> > >>> It example useful for testing, because gathers features together. > >>> > >>> Can you advice acceptable size for 3d models and images for > textures? > >>> > >> > >> 256x256 for this kind of stuff at most (everything above that is an > >> overkill; i believe in most cases even 128x128 would do). Fix up the > names > >> and paths (all lowercase, no spaces). Keep all textures with > power-of-two > >> sizes (32, 64, 128 etc) so that mipmapping behaves correctly (and so > that > >> the examples work with all versions of opengl and with all supported > >> hardware). As for the models, you can probably dramatically reduce > >> polycount on everything (and scale down the skins). Make sure the assets > >> dir stays small, 50MB is really bad. > > I think the requirement on being power-of-two is irrelevant in the > case of Evas as we should be using Evas_GL_Image which already does > automatic packing into an atlas with the right size for us (Otherwise > we would have trouble with all the other image we load for widgets). > As for size, I agree 256x256 should be enough for this example and I > should start paying attention to file size... > > > And yeah, as Tom said, this would best go into a separate repository. We > > don't really want this kind of stuff in efl.git. > > This I disagree. I think this is not orthogonal to efl. We are pushing > a 3d and a vector scenegraph in efl to use it for widget and > application. Showing how to use that infrastructure does make sense. > > Same actually goes with exactness data, as we are doing a graphical > toolkit and we don't have visual test in our make check. It's just a > shame and a bad excuse for not having it. If you really want that out > of the main git, I guess we could use some submodule and force make > check/examples to pull that part if necessary, but that doesn't feel > reliable at all. > Doesn't matter. We could have an efl-examples.git repository and link it as a submodule, then only people who need those examples could get it and the others (i.e. majority of people, as most never build examples at all) could do with smaller repo. > -- > Cedric BAIL > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
