Hi Ricardo, On Wed, Jul 01, 2009 at 12:36:27AM +0100, Jo?o Ricardo Louren?o wrote:
Ter, 2009-06-30 ?s 22:43 +0100, Jo?o Ricardo Louren?o escreveu:
Well, I promised I would report to you when I got more free time. Guess what, I'm on vacation! Getting free time from my own personal projects finally lets me take a closer look at Dillo. I am sorry for being away for such a long time, though.
I would like to contribute to one area that I have contributed previously -- the close-tab button. It isn't critical, I know, but, for now, it's the best I can do. The idea now is to finally have a button in each tab.
It is tough, but I am getting somewhere. The 'initial' drawing part is done, but I have had to make some small changes to some virtual functions, and also changing non-virtual functions and finding a way to 'enable' them in the code.
It's pretty hackish right now, but I have managed to print the button and am now starting to handle all the events and different button states (clicked, over, etcetera).
I'll keep you updated!
Jo?o
Answering myself, I've got the system working! There are still many more code-cleanups to do and add a couple of documentation features here and there.... It isn't 'pretty', but someone with more skills in the 'design' area can do better than me, I've got the system (which is pretty dumb and slow, IMO).
There are, however, three issues I have:
1. I still haven't sorted things with the pager to have tabs behave 'correctly', but that should be _too_ hard, just quite some research.
2. When I destroy a tab, their order gets 'mixed up', but only sometimes.
3. For some reason, clicking on some tabs isn't working (not the buttons, but the tabs).
I'll go into them and I think that 3 and 2 are related. I just decided to inform all of you how progress was going.
It's good to see you around again! WRT tabs. If you succeed in a short time span, great. If it takes more effort, I'd prefer you to work on another area. The fact is most probably we'll have to port dillo2 to FLTK-1.3 at some point this year, and our fine tunning/hacking/workarounds for FLTK2 will be lost, and we'll have to start again... e.g. 1.- Jump to #anchor doesn't work correctly. Find out what is wrong in the current mechanism, fix it. (Related: there's a need to add a timeout-remove function and use it for cancel operations in the rest of the code). 2.- http://planet.postgresql.org/ Unrendered HTML. Simple one to start with. -- Cheers Jorge.-