We would need to export a list of all different types of materials like tile, flooring, concrete, shingles, etc to work out the costs per m, m2, m3 etc.
About the local interface - of course the most UX friendly option is what we want. I think in this case, an extension would do the job. I want the user click on the extension’s “Export Material Take Off” button and see the items load onto the web app.
Thanks again for the speedy reply Dan. My next question would be, Are you available to build such extension (I’m flexible with time) and what would be the cost. Feel free to private message me, I’ll be happy to answer any questions and tell you more about the web app.
No problem just giving some general information to help with your decision making.
This describes a toolbar button (and/or menu item) command, I think.
If there are more complex options then a html dialog with checkboxes, radio buttons, text filter inputs, etc. can be used.
The server-side web app can be displayed within a html dialog window within SketchUp, either before or after the data upload.
Myself, likely not for a large extension from scratch. (Arthritis in my hands.) And I’m not familiar with Bubble.io.
There are other coders here who specialize in web data transfer.
There are some extensions that do the wood lumber materials list collection from the model, such as OpenCutList, or CutList Bridge and others. These might be leveraged to create at least some of the “take off” data.
The data could always be reorganized to match what your server app expects. Ie, current extensions often compile CSV data table files. These are easily converted to JSON.
And, by the way, Ruby has easy ability to create JSON data strings. Many extensions use this to save or write local JSON data files. Some extension send and receive JSON data via the HTTP calls mentioned above.
The server-side webapp page can detect that it’s running inside a html dialog by parsing the User Agent string. When this is the case an “Upload from SketchUp” button could appear. The onClick event handler function attached to the button can fire a Ruby callback (from your SketchUp extension) to prepare and send the data to your server.
But this is only one way to do it. The data gathering interface could also be all client-side and only display the server-side webapp page after a successful upload.
Whatever seems intuitive to the end users is best.
Not meaning to exclude anyone specific nor in any particular order …
Take a look at some of the projects of these programmers: