Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Class Wizard Plugin Enhancements

(1/4) > >>

scarphin:
I've implemented scope (public etc..) selection for member variables for the class wizard. And I'm implementing other stuff to make the class wizard more suitable for general usage as I believe it is very strictly tuned to wx and CB development (like space character usage everywhere without the option for tab usage, methods implemented in class definition etc...). So please let me know if it is still maintained as I don't want my patches to end up dead in the patch tracker because of lack of maintenance. ;)

Let me be clear, my intention is NOT to change the default behavior but to add extra functionality and options for the user.

MortenMacFly:

--- Quote from: scarphin on October 07, 2014, 01:20:08 pm ---So please let me know if it is still maintained as I don't want my patches to end up dead in the patch tracker because of lack of maintenance. ;)

--- End quote ---
Yes, but please don't make it over-complicated. Sometimes its easier to just implement things in the source code than understanding and using an UI. Keep in mind, the class wizard is there especially for beginners. :-)

scarphin:
Ok thnx. Actually my syntax for a class is much more different than what the class wizard spits out (I use tabs for indentation, begin methods with lowercase, implement every method in source file etc...) but I don't have the time and patience to implement each and every different usage of mine into the wizard and I also think the easier is the better so I don't plan to complicate things. I personally believe the experienced might benefit more from the capabilities of the class wizard with some extra additions. Most of the things I plan to implement are time-consuming differences to edit manually (like deleting spaces and inserting tabs, creating methods in the source file etc...). Here is a list of what I plan:

1- Scope selection for member variables,
2- Option to use spaces or tabs,
3- Optional indentation level (like no indentation for scope delimiters and 1 level of indentation for methods or the current default),
4- Option to move getter, setter methods and the documentation for methods from header to source.

Please comment!

I'll submit the patch for item 1 to the patch tracker on sourceforge (if I can find it ;)) or should I submit it to somewhere else?

Btw I have a novice question about creating patches. How should I create patches, 1 by 1 adding functionality over the previous version or a single patch for all? Or is there any other way to create sequential patches for modifications to the same file?

MortenMacFly:
Features look ok. Make sure you consider the users default settings from the editor. For patches use svn.
Checkout your copy of trunk
Change sources as needed
Run: svn diff > my_patch.patch
From the command line and from the root of your checkout.
Post the patch at sourceforge using the tracker one by one, at best one patch per feature.

oBFusCATed:

--- Quote from: scarphin on October 07, 2014, 06:25:46 pm ---Btw I have a novice question about creating patches. How should I create patches, 1 by 1 adding functionality over the previous version or a single patch for all? Or is there any other way to create sequential patches for modifications to the same file?

--- End quote ---
Sorry to be the git advocate once more time, but if you plan to do multiple patches git is one of the softwares you can use.

About the tabs - just consider the settings for the editors and don't add UI for choosing tabs vs spaces... It should just work automagically...

Navigation

[0] Message Index

[#] Next page