wxdevide-devs — Developer discussion for the project.

Re: [Wxdevide-devs] discussing wxDevIDE publicly

[Tony R. <tb...@gm...>]

Yes, I've had the exact same thoughts.

 I suppose my preference would be to wait until a week or so after we
release 7.0 to make any announcement about wxDevIDE. My thought is that we
shouldn't steal 7.0's thunder. Also, I'm not sure if people will be hesitant
to upgrade if they think there is a forthcoming new IDE.

In reality, when Nuklear and I tested wxDev-C++ with Wine under Linux, it
performed quite well. The biggest problem we had was that the makefiles
weren't properly written (since the libs and compilers were different on
Linux). However, it is possible to manually alter the makefile and get the
projects to compile and run just fine. So Wine is a viable (albeit not
ideal) alternative for the present time.

Finally, since Nuklear is the lead on wxDevIDE, I wanted to give him a
chance to do the formal announcement (unless he wishes to defer to one of
us).

Nuklear? Any thoughts?

-Tony


On Sat, Jul 25, 2009 at 4:56 PM, Esteban Aguilar B. <nab...@ya...>wrote:

> I said that I may not be that much involved with wxDevIDE, but I'm not sure
> of this yet; as wxDeCpp 7 is getting closer, I'm actually feeling a little
> more entusiastic about wxDevIDE again.
>
> That said, would it be a good idea to start discussing this project more
> publicly? As always, people ask (
> http://wxforum.shadonet.com/viewtopic.php?t=24962)  about wxDevCpp not
> being multiplatform and its kind of bad not giving any answers to them.
>
> Or, would it be better to wait for the final 7.0 relase of wxDevCpp to make
> the announcement?
>
>
>
>  ____________________________________________________________________________________
> ¡Obtén la mejor experiencia en la web!
> Descarga gratis el nuevo Internet Explorer 8.
> http://downloads.yahoo.com/ieak8/?l=e1
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Wxdevide-devs mailing list
> Wxd...@li...
> https://lists.sourceforge.net/lists/listinfo/wxdevide-devs
>

[Wxdevide-devs] discussing wxDevIDE publicly

[Esteban A. B. <nab...@ya...>]

I said that I may not be that much involved with wxDevIDE, but I'm not sure of this yet; as wxDeCpp 7 is getting closer, I'm actually feeling a little more entusiastic about wxDevIDE again.

That said, would it be a good idea to start discussing this project more publicly? As always, people ask (http://wxforum.shadonet.com/viewtopic.php?t=24962)  about wxDevCpp not being multiplatform and its kind of bad not giving any answers to them. 

Or, would it be better to wait for the final 7.0 relase of wxDevCpp to make the announcement?


      ____________________________________________________________________________________
¡Obtén la mejor experiencia en la web!
Descarga gratis el nuevo Internet Explorer 8. 
http://downloads.yahoo.com/ieak8/?l=e1

[Wxdevide-devs] integrated debugger option

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

http://sourceforge.net/projects/gdbrui/

i ran across this while trying to find a gui for gdb. might prove useful
with creating an integrated debugger. i don't know too much about what i am
talking about, but i remember joel saying something about di8fficulties
parsing gdb output.

Nuklear

Re: [Wxdevide-devs] my progress page

[Tony R. <tb...@gm...>]

http://sourceforge.net/projects/wx2xml/


I've started the basic framework for wx2xml, a program that will allow us to
convert wxDev-C++-designed wxFrames/wxDialogs to wxDevIDE. Initially, I was
just going to convert the .wxform files to xml, but eventually settled on
attempting to parse the C++/wxWidgets code directly and build an XML file
based on the C++ code. The upside is that it might be generic enough to
parse any C++/wxWidgets code (not just wxDev-C++ generated code) and produce
an XML for the visual designer.

The current code will parse a file like Project1Frm.cpp and return an XML
output (currently, in the wxMemo box). I still need to save the XML output
to file and make the GUI look pretty, but I figure it's at a point now where
I'm ready for others to comment (and possibly contribute).

-Tony


On Sun, Jul 5, 2009 at 9:11 PM, Nuklear Zelph <nuk...@gm...>wrote:

> hi, i don't want to be distracting to anyone not interested, so i am going
> to put up my progress/status/findings/etc on my website. right now i am
> looking at what has been started and getting to know the sources. i'm
> impressed at what i see already.
>
> http://nuklearzelph.org/
>
> to get to the wxDevIDE page click on the "Software Projects" link on the
> left bar and then "wxdevide". i hope i will continue to have time to work on
> this in upcoming months. anyway, unless i need some advice i will keep off
> the list for now. good work on the current rc ;)
>
> Nuklear
>

[Wxdevide-devs] my progress page

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

hi, i don't want to be distracting to anyone not interested, so i am going
to put up my progress/status/findings/etc on my website. right now i am
looking at what has been started and getting to know the sources. i'm
impressed at what i see already.

http://nuklearzelph.org/

to get to the wxDevIDE page click on the "Software Projects" link on the
left bar and then "wxdevide". i hope i will continue to have time to work on
this in upcoming months. anyway, unless i need some advice i will keep off
the list for now. good work on the current rc ;)

Nuklear

[Wxdevide-devs] have time again

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

wow! rc5. i guess its a lot better than having a buggy final version huh. i
have not tried it yet, i am still doing the long delayed house keeping i
have been ignoring. i lost my job this week, so in between job searching i
am catching up on the computer. i am going to do some more work on refining
the gui stuff. i might take a good look at the editor module too, maybe i
can figure out a good way to make a templated editor dialog and get a
working editor in with all the menu stuff.

Nuklear

Re: [Wxdevide-devs] [Wxdsgn-devs] Next release

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

work sucks, vehicles are giving me lotsa grief right now and i don't have
much time for anything. i won't be able to do much on the project for a
while. maybe things will settle down this next winter. if you want to go to
another project go right on ahead. you did amazing work on the plugin system
and it is much appreciated. your certainly welcome back later if you decide
to go elsewhere.

i won't give up on wxDevIDE, but if everyone has to dissperse or has not got
time when i finally do, i will work on the interface and editing stuff and
deal with the backend later. at least it can be a good friendly editor that
one can compile in something else. i think one of the biggest problems is
that the project aims to cross the ide and the form designer. the wxDev-C++
project aimed primarily at complimenting the already exsisting ide with a
form designer. its great that you guys fixed some of the ide's issues too. i
think based on what i understand that part of why things are drying up is
the direction shift to the ide. i don't know this though, that is just what
it looks like to me.

anyway whatever you and anyone else wants to do is fine with me. sourceforge
doesn't care if the project is active, so it is not going anywhere any time
soon.

Nuklear

Re: [Wxdevide-devs] wxDevIDE for 2.9 branch?

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

where we going to write an xml based template designer? i remember that
being mentioned from a while back. if that is so, we will not have to worry
about which version we build for. i am not sure how we would design such a
thing, but that may have been a brainstorm idea. it does make sense to build
for the current, since we already have a suitable designer for 2.6 and 2.8
in the wxDev-C++ releases.

Nuklear

On Thu, Apr 16, 2009 at 11:28 PM, Malcolm Nealon <m.n...@wa...>wrote:

> Hi all,
>
> Just checking in here. I noticed that loads of constants/flags have been
> changed between the wxWidgets 2.8 branch and the 2.9 branch.
>
> Consequently I was wondering if we should concentrate on the wx2.9
> branch for wxDevIDE? Or should we allow switching between branches?
> Allow users to choose which branch they wish to use for compiling?
>
> It could of course also be the case that when we are actually in a
> position to release the first version of wxDevIDE that 2.8 will no
> longer be supported by wxWidgets itself.
>
> What do you all think?
>
> Regards
> Mal
>
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Wxdevide-devs mailing list
> Wxd...@li...
> https://lists.sourceforge.net/lists/listinfo/wxdevide-devs
>

[Wxdevide-devs] wxDevIDE for 2.9 branch?

[Malcolm N. <m.n...@wa...>]

Hi all,

Just checking in here. I noticed that loads of constants/flags have been 
changed between the wxWidgets 2.8 branch and the 2.9 branch.

Consequently I was wondering if we should concentrate on the wx2.9 
branch for wxDevIDE? Or should we allow switching between branches? 
Allow users to choose which branch they wish to use for compiling?

It could of course also be the case that when we are actually in a 
position to release the first version of wxDevIDE that 2.8 will no 
longer be supported by wxWidgets itself.

What do you all think?

Regards
Mal

[Wxdevide-devs] got excited when i heard about a the wxDev-C++ release

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

so i took a look at the c++ sources and built the project and started
looking around.
and i found that the color buttons in the settings dialogs where not too
great. just stubs i'm sure.
so i looked at wxWidgets and didn't find anything too thrilling, the
colorpicker just seems kinda buggy and the delphi component looks a lot
better.
with nothing better to do i wrote a colorbutton component to use for that
purpose. it is not yet finished, but is useable. look here, the link is at
the bottom of the page:

http://nuklearzelph.org/index.php?id=26

i still need to write button state drawing code for the main button and i
have some ideas on making it a little more flexible in terms of layout. the
popup window positioning code is poor, seems wxWidgets does a bad job of
giving accurate screen coordinates or i am missing something that should be
obvious. it uses the initial color to set the default in the popup window
and syncronizes the colors between the dialog and popup. i will make both
methods optional and i need to add a button event since it is emulated with
wxControl.

i don't want to write the whole popup like it is in dev, since one can just
use the dialog with its custom color selection, but the popup is a lot more
convienient. its behavior needs some tweaking too. it is still in alpha, but
like i said, useable.

Nuklear

[Wxdevide-devs] Enhancement and Improvements to the wxDevIde designer

[Malcolm N. <m.n...@wa...>]

Hello All,

While working on my ever present screenwriting program, I came across a 
slight problem.

What I wanted to do was change the frame from one type to another. This 
is not obviously available in wxDev-Cpp, so I think that this might be 
sensible to include in the newer designer.

I also found a need to design a panel (which I intended to use for a 
wxAuiNotebookPage). This is also not easily done in wxDev-Cpp so I think 
that this should also be possible in the new designer.

Has anyone else any suggestions for improvements?


Best
Mal

Re: [Wxdevide-devs] Whats up?

[Malcolm N. <m.n...@wa...>]

Tony Reina wrote:
> We released RC4 a few days ago. It has AUI support which Mal added 
> since we'll likely being using it for the wxDevIDE GUI. You may want 
> to get RC4 if you're going to work with AUI.
>
> I don't think anyone has done more on the API docs. Feel free to give 
> it a try if you like. Esteban is on vacation. I think that by the 
> beginning of Feb we'll have a full wxDev-C++ 7.0 release.  After that 
> everyone will be moved to working on wxDevIDE 1.0.
>
> -Tony


I am also working on extending wxAui as we currently support it. I am 
adding control bars, which don't really exist in wxW, but are useful 
when designing multiple toolbars. I am also implementing wxAuiToolbar's 
to work with the control bars.

Basically the idea is that the user can add up to 4 bars, and should 
place them at the 4 edges of the frame/dialog. (of course if he only 
needs toolbars at the top, as wxDevIde does then he only needs to add 
one). He drops wxAuiToolbars into these control bars, then populates 
them as he desires, and finally adds a wxAuiPaneInfo component and sets 
the ToolBar flag. The intention is that the layout in the designer will 
be replicated in the final program, but I don't see this as a fixed 
requirement for this release. wxToolbars remain functioning as they 
currently do (being parented to the frame and expanding to the full 
width of the frame).

I also wanted to add support for adding wxAuiPaneInfo components to 
things such as tree/edit/list/grid controls but the current 
implementation of wxDevC++ is preventing this (which will need to be 
adressed when we design for wxDevIde).

Curently the simplest way to get things such as tree/edit/list/grid 
controls being controlled by wxAui is to drop a panel, a wxAuiPaneInfo, 
then a sizer and the required component. It functions quite well.

I have done some work on making the wxDevIde dialogs/frames sizer based 
instead of the fixed position used previously (a residue from the delphi 
design), and will return to this as soon as I get this current addition 
to wxAui support in wxDevC++ implemented. (I also am going to move my 
wxForms based project over to wxDevC++/wxDevIde (assuming we will still 
be able to read the .wxform from wxDevC++ in wxDevIde).

I am also pleased to see that the wxDevs are looking at implementing a 
wxButton with image support, which solves a problem I foresaw with using 
the wxCustomButton from the designer (accelerator support).

So all in all I have been/am pretty busy wrt wxDevC++ and wxDevIde (can 
we shorten that to wxDI ??)

Great to see Kinming back, and on both projects.

Best wishes to all and a Happy New Year all round.

Mal

Re: [Wxdevide-devs] Whats up?

[<Nuk...@gm...>]

ok, sounds good. not sure if i will get around to AUI before then, but i  
will see. i want to do the basic revamp on XSTC before i do anything else  
so i have a better release out to work with.

On Jan 9, 2009 9:10pm, Tony Reina <tb...@gm...> wrote:
> We released RC4 a few days ago. It has AUI support which Mal added since  
we'll likely being using it for the wxDevIDE GUI. You may want to get RC4  
if you're going to work with AUI.
>
> I don't think anyone has done more on the API docs. Feel free to give it  
a try if you like. Esteban is on vacation. I think that by the beginning of  
Feb we'll have a full wxDev-C++ 7.0 release. After that everyone will be  
moved to working on wxDevIDE 1.0.
>
>
> -Tony
>
>
> On Fri, Jan 9, 2009 at 6:19 PM, Nuklear Zelph nuk...@gm...>  
wrote:
>
> i saw the message from kin ming about an rc3 bug and wanting to code, so  
i added his username to the wxdevide project. i wasn't sure before since he  
didn't say anything.
>
> also, what is the status of wxDev7? i noticed something about rc4 but  
don't remember where i saw it.
>
>
>
> has anyone come up with an api proposal? looks like its been on hold for  
a while since i have not heard anything of it.
>
> i figured out how to install xp on my x64 machine so i finally have a  
stable build system and i am getting back on the band wagon. i finally gave  
up on things because even gcc was giving me hell. now that i know i can  
install a 32 bit kernel i will just go back to fc6 and forget about the x64  
systems for now. so i was very bored for two months.
>
>
>
> so i am starting on XSTC again. i looked at wxSTed and i realized it may  
not be as smooth integrating XSTC into it since it will/can shut off  
scintilla interfaces. also it seems to be designed to "be" the main editor  
whereas we already have one. (dev) so i think it would be better to just  
build our own editor interface. i think most of wxScintilla is pretty good,  
but some functionality like alpha and HomeEX is not a standard option in  
editors. those can be wrapped and put into the editor dialog.
>
>
>
> i am going to rework the XSTC build options to use a config.h file and  
allow for more control over the "installed options" as well as add some  
more general functionality. i am going to take a little out of wxSTed since  
it had a couple things i liked and i am going to start writing an 'e'  
subsystem after i get this other stuff done.
>
>
>
> i am wondering if it would be a good idea to hack on the main gui some  
like adding aui. since nobody is really (seem to be anyway) working on that  
project at the moment.
>
> Nuklear
>
>
>  
------------------------------------------------------------------------------
>
> Check out the new SourceForge.net Marketplace.
>
> It is the best place to buy or sell services for
>
> just about anything Open Source.
>
> http://p.sf.net/sfu/Xq1LFB
> _______________________________________________
>
> Wxdevide-devs mailing list
>
> Wxd...@li...
>
> https://lists.sourceforge.net/lists/listinfo/wxdevide-devs
>
>
>
>
>

Re: [Wxdevide-devs] Whats up?

[Tony R. <tb...@gm...>]

We released RC4 a few days ago. It has AUI support which Mal added since
we'll likely being using it for the wxDevIDE GUI. You may want to get RC4 if
you're going to work with AUI.

I don't think anyone has done more on the API docs. Feel free to give it a
try if you like. Esteban is on vacation. I think that by the beginning of
Feb we'll have a full wxDev-C++ 7.0 release.  After that everyone will be
moved to working on wxDevIDE 1.0.

-Tony


On Fri, Jan 9, 2009 at 6:19 PM, Nuklear Zelph <nuk...@gm...>wrote:

> i saw the message from kin ming about an rc3 bug and wanting to code, so i
> added his username to the wxdevide project. i wasn't sure before since he
> didn't say anything.
>
> also, what is the status of wxDev7? i noticed something about rc4 but don't
> remember where i saw it.
>
> has anyone come up with an api proposal? looks like its been on hold for a
> while since i have not heard anything of it.
>
> i figured out how to install xp on my x64 machine so i finally have a
> stable build system and i am getting back on the band wagon. i finally gave
> up on things because even gcc was giving me hell. now that i know i can
> install a 32 bit kernel i will just go back to fc6 and forget about the x64
> systems for now. so i was very bored for two months.
>
> so i am starting on XSTC again. i looked at wxSTed and i realized it may
> not be as smooth integrating XSTC into it since it will/can shut off
> scintilla interfaces. also it seems to be designed to "be" the main editor
> whereas we already have one. (dev) so i think it would be better to just
> build our own editor interface. i think most of wxScintilla is pretty good,
> but some functionality like alpha and HomeEX is not a standard option in
> editors. those can be wrapped and put into the editor dialog.
>
> i am going to rework the XSTC build options to use a config.h file and
> allow for more control over the "installed options" as well as add some more
> general functionality. i am going to take a little out of wxSTed since it
> had a couple things i liked and i am going to start writing an 'e' subsystem
> after i get this other stuff done.
>
> i am wondering if it would be a good idea to hack on the main gui some like
> adding aui. since nobody is really (seem to be anyway) working on that
> project at the moment.
>
> Nuklear
>
>
> ------------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
> _______________________________________________
> Wxdevide-devs mailing list
> Wxd...@li...
> https://lists.sourceforge.net/lists/listinfo/wxdevide-devs
>
>

[Wxdevide-devs] Whats up?

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

i saw the message from kin ming about an rc3 bug and wanting to code, so i
added his username to the wxdevide project. i wasn't sure before since he
didn't say anything.

also, what is the status of wxDev7? i noticed something about rc4 but don't
remember where i saw it.

has anyone come up with an api proposal? looks like its been on hold for a
while since i have not heard anything of it.

i figured out how to install xp on my x64 machine so i finally have a stable
build system and i am getting back on the band wagon. i finally gave up on
things because even gcc was giving me hell. now that i know i can install a
32 bit kernel i will just go back to fc6 and forget about the x64 systems
for now. so i was very bored for two months.

so i am starting on XSTC again. i looked at wxSTed and i realized it may not
be as smooth integrating XSTC into it since it will/can shut off scintilla
interfaces. also it seems to be designed to "be" the main editor whereas we
already have one. (dev) so i think it would be better to just build our own
editor interface. i think most of wxScintilla is pretty good, but some
functionality like alpha and HomeEX is not a standard option in editors.
those can be wrapped and put into the editor dialog.

i am going to rework the XSTC build options to use a config.h file and allow
for more control over the "installed options" as well as add some more
general functionality. i am going to take a little out of wxSTed since it
had a couple things i liked and i am going to start writing an 'e' subsystem
after i get this other stuff done.

i am wondering if it would be a good idea to hack on the main gui some like
adding aui. since nobody is really (seem to be anyway) working on that
project at the moment.

Nuklear

Re: [Wxdevide-devs] [Wxdsgn-devs] RC3 Bug?

[Tony R. <re...@al...>]

kinming,

We had assumed that you wanted to be part of the wxDevIDE developers.
Looking forward to the new code completion stuff.

I posted RC4 a few days ago. Could you give it a try and see if it has
solved the bug you are reporting?

Thanks.
-Tony



On Thu, Jan 8, 2009 at 11:43 AM, kinming2003 <kin...@16...> wrote:

> Hi, all.
>
>   Sorry for being silence all that long. It's been a busy semester, all the experiments and homework drove me crazy. Now that the holiday comes, I have lots of time to do things I interest in.
>
>   Since the WxDevIDE project have been started, I would like to join you. The mailinglist admin may notice that I subscribed to the mailing list at the very beginning. I would like to do the code complete part. I already have a plan that we use 2 Sqlite3 database and try to make it as good as M$ intellisense.
>
>   Last night I checked out the source and try to build it, an error occured and I am not able to fix it. I don't even sure it is a bug in WxDevCpp--RC3 or it's something about the path (I installed WxDevCpp in "D:\program files\Dev-cpp").  The problem happened when I open devcpp.dev using wxDevCpp-RC3.
>    Here is the bug report(major part):
>
> date/time         : 2009-01-08, 23:19:31, 203ms
> computer name     : KIN
> user name         : Administrator <admin>
> registered owner  : 微软用户 / 微软中国
> operating system  : Windows XP Service Pack 2 build 2600
> system language   : Chinese
> system up time    : 6 hours 31 minutes
> program up time   : 59 seconds
> processor         : Intel(R) Celeron(R) D CPU 3.06GHz
> physical memory   : 1240/1917 MB (free/total)
> free disk space   : (C:) 860.97 MB (D:) 1023.98 MB
> display mode      : 1280x960, 32 bit
> process id        : $9a4
> allocated memory  : 30.20 MB
> executable        : wxdevcpp.exe
> exec. date/time   : 2008-11-24 16:04
> version           : 7.0.0.42
> compiled with     : BCB6
> madExcept version : 3.0d
> contact name      : Kin
> contact email     : kin...@16...
> callstack crc     : $55903c02, $e42904bf, $516bb319
> exception number  : 1
> exception class   : EFCreateError
>
> exception message : Cannot create file D:\Program Files\Dev-Cpp\Output\MingW\DevCpp.exe.Manifest.
>
> main thread ($dd8):
> 4002f1fd rtl60.bpl    Classes                TFileStream.Create
> 4002f174 rtl60.bpl    Classes                TFileStream.Create
> 4002df4d rtl60.bpl    Classes                TStrings.SaveToFile
> 0058fdd0 wxdevcpp.exe project            791 TProject.BuildPrivateResource
> 0058efa5 wxdevcpp.exe project            568 TProject.Create
> 00559af4 wxdevcpp.exe main              3281 TMainForm.OpenProject
> 0055b9f6 wxdevcpp.exe main              3899 TMainForm.actOpenExecute
> 400387ef rtl60.bpl    Classes                TBasicAction.Execute
> 400e71a1 vcl60.bpl    Actnlist               TContainedAction.Execute
> 400e7e39 vcl60.bpl    Actnlist               TCustomAction.Execute
> 400386c4 rtl60.bpl    Classes                TBasicActionLink.Execute
> 400fd317 vcl60.bpl    Menus                  TMenuItem.Click
> 400fe7db vcl60.bpl    Menus                  TMenu.DispatchCommand
> 400f0b8b vcl60.bpl    Forms                  TCustomForm.WMCommand
> 401077ec vcl60.bpl    Controls               TControl.WndProc
> 4010a9a3 vcl60.bpl    Controls               TWinControl.WndProc
> 400eec6d vcl60.bpl    Forms                  TCustomForm.WndProc
> 4010a620 vcl60.bpl    Controls               TWinControl.MainWndProc
> 00505bdf wxdevcpp.exe JvDockControlForm 2525 TJvDockBaseControl.WindowProc
> 0050927d wxdevcpp.exe JvDockControlForm 4631 TJvDockServer.WindowProc
> 4010a620 vcl60.bpl    Controls               TWinControl.MainWndProc
> 77d196c2 user32.dll                          DispatchMessageA
> 400f582f vcl60.bpl    Forms                  TApplication.ProcessMessage
> 400f5866 vcl60.bpl    Forms                  TApplication.HandleMessage
> 400f5a86 vcl60.bpl    Forms                  TApplication.Run
> 005b6dba wxdevcpp.exe devcpp             261 initialization
>
> thread $48c (TdevMonitorThread):
> 7c92eb94 ntdll.dll                         KiFastSystemCallRet
> 7c92e9a9 ntdll.dll                         NtWaitForMultipleObjects
> 7c8094dc kernel32.dll                      WaitForMultipleObjectsEx
> 7c80a070 kernel32.dll                      WaitForMultipleObjects
> 004ba413 wxdevcpp.exe devMonitorThread 194 TdevMonitorThread.Execute
> 00448f4f wxdevcpp.exe madExcept            HookedTThreadExecute
> 00448e31 wxdevcpp.exe madExcept            CallThreadProcSafe
> 00448e9b wxdevcpp.exe madExcept            ThreadExceptFrame
> >> created by main thread ($dd8) at:
> 004ba13a wxdevcpp.exe devMonitorThread 103 TdevMonitorThread.Create
>
> thread $2b4:
> 7c92eb94 ntdll.dll  KiFastSystemCallRet
> 7c92d85a ntdll.dll  NtDelayExecution
>
> thread $d80:
> 7c92eb94 ntdll.dll  KiFastSystemCallRet
> 7c92e319 ntdll.dll  NtRemoveIoCompletion
>
> thread $eb8:
> 7c92eb94 ntdll.dll  KiFastSystemCallRet
> 7c92e319 ntdll.dll  NtRemoveIoCompletion
>
> modules:
> 00400000 wxdevcpp.exe 7.0.0.42         D:\Program Files\Dev-Cpp
>
> 02920000 wxdsgn.bpl   7.0.0.14         D:\Program Files\Dev-Cpp\plugins\wxdsgn
> 20000000 xpsp2res.dll 5.1.2600.2180    C:\WINDOWS\system32
> 40000000 rtl60.bpl    6.0.6.243        D:\Program Files\Dev-Cpp
> 400b0000 vcl60.bpl    6.0.6.240        D:\Program Files\Dev-Cpp
> 5adc0000 UxTheme.dll  6.0.2900.2180    C:\WINDOWS\system32
> 5fdd0000 NETAPI32.dll 5.1.2600.3462    C:\WINDOWS\system32
> 62c20000 LPK.DLL      5.1.2600.2180    C:\WINDOWS\system32
> 68bf0000 hhctrlui.dll 4.74.9273.0      C:\WINDOWS\system32\mui\0804
> 71a10000 WS2HELP.dll  5.1.2600.2180    C:\WINDOWS\system32
> 71a20000 WS2_32.dll   5.1.2600.2180    C:\WINDOWS\system32
> 71a40000 wsock32.dll  5.1.2600.2180    C:\WINDOWS\system32
> 71a90000 mpr.dll      5.1.2600.2180    C:\WINDOWS\system32
> 72f70000 winspool.drv 5.1.2600.2180    C:\WINDOWS\system32
> 73640000 msctfime.ime 5.1.2600.2180    C:\WINDOWS\system32
> 73fa0000 USP10.dll    1.420.2600.2180  C:\WINDOWS\system32
> 74680000 MSCTF.dll    5.1.2600.3284    C:\WINDOWS\system32
> 74c90000 oledlg.dll   5.1.2600.3016    C:\WINDOWS\system32
> 75430000 CRYPTUI.dll  5.131.2600.2180  C:\WINDOWS\system32
> 759d0000 USERENV.dll  5.1.2600.2180    C:\WINDOWS\system32
> 75ef0000 browseui.dll 6.0.2900.3462    C:\WINDOWS\system32
> 76060000 SETUPAPI.dll 5.1.2600.2180    C:\WINDOWS\system32
> 76300000 imm32.dll    5.1.2600.2180    C:\WINDOWS\system32
> 76320000 comdlg32.dll 6.0.2900.2180    C:\WINDOWS\system32
> 76570000 CSCDLL.dll   5.1.2600.2180    C:\WINDOWS\System32
> 76590000 cscui.dll    5.1.2600.2180    C:\WINDOWS\System32
> 765e0000 CRYPT32.dll  5.131.2600.3272  C:\WINDOWS\system32
> 76680000 WININET.dll  6.0.2900.3462    C:\WINDOWS\system32
> 76750000 SHFolder.dll 6.0.2900.2180    C:\WINDOWS\system32
> 76960000 ntshrui.dll  5.1.2600.2180    C:\WINDOWS\system32
> 76990000 ole32.dll    5.1.2600.2726    C:\WINDOWS\system32
> 76af0000 ATL.DLL      3.5.2284.0       C:\WINDOWS\system32
> 76b10000 winmm.dll    5.1.2600.2180    C:\WINDOWS\system32
> 76c00000 WINTRUST.dll 5.131.2600.2180  C:\WINDOWS\system32
> 76c60000 IMAGEHLP.dll 5.1.2600.2180    C:\WINDOWS\system32
> 76d70000 appHelp.dll  5.1.2600.2180    C:\WINDOWS\system32
> 76db0000 MSASN1.dll   5.1.2600.2180    C:\WINDOWS\system32
> 76f30000 WLDAP32.dll  5.1.2600.2180    C:\WINDOWS\system32
> 76fa0000 CLBCATQ.DLL  2001.12.4414.308 C:\WINDOWS\system32
> 77020000 COMRes.dll   2001.12.4414.258 C:\WINDOWS\system32
> 770f0000 oleaut32.dll 5.1.2600.3266    C:\WINDOWS\system32
>
> 77180000 comctl32.dll 6.0.2900.2982    C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03
> 77bd0000 version.dll  5.1.2600.2180    C:\WINDOWS\system32
> 77be0000 msvcrt.dll   7.0.2600.2180    C:\WINDOWS\system32
> 77d10000 user32.dll   5.1.2600.3099    C:\WINDOWS\system32
> 77da0000 advapi32.dll 5.1.2600.2180    C:\WINDOWS\system32
> 77e50000 RPCRT4.dll   5.1.2600.3173    C:\WINDOWS\system32
> 77ef0000 GDI32.dll    5.1.2600.3466    C:\WINDOWS\system32
> 77f40000 SHLWAPI.dll  6.0.2900.3462    C:\WINDOWS\system32
> 77fc0000 Secur32.dll  5.1.2600.2180    C:\WINDOWS\system32
> 7c800000 kernel32.dll 5.1.2600.3119    C:\WINDOWS\system32
> 7c920000 ntdll.dll    5.1.2600.2180    C:\WINDOWS\system32
> 7d590000 SHELL32.dll  6.0.2900.3402    C:\WINDOWS\system32
> 7e550000 shdocvw.dll  6.0.2900.3462    C:\WINDOWS\system32
> 7e6d0000 hhctrl.ocx   5.2.3790.2847    C:\WINDOWS\system32
>
> processes:
> 000 Idle
> 004 System         normal
> 2ec smss.exe       normal C:\WINDOWS\system32
> 32c csrss.exe
> 344 winlogon.exe   high   C:\WINDOWS\system32
> 370 services.exe   normal C:\WINDOWS\system32
> 37c lsass.exe      normal C:\WINDOWS\system32
> 418 svchost.exe    normal C:\WINDOWS\system32
> 454 svchost.exe
> 4f8 svchost.exe    normal C:\WINDOWS\System32
> 5a4 svchost.exe
> 5fc svchost.exe
> 654 scardsvr.exe
>
> 674 sched.exe      normal D:\Program Files\Avira\AntiVir PersonalEdition Classic
>
> 75c avguard.exe    normal D:\Program Files\Avira\AntiVir PersonalEdition Classic
> 768 cmdagent.exe   normal C:\Program Files\COMODO\Firewall
> 7b8 nvsvc32.exe    normal C:\WINDOWS\system32
> 4dc Explorer.EXE   normal C:\WINDOWS
> 62c RTHDCPL.EXE    normal C:\WINDOWS
> 260 cfp.exe        normal C:\Program Files\COMODO\Firewall
> 5f4 VStart.exe     normal D:\Program Files\VStart50
>
> 1fc avgnt.exe      normal D:\Program Files\Avira\AntiVir PersonalEdition Classic
> 54c ctfmon.exe     normal C:\WINDOWS\system32
> 464 FishDesk.exe   normal D:\Program Files\鱼鱼桌面
> ec0 conime.exe     normal C:\WINDOWS\system32
> 3b0 QQ.exe         normal D:\Program Files\Tencent\qq
> 938 TXPlatform.exe normal D:\Program Files\Tencent\qq
> f8c svchost.exe    normal C:\WINDOWS\System32
> a9c TTPlayer.exe   normal C:\Program Files\TTPlayer
> 694 firefox.exe    normal D:\Program Files\Mozilla Firefox
> 9a4 wxdevcpp.exe   normal D:\Program Files\Dev-Cpp
>
>
> disassembling:
> [...]
>
> 4002f1ee   mov     eax, [$400266cc]       ; Classes.EFCreateError.Create (rtl60.bpl)
>
> 4002f1f3   call    -$1c4c8 ($40012d30)    ; Sysutils.Exception.Create (rtl60.bpl)
> 4002f1f3
> 4002f1f8   call    -$29219 ($40005fe4)    ; System.@RaiseExcept
>  (rtl60.bpl)
> 4002f1f8
> 4002f1fd > jmp     loc_4002f23e
> 4002f1fd
> 4002f1fd ; ---------------------------------------------------------
> 4002f1fd
> 4002f1ff loc_4002f1ff:
> 4002f1ff   movzx   edx, di
> [...]
>
>
>                                        --Kin
>                                      Best
>
> ------------------------------
> 《大话西游外传》贺岁新作，送豪宅、送你5000元压岁钱<http://allyes.nie.163.com/main/adfclick?db=afanie&bid=1698,833,77&cid=148,4,1&sid=1804&show=ignore&url=http://xyw.16%0A3.com/2008/heka/>
>
> ------------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It is the best place to buy or sell services for
> just about anything Open Source.
> http://p.sf.net/sfu/Xq1LFB
> _______________________________________________
> Wxdsgn-devs mailing list
> Wxd...@li...
> https://lists.sourceforge.net/lists/listinfo/wxdsgn-devs
>
>

Re: [Wxdevide-devs] New dev file format

[Esteban A. B. <nab...@ya...>]

Ditto on Mal's opinion. But the problem could be.. what if we need more things than what Bakefile or CMake offers? 
I think one option is to have our own .dev file format (XML based on this new version), that just refers to the proper Bakefile or whatever for compiler settings. Kind of like those new office suit file formats, that are zipped files that contains several files: a main XML file and several JPGs, fonts, etc, that compound the document.Remember that wxDevIDE may (and should at some point, if succesful) support not only C++ projects, but all kind of things. A "modular" .dev file would make this easier.
--- El sáb 25-oct-08, Malcolm Nealon <m.n...@wa...> escribió:
De: Malcolm Nealon <m.n...@wa...>
Asunto: Re: [Wxdevide-devs] New dev file format
A: re...@al...
Cc: "wxDevIde Developers" <wxd...@li...>
Fecha: sábado, 25 octubre, 2008, 3:09 am

Tony Reina wrote:
> Now that I'm looking at the MSVC file importer code, it occurred to me

> that I'd really like to update the .dev file format when we move to 
> wxDevIDE. In particular, the compiler switches are just a string of 
> characters (e.g. "000a0001b0000000"). I hate that. It's
pretty hard to 
> know what "a" means or what switch it refers to.
> I'm wondering whether we can kill several birds with one stone. What 
> if we use Bakefile (or CMake) as the new .dev file format? So a 
> Bakefile will hold the project information (or workspace, or whatever 
> you want to call it). When we hit "Compile" or "Rebuild
All" the 
> makefile is autogenerated by the Bakefile system. So we still use 
> makefile, but we let Bakefile generate them.
> The advantage is that this is much less code for us to handle (no 
> makefile generation code). Also, projects are more easily ported to 
> other OS's and compiler sets (since Bakefile is portable).
> -Tony


I'm not saying "do it", but I do think that it is worth
investigating. I 
would probably prefer bakefile as opposed to cmake, since this is the 
"official" wxWidgets way, but whichever way you want to investigate
is 
OK by me.

Mal

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Wxdevide-devs mailing list
Wxd...@li...
https://lists.sourceforge.net/lists/listinfo/wxdevide-devs



      ____________________________________________________________________________________
¡Todo sobre Amor y Sexo!
La guía completa para tu vida en Mujer de Hoy.                       
http://mujerdehoy.telemundo.yahoo.com/

Re: [Wxdevide-devs] New dev file format

[Malcolm N. <m.n...@wa...>]

Tony Reina wrote:
> Now that I'm looking at the MSVC file importer code, it occurred to me 
> that I'd really like to update the .dev file format when we move to 
> wxDevIDE. In particular, the compiler switches are just a string of 
> characters (e.g. "000a0001b0000000"). I hate that. It's pretty hard to 
> know what "a" means or what switch it refers to.
> I'm wondering whether we can kill several birds with one stone. What 
> if we use Bakefile (or CMake) as the new .dev file format? So a 
> Bakefile will hold the project information (or workspace, or whatever 
> you want to call it). When we hit "Compile" or "Rebuild All" the 
> makefile is autogenerated by the Bakefile system. So we still use 
> makefile, but we let Bakefile generate them.
> The advantage is that this is much less code for us to handle (no 
> makefile generation code). Also, projects are more easily ported to 
> other OS's and compiler sets (since Bakefile is portable).
> -Tony


I'm not saying "do it", but I do think that it is worth investigating. I 
would probably prefer bakefile as opposed to cmake, since this is the 
"official" wxWidgets way, but whichever way you want to investigate is 
OK by me.

Mal

[Wxdevide-devs] New dev file format

[Tony R. <tb...@gm...>]

Now that I'm looking at the MSVC file importer code, it occurred to me that
I'd really like to update the .dev file format when we move to wxDevIDE. In
particular, the compiler switches are just a string of characters (e.g.
"000a0001b0000000"). I hate that. It's pretty hard to know what "a" means or
what switch it refers to.

I'm wondering whether we can kill several birds with one stone. What if we
use Bakefile (or CMake) as the new .dev file format? So a Bakefile will hold
the project information (or workspace, or whatever you want to call it).
When we hit "Compile" or "Rebuild All" the makefile is autogenerated by the
Bakefile system. So we still use makefile, but we let Bakefile generate
them.

The advantage is that this is much less code for us to handle (no makefile
generation code). Also, projects are more easily ported to other OS's and
compiler sets (since Bakefile is portable).

-Tony

[Wxdevide-devs] XSTC sample wth exporting

[Edward T. <edw...@ti...>]

I'm attaching a link to a small sample I am working on using XSTC. At
present the sample only does a couple of things, but in developing it I
am looking closer at the code for XSTC and extending it where needed.
The sample is built with wxWidgets 2.9.0, it should build with earlier
versions but features like colour exporting will not be available.

 

I have built 3 exporters HTML (which supports version 4.0), xhtml, and
rtf.

 

I have added a few extra functions into the XSTC code to allow the user
to query which styles are built in for colour coding and then selecting
a style by name. I have added one extra style Matrix to see how easy it
would be. I have also added a function ReLex. Before this the coulour
styles were only set when the code was lexed, so to change the style you
needed to reload the page (comment out the call to ReLex to see what I
mean). I plan to spend some time adding functions to this code to make
it support some of the features available in DevCpp, then hopefully it
will make it easier to turn into a plugin.

 

The link to the code is here

 

http://myweb.tiscali.co.uk/monoworld/temp/sample.zip

 

Sof.T

[Wxdevide-devs] XSTC

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

sorry, i have not had much time to mess with it lately. i ran into some
issues with my video hardware and when i changed to another one it screwed
up ubuntu so it would only show a very small screen.  i ended up changing
from nvidia to ati. so i tried reinstalling, but i had a second hard drive
in and it messed up the boot loader. i am finding that fedora is more to my
liking, it would have not messed up since i had tried the same thing in the
past. i just hope they don't screw up 10 too.

i have a truck to get ready to roll. need to check out a wheel bearing and
ball joints. i have been cleaning up the yard to get ready for winter and
tring to get a hold of a motorcycle engine and sell some of my extra stuff.
i was figuring that we where waiting for a release on wxdsgn and a decent
draft of the plugin system before we got too serious. work has not been too
great lately either, so i have had to work late a lot.

i am hoping to get ubuntu installed correctly again this weekend and then
maybe i can do a little invesigating.

i have not messed witht he svn on wxcode since it was made. i did move the
header on my local copy of XSTC. i think i tried fixing the website, but
someone screwed with the database or something since it still didn't come up
for the component on wxcode.

anyway i just wasn't getting too excited becuase y'all where working on
getting 7 out last i knew.

Nuklear

[Wxdevide-devs] ATTN: Nuklear How is the xstc adapting coming?

[Malcolm N. <m.n...@wa...>]

Hi Nuke,

Forgive me if I am wrong, but ISTR that you would be investigating 
replacing wxStyledTextCtrl with XSTC in SOF.T's code.

IF so, could you give me an update as to your position? Has anything 
happened? Or should we proceed with wxStyledTextCtrl or wxSteditCtrl?

Best
Mal

[Wxdevide-devs] ATTN: NUKLEAR xstc.h file location

[Malcolm N. <m.n...@wa...>]

Hi Nuke,

Would you mind placing your xstc.h file in a folder include/wx/xstc in 
the svn tree?

I know that this is being pedantic, but it is the accepted wxWidgets 
philosophy.

It would then make replacing wx/stc/stc.h by wx/xstc/xstc.h a mostly 
trivial matter in SofT's code.

Thanks
Mal

Re: [Wxdevide-devs] code license consern

[Tony R. <tb...@gm...>]

>
>
> i for one do not care about making money from wxDevIDE. i just want it open
> sourced, but i don't care if someone modifies it and distributes their
> version. as long as whomever gets it knows where to find the original and
> knows who created it. that way creep can only make a couple bucks before it
> costs him too much to keep up his server.
>
> this has been enlightening to understand licenses anyway.
>
>
Yes, I think that's clear.

To stress the point, AFAIK ALL open source licenses require the creep to not
only acknowledge that he got some or all of our code, but also that he has
some method for his clients to download the code he took.

In the case of the Code:Blocks creep, I think his biggest error was that he
neglected to mention that he grabbed the C:B source, changed a few window
captions, and voila!

-Tony

Re: [Wxdevide-devs] code license consern

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

On Mon, Oct 13, 2008 at 7:56 PM, Nuklear Zelph <nuk...@gm...>wrote:

> whoa! what a mess.
>
> my biggest concern is just not to have the project origins mis represented.
> so creep makes people think he built it and then gets money. sham is not
> something that occurred to me, but we do have quite a few options available
> to sham.
>
> i for one do not care about making money from wxDevIDE. i just want it open
> sourced, but i don't care if someone modifies it and distributes their
> version. as long as whomever gets it knows where to find the original and
> knows who created it. that way creep can only make a couple bucks before it
> costs him too much to keep up his server.
>
> this has been enlightening to understand licenses anyway.
>
> yeah, hope that is clear enough :)
>
> Nuklear
>