wxcode-users — Submission, Questions, Information

[wxCode-users] wxEMail compilation problems

[pao_drop <pao...@bl...>]

Thank you for your prompt answer

Unfortunately, the new makefile yields exactly the same result...

By the way, at first sight both makefiles look indentical...
but maybe I have missed some point?

And sorry for forgetting my name!

Paul

[wxCode-users] wxEMail compilation problems

[pao_drop <pao...@bl...>]

Hello!
I have downloaded wxEMail-1.0-Beta-2, and I have some difficulties 
compiling it.

I am working on a Windows 7 system, with mingw version gcc 4.7.1.
My version of wxWidget is 2.8.12.

I am compiling with the following command:

mingw32-make -f makefile.gcc WX_DIR=D:\wxW WX_UNICODE=1 WX_DEBUG=0 
WX_SHARED=1 WX_MONOLITHIC=0

Now, I am facing error in the wxPOP3 class. These errors ate linked to 
static initialisation. Here are the compilation messages:

STARTING ERROR MESSAGES
../src/pop3/wxpop3.cpp:28:1: warning: 'wxPOP3::wxPOP3(wxString, 
wxString, wxString, long unsigned int, wxPOP3::AuthenticationScheme_t, 
bool, wxPOP3::Listener*)' redeclared without dllimport attribute: 
previous dllimport ignored [-Wattributes]
In file included from ../src/pop3/wxpop3.cpp:24:0:
..\include/wx/pop3/wxpop3.h: In constructor 'wxPOP3::wxPOP3(wxString, 
wxString, wxString, long unsigned int, wxPOP3::AuthenticationScheme_t, 
bool, wxPOP3::Listener*)':
..\include/wx/pop3/wxpop3.h:589:12: warning: 'wxPOP3::in_init' will be 
initialized after [-Wreorder]
..\include/wx/pop3/wxpop3.h:562:12: warning: 'bool wxPOP3::ssl_enabled' 
[-Wreorder]
../src/pop3/wxpop3.cpp:28:1: warning: when initialized here [-Wreorder]
../src/pop3/wxpop3.cpp: At global scope:
../src/pop3/wxpop3.cpp:56:6: warning: 'void 
wxPOP3::ConfigureAuthenticationScheme(wxPOP3::AuthenticationScheme_t, 
const wxString&, const wxString&, bool)' redeclared without dllimport 
attribute: previous dllimport ignored [-Wattributes]
../src/pop3/wxpop3.cpp:67:6: warning: 'bool 
wxPOP3::OperationInProgress()' redeclared without dllimport attribute: 
previous dllimport ignored [-Wattributes]
../src/pop3/wxpop3.cpp:72:6: warning: 'bool 
wxPOP3::CheckConnection(wxPOP3::Listener*)' redeclared without dllimport 
attribute: previous dllimport ignored [-Wattributes]
../src/pop3/wxpop3.cpp:77:6: warning: 'bool 
wxPOP3::DownloadMessages(wxPOP3::Listener*)' redeclared without 
dllimport attribute: previous dllimport ignored [-Wattributes]
../src/pop3/wxpop3.cpp:82:6: warning: 'bool 
wxPOP3::PerformOperation(int, wxPOP3::Listener*)' redeclared without 
dllimport attribute after being referenced with dll linkage [enabled by 
default]
../src/pop3/wxpop3.cpp:109:40: warning: 'wxPOP3::initial_state' 
redeclared without dllimport attribute after being referenced with dll 
linkage [enabled by default]
../src/pop3/wxpop3.cpp:110:40: warning: 'wxPOP3::ssl_negociation_state' 
redeclared without dllimport attribute: previous dllimport ignored 
[-Wattributes]
../src/pop3/wxpop3.cpp:111:40: warning: 'wxPOP3::hello_state' redeclared 
without dllimport attribute: previous dllimport ignored [-Wattributes]
../src/pop3/wxpop3.cpp:112:40: warning: 'wxPOP3::authorisation_state' 
redeclared without dllimport attribute: previous dllimport ignored 
[-Wattributes]
../src/pop3/wxpop3.cpp:113:40: warning: 'wxPOP3::get_message_list_state' 
redeclared without dllimport attribute: previous dllimport ignored 
[-Wattributes]
../src/pop3/wxpop3.cpp:114:40: warning: 'wxPOP3::handling_message_state' 
redeclared without dllimport attribute: previous dllimport ignored 
[-Wattributes]
../src/pop3/wxpop3.cpp:115:40: warning: 
'wxPOP3::downloading_message_state' redeclared without dllimport 
attribute: previous dllimport ignored [-Wattributes]
../src/pop3/wxpop3.cpp:116:40: warning: 
'wxPOP3::suppressing_message_state' redeclared without dllimport 
attribute: previous dllimport ignored [-Wattributes]
../src/pop3/wxpop3.cpp:117:40: warning: 'wxPOP3::exit_state' redeclared 
without dllimport attribute after being referenced with dll linkage 
[enabled by default]
../src/pop3/wxpop3.cpp:121:40: warning: 'wxPOP3::default_class_listener' 
redeclared without dllimport attribute after being referenced with dll 
linkage [enabled by default]
../src/pop3/wxpop3.cpp: In function 'void __tcf_2()':
../src/pop3/wxpop3.cpp:110:32: error: definition of static data member 
'wxPOP3::ssl_negociation_state' of dllimport'd class
../src/pop3/wxpop3.cpp: In function 'void __tcf_3()':
../src/pop3/wxpop3.cpp:111:32: error: definition of static data member 
'wxPOP3::hello_state' of dllimport'd class
../src/pop3/wxpop3.cpp: In function 'void __tcf_4()':
../src/pop3/wxpop3.cpp:112:32: error: definition of static data member 
'wxPOP3::authorisation_state' of dllimport'd class
../src/pop3/wxpop3.cpp: In function 'void __tcf_5()':
../src/pop3/wxpop3.cpp:113:32: error: definition of static data member 
'wxPOP3::get_message_list_state' of dllimport'd class
../src/pop3/wxpop3.cpp: In function 'void __tcf_6()':
../src/pop3/wxpop3.cpp:114:32: error: definition of static data member 
'wxPOP3::handling_message_state' of dllimport'd class
../src/pop3/wxpop3.cpp: In function 'void __tcf_7()':
../src/pop3/wxpop3.cpp:115:32: error: definition of static data member 
'wxPOP3::downloading_message_state' of dllimport'd class
../src/pop3/wxpop3.cpp: In function 'void __tcf_8()':
../src/pop3/wxpop3.cpp:116:32: error: definition of static data member 
'wxPOP3::suppressing_message_state' of dllimport'd class
mingw32-make: *** [gccmswu\wxEMail_lib_wxpop3.o] Error 1
END OF ERROR MESSAGES

Note that I have tested the trick proposed in a post by evstevemd (Sun 
Feb 12, 2012 9:20 pm) on the wxWidgets discussion Forum,
to no avail
Also, commenting off the offensing lines allows compiling wxPOP3 
(presumably in an incorrect way),
but then the compiling stops in wxsmtp.cpp, once again on the static 
initialisation lines,
even if they are now modified according to evstevemd proposal.

So what could I try???

Re: [wxCode-users] wxSQLIte supports encryption?

[Ulrich T. <ulr...@gm...>]

Am 31.08.2013 20:12, schrieb dd:>    Does wxSQLite support database 
encryption on winrt platform?(for tablet)

The encryption extension coming with wxSQLite3 is implemented in plain C 
based on the SQLite3 amalgamation source code. Since SQLite3 itself 
works on WinRT, I don't see any reason why the wxSQLite3 encryption 
extension for SQLite3 shouldn't work on WinRT, too. However, you would 
have to compile it yourself for WinRT.

Regards,

Ulrich

[wxCode-users] wxSQLIte supports encryption?

[dd <dur...@gm...>]

Hi All,

  Does wxSQLite support database encryption on winrt platform?(for tablet)

Thanks,
dd

Re: [wxCode-users] Harmonize SVN repository

[Ulrich T. <ulr...@gm...>]

Am 27.03.2013 16:45, schrieb PGridDev:
> No worries. I switched to the new address for wxTreeListCtrl.
>
> There is however a problem with the wxCode website: several components (including the above) still point to the old SVN repository. Trying to rename the existing web sub-site and running 'maint_updatesite.sh' yields (although I can see that 'helper_updatecompwebsites.sh' was modified in December):

I removed all components' websites and checked them out again today. So 
this issue should be fixed by now.

> I also got asked for credential at the end of the script's execution:

This should be also fixed as I changed the script to use HTTP access 
instead of HTTPS.

> I then restored the previous sub-site and stopped my experimentations, don't want to screw up the entire site...

I hope the wxCode website is now back to normal.

Let me know if you still discover issues. Thanks.

Regards,

Ulrich

> On 25/03/2013 21:35, Ulrich Telle wrote:
>> Dear wxCode developers,
>>
>> mid of December 2012 I followed the SourceForge advise to upgrade the
>> wxCode project to the new SourceForge platform Allura.
>>
>> Unfortunately I misinterpreted the SourceForge information regarding the
>> wxCode Subversion repository. Now I discovered that there are now 2 SVN
>> repositories, an old one and a new one, and that there are several
>> discrepancies, because some wxCode developers still access the old
>> repository.
>>
>> Please update the address of the wxCode SVn repository to
>>
>> https://svn.code.sf.net/p/wxcode/code/trunk
>>
>> if you haven't done so yet and commit the changes previoulsy made in the
>> old repository in the new repository, too. Thanks.
>>
>> I'm really sorry for the inconveniences this may cause.
>>
>> Regards,
>>
>> Ulrich

Re: [wxCode-users] Harmonize SVN repository

[PGridDev <pgr...@ya...>]

Hi Ulrich

No worries. I switched to the new address for wxTreeListCtrl.

There is however a problem with the wxCode website: several components (including the above) still point to the old SVN repository. Trying to rename the existing web sub-site and running 'maint_updatesite.sh' yields (although I can see that 'helper_updatecompwebsites.sh' was modified in December):

#25: Updating wxTreeListCtrl (from Subversion)...
    ...ops: /home/project-web/wxcode/htdocs/components/treelistctrl does not exist - checking it out...
svn: OPTIONS of 'https://svn.code.sf.net/p/wxcode/code/trunk/wxCode/components/treelistctrl/website': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.code.sf.net)

I also got asked for credential at the end of the script's execution:

#91: Updating wxStringFormatter (from Subversion)...
    ...the component's website folder already exists - updating it...
Authentication realm: <https://svn.code.sf.net:443> SourceForge User
Password for 'pgriddev':

I then restored the previous sub-site and stopped my experimentations, don't want to screw up the entire site...

Cheers -Ronan


On 25/03/2013 21:35, Ulrich Telle wrote:
> Dear wxCode developers,
>
> mid of December 2012 I followed the SourceForge advise to upgrade the
> wxCode project to the new SourceForge platform Allura.
>
> Unfortunately I misinterpreted the SourceForge information regarding the
> wxCode Subversion repository. Now I discovered that there are now 2 SVN
> repositories, an old one and a new one, and that there are several
> discrepancies, because some wxCode developers still access the old
> repository.
>
> Please update the address of the wxCode SVn repository to
>
> https://svn.code.sf.net/p/wxcode/code/trunk
>
> if you haven't done so yet and commit the changes previoulsy made in the
> old repository in the new repository, too. Thanks.
>
> I'm really sorry for the inconveniences this may cause.
>
> Regards,
>
> Ulrich
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] Harmonize SVN repository

[Ulrich T. <ulr...@gm...>]

Am 26.03.2013 05:24, schrieb John Labenski:
> On Mon, Mar 25, 2013 at 4:35 PM, Ulrich Telle <ulr...@gm...> wrote:
>> Dear wxCode developers,
>>
>> mid of December 2012 I followed the SourceForge advise to upgrade the
>> wxCode project to the new SourceForge platform Allura.
>>
>> Unfortunately I misinterpreted the SourceForge information regarding the
>> wxCode Subversion repository. Now I discovered that there are now 2 SVN
>> repositories, an old one and a new one, and that there are several
>> discrepancies, because some wxCode developers still access the old
>> repository.
>>
>> Please update the address of the wxCode SVn repository to
>>
>> https://svn.code.sf.net/p/wxcode/code/trunk
>>
>> if you haven't done so yet and commit the changes previoulsy made in the
>> old repository in the new repository, too. Thanks.
>
> This is really bad. I have made quite a few commits since then. It
> sounds like the old one should be readonly already [1]. Please don't
> ask them to make it read-only, at least not for another day or two so
> I can be sure that everything is synced up.

I'm really sorry for this to happen. It will stay as it is for the next 
2 weeks as I'm out of office for this time and won't be able to do anything.

> The new on-line SVN browser is terrible too. There doesn't seem to be
> a way to see the revision commit diffs per file, just per whole
> revision, unless I missed it?

Well, if you browse to a revision and click on an affected file, the 
diffs are shown.

Regards,

Ulrich

Re: [wxCode-users] Harmonize SVN repository

[John L. <jla...@gm...>]

On Mon, Mar 25, 2013 at 4:35 PM, Ulrich Telle <ulr...@gm...> wrote:
> Dear wxCode developers,
>
> mid of December 2012 I followed the SourceForge advise to upgrade the
> wxCode project to the new SourceForge platform Allura.
>
> Unfortunately I misinterpreted the SourceForge information regarding the
> wxCode Subversion repository. Now I discovered that there are now 2 SVN
> repositories, an old one and a new one, and that there are several
> discrepancies, because some wxCode developers still access the old
> repository.
>
> Please update the address of the wxCode SVn repository to
>
> https://svn.code.sf.net/p/wxcode/code/trunk
>
> if you haven't done so yet and commit the changes previoulsy made in the
> old repository in the new repository, too. Thanks.

This is really bad. I have made quite a few commits since then. It
sounds like the old one should be readonly already [1]. Please don't
ask them to make it read-only, at least not for another day or two so
I can be sure that everything is synced up.

The new on-line SVN browser is terrible too. There doesn't seem to be
a way to see the revision commit diffs per file, just per whole
revision, unless I missed it?

Regards,
     John

[1] http://sourceforge.net/p/forge/community-docs/SVN%20and%20project%20upgrades/

[wxCode-users] Harmonize SVN repository

[Ulrich T. <ulr...@gm...>]

Dear wxCode developers,

mid of December 2012 I followed the SourceForge advise to upgrade the 
wxCode project to the new SourceForge platform Allura.

Unfortunately I misinterpreted the SourceForge information regarding the 
wxCode Subversion repository. Now I discovered that there are now 2 SVN 
repositories, an old one and a new one, and that there are several 
discrepancies, because some wxCode developers still access the old 
repository.

Please update the address of the wxCode SVn repository to

https://svn.code.sf.net/p/wxcode/code/trunk

if you haven't done so yet and commit the changes previoulsy made in the 
old repository in the new repository, too. Thanks.

I'm really sorry for the inconveniences this may cause.

Regards,

Ulrich

[wxCode-users] SourceForge upgrade for wxCode

[Ulrich T. <ulr...@gm...>]

Dear wxCode maintainers,

yesterday I received the below mail from the SourceForge staff.

I plan to initiate the SourceForge upgrade shortly after December 15, if 
no one objects.

At the moment I don't know whether and how the wxCode project and 
website will be affected by this upgrade.

I'll post further information here if wxCode maintainers have to take 
additional actions.

Regards,

Ulrich

==== Mail from SourceForge ====

Dear wxCode - wxWidgets components project admin,

Since your project has shown some activity in the last few months, we want
to be sure that you're aware that some changes are happening at
SourceForge, and we want to be sure you're not caught by surprise.

As you may already be aware, SourceForge is upgrading to a new platform
(code-named Allura), and as a result, we'll be retiring the Classic
SourceForge platform, which your project is still using. Our goal is to
have everybody off of the old platform in the first quarter of next year,
so that we can retire that code and focus our attention on the new
platform. It would, of course, be preferable if you migrate your own
project in your own time.

You can read more about the new platform at
https://sourceforge.net/p/upgrade/ and then, when you're ready, press the
Upgrade button next to your project name.

If you have any concerns about the process, or if your project has an
unusually large number of forums, source code repositories, or trackers,
please don't hesitate to contact us to discuss your upgrade. It's
important to us that it go smoothly.

As always, thanks for being part of the SourceForge community.

Rich Bowen
SourceForge Community Manager
rb...@so...

[wxCode-users] [ wxcode-Bugs-3578735 ] wxsqlite3.pc file needed

[SourceForge.net <no...@so...>]

Bugs item #3578735, was opened at 2012-10-20 09:23
Message generated for change (Tracker Item Submitted) made by martinkg63
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3578735&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: MartinKG (martinkg63)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxsqlite3.pc file needed

Initial Comment:

wxsqlite3 doesn't provide .pc file. It is good when ever -devel subpackage provides flags for gcc compiler.
https://fedoraproject.org/wiki/Packaging:Guidelines#Pkgconfig_Files_.28foo.pc.29

We are here to create a program package which compiles against wxSQLite3.

Could you please provide the attaches file in your next version ?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3578735&group_id=51305

[wxCode-users] [ wxcode-Bugs-3577941 ] wxsqlite3: assert identifier not found

[SourceForge.net <no...@so...>]

Bugs item #3577941, was opened at 2012-10-17 17:33
Message generated for change (Tracker Item Submitted) made by dustb
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3577941&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: Subversion TRUNK
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: DustinB (dustb)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxsqlite3: assert identifier not found

Initial Comment:
Minor problem, but, in the "wxSQLite3Transaction(...)" function there is a "assert(db != NULL);". When building the the library for wxWinCE it cannot find this function. I'm assuming wxWinCE doesn't explicitly bring in <assert.h> while wxMSW does when you innclude <wx/wx.h>. Solutions:

1> Include "#include <assert.h>" before the function.
or
2> Why not use wxASSERT(...) instead?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3577941&group_id=51305

[wxCode-users] [ wxcode-Bugs-3577572 ] rpmlint - spurious-executable-perm

[SourceForge.net <no...@so...>]

Bugs item #3577572, was opened at 2012-10-16 00:26
Message generated for change (Tracker Item Submitted) made by martinkg63
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3577572&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: MartinKG (martinkg63)
Assigned to: Nobody/Anonymous (nobody)
Summary: rpmlint - spurious-executable-perm

Initial Comment:
rpmlint reports on Fedora 18 the following warnings:

wxsqlite3.x86_64: W: spurious-executable-perm /usr/share/doc/wxsqlite3-3.0.0.1/LICENCE.txt
wxsqlite3.x86_64: W: spurious-executable-perm /usr/share/doc/wxsqlite3-3.0.0.1/Readme.txt

a workaround for me is at the moment to change the permisson with chmod
find -type f -exec chmod a-x {} \;

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3577572&group_id=51305

[wxCode-users] [ wxcode-Bugs-3571007 ] [wxTreeListCtrll] text search bugs

[SourceForge.net <no...@so...>]

Bugs item #3571007, was opened at 2012-09-23 06:43
Message generated for change (Tracker Item Submitted) made by pgriddev
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3571007&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: treelistctrl
Group: CVS HEAD
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ronan Chartois (pgriddev)
Assigned to: Ronan Chartois (pgriddev)
Summary: [wxTreeListCtrll] text search bugs

Initial Comment:
on behalf of Robert Majewski:

I started to use your widget (ver. 1208), and I think some lines are incorrect:

treelistctrl.cpp:3223  int col, col_start, col_end;
treelistctrl.cpp:3224  if (column >= 0) { col_start = col_end = col; }

"col" is uninitialized, so it shouldn't be used as initializer for "col_start" and "col_end".

treelistctrl.cpp:3993 m_findStr.Append ((const char *)event.GetKeyCode());

event.GetKeyCode() returns int, so it shouldn't be casted to (const char*), my program crashed in this line.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3571007&group_id=51305

[wxCode-users] [ wxcode-Bugs-3569395 ] cannot compile wxcurl-svn3061 on Fedora 17

[SourceForge.net <no...@so...>]

Bugs item #3569395, was opened at 2012-09-19 03:36
Message generated for change (Tracker Item Submitted) made by martinkg2
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3569395&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: MartinKG (martinkg2)
Assigned to: Nobody/Anonymous (nobody)
Summary: cannot compile wxcurl-svn3061 on Fedora 17

Initial Comment:
tried to compile wxcurl-svn3061.tar.bz2 on Fedora 17, but the make command fails:


./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for the --enable-debug option... will be automatically detected
checking for the --enable-unicode option... will be automatically detected
checking for the --enable-shared option... will be automatically detected
checking for the --with-toolkit option... will be automatically detected
checking for the --with-wxshared option... will be automatically detected
checking for the --with-wxversion option... will be automatically detected
checking for wx-config... /usr/bin/wx-config
checking for wxWidgets version >= 2.6.0... yes (version 2.8.12)
checking for wxWidgets static library... no
checking if wxWidgets was built with UNICODE enabled... yes
checking if wxWidgets was built in DEBUG mode... no
checking if wxWidgets was built in STATIC mode... no
checking which wxWidgets toolkit was selected... gtk2
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gawk... gawk
checking for curl-config... /usr/bin/curl-config
checking for the version of libcurl... 7.24.0
checking for libcurl >= version 7.15.0... yes
checking whether libcurl is usable... yes
checking for curl_free... yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether we are using the Intel C compiler... no
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking whether we are using the Intel C++ compiler... no
checking whether we are using the Sun C++ compiler... no
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... yes
checking for ar... ar
checking for strip... strip
checking for nm... nm
checking for command to install directories... /usr/bin/install -c -d
checking if make is GNU make... yes
checking for dependency tracking method... gcc
configure: creating ./config.status
config.status: creating Makefile

 ----------------------------------------------------------------
  Configuration for wxCurl 0.3 successfully completed.
  Summary of main configuration settings for wxCurl:
  - RELEASE build
  - UNICODE mode
  - SHARED mode

  The wxWidgets build which will be used by wxCurl 0.3
  has the following settings:
  - RELEASE build
  - UNICODE mode
  - SHARED mode
  - VERSION: 2.8.12
  - PORT: gtk2

  Now, just run make.
 ----------------------------------------------------------------

[martin@fc17-64 wxcurl]$ make
Makefile:181: *** missing separator.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3569395&group_id=51305

[wxCode-users] [ wxcode-Bugs-3558648 ] 1.2.1 on Windows

[SourceForge.net <no...@so...>]

Bugs item #3558648, was opened at 2012-08-16 17:35
Message generated for change (Tracker Item Submitted) made by dustb
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3558648&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: wxJSON
Group: last released version
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: DustinB (dustb)
Assigned to: Nobody/Anonymous (nobody)
Summary: 1.2.1 on Windows

Initial Comment:
### Using NMAKE ###
nmake -fmakefile.vc WX_DIR=H:\path-to-wx\wxMSW-2.8.12 WX_UNICODE=1 WX_DEBUG=0 WX_SHARED=0
..\src\jsonreader.cpp(1853) : error C2371: 'byte' : redefinition; different basic types
        C:\Program Files\Microsoft Visual Studio\VC98\include\rpcndr.h(172) : see declaration of 'byte'
NMAKE : fatal error U1077: 'cl' : return code '0x2'
Stop.

### Using wxjson_vc8.sln ###
error C2371: 'byte' : redefinition; different basic types


In rpcndr.h it is typedefing byte to 'unsigned char'. In jsonreader.cpp it is 'union byte { unsigned char c[2]; short int b; };'. I've also tried using wxWidgets 2.9.3, and it gives the same error (plus more), but, 2.8.12 is what I want to work with.

Thanks

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3558648&group_id=51305

[wxCode-users] wxTreeListCtrl: looking for a new maintainer

[PGridDev <pgr...@ya...>]

Dear wxCode community

I just published my last release of wxTreeListCtrl (version 1208); website:
http://wxcode.sourceforge.net/components/treelistctrl/

Soon Baby 1.0 will ship, and I'm afraid I will no longer have time to maintain another component. I think that wxTreeListCtrl is fairly mature, many hours (most not mine) were invested to bring it there. It would be a shame to leave it unmaintained, especially since the native wxWidgets 2.9 namesake does not yet offer the same functionality.

==> if you are interested in taking over maintenance of wxTreeListCtrl, please let me or the wxCode admins know.

Thanks and long live wxCode!
Ronan

[wxCode-users] Release of wxTreeListCtrl 1208

[PGridDev <pgr...@ya...>]

Hi all

A new version of the wxTreeListCtrl control is available for download, direct download link:
http://sourceforge.net/projects/wxcode/files/Components/treelistctrl/treelistctrl_1208.zip/download

A list of changes follows, the main one being: support for wxWidgets 2.9.
(note that this control is *not* the homonymous control available natively in wxWidgets)

Link to the control page on the wxCode website:
     http://wxcode.sourceforge.net/components/treelistctrl/

Happy coding!
Ronan


==================== ChangeLog begin ====================

* treelistctrl_1208.zip
   - Fixed: HitTest() was not working [#3093531 --thanks Yogesh]
   - Fixed: click events now return position (Point) in all cases
   - Fixed: include item in event EVT_COMMAND_TREE_ITEM_MENU [#3522228 --thanks T. Modes]
   - Fixed: take hidden columns into account for total width [#3522074 --thanks T. Modes]
   - Changed: by default FindItem() searches all columns (instead of main) [#3246444]
   - Added: resource files / XRC support [#3103099 --thanks Pascal Potvin]
   - Added: sample program now shows HitTest() output on middle-click
   - Added: can now change parent with SetItemParent(), sample demonstrates this with drag&drop [feature#3429784]
   - Added: support for wxWidgets 2.9 with separate 'wxCode' namespace

* treelistctrl_1104.zip
   - Fixed: position of editor when a column is hidden [wxPack]
   - Fixed: extra check to prevent painting of zero-width columns under GTK [#3061215]
   - Fixed: improved computing of BestSize, non-expanded controls in a sizer keep their initial size [#3061207]
   - Fixed: Edit control does not move with columns (stop editing on column move) [#2815443]
   - Changed: background color is applied to entire column width. Same for cursor and selection highlight excepted for main col [#2823804]
   - Added: make scroll events accessible to child class [#3082693]
   - Added: test program includes demonstrates capturing mouse events in child class (compile option WITH_CHILD_CLASS) [#3082693]
   - Added: SetCurrentItem() allows to set/reset the current item (cursor indicated by the black rectangle) [Remigius]
   - Added: EndEdit() to match EditLabel() [#2815443]
   - Added: multi-column support for various attribute (colors, font, ...) [#2823804 --thanks Chris Klecker]
   - Added: extented Sort() method [--thanks Chris Klecker]
   - Added: test program now has a 'Item' and 'Cell' menu to better play with attributes
   NOTE for DLL builders: some methods were removed or changed

* treelistctrl_2010-06.26.tar.gz
   - Fixed: improved support for GCC 4.x & compiling under Linux/GTK [#2858731]
   - Fixed: crash on start with GTK (call to SetBackgroundStyle)
   - Fixed: Unicode support [#2911015]
   - Fixed: spurious warning, unicode support with VC8.0 [#2962879]
   - Fixed: keep multiple selection when right-clicking on any selected (included last selected) item
   - Fixed: rectangle on non-current item after multiple unselection
   - Fixed: explicit conversions around size_t
   - Changed: made GetHeaderWindow() and GetMainWindow() protected (useless outside treelistctrl.cpp)
   - Changed: IsVisible now with 'within' option, and will only return true for fully visible items
   - Added: test program now reports selection content
   - Added: tooltip support, also for individual items [feature#2858734]
   - Added: support for page-up/page-down, improved 'end' key [feature#2989510]

* treelistctrl_2009-07-19.tar.gz
   - Fixed: GetPrev() not working at all [#2691182]
   - Changed: reduced flickering [feature #2460180]

* treelistctrl_2008-12-05.tar.gz
   - Fixed: non-compliant declarations in class wxTreeListMainWindow [#2051640]
   - Fixed: edit changes commited to wrong column [#2342061]
   - Fixed: crash after rename / cell edit [#2342054]
   - Fixed: crash on deletion of selected item (seen with multiple selection enabled on shutdown); bug introduced in v2008-07-21
   - Fixed: empty item text (in main & other columns)
   - Fixed: Drag from treelistctrl to another works improperly (drag origin not remembered accurately) [#1811335]
   - Fixed: allow multiple selection in right-click & dragging [#1488235]
   - Fixed: assertion in DoNotifyWindowAboutCaptureLost in wxMSW 2.7.1 [#1583135]
   - Changed: better positioning and size of editing cell

* treelistctrl_2008-07-21.tar.gz
   - Fixed: selection behavior
   - Fixed: make all mouse events accessible to child class [#2018407]
   - Fixed: column now always populated for mouse events [#2018407]
   - Fixed: crash on key navigation after item delete [#2021908]
   - Fixed: crash on edit after item delete [#2021908]
   - Fixed: missing event EVT_TREE_END_LABEL_EDIT when cancelled
   - Fixed: several crash possibilities when there is no root [#2021908]
   - Changed: changing the selection mode (wxTR_MULTIPLE style) will now reset the selection
   - Changed: id of main column is always returned in events (used to be -1 on blank area)
   - Changed: after an item is deleted, its next siblings is selected if it exists
   - Changed: key actions: if no item is selected, root is selected and no further action is taken
   - Changed: use same logic for double-click and return key (i.e. activate event will expand by default)
   - Added: events EVT_TREE_ITEM_MIDDLE_CLICK, EVT_TREE_ITEM_MENU
   - Added: events are also generated when empty area is clicked (with wxTreeEvent::IsOk() returning false) [#2018407]
   - Added: test program now with log window showing events fired
   - Added: test program includes compile option WITH_CHILD_CLASS demonstrating capturing mouse events in child class [#2018407]
   - Doc: added ommited (EVT_TREE_END_DRAG,EVT_TREE_ITEM_RIGHT_CLICK) and new events [#2018407]
   - Doc: mention wxTreeEvent::GetInt() to obtain column [#2018407]
   - Doc: corrected incorrect mention of no event on some delete actions

* treelistctrl_2008-06-18.tar.gz
   - Fixed: dead zone in labels with big fonts
   - Fixed: improved text/frame proportion in label row for big fonts (MSW)
   - Added: support for MinGW+MSYS through Makefile
   - Added: support for CodeBlock+GCC through project file

* treelistctrl_2006-06-21.tar.gz
   - first available release on sf.net

==================== ChangeLog end ====================

Re: [wxCode-users] github 'poll' request

[Bryan P. <br...@ib...>]

On Sun, Jul 1, 2012 at 10:59 PM, John Labenski <jla...@gm...> wrote:
> There is a "live" SVN -> Git translator and wxWidgets uses it. Perhaps
> this could work here as well?
>
> https://github.com/wxWidgets/wxWidgets

This is only really useful for advanced Git developers, who still are
required to make commits using SVN with the original repository, not
the one on GitHub. See the git-svn manpage for details on how to set
this up if you're interested though, anyone with SVN read access can
do it.

But it might also be interesting to note that GitHub actually has also
provided SVN support directly into repositories hosted on GitHub. This
works not only for checkout, but also for commits:
https://github.com/blog/1178-collaborating-on-github-with-subversion

Regards,
Bryan Petty

Re: [wxCode-users] github 'poll' request

[John L. <jla...@gm...>]

On Tue, Jun 19, 2012 at 10:14 AM, Ulrich Telle <ulr...@gm...> wrote:
> Hi Andrea,
>
>> I would like to have a new wxCode home on github (so to use Git instead
>> SVN as SCM system).

I don't know if I'm ready for Git yet, I'm just getting accustomed to
SVN after having dropped CVS, but see the bottom for a solution that
may perhaps work.

> As SourceForge put up several restrictions regarding project maintenance
> and administration which makes maintaining wxCode sometimes quite
> cumbersome and as a single SourceForge project is not very well suited
> for maintaining a big collection of only loosely coupled components I
> definitely support your experiment.

As perhaps the only active developer on it besides Ulrich, one of the
earliest adopters of wxCode, and an absentee administrator, I have to
say that it has not worked out as planned.

The real reason is not technical, but simply manpower and interest.
Projects need to be marked as working, updated to 2.9, documentation,
working builds, etc and nobody has the time or interest.

> For the wxCode SourceForge project in effect every project member could
> work on *all* components. The SourceForge SVN doesn't support a
> fine-grained access control.

This has never been a problem as far as I know.

>> This will be something I would like to try to do as an experimental/demo
>> project to let you see how it will works and also get possible
>> suggestions time by time and, if successful, consider a future transition.
>
> I think it's an interesting idea and I'm curious to hear about the first
> experiences of you. Maybe this could give wxCode a new impulse to get a
> better image and to get into a better shape.

There is a "live" SVN -> Git translator and wxWidgets uses it. Perhaps
this could work here as well?

https://github.com/wxWidgets/wxWidgets

Regards,
    John

Re: [wxCode-users] github 'poll' request

[PGridDev <pgr...@ya...>]

Hi Andrea & all

Here my 2 cents in reply to Andrea's proposal:

I just started using GIT a few months ago on another project, but it seems to me like the way to go: very flexible and designed just for massively distributed, open source software projects.

There is a 'but' of course: the learning curve is steeper than CVS/SVN, and the administration complexer. I think that we would need at least 2 admins who know GIT well enough and can help in case of merge conflicts and who can generally support the wxCode community (e.g. branch issues, corrupt repositories)

We might want to use gitolite (https://github.com/sitaramc/gitolite/) for the user/priviledge administration.

Regards -Ronan



On 19/06/2012 13:36, Andrea wrote:
> Hi,
> I would like to ask to you all wxCode component maintainers your
> opinion/suggestions about an idea I had in mind from a couple of time:
>
> I would like to have a new wxCode home on github (so to use Git instead
> SVN as SCM system).
>
> I think this way will improve wxCode project with a better organization,
> having:
>
> - more than one maintainer for each component project
> - create more components categories (e.g. pre and post wx 2.9,
> 'wxSnippets' for dead/wxCode external projects etc.)
> - use git hooks / custom scripts for easy websites/components maintainance
> - more flexible repositories inside a unique wxCode 'github organization'
> - more than one repository for each component project (like the usual
> trunk/tags/branches)
> - get component fixes via github pull requests instead usual patch files
>
> I've discussed about this with Ulrich Telle and we would like to see
> your point of view.
>
> This will be something I would like to try to do as an experimental/demo
> project to let you see how it will works and also get possible
> suggestions time by time and, if successful, consider a future transition.
>
> Regards
>
> Andrea

Re: [wxCode-users] github 'poll' request

[Ulrich T. <ulr...@gm...>]

Hi Andrea,

> I would like to ask to you all wxCode component maintainers your
> opinion/suggestions about an idea I had in mind from a couple of time:
>
> I would like to have a new wxCode home on github (so to use Git instead
> SVN as SCM system).

As SourceForge put up several restrictions regarding project maintenance 
and administration which makes maintaining wxCode sometimes quite 
cumbersome and as a single SourceForge project is not very well suited 
for maintaining a big collection of only loosely coupled components I 
definitely support your experiment.

> I think this way will improve wxCode project with a better organization,
> having:
>
> - more than one maintainer for each component project

For the wxCode SourceForge project in effect every project member could 
work on *all* components. The SourceForge SVN doesn't support a 
fine-grained access control.

> - create more components categories (e.g. pre and post wx 2.9,
> 'wxSnippets' for dead/wxCode external projects etc.)

Introducing new component categories could be easily added on SF wxCode 
as well, but only an administrator could do it.

> - use git hooks / custom scripts for easy websites/components maintainance

This would be definitely much better than what have now.

> - more flexible repositories inside a unique wxCode 'github organization'

This would also be a big advantage.

> - more than one repository for each component project (like the usual
> trunk/tags/branches)

AFAIK on the SF wxCode SVN tags weren't used at all, probably because 
tagging would really mean to tag wxCode as a whole what just isn't the 
right thing for independent components.

> - get component fixes via github pull requests instead usual patch files

As I seldom received patch files for my own components over the last 7 
years I can't judge how important this feature might be for other wxCode 
maintainers.

> This will be something I would like to try to do as an experimental/demo
> project to let you see how it will works and also get possible
> suggestions time by time and, if successful, consider a future transition.

I think it's an interesting idea and I'm curious to hear about the first 
experiences of you. Maybe this could give wxCode a new impulse to get a 
better image and to get into a better shape.

Regards,

Ulrich

[wxCode-users] github 'poll' request

[Andrea <xvi...@gm...>]

Hi,
I would like to ask to you all wxCode component maintainers your 
opinion/suggestions about an idea I had in mind from a couple of time:

I would like to have a new wxCode home on github (so to use Git instead 
SVN as SCM system).

I think this way will improve wxCode project with a better organization, 
having:

- more than one maintainer for each component project
- create more components categories (e.g. pre and post wx 2.9, 
'wxSnippets' for dead/wxCode external projects etc.)
- use git hooks / custom scripts for easy websites/components maintainance
- more flexible repositories inside a unique wxCode 'github organization'
- more than one repository for each component project (like the usual 
trunk/tags/branches)
- get component fixes via github pull requests instead usual patch files

I've discussed about this with Ulrich Telle and we would like to see 
your point of view.

This will be something I would like to try to do as an experimental/demo 
project to let you see how it will works and also get possible 
suggestions time by time and, if successful, consider a future transition.

Regards

Andrea

[wxCode-users] [ wxcode-Bugs-3531156 ] wxStEdit Build error

[SourceForge.net <no...@so...>]

Bugs item #3531156, was opened at 2012-05-31 12:16
Message generated for change (Tracker Item Submitted) made by smitchell
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3531156&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: Subversion TRUNK
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: smitchell (smitchell)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxStEdit Build error

Initial Comment:
Using SVN rev. 3015
wxCheckBox not defined in context.
Build env. MinGW 4.6.1, wx2.9.3 monolithic DLL, win7-x64
Patch file attached

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=3531156&group_id=51305

[wxCode-users] FormatValidator 2.0 released

[Manolo <man...@gm...>]

Hi all

I'm proud to announce the release of wxFormatValidator 2.0
With it, formatting a number and validating it is featured as never before.

Formatting:
- It works only with wxString, allowing a very very large number. No CPU limits.
- Format style can be from very simple to very complex, allowing not
only thousands separator but also prefix,
suffix, padding, characters between digits, sign position,
exponential, scientific and engineering notation, etc.
- Different format-styles for positive, negative and zero values.
- Rounding off is an option.
- Formatted strings can be unformatted. You can read formatted strings
from a file and transform them into their
C-locale representation.

Validating:
- Tolerant/Strict modes allow dismiss "typos" or complain about them.
- Range check. Several types of range definition.
- Not only "numbers" are valid entries. You can set other strings to
be accepted as valid.
- You decide what to do with an empty entry: allow, reject, replace
- You decide "when" validation will be done: while typing, when
"Enter/Tab-key", when focus is lost or combinations of them.
- You can decide if focus should be retained when validation fails.
- Coloring the control depending on validation succeed/fail.
- This validator can be attached to a wxTextCtrl or a wxComboBox.
Special wxGridCellEditor are also featured.
- Transfer the control's string to your var unformatted or keeping it formatted.

Download sources, documentation and a sample for this component at
http://wxcode.sourceforge.net/
wxWidgets 2.9 is required.

Regards,
Manolo