Peter M. Groen / dali-demo

  • Fixed physics initialization in benchmark ...
    29710d93 
    Physics bodies created in the same location creates too many
collision arbiters when added to the space, and initialization
takes too long

Solution: ensure that they are positioned separately before
adding to the space.

Note, if there are so many particles that they overlap, then collision
is noticeably slow.

Change-Id: I88f8ce970bcceb90b213d0f9999400a4e2134944
Signed-off-by: David Steele <david.steele@samsung.com>
    David Steele authored
     
    Browse Code »
  • Added option to benchmark physics 2d example ...
    8144f125 
    Added option to execute physics or animation benchmark.

Change-Id: I5ecf677cb296e02fecc1fa2287da2141bdbcf191
Signed-off-by: David Steele <david.steele@samsung.com>
    David Steele authored
     
    Browse Code »
  • Optimized benchmark animation (Reduce event thread overhead) ...
    a05f0941 
    Since we were create new animations every PropertyNotify, and at that time,
we iterate whole balls.

If event thread time delayed (~= the ball is very much) event callback
stacked a lot, and then break the app.

To avoid it, we make the number of animations relative with ball +
change the animation only if we need, not always.

It will reduce the event thread overhead.

Change-Id: Ic6da267e827d012c9e68c7d64594596f3617233a
Signed-off-by: Eunki, Hong <eunkiki.hong@samsung.com>
    Eunki, Hong authored
     
    Browse Code »
  • Added 2d physics benchmark ...
    f6389206 
    First 30s, runs N balls using Animation & property notification that don't
interact,
Second 30s, runs N balls using 2D Physics and collisions.

N by default is 500, but can be changed on the command line.
FPS tracking is automatically switched on for this benchmark

(Also changed CMakeLists.txt to be able to work as a subdirectory
in a multi-repo build)

Change-Id: Iccee1d40650563e3f45e021b4fb3fff871cc393e
    David Steele authored
     
    Browse Code »
  • Add window example ...
    ed4bd29a 
    <Summary>
DALi is a rendering engine of NUI and was previously a public interface that can be used by applications, but now it is only used as an internal engine, so most verifications are verified by NUI sample and UTC. This makes it difficult to verify whether it is DALi's own issue or NUI issue.

<What>
A window sample was added to the DALi-demo so that the APIs provided by DALi can be verified. This patch contains the DALi Window Function function.

<Why>
Other modules of the existing DALi had samples in the dali-demo, so it was possible to verify the function in the DALi layer, but the window did not have the sample, so it was difficult to verify the DALi window itself. In addition, the Window module itself had a strong dependence on external modules such as Display Server, AppFW, and Sensor FW, so it had no choice but to perform limited verification to the existing UTC.
To solve this problem, I am adding the sample.

<Plan>
Now the patch is only provided with samples for Window Function. We also plan to add function verification for Event or Signal.

Change-Id: I415a8795684964a492f1a229f17e129a02903724
    Wonsik Jung authored
     
    Browse Code »