2009/6/8 Mark <[email protected]>:
> Hi Pawel,
>
> Are you referring to favicons here? Then I'd suggest, generally, looking at
> the core functions I wrote for my favicon branch, that really should be
> merged to trunk quite quickly to avoid duplication of work; treating that as
> a kind of 'API' to retrieve favicons;

I'm using 'icons' in a little broader meaning here. The icons in the
tree either represent the type of a node or are set individually.The
latter includes favicons for url nodes so as soon as the API gets
merged into trunk I'll add the usage of it.

> As for the text input, my only comment is that at current projections, I'd
> hope to complete the customisation branch perhaps in time for Friday
> [although my car may need major work so I may have limited time for now],
> while it may well be that theme support would naturally be a simple addition
> to the customisation branch; at that stage then the only branch for me to
> work at would be hotlist, so I'd really encourage you to fully complete your
> treeview/hotlist branch first, before touching text input — in a new branch
> please :-)

I am working on creating core history/bookmarks/cookies UI elements so
the main purpose is to reduce the platform dependent part as far as
possible. In consequence the front end will be responsible only for
handling the window (together with a toolbar menu probably), passing
events and maybe a right click menu. I am not sure how much of front
end specific work will be left on that.

I think I need to better understand the details of the new features
your project covers (I tried to find some info on the ML but maybe I
missed something)? I'm quite confused in the matter of the overlapping
part of our gsoc projects (and what the final result is meant to be).
Also, I just realised that I didn't post my proposal to the ML, what I
will do in a separate posting right after this one. AS in the
following days I will be working/on IRC most of the time I won't be
sleeping :) we can easily find some time to have a more detailed
conversation.

Reply via email to