wxcode-users — Submission, Questions, Information

[wxCode-users] New autoconf build support

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

Hi all,

    I would like to inform everyone that I finally managed to create a good way to support 
"autoconf" format, too with wxCode bakefiles.
The new configure.ac for a wxCode component looks like:


AC_INIT([wxXml2], [1.5], [fr...@so...])
m4_include(../../../build/bakefiles/wxcode.m4)
AM_WXCODE_INIT
AM_OPTIONS_WXCONFIG
AM_OPTIONS_WXPRESETS
AM_WXCODE_CHECKS([2.4.0])       # 2.4.0 is the minimum required version of wx
AM_WXCODE_END


(see wxcode/build/bakefiles/configure.ac for more info).
I've updated wxcode/build/bakefiles/readme.txt with a lot of details it was missing before.

Also, the new Bakefiles.bkgen file tells bakefile to put "Makefile.in" in the root folder 
of your component so that a typical components will have the following makefiles:

          build\makefile.vc       for MSVC (nmake)
          build\makefile.gcc      for Mingw (mingw32-make)
          build\makefile.wat      for Watcom (wmake)
          build\makefile.bcc      for Borland (make)

          Makefile.in   used by configure script to provide the "Makefile" under Unix
          configure     configures the Makefile.in doing the right substitutions and 
creates "Makefile"

which is much more in "unix" style. I found the way to keep all other unix stuff 
(config.sub, config.guess, *.m4, etc) in build\ which is much more clean than having these 
files in the root folder.

I took the freedom to update all the Bakefiles.bkgen files of the components.
If you need help with your component bakefiles, please ask NOW until I have some free time ;)

Francesco

[wxCode-users] About folders to remove

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

Hi,
     I was going to update the wiki page with some new entries when it came up to my mind 
that probably even SF administrators won't remove CVS empty folders completely: look at 
this support request I did some time ago to remove the "components" folder (the one which 
is empty):

http://sourceforge.net/tracker/index.php?func=detail&aid=1231255&group_id=1&atid=200001

and look at the repository:

http://cvs.sourceforge.net/viewcvs.py/wxcode/

that folder is still there... maybe that we will have to wait for Subversion.... :-(

Francesco

Re: [Fwd: [wxCode-users] [ wxcode-Bugs-1281776 ] wxListCtrlex does not exist]

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

I've removed the wxListCtrlEx component and closed this bug.

Francesco



Francesco Montorsi wrote:
> I'm forwarding this mail both to wxcode-users and to the author of 
> wxListCtrlEx...
> The "bug" is TRUE: the component does not have any source in the CVS nor 
> in the file release page...
> 
> if the author won't reply this mail, wxCode administrators will assume 
> that this component needs to be removed.
> 
> Francesco Montorsi
> 
> 
> -------- Original Message --------
> Subject: [wxCode-users] [ wxcode-Bugs-1281776 ] wxListCtrlex does not exist
> Date: Sun, 04 Sep 2005 14:25:30 -0700
> From: SourceForge.net <no...@so...>
> Reply-To: wxc...@li...
> To: no...@so...
> 
> Bugs item #1281776, was opened at 2005-09-04 21:25
> Message generated for change (Tracker Item Submitted) made by Item 
> Submitter
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1281776&group_id=51305 
> 
> 
> Please note that this message will contain a full copy of the comment 
> thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: website
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Submitted By: Michalis Kabrianis (mkab)
> Assigned to: Francesco Montorsi (frm)
> Summary: wxListCtrlex does not exist
> 
> Initial Comment:
> subject says all. there is no code and no info for that
> contribution.
> 
> ----------------------------------------------------------------------
> 
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1281776&group_id=51305 
> 
> 
> 
> -------------------------------------------------------
> 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] wxCode bakefiles for unix (was Re: ANN: wxPdfDocument 0.5 released)

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

 Hi Francesco,

> usually with non-graphical components using wx I get *exactly* the
> same behaviour under all platforms;

Well, I'll keep to my habit to not promise things not confirmed to be 
working. That's the reason, I flagged wxPdfDocument for wxMSW only, 
although I'm pretty sure it should work as expected on _all_ wxWidgets 
platforms. Maybe I'm able to add wxGTK soon.

> If you don't need it and you like the usual
> libCOMPNAME[u][d].a             (for static builds)
> or
> libCOMPNAME[u][d].so.0.0.0             (for shared builds)
> then you don't need to change anything in your component bakefile.

Ok, I think I stay with the default for now.

> > This will be corrected in 2.6.2?
> sure; I'm just waiting for 2.6.2 which will have a new option in the
> "wx-config" script which I'll use to set WX_* option vars. 

Fine.

> Unfortunately an easy way to set them won't be integrated directly in
> wx since Bakefile author's does not think it's a good thing; 

Too bad. Especially for component like those on wxCode it would make 
life much easier for wxCode maintainers.

> the only way I can see is to write a configure.in/ac file which gives
> to the user the options: 
> 
> --enable-debug
> --enable-shared
> --enable-unicode
> --with-gtk
> --with-x11
> --with-motif
> --with-mac
> --with-msw
> 
> which the user *must* use to indicate to the configure script of its component the same 
> configuration he told to the configure script of wxWidgets.
> I'm a little busy now; I'll try to implement this in a reusable way first in my components 
> and then put some info about this in wxcode/build/bakefiles/readme.txt.

That would be really great!

Regards,

Ulrich
-- 
E-Mail privat:  Ulr...@gm...
E-Mail Studium: Ulr...@Fe...
World Wide Web: http://www.stud.fernuni-hagen.de/q1471341

Re: [wxCode-users] wxCode bakefiles for unix (was Re: ANN: wxPdfDocument 0.5 released)

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

Hi,

Ulrich Telle wrote:
> Hi Francesco,
> 
> 
>>>configure did not work since it believed that the makefiles were
>>>created by bakefile 0.1.9 although I definitely created them with
>>>0.1.9.1. I changed the version number in autoconf_inc.m4 from 0.1.9
>>>to 0.1.9.1. 
>>
>>yes; this is a bug in the latest version of bakefile which has already
>>been solved in the CVS. I forgot to mention it, sorry. 
> 
> 
> If it's not already there I would suggest to add this information to 
> the wxCode maintainer guide.
done ;)


> The good news is, that wxPdfDocument compiles and runs on Linux without 
> further problems (if the makefile is ok, that is).
good !
usually with non-graphical components using wx I get *exactly* the same behaviour under 
all platforms; with graphic components the bugs I found to be present in a platform and 
not in another one are usually due to an incorrect use by me of some wx feature :)


>>>2) What changes are needed that the component's library name reflects 
>>>for which wxWidgets build it was created?
>>
>>the libname should get the [u][d] postfix like it does on windows... but it won't use 
>>exactly the same naming convention used by wx under unix... (i.e. 
>>libwx_[gtk2,x11][u][d]_sublib-MAJOR.MINOR.so.0.RELEASE.0)
> 
> 
> I'll check whether this works for my component tomorrow. Where can I 
> set MAJOR, MINOR and RELEASE for my own component?
well, the string

libwx_[gtk2,x11][u][d]_sublib-MAJOR.MINOR.so.0.RELEASE.0

is a description of the naming convention for wx used on unix-like systems.
If you don't need it and you like the usual

libCOMPNAME[u][d].a             (for static builds)

or

libCOMPNAME[u][d].so.0.0.0             (for shared builds)

then you don't need to change anything in your component bakefile.

anyway, if you want to set version numbers for your components, you should use the tags:

		<version>MAJOR.MINOR</version>
		<so_version>0.RELEASE.0</so_version>
		<mac_version>0</mac_version>

in your component_dll target.
As you can see in wxcode/build/bakefiles/templates.bkl the default settings for these tags 
(which have sense only for shared builds) are:

		<version>1.0</version>
		<so_version>0.0.0</so_version>
		<mac_version>0</mac_version>

You should override them in your component's bakefile to implement versioning.

NOTE: I'm not sure at 100% that MAJOR, MINOR and RELEASE must be used as I told above:
	        <version>MAJOR.MINOR</version>
		<so_version>0.RELEASE.0</so_version>
		<mac_version>0</mac_version>
       in fact the unix shared library versioning is quite complex since it allows to do a 
lot of things; I read a linux HOWTO some time ago but I also forget most of it :)
In bakefile docs these tags are not described so I think that MAJOR, MINOR and RELEASE 
should be used that way but I cannot grant it.


>>the Makefile created by configure can be used only for the
>>configuration you told to "./configure"... if you need to use another
>>wx build, you should do a "make install" for that wx build and then
>>relaunch your component's "configure" script.
> 
> 
> Ah, ok, I understand. (I'm very new to Linux, you know.)
;)



>>The Makefile will be adapted to the currently installed build of wx
>>(and here comes in the bug I told you in some previous mail: wx build
>>flags detection is buggy in wxcode bakefiles since prior 2.6.2 it was
>>not possible to detect them easily). 
> 
> 
> Absolutely true. I built 4 different versions of wxWidgets (ANSI, ANSI 
> DEBUG, UNICODE, UNICODE DEBUG). wxCode configure  said in the message 
> UNICODE DEBUG but created a makefile for ANSI without DEBUG.
> 
> This will be corrected in 2.6.2?
sure; I'm just waiting for 2.6.2 which will have a new option in the "wx-config" script 
which I'll use to set WX_* option vars.

Unfortunately an easy way to set them won't be integrated directly in wx since Bakefile 
author's does not think it's a good thing; even if I asked him many times his replies did 
not give any reason for this motivation - I'm not going to insist anymore since I fear 
that he will try to kill me; this thing gives me hell !!
This is the text of the mail he sent me recently:

Vaclav Slavik wrote:
 > Hi,
 >
 > Francesco Montorsi wrote:
 > [...]
 >>(or something like that, possibly shorter :-)) option which, only
 >>in case it is used, sets the WX_* options so that people who want
 >>to give to their wx-based libraries a name with, for example,
 >>[u][d] postfix, can use these info to set all their variables to be
 >>substituted into Makefile.in... do you think this is not a good
 >>approach ?
 >
 >
 > No. I really don't know what should I do to get the message through if
 > repeatedly explaining it to you is apparently not enough :( -- the
 > WX_* options are *NOT* part of wxpreset's public API, you should
 > *NOT*  use them for *ANYTHING*.

and more info at:
http://sourceforge.net/tracker/index.php?func=detail&aid=1254557&group_id=9863&atid=309863

So, he decided that wxpresets won't be useful for developers like me and you who want to 
give to their components an easy unix build system, i.e. which detects automatically wx 
build flags.

This means that I'll have to ship an additional .m4 macro file in wxcode/build/bakefiles 
folder which maintainers will need to install to write shorter configure.in/ac files.
And this also means that I'll have to do that in all my wx projects, grrrrrrr.

In conclusion, also with wx2.6.2 creating a good "configure" script won't be as easy as it 
could be.


> I guess not every wxWidgets user will switch to 2.6.2 immediately. Is 
> there a way to support pre 2.6.2 users?
the only way I can see is to write a configure.in/ac file which gives to the user the options:

--enable-debug
--enable-shared
--enable-unicode
--with-gtk
--with-x11
--with-motif
--with-mac
--with-msw

which the user *must* use to indicate to the configure script of its component the same 
configuration he told to the configure script of wxWidgets.
I'm a little busy now; I'll try to implement this in a reusable way first in my components 
and then put some info about this in wxcode/build/bakefiles/readme.txt.

Francesco

Re: [wxCode-users] wxCode bakefiles for unix (was Re: ANN: wxPdfDocument 0.5 released)

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

Hi Francesco,

> > configure did not work since it believed that the makefiles were
> > created by bakefile 0.1.9 although I definitely created them with
> > 0.1.9.1. I changed the version number in autoconf_inc.m4 from 0.1.9
> > to 0.1.9.1. 
> yes; this is a bug in the latest version of bakefile which has already
> been solved in the CVS. I forgot to mention it, sorry. 

If it's not already there I would suggest to add this information to 
the wxCode maintainer guide.

> > 1) What changes are needed in my component's bakefile or elsewhere so 
> > that the BUILDDIR directory is created if it does not exist?
> that's not an easy thing like it could seem.

What a pity.

> In short, you should not use BUILDDIR != "." with autoconf since the
> author of Bakefile decided not to support automatic BUILDDIR creation
> with autoconf and it's not easy to add this manually. 

Ok, good to know.

> Thus I suggest you to use:
> <if cond="FORMAT!='autoconf'">
> <set var="BUILDDIR">$(FORMAT)$(WXLIBPOSTFIX)$(POSTFIX)</set>
> </if>

I'll adjust my component's bakefile. I'll experiment until I get 
something which works on Linux without too much difficulties.

The good news is, that wxPdfDocument compiles and runs on Linux without 
further problems (if the makefile is ok, that is).

> > 2) What changes are needed that the component's library name reflects 
> > for which wxWidgets build it was created?
> the libname should get the [u][d] postfix like it does on windows... but it won't use 
> exactly the same naming convention used by wx under unix... (i.e. 
> libwx_[gtk2,x11][u][d]_sublib-MAJOR.MINOR.so.0.RELEASE.0)

I'll check whether this works for my component tomorrow. Where can I 
set MAJOR, MINOR and RELEASE for my own component?

> the Makefile created by configure can be used only for the
> configuration you told to "./configure"... if you need to use another
> wx build, you should do a "make install" for that wx build and then
> relaunch your component's "configure" script.

Ah, ok, I understand. (I'm very new to Linux, you know.)

> The Makefile will be adapted to the currently installed build of wx
> (and here comes in the bug I told you in some previous mail: wx build
> flags detection is buggy in wxcode bakefiles since prior 2.6.2 it was
> not possible to detect them easily). 

Absolutely true. I built 4 different versions of wxWidgets (ANSI, ANSI 
DEBUG, UNICODE, UNICODE DEBUG). wxCode configure  said in the message 
UNICODE DEBUG but created a makefile for ANSI without DEBUG.

This will be corrected in 2.6.2?

I guess not every wxWidgets user will switch to 2.6.2 immediately. Is 
there a way to support pre 2.6.2 users?

> PS: I'm moving the thread from wxusers to wxcode since I think it's
> more relevant there. 

Right.

Thank you for your helpful responses!

Regards,

Ulrich
-- 
E-Mail privat:  Ulr...@gm...
E-Mail Studium: Ulr...@Fe...
World Wide Web: http://www.stud.fernuni-hagen.de/q1471341

[wxCode-users] wxCode bakefiles for unix (was Re: ANN: wxPdfDocument 0.5 released)

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

Hi,

Ulrich Telle wrote:

> Not really. configure did not work since it believed that the makefiles 
> were created by bakefile 0.1.9 although I definitely created them with 
> 0.1.9.1. I changed the version number in autoconf_inc.m4 from 0.1.9 to 
> 0.1.9.1. 
yes; this is a bug in the latest version of bakefile which has already been solved in the 
CVS. I forgot to mention it, sorry.

>Thereafter I could exceute configure without error messages. 
> But when executing make I got
> 
> cc1plus:
> File or directory not found:
> opening dependency file
> autoconf_dll/wxpdfdoc_dll_pdfdoc.d
> 
> The reason is that I had added the line
> 
> <set var="BUILDDIR">$(FORMAT)$(WXLIBPOSTFIX)$(POSTFIX)</set>
> 
> to the bakefile of my component, so that I'm able to build my component 
> for different wxWidgets configurations like ANSI, UNICODE, with or 
> without DEBUG etc., but the makefile does not create the directory if it 
> does not exist (as does MSVC). I created it manually. make then worked.
> 
> I still have several questions:
> 
> 1) What changes are needed in my component's bakefile or elsewhere so 
> that the BUILDDIR directory is created if it does not exist?
that's not an easy thing like it could seem.
Please seem my old post (and the replies):

http://article.gmane.org/gmane.comp.sysutils.bakefile.devel/142

for more info.
In short, you should not use BUILDDIR != "." with autoconf since the author of Bakefile 
decided not to support automatic BUILDDIR creation with autoconf and it's not easy to add 
this manually.
Thus I suggest you to use:

<if cond="FORMAT!='autoconf'">
<set var="BUILDDIR">$(FORMAT)$(WXLIBPOSTFIX)$(POSTFIX)</set>
</if>


> 2) What changes are needed that the component's library name reflects 
> for which wxWidgets build it was created?
the libname should get the [u][d] postfix like it does on windows... but it won't use 
exactly the same naming convention used by wx under unix... (i.e. 
libwx_[gtk2,x11][u][d]_sublib-MAJOR.MINOR.so.0.RELEASE.0)


> 3) How do I create my component for different wxWidgets builds using the 
> Makefile created by configure? Is it sufficient to specify for example 
> -DDEBUG and/or -DUNICODE when invoking make? Or whatelse is needed?
the Makefile created by configure can be used only for the configuration you told to 
"./configure"...  if you need to use another wx build, you should do a "make install" for 
that wx build and then relaunch your component's "configure" script.
The Makefile will be adapted to the currently installed build of wx (and here comes in the 
bug I told you in some previous mail: wx build flags detection is buggy in wxcode 
bakefiles since prior 2.6.2 it was not possible to detect them easily).

Francesco

PS: I'm moving the thread from wxusers to wxcode since I think it's more relevant there.

[wxCode-users] [ wxcode-Bugs-1285407 ] user-defined font lost when using bold, text/bg colour

[SourceForge.net <no...@so...>]

Bugs item #1285407, was opened at 2005-09-08 23:49
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1285407&group_id=51305

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: treelistctrl
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Armel Asselin (aasselin)
Assigned to: Otto Wyss (wyo)
Summary: user-defined font lost when using bold, text/bg colour

Initial Comment:
create a treelistctrl, do "SetFont (<any_font>)", then on 
some items, do "SetItemTextColour(<item_id>, 
*wxRED).
these items are not using <any_font> but the "system 
default font".

when using wxTreeListItem::Attr(), we don't ensure 
the "local default attr" are used....
pItem->Attr().SetTextColour (colour); // for example.
Attr() may create a new set of attributes.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1285407&group_id=51305

Re: [wxCode-users] Cron job: wxDom is pending approval

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

Hi,

Dj Gilcrease wrote:
> Yes, I just added the functions to do the convetion for you. I also plan 
> on adding a few other functions that I felt were missing like 
> HasChild(child name), GetChild(child name), NumChildren(), NumAttrib().
> 
> Only reason I seperated it from wxXML at all is because I did not know 
> if any of the changes I was planing would potentialy break the other 
> things that use wxXML.
ok; the component has been approved; however I think that in wx2.7 the wx developers will 
document the wxXml API and make it "official" part of wx.
Thus I suggest you to follow strictly all wxWidgets coding standard: they could integrate 
the additions you make in wxXML ;)

Francesco


> 
> On 9/8/05, *Francesco Montorsi* <f18...@ya... 
> <mailto:f18...@ya...>> wrote:
> 
>     Hi,
>          just some questions before approving the component
> 
>     AFAIK wxXmlDocument::Load takes a wxInputStream and thus already
>     allows you to load from
>     file/url/strings.... see wxStringInputStream.
> 
>  
> 
>     AFAIK wxXmlDocument::Save takes a wxOutputStream and thus using a
>     wxStringOutputStream
>     gives the same feature, isn't it?
> 
>      > I changed the class names, and some of the function names soas to
>     not conflict with wxXML.
> 
>      > location: wxdom
>      > cdate: 2006-09-20
>      > id: 102
>      > status: beta
>      > docs: notavailable
>      > buildsys: projectfiles
>      > extdep: none
>      > wiki: enabled
>      > wxport: all
>      > samples: 0
>      > approved: 0
>      > author: Vaclav Slavik
>      > version: 1.0
>      > maintainerid: 24
>      >
>      > Maintainer SF username: Digitalxero
>      > Maintainer name: Dj Gilcrease
>      > Maintainer mail address: dig...@us...
>     <mailto:dig...@us...>
>      >
>      >
>      >
>      > -------------------------------------------------------
>      > 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
>      >
> 
> 
> 
> 
> -- 
> Dj Gilcrease
> OpenRPG Developer
> ~~http://www.openrpg.com
> MQ2 Plugin Developer
> ~~http://digitalxero.no- ip.org <http://ip.org>
> Web Admin for Thewarcouncil.com <http://Thewarcouncil.com>
> ~~http://www.thewarcouncil.com

Re: [wxCode-users] Cron job: wxDom is pending approval

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

Hi,
     just some questions before approving the component

Francesco Montorsi wrote:

 > name: wxDom
 > wxversion: 2.6
 > category: data container,text processing
 > language: cpp
 > description: This is a modification of wxXML that allows loading from a File, URL, or 
XML String.

AFAIK wxXmlDocument::Load takes a wxInputStream and thus already allows you to load from 
file/url/strings.... see wxStringInputStream.

Also allows dumping the Dom to String insted of just saving it to a file.
AFAIK wxXmlDocument::Save takes a wxOutputStream and thus using a wxStringOutputStream 
gives the same feature, isn't it?

 > I changed the class names, and some of the function names soas to not conflict with wxXML.

 > location: wxdom
 > cdate: 2006-09-20
 > id: 102
 > status: beta
 > docs: notavailable
 > buildsys: projectfiles
 > extdep: none
 > wiki: enabled
 > wxport: all
 > samples: 0
 > approved: 0
 > author: Vaclav Slavik
 > version: 1.0
 > maintainerid: 24
 >
 > Maintainer SF username: Digitalxero
 > Maintainer name: Dj Gilcrease
 > Maintainer mail address: dig...@us...
 >
 >
 >
 > -------------------------------------------------------
 > 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] Cron job: wxDom is pending approval

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

Hi,
     just some questions before approving the component

Francesco Montorsi wrote:
> name: wxDom
> wxversion: 2.6
> category: data container,text processing
> language: cpp
> description: This is a modification of wxXML that allows loading from a File, URL, or XML String. 
AFAIK wxXmlDocument::Load takes a wxInputStream and thus already allows you to load from 
file/url/strings.... see wxStringInputStream.

Also allows dumping the Dom to String insted of just saving it to a file.
AFAIK wxXmlDocument::Save takes a wxOutputStream and thus using a wxStringOutputStream 
gives the same feature, isn't it?

  I changed the class names, and some of the function names soas to not conflict with wxXML.
> location: wxdom
> cdate: 2006-09-20
> id: 102
> status: beta
> docs: notavailable
> buildsys: projectfiles
> extdep: none
> wiki: enabled
> wxport: all
> samples: 0
> approved: 0
> author: Vaclav Slavik
> version: 1.0
> maintainerid: 24
> 
> Maintainer SF username: Digitalxero
> Maintainer name: Dj Gilcrease
> Maintainer mail address: dig...@us...
> 
> 
> 
> -------------------------------------------------------
> 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
> 

[wxCode-users] Cron job: wxDom is pending approval

[Francesco M. <fr...@us...>]

name: wxDom
wxversion: 2.6
category: data container,text processing
language: cpp
description: This is a modification of wxXML that allows loading from a File, URL, or XML String. Also allows dumping the Dom to String insted of just saving it to a file. I changed the class names, and some of the function names soas to not conflict with wxXML. 
location: wxdom
cdate: 2006-09-20
id: 102
status: beta
docs: notavailable
buildsys: projectfiles
extdep: none
wiki: enabled
wxport: all
samples: 0
approved: 0
author: Vaclav Slavik
version: 1.0
maintainerid: 24

Maintainer SF username: Digitalxero
Maintainer name: Dj Gilcrease
Maintainer mail address: dig...@us...

[wxCode-users] [ wxcode-Feature Requests-1284226 ] Optional links

[SourceForge.net <no...@so...>]

Feature Requests item #1284226, was opened at 2005-09-07 21:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462819&aid=1284226&group_id=51305

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: website
Group: None
Status: Open
Resolution: None
Priority: 1
Submitted By: cecilio (cecilios)
Assigned to: Francesco Montorsi (frm)
Summary: Optional links

Initial Comment:
In the 'edit your component' page, I would suggest to
include two
check boxes to mark if your component has screenshots
and logo, respectively. If any of these check boxes are
not marked, the respective links should not appear in
the component page.

The idea is that not all components have a logo (it
should be optional to have one) and that not all
components have screenshots, especially those that are
libraries, have no windows or are not controls.

In theses cases, when a user clicks on any of these
links an error page is isplayed as if there where
something wrong with the wxCode page and the
maintainers didn't do their duties.

My proposal is to make these links optional and could
be extended to all links (website, documentation, ...)
as this could be of help in certain cases (i.e. during
set up or if you decide not to have that item for your
component).


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462819&aid=1284226&group_id=51305

Re: [wxCode-users] Cron job: wxLocalize is pending approval

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

Hi Otto,
  I have updated the database with this new component; I remember you that you can create 
a template-like structure for this component using the command:

./makenewcomp wxLocalize localize Otto Wyss

in the wxCode/components folder.
That cmd will automatically update also wxcode/website/updatesite.sh (just commit it after 
launching the script) so that the website for wxLocalize will be automatically synch with cvs.
Francesco

Francesco Montorsi wrote:
> name: wxLocalize
> wxversion: 2.6
> category: system
> language: cpp
> description: This component contains the localization functions which are missing from wxWidgets.
> location: localize
> cdate: 2006-09-20
> id: 101
> status: alpha
> docs: hand
> buildsys: makefiles,projectfiles
> extdep: none
> wiki: disabled
> wxport: all
> samples: 1
> approved: 0
> author: Otto Wyss
> version: 0.2.2
> maintainerid: 8
> 
> Maintainer SF username: wyo
> Maintainer name: Otto Wyss
> Maintainer mail address: wy...@us...
> 
> 
> 
> -------------------------------------------------------
> 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
> 

[wxCode-users] Cron job: wxLocalize is pending approval

[Francesco M. <fr...@us...>]

name: wxLocalize
wxversion: 2.6
category: system
language: cpp
description: This component contains the localization functions which are missing from wxWidgets.
location: localize
cdate: 2006-09-20
id: 101
status: alpha
docs: hand
buildsys: makefiles,projectfiles
extdep: none
wiki: disabled
wxport: all
samples: 1
approved: 0
author: Otto Wyss
version: 0.2.2
maintainerid: 8

Maintainer SF username: wyo
Maintainer name: Otto Wyss
Maintainer mail address: wy...@us...

Re: Components recategorized was Re: [wxCode-users] wxCode categories (please ALL read)

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

Hi,
John Labenski wrote:
> ps. Francesco - I can't seem to get the update script to work,
> permission problems. Could you run it.
Done.

Francesco

Components recategorized was Re: [wxCode-users] wxCode categories (please ALL read)

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

I have updated all the components from misc to what I understand them
to be. If you are the author, please readjust as necessary. Don't
forget to read
http://wxcode.sf.net/categories.php=20
to get an idea of "our" definitions of the category names.

Regards,
    John Labenski

ps. Francesco - I can't seem to get the update script to work,
permission problems. Could you run it.

Re: [wxCode-users] wxCode categories (please ALL read)

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

> I created the page wxcode.sf.net/categories.php which needs to be complet=
ed but I already
> added references to that page in the COMPSUBMIT & EDIT form.

I updated it to what we had talked about, giving examples of common
wxWidgets classes to help people understand their purpose.

> So everyone can now re-categorize its own components.

Hopefully, they will.

> PS: John, have you time to re-categorize the unmaintained components ? I =
won't be able to
> do it until next week

Probably later this week...=20

Regards,
    John Labenski

Re: [wxCode-users] Proposal: optional links

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

Hi,
    this would be a good thing. in this week I won't have much time for wxCode website... 
and since this is not so urgent, I would ask you to open a feature request on wxcode 
project page to remember me to do it in future ;-)

Ideally, the need for a screenshot / doc link page would be detected by the website itself 
looking at the

/home/groups/w/wx/wxcode/htdocs/documentation/PROJNAME
and
/home/groups/w/wx/wxcode/htdocs/screenshots/PROJNAME

folders: if they are empty no links are shown. However I think this would have a big 
performance impact on the website so options like you proposed are probably better.

However I would not allow the possibility to remove the LOGO since
1) it's used as a link anchor for the showcomp.php?name=XXXX page.
2) it gives an idea of the component (for libraries which don't have GUI you can think to 
something else - e.g. look at wxxml2 or keybinder or wxscript's logos) and makes the 
complist page pretty ;)

Francesco


cecilio wrote:
> Hi, 
> 
> I have a proposal for wxCode administrators:
> 
> In the 'edit your component' page, I would suggest to include two
> check boxes to mark if your component has screenshots and logo,
> respectively. If any of these check boxes are not marked, the
> respective links should not appear in the component page.
> 
> The idea is that not all components have a logo (it should be optional
> to have one) and that not all components have screenshots, especially
> those that are libraries, have no windows or are not controls.
> 
> In theses cases, when a user clicks on any of these links an error
> page is isplayed as if there where something wrong with the wxCode
> page and the maintainers didn't do their duties.
> 
> My proposal is to make these links optional and could be extended to
> all links (website, documentation, ...) as this could be of help in
> certain cases (i.e. during set up or if you decide not to have that
> item for your component).
> 
> Regards,
> Cecilio
> 
> 
> -------------------------------------------------------
> 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] wxCode categories (please ALL read)

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

> 'window container', 'dialog', 'control', 'window layout',
> 'networking', 'stream', 'database',
> 'data container',
> 'graphics'
> 'text processing'
> 'printing'
> 'import/export'
> 'system',
> 'tutorials/documentation' ,
> 'application'
> 'miscellaneous',
> 'wrapper'

>>Please try to eliminate ''miscellaneous'. I find it better to introduce
>>new categories than to allow such an unspecific category.
> 
> 
> Well, it'll be used for things that just don't fit anywhere else. Once
> we start to get a few of them, we can then decide what sort of new
> category we'd need and recategorize them. We can have a page with
> "our" interpretations of what each category is for to make it easy for
> people browsing to know where to look, but also help people decide
> what to use for their projects. We'll also say that new projects
> should try their best to use an existing category if possible and use
> misc as a last resort.
this is the best thing to do, in my opinion: completely removing "miscellaneous" could be
"hazardous".

I created the page wxcode.sf.net/categories.php which needs to be completed but I already 
added references to that page in the COMPSUBMIT & EDIT form.

I also updated the categories both in the Database and in the website since I assume those 
listed above are okay. Finally, I created the "multiple categories" feature.
So everyone can now re-categorize its own components.

Francesco

PS: John, have you time to re-categorize the unmaintained components ? I won't be able to 
do it until next week

[wxCode-users] Proposal: optional links

[cecilio <s.c...@gm...>]

Hi,=20

I have a proposal for wxCode administrators:

In the 'edit your component' page, I would suggest to include two
check boxes to mark if your component has screenshots and logo,
respectively. If any of these check boxes are not marked, the
respective links should not appear in the component page.

The idea is that not all components have a logo (it should be optional
to have one) and that not all components have screenshots, especially
those that are libraries, have no windows or are not controls.

In theses cases, when a user clicks on any of these links an error
page is isplayed as if there where something wrong with the wxCode
page and the maintainers didn't do their duties.

My proposal is to make these links optional and could be extended to
all links (website, documentation, ...) as this could be of help in
certain cases (i.e. during set up or if you decide not to have that
item for your component).

Regards,
Cecilio

Re: [wxCode-users] wxCode categories (please ALL read)

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

'window container', 'dialog', 'control', 'window layout',
'networking', 'stream', 'database',
'data container',
'graphics'
'text processing'
'printing'
'import/export'
'system',
'tutorials/documentation' ,
'application'
'miscellaneous',
'wrapper'
=20
> Please try to eliminate ''miscellaneous'. I find it better to introduce
> new categories than to allow such an unspecific category.

Well, it'll be used for things that just don't fit anywhere else. Once
we start to get a few of them, we can then decide what sort of new
category we'd need and recategorize them. We can have a page with
"our" interpretations of what each category is for to make it easy for
people browsing to know where to look, but also help people decide
what to use for their projects. We'll also say that new projects
should try their best to use an existing category if possible and use
misc as a last resort.
=20
> > > I think graphics could cover wxImage stuff and wxDC anything to do
> > > with drawing and images, wxPlot could go here then. wxPDFDocument
> > > could be import/export and graphics.
> > after looking at the component list, I see that it's not so
> > generic.... so it's okay for me.
>=20
> For wxPdfDocument I would use the categories 'printing' and 'graphics'.
> I wouldn't expect it to be found in 'import/export'

I was thinking in terms of exporting to a pdf file, some other things
that might end up here would be html, SVG, and other file format
readers and writers. It's up to you though.

Regards,
    John Labenski

[Fwd: [wxCode-users] [ wxcode-Bugs-1281776 ] wxListCtrlex does not exist]

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

I'm forwarding this mail both to wxcode-users and to the author of wxListCtrlEx...
The "bug" is TRUE: the component does not have any source in the CVS nor in the file 
release page...

if the author won't reply this mail, wxCode administrators will assume that this component 
needs to be removed.

Francesco Montorsi


-------- Original Message --------
Subject: [wxCode-users] [ wxcode-Bugs-1281776 ] wxListCtrlex does not exist
Date: Sun, 04 Sep 2005 14:25:30 -0700
From: SourceForge.net <no...@so...>
Reply-To: wxc...@li...
To: no...@so...

Bugs item #1281776, was opened at 2005-09-04 21:25
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1281776&group_id=51305

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: website
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michalis Kabrianis (mkab)
Assigned to: Francesco Montorsi (frm)
Summary: wxListCtrlex does not exist

Initial Comment:
subject says all. there is no code and no info for that
contribution.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1281776&group_id=51305


-------------------------------------------------------
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

[wxCode-users] [ wxcode-Bugs-1281776 ] wxListCtrlex does not exist

[SourceForge.net <no...@so...>]

Bugs item #1281776, was opened at 2005-09-04 21:25
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1281776&group_id=51305

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: website
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michalis Kabrianis (mkab)
Assigned to: Francesco Montorsi (frm)
Summary: wxListCtrlex does not exist

Initial Comment:
subject says all. there is no code and no info for that
contribution.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1281776&group_id=51305

Re: [wxCode-users] wxCode categories (please ALL read)

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

> > 'window container', 'dialog', 'control', 'window layout',
> > 'networking', 'stream', 'database',
> > 'data container',
> > 'graphics'
> > 'text processing'
> > 'printing'
> > 'import/export'
> > 'system',
> > 'tutorials/documentation' ,
> > 'application'
> > 'miscellaneous',
> > 'wrapper'

Please try to eliminate ''miscellaneous'. I find it better to introduce 
new categories than to allow such an unspecific category.

In my opinion 'system' is a too general term. I would propose something 
like 'operating system oriented' (or shorter 'os oriented').

> > I think graphics could cover wxImage stuff and wxDC anything to do
> > with drawing and images, wxPlot could go here then. wxPDFDocument
> > could be import/export and graphics.
> after looking at the component list, I see that it's not so
> generic.... so it's okay for me. 

For wxPdfDocument I would use the categories 'printing' and 'graphics'. 
I wouldn't expect it to be found in 'import/export'

> >>text what would group ?
> > 
> > Text processing, wxScintilla, wxSpellcheck...
> ok, "text processing" is a better name ;)

I agree.

> > I think just calling it "system" would allow it to cover wxCTB (serial
> > port) as well as filesystem stuff, there will probably only be a
> > couple of these.
> the best option would probably to create something like "hardware" for wxCTB but I think 
> wxCTB would be the only component inside it :-)
> So "system" is okay, after all.

See my comment above.

Regards, 

Ulrich
-- 
E-Mail privat:  Ulr...@gm...
E-Mail Studium: Ulr...@Fe...
World Wide Web: http://www.stud.fernuni-hagen.de/q1471341