Code::Blocks

User forums => Announcements => Topic started by: mandrav on August 06, 2006, 11:39:26 am

Title: About wxSmith development
Post by: mandrav on August 06, 2006, 11:39:26 am
Byo (for those of you who don't know him, he 's the wxSmith author) will be stopping development on the old wxSmith code. He will focus instead on the new wxSmith he 's been preparing.

What this means is that we won't see wxSmith updates for a while, until the new wxSmith code gets stable.

According to byo (but my own experience with wxSmith too), wxSmith for windows is in a stable state. Meaning there are some bugs, but it's mostly stable for working with.
The linux version is not stable. It can crash out of nowhere and has known bugs.

So, instead of working on old code (that's hard to maintain), byo will be working on the new code which, according to him, is a pleasure to work with.

Please be patient for the time needed until the new wxSmith is released.

For the Code::Blocks Team,
Yiannis.
Title: Re: About wxSmith development
Post by: L_O_J on August 08, 2006, 12:10:30 pm
Yay, hopefully the new wxSmith will be better (something like DialogBlocks maybe  :D, J/K)
Title: Re: About wxSmith development
Post by: Bonanza on August 13, 2006, 09:17:33 pm
Hi folks,

I have a small question about new and old wxSmith. I have already looked around this forum for an answer, but maybe it is easier to ask here.

Which of the two wxSmiths are in the nightly build?

When was/will the switch to new wxSmith be made?

TIA
Title: Re: About wxSmith development
Post by: killerbot on August 13, 2006, 09:49:10 pm
the old one is in the nightly build.
Title: Re: About wxSmith development
Post by: Bonanza on August 13, 2006, 10:16:08 pm
So I need to compile Code:Blocks myself for trying out the new wxSmith?
Title: Re: About wxSmith development
Post by: killerbot on August 13, 2006, 10:19:28 pm
that's right. The moment byo feels like it's getting stable enough we'll put it in the nightlies.
Title: Re: About wxSmith development
Post by: Bonanza on August 13, 2006, 10:21:01 pm
Thanks:-)
Title: Re: About wxSmith development
Post by: byo on August 27, 2006, 11:51:40 pm
I've been unavailable for few weeks (something really not related to computers ;)), it's nice to see C::B community again :D
I hope you will forgive all unanswered messages and all problems with wxSmith during my absence. And I hope you will understand my decision to develop new version only. Old version may be really unstable since I've fixed some bugs in rush without deeper investigation (it may be even better to revert to some ealier revision). But it's currently the only choice for developers using wxSmith, new ver. isn't good enough yet.

I'll try to get back to work as fast as possible 8) but since I've finished studies I won't have as much time as before :(. And there's lot of work to do, especially when dealing with incompatibilities between different platforms (just try to paint over widget or group of widgets, it's really a nightmare, if it works on win, it doesn't on linux and if it works on linux it doesn't on win...  :|  I don't want to try Mac ;) ). Huh, maybe I should stop talking (typing) ans focus on things which need to be done ;) Hello world again :D
Title: Re: About wxSmith development
Post by: Michael on August 29, 2006, 07:38:42 pm
Byo (for those of you who don't know him, he 's the wxSmith author) will be stopping development on the old wxSmith code. He will focus instead on the new wxSmith he 's been preparing.

Hello,

IMHO this is a good choice :). Therfore, Byo can concentrate all his resources on the new wxSmith instead of sharing them between the old and the new one.

Best wishes,
Michael
Title: Re: About wxSmith development
Post by: GuZ4217 on September 18, 2006, 10:27:16 pm
Quote
And there's lot of work to do, especially when dealing with incompatibilities between different platforms (just try to paint over widget or group of widgets, it's really a nightmare, if it works on win, it doesn't on linux and if it works on linux it doesn't on win...  Neutral  I don't want to try Mac Wink)

I just started using Code::Blocks and wxsmith in a new project and both work fine and smooth under windows. Now I just read this little centense and am a littlebit frightened :shock:. As i don't like to fall into panic i just want to ask:
This means wxsmith Project generated files should not be crossed over Platforms, right?

I just ask before i do more work under windows and suddenly notice that I fall into that little nightmare :evil:

PS.: great IDE and tool anyway      8)
Title: Re: About wxSmith development
Post by: takeshi miya on September 18, 2006, 11:37:54 pm
This means wxsmith Project generated files should not be crossed over Platforms, right?
No, that means that the old wxSmith linux version is extremely unstable, but if you don't touch anything you'll probably can compile successfully.  :)
I also hope that code generated by old wxSmith will work ok in the new version.
Title: Re: About wxSmith development
Post by: GuZ4217 on September 19, 2006, 12:08:34 am
Thanks, thats a relief ... somehow :?

So I will continue GUI-ing under windows and port after completition of that part.
Title: Re: About wxSmith development
Post by: Bonanza on October 21, 2006, 09:20:48 pm
I tried to build the "new wxsmith" myself. I am using the \src\plugins\contrib\wxSmith\new\wxsmith.cbp project.

I got an error:
Code: DOS
  1. :: === wxSmith, wxSmith ===
  2. wxsmith.h:104: error: expected constructor, destructor, or type conversion before ';' token
  3. :: === Build finished: 1 errors, 0 warnings ===

wxsmith.h contains following (macro i guess) at line 104:
CB_DECLARE_PLUGIN();

I tried to scan source files of codeblocks but could not find this identifier.

I am using revision 3116.

Does anyone know why this error occur?
Am I using the right project to build "new wxsmith"?
Can anyone point me to a revision that builds without error?

I know I am supposed to let wxsmith developers work undisturbed but I would very much like to build this or at least to try it.

Thanks in advance.
Title: Re: About wxSmith development
Post by: MortenMacFly on October 21, 2006, 10:52:02 pm
I tried to build the "new wxsmith" myself. I am using the \src\plugins\contrib\wxSmith\new\wxsmith.cbp project.
This version is out-dated. A branch has been created for the new wxSmith making this folder deprecated. Point your favorite Subversion client appropriate. This old "new" wxSmith uses the old plugin interface which is not compatible with the new (revamped) one from the (SVN) SDK.
With regards, Morten.
Title: Re: About wxSmith development
Post by: MortenMacFly on October 21, 2006, 10:52:34 pm
I tried to build the "new wxsmith" myself. I am using the \src\plugins\contrib\wxSmith\new\wxsmith.cbp project.
This version is out-dated. A branch has been created for the new wxSmith making this folder deprecated. Point your favorite Subversion client appropriate. This old "new" wxSmith uses the old plugin interface which is not compatible with the new (revamped) one from the C::B (SVN) SDK.
With regards, Morten.
Title: Re: About wxSmith development
Post by: Bonanza on October 21, 2006, 11:50:59 pm
Hi Morten,

Thanks for the answer. Sadly I am a novice to SVN (some experience in CVS) and I have no clue how to do the suggested operation. Where do I find the mentioned branch? Does it apply for a certain set of files and folders?

I am using TortoiseSVN....

Could you please give me a hint or two?
TIA
Title: Re: About wxSmith development
Post by: MortenMacFly on October 22, 2006, 10:17:27 am
Could you please give me a hint or two?
If you have checked out the sources from trunk (you did, right?!) then you have to go to one level beneath that. There is a directory called "branches". This you have to setup to access a branch you like. You can browse the repository at http://svn.berlios.de/wsvn/codeblocks (http://svn.berlios.de/wsvn/codeblocks) to make you a picture of that. So basically where you now have setup "svn.berlios.de/svnroot/repos/codeblocks/trunk" in your SVN client you point now to "svn.berlios.de/svnroot/repos/codeblocks/branches/New_wxSmith" and that's it. All other instructions how to obtain the C::B sources from SVN remain (see http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows (http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows)).
With regards, Morten.
Title: Re: About wxSmith development
Post by: bnilsson on October 22, 2006, 12:12:22 pm
Hi!

What would be the prospects of trying New_wxSmith on Mac?
I have no problems building the standard CB using svn update, (a modified) bootstrap, configure and make.

I did svn checkout on New_wxSmith but there were no makefiles and I am unable to set up a working wxSmith.cbp.
If the wxSmith.cbp is the preferred choice, I would need some help there.

Title: Re: About wxSmith development
Post by: byo on October 23, 2006, 03:16:29 pm
Hmm, new wxSmith won't actually work. I'm recoding some basic classes and almost all wxSmith functionality has been disabled :(.

EDIT:
files in New_wxSmith are outdated to there's no use using this project. I'll remove this soon. The easiest way to get new wxSmith compiling is to checkout
   svn.berlios.de/svnroot/repos/codeblocks/branches/New_wxSmith
into
   src/plugins/contrib
folder and compile that projet
Title: Re: About wxSmith development
Post by: Bonanza on October 26, 2006, 08:15:28 pm
Hi Guys,

I compiled the new wxsmith replaced the dll and zip file and it seems to work.

However the possibility to create a new wxsmith project seems to have dissapeared form the project wizrd.

Is this supposed to happen?

Thanks
Title: Re: About wxSmith development
Post by: byo on October 26, 2006, 10:01:32 pm
Hi Guys,

I compiled the new wxsmith replaced the dll and zip file and it seems to work.

However the possibility to create a new wxsmith project seems to have dissapeared form the project wizrd.

Is this supposed to happen?

Thanks

Yes, new wxSmith currently doesn't have it's own wizard. In order to create wxSmith app you could create standard wxWidgets app and choose "Configure current project" - this will search for available wxApp classes and adopt it for wxSmith.

But once again I must warn - new wxSmith is NOT USABLE yet. It doesn't event create editor for resources. I need some time to reorganize base classes responsible for really basic things :(
Title: Re: About wxSmith development
Post by: Bonanza on October 26, 2006, 10:37:19 pm
Thanks for all the help:-)
Title: Re: About wxSmith development
Post by: DC@DR on December 03, 2006, 04:09:01 pm
OK, so now is there any info about the progress of the new wxSmith? When can we expect it to be integrated into NBs and become usable? Thanks :-)
Title: Re: About wxSmith development
Post by: byo on December 04, 2006, 12:36:23 am
Ok, current status of new wxSmith (I've worked really hard on wxSmith last week to make it usable in any way :))

Currently working:
* New framework prepared for new resources and even GUIs
* Adopting wxWidgest projects created using wxWidgets wizard to work with wxSmith (it tries to modify code where wxApp is created) - wxSmith's wizad is no longer needed
* Create wxFrame / wxDialog / wxPanel (just like before)
* Editor almost done - you can add new items, edit them in property grid and use mouse to change size / placement of items
* Full source code creation - all required source code is generated, but I haven't tested resources using XRC files
* Undo / redo
* Cut / Copy / Paste (but not yet tested)
* Each item has priority - items palette is better organized now
* Can use dialog units in resources for size / position and few other properties (this wasn't supported in old wxSmith)

Not yet working (comparing to old wxSmith):
* resource browser is not fully supported (resources are shown, selecting resource opens editor but selecting item inside resource does not select it on editor)
* No Quick-Properties panels
* No importing of XRC files
* Preview button in editor does not work
* Can not edit events (this is almost done but not enabled in property grid)
* Not all items supported in old wxSmith version are supported (few items require some extra threatment - like wxNoteBoox needs system to swap currently edited page)
* Converting from old wxSmith format not yet done
* No MAC support
* Not tested on Linux
* Editor needs to be polished up - it tends to blink to much and sometimes it does not refresh correctly (but looks like it's more stable than previous versions)
* No automake files
* No linux project file

In my opinion, 80-90% of rewrite is done :)

Regards
   BYO
Title: Re: About wxSmith development
Post by: DC@DR on December 04, 2006, 06:41:04 pm
Sounds interesting, huh. We're all looking forward to see new wxSmith rolled out in good shape, thanks in advance for the great coming plug-in, Byo. Cheers :-)
Title: Re: About wxSmith development
Post by: afb on December 04, 2006, 08:06:02 pm
Not yet working (comparing to old wxSmith):
...
* No MAC support
* Not tested on Linux
* Editor needs to be polished up - it tends to blink to much and sometimes it does not refresh correctly (but looks like it's more stable than previous versions)
* No automake files
* No linux project file

In my opinion, 80-90% of rewrite is done :)

80% Windows, 10% Linux, 10% Mac OS X.

Sounds about fair :-)
Title: Re: About wxSmith development
Post by: stahta01 on December 04, 2006, 08:10:29 pm
80% Windows, 10% Linux, 10% Mac OS X.

Sounds about fair :-)


That adds up to 100%

Tim S
Title: Re: About wxSmith development
Post by: afb on December 04, 2006, 08:12:19 pm
80% Windows, 10% Linux, 10% Mac OS X.

Sounds about fair :-)


That adds up to 100%

Tim S

Did I miss any wx platform ?
Title: Re: About wxSmith development
Post by: byo on December 04, 2006, 09:12:43 pm
80% Windows, 10% Linux, 10% Mac OS X.

Sounds about fair :-)


I wish I could say that :roll: Has anybody some magic wand to make it true ;)
(Real estimations are not so optimistic so I won't bother you ;) )
Title: Re: About wxSmith development
Post by: afb on December 04, 2006, 10:21:54 pm
I was just kidding around. Checked out New_wxSmith (http://svn.berlios.de/wsvn/codeblocks/branches/New_wxSmith) to get a grip on where it's at (on wxGTK/wxMac), if I figure it out I'll let you know...
Title: Re: About wxSmith development
Post by: afb on December 04, 2006, 10:50:19 pm
Besides from a truckload of missing headers, it doesn't look all bad :-)

Maybe you can run it through once without the implicit/precomp headers,
in order to help add the missing <wx/string.h>,<wx/hashmap.h>,etc. ?
Title: Re: About wxSmith development
Post by: byo on December 05, 2006, 12:27:56 am
Besides from a truckload of missing headers, it doesn't look all bad :-)

Maybe you can run it through once without the implicit/precomp headers,
in order to help add the missing <wx/string.h>,<wx/hashmap.h>,etc. ?

:shock: missing headers, I don't like that kind of stuff - they always give me hadaches ;)

EDIT:
Ok, maybe some few better news: Resouce browser is done, preview almost done (just few bugs to fix and I'll commit this) - so the number of unimplemented features is smaller every day ;)
Title: Re: About wxSmith development
Post by: stahta01 on December 06, 2006, 12:06:37 pm
Byo:

Please see this thread http://forums.codeblocks.org/index.php?topic=4638.msg36627#msg36627
I am trying to submit a patch to update wxPropertyGrid to version 1.2.4 and the solution affects wxSmith plug-in.

Tim S
Title: Re: About wxSmith development
Post by: byo on December 06, 2006, 08:04:32 pm
I've updated (New) wxSmith to work without PCH. Can anybody check if it will work ? (It compiles on MingW 3.4.5 but few headers may be missing on other compilers - I've seen such beehaviour before)
Title: Re: About wxSmith development
Post by: stahta01 on December 07, 2006, 03:18:49 am
I keep getting errors on compiling the new wxSmith. Note, I am doing it with the new wxPropertyGrid version 1.2.x and with wxWidgets 2.8.0RC3/CVS. Can you verify that file wxsitemrestreedata.h should be used and is it in SVN?

Compiling: wxwidgets\wxsitem.cpp
wxwidgets\wxsitem.cpp:4:32: wxsitemrestreedata.h: No such file or directory
wxwidgets\wxsitem.cpp: In member function `void wxsItem::BuildItemTree(wxsResourceTree*, wxsResourceItemId, int)':
wxwidgets\wxsitem.cpp:164: error: `wxsItemResTreeData' has not been declared
wxwidgets\wxsitem.cpp:168: error: `wxsItemResTreeData' has not been declared
Process terminated with status 1 (2 minutes, 29 seconds)
3 errors, 3 warnings
Title: Re: About wxSmith development
Post by: byo on December 07, 2006, 12:55:35 pm
I keep getting errors on compiling the new wxSmith. Note, I am doing it with the new wxPropertyGrid version 1.2.x and with wxWidgets 2.8.0RC3/CVS. Can you verify that file wxsitemrestreedata.h should be used and is it in SVN?

Compiling: wxwidgets\wxsitem.cpp
wxwidgets\wxsitem.cpp:4:32: wxsitemrestreedata.h: No such file or directory
wxwidgets\wxsitem.cpp: In member function `void wxsItem::BuildItemTree(wxsResourceTree*, wxsResourceItemId, int)':
wxwidgets\wxsitem.cpp:164: error: `wxsItemResTreeData' has not been declared
wxwidgets\wxsitem.cpp:168: error: `wxsItemResTreeData' has not been declared
Process terminated with status 1 (2 minutes, 29 seconds)
3 errors, 3 warnings


My mistake  :oops: - files should be in repository now (rev. 3351). Thx for reporting that :)
Title: Re: About wxSmith development
Post by: stahta01 on December 07, 2006, 09:43:29 pm
Patch submitted to BerliOS to patch wxSmith (old) in prep of wxPropertyGrid update.
   https://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=1696&group_id=5358

Patch submitted to BerliOS to patch wxSmith (NEW) in prep of wxPropertyGrid update.
   [ Patch #1702 ] patch to the NEW wxSmith to use wxPropertyGrid version 1.2.x
   https://developer.berlios.de/patch/?func=detailpatch&patch_id=1702&group_id=5358

The above patches need testing, I don't know how to use wxSmith; so my testing was very very simple.
Reply with issues in this thread
    http://forums.codeblocks.org/index.php?topic=4638.0

Tim S
Title: Re: About wxSmith development
Post by: byo on December 11, 2006, 09:37:34 pm
I've added recently automake files allowing to compile new wxSmith on linux. Here's short guide:

* Checkout standard branch to some directory:
Code: [Select]
svn checkout http://svn.berlios.de/svnroot/repos/codeblocks/trunk* Checkout new wxsmith branch into contrib directory:
Code: [Select]
cd trunk/src/plugins/contrib
svn checkout http://svn.berlios.de/svnroot/repos/codeblocks/branches/New_wxSmith
* Apply patch included in this post switching to New_wxSmith:
Code: [Select]
patch -p0 < New_wxSmith.patch*Bootstrap, configure and compile
Code: [Select]
./bootstrap
mkdir build
cd build
../configure --enable-contrib --prefix=`pwd`/output
make
make install
cd output/bin
./codeblocks

Here's patch (couldn't find option to attach file :shock: so I paste it here):
Code: [Select]
Index: configure.in
===================================================================
--- configure.in (wersja 3362)
+++ configure.in (kopia robocza)
@@ -217,11 +217,12 @@
  src/plugins/contrib/symtab/Makefile
  src/plugins/contrib/symtab/resources/Makefile
  src/plugins/contrib/regex_testbed/Makefile
- src/plugins/contrib/wxSmith/Makefile
- src/plugins/contrib/wxSmith/defwidgets/Makefile
- src/plugins/contrib/wxSmith/properties/Makefile
- src/plugins/contrib/wxSmith/resources/Makefile
- src/plugins/contrib/wxSmith/smithicons/Makefile
+ src/plugins/contrib/New_wxSmith/Makefile
+ src/plugins/contrib/New_wxSmith/properties/Makefile
+ src/plugins/contrib/New_wxSmith/wxwidgets/Makefile
+ src/plugins/contrib/New_wxSmith/wxwidgets/properties/Makefile
+ src/plugins/contrib/New_wxSmith/wxwidgets/defwidgets/Makefile
+ src/plugins/contrib/New_wxSmith/wxwidgets/icons/Makefile
  src/scripts/Makefile
  src/tools/Makefile
  src/tools/cb_share_config/Makefile
Index: src/sdk/tinyxml/Makefile.am
===================================================================
--- src/sdk/tinyxml/Makefile.am (wersja 3362)
+++ src/sdk/tinyxml/Makefile.am (kopia robocza)
@@ -1,5 +1,6 @@
 INCLUDES = $(WX_CXXFLAGS) \
- -I$(top_srcdir)/src/sdk/wxscintilla/include
+ -I$(top_srcdir)/src/sdk/wxscintilla/include \
+ -I$(top_srcdir)/src/sdk
 
 sdkdir=$(includedir)/codeblocks/tinyxml
 
Index: src/plugins/contrib/Makefile.am
===================================================================
--- src/plugins/contrib/Makefile.am (wersja 3362)
+++ src/plugins/contrib/Makefile.am (kopia robocza)
@@ -1 +1 @@
-SUBDIRS = byogames cb_koders codesnippets codestat dragscroll envvars help_plugin keybinder lib_finder profiler source_exporter symtab regex_testbed wxSmith
+SUBDIRS = byogames cb_koders codesnippets codestat dragscroll envvars help_plugin keybinder lib_finder profiler source_exporter symtab regex_testbed New_wxSmith
Title: Re: About wxSmith development
Post by: DC@DR on December 14, 2006, 12:42:09 am
Today while surfing the net, I found this VisualWX (http://visualwx.altervista.org/), which is a RAD tool for building GUI, and its features are pretty impressive. I just wonder will we gonna have some kind of "form design" tool with new wxSmith? It's always nice to drag&drop "widgets" around a form and play with it :-).
Title: Re: About wxSmith development
Post by: SamT on December 14, 2006, 01:53:13 am
Today while surfing the net, I found this VisualWX (http://visualwx.altervista.org/), which is a RAD tool for building GUI, and

http://wiki.codeblocks.org/index.php?title=Comparison_of_wxSmith_features

I am using wxSmith because it's embedded in CB.  :)
Hope to have more progress with more function integrated or an open arch which could add component easily. Many people could contribute to enlarge the component base, just like wiki.
Title: Re: About wxSmith development
Post by: Grom on December 14, 2006, 02:56:29 am
I would say that GUI developer is priority number one. At first most of all people are watching at first on to a GUI developer and UML plugins. As second on to other stuff.  I do like Code::Blocks, because I am working with multi platform scientific problems.
But if Byo will not get help and strong support in his "heroes quest" - probably a lot of people will change the environment. I think in Code::Blocks development Byo's wxSmith project should have priority number one.
The VisualWx looks like cool stuff and have promising future. If that will be cross-platform free software - Code::Blocks will die :cry:.
As an idea - that will be grate to have a UML plugin in Code::Blocks  :idea:.
Title: Re: About wxSmith development
Post by: byo on December 14, 2006, 10:33:44 am
I just wonder will we gonna have some kind of "form design" tool with new wxSmith? It's always nice to drag&drop "widgets" around a form and play with it :-).

It currently support drag&drop even in old wxSmith (only one thing not using it is adding items into current form, but this will change soon).

I am using wxSmith because it's embedded in CB.  :)
Hope to have more progress with more function integrated or an open arch which could add component easily. Many people could contribute to enlarge the component base, just like wiki.

Yop, one of main goals of new framework is to provide easy support for user-defined widgets and other stuff (including new GUIs).

I would say that GUI developer is priority number one. At first most of all people are watching at first on to a GUI developer and UML plugins. As second on to other stuff.  I do like Code::Blocks, because I am working with multi platform scientific problems.
But if Byo will not get help and strong support in his "heroes quest" - probably a lot of people will change the environment. I think in Code::Blocks development Byo's wxSmith project should have priority number one.
The VisualWx looks like cool stuff and have promising future. If that will be cross-platform free software - Code::Blocks will die :cry:.
As an idea - that will be grate to have a UML plugin in Code::Blocks  :idea:.

Ok, first think - I don't think that C::B will day because even now many people use it without RAD designer - just because it has many other features developers like. And it looks like interest in C::B is growing (f.ex. new backend for Reactos' rbuild creating C::B projects was added recently).

But in fact I understand you may be little bit worried about future of wxSmith. Last few months i was working on code which already should be done (Yop, we're learning all the time, me too, I had to learn many things about design stage of a project :( and some lack of experience resulted in few really big bugs in project level )

Another thing is that I haven't seen cyberkoa for few months and I'm developing wxSmith alone (if I remember correctly, almost all 25k lines of code in new wxSmith i've written by myself).

But here are some good news: just in few days new wxSmith will have all major features of old wxSmith so switch to new one should be done soon. After that I'll start working on new features. And in short-term plan I'll try to write some docs / improove code to support user-defined widgets and hope that other people will help me increasing wxSmith's functionality :) Practise show one clear thing today: giving ability to add custom stuff for anybody and support from community is a big treasure for projects like wxSmith.

Regards
  BYO
Title: Re: About wxSmith development
Post by: joubertdj on December 14, 2006, 10:46:24 am
 :D Great job BYO...

Quote
And it looks like interest in C::B is growing

And if C::B grows... wxSmith will grow and receive contributions from other developers!

Good Luck
Title: Re: About wxSmith development
Post by: thomas on December 14, 2006, 10:57:02 am
If that will be cross-platform free software - Code::Blocks will die :cry:.
Well, that's a bit of a sinister view, considering they don't even have the same target user base as we do. :)
Neither DialogBlocks, wxDesigner, wxCpp, nor any of the many other RAD tools caused Code::Blocks to die until now :)

As of UML, many people I know (including myself) see it rather as a toy than a serious thing. Some even consider it a waste of development time. Maybe it's good for some academic purposes, I wouldn't know. Maybe it is used in certain circles, I would not know either.
Having said that, it may be daring to assume that most people will be looking for UML as the first thing.

I think most programmers will look for an IDE that works, an IDE that supports the compiler they use, and that takes care of the dirty things they don't like (as managing project files).
Title: Re: About wxSmith development
Post by: tiwag on December 14, 2006, 11:56:13 am
...As of UML, many people I know (including myself) see it rather as a toy than a serious thing. Some even consider it a waste of development time. Maybe it's good for some academic purposes, ...

mostly useful for students which have to document their homework using UML diagrams ...
Title: Re: About wxSmith development
Post by: Grom on December 14, 2006, 05:10:06 pm
We use UML for development planing. That is ok to start without diagram some small programming project. But, If you are developing back bone of a huge comput math project - you have to use UML. We can decide what we will do only after a serious discussions of a diagram of classes which should cover large set of problems. Specially in case if you start international project and you can't meet other side near the same blackboard.
UML inside codeblocks will bring a lot of people, include students who always want to do something and try them self on real projects.
Title: Re: About wxSmith development
Post by: MortenMacFly on December 14, 2006, 05:59:13 pm
UML inside codeblocks will bring a lot of people, include students who always want to do something and try them self on real projects.
Yes, but not if the UML diagrams cannot be sync'd in both directions. Otherwise one could use an external tool, as well -> sync'ing into the sources which compile with C::B.
With regards, Morten.
Title: Re: About wxSmith development
Post by: byo on December 14, 2006, 10:48:41 pm
... But, If you are developing back bone of a huge comput math project - you have to use UML....

Yup, agree. I was really against UML some time ago. I thought that only adventage of it was class diagram because it allowed me to create code skeleton faster than usual. But in big group of developers where everyone want to show his idea in his personal way, expecially if workign on some bigger project one unified language is necessary compromise. Even now I don't like few things in UML, but maybe because I've never worked on really huge project ;)

Ok, but back to the subject of this thread:

I've finished adopting ALL widgets from old wxSmith to new one. That means that all major goals of rewrite has been reached. New version still misses few functions but it's usable.

Now it's time for testing and bug-hunting
Title: Re: About wxSmith development
Post by: takeshi miya on December 15, 2006, 08:24:48 pm
New version still misses few functions but it's usable.

Now it's time for testing and bug-hunting
Great news :D
Title: Re: About wxSmith development
Post by: Christiaan on December 16, 2006, 04:15:47 pm
Great work  :D

Compiled it from SVN and it works better then the old wxSmith.

Opened a old wxSmith project and found a couple of small bugs.

Notebook->AddPagePanel1,_("My Page"),false);
There is a "(" missing between AddPage and Panel1

In file wxnotebook.cpp on line 261 changing:
Code << GetVarName() << _T("->AddPage")
to:
Code << GetVarName() << _T("->AddPage(")
seams to fix the problem

undefined reference to `MainFrame::ID_NOTEBOOK1'
The //(*IdInit(NewFrame) section is missing possible a conversion error.

After adding:
//(*IdInit(MainFrame)
//*)
to my mainframe.cpp the IdInit was generated and my project compiled without errors.
Title: Re: About wxSmith development
Post by: byo on December 16, 2006, 07:52:45 pm
Opened a old wxSmith project and found a couple of small bugs.

Notebook->AddPagePanel1,_("My Page"),false);
There is a "(" missing between AddPage and Panel1

In file wxnotebook.cpp on line 261 changing:
Code << GetVarName() << _T("->AddPage")
to:
Code << GetVarName() << _T("->AddPage(")
seams to fix the problem

Yop, you're right :) I haven't tested that code yet (same bug was in wxChoicebook and wxListbook).

Quote
undefined reference to `MainFrame::ID_NOTEBOOK1'
The //(*IdInit(NewFrame) section is missing possible a conversion error.

After adding:
//(*IdInit(MainFrame)
//*)
to my mainframe.cpp the IdInit was generated and my project compiled without errors.


I've already fixed that, in fact there's another section missing:

//(*InternalHeaders(MainFrame)
//*)

to make it working in all cases. wxSmith shuld do the conversion automatically :)

Thx for your report (I desperately need such reports right now ;) )

Regards
  BYO
Title: Re: About wxSmith development
Post by: nottin on January 14, 2007, 06:07:24 am
Getting this error when building new wxSmith:

 g++ -DHAVE_CONFIG_H -I. -I../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems -I../../../../../../src/sdk -I/usr/local/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread -I../../../../../../../src/sdk -I../../../../../../../src/sdk/wxFlatNotebook/include -I../../../../../../../src/sdk/wxscintilla/include -I../../../../../../../src/sdk/wxFlatNotebook -I../../../../../../../src/sdk/propgrid/include -O2 -ffast-math -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -MT wxsdatepickerctrl.lo -MD -MP -MF .deps/wxsdatepickerctrl.Tpo -c ../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./wxsdatepickerctrl.cpp  -fPIC -DPIC -o .libs/wxsdatepickerctrl.o
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h:114: error: 'wxArrayString' does not name a type
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h: In member function 'const wxString& wxsEvents::GetHandler(int)':
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h:80: error: 'm_Functions' was not declared in this scope
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h: In member function 'void wxsEvents::SetHandler(int, const wxString&)':
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h:83: error: 'm_Functions' was not declared in this scope
make[2]: *** [wxsdatepickerctrl.lo] Error 1
make[2]: Leaving directory `/home/bjorn/dev/apps/codeblocks/build/src/plugins/contrib/New_wxSmith/wxwidgets/defitems'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bjorn/dev/apps/codeblocks/build/src/plugins/contrib/New_wxSmith/wxwidgets'
make: *** [all-recursive] Error 1

using wxWidgets 2.8.1 on Ubuntu 6.10 (Edgy Eft)
Title: Re: About wxSmith development
Post by: stahta01 on January 14, 2007, 06:46:18 am
Getting this error when building new wxSmith:

 g++ -DHAVE_CONFIG_H -I. -I../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems -I../../../../../../src/sdk -I/usr/local/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread -I../../../../../../../src/sdk -I../../../../../../../src/sdk/wxFlatNotebook/include -I../../../../../../../src/sdk/wxscintilla/include -I../../../../../../../src/sdk/wxFlatNotebook -I../../../../../../../src/sdk/propgrid/include -O2 -ffast-math -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -MT wxsdatepickerctrl.lo -MD -MP -MF .deps/wxsdatepickerctrl.Tpo -c ../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./wxsdatepickerctrl.cpp  -fPIC -DPIC -o .libs/wxsdatepickerctrl.o
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h:114: error: 'wxArrayString' does not name a type
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h: In member function 'const wxString& wxsEvents::GetHandler(int)':
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h:80: error: 'm_Functions' was not declared in this scope
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h: In member function 'void wxsEvents::SetHandler(int, const wxString&)':
../../../../../../../src/plugins/contrib/New_wxSmith/wxwidgets/defitems/./../wxsevents.h:83: error: 'm_Functions' was not declared in this scope
make[2]: *** [wxsdatepickerctrl.lo] Error 1
make[2]: Leaving directory `/home/bjorn/dev/apps/codeblocks/build/src/plugins/contrib/New_wxSmith/wxwidgets/defitems'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bjorn/dev/apps/codeblocks/build/src/plugins/contrib/New_wxSmith/wxwidgets'
make: *** [all-recursive] Error 1

using wxWidgets 2.8.1 on Ubuntu 6.10 (Edgy Eft)

The patch for the new wxSmith is here; note, the OLD wxSmith is already patched.
  [ Patch #1766 ] NEW (experimental) wxSmith patch for wxWidgets 2.8 Submitted By: stahta01
   https://developer.berlios.de/patch/?func=detailpatch&patch_id=1766&group_id=5358
  How to get the new wxSmith is here
   http://forums.codeblocks.org/index.php?topic=3765.msg33855#msg33855

Have you applied my wxWidgets 2.8 patch?
See thread http://forums.codeblocks.org/index.php?topic=4495.0

Please post the link errors against wxWidgets 2.8 in my thread http://forums.codeblocks.org/index.php?topic=4495.0

Note: I have NOT tested my patch on the new wxSmith in the last two weeks if it has an compile or link error please post it in my thread and I will check it out. Note, I don't use wxSmith so don't ask me to do testing of it.

Tim S
Title: Re: About wxSmith development
Post by: byo on January 21, 2007, 12:04:21 am
New wxSmith has just been merged into trunk. It should be available with next nightly.
Remember to save project right after converting to new format :)
Unfortunately I've yet found two bugs during convertion from old format to new one. So please take this into consideration:
I'll probably fix these bugs on Monday so Sunday will have to be little "buggy" ;)

Here's short log what's in new wxSmith comparing to old one:

Source code for resources will be automatically regenerated when opening resource's editor for the first time (after conversion).

I hope you'd like this new "smithy" :)
Regards

   BYO
Title: Re: About wxSmith development
Post by: Grom on January 21, 2007, 02:46:15 am
Cool, thanks a lot!!!
When we will have statusbar, toolbar and menu? Is that new wxSmith expandable to add those components? If yes... This is not a problem :wink:
Title: Re: About wxSmith development
Post by: Michael on January 21, 2007, 09:45:05 pm
I hope you'd like this new "smithy" :)
Regards

   BYO

Great job Byo :D.

Best wishes,
Michael
Title: Re: About wxSmith development
Post by: byo on January 22, 2007, 12:26:32 am
Cool, thanks a lot!!!
When we will have statusbar, toolbar and menu? Is that new wxSmith expandable to add those components? If yes... This is not a problem :wink:

Sure, it should not be hard to add. I have got some generic idea on how to implement them already. The only thing that I'm worried about is that XRC standard doesn't support these extra things directly from frame/dialog. So there's possibility that it will be available only without XRC file (of course I'll add ability to edit it as separate resource :) )
Title: Re: About wxSmith development
Post by: byo on February 24, 2007, 11:22:34 pm
Ok, wxMenuBar, wxToolBar and wxStatusBar are now supported. wxToolBar class may still have some serious bugs, I haven't tested it very well but for simple tasks (like creating toolbar with few icons) it worked fine.

There are still few things in my (and probably yours) wishlist: most important one is to add any preview inside editor (currently new items can be edited by double-clicking on it's icon in tools list or through resource and property browser), second thing is to add images support into menus. Third one will be to create separate resources for items, but this may be delayed a little bit becuase of first two "wishes" and some other things planned.

In the meantime I've checked xrc sources better and they support loading wMenuBar, wxToolBar and wxStatus directly into frame without need of external resource so also xrc-based resources support them.

If someone is interested in what's really going on in wxSmith, I've made some small web page wxsmith.ovh.org (http://wxsmith.ovh.org) - this is only a scratch-pad I've written when I was sick of c++ and wanted to write something in some other language ;) Please do not consider it as a competition to forum, most things should go here, but I've thought that putting all that details into forum would be just messy.

Regards
  BYO