Menu
▾
▴
wxcode-users — Submission, Questions, Information
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...> - 2005-07-28 19:01:38
|
name: wxHTTPEngine wxversion: 2.5,2.6 category: language: cpp description: Put here 5-6 lines of description... location: wxhttpengine cdate: 2028-07-20 id: 77 status: stable docs: hand buildsys: bakefile extdep: none wiki: enabled wxport: all samples: 1 approved: 0 author: Angelo Mandato version: 1.0.2 mantainerid: 16 Mantainer SF username: amandato Mantainer name: Angelo Mandato Mantainer mail address: an...@sp... |
|
From: John L. <jla...@gm...> - 2005-07-28 15:12:33
|
On 7/28/05, Jorgen Bodde <sol...@xs...> wrote:
> John, thanks for your insight. I never thought about the cygwin solution
> and that when I used it lots in the old days ;-)
It's really nice these days, I don't know what I'd do on windows
without it. :) If you're interested I use icewm-1.2.15-1.tar.bz2
(which is now gone from the web) as a window manager since it's small
and unobtrusive, I could make it available to you.
> I am really curious what this issue is. Your corrupted CVS store makes
> sense, however I always deleted the old data completely before
> re-attemtping.
Can you download anything from wxCode's CVS? If so then maybe you
should look at the CVS/Root files to see if they're right. Compare
them to your other SF projects.
Mine contain
:ext:jr...@cv...:/cvsroot/wxcode
=20
> I can't wait to get this issue solved, because it has been some time now
> that wxTreeMultiCtrl needs to be checked in.
It's a shame that it doesn't work, please keep us updated.
> By the way, is it possible to have more then one maintainer for the code?
Sure, just write back with who you'd like to add.
Regards,
John Labenski
|
|
From: Francesco M. <f18...@ya...> - 2005-07-28 13:45:21
|
Hi, > By the way, is it possible to have more then one maintainer for the code? for CVS access, there's no problem; John or Otto should just add a new entry in the AVAIL file... also SF release system will work with multiple maintainers. however wxCode database currently allows only a single registered maintainer for each component... however, it could be useful to register multiple maintainers. However, it would require various work - we would need to change the "maintainerid" field from INT to SET, I think. Another solution could be to add another column: "maintainer2id" for a second maintainer (which should be enough). However, I'll not be able to implement this feature until I return back from my holidays ;-) Francesco > John Labenski wrote: > >> On 7/27/05, Jorgen Bodde <sol...@xs...> wrote: >> >>>>>> also I see that the following components have no source or header >>>>>> files >>>>>> in the CVS, just a "website" folder: >>>>>> >>>>>> treemultictrl -- this was just added two weeks ago IIRC >>> >>> >>> I am having problems with the stupid CVS interface of SF.net. I had a >>> previous project (multiple even like wxCRP) and I have never had as many >>> checkout problems as I have now. Basically all that happens is; >>> >>> I check out, files are created >>> Then WinCVS / TCVS hangs. Nothing happens anymore for hours >> >> >> >> I used to use WinCVS, but had similiar problems. Sometimes I found >> that just deleting the CVS directory and starting over would work. If >> you didn't properly log into the CVS WinCVS seemed to mess up the /CVS >> dirs making it impossible to update. It's pretty light on giving >> usable error messages (as is CVS) so it was hard to debug. Also there >> was always the confusion as to what repository WinCVS was set to use, >> which IIRC setting this seemed a little obtuse, but I don't remember >> it too well anymore. >> >> I switched to using cygwin instead and haven't looked back. You then >> use $cvs on the command line just like in linux and it works great. >> You have to mount your c:\ (or whatever drive you use) in DOS mode so >> that all files read/written will use CRLF instead of just LFs. >> I created a dir "/mnt/c" and then ran $mount -t -f "c:/" "/mnt/c" >> Now the c:\ drive is mounted every time you start cygwin as /mnt/c and >> if you go there all the files have DOS line endings and when you >> commit they are properly converted back to just LF for the CVS >> repository. >> >> I use this, instead of ssh since I haven't had time to understand it. >> I have to incessantly enter my password, but it ok for now. >> cvs -z3 -d:ext:jr...@cv...:/cvsroot/wxcode co ... >> >> Hope this helps, John Labenski >> >> ps. If you figure it out and think that something needs to be added or >> clarified on this page http://wxcode.sourceforge.net/mantguide.php >> could you write back. >> >> >> ------------------------------------------------------- >> 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Ìk >> _______________________________________________ >> wxCode-users mailing list >> wxC...@li... >> https://lists.sourceforge.net/lists/listinfo/wxcode-users >> >> >> > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September > 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users > |
|
From: Jorgen B. <sol...@xs...> - 2005-07-28 08:29:36
|
John, thanks for your insight. I never thought about the cygwin solution=20 and that when I used it lots in the old days ;-) I am really curious what this issue is. Your corrupted CVS store makes=20 sense, however I always deleted the old data completely before=20 re-attemtping. I can't wait to get this issue solved, because it has been some time now=20 that wxTreeMultiCtrl needs to be checked in. By the way, is it possible to have more then one maintainer for the code? - Jorgen John Labenski wrote: > On 7/27/05, Jorgen Bodde <sol...@xs...> wrote: >=20 >>>>>also I see that the following components have no source or header fi= les >>>>>in the CVS, just a "website" folder: >>>>> >>>>>treemultictrl -- this was just added two weeks ago IIRC >> >>I am having problems with the stupid CVS interface of SF.net. I had a >>previous project (multiple even like wxCRP) and I have never had as man= y >>checkout problems as I have now. Basically all that happens is; >> >>I check out, files are created >>Then WinCVS / TCVS hangs. Nothing happens anymore for hours >=20 >=20 > I used to use WinCVS, but had similiar problems. Sometimes I found > that just deleting the CVS directory and starting over would work. If > you didn't properly log into the CVS WinCVS seemed to mess up the /CVS > dirs making it impossible to update. It's pretty light on giving > usable error messages (as is CVS) so it was hard to debug. Also there > was always the confusion as to what repository WinCVS was set to use, > which IIRC setting this seemed a little obtuse, but I don't remember > it too well anymore. >=20 > I switched to using cygwin instead and haven't looked back. You then > use $cvs on the command line just like in linux and it works great. > You have to mount your c:\ (or whatever drive you use) in DOS mode so > that all files read/written will use CRLF instead of just LFs. > I created a dir "/mnt/c" and then ran=20 > $mount -t -f "c:/" "/mnt/c" > Now the c:\ drive is mounted every time you start cygwin as /mnt/c and > if you go there all the files have DOS line endings and when you > commit they are properly converted back to just LF for the CVS > repository. >=20 > I use this, instead of ssh since I haven't had time to understand it. > I have to incessantly enter my password, but it ok for now. > cvs -z3 -d:ext:jr...@cv...:/cvsroot/wxcode co ... >=20 > Hope this helps,=20 > John Labenski >=20 > ps. If you figure it out and think that something needs to be added or > clarified on this page http://wxcode.sourceforge.net/mantguide.php > could you write back. >=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_idt77&alloc_id=16492&op=CCk > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users >=20 >=20 >=20 |
|
From: <did...@op...> - 2005-07-27 23:43:46
|
> On 7/27/05, Jorgen Bodde <sol...@xs...> wrote: >> >>> also I see that the following components have no source or header files >> >>> in the CVS, just a "website" folder: >> >>> >> >>> treemultictrl -- this was just added two weeks ago IIRC >> >> I am having problems with the stupid CVS interface of SF.net. I had a >> previous project (multiple even like wxCRP) and I have never had as many >> checkout problems as I have now. Basically all that happens is; >> >> I check out, files are created >> Then WinCVS / TCVS hangs. Nothing happens anymore for hours I also had problems with WinCvs one time, and only on one repository. After long time searching, I only found the solution to use ssh protocol instead of :pserver: And some time after, I saw that the problem was my internet provider: when I used Cvs via my telephone line (RTC) I got no problem, with ADSL I could'nt checkout properly: it worked for some files, and then it waited, the it hangs. The pserver protocol seemed to be partialy blocked by the internet provider. Didier |
|
From: John L. <jla...@gm...> - 2005-07-27 17:41:34
|
On 7/27/05, Jorgen Bodde <sol...@xs...> wrote: > >>> also I see that the following components have no source or header fil= es > >>> in the CVS, just a "website" folder: > >>> > >>> treemultictrl -- this was just added two weeks ago IIRC >=20 > I am having problems with the stupid CVS interface of SF.net. I had a > previous project (multiple even like wxCRP) and I have never had as many > checkout problems as I have now. Basically all that happens is; >=20 > I check out, files are created > Then WinCVS / TCVS hangs. Nothing happens anymore for hours I used to use WinCVS, but had similiar problems. Sometimes I found that just deleting the CVS directory and starting over would work. If you didn't properly log into the CVS WinCVS seemed to mess up the /CVS dirs making it impossible to update. It's pretty light on giving usable error messages (as is CVS) so it was hard to debug. Also there was always the confusion as to what repository WinCVS was set to use, which IIRC setting this seemed a little obtuse, but I don't remember it too well anymore. I switched to using cygwin instead and haven't looked back. You then use $cvs on the command line just like in linux and it works great. You have to mount your c:\ (or whatever drive you use) in DOS mode so that all files read/written will use CRLF instead of just LFs. I created a dir "/mnt/c" and then ran=20 $mount -t -f "c:/" "/mnt/c" Now the c:\ drive is mounted every time you start cygwin as /mnt/c and if you go there all the files have DOS line endings and when you commit they are properly converted back to just LF for the CVS repository. I use this, instead of ssh since I haven't had time to understand it. I have to incessantly enter my password, but it ok for now. cvs -z3 -d:ext:jr...@cv...:/cvsroot/wxcode co ... Hope this helps,=20 John Labenski ps. If you figure it out and think that something needs to be added or clarified on this page http://wxcode.sourceforge.net/mantguide.php could you write back. |
|
From: Jorgen B. <sol...@xs...> - 2005-07-27 12:30:30
|
Don't worry about it Franchesco, I am really glad you have been so patient in helping me sofar. It is just frustrating that this happens, and I cannot find out why :-( I will try soon again under Linux. If that does not fail, I will keep working under linux on my laptop and give windows the boot. - Jorgen Francesco Montorsi wrote: > Hi, > >> I am having problems with the stupid CVS interface of SF.net. I had a >> previous project (multiple even like wxCRP) and I have never had as >> many checkout problems as I have now. Basically all that happens is; >> >> I check out, files are created >> Then WinCVS / TCVS hangs. Nothing happens anymore for hours >> >> The answer from Franchesco (reinstalling windows XP) seems to not >> solve this issue as I am not having problems with other SF.net checkouts. > > well, *I* solved my problems reinstalling winXP but that's was because > of a corruption of my installation. > > I don't understand what can be the cause of your CVS problems; your > CVSROOT is set to: > > :ssh:jo...@cv...:/cvsroot/wxcode > > ? > > anyway, if the files are created, you can terminate CVS client using > brute force and then work on the files which have been checked-out; > isn't it ? > > >> I will investigate further, but now that my 5th day of trying failed, >> I lost a bit of my interest in keeping trying. I have more things to >> do, and will see when I have the time again. So I am sorry for no >> updated source yet. > > I know that SF also creates nightly CVS tarballs for wxCode at: > > http://cvs.sourceforge.net/cvstarballs/wxcode-cvsroot.tar.bz2 > > but I don't know how to use that tarballs (they are some sort of CVS > backups which keep trace of all the modifications on all the files of > the repository...)... does anyone know ? > > 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 > > |
|
From: Francesco M. <f18...@ya...> - 2005-07-27 10:15:52
|
Hi, > I am having problems with the stupid CVS interface of SF.net. I had a > previous project (multiple even like wxCRP) and I have never had as many > checkout problems as I have now. Basically all that happens is; > > I check out, files are created > Then WinCVS / TCVS hangs. Nothing happens anymore for hours > > The answer from Franchesco (reinstalling windows XP) seems to not solve > this issue as I am not having problems with other SF.net checkouts. well, *I* solved my problems reinstalling winXP but that's was because of a corruption of my installation. I don't understand what can be the cause of your CVS problems; your CVSROOT is set to: :ssh:jo...@cv...:/cvsroot/wxcode ? anyway, if the files are created, you can terminate CVS client using brute force and then work on the files which have been checked-out; isn't it ? > I will investigate further, but now that my 5th day of trying failed, I > lost a bit of my interest in keeping trying. I have more things to do, > and will see when I have the time again. So I am sorry for no updated > source yet. I know that SF also creates nightly CVS tarballs for wxCode at: http://cvs.sourceforge.net/cvstarballs/wxcode-cvsroot.tar.bz2 but I don't know how to use that tarballs (they are some sort of CVS backups which keep trace of all the modifications on all the files of the repository...)... does anyone know ? Francesco |
|
From: Jorgen B. <sol...@xs...> - 2005-07-27 09:46:38
|
>>> also I see that the following components have no source or header files >>> in the CVS, just a "website" folder: >>> >>> treemultictrl -- this was just added two weeks ago IIRC I am having problems with the stupid CVS interface of SF.net. I had a previous project (multiple even like wxCRP) and I have never had as many checkout problems as I have now. Basically all that happens is; I check out, files are created Then WinCVS / TCVS hangs. Nothing happens anymore for hours The answer from Franchesco (reinstalling windows XP) seems to not solve this issue as I am not having problems with other SF.net checkouts. I will investigate further, but now that my 5th day of trying failed, I lost a bit of my interest in keeping trying. I have more things to do, and will see when I have the time again. So I am sorry for no updated source yet. Regards, - Jorgen |
|
From: Francesco M. <f18...@ya...> - 2005-07-27 09:16:02
|
Hi, > I see that you can navigate using the link below the upperleft wxCode > logo, but could you add a link for wxcode logo image to go to > http://wxcode.sf.net. A lot of sites do this, so people are probably > used to it. I looked at the code, (header.inc.php) but with the php > stuff ("{ ?>") I was afraid I'd break it. I'll check back to see how > you did it. no problem, added the link ;-) >>also I see that the following components have no source or header files >>in the CVS, just a "website" folder: >> >>treemultictrl -- this was just added two weeks ago IIRC >>wxbetterdialog -- Brian Allen Vanderburg II (brianvanderburg) >>wxbzipstream * -- Ryan Norton (ryannpcs) >>wxhttpserver -- Ryan Norton (ryannpcs) >>wxlistctrlex -- Blake Madden (blizzymadden) doesn't look familiar >>wxstreammerger -- Ryan Norton (ryannpcs) >> >>* has only a file release >>Maybe these should be really removed ? > > > I know that Ryan is around. How about we just create a list (I don't > know where to store it though) of projects that are unusable. I think > we'll be able to add more. > > There are some others that should go too. > animate is now in wxWidgets/contrib, > styledtextctrl is empty too animate is part of wx contrib but if everyone agree when Robin Dunn gives the okay wx developers will move the contrib folder into wxCode so that we will host not only animate but also the other contrib components... so let's keep animate, by now styledtextctrl folder is empty and thus my CVS clients prune that folder and that's okay since it's the only way to remove a folder from CVS. (i.e. styledtextctrl is already removed from wxCode). > I really won't have time to look too hard for a while now, not until september. Ok; in august I will be on holidays, too ;-) Francesco |
|
From: Ryan N. <wxp...@co...> - 2005-07-26 20:52:18
|
Hi, >> also I see that the following components have no source or header >> files >> in the CVS, just a "website" folder: >> >> treemultictrl -- this was just added two weeks ago IIRC >> wxbetterdialog -- Brian Allen Vanderburg II (brianvanderburg) >> wxbzipstream * -- Ryan Norton (ryannpcs) >> wxhttpserver -- Ryan Norton (ryannpcs) >> wxlistctrlex -- Blake Madden (blizzymadden) doesn't look >> familiar >> wxstreammerger -- Ryan Norton (ryannpcs) >> >> * has only a file release >> Maybe these should be really removed ? > > I know that Ryan is around. How about we just create a list (I don't > know where to store it though) of projects that are unusable. I think > we'll be able to add more. wxhttpserver and wxstreammerger should be removed.... wxzipstream and wxrarinputstream (file releases only I believe) should be added to the website, however. Great work guys... I'll try to take a look at it today along with the new rules. Thanks, RN |
|
From: John L. <jla...@gm...> - 2005-07-26 20:33:25
|
On 7/26/05, Francesco Montorsi <f18...@ya...> wrote: > Hi, > I added the (Want to be the maintainer of this component ?) link in ... > Last, I updated the categories field using the WX guide to the following Looks great. Thanks. I see that you can navigate using the link below the upperleft wxCode logo, but could you add a link for wxcode logo image to go to http://wxcode.sf.net. A lot of sites do this, so people are probably used to it. I looked at the code, (header.inc.php) but with the php stuff ("{ ?>") I was afraid I'd break it. I'll check back to see how you did it. > also I see that the following components have no source or header files > in the CVS, just a "website" folder: >=20 > treemultictrl -- this was just added two weeks ago IIRC > wxbetterdialog -- Brian Allen Vanderburg II (brianvanderburg) > wxbzipstream * -- Ryan Norton (ryannpcs) > wxhttpserver -- Ryan Norton (ryannpcs) > wxlistctrlex -- Blake Madden (blizzymadden) doesn't look familia= r > wxstreammerger -- Ryan Norton (ryannpcs) >=20 > * has only a file release > Maybe these should be really removed ? I know that Ryan is around. How about we just create a list (I don't know where to store it though) of projects that are unusable. I think we'll be able to add more. There are some others that should go too. animate is now in wxWidgets/contrib,=20 styledtextctrl is empty too I really won't have time to look too hard for a while now, not until septem= ber.=20 Regards, John Labenski |
|
From: John L. <jla...@gm...> - 2005-07-26 19:23:21
|
The project has been added as components/wxresizeablecontrol. It
should be available in a few hours after SF updates their end.
Thanks,
John Labenski
On 7/26/05, Francesco Montorsi <fr...@us...> wrote:
> name: wxResizeableControl
> wxversion: 2.4,2.5,2.6
> category:
> language: cpp
> description: This wxWidgets based C++ class provides a user interface for=
child windows placed within other windows. The user can drag them around, =
and resize them using 8 marks drawn on each edge corner of the control. Thi=
s class sends notification events to its parent when the window is created,=
resized, moved or deleted. There are derived classes for displaying pictur=
es in bitmap or (WIN32 only) metafile formats.
> location: wxresizeablecontrol
> cdate: 2003-08-20
> id: 76
> status: stable
> docs: doxygen
> buildsys: bakefile,makefiles
> extdep: none
> wiki: enabled
> wxport: wxmsw,wxgtk
> samples: 1
> approved: 0
> author: Markus Greither
> version: 1.06
> mantainerid: 15
>=20
> Mantainer SF username: magr
> Mantainer name: Markus Greither
> Mantainer mail address: Mar...@ya...
>=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
>
|
|
From: Francesco M. <fr...@us...> - 2005-07-26 19:01:04
|
name: wxResizeableControl wxversion: 2.4,2.5,2.6 category: language: cpp description: This wxWidgets based C++ class provides a user interface for child windows placed within other windows. The user can drag them around, and resize them using 8 marks drawn on each edge corner of the control. This class sends notification events to its parent when the window is created, resized, moved or deleted. There are derived classes for displaying pictures in bitmap or (WIN32 only) metafile formats. location: wxresizeablecontrol cdate: 2003-08-20 id: 76 status: stable docs: doxygen buildsys: bakefile,makefiles extdep: none wiki: enabled wxport: wxmsw,wxgtk samples: 1 approved: 0 author: Markus Greither version: 1.06 mantainerid: 15 Mantainer SF username: magr Mantainer name: Markus Greither Mantainer mail address: Mar...@ya... |
|
From: Francesco M. <f18...@ya...> - 2005-07-26 16:10:52
|
Hi,
I added the (Want to be the maintainer of this component ?) link in
the complist for the unmaintained components... I also changed the
possible choices for the status column to ALPHA, BETA, STABLE removing
the UNMAINTAINED entry so that also unmaintained components can now have
a status set.
This helps to understand which is the status of a unmaintained component...
Last, I updated the categories field using the WX guide to the following
choices: 'managed windows', 'miscellaneous windows', 'common dialogs',
'controls', 'window layout', 'networking', 'stream classes', 'database
classes', 'miscellaneous'...
So please update your component info using the new available categories
or mail me if you would like a new category to be added...
also I see that the following components have no source or header files
in the CVS, just a "website" folder:
treemultictrl
wxbetterdialog
wxbzipstream *
wxhttpserver
wxlistctrlex
wxstreammerger
* has only a file release
Maybe these should be really removed ?
Francesco
Francesco Montorsi wrote:
> 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
>
>
> -------------------------------------------------------
> 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
>
|
|
From: Francesco M. <f18...@ya...> - 2005-07-26 14:29:50
|
Hi, > I think Ryan's idea is best, they can dual licence it if they like, > but one of them has to the wxWindows license. As he pointed out, I > completely missed the ramifications of the BSD license clause and I'm > sure it can get much uglier than that. I've seen quite a few licenses > with catches like, "for commercial use you must merely contact me...". > What if you're not around anymore? The more I think about it, we > should be fairly strict about licensing since it'll only cause > problems later. > > How about the wording below, I think we need a compelling explanation > why we want the wxWindows license and a note about 3rd party libs > since it's bound to come up as a question eventually. > > "Each component must be made available under the wxWindows license. > This is to ensure that there will be no misunderstandings by users of > your code or clashes between components that may rely on each other. > Remember; this code repository is designed to facilitate code reuse. > Small third party libraries that you may include or link with your > component will (of course) maintain their original license and you > should note that in your documentation." ok, that's still okay for me... Francesco |
|
From: John L. <jla...@gm...> - 2005-07-25 21:44:22
|
On 7/25/05, Francesco Montorsi <f18...@ya...> wrote:
> > I think the website has it's own "news" which would suffice, but
> > Francesco would know better. I'll check into this.
> sorry John; I do not understand what you mean... are you saying that you
> prefer a message to wxcode-users mailing list on new releases ?
I didn't realize that the wxcode news *is* the sf news.
=20
> I wrote that any component should use the "wxWidgets" license only
> because wx developers told me that an important point in moving contrib
> stuff to wxCode is that all the sources at wxCode must be easily
> integrable in wxWidgets, eventually.
> So wxWidgets-license should be used for the components that hope to be
> integrated in wx...
> however, I do understand that many other components are not designed to
> be integrated in wx at all ... so using a license different from
> wxWidgets one is okay...
It's not that they'll be integrated into wxWidgets, but that they're usable=
.=20
I think Ryan's idea is best, they can dual licence it if they like,
but one of them has to the wxWindows license. As he pointed out, I
completely missed the ramifications of the BSD license clause and I'm
sure it can get much uglier than that. I've seen quite a few licenses
with catches like, "for commercial use you must merely contact me...".
What if you're not around anymore? The more I think about it, we
should be fairly strict about licensing since it'll only cause
problems later.
How about the wording below, I think we need a compelling explanation
why we want the wxWindows license and a note about 3rd party libs
since it's bound to come up as a question eventually.
"Each component must be made available under the wxWindows license.
This is to ensure that there will be no misunderstandings by users of
your code or clashes between components that may rely on each other.
Remember; this code repository is designed to facilitate code reuse.
Small third party libraries that you may include or link with your
component will (of course) maintain their original license and you
should note that in your documentation."
Regards,
John Labenski
|
|
From: Ryan N. <wxp...@co...> - 2005-07-25 18:35:21
|
Hi, > >>> 8 - I really think this should be something like wxWidgets or >>> something >>> compatable and less restrictive >> This is just to discourage GPL'd stuff. The wording should be >> something like, "a license as or more liberal than the wxWindows >> license." But, we don't want to start flame wars about meaning of the >> word "liberal" or "restrictive". Either that or just list the >> acceptable ones, BSD, MIT, zlib/libpng ... but I think that'd create >> more questions than give answers. >> I just checked here >> (http://www.opensource.org/licenses/wxwindows.php), looking at ones I >> though would work, but it's tough to fully understand them and it'll >> make it unecessarily complicated if it's a free for all. Eventually >> components may start to rely on other components and because of this, >> they need to be compatible. >> Take this one for example, it looks good at first, but has a few >> gotch-ya's, whose rammifictaions are not immediately clear. >> http://www.opensource.org/licenses/artistic-license.php >> How about this: >> "Each component must be submitted under the wxWindows license or a >> license that is compatible and less restrictive, such as the BSD, MIT, >> and zlib/libpng." > Maybe this is the best. > > I wrote that any component should use the "wxWidgets" license only > because wx developers told me that an important point in moving > contrib stuff to wxCode is that all the sources at wxCode must be > easily integrable in wxWidgets, eventually. > So wxWidgets-license should be used for the components that hope to be > integrated in wx... > however, I do understand that many other components are not designed > to be integrated in wx at all ... so using a license different from > wxWidgets one is okay... > > Francesco Or, a different idea - something along the lines of "it must be available under the wxWidgets license"... i.e. give them permission to dual-license it or whatever... that way we don't have to deal with compatability issues etc.. Also remember that the original BSD license had the advertising clause and would be unacceptable Ryan |
|
From: Ulrich T. <Ulr...@gm...> - 2005-07-25 16:54:53
|
Hi, > >>6 - You've already got sourceforge release notes for each update.... > >> you could also give the person news access also to notify sf of > >> thier new release > well, I strongly encourage all wxCode mantainers to use SF news system > to inform others of their updates. I fully agree. After the release of a component a message on SF news reaches all wxCode users through the wxCode website and probably additional SF users. > I think that a mantainer should do: > - a new SF entry > - a message to wxcode-users > - a message to wxusers > when he is releasing its new component... Could this be automated somehow? > >>8 - I really think this should be something like wxWidgets or something > >>compatable and less restrictive > > [...] > > How about this: > > "Each component must be submitted under the wxWindows license or a > > license that is compatible and less restrictive, such as the BSD, MIT, > > and zlib/libpng." > Maybe this is the best. > > I wrote that any component should use the "wxWidgets" license only > because wx developers told me that an important point in moving contrib > stuff to wxCode is that all the sources at wxCode must be easily > integrable in wxWidgets, eventually. > So wxWidgets-license should be used for the components that hope to be > integrated in wx... > however, I do understand that many other components are not designed to > be integrated in wx at all ... so using a license different from > wxWidgets one is okay... In my opinion the components in wxCode should all have the wxWidgets license. This would take from the user of a wxCode component the burden to check several different licenses whether they allow the planned use or not. AFAIK the wxWidgets license is very liberal and allows commercial use. What more is needed? Maybe a developer could license his component under several licenses? Ulrich Telle -- E-Mail privat: Ulr...@gm... E-Mail Studium: Ulr...@Fe... World Wide Web: http://www.stud.fernuni-hagen.de/q1471341 |
|
From: Francesco M. <f18...@ya...> - 2005-07-25 15:50:54
|
Hi, >>6 - You've already got sourceforge release notes for each update.... you >>could also give the person news access also to notify sf of thier new >>release well, I strongly encourage all wxCode mantainers to use SF news system to inform others of their updates. Currently, you'll see that Ulrich Telle has already folled my advice (see wxSQLite3 v1.0 released news)... however, that should be written in the wxCode maintainer guide; I'll try to write all the missing FAQ entries and TODO items of the wxCode website in this weekend... > This is just a suggestion, I think a small note to the wx-code mailing > list would go a long way to generate interest. It's more inviting to > respond to a message *from the author* to ask about a project than > start your own new thread not knowing if the author is even checking > the list. > > I think the website has it's own "news" which would suffice, but > Francesco would know better. I'll check into this. sorry John; I do not understand what you mean... are you saying that you prefer a message to wxcode-users mailing list on new releases ? I think that a mantainer should do: - a new SF entry - a message to wxcode-users - a message to wxusers when he is releasing its new component... >>8 - I really think this should be something like wxWidgets or something >>compatable and less restrictive > > > This is just to discourage GPL'd stuff. The wording should be > something like, "a license as or more liberal than the wxWindows > license." But, we don't want to start flame wars about meaning of the > word "liberal" or "restrictive". Either that or just list the > acceptable ones, BSD, MIT, zlib/libpng ... but I think that'd create > more questions than give answers. > > I just checked here > (http://www.opensource.org/licenses/wxwindows.php), looking at ones I > though would work, but it's tough to fully understand them and it'll > make it unecessarily complicated if it's a free for all. Eventually > components may start to rely on other components and because of this, > they need to be compatible. > > Take this one for example, it looks good at first, but has a few > gotch-ya's, whose rammifictaions are not immediately clear. > http://www.opensource.org/licenses/artistic-license.php > > How about this: > "Each component must be submitted under the wxWindows license or a > license that is compatible and less restrictive, such as the BSD, MIT, > and zlib/libpng." Maybe this is the best. I wrote that any component should use the "wxWidgets" license only because wx developers told me that an important point in moving contrib stuff to wxCode is that all the sources at wxCode must be easily integrable in wxWidgets, eventually. So wxWidgets-license should be used for the components that hope to be integrated in wx... however, I do understand that many other components are not designed to be integrated in wx at all ... so using a license different from wxWidgets one is okay... Francesco |
|
From: Francesco M. <f18...@ya...> - 2005-07-25 15:43:03
|
Hi, >>What's this about a monthly status report? > > > I don't think a status report is necessary, I have removed this rule > and tried to appeal to people's better judgement. Do these "rules" > sound a little more reasonable? The idea was that if wxCode is to be > successful, the components have to be updated and not collect dust. > > http://wxcode.sourceforge.net/rules.php Maybe you're right; a monthly status report would be a rule to strict to be respected... I wrote that rules in a hurry when I restyled the site... I found John corrections very good; thanks ! Francesco |
|
From: John L. <jla...@gm...> - 2005-07-24 16:02:05
|
On 7/24/05, Ryan Norton <wxp...@co...> wrote: > Hi John, > Thanks for updating those... some comments... >=20 > 6 - You've already got sourceforge release notes for each update.... you > could also give the person news access also to notify sf of thier new > release This is just a suggestion, I think a small note to the wx-code mailing list would go a long way to generate interest. It's more inviting to respond to a message *from the author* to ask about a project than start your own new thread not knowing if the author is even checking the list. I think the website has it's own "news" which would suffice, but Francesco would know better. I'll check into this. =20 > 8 - I really think this should be something like wxWidgets or something > compatable and less restrictive This is just to discourage GPL'd stuff. The wording should be something like, "a license as or more liberal than the wxWindows license." But, we don't want to start flame wars about meaning of the word "liberal" or "restrictive". Either that or just list the acceptable ones, BSD, MIT, zlib/libpng ... but I think that'd create more questions than give answers. I just checked here (http://www.opensource.org/licenses/wxwindows.php), looking at ones I though would work, but it's tough to fully understand them and it'll make it unecessarily complicated if it's a free for all. Eventually components may start to rely on other components and because of this, they need to be compatible. Take this one for example, it looks good at first, but has a few gotch-ya's, whose rammifictaions are not immediately clear. http://www.opensource.org/licenses/artistic-license.php How about this: "Each component must be submitted under the wxWindows license or a license that is compatible and less restrictive, such as the BSD, MIT, and zlib/libpng." Regards, John Labenski |
|
From: Ryan N. <wxp...@co...> - 2005-07-24 09:45:22
|
Hi John, Thanks for updating those... some comments... 6 - You've already got sourceforge release notes for each update.... you could also give the person news access also to notify sf of thier new release 8 - I really think this should be something like wxWidgets or something compatable and less restrictive Ryan |
|
From: John L. <jla...@gm...> - 2005-07-24 07:34:27
|
On 7/23/05, Ryan Norton <wxp...@co...> wrote: > Sorry for not following recent developments here (I think I was the aroun= d > the 5th registered wxCode dev), but someone at the forum raised an > interesting question- > http://www.solidsteel.nl/users/wxwidgets/viewtopic.php?p=3D13677#13677 >=20 > What's this about a monthly status report? I don't think a status report is necessary, I have removed this rule and tried to appeal to people's better judgement. Do these "rules" sound a little more reasonable? The idea was that if wxCode is to be successful, the components have to be updated and not collect dust. http://wxcode.sourceforge.net/rules.php Regards, John Labenski |
|
From: Ryan N. <wxp...@co...> - 2005-07-24 02:11:55
|
Hi, Sorry for not following recent developments here (I think I was the around the 5th registered wxCode dev), but someone at the forum raised an interesting question- http://www.solidsteel.nl/users/wxwidgets/viewtopic.php?p=13677#13677 What's this about a monthly status report? Ryan |
6 messages has been excluded from this view by a project administrator.
