Alternatively or in combination with this table-plugin you can export your dots as Objects Properties (*.csv). That way you can for example use the dot’s layer name as a time stamp and the object name as the comment title. You can add any text information with _SetUserText. Make sure to enable User Text in the CSV Export Options then you’ll get something like this in Excel:
I’ve developed tools for reviewing our architectural projects. It’s pretty complex and based on our project file-naming, directory structure and versioning. So I doubt that you want to adopt this. However, with some scripting it is pretty comfortable to create comments with all required properties and also directly link these with Excel.
Since you did not tell anything about your projects I’ll give some more general hints:
It is a good idea to have all major parts of your model in separate files. Good file and directory naming conventions will help to keep things organized further down the road. Same with Layer names, especially if you are working with assemblies. Versioning is a special topic which we may discuss later…
I prefer to make separate review files which contain all the comments. There are two basic ways to make a review file:
An “Assembly” where you _Insert the geometry files you want to review as blocks. You can choose to embed and/or link the files. What’s best depends on how you intend to use the review files later on. If you embed the inserted geometry, then you can view the file on any computer but it bloats the size of the review-file. If you link the geometry then the files must be in the same locations (paths) and accessible from the computer you are looking at the review file (relative paths are also possible). If you embed and link the files, then you have the geometry with the state when you made the review but you can also update the linked files from the block manager.
You can make a Worksession and _Attach the files you want to review. This is what I prefer, cause then the files are nicely separated in the Layers pane.
Inside such a separate review file you can do anything you want without modifying the geometry files. You can make named views per comment or even layouts with more detailed explanations and so on.
Hope this helps a bit. Sure there is much more to discuss…
I downloaded the plugin and it looks very promising.
As for the basic ways you described, we use worksession reviewing.
For now we only reviewing one model, so a revision file/folder setup isn’t necessary.
What I basically want to achieve is to create a script that does the following.
To create a review note:
Select an object
User input, such as Note
Automatic input, such as CurrentDate, ObjectName, Createdby (logged in user)
Add a Dot with the note number
Write the user texts to the objects or the Dots
Than export with *.csv.
In combination with the plugin this should work great!
My scripting is not very well… but here’s a start:
I think the best way to achieve that would be to use an explicit csv file structure. For example if the csv will always look like this:
CommentNumber ; CommentText ; CommentDate ; CommentLocation ; CommentLayer ; …
Then you can easily read out the file and analyze its content. You can update the dots and as well the table representation (if you are using the mentioned plugin). Or you can update the CSV-file from rhino with you custom CSV export. There is a sample in the Python-Editor Help menu about how to write text files (10 ExportPoints). This should get you going, if you have further questions I’ll try to help.
I created an excel file an used “Insert external data” to connect the export file of rhino. Set the settings to update every 1 min and it works perfect!
I even connected the autocad 2d output in the same excel file to combine the review notes.