Physics Engine support

[Kevin Miller]

I will be asleep shortly. I am the only one left up so I am unable to get
anyone on the dev team to provide much more info. I've been party to
various discussions on this but I should really check with them on the
final plan for it. This blurb I have from a management doc and it is up to
date but it doesn't provide much more than is up on the site unfortunately:

The target of this goal is to provide a replacement for the existing
Œgraphic¹ object. The new object (referred to at present as a Œshape¹)
would use sub-pixel positioning and standard 2d vector paths.
Additionally, the idea of a Œgroup¹ shape type would be used to allow
nested rendering - the ultimate goal being that the Œshape¹ object be able
to import and display SVG. This is (essentially) an entirely
platform-independent project with most of the work going into the syntax
and semantics of the object, and the SVG importer.


Kind regards,

Kevin

Kevin Miller ~ kevin at runrev.com ~ http://www.runrev.com/
LiveCode: Everyone can code




On 28/02/2013 00:30, "Monte Goulding" <monte at sweattechnologies.com> wrote:

>Kevin seeing as you refuse to heed my advice to take a sleeping pill
>could you elaborate on the vector object a bit more. Anything you can
>share would be great. The other thing I'm wondering is will any of this
>stuff improve scrolling groups on iOS?
>
>--
>M E R Goulding
>Software development services
>
>mergExt - There's an external for that!
>
>On 28/02/2013, at 11:26 AM, Kevin Miller <kevin at runrev.com> wrote:
>
>> It does. That's the big challenge with the Physics stretch goal and its
>> vital to so many apps. Just hooking in the physics engine isn't so hard.
>> The GPU is where it is at, or rather, where it needs to be for this sort
>> of stuff to work well.
>> 
>> Kind regards,
>> 
>> Kevin
>> 
>> Kevin Miller ~ kevin at runrev.com ~ http://www.runrev.com/
>> LiveCode: Everyone can code
>> 
>> 
>> 
>> 
>> On 28/02/2013 00:13, "Scott Rossi" <scott at tactilemedia.com> wrote:
>> 
>>> I am fully excited.  With all due respect to Richard, I share his need
>>> for reliable video playback, but physics and better (?) vector support
>>>is
>>> substantially appealing, and makes LiveCode a viable contender in games
>>> and simulation spaces, where currently it is not. A bigger market, and
>>> more users.
>>> 
>>> My bigger overall issue is display performance.  Physics, improved
>>>video
>>> playback, and pretty much displaying everything on screen needs better
>>> performance.  Am hoping the new changes bring about a new display
>>> architecture or whatever is needed to make LiveCode worthy of all these
>>> great new features.
>> 
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>>subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>_______________________________________________
>use-livecode mailing list
>use-livecode at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode