2D Toolkit Forum

2D Toolkit => Add-ons and Extensions => Topic started by: cakesauce on March 12, 2014, 12:55:49 pm

Title: Optional 3rd Party Support Strategies for tk2d
Post by: cakesauce on March 12, 2014, 12:55:49 pm
Hey,

I'm in the process of releasing an asset (http://stevekellock.com/ps2d) and I'm looking to add tk2d.

The thing is... I'd like it to be optional, but contained in the asset.

I've seen what the ColliderGen guys do with their reflection-meta-fu, but I'm thinking that might be overkill for me (beyond my skills and patience :) )

Basically, I don't want to blow up people's projects because they don't use tk2d like I do. 

Are ifdef's an option?
Should I comment out all tk2d references?
Do I rename the files to .txt so they don't get loaded?
Maybe offer an additional download?
Code generate the .cs files?
Suck it up and go meta like real programmers?

Just wondering what the best approach as I get started refactoring here.

Cheers!

Thanks for tk2d btw. 

Steve


 
Title: Re: Optional 3rd Party Support Strategies for tk2d
Post by: unikronsoftware on March 12, 2014, 01:35:45 pm
Ifdefs would be the easiest option, but a pain to maintain as you will have to make sure your project works with and without them. You could also offer an additional download for t2kd support.

To be honest the ideal option will be a unity package within it, but the asset store guys don't like that annoyingly.
Title: Re: Optional 3rd Party Support Strategies for tk2d
Post by: cakesauce on March 12, 2014, 01:55:22 pm
Thanks for the quick reply.

Ya, I saw in the Asset Store rules "No .unitypackages need apply".  Bummer.  I know ProBuilder2 uses them for the purposes of Good, but I understand why Unity is not onboard.

I'll start with #define for now.  Thanks for the advice.

Title: Re: Optional 3rd Party Support Strategies for tk2d
Post by: BillBurning on July 02, 2018, 08:30:24 am
 pain to maintain as you will have to make sure your project wor