Thanks for your valuable input! We'll take it into consideration. If you have feedback for the developer team in the future, please be sure to include technical data to support your comments so that we can evaluate it fairly.
On Thu, Jan 11, 2018 at 3:41 AM Carsten Haitzler <ras...@rasterman.com> wrote: > On Wed, 10 Jan 2018 20:38:27 +0000 Stephen Houston <smhousto...@gmail.com> > said: > > i'm going to put my take on this: i think this is bad. it flies in the > face of > everything e was built to do. to be efficient. having a process per gadget > is > horribly inefficient. this is precisely what helps bloat out gnome and kde > memory footprints and what has kept e lean. > > while avoiding e crashing due to a bad gadget is a good thing, the > following is > just a bad way to do it. > > 2 other alternatives: > > 1. have a SINGLE "gadget process" to hold all gadgets and load modules into > this process, so we don't have 20 processes, but instead have just e + > gadget > process. > > 2. remote ui. gadgets could be written in any language that can do stdio. > they > echo/printf commands to e to create objects and change their state, and e > "echos" back on stdin events and things the gadget should know. your gadget > could be a stripped down super-lean basic libc executable. python. shell > script. anything that can do stdio. while this still has 1 process per > gadget - > it's for the back-end only and this should make then far leaner than with a > full ui. > > i actually wanted to spend time on #2 but am busy with efl atrm. #2 would > be > great because it'd massively lower the work needed to quickly make a > gadget of > your own. write it in python or shell quickly and dirtily and life would be > easy. > > > Hello, > > > > I would like to point everyone to a new wiki page we have that details > > developing gadgets for Enlightenment using the sandbox method. > > > > https://www.enlightenment.org/develop/e/sandbox_gadgets > > > > Feel free to use the guide to create cool new gadgets for E and make sure > > you contribute back feedback about the guide so we can improve it as > needed. > > > > Thanks! > > Stephen (okra) > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > Carsten Haitzler - ras...@rasterman.com > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
