Just submit your changes and I'll dump them on SVN, or sign up for the power to do SVN Commit :)
It sounds like you want to do some biggish changes, but essentially just to sorting everything, so it shouldn't hurt the final use of the library much or at all, right?
Therefore, no problem.
Snapshots from SVN will be kept around for a while, so anyone wanting Klepto's original arrangement can still use it. (Either from Klepto himself or from the snapshot).
I agree with the giant Functions file being a bit troublesome because it is still rather bulky.
However, it seems logical with the files for each type declaration being specifically for the Type declaration (and only the Type declaration).
Thus, if you want to change that (and go ahead!) I suggest putting functions into files like FBrush.bmx, FMesh.bmx, etc.
Conts... I'm assuming you mean constants defined somewhere?
Ah, in the MD2 loader?
May as well change as long as it doesn't hurt anything...
Of course, for changes like this in the glorious future, discussions should be created in the discussion group. At this time, there is probably little point.
I also see what you mean about the MD2 loader...
I was about to start a discussion (for what it's worth at this point in time :b) about Extensions, and how it will become tempting to add features that sometimes don't quite fit in smoothly to the design.
I've noticed with Irrlicht, for example, that things look horribly messy when there are strange debug tools lying around in the source code, such as automatic FPS cameras which nobody in their right mind would use in an end product (and which are not hard to create!).
If somebody wanted to add a debug tools thing to MiniB3d, it could be added as an optional Include following some kind of convention.
The same sort of convention could be done with the MD2 loader; a particular extension could add itself (via function pointers, perhaps?) to a list of Loaders and called cleanly/automatically, but only if the extension has been enabled.
Adding to that (I am obsessed with soft-coding), some Extensions could be included by default for simplicity and symmetry. (All file loaders as Extensions).
This probably has a speed hit, but also a big boost to the "Ooh, neat code!" thing and it improves the scalability or whatever.
Edit:
Okay, Simon, I've changed all my "3d"s to "3D"s :b
Edit:
Here is that discussion...
The idea actually is a lot like my own recent fiddlings in stuff, so I will try my hand at it; I'm already sort of in the mode for Extension System building. (Although the most recent thing has been converting my beautiful PHP 5 to PHP 4 with Magic Quotes on, so my morale is a bit low and my code may look awful now that I've become resigned to the disgusting PHP 4 glurk).
It sounds like you want to do some biggish changes, but essentially just to sorting everything, so it shouldn't hurt the final use of the library much or at all, right?
Therefore, no problem.
Snapshots from SVN will be kept around for a while, so anyone wanting Klepto's original arrangement can still use it. (Either from Klepto himself or from the snapshot).
I agree with the giant Functions file being a bit troublesome because it is still rather bulky.
However, it seems logical with the files for each type declaration being specifically for the Type declaration (and only the Type declaration).
Thus, if you want to change that (and go ahead!) I suggest putting functions into files like FBrush.bmx, FMesh.bmx, etc.
Conts... I'm assuming you mean constants defined somewhere?
Ah, in the MD2 loader?
May as well change as long as it doesn't hurt anything...
Of course, for changes like this in the glorious future, discussions should be created in the discussion group. At this time, there is probably little point.
I also see what you mean about the MD2 loader...
I was about to start a discussion (for what it's worth at this point in time :b) about Extensions, and how it will become tempting to add features that sometimes don't quite fit in smoothly to the design.
I've noticed with Irrlicht, for example, that things look horribly messy when there are strange debug tools lying around in the source code, such as automatic FPS cameras which nobody in their right mind would use in an end product (and which are not hard to create!).
If somebody wanted to add a debug tools thing to MiniB3d, it could be added as an optional Include following some kind of convention.
The same sort of convention could be done with the MD2 loader; a particular extension could add itself (via function pointers, perhaps?) to a list of Loaders and called cleanly/automatically, but only if the extension has been enabled.
Adding to that (I am obsessed with soft-coding), some Extensions could be included by default for simplicity and symmetry. (All file loaders as Extensions).
This probably has a speed hit, but also a big boost to the "Ooh, neat code!" thing and it improves the scalability or whatever.
Edit:
Okay, Simon, I've changed all my "3d"s to "3D"s :b
Edit:
Here is that discussion...
The idea actually is a lot like my own recent fiddlings in stuff, so I will try my hand at it; I'm already sort of in the mode for Extension System building. (Although the most recent thing has been converting my beautiful PHP 5 to PHP 4 with Magic Quotes on, so my morale is a bit low and my code may look awful now that I've become resigned to the disgusting PHP 4 glurk).