Hello. On 10/10/12 09:50, David Seikel wrote: > On Wed, 10 Oct 2012 09:37:00 +0100 Stefan Schmidt > <s.schm...@samsung.com> wrote: >> Image loaders are way more complicated sadly as we drag in >> dependencies here. I would vote for making jpeg, png, gif, bmp, eet >> on by default. >> >> For the others we might need to see what libs distros ship in a >> default installation so we can decide if we have a hard dep on these >> libs or not. > > Better would be to remove the options, but detect them at build time to > see if they should be included. Things should never be hard > dependencies, unless they actually are.
I see that you don't want to have this for your embedded project. :) But I disagree here. Autodetection is even worse in the case for the image loaders as your application will fail during runtime to load a theme or display thumbnails, etc. In your strictly controlled env this is not a problem as you can only blame yourself but in my opinion this is a no-no for almost all other users. Thus I would vote against autodetection and choose the hard deps carefully to fit the majority of our users. regards Stefan Schmidt ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
