wxcode-users — Submission, Questions, Information

Re: [wxCode-users] error LNK2019: unresolved external symbol

[kill k. <ic...@gm...>]

kill koll <icmp128@...> writes:

> 
> Hi.
> 
> app.obj : error LNK2019: unresolved external symbol
>  "public: void __thiscall
> wxStringData::Free(void)" (?Free <at> wxStringData <at>  <at> QAEXXZ)
>  referenced in function
> "public: void __thiscall wxStringData::Unlock(void)" 
> (?Unlock <at> wxStringData <at>  <at> QAEXXZ)
> 
> C:\dev\msvc\app.exe : fatal error LNK1120: 1 unresolved externals
> 
> Can anyone help with this. I've set up everything like in
> 
> http://www.wxwidgets.org/wiki/index.php/Compiling_WxWidgets#Your_Application_2
> google search doesnt seem to help either.
> 
> thanks.
ok, changed project->properties->c/c++->code generation->Runtime library 
to multi-threaded debug DLL(/MDd)

was before
/MTd

but this /MDd generates dynamically linked .exe, I still want staticaly linked
one... 

[wxCode-users] error LNK2019: unresolved external symbol

[kill k. <ic...@gm...>]

Hi.


app.obj : error LNK2019: unresolved external symbol
 "public: void __thiscall
wxStringData::Free(void)" (?Free@wxStringData@@QAEXXZ)
 referenced in function
"public: void __thiscall wxStringData::Unlock(void)" 
(?Unlock@wxStringData@@QAEXXZ)

C:\dev\msvc\app.exe : fatal error LNK1120: 1 unresolved externals

Can anyone help with this. I've set up everything like in

http://www.wxwidgets.org/wiki/index.php/Compiling_WxWidgets#Your_Application_2
google search doesnt seem to help either.

thanks.

[wxCode-users] [ wxcode-Patches-1546132 ] wxArchive fails with some malformed archives

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

Patches item #1546132, was opened at 2006-08-24 17:36
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=1546132&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
Submitted By: David Hart (dghart)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxArchive fails with some malformed archives

Initial Comment:
Hi Mike,

I've found a problem with wxArchive tarstrm.cpp. It
happens with tar archives that were downloaded as
tar.bz2 files, and decompressed either with bunzip2 or
with Ryan Norton's wxBZipStream class. About half of
these are currently not readable: they give a "checksum
failure reading tar header block" message.

The problem is that in these archives, the TypeFlag
field for regular files is blank, rather than holding
'0'. As a result m_TypeFlag holds '\0', and this is
matched in the strchr(ignore,...) call in
GetDataSize(). So all files are assumed to have zero
size.  This means the next header is not found
correctly; thus the error message.

I could have translated each blank into '0', but I
don't know what the buggy version of tar will do to
pipes etc (none of the broken archives had such
rarities). So I've made the lesser change of checking
in GetDataSize() for a null m_TypeFlag, and assuming
this to be a regular file. All the tar.bz2 files that
I've tried can now be untarred successfully.

The good news is that tarstreams  work well in
conjunction with both wxZlibInputStream (for .tgz) and
(the patched) wxBZipStream, in a real-life situation:
'peeking' into archives in a (linux) filemanager.
Thanks for creating them, and I hope tarstreams and
wxBZipStream are added soon to the wxWidgets, er,
mainstream.

I've sent a similar report to Chris Elliott at wxHatch.

Regards,

David Hart


--- tarstrm.cpp	2006-08-24 17:56:50.000000000 +0100
+++ tarstrm.cpp	2006-08-24 17:57:01.000000000 +0100
@@ -350,4 +350,6 @@
 static inline wxFileOffset GetDataSize(const
wxTarEntry& entry)
 {
+    if ( entry.GetTypeFlag() == '\0' ) return
entry.GetSize();  // First check there *is* a file
type: some archives seem to omit it for regular files
+
     const char ignore[] = {
         wxTAR_CHRTYPE, wxTAR_BLKTYPE, wxTAR_DIRTYPE,
wxTAR_FIFOTYPE, 0




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

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

Re: [wxCode-users] Removing wxMidi from wxCode CVS

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

On 8/20/06, cecilio <s.c...@gm...> wrote:
> I am having problems to keep wxMidi CVS updated.
>
> wxMidi was developed as a need for project LenMus
> (lenmus.sourceforge.net), so wxMidi is part of it and is maintaned
> inside lenmus project; wxMidi is also stored in lenmus SVN.

I agree that this would be annoying.

> Having to maintain wxMidi also in wxCode is causing me a lot of
> trouble, specially because I no longer use CVS (I moved lenmus project
> to SVN). Yesterday I was trying to update wxMidi and I discovered that
> my CVS software is not updated, and my CVS access is not working
> properly. Also I am loosing the little knowledge I had about how to

Sourceforge has changed their hostnames so that you need to use
wxcode.cvs.sourceforge.net and not just cvs.sourceforge.net. Maybe
this is the problem.

> use CVS. Taking into account that wxMidi is quite stable and That I
> make an occasional change just every six months, the situation is
> going to be worst in future.

If you get your CVS working again, maybe updates to the wxCode version
wouldn't be too troublesome? I hate to say it, (I do it too), but
updating the wxCode version every 6 months and let it lag behind a
little might not be too much trouble.

> So I am thinking about removing wxMidi from wxCode CVS. That is,
> everything will continue as it is now: wxMidi will be part of wxCode,
> but the only difference will be that wxMidi source code will not be
> available in wxCode CVS, but in LenMus CVS. As the wxMidi distribution

If it's easy to get to then it's almost the same.

> package already includes all source code I don't think this change is
> important.

The one nice thing about wxCode is that eventually we'd like to get
all the bakefile build files in order and then people can just
download the whole wxCode distribution and mix and match the
components. My personal pet peeve about using external libs is that
they all use different build files and methods and it's a pain to
integrate them with your project. With wxMidi as a part of wxCode
people may find it easier to manage if they're also using something
else from wxCode.

Anyway, that's my thoughts, it's up to you in the end.
    John Labenski

ps. If you do decide to remove it, please put a note in the components
page saying as much and where to get it.

[wxCode-users] [ wxcode-Patches-1544006 ] Patch to stop wxBZipStream hanging on large archives

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

Patches item #1544006, was opened at 2006-08-21 15:21
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=1544006&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
Submitted By: David Hart (dghart)
Assigned to: Nobody/Anonymous (nobody)
Summary: Patch to stop wxBZipStream hanging on large archives

Initial Comment:
Hi Ryan,

I've been using wxBZipStream on top of Mike Wetherell's
wxArchive tarstreams, to peek inside tar.bz2 files in a
filemanager.  I've found one 'issue' and one bug.

The issue is that you use #ifndef _WX_WXZSTREAM_H__ to
protect the .h file. So does wx/zstream.h, which caused
interesting problems until I twigged.  Perhaps
_WX_WXBZSTREAM_H__ ...

The bug occurs with large archives, say 1MB or so.
Trying to decompress them hangs the app in an infinite
loop.  I've traced the cause to this delectable line in
wxBZipInputStream::OnSysRead

  nBufferPos += -(nRead - (
    nRead += (WXBZBS - nBufferPos -
((bz_stream*&)hZip)->avail_in)
      ));

Presumably this gets parsed from right to left, so
because of the second +=, it simplifies to nBufferPos
+= -(nRead - nRead); and nBufferPos remains unchanged.
 In particular, if nBufferPos is 0 it stays 0; and if
bufsize was originally 0 too, the function returns 0.
This causes it to be called again with a bufsize of 0,
and so ad infinitum.

I have very little idea what *should* be happening
here, but storing the amount of data remaining seemed
like a good idea, and I'm pleased to say it works :) .
I've tested with bzipped archives up to 600MB
successfully (it took 6 minutes, mind you).

Also, in the diff I've removed the  "- nRead" from line
128 since this had just been set to zero.

Regards,

David Hart


--- bzipstream.cpp	2006-08-21 14:25:00.000000000 +0100
+++ newbzipstream.cpp	2006-08-21 14:26:59.000000000 +0100
@@ -126,5 +126,5 @@
 
 	((bz_stream*&)hZip)->next_out =
&(((char*&)buffer)[nRead]);
-	((bz_stream*&)hZip)->avail_out = bufsize - nRead;
+	((bz_stream*&)hZip)->avail_out = bufsize;
 
 	while (((bz_stream*&)hZip)->avail_out != 0)
@@ -157,7 +157,5 @@
 		if (nRet == BZ_OK)	
 		{
-			nBufferPos += -(nRead - (
-			nRead += (WXBZBS - nBufferPos -
((bz_stream*&)hZip)->avail_in)
-			));
+			nBufferPos = WXBZBS  - ((bz_stream*&)hZip)->avail_in;
 		}
 		else if(nRet == BZ_STREAM_END)


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

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

[wxCode-users] Removing wxMidi from wxCode CVS

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

Hi Francesco and wxCode colleagues,

I am having problems to keep wxMidi CVS updated.

wxMidi was developed as a need for project LenMus
(lenmus.sourceforge.net), so wxMidi is part of it and is maintaned
inside lenmus project; wxMidi is also stored in lenmus SVN.

Having to maintain wxMidi also in wxCode is causing me a lot of
trouble, specially because I no longer use CVS (I moved lenmus project
to SVN). Yesterday I was trying to update wxMidi and I discovered that
my CVS software is not updated, and my CVS access is not working
properly. Also I am loosing the little knowledge I had about how to
use CVS. Taking into account that wxMidi is quite stable and That I
make an occasional change just every six months, the situation is
going to be worst in future.

So I am thinking about removing wxMidi from wxCode CVS. That is,
everything will continue as it is now: wxMidi will be part of wxCode,
but the only difference will be that wxMidi source code will not be
available in wxCode CVS, but in LenMus CVS. As the wxMidi distribution
package already includes all source code I don't think this change is
important.

I would appreciate your comments and suggestions before taking a final decision.

Thank you and kind regards,

Cecilio Salmeron

[wxCode-users] Bakefile issues

[Jaakko S. <jaa...@pp...>]

Hi all,

I'm compiling a component for wxWidgets 2.7.0,
and it seems that bakefile-generated makefiles
are not generated correctly for it. In the
resulting makefile.vc, for instance, I would
need to manually adjust WX_VERSION to 27 before
it builds. I did double-check that my WXWIN was
set to directory with correct wxWidgets version.

Also, can anyone tell me why makefile command-
line uses different symbols than when building
wxWidgets itself? Atleast for makefile.vc, I
need to specify WX_DEBUG=1 instead of DEBUG=1,
and so forth.

Thanks,
  Jaakko Salli

[wxCode-users] [ wxcode-Bugs-1540956 ] wxSqlite3 Invalid dependency

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

Bugs item #1540956, was opened at 2006-08-15 21:52
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=1540956&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
Submitted By: kavius (kavius)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxSqlite3 Invalid dependency

Initial Comment:
wxSqlite has a library dependency of wxmsw26d.lib, 
but this file is not created by the wxWidgets build.

Replacing this dependancy with wxmsw26d_core.dll, 
wxbase26d.dll, and wxmsw26d_adv.lib appears to allow 
the app to link.


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

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

[wxCode-users] XSTC initial release

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

I commited the XSTC first alpha release quite a while ago and I would have
let the list know, but the next day my computer died. Now I am running on an
old box I found. The alpha 1 release is useable but not very good, the
configuration stuff has not been implimented yet and only c++ for lexing.

Its goal is to automate code folding and lexer setting, along with coloring
and bracematching. It can be configured using text files including keywords.
Many lexers have default keywords should no word list be avalible. Most
correctly extentioned files should just come up colored right. So tweaks or
new extentions would be in a configuration file.

More information on the component website or in the source code.

-- 
Nuklear

[wxCode-users] [ wxcode-Patches-1526141 ] make "wxFont& font" const for void wxScintilla::StyleSetFont

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

Patches item #1526141, was opened at 2006-07-20 16:11
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=1526141&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
Submitted By: Jim Bentler (jimbentler)
Assigned to: Nobody/Anonymous (nobody)
Summary: make "wxFont& font" const for void wxScintilla::StyleSetFont

Initial Comment:
diff -ruN wxscintilla_1.69.2/include/wx/wxscintilla.h
wxscintilla_1.69.2-new/include/wx/wxscintilla.h
--- wxscintilla_1.69.2/include/wx/wxscintilla.h
2006-06-24 02:38:07.000000000 -0500
+++ wxscintilla_1.69.2-new/include/wx/wxscintilla.h   
 2006-07-20 15:54:25.591046920 -0500
@@ -3213,7 +3213,7 @@

     // Set style size, face, bold, italic, and
underline attributes from
     // a wxFont's attributes.
-    void StyleSetFont (int styleNum, wxFont& font);
+    void StyleSetFont (int styleNum, const wxFont& font);

     // Set all font style attributes at once.
     void StyleSetFontAttr (int styleNum, int
size,const wxString& faceName,
diff -ruN wxscintilla_1.69.2/src/wxscintilla.cpp
wxscintilla_1.69.2-new/src/wxscintilla.cpp
--- wxscintilla_1.69.2/src/wxscintilla.cpp     
2006-06-24 02:37:29.000000000 -0500
+++ wxscintilla_1.69.2-new/src/wxscintilla.cpp 
2006-07-20 15:50:52.996366224 -0500
@@ -2646,7 +2646,7 @@

 // Set style size, face, bold, italic, and underline
attributes from
 // a wxFont's attributes.
-void wxScintilla::StyleSetFont (int styleNum, wxFont&
font) {
+void wxScintilla::StyleSetFont (int styleNum, const
wxFont& font) {
 #ifdef __WXGTK__
     // Ensure that the native font is initialized
     int x, y;

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

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

[wxCode-users] [ wxcode-Patches-1526140 ] make wxFont& font arg const for wxScintilla::StyleSetFont

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

Patches item #1526140, was opened at 2006-07-20 16:05
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=1526140&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
Submitted By: Jim Bentler (jimbentler)
Assigned to: Nobody/Anonymous (nobody)
Summary: make wxFont& font arg const for wxScintilla::StyleSetFont

Initial Comment:
diff -ruN wxscintilla_1.69.2/include/wx/wxscintilla.h
wxscintilla_1.69.2-new/include/wx/wxscintilla.h
--- wxscintilla_1.69.2/include/wx/wxscintilla.h
2006-06-24 02:38:07.000000000 -0500
+++ wxscintilla_1.69.2-new/include/wx/wxscintilla.h   
 2006-07-20 15:54:25.591046920 -0500
@@ -3213,7 +3213,7 @@

     // Set style size, face, bold, italic, and
underline attributes from
     // a wxFont's attributes.
-    void StyleSetFont (int styleNum, wxFont& font);
+    void StyleSetFont (int styleNum, const wxFont& font);

     // Set all font style attributes at once.
     void StyleSetFontAttr (int styleNum, int
size,const wxString& faceName,
Files wxscintilla_1.69.2/lib/libwxscintilla.so and
wxscintilla_1.69.2-new/lib/libwxscintilla.so differ
diff -ruN wxscintilla_1.69.2/src/wxscintilla.cpp
wxscintilla_1.69.2-new/src/wxscintilla.cpp
--- wxscintilla_1.69.2/src/wxscintilla.cpp     
2006-06-24 02:37:29.000000000 -0500
+++ wxscintilla_1.69.2-new/src/wxscintilla.cpp 
2006-07-20 15:50:52.996366224 -0500
@@ -2646,7 +2646,7 @@

 // Set style size, face, bold, italic, and underline
attributes from
 // a wxFont's attributes.
-void wxScintilla::StyleSetFont (int styleNum, wxFont&
font) {
+void wxScintilla::StyleSetFont (int styleNum, const
wxFont& font) {
 #ifdef __WXGTK__
     // Ensure that the native font is initialized
     int x, y;

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

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

[wxCode-users] [ wxcode-Bugs-1525461 ] wxScintilla 1.63.2 - missing symbol "lmSpice"

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

Bugs item #1525461, was opened at 2006-07-19 12: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=1525461&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
Submitted By: Jim Bentler (jimbentler)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxScintilla 1.63.2 - missing symbol "lmSpice"

Initial Comment:
The final shared object has an unresolved symbol
"lmSpice".  Since you have the symbol is marked extern,
wxscintilla.so is created with this symbol unresolved.

You only find the error when you try to link to
wxscintilla.so.  (That is, after you have it
installed.)  Then, you get:
/usr/X11R6/lib/libwxscintilla.so: undefined reference
to `lmSpice' 

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

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

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

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

Hi,

      I've set the component as approved but I've removed the 'wx' 
prefix from the name of the directory. I.e. you can checkout 
wxCode/components/coolbar and work there...

Please refer to the maintainer guide for any problem (see 
http://wxcode.sf.net/maintguide.php) and post here any problem/doubt...

Thanks!
Francesco



Francesco Montorsi ha scritto:
> name: wxCoolBar
> wxversion: all
> category: window container,control,window layout,wrapper
> language: cpp
> description: wxCoolBar is a wrapper around the mickeysoft rebar control for use with the famous wxWidgets gui library. So developers can easily add the nice looking toolbars known from ms ie or other applications to their existing wxWidgets apps. Only if compiled against wxMSW on Win > 95 of course.
> location: wxcoolbar
> cdate: 2005-04-08
> id: 119
> status: beta
> docs: hand
> buildsys: makefiles
> extdep: none
> wiki: disabled
> wxport: wxmsw
> samples: 1
> approved: 0
> author: Martin Simon
> version: 0.9
> maintainerid: 43
> 
> Maintainer SF username: martinsfromb
> Maintainer name: MartinSfromB
> Maintainer mail address: mar...@pl...
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

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

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

Hi,

      I've set the component as approved.

Please refer to the maintainer guide for any problem (see 
http://wxcode.sf.net/maintguide.php) and post here any problem/doubt...

Thanks!
Francesco


Francesco Montorsi ha scritto:
> name: XSTC
> wxversion: all
> category: text processing,wrapper
> language: cpp
> description: This is a class designed to automate some of the fuctionality of scintilla through wxSTC or wxScintilla. it abstracts between thier api's so that one can use either without changing the program code. bracematching, folding and coloring is done automatically.
> location: xstc
> cdate: 2006-07-11
> id: 118
> status: alpha
> docs: doxygen
> buildsys: projectfiles
> extdep: wxStyledTextCtrl, wxScintilla, wxWidgets
> wiki: disabled
> wxport: all
> samples: 1
> approved: 0
> author: Nuklear Zelph
> version: 1.0
> maintainerid: 42
> 
> Maintainer SF username: datatab1
> Maintainer name: Nuklear Zelph
> Maintainer mail address: nuk...@gm...
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

Re: [wxCode-users] XSTC now what?

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

Otto Wyss wrote:
> Nuklear Zelph wrote:
>   
>> so what is to happen? did i just not wait long enough or did i miss 
>> something? i did go back and read the rules again.
>>
>>   
>>     
> I've answered to your first message in private but it seems you haven't 
> gotten it.
>
> Depending on what you want to achieve you might first try to enhance 
> wxScintilla when no state information (no configuration) is needed. Next 
> whatever doesn't belong into wxScintilla you might add to wxSTedit. Yet 
> if this still doesn't suit you, you can still add your own control to 
> wxCode and see if others like it. In general it's not a good idea to 
> create something "yet another" but sometimes there's no other choice.
>
> O. Wyss
>   
oh i see, this would move you further from the point of wxSTC. i have an 
alpha version here if you'd like to look.
tetristahedron.sourceforge.net/XSTC.7z

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

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

name: XSTC
wxversion: all
category: text processing,wrapper
language: cpp
description: This is a class designed to automate some of the fuctionality of scintilla through wxSTC or wxScintilla. it abstracts between thier api's so that one can use either without changing the program code. bracematching, folding and coloring is done automatically.
location: xstc
cdate: 2006-07-11
id: 118
status: alpha
docs: doxygen
buildsys: projectfiles
extdep: wxStyledTextCtrl, wxScintilla, wxWidgets
wiki: disabled
wxport: all
samples: 1
approved: 0
author: Nuklear Zelph
version: 1.0
maintainerid: 42

Maintainer SF username: datatab1
Maintainer name: Nuklear Zelph
Maintainer mail address: nuk...@gm...

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

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

name: wxCoolBar
wxversion: all
category: window container,control,window layout,wrapper
language: cpp
description: wxCoolBar is a wrapper around the mickeysoft rebar control for use with the famous wxWidgets gui library. So developers can easily add the nice looking toolbars known from ms ie or other applications to their existing wxWidgets apps. Only if compiled against wxMSW on Win > 95 of course.
location: wxcoolbar
cdate: 2005-04-08
id: 119
status: beta
docs: hand
buildsys: makefiles
extdep: none
wiki: disabled
wxport: wxmsw
samples: 1
approved: 0
author: Martin Simon
version: 0.9
maintainerid: 43

Maintainer SF username: martinsfromb
Maintainer name: MartinSfromB
Maintainer mail address: mar...@pl...

Re: [wxCode-users] XSTC now what?

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

Nuklear Zelph wrote:
> so what is to happen? did i just not wait long enough or did i miss 
> something? i did go back and read the rules again.
>
>   
I've answered to your first message in private but it seems you haven't 
gotten it.

Depending on what you want to achieve you might first try to enhance 
wxScintilla when no state information (no configuration) is needed. Next 
whatever doesn't belong into wxScintilla you might add to wxSTedit. Yet 
if this still doesn't suit you, you can still add your own control to 
wxCode and see if others like it. In general it's not a good idea to 
create something "yet another" but sometimes there's no other choice.

O. Wyss

-- 
Cross-platform: http://wyoguide.sf.net/index.php?page=Cross-platform.html

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

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

name: XSTC
wxversion: all
category: text processing,wrapper
language: cpp
description: This is a class designed to automate some of the fuctionality of scintilla through wxSTC or wxScintilla. it abstracts between thier api's so that one can use either without changing the program code. bracematching, folding and coloring is done automatically.
location: xstc
cdate: 2006-07-11
id: 118
status: alpha
docs: doxygen
buildsys: projectfiles
extdep: wxStyledTextCtrl, wxScintilla, wxWidgets
wiki: disabled
wxport: all
samples: 1
approved: 0
author: Nuklear Zelph
version: 1.0
maintainerid: 42

Maintainer SF username: datatab1
Maintainer name: Nuklear Zelph
Maintainer mail address: nuk...@gm...

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

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

name: wxCoolBar
wxversion: all
category: window container,control,window layout,wrapper
language: cpp
description: wxCoolBar is a wrapper around the mickeysoft rebar control for use with the famous wxWidgets gui library. So developers can easily add the nice looking toolbars known from ms ie or other applications to their existing wxWidgets apps. Only if compiled against wxMSW on Win > 95 of course.
location: wxcoolbar
cdate: 2005-04-08
id: 119
status: beta
docs: hand
buildsys: makefiles
extdep: none
wiki: disabled
wxport: wxmsw
samples: 1
approved: 0
author: Martin Simon
version: 0.9
maintainerid: 43

Maintainer SF username: martinsfromb
Maintainer name: MartinSfromB
Maintainer mail address: mar...@pl...

Re: [wxCode-users] XSTC now what?

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

Hi,
    sorry for not replying to the previous mail but I hoped that someone 
more expert about STC stuff would have done it...

Nuklear Zelph ha scritto:
> i logged in as a maintainer and found that XSTC existed there, but 
> nowhere else.
sorry, I don't understand. What you mean that it already exists ?
AFAIK there's only "wxstedit" as STC-related component.

> i am a little confused by that. was there suppose to be an 
> automatic message sent to the list?
automatic messages are sent when someone wants to submit a new component.

> also i checked out wxSTedit and i realized that it wasn't doing quite 
> what i thought it was inside. i hadn't actually looked in it when i 
> asked the question earlier.
> 
> all that my class is doing is handling code folding, brace matching, 
> coloring, and setting lexers based on file extension automatically. it 
> does not interfere with wxSTC/wxSci/Scintilla at all. it uses a copy 
> constructor too so a wxSci function can be called like using wxSci directly.
 >
> i did this in hopes it would make the creation of a usable edit instance 
> easier.
> 
> so what is to happen? did i just not wait long enough or did i miss 
> something? i did go back and read the rules again.
Just consider if:

1) it wouldn't be better to submit patches to the already existing 
wxstedit component so that it improves and targets your needs, too

2) if you think your component is somewhat completely different (I'm 
quite ignorant about STC - sorry), then please submit it as new 
component using the appropriate form

Thanks!
Francesco

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

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

Hi,

      I've set the component as approved but I've removed the 'wx' 
prefix from the name of the directory. I.e. you can checkout 
wxCode/components/dockingframe and work there...

Please refer to the maintainer guide for any problem (see 
http://wxcode.sf.net/maintguide.php) and post here any problem/doubt...

Thanks!
Francesco


Francesco Montorsi ha scritto:
> name: wxdockingframe
> wxversion: 2.6
> category: window container,dialog
> language: cpp
> description: a wxFrame that can be docked on the desktop. Such as a DockBar
> Can be docked Left, right, Top, bottom
> 
> works on windows, not yet ported to linux or mac.
> 
> location: wxdockingframe
> cdate: 2006-07-11
> id: 117
> status: alpha
> docs: doxygen
> buildsys: makefiles
> extdep: none
> wiki: disabled
> wxport: wxmsw
> samples: 1
> approved: 0
> author: barthelemy rolet
> version: 1.0
> maintainerid: 41
> 
> Maintainer SF username: bart59
> Maintainer name: barthelemy rolet
> Maintainer mail address: bar...@gm...
> 
> 
> 
> -------------------------------------------------------------------------
> 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] XSTC now what?

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

i logged in as a maintainer and found that XSTC existed there, but 
nowhere else. i am a little confused by that. was there suppose to be an 
automatic message sent to the list?

also i checked out wxSTedit and i realized that it wasn't doing quite 
what i thought it was inside. i hadn't actually looked in it when i 
asked the question earlier.

all that my class is doing is handling code folding, brace matching, 
coloring, and setting lexers based on file extension automatically. it 
does not interfere with wxSTC/wxSci/Scintilla at all. it uses a copy 
constructor too so a wxSci function can be called like using wxSci directly.

i did this in hopes it would make the creation of a usable edit instance 
easier.

so what is to happen? did i just not wait long enough or did i miss 
something? i did go back and read the rules again.

Nuklear

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

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

name: wxdockingframe
wxversion: 2.6
category: window container,dialog
language: cpp
description: a wxFrame that can be docked on the desktop. Such as a DockBar
Can be docked Left, right, Top, bottom

works on windows, not yet ported to linux or mac.

location: wxdockingframe
cdate: 2006-07-11
id: 117
status: alpha
docs: doxygen
buildsys: makefiles
extdep: none
wiki: disabled
wxport: wxmsw
samples: 1
approved: 0
author: barthelemy rolet
version: 1.0
maintainerid: 41

Maintainer SF username: bart59
Maintainer name: barthelemy rolet
Maintainer mail address: bar...@gm...

Re: [wxCode-users] [wxScript] can a script launched from wxScript use a binding e.g. wxPython? / multi-threading?

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

Hi,
    first of all, some words about wxScript: it's not completed yet - 
mainly because:
1) lua was the only real 'interpreter engine' which was easily 
embeddable in a C++ project; python gave me ton of memory leaks and I 
never got it fixed. Also, since wxLua project resurrected thanks to John 
Labenski and other developers, I preferred to give an hand to that 
project rather than focusing on wxScript.

2) CINT is old and makes interactions with loaded scripts very very 
difficult. OTOH the optimal UnderC project is almost dead - IMHO it 
would be a Great Thing to have a C++ interpreter (in general for the 
entire FOSS world!!) and AFAIR UnderC only needs some 'final touches' 
(E.g. a good build system and a good website) - I always wanted to help 
the author with these things but this point is the million-th point of 
my TODO list and days are limited to 24 hours unluckily.

3) perl support was contributed by Jerry Fath as I'm quite ignorant in 
perl unfortunately and I'm not sure how much it covers.

So, my advise is to currently use wxLua as interpreter to allow the 
users of your programs to extend it. Lua is coinceived exactly for that 
purpose and thus provide tools to do it.
Other interpreted languages like Perl or Python provide almost no API to 
the C++ layers which want to embed them as they are coinceived for 
writing entire applications in those languages.


Armel Asselin ha scritto:
> Hello,
>  
> i'm evaluating the opportunity of using wxScript from within my app to 
> allow my users to easily extend my soft.
> In order to reach maximum power through this integration I'd need two 
> big features:
> - multi-threading: two absolutely unrelated scripts should be able to be 
> executed in two different threads, is it the case with wxScript?
never tested. Maybe with some hacking you can do it but I have no idea 
about where to start with it, sorry.

> - GUI: from the "main thread" i'd like to show dialog boxes from the 
> scripts, is it possible to build a wxPython binding in my wx app and let 
> wxScript wxPython object show/manipulate them?
  wxScript was not intended to expose also the bindings to the wxWidgets 
API to the user (the scripter); just to expose the bindings of the 
program to extend. To do what you need you'll need to link against the 
entire wxPython library, too and obviously find some way to make all 
these things work together.

In conclusion my advice is: use wxLua :)
John is very expert in this field and wxLua is now working very well...

HTH,
Francesco