Bart70
Well-Known Member
I got the warning along the lines of "if I chose a value smaller than the minimum width ensure it is no smaller than 20% of the length of the snake".
In the case I entered I did not touch the minimum width....I entered Diamond Python and 3 metre length at the top. I left the width set at its 'minimum' (as a noob I would assume that it is a minimum and allowable) and just entered lengths until I got a green box - The red warning box came up but in my case (thinking a like a person who does not understand the CoP's) would read it and assume it did not apply because I did not alter (or lower) the min width.
What about instead of the red warning box - A field is added calculating the max length snake permitted for the width entered? That way if I were trying to determine a permitted size to build an enclosure fro my snake I then get full disclosure of what I am doing - IE: I get a green box for Dimension abc x abc so I know the area complies - and a stated length telling me the max length snake for those dimensions? I could then play with the dimensions to get more allowable length or reduce if required. I think this calc will be the most used as people will enter their current dimensions to see if they comply, and will use it to plan new enclosures so having it display the maximim allowable snake length would be a good idea.
Not sure how to tackle the issue of climbers/terrestrials and floor/wall areas - Any calculator will be likely used by people who don't understand the CoPs (otherwise they would just grab a calculator) so assuming they will know (and understand) when to apply height instead of width could be a bit dicey. I have no real suggestions other requiring entry of full dimensions and using some logic and formula's to apply the appropriate ones.....but then it starts to get tricky to set up.
I appreciate the time you have put into this, and please don't see me as a 'knocker' - Part of my day job is to write technical specs for software then try to break it when it is coded so it is in my nature to try to break things. If I had the time I have resources around me that would likely allow me to set something up in a web based page to do it which would allow for a lot more options in terms of calculating and displaying data - I just don't have the bandwidth to do it and understand the time and effort you have afforded to get it to where you have.
In the case I entered I did not touch the minimum width....I entered Diamond Python and 3 metre length at the top. I left the width set at its 'minimum' (as a noob I would assume that it is a minimum and allowable) and just entered lengths until I got a green box - The red warning box came up but in my case (thinking a like a person who does not understand the CoP's) would read it and assume it did not apply because I did not alter (or lower) the min width.
What about instead of the red warning box - A field is added calculating the max length snake permitted for the width entered? That way if I were trying to determine a permitted size to build an enclosure fro my snake I then get full disclosure of what I am doing - IE: I get a green box for Dimension abc x abc so I know the area complies - and a stated length telling me the max length snake for those dimensions? I could then play with the dimensions to get more allowable length or reduce if required. I think this calc will be the most used as people will enter their current dimensions to see if they comply, and will use it to plan new enclosures so having it display the maximim allowable snake length would be a good idea.
Not sure how to tackle the issue of climbers/terrestrials and floor/wall areas - Any calculator will be likely used by people who don't understand the CoPs (otherwise they would just grab a calculator) so assuming they will know (and understand) when to apply height instead of width could be a bit dicey. I have no real suggestions other requiring entry of full dimensions and using some logic and formula's to apply the appropriate ones.....but then it starts to get tricky to set up.
I appreciate the time you have put into this, and please don't see me as a 'knocker' - Part of my day job is to write technical specs for software then try to break it when it is coded so it is in my nature to try to break things. If I had the time I have resources around me that would likely allow me to set something up in a web based page to do it which would allow for a lot more options in terms of calculating and displaying data - I just don't have the bandwidth to do it and understand the time and effort you have afforded to get it to where you have.