Is there a design philosophy behind the decision not to implement permanent viewport construction guides?

 From:  jonmoore
6363.7 In reply to 6363.2 
>Having construction lines clear out at the end of commands solves that problem, you don't have to do any extra steps to eliminate the guides that you created for getting a >particular strategic point pick.

>Since you don't need to spend any extra effort to get rid of them it also kind of takes away any hesitation about putting them in. It just generally makes it easier for them to >be used more frequently.

Everything you state here makes complete sense to me and I'd agree that for many users this strategy of having constructions lines automatically clear after every command could make it easier for those users to make greater use of construction lines as they're a whole lot less hassle to manage. It's certainly one of the things that I've enjoyed about working with MoI. However architectural modelling is based on a lot of repeating design patterns (a simple example being the spacing of window openings on a wall) and in this case you need permanent construction guides to aid you when designing these aspects so it's great that there's a script available that enables the user to keep their guides after completing a command should they choose.

I think it will really benefit end users when you've been able to implement the scripts browser within MoI we've discussed previously so that access to this kind of script is made as simple as possible. I wouldn't suggest for a second that MoI should ship with all the scripts listed on Petr's page but a pick of the best and an ability for users to easily add new scripts to the library.