Re: [wxCode-users] wxCode categories

[Ulrich T. <Ulr...@gm...>]

Hi,

> Ok; I've implemented this feature and now there is an additional
> component field called "category2" which can be set by the EDIT &
> compsubmit forms. 

In principle it is good to have the possibility to add a second 
category to a component. But in case a component belongs to exactly 
_one_ category the category2 field should be unassigned. As it is 
implemented now, one has two options:

1) select the same category for category1 and category2
2) select miscelleaneous for category2 (which would be definitely 
misleading)

I think a choice of "not applicable" would be necessary for category2.

> complist in name mode now that I have implemented the "ignore wx
> prefix" logic is much more usable.

Yes that's definitely true.

> however, the complist is quite useless when browsed in "category" mode
> since all categories must be set to their right values. 

Sure. But until now it wasn't possible to edit the category field. So 
as soon as the list of categories is fixed, the maintainers should be 
informed and each maintainer should then update the component entry.

> John and I discussed to change them to:
> 
> 'window containers', 'dialogs', 'controls', 'window layout',
> 'networking', 'stream classes', 'database classes', 'miscellaneous',
> 'utilities', 'tutorials/wxdocs' , 'data container' 

In my opinion we should try to avoid categories like ''miscellaneous' 
or 'utilities'.

Instead of 'utilities' I would propose 'stand alone applications' - 
although it does not say much about the purpose of the component it 
makes clear that it's a complete program and not a library. To the 
component "WebUpdate" one would probably then assign the categories 
'networking' and 'stand alone'.

In the case of 'miscellaneous' the matter is more complex. For how many 
and which components none of the other categories are suitable? The 
list of these components should be analyzed and then appropriate 
additional categories should be introduced. I would propose to add a 
category "unassigned". This would be a signal to the administrator(s) 
of wxCode that maybe a new category has to be created. The issue could 
be discussed with the maintainer of the component and the wxCode users, 
whether the 'unassigned' component matches one of the existing 
categories or a new one has to be created.

Regards,

Ulrich

P.S.: There are still problems with the display of component's web 
page. The website of my component wxSQLite3 is shown, the one of my 
component wxPdfDocument is not. Another issue is the link to the 
documentation. Currently a directory listing is shown. This should be 
configured in such a way that the page 'index.html' is shown.

P.P.S.: For my new component wxPdfDocument I don't have screenshots, 
but I would like to show some example PDF documents. How should I 
handle this?

P.P.P.S: I'd like to make two or three third party add-ons available 
for my component wxPdfDocument, but I don't think these should be 
included in CVS, since they are mostly binary resources. Should I make 
file releases for these add-ons within wxCode or should I only include 
links on the component's website where these add-ons can be found on 
the web?
-- 
E-Mail privat:  Ulr...@gm...
E-Mail Studium: Ulr...@Fe...
World Wide Web: http://www.stud.fernuni-hagen.de/q1471341