You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(5) |
Apr
(7) |
May
(11) |
Jun
(19) |
Jul
(9) |
Aug
(5) |
Sep
(6) |
Oct
(18) |
Nov
(9) |
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(8) |
Feb
(1) |
Mar
(5) |
Apr
(1) |
May
(1) |
Jun
(73) |
Jul
(128) |
Aug
(39) |
Sep
(91) |
Oct
(24) |
Nov
(42) |
Dec
(37) |
2006 |
Jan
(8) |
Feb
(22) |
Mar
(15) |
Apr
(44) |
May
(13) |
Jun
(9) |
Jul
(19) |
Aug
(35) |
Sep
(28) |
Oct
(53) |
Nov
(19) |
Dec
(29) |
2007 |
Jan
(28) |
Feb
(37) |
Mar
(86) |
Apr
(14) |
May
(48) |
Jun
(2) |
Jul
(20) |
Aug
(19) |
Sep
(19) |
Oct
(8) |
Nov
(11) |
Dec
(11) |
2008 |
Jan
(3) |
Feb
(1) |
Mar
(22) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(16) |
Aug
(10) |
Sep
(5) |
Oct
(3) |
Nov
(24) |
Dec
(9) |
2009 |
Jan
(14) |
Feb
(4) |
Mar
(16) |
Apr
(13) |
May
(22) |
Jun
(3) |
Jul
(3) |
Aug
(8) |
Sep
(20) |
Oct
(18) |
Nov
(5) |
Dec
(11) |
2010 |
Jan
(4) |
Feb
(4) |
Mar
(7) |
Apr
(5) |
May
(41) |
Jun
(15) |
Jul
(3) |
Aug
(2) |
Sep
(9) |
Oct
(7) |
Nov
(8) |
Dec
(3) |
2011 |
Jan
(28) |
Feb
(29) |
Mar
(3) |
Apr
(7) |
May
(3) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
(4) |
Nov
(7) |
Dec
|
2012 |
Jan
(3) |
Feb
(4) |
Mar
(3) |
Apr
(3) |
May
(2) |
Jun
(2) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(3) |
Nov
|
Dec
(1) |
2013 |
Jan
|
Feb
|
Mar
(4) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(7) |
Dec
(5) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
|
2015 |
Jan
(7) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Francesco M. <fr...@us...> - 2007-08-02 23:46:02
|
name: RlLayout wxversion: 2.8,2.9,cvs category: window container,window layout language: cpp description: wxRecursiveLayout (or wxRL for short) is a generic window layout manager. It does not enforce a central 'document' area, but allows layouts with several main areas (panes, aka Eclipse). As such it can manage top-level windows/frames, child windows and also dialogs and panels. Support for window panes, toolbars, dragging parts, floating and docking, saving/loading layouts (aka perspectives). It uses wxSizers for the entire layout so it is quite flexible in terms of what layouts it permits. It also provides a light-weight class for drawing customized window/tool decorations and borders, allowing for sizer items to paint themselves and do simple messaging. location: RL cdate: 2007-07-29 id: 137 status: beta docs: hand buildsys: cmake,makefiles,projectfiles extdep: none wiki: disabled wxport: wxmsw,wxgtk samples: 2 approved: 0 author: Arne Steinarson version: 0.5 inCVS: 0 maintainerid: 56 Maintainer SF username: arst Maintainer name: Arne Steinarson Maintainer mail address: ast...@gm... |
From: Arne S. <ast...@gm...> - 2007-08-02 07:36:55
|
On 8/1/07, Francesco Montorsi <f18...@ya...> wrote: > > Hi, > > Arne Steinarson ha scritto: > > Thx for feedback. Of course I want to make it clear to visitors what the > > component is about. There is some new thinking in it, so its maybe not > > so easy to get the message straight through. > sure > > > >> name: RlLayout > > >a question: why the "rl" in front of the name? > > >It's not clear from description below what does it means... > > > > Rl stands for Recursive Layout, > ok but then I'd call it "wxRLayout" or "wxRecursiveLayout", not > "rllayout" as expanded it becomes "recursive layout layout"... (the 'wx' > prefix is not indispensable - choose what you prefer: use it or not use > it).... OK, I think we could settle for wxRL which expands to wxRecursiveLayout. I'll see if it means renamining some source files. > and describes the algorithmic approach, > > without using very specialized code to represent 'panes', 'captions', > > 'edges' > > and other layout components. It is more based on rules. > ok > > > >all other infos seems ok to me except maybe the central reason for > > >having such component: it would be nice to explicitely state what this > > >component would provide besides what is already provided by the > wxSizers > > >and wxAUI framework... > > > > Essentially, wxSizer & friends cannot paint themselves (and are > > invisible to > > the user). wxRlLayout let them draw themselves (and do some simple > > messaging) so they can represent edges, captions, buttons without the > > overhead of a wxWindow for each part. > > > > wxAui assumes a layout with a central document area and builds around > > that. It does not work so well for layouts that have two (or more) > parallel > > main areas (think of Eclipse IDE or old Norton Commander). > > > > RlLayout can also be used on dialogs or panels, so that elements can be > > visually moved, resized and dragged. Since dialogs in general don't have > > a central document area wxAui does not do such layouts. > > > > RlLayout solves a more general layout problem and can therefore be > > applied also in the dialog case. > > > > Does it make sense? > yes, it does! And seems very cool indeed! > > Now it's much clearer what it is and why it does not duplicate > wxSizer/wxAUI systems. I'll see if I can tweak the description a bit. Regards // ATS I'll setup the component as soon as we fix the name. > > Francesco > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users > |
From: Francesco M. <fr...@us...> - 2007-08-01 23:46:07
|
name: RlLayout wxversion: 2.8,2.9,cvs category: window container,window layout language: cpp description: wxRlLayout is a window layout manager for top-level windows, child windows, panels and dialogs. Support for window panes, toolbars, dragging panes & toolbars, floating and docking, saving/loading layouts (aka perspectives). It uses wxSizers for the entire layout so it is quite flexible in terms of what layouts it permits. It does not enforce a central 'document' area. It also provides a light-weight class for drawing customized window/tool decorations and borders. location: rllayout cdate: 2007-07-29 id: 137 status: beta docs: hand buildsys: cmake,makefiles,projectfiles extdep: none wiki: disabled wxport: wxmsw,wxgtk samples: 2 approved: 0 author: Arne Steinarson version: 0.5 inCVS: 0 maintainerid: 56 Maintainer SF username: arst Maintainer name: Arne Steinarson Maintainer mail address: ast...@gm... |
From: Francesco M. <f18...@ya...> - 2007-08-01 18:30:12
|
Hi, Arne Steinarson ha scritto: > Thx for feedback. Of course I want to make it clear to visitors what the > component is about. There is some new thinking in it, so its maybe not > so easy to get the message straight through. sure > >> name: RlLayout > >a question: why the "rl" in front of the name? > >It's not clear from description below what does it means... > > Rl stands for Recursive Layout, ok but then I'd call it "wxRLayout" or "wxRecursiveLayout", not "rllayout" as expanded it becomes "recursive layout layout"... (the 'wx' prefix is not indispensable - choose what you prefer: use it or not use it).... > and describes the algorithmic approach, > without using very specialized code to represent 'panes', 'captions', > 'edges' > and other layout components. It is more based on rules. ok > >all other infos seems ok to me except maybe the central reason for > >having such component: it would be nice to explicitely state what this > >component would provide besides what is already provided by the wxSizers > >and wxAUI framework... > > Essentially, wxSizer & friends cannot paint themselves (and are > invisible to > the user). wxRlLayout let them draw themselves (and do some simple > messaging) so they can represent edges, captions, buttons without the > overhead of a wxWindow for each part. > > wxAui assumes a layout with a central document area and builds around > that. It does not work so well for layouts that have two (or more) parallel > main areas (think of Eclipse IDE or old Norton Commander). > > RlLayout can also be used on dialogs or panels, so that elements can be > visually moved, resized and dragged. Since dialogs in general don't have > a central document area wxAui does not do such layouts. > > RlLayout solves a more general layout problem and can therefore be > applied also in the dialog case. > > Does it make sense? yes, it does! And seems very cool indeed! Now it's much clearer what it is and why it does not duplicate wxSizer/wxAUI systems. I'll setup the component as soon as we fix the name. Francesco |
From: Arne S. <ast...@gm...> - 2007-08-01 16:30:54
|
Hello, Thx for feedback. Of course I want to make it clear to visitors what the component is about. There is some new thinking in it, so its maybe not so easy to get the message straight through. >> name: RlLayout >a question: why the "rl" in front of the name? >It's not clear from description below what does it means... Rl stands for Recursive Layout, and describes the algorithmic approach, without using very specialized code to represent 'panes', 'captions', 'edges' and other layout components. It is more based on rules. >all other infos seems ok to me except maybe the central reason for >having such component: it would be nice to explicitely state what this >component would provide besides what is already provided by the wxSizers >and wxAUI framework... Essentially, wxSizer & friends cannot paint themselves (and are invisible to the user). wxRlLayout let them draw themselves (and do some simple messaging) so they can represent edges, captions, buttons without the overhead of a wxWindow for each part. wxAui assumes a layout with a central document area and builds around that. It does not work so well for layouts that have two (or more) parallel main areas (think of Eclipse IDE or old Norton Commander). RlLayout can also be used on dialogs or panels, so that elements can be visually moved, resized and dragged. Since dialogs in general don't have a central document area wxAui does not do such layouts. RlLayout solves a more general layout problem and can therefore be applied also in the dialog case. Does it make sense? Regards // ATS On 8/1/07, Francesco Montorsi <f18...@ya...> wrote: > > Hi Arne, > > Francesco Montorsi ha scritto: > > name: RlLayout > a question: why the "rl" in front of the name? > It's not clear from description below what does it means... > wxversion: 2.8,2.9,cvs > > category: window container,window layout > > language: cpp > > description: wxRlLayout is a window layout manager for top-level > windows, child windows, panels and dialogs. Support for window panes, > toolbars, dragging panes & toolbars, floating and docking, saving/loading > layouts (aka perspectives). It uses wxSizers for the entire layout so it is > quite flexible in terms of what layouts it permits. It does not enforce a > central 'document' area. It also provides a light-weight class for drawing > customized window/tool decorations and borders. > all other infos seems ok to me except maybe the central reason for > having such component: it would be nice to explicitely state what this > component would provide besides what is already provided by the wxSizers > and wxAUI framework... > > Francesco > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users > |
From: Francesco M. <f18...@ya...> - 2007-08-01 08:14:45
|
Hi, Jonas Rydberg ha scritto: > Francesco Montorsi wrote: >>> I am trying to build dmars makefiles for different wxcode components, but it >>> fails. >>> >> well, dmars is a "rarely-used" format. You're the first one asking about it... >> > Yes, I get that since I get these errors, but I thought that since the > main wx library builds ok with bakefile generated dmars makefiles, > wxcode components should "just work". not so easy :) > Maybe I've misunderstood something about bakefiles, but I thought that > the target logic (dmars, vs, bcc, etc) was the same for all projects > using bakefiles, and as long as a target (like dmars) was supported, > makefiles for any project should work. in very theory it should be so. In practice in bakefiles there are some points which needs to be "executed" only for some types of formats and not others. Thus testing the bakefiles & generated makefiles against a format is indispensable. > Guess I need to download bakefile sources and start debugging then. that's not a problem with bakefile itself, but rather with wxWidgets bakefile presets (in wxCode\build\bakefiles\presets\wx_*.bkl) and wxCode presets (in same folder). > Or > switch Win-compiler. My main dev platform is Debian and there it's no > problems, but my win machine is so slow, so the quick dmars compiler > seemed like a good choice. Tried mingw, but it took forever to build... I agree that mingw is the slowest compiler available on Win. It's hardly usable at all for me. I strongly suggest you to use free MSVC 8 compiler (M$ now gives away for free the "express edition") or the free Borland 5.5 compiler (probably the faster compiler I've ever used - but buggier than M$'s one). > >>> I get the following error when i run bakefile: >>> >>> [1/8] generating dmars from keybinder.bkl >>> D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx_win32.bkl:84: > error:output format does not support conditional processing ... > I think the first > error line is more important, since it signals a problem with output > format, ie problems with bakefile dmars support. ops, you're right! I didn't see it. Well, the error says pretty much everything: dmars MAKE is brain-dead and does not support "if" statements. Maybe dmars_smake is better? Francesco |
From: Francesco M. <f18...@ya...> - 2007-08-01 08:06:34
|
Hi Arne, Francesco Montorsi ha scritto: > name: RlLayout a question: why the "rl" in front of the name? It's not clear from description below what does it means... > wxversion: 2.8,2.9,cvs > category: window container,window layout > language: cpp > description: wxRlLayout is a window layout manager for top-level windows, child windows, panels and dialogs. Support for window panes, toolbars, dragging panes & toolbars, floating and docking, saving/loading layouts (aka perspectives). It uses wxSizers for the entire layout so it is quite flexible in terms of what layouts it permits. It does not enforce a central 'document' area. It also provides a light-weight class for drawing customized window/tool decorations and borders. all other infos seems ok to me except maybe the central reason for having such component: it would be nice to explicitely state what this component would provide besides what is already provided by the wxSizers and wxAUI framework... Francesco |
From: John L. <jla...@gm...> - 2007-08-01 03:15:17
|
On 7/31/07, Jeff Holle <jef...@be...> wrote: > This allowed me to a another problem. > Can't find wx_gtk2d_stc-2.8. > I assume that this is another dependability that this library has. > How do I get it? This is built from the wxWidgets/contrib/src/stc directory. The wxStyledTextCtrl class. I'm guessing that you're a little new to wxWidgets? In any case you may find this helpful. I like to create a directory in the wxWidgets root, wxWidgets/config_gtk2ud (for gtk2, unicode, debug) and run the script below (fix --prefix for your case and any other options) in the new directory. You should now have all the build files nicely partitioned off into this dir. Run make and then goto contrib/src/stc/ and run make again to get wx_gtk2d_stc-2.8. All you have to do now is put the --prefix into your path or better yet create a symbolic link to "wx-config" in your path. ../configure \ --prefix=/home/john/wx/wxWidgets/wxWidgets_28/wxWidgets/config_gtk2ud \ --enable-optimise=no \ --enable-debug=yes \ --enable-debug_gdb=yes \ --enable-mem_tracing=no \ --enable-profile=no \ --with-dmalloc=no \ --enable-prologio=no \ --enable-gtk2=yes \ --enable-unicode=yes \ --with-gnomeprint \ --enable-mediactrl=yes \ --with-opengl \ --enable-graphics_ctx Hope this helps, John Labenski > John Labenski wrote: > > On 7/31/07, Jeff Holle <jef...@be...> wrote: > > > >> I using an Ubuntu Linux system with gcc 4.12 > >> > >> I downloaded wxstedit-1.2.5.tar.gz, untar it, ran configure successfully. > >> However, when I run make I get: > >> stedefs.h:29:33: error: wx/stedit/setup.h: No such file or directory > >> in attempting to compile it. > >> > >> My wxWidgets version is wxGTK 2.8.4. Its at $HOME/wxGTK-2.8.4 and > >> installed. > >> > >> Any help would be appreciated! > >> > > > > Copy include/wx/stedit/setup0.h to setup.h. You can modify setup.h it > > to exclude various lexers. > > > > > |
From: Jeff H. <jef...@be...> - 2007-08-01 03:06:34
|
This allowed me to a another problem. Can't find wx_gtk2d_stc-2.8. I assume that this is another dependability that this library has. How do I get it? John Labenski wrote: > On 7/31/07, Jeff Holle <jef...@be...> wrote: > >> I using an Ubuntu Linux system with gcc 4.12 >> >> I downloaded wxstedit-1.2.5.tar.gz, untar it, ran configure successfully. >> However, when I run make I get: >> stedefs.h:29:33: error: wx/stedit/setup.h: No such file or directory >> in attempting to compile it. >> >> My wxWidgets version is wxGTK 2.8.4. Its at $HOME/wxGTK-2.8.4 and >> installed. >> >> Any help would be appreciated! >> > > Copy include/wx/stedit/setup0.h to setup.h. You can modify setup.h it > to exclude various lexers. > > |
From: John L. <jla...@gm...> - 2007-08-01 00:57:17
|
On 7/31/07, Jeff Holle <jef...@be...> wrote: > I using an Ubuntu Linux system with gcc 4.12 > > I downloaded wxstedit-1.2.5.tar.gz, untar it, ran configure successfully. > However, when I run make I get: > stedefs.h:29:33: error: wx/stedit/setup.h: No such file or directory > in attempting to compile it. > > My wxWidgets version is wxGTK 2.8.4. Its at $HOME/wxGTK-2.8.4 and > installed. > > Any help would be appreciated! Copy include/wx/stedit/setup0.h to setup.h. You can modify setup.h it to exclude various lexers. Regards, John Labenski |
From: Jeff H. <jef...@be...> - 2007-08-01 00:33:21
|
I using an Ubuntu Linux system with gcc 4.12 I downloaded wxstedit-1.2.5.tar.gz, untar it, ran configure successfully. However, when I run make I get: stedefs.h:29:33: error: wx/stedit/setup.h: No such file or directory in attempting to compile it. My wxWidgets version is wxGTK 2.8.4. Its at $HOME/wxGTK-2.8.4 and installed. Any help would be appreciated! |
From: Francesco M. <fr...@us...> - 2007-07-31 23:46:10
|
name: RlLayout wxversion: 2.8,2.9,cvs category: window container,window layout language: cpp description: wxRlLayout is a window layout manager for top-level windows, child windows, panels and dialogs. Support for window panes, toolbars, dragging panes & toolbars, floating and docking, saving/loading layouts (aka perspectives). It uses wxSizers for the entire layout so it is quite flexible in terms of what layouts it permits. It does not enforce a central 'document' area. It also provides a light-weight class for drawing customized window/tool decorations and borders. location: rllayout cdate: 2007-07-29 id: 137 status: beta docs: hand buildsys: cmake,makefiles,projectfiles extdep: none wiki: disabled wxport: wxmsw,wxgtk samples: 2 approved: 0 author: Arne Steinarson version: 0.5 inCVS: 0 maintainerid: 56 Maintainer SF username: arst Maintainer name: Arne Steinarson Maintainer mail address: ast...@gm... |
From: Francesco M. <fr...@us...> - 2007-07-30 23:46:35
|
name: RlLayout wxversion: 2.8,2.9,cvs category: window container,window layout language: cpp description: wxRlLayout is a window layout manager for top-level windows, child windows, panels and dialogs. Support for window panes, toolbars, dragging panes & toolbars, floating and docking, saving/loading layouts (aka perspectives). It uses wxSizers for the entire layout so it is quite flexible in terms of what layouts it permits. It does not enforce a central 'document' area. It also provides a light-weight class for drawing customized window/tool decorations and borders. location: rllayout cdate: 2007-07-29 id: 137 status: beta docs: hand buildsys: cmake,makefiles,projectfiles extdep: none wiki: disabled wxport: wxmsw,wxgtk samples: 2 approved: 0 author: Arne Steinarson version: 0.5 inCVS: 0 maintainerid: 56 Maintainer SF username: arst Maintainer name: Arne Steinarson Maintainer mail address: ast...@gm... |
From: Francesco M. <fr...@us...> - 2007-07-29 23:46:06
|
name: RlLayout wxversion: 2.8,2.9,cvs category: window container,window layout language: cpp description: wxRlLayout is a window layout manager for top-level windows, child windows, panels and dialogs. Support for window panes, toolbars, dragging panes & toolbars, floating and docking, saving/loading layouts (aka perspectives). It uses wxSizers for the entire layout so it is quite flexible in terms of what layouts it permits. It does not enforce a central 'document' area. It also provides a light-weight class for drawing customized window/tool decorations and borders. location: rllayout cdate: 2007-07-29 id: 137 status: beta docs: hand buildsys: cmake,makefiles,projectfiles extdep: none wiki: disabled wxport: wxmsw,wxgtk samples: 2 approved: 0 author: Arne Steinarson version: 0.5 inCVS: 0 maintainerid: 56 Maintainer SF username: arst Maintainer name: Arne Steinarson Maintainer mail address: ast...@gm... |
From: Jonas R. <jo...@ar...> - 2007-07-28 22:49:43
|
Francesco Montorsi wrote: >> I am trying to build dmars makefiles for different wxcode components, but it >> fails. >> > well, dmars is a "rarely-used" format. You're the first one asking about it... > Yes, I get that since I get these errors, but I thought that since the main wx library builds ok with bakefile generated dmars makefiles, wxcode components should "just work". Maybe I've misunderstood something about bakefiles, but I thought that the target logic (dmars, vs, bcc, etc) was the same for all projects using bakefiles, and as long as a target (like dmars) was supported, makefiles for any project should work. Guess I need to download bakefile sources and start debugging then. Or switch Win-compiler. My main dev platform is Debian and there it's no problems, but my win machine is so slow, so the quick dmars compiler seemed like a good choice. Tried mingw, but it took forever to build... >> I get the following error when i run bakefile: >> >> [1/8] generating dmars from keybinder.bkl >> D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx_win32.bkl:84: error:output format does not support conditional processing >> at D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx_win32.bkl:84 >> included from D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx.bkl:278 >> included from D:\Spara\Projekt\wxCode\build\bakefiles\presets\wxcode.bkl:15 >> included from D:\Spara\Projekt\wxCode\components\keybinder\build\keybinder.bkl:9 >> Traceback (most recent call last): >> File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 538, in ? >> run(sys.argv[1:]) >> File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 525, in run >> dryRun=options.dryRun) >> File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 363, in updateTargets >> _doUpdate(state, None, pretend=pretend) >> File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 332, in _doUpdate >> os.remove(tempDeps) >> OSError: [Errno 13] Permission denied: 'c:\\windows\\temp\\bakefilehobffi' >> > such error denied permissions suggests me that you're not logged in as the administrator of a windows system and that bakefile tries to create a temporary file in a folder which is not writable by your user. > > Try to login as admin and retry. > Since I am using Win ME this shouldn't be a problem. Also, there are other files generated from bakefile in that directory. I think the first error line is more important, since it signals a problem with output format, ie problems with bakefile dmars support. > However if you want to provide patches to e.g. wxCode\build\bakefiles\*bkl files to add dmars support, I would gadly accept them. I won't be able to add that myself however. > > Good luck! > Francesco > Thanks. I'll see if I can find out something, and then post any ideas here. /Jonas |
From: Francesco M. <f18...@ya...> - 2007-07-26 22:55:09
|
Hi, William H. Schultz ha scritto: > Hello, > > I'm looking at the wxWebUpdate documentation, but I'm having a hard time > finding what I'm looking for. Is it possible to use wxWebUpdate to find > out if an update is available without requiring the user to select a > menu item? That is, is there a library call that I can make that will > tell me whether there's an update available, well, effectively yours is a good request and I'd like to make it easier to be able to satisfy it. I'm out of free time currently but I'd gadly apply patches which work in that direction... > so that I can auto-launch > the wxWebUpdate program? I would like users to be notified when updates > are available. basically I suggest you to look at the sources of wxWebupdate (they should be fairly commented) and look at the relevant portions of webupdate[dlg].cpp; the code is there could be used/refactored to create a function exported then in the library and made easily accessible from extern programs. HTH, Francesco |
From: Francesco M. <f18...@ya...> - 2007-07-26 22:45:12
|
Hi, Jonas Rydberg ha scritto: > Hello > > I am trying to build dmars makefiles for different wxcode components, but it > fails. well, dmars is a "rarely-used" format. You're the first one asking about it... > I get the following error when i run bakefile: > > [1/8] generating dmars from keybinder.bkl > D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx_win32.bkl:84: > error: output format does not support conditional processing > at D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx_win32.bkl:84 > included from D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx.bkl:278 > included from D:\Spara\Projekt\wxCode\build\bakefiles\presets\wxcode.bkl:15 > included from D:\Spara\Projekt\wxCode\components\keybinder\build\keybinder.bkl:9 > Traceback (most recent call last): > File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 538, in ? > run(sys.argv[1:]) > File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 525, in run > dryRun=options.dryRun) > File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 363, in updateTargets > _doUpdate(state, None, pretend=pretend) > File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 332, in _doUpdate > os.remove(tempDeps) > OSError: [Errno 13] Permission denied: 'c:\\windows\\temp\\bakefilehobffi' such error denied permissions suggests me that you're not logged in as the administrator of a windows system and that bakefile tries to create a temporary file in a folder which is not writable by your user. Try to login as admin and retry. > I have the following setup: > Windows ME > wxWidgets-2.8.4 > bakefile 0.2.2 > > The wxWidgets library makefile.dmc was created with bakefile without problems. > > Has anyone seen this problem, or know where to look to try to fix it? not that I know of. I also believe the one you reported is probably only the first one of a long serie :( However if you want to provide patches to e.g. wxCode\build\bakefiles\*bkl files to add dmars support, I would gadly accept them. I won't be able to add that myself however. Good luck! Francesco |
From: William H. S. <whs...@ce...> - 2007-07-26 18:08:55
|
Hello, I'm looking at the wxWebUpdate documentation, but I'm having a hard time finding what I'm looking for. Is it possible to use wxWebUpdate to find out if an update is available without requiring the user to select a menu item? That is, is there a library call that I can make that will tell me whether there's an update available, so that I can auto-launch the wxWebUpdate program? I would like users to be notified when updates are available. Thanks. ------------------------------- Hank Schultz Cedrus Corporation http://www.cedrus.com/ |
From: William H. S. <whs...@ce...> - 2007-07-26 00:57:25
|
Hello, Sorry about not having a commit note on this revision. I was having difficulty doing the commit, so I tried a different method, and the notes didn't attach like I thought they would. I also tried modifying the notes after the commit, but that's failing too. Here's what it should have said: wxDNSSD: Added a call to wxServiceDiscoveryResult that bypesses a conversion from a UTF-8 char * to wxString and back again. ------------------------------- Hank Schultz Cedrus Corporation http://www.cedrus.com/ |
From: SourceForge.net <no...@so...> - 2007-07-21 12:13:01
|
Bugs item #1758052, was opened at 2007-07-21 14:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1758052&group_id=51305 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: CVS HEAD Status: Open Resolution: None Priority: 5 Private: No Submitted By: JC Francois (jeancf) Assigned to: Nobody/Anonymous (nobody) Summary: wxCURL: "multiple definition" error with static library Initial Comment: Hi, when trying to link my application with a static build of my libraries (wxMSW, wxSqlite3, wxCURL) using Code::Blocks + mingw I get the following error: c:\dev\wxMSW-2.8.4\lib\gcc_lib/libwxmsw28ud.a(monolib_log.o): In function `Z10wxLogDebugPKwz':C:/dev/wxMSW-2.8.4/build/msw/../../src/common/log.cpp:237: multiple definition of `wxLogDebug(wchar_t const*, ...)' C:\dev\wxCURL-SVN\lib\gcc_lib/libwxcode_msw28u_wxcurl.a(wxcurl_lib_base.o):base.cpp:(.text$_Z10wxLogDebugPKwz[wxLogDebug(wchar_t const*, ...)]+0x0): first defined here collect2: ld returned 1 exit status When doing the same thing using DLLs I get no error. What can it be? Thanks for your help, /~jc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1758052&group_id=51305 |
From: SourceForge.net <no...@so...> - 2007-07-21 09:08:55
|
Bugs item #1757962, was opened at 2007-07-21 11:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1757962&group_id=51305 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: CVS HEAD Status: Open Resolution: None Priority: 5 Private: No Submitted By: JC Francois (jeancf) Assigned to: Nobody/Anonymous (nobody) Summary: wxCURL: "multiple definition" error with static library Initial Comment: Hi, when trying to link my application with a static build of my libraries (wxMSW, wxSqlite3, wxCURL) using Code::Blocks + mingw I get the following error: c:\dev\wxMSW-2.8.4\lib\gcc_lib/libwxmsw28ud.a(monolib_log.o): In function `Z10wxLogDebugPKwz':C:/dev/wxMSW-2.8.4/build/msw/../../src/common/log.cpp:237: multiple definition of `wxLogDebug(wchar_t const*, ...)' C:\dev\wxCURL-SVN\lib\gcc_lib/libwxcode_msw28u_wxcurl.a(wxcurl_lib_base.o):base.cpp:(.text$_Z10wxLogDebugPKwz[wxLogDebug(wchar_t const*, ...)]+0x0): first defined here collect2: ld returned 1 exit status When doing the same thing using DLLs I get no error. What can it be? Thanks for your help, /~jc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1757962&group_id=51305 |
From: Jonas R. <jo...@ar...> - 2007-07-20 13:36:33
|
Hello I am trying to build dmars makefiles for different wxcode components, but it fails. I get the following error when i run bakefile: [1/8] generating dmars from keybinder.bkl D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx_win32.bkl:84: error: output format does not support conditional processing at D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx_win32.bkl:84 included from D:\Spara\Projekt\wxCode\build\bakefiles\presets\wx.bkl:278 included from D:\Spara\Projekt\wxCode\build\bakefiles\presets\wxcode.bkl:15 included from D:\Spara\Projekt\wxCode\components\keybinder\build\keybinder.bkl:9 Traceback (most recent call last): File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 538, in ? run(sys.argv[1:]) File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 525, in run dryRun=options.dryRun) File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 363, in updateTargets _doUpdate(state, None, pretend=pretend) File "C:\PROGRAM\BAKEFILE\SRC\BAKEFILE_GEN.py", line 332, in _doUpdate os.remove(tempDeps) OSError: [Errno 13] Permission denied: 'c:\\windows\\temp\\bakefilehobffi' Error executing the script! I have the following setup: Windows ME wxWidgets-2.8.4 bakefile 0.2.2 The wxWidgets library makefile.dmc was created with bakefile without problems. Has anyone seen this problem, or know where to look to try to fix it? Regards /Jonas |
From: SourceForge.net <no...@so...> - 2007-07-18 09:24:15
|
Patches item #1755979, was opened at 2007-07-18 11:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=462818&aid=1755979&group_id=51305 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: last released version Status: Open Resolution: None Priority: 5 Private: No Submitted By: laurent humbertclaude (chowette) Assigned to: Nobody/Anonymous (nobody) Summary: [wxchart] bakefile script update Initial Comment: This is the updated bakefile as stated in the following mail: http://www.mail-archive.com/wxc...@li.../msg00360.html Contains wxchart.bkl and Bakefile.bkgen files. note that you need to move the resource file from $(WXCODE)\wxchart\build\msw\wxchart.rc to $(WXCODE)\wxchart\samples\wxchart.rc This seems to be a more logical place to put the resource file, as it belongs to the .exe Laurent ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=462818&aid=1755979&group_id=51305 |
From: Francesco M. <fr...@us...> - 2007-07-16 04:31:58
|
[automated message for informative purposes]. >From an heuristic check it results that 7 components have no sources in the CVS/SVN; here follows the list of these components and the relative maintainers: kwxIndustrialIndicators, maintainer: Marco Cavallini wxAutoStartUp, maintainer: Priyank Bolia wxDom, maintainer: Dj Gilcrease wxAudio, maintainer: Ryan Norton wxCoolBar, maintainer: MartinSfromB wxZeroconf, maintainer: Ishan Arora wxWinService, maintainer: Jan Knepper The relative maintainers have already been notified by mail of this issue. Your friendly wxCode script. |
From: SourceForge.net <no...@so...> - 2007-07-10 23:15:41
|
Bugs item #1751548, was opened at 2007-07-10 16:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1751548&group_id=51305 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sander Berents (bezhe) Assigned to: Nobody/Anonymous (nobody) Summary: wxCurl: wxCurlDownloadDialog & wxCTDS_CAN_START Initial Comment: If a wxCurlDownloadDialog is being created without the wxCTDS_CAN_START flag the automatic download will fail because of void wxCurlTransferDialog::OnStart(wxCommandEvent &WXUNUSED(ev)) { wxASSERT(HasFlag(wxCTDS_CAN_START)); ... by removing this line, the download will succeed. This wxASSERT line should not be there, as can be seen in the way it can be called: wxCurlDialogReturnFlag wxCurlTransferDialog::RunModal() { m_pThread->GetCurlSession()->SetVerbose(m_bVerbose); if (!HasFlag(wxCTDS_CAN_START)) { wxCommandEvent fake; OnStart(fake); // start immediately } ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1751548&group_id=51305 |