BrushCreate is a half-hearted attempt at OO. The procedural API should follow procedural norms.
Therefore I think the API should be CreateBrush and Brush.Create. ;-)
A properly organised, searchable set of documentation would mean that the naming convention ultimately doesn't matter.
I totally agreeTherefore I think the API should be CreateBrush and Brush.Create. ;-)
A properly organised, searchable set of documentation would mean that the naming convention ultimately doesn't matter.
For the naming convention, I'd like to see 'verb' 'noun' to set and 'noun' 'verb' to get, just as you'd use in plain english.
To set attributes:
ColorBrush
TextureBrush
...ETC...
To get atributes:
BrushColor
BrushTexture
...ETC...
This seems logical and natural to me, but I'd be just as happy with SetBrushxxx and GetBrushxxx.
I would assume Max3D will mainly be for basic languages, blitzmax b3d & blitzplus, so it should definitely be SetBrushxxx and GetBrushxx, as that has been for quite some time with blitzmax already. To set attributes:
ColorBrush
TextureBrush
...ETC...
To get atributes:
BrushColor
BrushTexture
...ETC...
This seems logical and natural to me, but I'd be just as happy with SetBrushxxx and GetBrushxxx.