New Plugin: wxCrafter Integration with CodeBlocks

[eranif]

Anyone succeed in downloading the CB 13.12 plugin?

I am have issues; but, my internet is sometimes poor.

Tim S.

Thanks for reporting this, I have updated the link

Eran

[MortenMacFly]

Well I tried to compile this plugin but I failed miserably.

First f all there is no C::B project file... so I installed CodeLite and opened the workspace. But unfortunately it tells me it cannot find the reference to the clang compiler which would be wrong anyways - it should use MinGW as C::B is compiled using MinGW, too.

I am not that deep in CodeLite to know what to do. Do I need clang? My experience with clang on Windows is that its not working unless you are using Visual Studio. Can you provide some hints what to do on a Windows platform, please?

[MortenMacFly]

Well I tried to compile this plugin but I failed miserably.

OK - I managed to create a C::B project file myself. (If you are interested I can provide it to you).

However, the plugin is integrated, I can start the wizard to create a new project, I see the wxCrafter tab but then nothing happens. I cannot add any wx element (like wxFrame). There is also no error message - just nothing happens. I also don't see an option to setup a path to wxCrafter - I believe this might be needed?!

[eranif]

I also don't see an option to setup a path to wxCrafter - I believe this might be needed?!

Sorry for the long silence, been busy in the last few days...

the plugin should be reading the path to wxCrafter from registry, unless you don't have the new version (you will need the latest wxCrafter 1.5)

Code

        wxRegKey key(wxRegKey::HKLM, wxT("Software\\wxCrafter\\settings"));
        if ( !key.QueryValue(wxT("InstallPath"), wxcrafterPath) ) {
            // FIXME :: report an error
            return false;
            
        } else {
            wxFileName fnWxc(wxcrafterPath, wxT("wxcrafter.exe"));
            fnWxc.AppendDir(wxT("Standalone"));
            wxcrafterPath = fnWxc.GetFullPath();
        }

As you can see, I have left a "FIXME" there

Try downloading this one ( I assume that you are using Windows )
http://codelite.org/downloads/wxCrafter/wxCrafterDownloads.php?windows

FYI: The C::B plugin installer that I have uploaded in my earlier posts also includes wxCrafter standalone bundled

Eran

[MortenMacFly]

FYI: The C::B plugin installer that I have uploaded in my earlier posts also includes wxCrafter standalone bundled

OK, but I would like to use it for trunk, so this installer is of no help.

Additionally as I have all my S/W portable the registry entry is missing. I'll try what happens if I create it. On the long run it would be nice to have an option to set wxCrafter explicitly. :-)

[eranif]

On the long run it would be nice to have an option to set wxCrafter explicitly. :-)

Sure, I will add it

Eran

[eranif]

Done, I have added configuration settings dialog that allows you to set a different path to wxCrafter. The default value is set to /usr/bin/wxcrafter on Linux and to the value that exists in the registry for Windows.

Do:

Code

git pull --rebase

for the latest change

Thanks,
Eran

[MortenMacFly]

Code

git pull --rebase

for the latest change

Working with this plugin for some time I realised its also the root of an annoyance I was not able to track down until now:

If you have this plugin enabled, you'll get this error on C::B startup:
---------------------------
Codeblocks Error
---------------------------
Resource files must have same version number!
---------------------------

I was looking for a long time which XRC files cause the version mismatch but didn't find one. Now I did by accident: It seems that you integrate XRC files as ASCII stream in the sources of the plugin that must contain a version number. As these are not proper XRC files its well hidden from the developer (me).

Would you please either make these XRC files... well... XRC files or remove the version number? In C::B all XRC files share the same (version-free) header like:
<?xml version="1.0" encoding="utf-8" ?>
<resource xmlns="http://www.wxwidgets.org/wxxrc">
[...]


Also, I would like to state again that if this was a subversion repo (probably on sourceforge) it would be easy to integrate into C::B trough an SVN external. Having this plugin on GIT and the need to self-compile it makes it well hidden.

[Alpha]

Also, I would like to state again that if this was a subversion repo (probably on sourceforge) it would be easy to integrate into C::B trough an SVN external. Having this plugin on GIT and the need to self-compile it makes it well hidden.

Github states you can use subversion on their repositories as well.

[MortenMacFly]

Github states you can use subversion on their repositories as well.

Good catch! ...and it actually works!