It has been a long time... Anyway I'm still working on the same realtime communication package for linux, in the past year it has really matured into a powerfull piece of software, too bad I can never release it....

But, I've started the userinterface of the project and it is being done in gtk+. I've developed 1 custome widget that I've got permission to release under the LGPL after the project is released. When that happens it will be nice to give back to a community that has given me so much.

My current head banging experience is changing the background color of gtk widgets, it is really beginning to suck, I've discoved a way to get label widgets background to change by this little snipet of code

	GtkRcStyle *rc_style = gtk_rc_style_new();

 	rc_style->color_flags[GTK_STATE_NORMAL] = 
			(GtkRcFlags)(rc_style->color_flags[GTK_STATE_NORMAL] |
			 GTK_RC_BG);

 	rc_style->bg[GTK_STATE_NORMAL].red = 0;
	rc_style->bg[GTK_STATE_NORMAL].green = 0;
	rc_style->bg[GTK_STATE_NORMAL].blue = 0xA0FF;

 	gtk_widget_modify_style (eventBox, rc_style);
	gtk_widget_modify_style (label1, rc_style);

 

But it only seems to work for labels, and I need entries, if anybody happens to read this and knows how to change gtk+ widget colors please I beg you, email me!!!

Well, I got to go.

I've been working with the mozilla source a little, but mostly I've been playing with the gtkmozembed widget for gtk+. It is really cool and I'm waiting for the release of M17 because there are suppousd to be enhancements to the widget to allow you to get into the internals of the Gecko engine itself, i.e. get behind the wrapper.

Anyway the nightly downloads for mozilla seem to be really stable. I downloaded the Win32 version and am running it on a P166 w/32MB RAM. It is a little slow but when it comes to rendering speed it kicks IE's butt! When Mozilla goes gold its gonna rock the web world!!!

I'm still working on the implementation of that specification. Its gonna kill be before it is over but will be worth it in the end:) I just have to go through more dry reading and trying to figure out how to implement it with out breaking my arcetecture. Very slow process when you are trying to do it right.

BTW. This diary entry made possible by Mozilla!

Ahh!!!!! I edited one of my older diary entries and it chaned the date! I chaned a small mistake I had. Somthing I didn't realize would happen, Oh well...

July 25: I got mozilla built and running. Right now plying with the gtk+ wrapper. After 12+ hours switching between c and c++ you start to see funny things in the code:) I don't reccommend downloading, compiling, playing/learning, accidentally mixing versions, building, breaking, building again, pulling hair ot of head, creating gtk+ app utilizing gecko for first time, and considering licensing issues between GPL and MOZPL in > 12 hours unless you have large quantities of caffeine saturated beverages available.

Anyway I look forward to tomorrow and getting some real functionality into a basic browser app utilizing gecko from todays daily build. Yea I know Galeon does it but I'd like a gtk+ light browser that doesn't rely on GNOME. I love GNOME but why integrate a light browser with it. Its suppoused to be LIGHT. Maybe if I work on the project enough I'll be able to open it up and get an awsome standalone gtk+ gecko browser. I'll call it SGGB (Standalone Gtk+ Gecko Browser). Now I'm getting silly. Too much work and caffien and not enough sleep. I'll get to bed now.
-----------------------------------------
-----------------------------------------
I'm building mozilla from the source toay. I'm interested in getting just the gtk+ wrapper working for light browsing.

Implimentation of that protocol is really slow!

I hope to have it working in about 2 weeks, but I have a feeling that 2 weeks is a little optimistic. Hope my manager understands.
---------------------------
---------------------------
I hope nyma reads this because I have an answer to the g++ name mangling problem. I had the same problem a week ago. The function that you are exporting needs to be delcared in an extern "C" block. Here is an example...

extern "C" {
void MyNonMangledFunction ( int argc, char** argv );
}

This should stop C++ from mangaling the function names in the extern "C" block.

hope this helps nyma.

I'm gathering the requirements to a protocol from it's published specification right now. I cannot mention which one it due to the nature of the project that I am working on. When the product hits the shelves then all will be revealed... Anyway I digress... Gathering requirements from this specification is like reading 20 windbags speaking at once. I understand that the specification needs to be this way but it just seems to drag on and on and on and...

After the requirement gathering I have to implement the specification. This is the part that is going to hurt.

BTW. The dynamic loadable library functionality of Linux is just too cool. dlopen, dlsym... just totaly kick butt. My mind has exploded due to the possibilities

This is my first diary entry...

So far I really like Advogato.org. The dicussions threads are awsome with qutie a bit of good technical content. I'll be visiting more and if I like it be making more diary entrys.