Is it time for a new PyPRP release?

[Lontahv]

plClusterGroup really is just an interface for the referencing of multiple plBufferGroups, which Paradox is talking about. However, since not going though the Cluster "middle-man" works better with Blender's layout I strongly believe plClusterGroup shouldn't be merged to the trunk. The way I programmed in Clusters in interface with Blender was pretty nasty (although Paradox did clean it up slightly). Part of the reason why the ClusterGroup code didn't get merged to the trunk is because the Clusters were rather... unstable.

[GPNMilano]

I'm going to finish up tomorrow cleaning up any messes i left in my stuff and upload it all to my contrib so people can pick and choose what they want to keep.

If we're willing to break current age compatibility, like I said, I'll write up whatever supplemental documentation for the release that covers the new stuff and what needs to be adapted for proper export in the new version for pre-existing ages.

On that note, if we're willing to do that than I'll upload my material classes changes as IMO, it offers ALOT more flexibility with layer animations and all the different flags than the older version (pretty much everything is on a per layer basis in my version rather than a per-material basis the old way).

[Grogyan]

I am actually all for adding new ways of doing the same ol', if it means moving forward, just as long as we know what we will need to do.

*cringes* at thoughts of people with 10's of lights and 100's of materials that may need to be changed individually, and maybe manually */cringes*

So with that thought, as an idea, from what Robert did for PyPrp0.5 to 1.0 was to write a script that would alter that which need to change, could the same be done here too?

[Lontahv]

Yeah. A conversion script can be written pretty easily if anything drastic happens between versions.

[Marcello]

Wow... feels great to see things are really moving toward a new release! Burstmode!!

[GPNMilano]

Wow... feels great to see things are really moving toward a new release! Burstmode!!

Yes and after this release I can start putting in new stuff to the plugin that will make Bob yell at me to stop talking about them (Just Kidding Bob)

[teedyo]

Just a thought about version numbering. Would it make sense to add a level? Something like <architecture>.<compatibility>.<feature>.<bugfixes>. So this next release would be 1.6.0.0 which indicates broken compatibility with 1.5 even though it's the same architecture.

I also think that 1.5 should be tagged and remain available to those who don't want to break their work on existing ages.

[Marcello]

GPNMilano and feel free to contact me to help out and write comprehensive tutorials for the new stuff you'll add

[Whilyam]

Maybe Open Uru can have a rule that says "you can't submit your code without at least a basic explanation of what it does/changes and how it works."

[boblishman]

Maybe Open Uru can have a rule that says "you can't submit your code without at least a basic explanation of what it does/changes and how it works."

or better still ... "you can't talk about new features you have unlocked unless you are prepared to add them to the trunk and give an explanation of what it does/changes and how it works" ..... (just kidding Chloe ... )