Re: BalsaIndex ported to GtkTreeView

On 10.07.2002 13:12 Peter Bloomfield wrote:
> On 2002.07.09 11:44 Emmanuel wrote:
> [ snip ]
>> I have not actually read the code, just your comments about the speed 
>> concerns. If I understand well, moving messages has to be done the hard 
>> way (sic ;-) because of the insufficiencies of GtkTreeView.
> Either that, or I'm missing an obvious way to do it!
>> Perhaps should we ask to the gtk+ developpers for this feature,
> I'm looking at the gtk+ code right now to get a sense of how big a job 
> it would be.
>> moreover I'm sure we're not the only one to need this.
> You're right: 
>> If this is not planned as a new feature for the GtkTreeView, the idea 
>> to speed the threading (I think this is the worst problem) to do it in 
>> two stages : a light structure keeping all relevant datas for the 
>> threading (perhaps only a ref. ), and after fill the Tree.
> That works for the initial threading, but we also need to rethread when 
> new messages arrive, preferably without rebuilding the tree from
> scratch. We *could* go to separate methods for each action, but that 
> would be annoying! All in all, getting the natural capabilities into the 
> gtk+ code seems like the better route.

This is also what I think. This only concerns the storing object I guess.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]