Author Topic: wxSmith - Help with C::B plugin  (Read 4837 times)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9595
wxSmith - Help with C::B plugin
« on: November 30, 2005, 08:20:58 pm »
Dear wxSmith devs,

I have started using wxSmith and I really, really like it. Very nice work!

I read the tutorial you provided which was really helpful to develop my first-ever wxWidget application. Thanks to wxSmith it worked from scratch. Now I have a question: I want to implement a C::B plugin and tried to find a way to use the built-in C::B plugin wizard and wxSmith. I was able to manage (somehow) but I am pretty sure that there is a better way. Therefore my question:
(If you have the time...)
Could you extend the tutorial to include a step-by-step instruction how to use/enable wxSmith for C::B plugins? I guess all C::B plugin developers would also LOVE (:D) if you could extend/provide a plugin wizard plugin... but that's maybe not even required.

Any help is really appreciated. How do you think?

With best regards,

Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline byo

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 837
Re: wxSmith - Help with C::B plugin
« Reply #1 on: November 30, 2005, 11:58:28 pm »
Ok, the way I use wxSmith in plugins is:

* Create C::B plugin using wizzard
* Add Dialog from wxSmith menu

It will ask to use wxSmith and add dialog. And voila - You have wxSmith-managed dialog in Your pluggin ;)

But If You thought about more deetailed tutorial (f.ex describing how to deal with dialog data) I can add new tutorial but need some time for this :)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9595
Re: wxSmith - Help with C::B plugin
« Reply #2 on: December 01, 2005, 08:30:13 am »
Ok, the way I use wxSmith in plugins is: [...]
Ok, I guess it was my fault. I was a little curious about how to do. I created a new plugin using the plugin wizard and then used "Configure wxSmith for current projects" from the wxSmith menu. wxSmith complained that I should add "//(*AppHeaders ..." and stuff into my project - what I did. But there was never something filled in but (of course) in the new wxSmith managed dialog that I had created (also :)). So I was not sure whether that's right or wrong what I'm doing. No I know that I don't need this step everything becomes clear... :lol:

Thank you very much for the help anyway. However, if you have the time at some point... as you said: I believe it would still be helpful to write a tutorial. I guess for beginners it would be interesting to see a way to pipe the settings/messages from the wxSmith managed dialog to the plugin methods.

Morten.
« Last Edit: December 01, 2005, 08:32:00 am by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9595
Re: wxSmith - Help with C::B plugin
« Reply #3 on: December 01, 2005, 08:57:13 pm »
Dear byo,

I've just downloaded and "inspected" your (besides: cool!) lib_finder plugin. This is really of help if one tries to develop plugins with wxSmith. All you need is an example... isn't it?! ;-)

Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline byo

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 837
Re: wxSmith - Help with C::B plugin
« Reply #4 on: December 01, 2005, 10:25:24 pm »
Ok, I guess it was my fault. I was a little curious about how to do. I created a new plugin using the plugin wizard and then used "Configure wxSmith for current projects" from the wxSmith menu. wxSmith complained that I should add "//(*AppHeaders ..." and stuff into my project - what I did.

Hmm, I should change this message box :)
Configure wxSmith for current projects - this option will be usefull when creating wxSmith project from tempate (it's on the way :) ). But I forgot about projects without wxApp class - like C::B plugins ant here such message may be little bit confusing  :oops:

And C::B plugin using wxSmith - tutorial will be available soon :) I don't know exackly when but for me it's just few minutes to write it ant for You maybe few hours multiplied by number of devs trying to write plugin... may be a big number :D