User forums > Embedded development
Debugging with Segger JLINK
Grad:
--- Quote from: oBFusCATed on March 27, 2013, 11:56:04 pm ---Why wxWidgets is related to embedded develoment?
--- End quote ---
It is not, well, ... it is equally related to embedded as desktop :)
I have changed a lot of wxWidgets code on the MSW part but also generic. There were some annoying bugs (like in the statusbar handling of text) but I also freely added stuff or changed behaviour of it.
I didn't like, as an example, the handling of menus. Why different approach for a menu with checkboxes than with icon's? But the changes of wxWidgets also changed the rest of the code, different function calls etc etc.
The objectives are a little bit different here. The goal (mission statement is a bit heavy I guess) is to make an user friendly embedded development suite for windows. An embedded development suite without all kind of tweaks etc. Working out of the box with the same experiences as if you would use uVision (my favourite at that moment). Once started, almost 2 years ago, I came across all kind of problems. I first kept a list with changes or bugs that I found but that was not workable, I was more administrating than programming. So the end result became more important than the backward compatibility with the used components like e.g. wxWidgets or codeblocks.
But EmBlocks is only suitable for embedded, it can't build desktop applications. All the desktop related stuff is removed from the source pool (like resource compiler, dynamic libraries etc). In the next release I will shrink it further by removing the 22px toolbar and the Batch/make file support. There is not much left of the original codeblocks code of 2 years ago and it is drifting further away with the day ::)
Because it is a one man project, Github etc is at this moment a bit too much overhead. I have also a daytime job to do.
So yes, I wrote it.
oBFusCATed:
So you say that EmBlocks uses customized version of wxWidgets?
I'm interested in looking at the code, btw, some things might be worth to integrate back.
I might integrate your version of the Examine memory windows, for example, because it looks good.
The toolbars and the overall look of the IDE look cool in windows. Is this possible with vanilla wxwidgets?
Grad:
--- Quote from: oBFusCATed on March 28, 2013, 08:14:38 am ---So you say that EmBlocks uses customized version of wxWidgets?
The toolbars and the overall look of the IDE look cool in windows. Is this possible with vanilla wxwidgets?
--- End quote ---
Yes, the wxWidgets is heavily customized (like a lot of us do) which is allowed under the wxWindows license 3.1.
You may change the library and it is allowed to only provide the binaries so that gives space at the wxWidget part :).
You have to add styling to it and the MSW need additional low-level stuff.
I'm not familiar with vanilla, never heard of it.
oBFusCATed:
--- Quote from: Grad on March 28, 2013, 09:11:48 am ---I'm not familiar with vanilla, never heard of it.
--- End quote ---
Vanilla means clean upstream version.
Modifying wxWidgets isn't fun in the longer run.
Still I'd like to see the sources. If you like to show them to me you can p.m. me with you e-mail and I can send you a message,
this is if you don't want to bother with putting them online for everyone (no matter that this is required by the license).
Grad:
No problem, I think it's better for now that you point out in which part you are interested in.
If it is using added wxWidget stuff, like the memory window, I could isolate that. Or I could help you with porting that part to code::blocks.
I think that you have my email (it was a part of the registration). I'm quite busy the next couple of weeks but after that I will have time.
Cheers
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version