From: Francesco <fr...@us...> - 2005-07-13 19:01:04
|
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 the same basic interface. However, the underlying functionality is a complete 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 |
From: Francesco M. <f18...@ya...> - 2005-07-13 19:41:26
|
approved & updated the DB... John or Otto will update the CVSROOT\avail file to give you CVS access as soon as possible... FM 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 the same basic interface. However, the underlying functionality is a complete 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 > > > > ------------------------------------------------------- > 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 > |
From: John L. <jla...@gm...> - 2005-07-13 20:17:02
|
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 |
From: Francesco M. <f18...@ya...> - 2005-07-13 20:29:57
|
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 |
From: John L. <jla...@gm...> - 2005-07-13 20:56:39
|
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 |
From: Francesco M. <f18...@ya...> - 2005-07-13 21:14:23
|
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 |