FOSS culture is quite flexible. You may do as you wish.
All the best,
That will take some time. Moreover for a new type of work, estimate may be come guestimate
All looks great.
Fantastic. I would prefer vertical expandable.pPodest wrote: ↑Sun May 26, 2019 1:35 pmAlso if a comment is linked to a viewpoint I want to make this visible by coloring the comment in a light shade of blue or any other non-signal-color. With a double click on such a comment the view of the object shall assume the settings defined in the viewpoint. For adding comments the text field and the "Add" button can be used.
Below the comment section a horizontal list of snapshots could be displayed which are shown in original size when clicked. If more than three snapshots are available in the topic then a horizontally scrollable list or a vertically expandable list would be a solution.
Good progress.pPodest wrote: ↑Sun May 26, 2019 1:35 pmThe last part is for showing the available viewpoints, in list form. Therefore I want, contrary to the screenshots, to hide the above mentioned parts and show the list with a button that, when clicked, shows the selected viewpoint. Because how I currently set up the UI, all the above parts are aligned in one vertical layout, with sublayouts, and no groups I couldn't show this in the screenshots. In the next version I want to add groups, like yorik's BIMBots plugin uses, and then have a comments and viewpoint group.
Partially: Yes! I want to give the author the possibility of changing his or her own comments, but, apart from the modified date, I don't want to keep any change logs. Although the definition of the comment structure, in the corresponding XSD file suggests that also other people can edit the same comment. Especially the ModifiedAuthor field in the comment suggests this. I think it would make more sense if only the original author could edit his or her comment, like it is in this forum (for some timelimit at least).
Thank you very much! I will do it vertically then
Currently it looks redundant, I agree with you. I thought of it not to only save newly added comments, but also other changes that might be applied to the all encompassing project object (i.e.: the representation of the BCF file in a python data structure). Like a newly added viewpoint.
There already exists something like that? Well thank you for the hint, I will change it accordingly!
what are you thinking about? Do you mean like adding and removing topics? Well I want to integrate adding topics, but only after I have finished the BCF viewer part. But deleting topics would not make that much sense, does it? I can imagine that it is preferable to have a collection of all topics/issues at the end of a project or planning phase of a building project.
... well this will give some hours of headaches ^^ What would you suggest to do in the case that certain elements don't validate? With xmlschema I have the option to ignore non-conforming nodes and attributes during parsing the XML file. I could ignore them altogether and don't write them to the data structure, but this means that the data gets lost. Another possibility would be to define a new class that replaces every value currently in the class model. This class would then have two values, one indicating whether the corresponding node/attribute of the XML file could be parsed, and one that contains the parsed value of that node/attribute. If it could not be parsed then the plain XML code would be written to the value field instead. I hope this is somewhat understandable. Maybe the code example helps to clarify my point a bit:
Code: Select all
class Element: self.valid self.value validNode = Element(True, "3") invalidNode = Element(False, "<node>3</node>")
I was more thinking about comments, not topics. It's true, you have a point there. We can think of a bcf file as a git repo where one would be unable to edit the history. But comments should still be editable because you could make a mistake writing it and would want to correct without having to rewrite it all over again.pPodest wrote: ↑Thu May 30, 2019 7:27 amwhat are you thinking about? Do you mean like adding and removing topics? Well I want to integrate adding topics, but only after I have finished the BCF viewer part. But deleting topics would not make that much sense, does it? I can imagine that it is preferable to have a collection of all topics/issues at the end of a project or planning phase of a building project.