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

CodePacks Plugin

(1/3) > >>

JGM:
Hi to all,

I was thinking of improving the devpacks plugin, actually implement a new one. The plugin would be cross plataform.

Example:

Listbox->Plataforms: Windows, Linux, Mac(may be)
and another listbox that display the version or distribution, For example if linux: Fedora,Suse,Ubuntu. If windows: Windows 95/98, windows2000/xp, vista. This information would be stored in a plataforms.xml file for download as the list of categories and packages available.

To help cross compiling the programmer, if on linux, will also have the ability to download windows packages to a special directory, same for windows

Another ability would be to select the packages by compiler, the user can select libraries that are compatible with his compiler.

The file format would be zip instead of gzip since it's available on wxWidgets (7-zip would be great, better compression algorithms).

The cbpack will be divided in 3 parts (may be more?), one for necessary includes (or just add this includes also with the other packs making only 2) and other 2 packs, one for dynamic libraries and other for static ones. So the user could browse between them. The documentation would be on a separate download with an option to be added to the help plug in list. There should be a configuration file since the plugin should be able to configure the current project with the library that the user desires, for example, needed defines.

Also develop a small php community where users can upload a cbpack. Since codeblocks is becoming more popular every day I think that users will be happy to contribute cbpacks. And maintain some packages that we thing that are of generic use, multiplataform and that every one could need, like tinyxml or wxWidgets. So instead of using devpaks.org create a codeblocks one.

The idea of adding linux as a supported plataform is dumb but what can I loose  :D just wanted to improve the ability of RAD on both plataforms as Java and .Net does :), where many other c++ IDE's fail. Many distributions like fedora and ubuntu bring software repositories with libraries and sources, but not categorized like dev packs does.

Maybe I have ommited other details that I would like to implement, but that's part of the fun :D.

So code blocks developers, I just want to know if this is a good idea to start working on, also suggestions are very welcome!

EnterTheNameHere:

--- Quote from: JGM on January 13, 2008, 12:07:17 am ---To help cross compiling the programmer, if on linux, will also have the ability to download windows packages to a special directory, same for windows

--- End quote ---

Or every platform could have it's own directory, for example "TestLib" directories [..]/TestLib/Win or Linux or Mac, and desired platform release could be downloaded to this directory.
( directory structure is only an example.. )


--- Quote from: JGM on January 13, 2008, 12:07:17 am ---The cbpack will be divided in 3 parts (may be more?), one for necessary includes [...]

--- End quote ---
You mean headers as includes or other required packages for successful compile of the lib inside the package?

JGM:

--- Quote from: EnterTheNameHere on January 13, 2008, 07:06:02 am ---You mean headers as includes or other required packages for successful compile of the lib inside the package?

--- End quote ---

Yep, the headers on a package and the static or dynamic files on another package.

EnterTheNameHere:
And another dumb question ahead(:
You mean a static or dynamic files as a binaries, or a source code? ( If You mean source code then Ithought that dynamic or static build is more dependent on the compiling options than different source codes. Or You mean distibuting headers and compiled files but then what about source code( also distribute with headers? ), and what about libs that doesn't distribute binaries, I'll have to compile them myself as a package creator? )

JGM:

--- Quote from: EnterTheNameHere on January 13, 2008, 06:18:49 pm ---And another dumb question ahead(:
You mean a static or dynamic files as a binaries, or a source code? ( If You mean source code then Ithought that dynamic or static build is more dependent on the compiling options than different source codes. Or You mean distibuting headers and compiled files but then what about source code( also distribute with headers? ), and what about libs that doesn't distribute binaries, I'll have to compile them myself as a package creator? )

--- End quote ---

Well Distribute only the headers (.h files), not source code (.cpp files). And yes the static and dynamic would be the binary files to link with the compiler, then only declarations (.h files)  are needed, with the neccesary configurations to add into the compiler options if applicable.

Navigation

[0] Message Index

[#] Next page