search

Krypton-Suite-Legacy-Archive / Krypton-Toolkit-Suite-Extended-NET-5.470

An extension to the Krypton Toolkit suite of controls for .NET framework 4.7
BSD 3-Clause "New" or "Revised" License
53 stars 11 forks source link

Can the "Extended Toolit" be broken into seperate "Chunks"... #87

Closed Smurf-IV closed 5 years ago

Smurf-IV commented 5 years ago

When downloading the existing "Extended kit" just to use a MessageBox and a button, It needs to pull in several Third Party NuGet packages as well.

Please can these third party package requirements be "broken out" into seperate "singular" extensions, so that if a user want to use scintilla etc. they can take that nuget extension as needed.

PWagner1 commented 5 years ago

Do you mean like a core/basic and full versions? If so yes, that will be possible.

PWagner1 commented 5 years ago

I've actually thought about it when doing the floating tool/menu strips!

Smurf-IV commented 5 years ago

Do you mean like a core/basic and full versions? If so yes, that will be possible.

Probably, Core: Only a single dll that has the controls that do not need any other nuGet package (Apart from Krypton base !) Winform Anim Ext: The controls that allow animation (With Core as a dependency etc) Scintilla Ext: An Additional Ext Dll that overrides those controls (With Core as a dependency etc) APICodePack Ext: whatever is needed for that to happen until other methods that do not rely on them are used (With Core as a dependency etc) Experimental Ext: Controls that are still underdevelopment (Probably the equivalent of your Full version)

PWagner1 commented 5 years ago

Will need to pick apart the toolkit to see which controls go where. Might also do a colour control one and a dialogs one plus a IO/System one for file system controls.

PWagner1 commented 5 years ago

Hi @Smurf-IV

I found out that all modules will require the standard toolkit as a base. By doing this, it makes me wonder if I should split up the standard toolkit into modular NuGet packages too?

Smurf-IV commented 5 years ago

if I should split up the standard toolkit into modular NuGet packages too?

At least just the "base Component controls", and then leave the Complete Toolkit as the current "Standard" NuGet package. Not Sure what it could be called (Minimal, Base, Controls, Toolkit Controls only, ... )

PWagner1 commented 5 years ago

Yes still have all binaries all in one package, but have 6 new packages for each separate DLL/XML files. I may also package all the palette XML files into another separate module package.

Maybe name them as follows:-

Smurf-IV commented 5 years ago

Yes still have all binaries all in one package, but have 6 new packages for each separate DLL/XML files. I may also package all the palette XML files into another separate module package.

This will work, It will just be the "Management" of the NuGet releases thay could be the downfall of this.....