wxcode-users — Submission, Questions, Information

[wxCode-users] what failed with wxPDF?

[Sven B. <fam...@gm...>]

Hi everyone,

well, a real newbie question...
I just got wxPDF from sourceforge.net. I ran the configure and make skript and now I surely want to use the classes. Do I have to copy all files from wxPDF-include/libs etc. to these directories, where I installed wxWidgets? Or what do I have to do? 

I really need help...

Best regards, Sven
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

Re: [wxCode-users] Problem with wxXml2

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

HI Francesco,

> Very strange - I'm rebuilding wx now in Unicode mode so that I can test it.
OK. Thank you.

> sincerely I don't remember if I ever added support for external entities
> in wxXml2... I'll have a look at it when I have time (which means not so
> soon unfortunately): if you need this feature in brief time you may want
> to look at libxml2 documentation and see how you can enable that in
> libxml2 and then wrap required function calls in wxXml2...

Any clue about where should I start looking in wxXml2?

Thank you.
Regards, Cecilio

Re: [wxCode-users] Problem with wxXml2

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

cecilio ha scritto:
> Hi Francesco,
> 
> I'm trying to use wxXml2 and I've found two problems. I am using
> Windows XP, MSVC and wxWidgets 2.8.0rc1. The problems are:
> 
> 1. In Unicode build (Debug Unicode) messages from libxml2 are not
> properly displayed. See attached filed:
> - 'ok.jpg' for the right output (minimal sample build in 'Debug' 
> configuration)
> - 'wrong.jpg' for the same xml file processed with minimal sample
> build in 'Debug Unicode' configuration.
Very strange - I'm rebuilding wx now in Unicode mode so that I can test it.


> 2. External entities are not properly included in the processed file.
> Just the name of the entity is included. As an example find attached
> three files:
> - 'document.xml' the XML document to process (menu LoadXML in minimal
> sample). This xml file is copied from book 'The XML bible, listing 9-4
> - 'signature.xml' this file is the content of the external entity.
> Copied from the same book, listing 9-3
> - 'output.jpg' is the output window of minimal sample. You can see
> that external entity &SIG; has been replaced just by its name instead
> of include its content.
sincerely I don't remember if I ever added support for external entities 
in wxXml2... I'll have a look at it when I have time (which means not so 
soon unfortunately): if you need this feature in brief time you may want 
to look at libxml2 documentation and see how you can enable that in 
libxml2 and then wrap required function calls in wxXml2...

Francesco

[wxCode-users] Problem with wxXml2

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

Hi Francesco,

I'm trying to use wxXml2 and I've found two problems. I am using
Windows XP, MSVC and wxWidgets 2.8.0rc1. The problems are:

1. In Unicode build (Debug Unicode) messages from libxml2 are not
properly displayed. See attached filed:
- 'ok.jpg' for the right output (minimal sample build in 'Debug' configuration)
- 'wrong.jpg' for the same xml file processed with minimal sample
build in 'Debug Unicode' configuration.


2. External entities are not properly included in the processed file.
Just the name of the entity is included. As an example find attached
three files:
- 'document.xml' the XML document to process (menu LoadXML in minimal
sample). This xml file is copied from book 'The XML bible, listing 9-4
- 'signature.xml' this file is the content of the external entity.
Copied from the same book, listing 9-3
- 'output.jpg' is the output window of minimal sample. You can see
that external entity &SIG; has been replaced just by its name instead
of include its content.

Am I doing something wrong?

Regards,
Cecilio

[wxCode-users] XSTC 4 beta released

[Nuklear Z. <nuk...@gm...>]

XSTC is now in beta. there was two small changes to the api, check 
changes.txt, they should be simple to correct for. still not many 
languages are fully supported, but next release should wrap that up. 
most of the support code is already there, i just need to fill in the 
color settings for everything. also there are readme and configuration 
text files, the documentation should be close to up-to-date this time. 
next release should have all the languages supported and documentation 
accurate. mostly it is just the addition of variables that i didn't 
document. cvs does update so if you want things faster than the official 
releases keep an eye on it.

Nuklear

Re: [wxCode-users] WX_DEBUG or BUILD

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

klaas.holwerda ha scritto:
> Hi John or Francesco,
> 
> I realized finally that to make stedit release, i needed this:
> 
> nmake  WX_DEBUG=0 -f makefile.vc
> 
> 
> But on wxLua i always typed this:
> 
> nmake  BUILD=release -f makefile.vc
> 
> Just curious, why is there this difference? Is it because of old/new bakefile generation?
yes, exactly. In wxLua we're using a modified bakefile version which 
allows to rename the options and I've renamed the WX_DEBUG option (which 
is declared by wxpresets) to BUILD (also remapping its accepted values) 
to resemble the wx-style of options....

in wxCode we're using official bakefile where the "rename option" patch 
has not been applied yet (grrr)...

Francesco

[wxCode-users] WX_DEBUG or BUILD

[klaas.holwerda <kho...@xs...>]

Hi John or Francesco,

I realized finally that to make stedit release, i needed this:

nmake  WX_DEBUG=0 -f makefile.vc


But on wxLua i always typed this:

nmake  BUILD=release -f makefile.vc

Just curious, why is there this difference? Is it because of old/new bakefile generation?

Klaas

Re: [wxCode-users] wxstedit wrong libname in release

[Klaas H. <db...@nl...>]

Francesco Montorsi wrote:
> Klaas Holwerda ha scritto:
> 
>>John Labenski wrote:
>>
>>
>>>$nmake WX_VERSION=27 WX_DEBUG=0 -f makefile.vc
>>
>>Oke if that is the way, better cjhange it to the lattest official release i think.
>>
>>I wonder why it is not possible to detect the version (as i do in Cmake from the library names ).
>>
>>C:\wxMSW-2.7.2\lib\vc_lib\mswd\build.cfg
>>
>>Contains this after wxWidgets is build:
>>
>>WXVER_MAJOR=2
>>WXVER_MINOR=7
>>WXVER_RELEASE=2
>>
>>So the information is there, wonder why Franscesco is not using this, maybe it is not doable in nmake.
> 
> right - DOS and NMAKE don't give you enough tools to do that.
> And I also see another major problem: if you have multiple wx builds 
> then you're going to have multiple build.cfg files in different 
> subfolders of vc_lib; how can you choose one among them ?
> 
> There's no notion of "default build" on Windows... so autodetection of 
> the build configuration is possible only on linux with autoconf format...

The default is debug, which is found in %WXWIN%. Others need to be specified with BUILD=

> 
> 
>>wx-config.exe ( recently mentioned on the dev list )does it like that.
> 
> right... but it needs a shell / make tool which supports backtick 
> expansion (aka command expansion), which is not the case for most of 
> win32 MAKEs...

He also talks about "and in VC using response files" to make this happen.
I don't know what that is. I do know that Cmake produces targets that run *.bat batch files, and produce files.
Those targets are part of the VC projects files. I will try to find what is happening in case of nmake generated makefile.
If such a target can produce some file, which is include in the nmake files somehow, it might be possible.

Klaas



-- 
Unclassified

Re: [wxCode-users] wxstedit wrong libname in release

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

Klaas Holwerda ha scritto:
> John Labenski wrote:
> 
>> $nmake WX_VERSION=27 WX_DEBUG=0 -f makefile.vc
> 
> Oke if that is the way, better cjhange it to the lattest official release i think.
> 
> I wonder why it is not possible to detect the version (as i do in Cmake from the library names ).
> 
> C:\wxMSW-2.7.2\lib\vc_lib\mswd\build.cfg
> 
> Contains this after wxWidgets is build:
> 
> WXVER_MAJOR=2
> WXVER_MINOR=7
> WXVER_RELEASE=2
> 
> So the information is there, wonder why Franscesco is not using this, maybe it is not doable in nmake.
right - DOS and NMAKE don't give you enough tools to do that.
And I also see another major problem: if you have multiple wx builds 
then you're going to have multiple build.cfg files in different 
subfolders of vc_lib; how can you choose one among them ?

There's no notion of "default build" on Windows... so autodetection of 
the build configuration is possible only on linux with autoconf format...

> wx-config.exe ( recently mentioned on the dev list )does it like that.
right... but it needs a shell / make tool which supports backtick 
expansion (aka command expansion), which is not the case for most of 
win32 MAKEs...

Francesco

Re: [wxCode-users] wxstedit wrong libname in release

[Klaas H. <db...@nl...>]

John Labenski wrote:

> $nmake WX_VERSION=27 WX_DEBUG=0 -f makefile.vc

Oke if that is the way, better cjhange it to the lattest official release i think.

I wonder why it is not possible to detect the version (as i do in Cmake from the library names ).

C:\wxMSW-2.7.2\lib\vc_lib\mswd\build.cfg

Contains this after wxWidgets is build:

WXVER_MAJOR=2
WXVER_MINOR=7
WXVER_RELEASE=2

So the information is there, wonder why Franscesco is not using this, maybe it is not doable in nmake.
wx-config.exe ( recently mentioned on the dev list )does it like that.
One problem is that building wxWidgets using VC project files, does not produce the build.cfg.
So the version option would be needed still.

Klaas



-- 
Unclassified

Re: [wxCode-users] wxstedit wrong libname in release

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

On 11/8/06, John Labenski <jla...@gm...> wrote:
> On 11/8/06, klaas.holwerda <kho...@xs...> wrote:
> > klaas.holwerda wrote:
> > > But it is looking in the rigth directories for it, so these things seem
> > > to be hard coded somewhere?
> > >
> > In the makefile.vc i changed the WX_VERSION to 27 , that solved one problem.
> > Still i though setting WXWIN should be enough.
>
> To my knowledge there is no way in MSW to get the version number into
> the nmake makefiles. There is no equivalent to wx-config so
> unfortunately you always have to specify WX_VERSION. WXWIN on the
> other hand is traditionally the path to the wxWidgets library and so
> it'll contain 'C:\path\to\wxWidgets-XXX'.

After reviewing the makefile.vc the behavior you saw is "normal." You
actually have to specify on the command line what build you want.
Instead of editing the makefile.vc just put the directives you want to
override on the command line like this.

$nmake WX_VERSION=27 WX_DEBUG=0 -f makefile.vc

Regards,
    John Labenski

[wxCode-users] [ wxcode-Bugs-1593097 ] wxthings, wxplotctrl do not build in static mode

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

Bugs item #1593097, was opened at 2006-11-08 18:20
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=1593097&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: any
Group: CVS HEAD
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxthings, wxplotctrl do not build in static mode

Initial Comment:
wxthings and wxplotctrl will not build a static library
even if --disable-shared is specified for configure and
configure reports STATIC mode.
Linking sample shared library is not found whether or
not static mode is selected.

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

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

Re: [wxCode-users] wxstedit wrong libname in release

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

On 11/8/06, klaas.holwerda <kho...@xs...> wrote:
> klaas.holwerda wrote:
> > But it is looking in the rigth directories for it, so these things seem
> > to be hard coded somewhere?
> >
> In the makefile.vc i changed the WX_VERSION to 27 , that solved one problem.
> Still i though setting WXWIN should be enough.

To my knowledge there is no way in MSW to get the version number into
the nmake makefiles. There is no equivalent to wx-config so
unfortunately you always have to specify WX_VERSION. WXWIN on the
other hand is traditionally the path to the wxWidgets library and so
it'll contain 'C:\path\to\wxWidgets-XXX'.

-John Labenski

Re: [wxCode-users] wxstedit wrong libname in release

[klaas.holwerda <kho...@xs...>]

klaas.holwerda wrote:
> But it is looking in the rigth directories for it, so these things seem 
> to be hard coded somewhere?
>   
In the makefile.vc i changed the WX_VERSION to 27 , that solved one problem.
Still i though setting WXWIN should be enough.

Klaas

Re: [wxCode-users] wxstedit wrong libname in release

[klaas.holwerda <kho...@xs...>]

Next i tried using wxWidgets 2.7.2., and it wants to produce the same 
name ( so not with 27 in it ).
And it wants to use wxmsw26d_stc.lib and it should be wxmsw27d_stc.lib??

But it is looking in the rigth directories for it, so these things seem 
to be hard coded somewhere?

Klaas

klaas.holwerda wrote:
> Hi John,
>
> At least the latest CVS of wxstedit under VC6 with nmake in release 
> build , produces  the wrong library name.
>   

Re: [wxCode-users] wxstedit wrong libname in release

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

On 11/8/06, klaas.holwerda <kho...@xs...> wrote:
> Hi John,
>
> At least the latest CVS of wxstedit under VC6 with nmake in release
> build , produces  the wrong library name.
>
> nmake -f makefile.vc BUILD=release
>
> I did clean all *.lib *.obj files etc. by hand first, to be sure.
>
> I think it should produce wxmsw26_stedit.lib
> But in debug and release i only get wxmsw26d_stedit.lib
>
> Hope you know how to fix this,

Ugh... more bakefile problems. I'll try to look into it tonight. For
now just copy it to the right name...

-John Labenski

[wxCode-users] wxstedit wrong libname in release

[klaas.holwerda <kho...@xs...>]

Hi John,

At least the latest CVS of wxstedit under VC6 with nmake in release 
build , produces  the wrong library name.
 
nmake -f makefile.vc BUILD=release

I did clean all *.lib *.obj files etc. by hand first, to be sure.

I think it should produce wxmsw26_stedit.lib
But in debug and release i only get wxmsw26d_stedit.lib

Hope you know how to fix this,

Klaas

[wxCode-users] [ wxcode-Patches-1592274 ] [wxScintilla]compile against wx2.7

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

Patches item #1592274, was opened at 2006-11-07 22:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462818&aid=1592274&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mispunt (mispunt)
Assigned to: Nobody/Anonymous (nobody)
Summary: [wxScintilla]compile against wx2.7

Initial Comment:
The keycodes are deprecated:
WXK_PRIOR
WXK_NEXT
WXK_NUMPAD_PRIOR
WXK_NUMPAD_NEXT

Patch in the file ScintillaWX.cpp: (sorry, I didn't
made a proper patch file, I don't have CVS)
    case WXK_HOME:              key = SCK_HOME;     break;
    case WXK_NUMPAD_END:        // fall through
    case WXK_END:               key = SCK_END;      break;
#if wxCHECK_VERSION(2, 7, 0)
    case WXK_NUMPAD_PAGEUP:     // fall through
    case WXK_PAGEUP:            key = SCK_PRIOR;    break;
#else
    case WXK_NUMPAD_PAGEUP:     // fall through
    case WXK_PAGEUP:            // fall through
    case WXK_NUMPAD_PRIOR:      // fall through
    case WXK_PRIOR:             key = SCK_PRIOR;    break;
#endif
#if wxCHECK_VERSION(2, 7, 0)
    case WXK_NUMPAD_PAGEDOWN:   // fall through
    case WXK_PAGEDOWN:          key = SCK_NEXT;     break;
#else
    case WXK_NUMPAD_PAGEDOWN:   // fall through
    case WXK_PAGEDOWN:          // fall through
    case WXK_NUMPAD_NEXT:       // fall through
    case WXK_NEXT:              key = SCK_NEXT;     break;
#endif
    case WXK_NUMPAD_DELETE:     // fall through
    case WXK_DELETE:            key = SCK_DELETE;   break;


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

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

Re: [wxCode-users] wxActiveRecordGenerator (aka wxARG) 1.1.0 Released

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

Matías Szeftel ha scritto:
> Hi wxCoders.
> Just wanted to let you know that I have released wxARG 1.1.0. In the
> download section you'll find the 32bit windows release (Btw, what else
> should I put in the download section?).
probably you should put the source code of wxARG as well. It's important 
in every Open Source project to provide that download and in this case 
it's even more important since it could be used by Unix users to compile 
your app against wxGTK.


> And in the website there is a tutorial on how to use the generated
> classes: http://wxcode.sourceforge.net/components/activerecord/
good work!


> 
> This version has 2 new features:
> - You can save your work in an xml file (.wxarg extension).
> - You can add methods and variables to the generated classes by coding
> inside the custom markers.
> 
> I would appreciate any feedback, bugs reports or just opinions or
> feature ideas.
I don't have much time right now but in future I'll give it a try ;)

Francesco


PS: just as side note: don't start a new thread on a mailing list using 
the "reply-to" function of your mail reader as otherwise your mail will 
be marked as a reply of the original thread (the "cron job: wxDNSSD is 
pending approval" in this case)... and will be archived as such ;)

[wxCode-users] wxActiveRecordGenerator (aka wxARG) 1.1.0 Released

[<msz...@ya...>]

Hi wxCoders.
Just wanted to let you know that I have released wxARG 1.1.0. In the
download section you'll find the 32bit windows release (Btw, what else
should I put in the download section?).
And in the website there is a tutorial on how to use the generated
classes: http://wxcode.sourceforge.net/components/activerecord/

This version has 2 new features:
- You can save your work in an xml file (.wxarg extension).
- You can add methods and variables to the generated classes by coding
inside the custom markers.

I would appreciate any feedback, bugs reports or just opinions or
feature ideas.
Thanks to wxCode to give this space to wx users and thanks the
DatabaseLayer team.

Regards, Matías.
__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam gratis! 
Abru cuenta ya! - http://correo.yahoo.com.ar

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

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

William H. Schultz ha scritto:
> Well, if we stick with wxServiceDiscovery, I would plan on naming my 
> classes as follows:  wxServiceDiscoveryTaskBase, 
> wxServiceDiscoveryBrowser, wxServiceDiscoveryResolver, 
> wxServiceDiscoveryService, and wxServiceDiscoveryResult.  If those names 
> don't seem too big, 
they don't seem excessively long to me...

>then I'm fine with wxServiceDiscovery.
> 
well, the component name isn't so strictly tied to the name of the C++ 
classes, even if it's a good habit to keep the two related.

In any case, I've added the "servicediscovery" directory to SVN repo.

Only warning: unfortunately SVN does not allow to set permissions and 
thus any wxCode developer could commit (by error) things in other's 
components. So, please be careful not to do it...

Thanks for this very interesting component!

Ask for any help,
Francesco

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

[William H. S. <whs...@ce...>]

Well, if we stick with wxServiceDiscovery, I would plan on naming my  
classes as follows:  wxServiceDiscoveryTaskBase,  
wxServiceDiscoveryBrowser, wxServiceDiscoveryResolver,  
wxServiceDiscoveryService, and wxServiceDiscoveryResult.  If those  
names don't seem too big, then I'm fine with wxServiceDiscovery.


-------------------------------
Hank Schultz
Cedrus Corporation
http://www.cedrus.com/


On Oct 30, 2006, at 11:39 AM, Francesco Montorsi wrote:

> William H. Schultz ha scritto:
>> Maybe wxSvcDiscov?
> why not wxServiceDiscovery ?
> I think it's worth adding those 7 additional characters since it's  
> much
> more readable with that name ;)
>
>
>>> Removing the wx is fine with me.  That just seemed to be what I was
>>> supposed to do from the description of the directions.
> right, I need to explicitely add a note about this in submission  
> form too.
>
>>  Also, DNSSD
>>> was something I came up with to fill out the form.  The classes are
>>> still implemented in our own proprietary internal naming system and
>>> have not been renamed yet.  I wanted to avoid putting Bonjour in the
>>> name, as the project could potential use compatible DNS Service
>>> Discovery APIs other than Apple's Bonjour, though currently, it's  
>>> only
>>> implemented using Bonjour.
> ah, ok.
>
>>>  Also, I chose wxDNSSD over something like
>>> wxDNSServiceDiscovery because I have about a half-dozen related
>>> classes that will need to be renamed.
>>>
>>> There's a small discussion on this going on over at the wx-dev list
>>> under the thread title "Bonjour Support."
> sorry - I didn't follow it closely.
>
>
> Francesco
>

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

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

William H. Schultz ha scritto:
> Maybe wxSvcDiscov?
why not wxServiceDiscovery ?
I think it's worth adding those 7 additional characters since it's much 
more readable with that name ;)


>> Removing the wx is fine with me.  That just seemed to be what I was 
>> supposed to do from the description of the directions.
right, I need to explicitely add a note about this in submission form too.

>  Also, DNSSD 
>> was something I came up with to fill out the form.  The classes are 
>> still implemented in our own proprietary internal naming system and 
>> have not been renamed yet.  I wanted to avoid putting Bonjour in the 
>> name, as the project could potential use compatible DNS Service 
>> Discovery APIs other than Apple's Bonjour, though currently, it's only 
>> implemented using Bonjour.
ah, ok.

>>  Also, I chose wxDNSSD over something like 
>> wxDNSServiceDiscovery because I have about a half-dozen related 
>> classes that will need to be renamed.
>>
>> There's a small discussion on this going on over at the wx-dev list 
>> under the thread title "Bonjour Support."
sorry - I didn't follow it closely.


Francesco

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

[William H. S. <whs...@ce...>]

Maybe wxSvcDiscov?


-------------------------------
Hank Schultz
Cedrus Corporation
http://www.cedrus.com/


On Oct 30, 2006, at 10:58 AM, William H. Schultz wrote:

> Removing the wx is fine with me.  That just seemed to be what I was  
> supposed to do from the description of the directions.  Also, DNSSD  
> was something I came up with to fill out the form.  The classes are  
> still implemented in our own proprietary internal naming system and  
> have not been renamed yet.  I wanted to avoid putting Bonjour in  
> the name, as the project could potential use compatible DNS Service  
> Discovery APIs other than Apple's Bonjour, though currently, it's  
> only implemented using Bonjour.  Also, I chose wxDNSSD over  
> something like wxDNSServiceDiscovery because I have about a half- 
> dozen related classes that will need to be renamed.
>
> There's a small discussion on this going on over at the wx-dev list  
> under the thread title "Bonjour Support."
>
> I'm fine with a rename, but I'm not convinced about what it  
> *should* be.
>
>
> -------------------------------
> Hank Schultz
> Cedrus Corporation
> http://www.cedrus.com/
>
>
> On Oct 30, 2006, at 10:31 AM, Francesco Montorsi wrote:
>
>> William H. Schultz ha scritto:
>>> I can see that the folder has been added to the CVS repository  
>>> (through
>>> sourceforge's browse CVS feature), but I can't login to do a CVS
>>> checkout with my sourceforge account.
>> sorry - we forget to add you to the devel list of wxCode project.  
>> Done now.
>>
>>> I would rather use SVN,
>>> personally, but I also can't added the directory to the SVN  
>>> repository
>>> (authorization failed).
>>>
>>> Ideas?
>> I'll move your new component under wxCode SVN. I really need to add a
>> "CVS/SVN repository" radio box in component submission form ;)
>>
>> Before doing it however:
>>
>>    1) I'd remove the "wx" prefix from the directory name. I hope  
>> this is
>> ok for you. Components with the 'wx' prefix in dir name should be  
>> avoid.
>>
>>    2) is wxDNSSD the best name for such component ? It looks a little
>> weird for me and, maybe because I'm ignorant, don't say me much about
>> what it is. Could it be better to rename it to e.g. wxBonjour?
>>
>>
>> Francesco
>>
>>
>>
>> --------------------------------------------------------------------- 
>> ----
>> Using Tomcat but need to do more? Need to support web services,  
>> security?
>> Get stuff done quickly with pre-integrated technology to make your  
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
>> Geronimo
>> http://sel.as-us.falkag.net/sel? 
>> cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> wxCode-users mailing list
>> wxC...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642______________________________ 
> _________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users

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

[William H. S. <whs...@ce...>]

Removing the wx is fine with me.  That just seemed to be what I was  
supposed to do from the description of the directions.  Also, DNSSD  
was something I came up with to fill out the form.  The classes are  
still implemented in our own proprietary internal naming system and  
have not been renamed yet.  I wanted to avoid putting Bonjour in the  
name, as the project could potential use compatible DNS Service  
Discovery APIs other than Apple's Bonjour, though currently, it's  
only implemented using Bonjour.  Also, I chose wxDNSSD over something  
like wxDNSServiceDiscovery because I have about a half-dozen related  
classes that will need to be renamed.

There's a small discussion on this going on over at the wx-dev list  
under the thread title "Bonjour Support."

I'm fine with a rename, but I'm not convinced about what it *should* be.


-------------------------------
Hank Schultz
Cedrus Corporation
http://www.cedrus.com/


On Oct 30, 2006, at 10:31 AM, Francesco Montorsi wrote:

> William H. Schultz ha scritto:
>> I can see that the folder has been added to the CVS repository  
>> (through
>> sourceforge's browse CVS feature), but I can't login to do a CVS
>> checkout with my sourceforge account.
> sorry - we forget to add you to the devel list of wxCode project.  
> Done now.
>
>> I would rather use SVN,
>> personally, but I also can't added the directory to the SVN  
>> repository
>> (authorization failed).
>>
>> Ideas?
> I'll move your new component under wxCode SVN. I really need to add a
> "CVS/SVN repository" radio box in component submission form ;)
>
> Before doing it however:
>
>    1) I'd remove the "wx" prefix from the directory name. I hope  
> this is
> ok for you. Components with the 'wx' prefix in dir name should be  
> avoid.
>
>    2) is wxDNSSD the best name for such component ? It looks a little
> weird for me and, maybe because I'm ignorant, don't say me much about
> what it is. Could it be better to rename it to e.g. wxBonjour?
>
>
> Francesco
>
>
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users