wxcode-users

[wxCode-users] New component list

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

Hi,
   I would like to make some improvements to the Components listing page of the wxCode 
website.
It's the most important page in the website and since the number of components is becoming
bigger and bigger, a better complist page is required to the let the user find quickly 
what's he's searching for.

In particular, for some reasons I explain below, I would like to keep only the current 
view options:

-> BROWSE BY "name" or "category"
-> COMPONENTS PER PAGE "10" or "-1" (all)

Reducing the possible view options would make simpler a powerful approach to the component 
listing which is what I would like to implement: the key are the page links currently 
shown as:

        << Previous | Page 1 | Page 2 | ... | Next >>

I would like to make these links in the following form, when browsing by category:

        Networking (12): 1 2 | Managed windows (2): 1 | Controls (30): 1 2 3 | ...

where the () parentheses indicates the number of components per category and the numbers 
after the ":" are the links to the paged list.

When browsing by name:

        A (5): 1 | B (12): 1 2 | C (3): 1 | ...

To make such page links, however, a lot of queries to the database would be required
(for browsebyname links, more than 26 !) since they provide much more info to the user
(in particular they will make the 'browse by category' option *much* more useful).
SourceForge servers cannot really handle such a traffic.
So I think that we can get all these "advanced page links" only using a little trick:
precalculating the page links and saving them in some files in the website folder.

Even if this precalculation would be done by a script, we must limit the number of view 
options in order to make the XHTML pages to precalculate as few as possible: with the view 
options I wrote above, we would need to recalc 4 pages (2 x 2).

Such "precalculation" script would have to be launched each time we add/remove a 
component, each time we change the category of a component and any time we change the name 
of a component.
This won't be a great issue, I hope. In fact, we could also avoid to manually call the 
script on these database changes and just put the script in a cron table.

If noone objects, then I will start making these changes (sorry but this means that for 
some hours the complist page won't work completely).

If someone wants to give suggestions, I'm open to any costructive critic ;)

Francesco

Re: [wxCode-users] New component list

[Jorgen B. <sol...@xs...>]

This sounds very good! I like a categoric approach. As long as the 
categories makes it easy to find controls. What do you mean with managed 
controls? Maybe it is an idea to get the following categories:

- Edit controls (spin controls, text edit)
- Layout / Container controls (controls that can contain other controls)
- Non visual networking
- Non visial misc

Thanks for your effort in the site!
- Jorgen

Re: [wxCode-users] New component list

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

Hi,

Jorgen Bodde wrote:
> This sounds very good! I like a categoric approach. As long as the 
> categories makes it easy to find controls. What do you mean with managed 
> controls?
When I wrote the string

Networking (12): 1 2 | Managed windows (2): 1 | Controls (30): 1 2 3 | ...

I was just thinking to the categories I put in the database... I took them from the 
wxWidgets documentation page "classes by category": as you can see the first section is 
"managed windows", then "misc windows", etc.

> Maybe it is an idea to get the following categories:
> 
> - Edit controls (spin controls, text edit)
> - Layout / Container controls (controls that can contain other controls)
> - Non visual networking
> - Non visial misc
At first I took a similar approach creating some categories like these but then I thought: 
maybe using wxWidgets documentation categories is better since our components are based on 
wx and maybe that in future some of them will be integrated directly into wx itself.

The current categories are:

'managed windows', 'miscellaneous windows', 'common dialogs', 'controls', 'window layout', 
'networking', 'stream classes', 'database classes', 'miscellaneous', 'utilities', 
'tutorials/wxdocs'

Unfortunately I see that I completely forgot to update the "category" listbox in the EDIT 
page of the website :(

Before repairing that I'd like to decide definitevely the main categories that the DB must 
support (in future others categories can be added to the DB without problems).

So, do you think it's best to stick to wx categories I listed above (maybe adding some new 
entry) or we should use another different set of categories ?

> Thanks for your effort in the site!
> - Jorgen
Thanks to all people submitting their code to wxCode ! ;)

Francesco

Re: [wxCode-users] New component list

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

I would like to start now with new component list; I tested the links creator scripts and 
you can see the results at (for example):

http://wxcode.sourceforge.net/complinks_category_partial.inc.html

If you have any objection/comment/suggestion, please do it now,
FM


Francesco Montorsi wrote:
> Hi,
> 
> Jorgen Bodde wrote:
> 
>> This sounds very good! I like a categoric approach. As long as the 
>> categories makes it easy to find controls. What do you mean with 
>> managed controls?
> 
> When I wrote the string
> 
> Networking (12): 1 2 | Managed windows (2): 1 | Controls (30): 1 2 3 | ...
> 
> I was just thinking to the categories I put in the database... I took 
> them from the wxWidgets documentation page "classes by category": as you 
> can see the first section is "managed windows", then "misc windows", etc.
> 
>> Maybe it is an idea to get the following categories:
>>
>> - Edit controls (spin controls, text edit)
>> - Layout / Container controls (controls that can contain other controls)
>> - Non visual networking
>> - Non visial misc
> 
> At first I took a similar approach creating some categories like these 
> but then I thought: maybe using wxWidgets documentation categories is 
> better since our components are based on wx and maybe that in future 
> some of them will be integrated directly into wx itself.
> 
> The current categories are:
> 
> 'managed windows', 'miscellaneous windows', 'common dialogs', 
> 'controls', 'window layout', 'networking', 'stream classes', 'database 
> classes', 'miscellaneous', 'utilities', 'tutorials/wxdocs'
> 
> Unfortunately I see that I completely forgot to update the "category" 
> listbox in the EDIT page of the website :(
> 
> Before repairing that I'd like to decide definitevely the main 
> categories that the DB must support (in future others categories can be 
> added to the DB without problems).
> 
> So, do you think it's best to stick to wx categories I listed above 
> (maybe adding some new entry) or we should use another different set of 
> categories ?
> 
>> Thanks for your effort in the site!
>> - Jorgen
> 
> Thanks to all people submitting their code to wxCode ! ;)
> 
> 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...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
> 

Re: [wxCode-users] New component list

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

Hi,

    just an aesthetical doubt: should we use change the view options (look at the 
component list at the top) to use radio buttons instead of listboxes ?

the viewmodes, browseby and # of comp contain only two choices... what's your advice ?

Francesco


Francesco Montorsi wrote:
> I would like to start now with new component list; I tested the links 
> creator scripts and you can see the results at (for example):
> 
> http://wxcode.sourceforge.net/complinks_category_partial.inc.html
> 
> If you have any objection/comment/suggestion, please do it now,
> FM
> 
> 
> Francesco Montorsi wrote:
> 
>> Hi,
>>
>> Jorgen Bodde wrote:
>>
>>> This sounds very good! I like a categoric approach. As long as the 
>>> categories makes it easy to find controls. What do you mean with 
>>> managed controls?
>>
>>
>> When I wrote the string
>>
>> Networking (12): 1 2 | Managed windows (2): 1 | Controls (30): 1 2 3 | 
>> ...
>>
>> I was just thinking to the categories I put in the database... I took 
>> them from the wxWidgets documentation page "classes by category": as 
>> you can see the first section is "managed windows", then "misc 
>> windows", etc.
>>
>>> Maybe it is an idea to get the following categories:
>>>
>>> - Edit controls (spin controls, text edit)
>>> - Layout / Container controls (controls that can contain other controls)
>>> - Non visual networking
>>> - Non visial misc
>>
>>
>> At first I took a similar approach creating some categories like these 
>> but then I thought: maybe using wxWidgets documentation categories is 
>> better since our components are based on wx and maybe that in future 
>> some of them will be integrated directly into wx itself.
>>
>> The current categories are:
>>
>> 'managed windows', 'miscellaneous windows', 'common dialogs', 
>> 'controls', 'window layout', 'networking', 'stream classes', 'database 
>> classes', 'miscellaneous', 'utilities', 'tutorials/wxdocs'
>>
>> Unfortunately I see that I completely forgot to update the "category" 
>> listbox in the EDIT page of the website :(
>>
>> Before repairing that I'd like to decide definitevely the main 
>> categories that the DB must support (in future others categories can 
>> be added to the DB without problems).
>>
>> So, do you think it's best to stick to wx categories I listed above 
>> (maybe adding some new entry) or we should use another different set 
>> of categories ?
>>
>>> Thanks for your effort in the site!
>>> - Jorgen
>>
>>
>> Thanks to all people submitting their code to wxCode ! ;)
>>
>> 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...
>> 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
> 

Re: [wxCode-users] New component list

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

On 9/3/05, Francesco Montorsi <f18...@ya...> wrote:
>     just an aesthetical doubt: should we use change the view options (loo=
k at the
> component list at the top) to use radio buttons instead of listboxes ?
>=20
> the viewmodes, browseby and # of comp contain only two choices... what's =
your advice ?

Whatever is easier, I looks ok to me.

-John Labenski