Simon Brown Posted May 26, 2009 Share Posted May 26, 2009 I'm currently working on code for the next version of CBM that will move to using Paint.NET FileTypes to load brushes rather than those based on a custom interface to allow extensibility without creating a new API. However, CBM also supports GIMP brushes and i'm not sure of the best way to implement this. I can currently see several options: [*:1hhpomen]Distribute the DLL with CBM as a seperate file. This has the advantage of keeping supported formats consistent and also allows users to open GBR files outside of CBM. However, it might be confusing for newbies to know where to put each file, although this effect would be diluted by the inclusion of the installer.[*:1hhpomen]Distribute the GBR format as a seperate plugin. This would allow users to choose whether they even want GBR support and it would also allow me to work on this plugin separately, I could even decide to GPL it if I no longer had the time to work on it. However, the GBR support seems specific to CBM and users would be forced to hunt to find what should be (in my mind) a core feature.[*:1hhpomen]Inject the GBR FileType into the FileTypes CBM scans. This would keep everything together and avoid confusion. Although it would prevent users from using GBR in Paint.NET and sacrifice consistency. Which of these would be the best option? Quote Link to comment Share on other sites More sharing options...
pyrochild Posted May 26, 2009 Share Posted May 26, 2009 I'm currently working on code for the next version of CBM that will move to using Paint.NET FileTypes to load brushes... What do you mean? Having the FileType plugin copy the file into the PdnUserFiles dir? Rick's not going to go for that. A FileType plugin's sole purpose is to enable saving and loading an image from and to Paint.NET. Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Simon Brown Posted May 26, 2009 Author Share Posted May 26, 2009 To parse brushes inside the brushes directory. Quote Link to comment Share on other sites More sharing options...
pyrochild Posted May 26, 2009 Share Posted May 26, 2009 [*]Inject the GBR FileType into the FileTypes CBM scans. This would keep everything together and avoid confusion. Although it would prevent users from using GBR in Paint.NET and sacrifice consistency. I have no idea what you mean by that Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Simon Brown Posted May 26, 2009 Author Share Posted May 26, 2009 As well as the FileTypes included with the PDN libraries and those in the FileTypes directory, CBM would also parse the hard-coded GBR plugin without it being installed in the official sense. Quote Link to comment Share on other sites More sharing options...
pyrochild Posted May 26, 2009 Share Posted May 26, 2009 WHy not have both? Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Simon Brown Posted May 26, 2009 Author Share Posted May 26, 2009 Both a seperate plugin and a hard-coded one? Every change to the GBR plugin would require an update and that solution would require the GBR plugin to be embedded as a pre-compiled (well, pseudo-compiled) resource rather than part of CBM's code. Quote Link to comment Share on other sites More sharing options...
pyrochild Posted May 26, 2009 Share Posted May 26, 2009 You can include a source code file in more than one project... But using an installer would take care of this dilemma, too. Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Simon Brown Posted May 26, 2009 Author Share Posted May 26, 2009 You can include a source code file in more than one project... I guess that would work, although it would still complicate release. But using an installer would take care of this dilemma, too. That'd work if everyone used the installer. Quote Link to comment Share on other sites More sharing options...
pyrochild Posted May 26, 2009 Share Posted May 26, 2009 Don't give them a choice! Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Simon Brown Posted May 26, 2009 Author Share Posted May 26, 2009 Force Vista (well, and XP, but i'm talking relatively) users who want to install the plugin to give admin privileges to another random program? Quote Link to comment Share on other sites More sharing options...
pyrochild Posted May 26, 2009 Share Posted May 26, 2009 Yes. Besides, not everyone who uses Custom Brushes needs to be able to edit GIMP brushes, and not everyone who wants to edit GIMP brushes needs Custom Brushes. Keep separate things separate. Quote ambigram signature by Kemaru [i write plugins and stuff] If you like a post, upvote it! Link to comment Share on other sites More sharing options...
Simon Brown Posted May 27, 2009 Author Share Posted May 27, 2009 I guess after [hopefully] receiving confirmation from Rick that the new CBM wouldn't be removed i'll implement the third option via two folders for effects and filetypes. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.