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

wxSmith - how it should look ?

<< < (2/2)

geijt:

--- Quote from: rickg22 on October 28, 2005, 08:41:18 pm ---Thanks for the info! I had forgotten how good it was to use Delphi (except *ugh* having to scroll for the tabs... eew)

--- End quote ---
I don't have to scroll for the tabs! (look at my previous post)
There's a great plug-in/add-on for that bug. (the way i see it)

lesnewell:
Just had a quick play with wxSmith and it looks good to me. I have a couple of questions. How do you add a new control? From the looks of it I need to:

create wxsmycontrol.cpp and .h
Add wxsMyControlId to wxsstdmanager.h
Add wxMyControl.png to the smithicons folder
Possibly add a wxsmyproperty.cpp and.h if needed
cross fingers
compile

Is that it?

Presumably everything between the //( *and //*) tags in the source must be strictly left alone  ;-)

Is there any chance of adding a
#ifndef WX_PRECOMP
#endif
guard block around the headers to speed up compilation when using PCHs. I know it is a matter of seconds to add it manually but I am a lazy sob :P

wx-DevCPP has a useful extra property called 'Base class'. Basically it just changes the widget's class name. This allows you to use a derived class without creating a new custom control. Is there any chance of implementing something similar?

Oh yeah, don't preview a borderless frame - you can't close it...

byo:

--- Quote from: lesnewell on November 04, 2005, 04:32:18 pm ---create wxsmycontrol.cpp and .h
Add wxsMyControlId to wxsstdmanager.h
Add wxMyControl.png to the smithicons folder
Possibly add a wxsmyproperty.cpp and.h if needed
cross fingers
compile

Is that it?

--- End quote ---

It's almost everything, wxsstdwidgetmanager.cpp need to be prepared for new widget also - need to add new entry to StdInfos array and add one case line into wxsStdManagerT::ProduceWidget. I've also been thinking about pluggable architecture, but this after first really stable and complete release ;)


--- Quote ---Presumably everything between the //( *and //*) tags in the source must be strictly left alone  ;-)

--- End quote ---

Code between those comments is generated automatically so if You change it You'll loose it :). Exception is //(*Handlers comment, wxSmith will only add new code here and basically parse what's inside.


--- Quote ---Is there any chance of adding a
#ifndef WX_PRECOMP
#endif

--- End quote ---
Shouldn't be a problem


--- Quote ---wx-DevCPP has a useful extra property called 'Base class'. Basically it just changes the widget's class name. This allows you to use a derived class without creating a new custom control. Is there any chance of implementing something similar?

--- End quote ---

Currently there's no such thing :( but I don't think it will be a big problem, but it may take some time before we fix all bugs and other things


--- Quote ---Oh yeah, don't preview a borderless frame - you can't close it...
--- End quote ---

Try Alt+F4 ;)

Thx for all comments :)

lesnewell:

--- Quote from: byo on November 04, 2005, 05:15:52 pm --- I've also been thinking about pluggable architecture, but this after first really stable and complete release ;)

--- End quote ---

A pluggable architecture would be very nice indeed :-)


--- Quote ---Try Alt+F4 ;)
--- End quote ---

Doh! :oops:

I am very impressed so far. Thanks for all of your hard work.

byo:

--- Quote from: lesnewell on November 04, 2005, 07:17:41 pm ---A pluggable architecture would be very nice indeed :-)

--- End quote ---

One of my basic assumptions :) There's even code prepared especially for this :D

Navigation

[0] Message Index

[*] Previous page