wxcode-users

[wxCode-users] Active maintenance

[Otto W. <ott...@or...>]

Since it's important for a user of wxCode to know if a component is
actively maintained I have to know if the current maintainer is still
taking care. The easiest way is if any maintainer sends a status report
to the wxcode-users list every halve year. So please send a message for
each component you still care for to the list until the end of June.
Please name the components in the subject. Any component I don't get a
status report will have the maintainer name on the component list
removed and is open for other developers to take over as a maintainer.

This status report might be the right time to update a component to the
latest development point. Also don't forget to upload an image.png
(160x120px) to your components website.

I've slightly changed the meaning of the wxWidgets field in the
component list, the first means the oldest usable version, der second
the last tested version. This gives a better idea how well a component
might work with a given wxWidgets release.

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

Re: [wxCode-users] Active maintenance for paletteframe, wxxml2, keybinder, wxscript

[f18m_217828 <f18...@ya...>]

Hi,

Otto Wyss wrote:
> Since it's important for a user of wxCode to know if a component is
> actively maintained I have to know if the current maintainer is still
> taking care. The easiest way is if any maintainer sends a status report
> to the wxcode-users list every halve year.
I agree; it's important to have some kind of "quality & development" 
check on the components

> So please send a message for
> each component you still care for to the list until the end of June.
> Please name the components in the subject.
I'm currently mantaining actively the following wxcode components:
- paletteframe
- wxxml2
- keybinder
- wxscript
and also wxcode bakefile build system.

As status report I could say that all the components are fully working 
with any wx version from 2.5.x to 2.6.x and they have no open bugs 
except for wxscript.

> This status report might be the right time to update a component to the
> latest development point. Also don't forget to upload an image.png
> (160x120px) to your components website.
I really appreciate this option but as said in some previous mail in wx, 
I suggest to make a wxcode site restyling maybe looking for example to 
the 'bluehaze' open source web design at  http://www.oswd.org/
You can see that theme in action at http://bakefile.sourceforge.net/
I managed to obtain some good-quality web pages (XHTML 1.1 & CSS 2 
conformant) and all with the same headers & footers just using a nice 
XSLT template...


However, I'll try to make some nice image for my components ASAP (very 
busy with studies, now) because that is required for a good presentation.


> I've slightly changed the meaning of the wxWidgets field in the
> component list, the first means the oldest usable version, der second
> the last tested version. This gives a better idea how well a component
> might work with a given wxWidgets release.
will give a look later...

Francesco Montorsi

[wxCode-users] Re: Active maintenance

[Joseph B. <jb...@um...>]

I'm still the maintainer on the wxSpellChecker and ShortcutPanel 
components.  I did a little work on wxSpellChecker to get it up to 
wxWidgets 2.5.5 and Aspell 0.60.2, but unfortunately I haven't done much 
with ShortcutPanel since Jonatan Magnusson allowed me to post the 
component.  It's worked so well that it hasn't needed changes.


On Thu, 16 Jun 2005, Otto Wyss wrote:

> Since it's important for a user of wxCode to know if a component is
> actively maintained I have to know if the current maintainer is still
> taking care. The easiest way is if any maintainer sends a status report
> to the wxcode-users list every halve year. So please send a message for
> each component you still care for to the list until the end of June.
> Please name the components in the subject. Any component I don't get a
> status report will have the maintainer name on the component list
> removed and is open for other developers to take over as a maintainer.
>
> This status report might be the right time to update a component to the
> latest development point. Also don't forget to upload an image.png
> (160x120px) to your components website.
>
> I've slightly changed the meaning of the wxWidgets field in the
> component list, the first means the oldest usable version, der second
> the last tested version. This gives a better idea how well a component
> might work with a given wxWidgets release.
>
> 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
>
>
>