[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: koStore tweaks needed? (long)
From:       Thomas <zander () xs4all ! nl>
Date:       2000-11-12 11:14:32
[Download RAW message or body]

> 
> 1. When a filter is constructed, it could be passed the current level (or 
> more likely, just the "tar:/0/0/1/2/0" prefix it should use) since the 
> caller knows its level.
> 
> 2. Somehow introduce the concept of a "current working directory" into 
> kostore, and have it manage the hierarchy. This *probably* requires the 
> introduction of "relative URL"s in kostore (say "tar:0" instead of "tar:/0") 
> and each filter.
> 
> Now, choice 1 requires changes to each filter wishing to support 
> cross-filter embedding. But the changes should be modest. Choice 2 might 
> seem to avoid this, except that each filter has to be changed to use 
> relative URLs (which is probably not hard BTW).

So the changes are about the same, for each filter you have to change 
 tar:/part 
to either
 prefix/part
or 
 tar:part

in the first one you also have to store the prefix in the class somewhere. Which actually
makes it a bit harder. ;)


> My instinct is that choice 1 will be the more robust and easy to debug.

Hmm, I think the opposite on the following basis; The filters will be a tad less 
intelligent and the store will have to do a little more work. 
And most importantly, if there is an old  filter on the harddisk of the user
that forgets to pass the full path, you have a problem. This problem will
not occur if in solution 2, because OO-wise solve 2 is nicer..

-- 
Thomas Zander                                            zander@earthling.net
The only thing worse than failure is the fear of trying something new
_______________________________________________
Koffice-devel mailing list
Koffice-devel@master.kde.org
http://master.kde.org/mailman/listinfo/koffice-devel

[prev in list] [next in list] [prev in thread] [next in thread]