yorik wrote:Yes that's a good idea... The thing is how to do that the clever way. There are a lot of standards to represent time (
https://en.wikipedia.org/wiki/Timestamp ) but a simple integer can be used to store a time stamp.
also, we might need something different than just timestamps, more like time spans. So this could evolve into something bigger, where your objects "belong" to a certain phase, etc...
I'm a beginner ... getting lost and learning ...
I think the gantt.py (
viewtopic.php?t=15865) code could be used as the basis for a built-in FRC planner. datetime.date was used, but if another type is better, I accept guidance.
saso wrote:First thing to check would IMO be to check if maybe IFC has support for this?
yorik wrote:I think it has, don't remember exactly what, but I've seen something about construction phases in the docs.
I do not even know where to start ...
yorik wrote:In any case this all goes into the same direction: We should look at what/how others do and build a plan...
But I think:
First stage (I'm developing):
Create object with file information: path, name, ...
Create sub-objects with task information
Linking obj FRC (property) to tasks
Do basic animation (transparency)
To appear in the FRC interface
Second stage:
Cascaded Animation managers (microelly2 help us)
Third stage:
(gantt.py)
Create interface to view the gantt in FRC
Create interface to manipulate gantt data, and export file
Fourth stage:
a dream...
Artificial intelligence: collision of objects, critical path of the work, cost as a function of time ...
yorik wrote:Maybe the construction phase needs to be like a material? An external object?
I think external object can give more freedom to designer linking obj FRC to tasks you want, but I still do not know FRC like you guys to say that.
Is it possible to create a property for objectgroup? It would be a way to create construction phase.