On Wed, Jun 15, 2011 at 7:40 AM, Mike McCormack <[email protected]> wrote: > On 06/15/2011 07:31 PM, Gustavo Sverzut Barbieri wrote: >> On Wed, Jun 15, 2011 at 4:28 AM, Enlightenment SVN >> <[email protected]> wrote: >>> + out->Set(v8::String::New("_eo"), v8::External::Wrap(eo)); >> >> Mike, >> >> A hint for you is to store common strings in a pool and use their >> reference later. Good cases are "_eo" and property names such as >> "size", "color"... this way you avoid creating/destroying lots of them >> for simple and common queries... and may avoid typo errors as well. > > Hey Gustavo, > > Thanks for the hint. I will try optimize it a bit more once I get > the structure looking right. Right now, I'm trying to make > setting a property on an object in JavaScript update that property > in Evas immediately.
yes, I understand it. Just consider this one a structure part as well, otherwise you'll have hard time looking for all cases later on :-) It's more of a design decision than actually optimization in the sense of profiling -> spot the hot path -> fix, as it will hardly be visible in that way, but will fragment memory in the long run. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
