wxcode-users — Submission, Questions, Information

Re: [wxCode-users] wxCode project improvements

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

On 7/23/05, Francesco Montorsi <f18...@ya...> wrote:
> Also I notices that one of them, "wxvidcap" was written by you... but
> it's currently flagged as unmaintained and it looks so :-(
> is that right ?

I've been meaning to update that with a newer version. Someone must
have uploaded that version, which is quite ancient. But, it would
compile and work just fine in wxWindows 2.2 IIRC. :)

> > I won't have any time to do anything before the fall. I suppose it
> > wouldn't be too hard to whip up bakefiles and at least try to compile
> > them, noting the result in the component list and of course adding the
> > bakefiles, makefiles, and project files to the cvs for others. If you
> > have time that'd be great.
> as soon as I complete the WebUpdate component, I'll try to do it...
> I'll also need CVS write access for these components...

I'll have to defer to Otto, but I don't see why not.

Regards,
    John Labenski

Re: [wxCode-users] wxCode project improvements

[Francesco M. <f18...@ya...>]

Hi,

>> >> I've just added the UNMANTAINED search option in the website search
>>page.
>> >> So it's now easier for wxCode administrator to find the unmantained
>> >> components (actually there are 15 of them ! half of the registered
>> >> components; shouldn't we do a cleanup ??)
>> >
>> > I don't know what you mean by cleanup, just because a project hasn't
>> > been tinkered with recently doesn't mean that it doesn't work as
>> > advertised.
>>
>>Almost all (and I say "almost" only because I haven't tried them all
>>yet) do not provide any working build system so that it's impossible to
>>compile them to test if they work without writing a new bakefile/makefile.
>>Looking at the dates in the source files and in the readmes I find that
>>most of these components have been created for wx2.0 or wx2.2 and I
>>really doubt that they could still compile and work for wx2.6 without
>>some work on them.
> 
> 
> You're right... after checking again, there are a few that are in
> rough shape. I don't know what's the best way to handle them. I'd say
> just leave them for now.
ok, but I will prepare a mail to send the next week on wx-users to find 
maintainers ;-)

Also I notices that one of them, "wxvidcap" was written by you... but 
it's currently flagged as unmaintained and it looks so :-(
is that right ?

Also we have 47 components in the CVS while we have registered in the 
wxCode DB only 33 of them... this should be fixed



>> > I was actually thinking that we should tone down the
>> > UNMAINTAINED banner since it'll only discourage people.
>>
>>maybe it does but I think that anyone who needs a component wants
>>something reliable or at least working; and actually unmaintained
>>components are not reliable nor "compilable"...
> 
> 
> I completely agree, in order to wxCode to be successful, the
> components have to work, otherwise people won't bother. However, each
> component does say if it has a build system and sample, which should
> be a good indication of it's "status".
> 
> 
>>It's a pity remove code that could still be useful with some
>>modifications... maybe we should add some links (something like "Want to
>>be the maintainer for this component ?") in the complist which are shown
>>in each unmaintained component and which point to the register page;
>>maybe in this way we could find some mantainer for reworking of current
>>components...
> 
> 
> That sounds like a good idea. 
ok; i'll implement that in the next week (this weekend I'm in holiday ;-))



> 
> 
>>if you find some unmaintaned components which you can get to work, then
>>please report it... maybe I should write a simple bakefile, maybe just
>>for win32 compilers (which I can test easier than GCC) to add to the
>>more promising unmaintaned components...
> 
> 
> I won't have any time to do anything before the fall. I suppose it
> wouldn't be too hard to whip up bakefiles and at least try to compile
> them, noting the result in the component list and of course adding the
> bakefiles, makefiles, and project files to the cvs for others. If you
> have time that'd be great.
as soon as I complete the WebUpdate component, I'll try to do it...
I'll also need CVS write access for these components...

Francesco

Re: [wxCode-users] wxCode project improvements

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

On 7/22/05, Francesco Montorsi <f18...@ya...> wrote:
>  >> I've just added the UNMANTAINED search option in the website search
> page.
>  >> So it's now easier for wxCode administrator to find the unmantained
>  >> components (actually there are 15 of them ! half of the registered
>  >> components; shouldn't we do a cleanup ??)
>  >
>  > I don't know what you mean by cleanup, just because a project hasn't
>  > been tinkered with recently doesn't mean that it doesn't work as
>  > advertised.
>=20
> Almost all (and I say "almost" only because I haven't tried them all
> yet) do not provide any working build system so that it's impossible to
> compile them to test if they work without writing a new bakefile/makefile=
.
> Looking at the dates in the source files and in the readmes I find that
> most of these components have been created for wx2.0 or wx2.2 and I
> really doubt that they could still compile and work for wx2.6 without
> some work on them.

You're right... after checking again, there are a few that are in
rough shape. I don't know what's the best way to handle them. I'd say
just leave them for now.

>  > I was actually thinking that we should tone down the
>  > UNMAINTAINED banner since it'll only discourage people.
>=20
> maybe it does but I think that anyone who needs a component wants
> something reliable or at least working; and actually unmaintained
> components are not reliable nor "compilable"...

I completely agree, in order to wxCode to be successful, the
components have to work, otherwise people won't bother. However, each
component does say if it has a build system and sample, which should
be a good indication of it's "status".

> It's a pity remove code that could still be useful with some
> modifications... maybe we should add some links (something like "Want to
> be the maintainer for this component ?") in the complist which are shown
> in each unmaintained component and which point to the register page;
> maybe in this way we could find some mantainer for reworking of current
> components...

That sounds like a good idea.=20

> if you find some unmaintaned components which you can get to work, then
> please report it... maybe I should write a simple bakefile, maybe just
> for win32 compilers (which I can test easier than GCC) to add to the
> more promising unmaintaned components...

I won't have any time to do anything before the fall. I suppose it
wouldn't be too hard to whip up bakefiles and at least try to compile
them, noting the result in the component list and of course adding the
bakefiles, makefiles, and project files to the cvs for others. If you
have time that'd be great.

Regards,
    John Labenski

Re: [wxCode-users] Cron job: wxPlot-plplot is pending approval

[Francesco M. <f18...@ya...>]

sorry; I forgot to set the "approved" flag for this component so that 
the script has sent it to the mailing list again...

(to be precise, I actually merged the old wxPlot component database 
entry with this new one).

Francesco


Francesco Montorsi wrote:
> name: wxPlot-plplot
> wxversion: 2.4
> category: gui
> language: cpp
> description: wxPlot - plplot - 5.5.1
> 
> wxPlot - plplot - 5.5.1 is a plplot distribution libraries to show scientific graphs on wxWindows/wxWidgets programs.
> 
> The driver was created in 1999 by F. Fhuebner. I have now updated the code to a newest version of plplot, and I have made a new makefile too for Linux and Windows Operating Systems using plplot code rules. 
> location: wxPlot - plplot - 5.5.1
> cdate: 2020-07-20
> id: 75
> status: beta
> docs: notavailable
> buildsys: makefiles
> extdep: none
> wiki: disabled
> wxport: wxmsw,wxgtk
> samples: 1
> approved: 0
> author: Germán Carrera
> version: 0.5
> mantainerid: 13
> 
> Mantainer SF username: carreracg
> Mantainer name: Germán Carrera
> Mantainer mail address: car...@us...
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
> 

[wxCode-users] Cron job: wxPlot-plplot is pending approval

[Francesco M. <fr...@us...>]

name: wxPlot-plplot
wxversion: 2.4
category: gui
language: cpp
description: wxPlot - plplot - 5.5.1

wxPlot - plplot - 5.5.1 is a plplot distribution libraries to show scientific graphs on wxWindows/wxWidgets programs.

The driver was created in 1999 by F. Fhuebner. I have now updated the code to a newest version of plplot, and I have made a new makefile too for Linux and Windows Operating Systems using plplot code rules. 
location: wxPlot - plplot - 5.5.1
cdate: 2020-07-20
id: 75
status: beta
docs: notavailable
buildsys: makefiles
extdep: none
wiki: disabled
wxport: wxmsw,wxgtk
samples: 1
approved: 0
author: Germán Carrera
version: 0.5
mantainerid: 13

Mantainer SF username: carreracg
Mantainer name: Germán Carrera
Mantainer mail address: car...@us...

Re: [wxCode-users] wxCode project improvements

[Francesco M. <f18...@ya...>]

Hi,

 >> I've just added the UNMANTAINED search option in the website search 
page.
 >> So it's now easier for wxCode administrator to find the unmantained
 >> components (actually there are 15 of them ! half of the registered
 >> components; shouldn't we do a cleanup ??)
 >
 >
 > I don't know what you mean by cleanup, just because a project hasn't
 > been tinkered with recently doesn't mean that it doesn't work as
 > advertised.

Almost all (and I say "almost" only because I haven't tried them all 
yet) do not provide any working build system so that it's impossible to 
compile them to test if they work without writing a new bakefile/makefile.
Looking at the dates in the source files and in the readmes I find that 
most of these components have been created for wx2.0 or wx2.2 and I 
really doubt that they could still compile and work for wx2.6 without 
some work on them.


 > I was actually thinking that we should tone down the
 > UNMAINTAINED banner since it'll only discourage people.

maybe it does but I think that anyone who needs a component wants 
something reliable or at least working; and actually unmaintained 
components are not reliable nor "compilable"...

It's a pity remove code that could still be useful with some 
modifications... maybe we should add some links (something like "Want to 
be the maintainer for this component ?") in the complist which are shown 
in each unmaintained component and which point to the register page; 
maybe in this way we could find some mantainer for reworking of current 
components...
we should also send a msg with a list of unmaintaned components to the 
wx-users mailist list searching for maintainers...

 > If however
 > there are projects that simply don't work (for the specified wxWidgets
 > version and platform) then that's a different story and this should be
 > noted somehow, but again not to completely discourage people since
 > maybe someone will try it and patch it up.

if you find some unmaintaned components which you can get to work, then 
please report it... maybe I should write a simple bakefile, maybe just 
for win32 compilers (which I can test easier than GCC) to add to the 
more promising unmaintaned components...

Francesco

Re: [wxCode-users] Cron job: wxPlot-plplot is pending approval

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

On 7/21/05, Francesco Montorsi <f18...@ya...> wrote:
> Subject: Re: [wxCode-users] Cron job: wxPlot-plplot is pending approval
>
> Hi Francesco,
>
> I think that the best option is to use the name of wxplot (for the
> component).
>
> There are a couple of problems to change the name of the class.
>
> The firts is that the people of plplot are working on a new driver
> called wxplplot (with this name of class).
>
> The second, is a reason of compatibility (old aplications made with
> the old Fhuebner's code)
> that use the wxPlot (not the contribs wxidgets wxPlot) name of class
> (wxPlot *wxplot; in samples). If the people want to upgrade or
> recompile their programs with the new wxPlot (wxplot plplot) library,
> they can have some problems with the change.

Ok, Germ=E1n, how about you just take over the current wxplot and update
it as necessary? If I understand correctly, that would make more sense
than creating a new project since I don't think anyone else is
maintaining it. I've updated the component list and added you as an
author and you have cvs write access for wxCode/components/wxplot.
Feel free to edit the description if you think it should be more
verbose as to it's features and also what platforms it works in.

Thanks,
   John Labenski

[Fwd: Re: [wxCode-users] Cron job: wxPlot-plplot is pending approval]

[Francesco M. <f18...@ya...>]

[Forwarded to wxCode ML]

-------- Original Message --------
Subject: Re: [wxCode-users] Cron job: wxPlot-plplot is pending approval
Date: Thu, 21 Jul 2005 16:18:02 +0200
From: Germán Carrera <ger...@gm...>
Reply-To: Germán Carrera <ger...@gm...>
To: f18...@ya...
References: <E1D...@sc...>	 
<a84...@ma...> <42D...@ya...>

Hi Francesco,

I think that the best option is to use the name of wxplot (for the 
component).

There are a couple of problems to change the name of the class.

The firts is that the people of plplot are working on a new driver
called wxplplot (with this name of class).

The second, is a reason of compatibility (old aplications made with
the old Fhuebner's code)
that use the wxPlot (not the contribs wxidgets wxPlot) name of class
(wxPlot *wxplot; in samples). If the people want to upgrade or
recompile their programs with the new wxPlot (wxplot plplot) library,
they can have some problems with the change.

Thanks, Germán.





On 7/21/05, Francesco Montorsi <f18...@ya...> wrote:
> Hi John,
> 
> John Labenski wrote:
> > Germán, can we just give it the unix name "wxplplot" (this is the
> > directory name that will be used) and wxPlPlot as the component name?
> > If I remember correctly, it's been years since I looked Fhuebner's
> > code, it's not related nor uses the wxPlot in the wxWidgets/contrib
> > dir?
> The code is completely independent from the wxPlot contrib library of
> the wxWidgets distribution but "wxplot" is the name of the old version
> of the Fhuebner's component in the wxCode repository... I think we
> should just use that name so that the sources in
> wxCode\components\wxplot can be updated with Germàn's new version.
> 
> Otherwise we should remove wxCode\components\wxplot and create something
> like wxCode\components\wxplplot like you said...
> 
> Francesco
> 
> 
> >
> > Thanks,
> >     John Labenski
> >
> > On 7/20/05, Francesco Montorsi <fr...@us...> wrote:
> >
> >>name: wxPlot-plplot
> >>wxversion: 2.4
> >>category: gui
> >>language: cpp
> >>description: wxPlot - plplot - 5.5.1
> >>
> >>wxPlot - plplot - 5.5.1 is a plplot distribution libraries to show scientific graphs on wxWindows/wxWidgets programs.
> >>
> >>The driver was created in 1999 by F. Fhuebner. I have now updated the code to a newest version of plplot, and I have made a new makefile too for Linux and Windows Operating Systems using plplot code rules.
> >>location: wxPlot - plplot - 5.5.1
> >>cdate: 2020-07-20
> >>id: 75
> >>status: beta
> >>docs: notavailable
> >>buildsys: makefiles
> >>extdep: none
> >>wiki: disabled
> >>wxport: wxmsw,wxgtk
> >>samples: 1
> >>approved: 0
> >>author: Germán Carrera
> >>version: 0.5
> >>mantainerid: 13
> >>
> >>Mantainer SF username: carreracg
> >>Mantainer name: Germán Carrera
> >>Mantainer mail address: car...@us...
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> >>from IBM. Find simple to follow Roadmaps, straightforward articles,
> >>informative Webcasts and more! Get everything you need to get up to
> >>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> >>_______________________________________________
> >>wxCode-users mailing list
> >>wxC...@li...
> >>https://lists.sourceforge.net/lists/listinfo/wxcode-users
> >>
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
> > _______________________________________________
> > wxCode-users mailing list
> > wxC...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxcode-users
> >
> 
>

Re: [wxCode-users] Cron job: wxPlot-plplot is pending approval

[Francesco M. <f18...@ya...>]

Hi John,

John Labenski wrote:
> Germán, can we just give it the unix name "wxplplot" (this is the
> directory name that will be used) and wxPlPlot as the component name?
> If I remember correctly, it's been years since I looked Fhuebner's
> code, it's not related nor uses the wxPlot in the wxWidgets/contrib
> dir?
The code is completely independent from the wxPlot contrib library of 
the wxWidgets distribution but "wxplot" is the name of the old version 
of the Fhuebner's component in the wxCode repository... I think we 
should just use that name so that the sources in 
wxCode\components\wxplot can be updated with Germàn's new version.

Otherwise we should remove wxCode\components\wxplot and create something 
like wxCode\components\wxplplot like you said...

Francesco


> 
> Thanks,
>     John Labenski
> 
> On 7/20/05, Francesco Montorsi <fr...@us...> wrote:
> 
>>name: wxPlot-plplot
>>wxversion: 2.4
>>category: gui
>>language: cpp
>>description: wxPlot - plplot - 5.5.1
>>
>>wxPlot - plplot - 5.5.1 is a plplot distribution libraries to show scientific graphs on wxWindows/wxWidgets programs.
>>
>>The driver was created in 1999 by F. Fhuebner. I have now updated the code to a newest version of plplot, and I have made a new makefile too for Linux and Windows Operating Systems using plplot code rules.
>>location: wxPlot - plplot - 5.5.1
>>cdate: 2020-07-20
>>id: 75
>>status: beta
>>docs: notavailable
>>buildsys: makefiles
>>extdep: none
>>wiki: disabled
>>wxport: wxmsw,wxgtk
>>samples: 1
>>approved: 0
>>author: Germán Carrera
>>version: 0.5
>>mantainerid: 13
>>
>>Mantainer SF username: carreracg
>>Mantainer name: Germán Carrera
>>Mantainer mail address: car...@us...
>>
>>
>>
>>-------------------------------------------------------
>>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>>informative Webcasts and more! Get everything you need to get up to
>>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>>_______________________________________________
>>wxCode-users mailing list
>>wxC...@li...
>>https://lists.sourceforge.net/lists/listinfo/wxcode-users
>>
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
> 

Re: [wxCode-users] Cron job: wxPlot-plplot is pending approval

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

Germ=E1n, can we just give it the unix name "wxplplot" (this is the
directory name that will be used) and wxPlPlot as the component name?
If I remember correctly, it's been years since I looked Fhuebner's
code, it's not related nor uses the wxPlot in the wxWidgets/contrib
dir?

Thanks,
    John Labenski

On 7/20/05, Francesco Montorsi <fr...@us...> wrote:
> name: wxPlot-plplot
> wxversion: 2.4
> category: gui
> language: cpp
> description: wxPlot - plplot - 5.5.1
>=20
> wxPlot - plplot - 5.5.1 is a plplot distribution libraries to show scient=
ific graphs on wxWindows/wxWidgets programs.
>=20
> The driver was created in 1999 by F. Fhuebner. I have now updated the cod=
e to a newest version of plplot, and I have made a new makefile too for Lin=
ux and Windows Operating Systems using plplot code rules.
> location: wxPlot - plplot - 5.5.1
> cdate: 2020-07-20
> id: 75
> status: beta
> docs: notavailable
> buildsys: makefiles
> extdep: none
> wiki: disabled
> wxport: wxmsw,wxgtk
> samples: 1
> approved: 0
> author: Germ=E1n Carrera
> version: 0.5
> mantainerid: 13
>=20
> Mantainer SF username: carreracg
> Mantainer name: Germ=E1n Carrera
> Mantainer mail address: car...@us...
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic=
k
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

[wxCode-users] Cron job: wxPlot-plplot is pending approval

[Francesco M. <fr...@us...>]

name: wxPlot-plplot
wxversion: 2.4
category: gui
language: cpp
description: wxPlot - plplot - 5.5.1

wxPlot - plplot - 5.5.1 is a plplot distribution libraries to show scientific graphs on wxWindows/wxWidgets programs.

The driver was created in 1999 by F. Fhuebner. I have now updated the code to a newest version of plplot, and I have made a new makefile too for Linux and Windows Operating Systems using plplot code rules. 
location: wxPlot - plplot - 5.5.1
cdate: 2020-07-20
id: 75
status: beta
docs: notavailable
buildsys: makefiles
extdep: none
wiki: disabled
wxport: wxmsw,wxgtk
samples: 1
approved: 0
author: Germán Carrera
version: 0.5
mantainerid: 13

Mantainer SF username: carreracg
Mantainer name: Germán Carrera
Mantainer mail address: car...@us...

Re: [wxCode-users] wxCode project improvements

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

On 7/19/05, Francesco Montorsi <f18...@ya...> wrote:
> I've just added the UNMANTAINED search option in the website search page.
> So it's now easier for wxCode administrator to find the unmantained
> components (actually there are 15 of them ! half of the registered
> components; shouldn't we do a cleanup ??)

I don't know what you mean by cleanup, just because a project hasn't
been tinkered with recently doesn't mean that it doesn't work as
advertised. I was actually thinking that we should tone down the
UNMAINTAINED banner since it'll only discourage people. If however
there are projects that simply don't work (for the specified wxWidgets
version and platform) then that's a different story and this should be
noted somehow, but again not to completely discourage people since
maybe someone will try it and patch it up.

> Francesco Montorsi wrote:
> >    I would like to inform all mantainers that recently
> > 1) the bakefile build system of wxCode was updated to allow not only

Looks good, I'll try it later this week.

Regards,
    John Labenski

Re: [wxCode-users] wxCode project improvements

[Francesco M. <f18...@ya...>]

I've just added the UNMANTAINED search option in the website search page.
So it's now easier for wxCode administrator to find the unmantained 
components (actually there are 15 of them ! half of the registered 
components; shouldn't we do a cleanup ??)

Francesco



Francesco Montorsi wrote:
> Hi,
>    I would like to inform all mantainers that recently
> 
> 1) the bakefile build system of wxCode was updated to allow not only 
> static builds but also easy-shared builds of wxCode components.
> Also some utilities for the "make uninstall" targets in the autoconf 
> scripts have been added.
> 
> 2) the wxCode\template folder (which is in the CVS) contains the 
> website\index.php file which, if you open in a simple editor, shows how 
> to make an amazing website for your component with the new wxCode 
> website style !
> It's so easy and it gives so many easy-to-use features (automatic 
> thumbnail creation, syntax highlighting, connection to the wxCode DB) 
> which I strongly suggest everyone to update their component website.
> 
> Remember that all changes you do to your component's website folder is 
> committed in the wxCode website each 24 hours.
> 
> 3) If you don't want to write a index page for your component you can 
> use the wxCode wiki at http://wxcode.sf.net/wiki/index.php...
> it also has the syntax highlighting feature...
> 
> 
> Last, I'd like to say a great thanks to David Hart which helped me a lot 
> to improve the website with new FAQ entries and website-bugs notifications.
> 
> For further info, please mail me,
> Francesco Montorsi
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by HP,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
> 

Re: [wxCode-users] wxCode logo

[Francesco M. <f18...@ya...>]

I've changed the wxCode logo to something I like... hope this is okay...

Francesco


Francesco Montorsi wrote:
> Hi,
>   I'd like to know if someone is interested in proposing some good 
> graphics for a wxCode logo to show in the top-left corner of the 
> website; thanks to Jorgen Bodde, I have now added to CVS a Paint Shop 
> Pro file of the wx-logo containing some vector graphics which can be 
> scaled at any size without resolution losses... I have tried to create 
> some original logo without great success; the results can be found at: 
> wxCode/website/images/ .
> 
> Have you some good idea ?
> 
> Francesco
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
> 

Re: [wxCode-users] Cron job: wxSQLite3 is pending approval

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

On 7/17/05, Francesco Montorsi <f18...@ya...> wrote:
> updated the DB; Otto or John will give you CVS access...

Added in components/wxsqlite3, give SF a few hours to update itself
before adding to it.

Regards,
    John Labenski

=20
> Francesco wrote:
> > name: wxSQLite3
> > wxversion: 2.6
> > category: non-gui
> > language: cpp
> > description: wxSQLite3 is a C++ wrapper around the public domain SQLite=
 3.x database and is specifically designed for use in programs based on the=
 wxWidgets library.
> >
> > wxSQLite3 does not try to hide the underlying database, in contrary alm=
ost all special features of the current SQLite3 version 3.2.2 are supported=
, like for example the creation of user defined scalar or aggregate functio=
ns.
> >
> > Since SQLite stores strings in UTF-8 encoding, the wxSQLite3 methods pr=
ovide automatic conversion between wxStrings and UTF-8 strings. This works =
best for the Unicode builds of wxWidgets. This feature is not fully tested =
for ANSI builds.
> >
> > location: wxsqlite3
> > cdate: 2017-07-20
> > id: 74
> > status: stable
> > docs: doxygen
> > buildsys: bakefile
> > extdep: SQLite database
> > wiki: disabled
> > wxport: wxmsw
> > samples: 1
> > approved: 0
> > author: Ulrich Telle
> > version: 1.0
> > mantainerid: 12
> >
> > Mantainer SF username: utelle
> > Mantainer name: Ulrich Telle
> > Mantainer mail address: ulr...@gm...
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcl=
ick
> > _______________________________________________
> > wxCode-users mailing list
> > wxC...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxcode-users
> >
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic=
k
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] Cron job: wxSQLite3 is pending approval

[Francesco M. <f18...@ya...>]

updated the DB; Otto or John will give you CVS access...

Francesco wrote:
> name: wxSQLite3
> wxversion: 2.6
> category: non-gui
> language: cpp
> description: wxSQLite3 is a C++ wrapper around the public domain SQLite 3.x database and is specifically designed for use in programs based on the wxWidgets library.
> 
> wxSQLite3 does not try to hide the underlying database, in contrary almost all special features of the current SQLite3 version 3.2.2 are supported, like for example the creation of user defined scalar or aggregate functions.
> 
> Since SQLite stores strings in UTF-8 encoding, the wxSQLite3 methods provide automatic conversion between wxStrings and UTF-8 strings. This works best for the Unicode builds of wxWidgets. This feature is not fully tested for ANSI builds. 
> 
> location: wxsqlite3
> cdate: 2017-07-20
> id: 74
> status: stable
> docs: doxygen
> buildsys: bakefile
> extdep: SQLite database
> wiki: disabled
> wxport: wxmsw
> samples: 1
> approved: 0
> author: Ulrich Telle
> version: 1.0
> mantainerid: 12
> 
> Mantainer SF username: utelle
> Mantainer name: Ulrich Telle
> Mantainer mail address: ulr...@gm...
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
> 

[wxCode-users] Cron job: wxSQLite3 is pending approval

[Francesco <fr...@us...>]

name: wxSQLite3
wxversion: 2.6
category: non-gui
language: cpp
description: wxSQLite3 is a C++ wrapper around the public domain SQLite 3.x database and is specifically designed for use in programs based on the wxWidgets library.

wxSQLite3 does not try to hide the underlying database, in contrary almost all special features of the current SQLite3 version 3.2.2 are supported, like for example the creation of user defined scalar or aggregate functions.

Since SQLite stores strings in UTF-8 encoding, the wxSQLite3 methods provide automatic conversion between wxStrings and UTF-8 strings. This works best for the Unicode builds of wxWidgets. This feature is not fully tested for ANSI builds. 

location: wxsqlite3
cdate: 2017-07-20
id: 74
status: stable
docs: doxygen
buildsys: bakefile
extdep: SQLite database
wiki: disabled
wxport: wxmsw
samples: 1
approved: 0
author: Ulrich Telle
version: 1.0
mantainerid: 12

Mantainer SF username: utelle
Mantainer name: Ulrich Telle
Mantainer mail address: ulr...@gm...

[wxCode-users] Best way to handle external dependencies ?

[Francesco M. <f18...@ya...>]

Hi,
    I'd like to know how are you handling external dependencies: I have
some components which work as "bridge" between other libraries &
wxWidgets and all the times I need to check them out in a new
workstation, I also need to download those other libraries, remember 
what I have to do to compile them; compile them and then compile my 
component using the appropriate OTHERLIB_DIR makefile options so that my 
component can find the header & .lib files of these "third-party" libraries.

I think that there must be some way to make the process quicker: I know 
that this issue is something more generic than wxCode but the problem is 
that those people who want to use such components which require 
additional libraries, always need to do all that additional work and 
maybe they just decide to give up using a component because of all this...

maybe the best solution is to add in the wxCode CVS the source files & 
header files (excluding all other stuff which usually comes with a 
release: docs, test programs, etc) of those "thirdparty" libraries.

I found this approach very comfortable when working on wxArt2d which 
keeps a folder "wxArt2d\thirdparty" where all the required libraries are 
stored.

Do you think this would be a good approach ?
In this case I would put in wxscript\thirdparty and wxxml2\thirdparty 
the libraries required by those two components... making a lot quicker 
and easier to use them...

Let me know your opinion,
Francesco

[wxCode-users] wxCode logo

[Francesco M. <f18...@ya...>]

Hi,
   I'd like to know if someone is interested in proposing some good 
graphics for a wxCode logo to show in the top-left corner of the 
website; thanks to Jorgen Bodde, I have now added to CVS a Paint Shop 
Pro file of the wx-logo containing some vector graphics which can be 
scaled at any size without resolution losses... I have tried to create 
some original logo without great success; the results can be found at: 
wxCode/website/images/ .

Have you some good idea ?

Francesco

Re: [wxCode-users] Cron job: try is pending approval

[Francesco M. <f18...@ya...>]

Ok;

> Mantainer SF username: frm
> Mantainer name: Francesco Montorsi
> Mantainer mail address: fr...@us...
now mantainer info are shown in the automatic mails...

FM

[wxCode-users] Cron job: try is pending approval

[Francesco <fr...@us...>]

name: try
wxversion: 2.4
category: gui
language: cpp
description: just a test for the new dumppendingcomp
location: your component name in lowercase
cdate: 0000-00-00
id: 73
status: alpha
docs: doxygen
buildsys: bakefile
extdep: none
wiki: website
wxport: wxmsw
samples: 0
approved: 0
author: me
version: 1.0
mantainerid: 1

Mantainer SF username: frm
Mantainer name: Francesco Montorsi
Mantainer mail address: fr...@us...

Re: [wxCode-users] Cron job: wxTreeMultiCtrl is pending approval

[Francesco M. <f18...@ya...>]

Hi,

>>do you mean that we should add the sf user name in the mails sent ?
>>When you submit a component you must be registered as mantainer and thus
>>you must have submitted a SF user name which is already in the DB...
> 
> I guess it's ok, in order to update the CVS access of a component we
> need the SF user name. I guess we can look it up in the wxcode
> maintainer's database (I forgot about this). I mentioned this since
> when I searched for "Jorgen Bodde" at SF (for people) it actually
> doesn't come up with him. :/  On a chance I tried "jorgb" and verified
> his SF user name. Maybe this was a fluke, but to avoid this and also
> to avoid problems with users with common names I thought it might make
> sense to just put their SF name with the component in the component
> database since they have to log in with it anyway.
there would be a problem putting SF user names in the "components" table 
which has to do with database normalization: we would put redundant info 
in component entries since a mantainer can be associated to more components.

So, that would really be a bad choice; it would also need a lot of work 
on the current PHP site code... :-(
Also, it would not give any advantage.. see below

>>If you mean that it's missing from the mails sent, I agree and I'll
>>modify the script ASAP
> 
> 
> I'm not sure what you mean about this, the mails sent from people can
> be from any address, how will you look up their SF user name? Anyway,
> if it makes sense, it sounds good to me. :)
Ooops; sorry; I did not mean that; I meant that in the mails generated 
by dumppendingcomp.sh script, have in their body all the infos about the 
component which has been submitted but do not contain *any* info about 
the mantainer who submitted that component (the Author name can be 
different from the actual mantainer...) so I'm going to add such info in 
the mails generated by the script.
So, when we receive the notification, we can read the mantainer's sf 
username directly in the mail... ;-)

Francesco

Re: [wxCode-users] Cron job: wxTreeMultiCtrl is pending approval

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

On 7/13/05, Francesco Montorsi <f18...@ya...> wrote:
> > ps. Francesco: I think we need to have an entry for the user's SF user
> > name in the component, is this possible and could you add it?
> do you mean that we should add the sf user name in the mails sent ?
> When you submit a component you must be registered as mantainer and thus
> you must have submitted a SF user name which is already in the DB...

I guess it's ok, in order to update the CVS access of a component we
need the SF user name. I guess we can look it up in the wxcode
maintainer's database (I forgot about this). I mentioned this since
when I searched for "Jorgen Bodde" at SF (for people) it actually
doesn't come up with him. :/  On a chance I tried "jorgb" and verified
his SF user name. Maybe this was a fluke, but to avoid this and also
to avoid problems with users with common names I thought it might make
sense to just put their SF name with the component in the component
database since they have to log in with it anyway.
=20
> If you mean that it's missing from the mails sent, I agree and I'll
> modify the script ASAP

I'm not sure what you mean about this, the mails sent from people can
be from any address, how will you look up their SF user name? Anyway,
if it makes sense, it sounds good to me. :)

Regards,
    John Labenski

Re: [wxCode-users] Cron job: wxTreeMultiCtrl is pending approval

[Francesco M. <f18...@ya...>]

Hi,

> ps. Francesco: I think we need to have an entry for the user's SF user
> name in the component, is this possible and could you add it?
do you mean that we should add the sf user name in the mails sent ?
When you submit a component you must be registered as mantainer and thus 
you must have submitted a SF user name which is already in the DB...

If you mean that it's missing from the mails sent, I agree and I'll 
modify the script ASAP

Francesco

Re: [wxCode-users] Cron job: wxTreeMultiCtrl is pending approval

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

On 7/13/05, Francesco Montorsi <f18...@ya...> wrote:
> approved & updated the DB...
> John or Otto will update the CVSROOT\avail file to give you CVS access
> as soon as possible...

Done, it should be available in a few hours.=20
You can access it in wxCode\components\treemultictrl.

ps. Francesco: I think we need to have an entry for the user's SF user
name in the component, is this possible and could you add it?

Regards,
    John Labenski

> Francesco wrote:
> > name: wxTreeMultiCtrl
> > wxversion: all
> > category: gui
> > language: cpp
> > description: A tree control that can contain other ontrols, like a tree=
 shaped property sheet.
> > The wxTreeMultiCtrl is loosely based upon the wxTreeCtrl and contains t=
he same basic interface. However, the underlying functionality is a complet=
e rewrite, to allow wxWindow derived classes to be painted in a tree shaped=
 structure.
> > location: treemultictrl
> > cdate: 2013-07-20
> > id: 72
> > status: stable
> > docs: doxygen
> > buildsys: cmake
> > extdep: none
> > wiki: enabled
> > wxport: all
> > samples: 1
> > approved: 0
> > author: Jorgen Bodde
> > version: 1.08
> > mantainerid: 11