Menu
▾
▴
wxcode-users
|
From: Francesco M. <f18...@ya...> - 2005-09-01 19:55:24
|
Hi all,
I was thinking that the new component list page will probably look like:
A (2): 1 | B(1): 1 | ... | W (40): 1 2 3 4 | ...
that is, since almost all component's names start by 'wx' the "W" initial will
be "abused".
Also: it's obvious that at wxCode we have only components wx-based;
so, why should we name all the components with "wx" prefix ?
So, I suggest to solve this problem removing the "wx" prefix by all
component names from wxCode database
(this would not require any change to CVS).
Then I could modify the scripts so that they show the component name with a "wx" prefix
automatically attached. This would mean that all components at wxCode have a name which
starts (at least in the component list page) by "wx"... is it okay ?
I have some components which do not have wx prefix and there is no problem at all for me
to add "wx" prefix to them. Please post your opinion if you wouldn't like this change.
Another solution would be to tell to the database to ignore the
"wx" prefix. Unfortunately AFAIK there's no way to tell this to
a database through an SQL query... anyone knows ?
Francesco
|
|
From: Angelo's G. <ama...@gm...> - 2005-09-01 22:38:12
|
I was not clear if the wx should prefix the name of the component or not. M= y=20 vote is for remoing the wx from the prefix of the component names. --Angelo On 9/1/05, Francesco Montorsi <f18...@ya...> wrote: >=20 > Hi all, > I was thinking that the new component list page will probably look like: >=20 > A (2): 1 | B(1): 1 | ... | W (40): 1 2 3 4 | ... >=20 > that is, since almost all component's names start by 'wx' the "W" initial= =20 > will > be "abused". >=20 > Also: it's obvious that at wxCode we have only components wx-based; > so, why should we name all the components with "wx" prefix ? >=20 > So, I suggest to solve this problem removing the "wx" prefix by all > component names from wxCode database > (this would not require any change to CVS). >=20 > Then I could modify the scripts so that they show the component name with= =20 > a "wx" prefix > automatically attached. This would mean that all components at wxCode hav= e=20 > a name which > starts (at least in the component list page) by "wx"... is it okay ? > I have some components which do not have wx prefix and there is no proble= m=20 > at all for me > to add "wx" prefix to them. Please post your opinion if you wouldn't like= =20 > this change. >=20 > Another solution would be to tell to the database to ignore the > "wx" prefix. Unfortunately AFAIK there's no way to tell this to > a database through an SQL query... anyone knows ? >=20 > Francesco >=20 >=20 > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle=20 > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q= A > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users > |
|
From: Francesco M. <f18...@ya...> - 2005-09-02 08:43:59
|
Hi, Angelo's Gmail wrote: > I was not clear if the wx should prefix the name of the component or > not. My vote is for remoing the wx from the prefix of the component names. good, we have a +1; what about other developers ? Francesco > On 9/1/05, *Francesco Montorsi* <f18...@ya... > <mailto:f18...@ya...>> wrote: > > Hi all, > I was thinking that the new component list page will probably > look like: > > A (2): 1 | B(1): 1 | ... | W (40): 1 2 3 4 | ... > > that is, since almost all component's names start by 'wx' the "W" > initial will > be "abused". > > Also: it's obvious that at wxCode we have only components wx-based; > so, why should we name all the components with "wx" prefix ? > > So, I suggest to solve this problem removing the "wx" prefix by all > component names from wxCode database > (this would not require any change to CVS). > > Then I could modify the scripts so that they show the component name > with a "wx" prefix > automatically attached. This would mean that all components at > wxCode have a name which > starts (at least in the component list page) by "wx"... is it okay ? > I have some components which do not have wx prefix and there is no > problem at all for me > to add "wx" prefix to them. Please post your opinion if you wouldn't > like this change. > > Another solution would be to tell to the database to ignore the > "wx" prefix. Unfortunately AFAIK there's no way to tell this to > a database through an SQL query... anyone knows ? > > Francesco > > > ------------------------------------------------------- > 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... > <mailto:wxC...@li...> > https://lists.sourceforge.net/lists/listinfo/wxcode-users > > |
|
From: Jorgen B. <sol...@xs...> - 2005-09-02 11:18:20
|
Yeah I agree. But, the example you showed was a bit biased towards one type of component, and still not very useful in it's current state: Managed windows (5): 1 | Miscellaneous windows (2): 1 | Controls (1): 1 | Window layout (2): 1 | Stream classes (4): 1 | Miscellaneous (26): 1 2 3 | Tutorials/wxdocs (1): 1 Misc has 26 entries, maybe there is still a more granular category splitting needed? Regards, - Jorgen Francesco Montorsi wrote: > Hi, > > Angelo's Gmail wrote: > >> I was not clear if the wx should prefix the name of the component or >> not. My vote is for remoing the wx from the prefix of the component >> names. > > good, we have a +1; what about other developers ? > > Francesco > > > >> On 9/1/05, *Francesco Montorsi* <f18...@ya... >> <mailto:f18...@ya...>> wrote: >> >> Hi all, >> I was thinking that the new component list page will probably >> look like: >> >> A (2): 1 | B(1): 1 | ... | W (40): 1 2 3 4 | ... >> >> that is, since almost all component's names start by 'wx' the "W" >> initial will >> be "abused". >> >> Also: it's obvious that at wxCode we have only components wx-based; >> so, why should we name all the components with "wx" prefix ? >> >> So, I suggest to solve this problem removing the "wx" prefix by all >> component names from wxCode database >> (this would not require any change to CVS). >> >> Then I could modify the scripts so that they show the component name >> with a "wx" prefix >> automatically attached. This would mean that all components at >> wxCode have a name which >> starts (at least in the component list page) by "wx"... is it okay ? >> I have some components which do not have wx prefix and there is no >> problem at all for me >> to add "wx" prefix to them. Please post your opinion if you wouldn't >> like this change. >> >> Another solution would be to tell to the database to ignore the >> "wx" prefix. Unfortunately AFAIK there's no way to tell this to >> a database through an SQL query... anyone knows ? >> >> Francesco >> >> >> ------------------------------------------------------- >> 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... >> <mailto: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: Francesco M. <f18...@ya...> - 2005-09-02 14:28:36
|
Hi, Jorgen Bodde wrote: > Yeah I agree. you mean that you agree on removing wx from comp names ? >But, the example you showed was a bit biased towards one > type of component, and still not very useful in it's current state: > > Managed windows (5): 1 | Miscellaneous windows (2): 1 | Controls (1): > 1 | Window layout (2): 1 | Stream classes (4): 1 | Miscellaneous > (26): 1 2 3 | Tutorials/wxdocs (1): 1 > > Misc has 26 entries, maybe there is still a more granular category > splitting needed? the sample above is for categorized view while removing wx from comp name is to give a better look to the browse-by-name list... also the problem of having so many components in "miscellaneous" is because almost no maintainer did set the right category for its components. The EDIT form needs some revision to make this work and I'm currently busy with the new component list; I'll let you know when you can adjust your components' categories. After everyone classifies his components I think we will get something much more equilibrated. Anyway I'm open to any new category proposal (see my previous mails for current list of categories). Francesco > > Regards, > - Jorgen > > Francesco Montorsi wrote: > >> Hi, >> >> Angelo's Gmail wrote: >> >>> I was not clear if the wx should prefix the name of the component or >>> not. My vote is for remoing the wx from the prefix of the component >>> names. >> >> >> good, we have a +1; what about other developers ? >> >> Francesco >> >> >> >>> On 9/1/05, *Francesco Montorsi* <f18...@ya... >>> <mailto:f18...@ya...>> wrote: >>> >>> Hi all, >>> I was thinking that the new component list page will probably >>> look like: >>> >>> A (2): 1 | B(1): 1 | ... | W (40): 1 2 3 4 | ... >>> >>> that is, since almost all component's names start by 'wx' the "W" >>> initial will >>> be "abused". >>> >>> Also: it's obvious that at wxCode we have only components wx-based; >>> so, why should we name all the components with "wx" prefix ? >>> >>> So, I suggest to solve this problem removing the "wx" prefix by all >>> component names from wxCode database >>> (this would not require any change to CVS). >>> >>> Then I could modify the scripts so that they show the component name >>> with a "wx" prefix >>> automatically attached. This would mean that all components at >>> wxCode have a name which >>> starts (at least in the component list page) by "wx"... is it okay ? >>> I have some components which do not have wx prefix and there is no >>> problem at all for me >>> to add "wx" prefix to them. Please post your opinion if you wouldn't >>> like this change. >>> >>> Another solution would be to tell to the database to ignore the >>> "wx" prefix. Unfortunately AFAIK there's no way to tell this to >>> a database through an SQL query... anyone knows ? >>> >>> Francesco >>> >>> >>> ------------------------------------------------------- >>> 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... >>> <mailto: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 >> >> > > > ------------------------------------------------------- > 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: cecilio <s.c...@gm...> - 2005-09-02 18:12:43
|
Hi, > >>> So, I suggest to solve this problem removing the "wx" prefix by a= ll > >>> component names from wxCode database > >>> (this would not require any change to CVS). > >>> > >>> Then I could modify the scripts so that they show the component n= ame > >>> with a "wx" prefix > >>> automatically attached. This would mean that all components at > >>> wxCode have a name which > >>> starts (at least in the component list page) by "wx"... is it oka= y ? I am not sure what are the implications of your proposal. I wouldn't like to rename all folders and programs just to remove the 'wx' so that the statistic looks nice at the cost of having to add 'wx' again to files, includes, etc. to prepare a package for distribution and package.. Perhaps, it would be simpler to ignore the wx in the index compilation. For example, components starting by 'A' or 'wxA' are indexed in letter 'A', and so on. Could you, please, detail more your proposal? |
|
From: Francesco M. <f18...@ya...> - 2005-09-02 19:29:22
|
Hi, >>>>> So, I suggest to solve this problem removing the "wx" prefix by all >>>>> component names from wxCode database >>>>> (this would not require any change to CVS). >>>>> >>>>> Then I could modify the scripts so that they show the component name >>>>> with a "wx" prefix >>>>> automatically attached. This would mean that all components at >>>>> wxCode have a name which >>>>> starts (at least in the component list page) by "wx"... is it okay ? > > > I am not sure what are the implications of your proposal. I wouldn't > like to rename > all folders and programs just to remove the 'wx' so that the statistic > looks nice at the cost of having to add 'wx' again to files, includes, > etc. to prepare a package for distribution and package.. that would not be required; I mean that the "wx" should be removed from the name registered in the wxCode database. As i said in previous mails, no changes would be required to CVS. > Perhaps, it would be simpler to ignore the wx in the index > compilation. For example, components starting by 'A' or 'wxA' are > indexed in letter 'A', and so on. thinking better to this approach I think that the following should do the "ignore wx prefix" logic: SELECT * FROM components WHERE (name LIKE 'a%' OR name LIKE 'wxa%') just I'm not so expert to evaluate the performance impact of such additional OR ... statements but I think it would be acceptable. Francesco |
|
From: Ulrich T. <Ulr...@gm...> - 2005-09-02 18:22:02
|
> Perhaps, it would be simpler to ignore the wx in the index compilation. > For example, components starting by 'A' or 'wxA' are indexed in letter > 'A', and so on. I think this is a very good proposal. Regards, Ulrich -- E-Mail privat: Ulr...@gm... E-Mail Studium: Ulr...@Fe... World Wide Web: http://www.stud.fernuni-hagen.de/q1471341 |
|
From: Otto W. <ott...@or...> - 2005-09-03 10:27:07
|
Francesco Montorsi wrote: > > Hi all, > I was thinking that the new component list page will probably look like: > > A (2): 1 | B(1): 1 | ... | W (40): 1 2 3 4 | ... > > that is, since almost all component's names start by 'wx' the "W" initial will > be "abused". > I thought so too but I'd also like to see the full name as the component is (e.g. wxTreeListCtrl). Would it be possible to strip the "wx" just for the sorting into pages but still show the name including "wx"? BTW can't the "single table" mode be a single table without pages? I like it most since it resembles the old components lists. And could the link on the name go the the component view (e.g. http://wxcode.sourceforge.net/showcomp.php?name=wxScintilla) instead of the component directory? O. Wyss -- Development of frame buffer drivers: http://linux-fbdev.sf.net Sample code snippets for wxWidgets: http://wxcode.sf.net How to build well-designed applications: http://wyoguide.sf.net Desktop with a consistent look and feel: http://wyodesktop.sf.net |
|
From: Francesco M. <f18...@ya...> - 2005-09-03 10:38:22
|
Hi, >> I was thinking that the new component list page will probably look like: >> >>A (2): 1 | B(1): 1 | ... | W (40): 1 2 3 4 | ... >> >>that is, since almost all component's names start by 'wx' the "W" initial will >>be "abused". > > I thought so too but I'd also like to see the full name as the component > is (e.g. wxTreeListCtrl). Would it be possible to strip the "wx" just > for the sorting into pages but still show the name including "wx"? this is an extract from another mail on the thread: >> Perhaps, it would be simpler to ignore the wx in the index >> compilation. For example, components starting by 'A' or 'wxA' are >> indexed in letter 'A', and so on. > >thinking better to this approach I think that the following should do the "ignore wx >prefix" logic: > >SELECT * FROM components WHERE (name LIKE 'a%' OR name LIKE 'wxa%') > >just I'm not so expert to evaluate the performance impact of such additional OR ... >statements but I think it would be acceptable. I think ignoring "wx" is the best choice... as you and others suggest. > BTW can't the "single table" mode be a single table without pages? I > like it most since it resembles the old components lists. would this still be useful ? I mean: we have a *lot* of components (> 50); putting them all into a single page would be stressing for the server and maybe not very useful... anyway if you find it useful I can try to implement that. > And could the > link on the name go the the component view (e.g. > http://wxcode.sourceforge.net/showcomp.php?name=wxScintilla) instead of > the component directory? yes, that's probably best than linking to the (sometimes missing) component website. I'm working on the website right now; I'm converting the PHP code which I wrote in a C-like syntax (with lot of globals, etc) into a C++-like syntax (using PHP class objects). This will make the website much more easier to mantain, I hope. At beginning, when creating the site I thought that was an overkill but now I changed idea :) Francesco |
|
From: Otto W. <ott...@or...> - 2005-09-03 10:52:58
|
Francesco Montorsi wrote: > > > BTW can't the "single table" mode be a single table without pages? I > > like it most since it resembles the old components lists. > would this still be useful ? > I mean: we have a *lot* of components (> 50); putting them all into a single page would be > stressing for the server and maybe not very useful... > anyway if you find it useful I can try to implement that. > For the database it shouldn't be a problem and since the layout is much simpler for "single table" it probably also okay for the webserver. The transfer to the user of course will be longer but then anyone could switch to the full view. O. Wyss -- Development of frame buffer drivers: http://linux-fbdev.sf.net Sample code snippets for wxWidgets: http://wxcode.sf.net How to build well-designed applications: http://wyoguide.sf.net Desktop with a consistent look and feel: http://wyodesktop.sf.net |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X