This was a logical result of what I had been advocating: A separate Blueprint Tab and Takeoffs On Overlays Instead of Pages. Effectively, this meant you would navigate the takeoffs (relevant drawin...

As much as I like the idea of preset design phases/milestones, it doesn’t have much relevance for residential construction in my area. Sometimes it seems like it goes from a stamped set, to design,...

Thanks Heber! This is what I needed to hear from you guys. If you could address these issues adequately, it would convert masses to zzTakeoff even without AI functionality.

The general structure of the documents here would be perfect for a blueprint tab. However, the key here is, as Kyle suggests, the “ability to transfer takeoff between milestone sets.” And that is e...

I would also like to see what’s going on dev side as well, since I will need to thoroughly understand your implementation in order to prepare data for POS.

Mark, I’m not sure I’m understanding your reservations in having blueprint related functions separate from takeoff related functions. Or is it the complimentary overlay concept that gives cause to ...

Mark, This was definitely a consideration in my thinking!

Mark, What I gather from what you are describing is that a minimum of two different tabs is required: one for doing takeoffs and one for doing research. This is why I had suggested elsewhere that t...

Again, this is easily accomplished using an overlay for takeoffs instead of pages, since you could align the underlying drawings however you like.

With takeoffs on overlays instead of pages, only the referenced pages would be shared for a particular overlay (since the overlay acts as a folder for referenced pages as well).

Edit: ***This way you don’t have to define views after the fact, they are put together as a matter of course and shared as needed.

If the takeoffs were on overlays instead of pages, all you would have to do is share the relevant overlays with the relevant parties. These would suffice in giving users the required views. If edit...

Heber, Why not have the takeoffs live in the layer (to use your terminology) and have the blueprint drawing/page have a home as a reference for that layer?

Heber, So is this “layer” idea analogous to the “overlay” idea that I am advocating with the takeoffs being separate from the blueprint pages? Or are the takeoffs still on the blueprint pages?

^This. The problem is that we are all spending time putting together representations of specific blueprints and not constructing models of the building to be. Architects and designers can be as cr...

I am not against the magnifer, but my experience with FPS games tells me that there is no loss of context when scoping in and out quickly enough. Show me the world’s fastest estimator, and I’ll sho...

I think printing, in general, needs to be relegated to the report tab. If takeoffs are on overlays instead of pages, then these sorts of “visual reports” could be automatic.

I think I would prefer a method of quickly defining 2 different zoom levels to hotkeys. So together with “zoom to fit” you would have 3 zooms to work with. Zoom the whole screen and avoid the tunne...

I currently use PlanSwift but have been working to revamp pretty much everything that I have access to. This is one of those things where I don't quite have access to everything I need to make it ...

I think it is a game changer while it is working…but the second it does anything wrong it loses all confidence. So no, I’m not very excited about it.

Sophia,What you are describing is exactly the reason for the takeoffs to be on an overlay. When you get new/updated/revised drawings/pages you just change them out. Slip the new pages under the exi...

These all look like reasons for Takeoffs On Overlays Instead of Pages. Each estimator can work on their own assigned divisions/pages/subsystems/items/anything either individually or with others. If...