|
|
Post by ylee on Jul 10, 2020 22:29:39 GMT
|
|
|
|
Post by Hippytaff on Jul 11, 2020 10:35:03 GMT
I guess it's a workload issue. I'd probably suggest putting the new on hold, improving the old and reviewing the situation in a few months.
|
|
|
|
Post by ylee on Jul 11, 2020 15:08:12 GMT
You know I wanted to link to okra's article on the new gadget API, its advantages, and so on. But that blog was hosted on a Samsung website and is gone forever not even on the Wayback machine  I think the new API had the advantage of sandboxing the modules which is IMHO great. Meanwhile, a number of new modules/gadgets designed utilizing the New Api are of course killed by this change with e24 being the last e-version they will compile and run on. This includes a really great weather module. And more. However, I never did learn the new API, but put such a task on my todo list. Now I suppose I can remove it. |
|
|
|
Post by simotek on Feb 20, 2022 13:23:09 GMT
Having tried using enlightenment with the new gadgets, there was a large number of older gadgets that were missing from the new API, the new API also had some performance concerns and the people who were working on it had mostly stopped which meant at the end of the day from a users perspective either a bunch of older gadgets had to still be ported to the new api or the one or two unique gadgets from the new api had to be ported to the old.
|
|
I think the new API had the advantage of sandboxing the modules which is IMHO great. Meanwhile, a number of new modules/gadgets designed utilizing the New Api are of course killed by this change with e24 being the last e-version they will compile and run on. This includes a really great 
