Pages: « 1 2
  Print  
Author Topic: Can enigma be a widget engine?  (Read 3499 times)
Offline (Male) edsquare
Reply #15 Posted on: August 05, 2014, 01:48:55 PM

Member
Location: The throne of ringworld
Joined: Apr 2014
Posts: 402

View Profile
An empty GM project is 15mb of ram right now. With all the bells and whistles of a widget, it probably be around 30mb. Taking into account I have seen rarely more than 3 widgets at the same time, then that is 90mb. Which is not that bad. The "engine" what you call shouldn't be more than a few megs in program anyway. Gathering data isn't that ram consuming. On the other hand the rendering and all that can be. From what I found widgets do use about that much ram or even more. They usually also use more CPU (like 2% to 9%) - this is from a topic I just read about Win7 gadgets.
And you said you would want to use JS and python to render them. I don't know what you can use to render JS as a widget though, I'd say Adobe AIR, which uses about 200mb of ram when launched. So I doubt you would get much less ram usage, than regular ENIGMA.

Okey gotcha, so it would be better and faster if done individually and operate individually, great! that means same stuff on windows and on linux, mac can go fuck itself, as for android... well when we can export to it I'll be more than happy to.
Logged
A child of five would understand this. Send someone to fetch a child of five.
Groucho Marx
Offline (Unknown gender) TheExDeus
Reply #16 Posted on: August 05, 2014, 02:10:17 PM

Developer
Joined: Apr 2008
Posts: 1872

View Profile
I cannot guarantee it will be better or faster, but I think it would be. Depends on what is the alternative, which you haven't really mentioned. Or even the resource consumption of current widget engines.
Logged
Offline (Male) edsquare
Reply #17 Posted on: August 05, 2014, 02:18:57 PM

Member
Location: The throne of ringworld
Joined: Apr 2014
Posts: 402

View Profile
I cannot guarantee it will be better or faster, but I think it would be. Depends on what is the alternative, which you haven't really mentioned. Or even the resource consumption of current widget engines.

The only one I've used is the desklets engine for gnome (Python) and I don't remember it's usage of cpu and ram  :( I would need to investigate to see if it's really interesting to do it anyway, but being interpreted JS, and python, and using qt in the case of some I would imagine its not little.
Logged
A child of five would understand this. Send someone to fetch a child of five.
Groucho Marx
Offline (Unknown gender) TheExDeus
Reply #18 Posted on: August 05, 2014, 03:21:11 PM

Developer
Joined: Apr 2008
Posts: 1872

View Profile
That is my reasoning as well. If a widget can be programmed in JS, then it's very unlikely to eat small amount of resources. Unless you somehow don't compile that JS into a native binary. That is why ENIGMA is actually not a bad platform for widgets, as it is compiled, extensible and modular (so you can remove whatever you don't need and leave only what you do need). This ends up as low ram and cpu usage by default.
Logged
Pages: « 1 2
  Print