Best place for development discussion?

[rgm]

As I continue to learn about the source code I find myself asking many questions such as, “Why is it desirable for objects to have an ID length of at least 12 (or 13) characters?” or “do you mind if I add a dependency on the lodash library in order to simplify some expressions?”

What is the best method to discuss the source code? Should we use the wiki in GitHub? Should we create a “Development” category in this forum software?

[valentin]

I do have little experience with the Github wiki.
I implemented this forum because it works very well for the openframeworks community.

I think we can combine the wiki and this forum here.
This forum is perfect for on going discussions.
However, a wiki is much better to generate a clean map of the platform.

What do you think?

I opened a new development category and moved the answer for your ID question to it:

Object Identification in a global scale

At this point the ID length comes from the uuidTime() function added with the name of the object. The fixed ID length comes from an early stage, where it made sense combining the name and the ID in to one string to make the UDP ping format easier. This is obsolet now. The goal for an object ID should be to generate a number that is “impossible” to be generated twice somewhere else in the world, since the objects should eventually be able to be referenced globally. It might be more clean, to m…

[valentin]

What would be the benefit of lodash?

[rgm]

There are quite a few benefits to using the lodash library, chiefly readability and compactness leading to increased ease of maintenance. For example, at a glance, can you tell what this does:

beatInterval + (Math.floor(Math.random() * 500) + 1) * (Math.floor(Math.random() * 2) == 1 ? 1 : -1))

Compare to the lodash equivalent:

beatInterval + _.random(-500, 500)

[valentin]

Ok lets use it.

Additionally: The OpenHybrid arduino Yun image has SSHFS on board.
You can mount the filesystem via
SSHFS: sshfs root@object.local:/ ~/mountpoint

In case you want to test right on the YUN

[rgm]

Very handy thank you. I’m still waiting on my Yún to arrive, so unfortunately I’m coding a bit “blind” at the moment, apologies if there are breaking changes. I hope to add some tests to minimize that possibility when I have fully understood the system and played with the getting started examples first-hand.

[valentin]

I just posted some diagrams that I had for reflecting the server architecture.
It does not show very accurate how the platform is actually working at this point, but it might give you a hint how everything fits together. I think the foundational structure around the objectEngine should still be the same.

Flow Diagramms for the Object Server

I have created two diagrams last year to sketch out how the server architecture works. They are far away from being accurate at this point! But they show a little bit how the architecture evolved. The Hybrid Object Diagram is closer to the final version. Later this year I will make a more accurate map. [image] [image]