The core plugins are installed by default and offer the basic functions of Code::Blocks. In your announcement in the forum please also ask for your plugin to be added to the Code::Blocks wiki plugin page with the details you would like to see on the page.Read this page for information on how to announce you have a plugin on the Code::Blocks forum.Once you have a working and production ready plugin for other developers to use then you can do the following: This will allow users to download the plugin to install on their Code::Blocks installation. Setup your own webpage on a file sharing platform that can be used for documenting and distribution of the plugin.You can do this on SourceForge or Github or your favorite source code repository web site. You will need to store the source code for the plugin for other developers to have access to it.Please read this page for creating and producing a plugin.There is no way to install them manually afterwards. You need to manually check the "contrib plugin" checkbox when asked for selected components to install. There might be information on the WiKi concerning other plugins on this page and here.įor Windows users, the default behavior of the current installer (10.05) does not install contrib plugins.Search the forums for announcements, especially the forums at.Notice that the installer / package manager might require you to enable some of the plugins specifically. Theses plugins often have their own repository or are being posted (including the source code) in the forums. 3rd party plugins - developed and maintained by the community but not (yet?) in the C::B repository. ![]() ![]() So they are integrated into the C::B SVN. Contrib plugins - developed and maintained by the community and proven to be very valuable.Core plugins - developed and maintained by the core C::B team.There are generally three types of plugins: Code::Blocks is also a very good IDE that I would recommend, although the recruitment of new users seems no not be top priority.Code::Blocks' features can be extend by using plugins, most of them listed on this page. Git appears to be the most used system these days, so it is a good idea to learn it, I guess. It took me quite a while before I figured out the part of Bazaar that I am now using (successfully). ![]() Understanding these things is worthwhile before you try integration in an IDE like Code::Blocks. subversion, Perforce or similar systems based on a central database. But it is worth noting that git, bazaar, hg and a few other source control systems are distributed and work differently from e.g. I have not used git beyond cloning locally so I wouldn't know. Figuring out how to contribute back to the project you mentioned is probably best done by asking the others on that project. I would recommend doing exactly what you have done and experiment locally before trying anything more advanced. Personally, I have few problems keeping my favorite source control system (Bazaar) separate from the IDE, although sometimes I can see closer integration would be a good idea. I would recommend checking the status of that (I have not used it). This can be done without offending I believe a Code::Blocks plugin for source control is being created for exactly this purpose, so that is a better reply IMHO. ![]() The question is legitimate enough and it is quite normal to expect source code control as an integrated feature in IDEs (VS has it), and one should therefore expect people to ask for it in C::B, even if the proper answer might be to encourage a different expectation. I would recommend not answering if replies like this is all you have. I don't see the point of rude answers like this.
0 Comments
Leave a Reply. |