OK can i close this now... I see it already done in unity :)
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework:
Btw, what does Unity implementing this imply for using this feature on a
regular desktop?
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
yes :)
On Sat, Aug 28, 2010 at 7:32 PM, Conrad Steenberg 592...@bugs.launchpad.net
wrote:
Btw, what does Unity implementing this imply for using this feature on a
regular desktop?
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification
Great!
Thanks for giving my request so much attention, it's much appreciated
:-)
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
** Changed in: zeitgeist
Status: Incomplete = Fix Released
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
When talking origin i think we should think in a timeline matter.
Every time the origin can be different for the same uri if we follow siegfried
interpretation.
I think Mikkels interpretation is more safe for now.
If i download a file from a website the origin is the website. I however
open the
How does GAJ open that? Also what value would you give origin(aka
dirname) there?
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
How GAJ handles that is up to GAJ. How about the tel: URI scheme how
does it handle that? ;-) If GAJ can not meaningfully handle some data it
should probably not go there (which is also how it works now i believe).
If I recall correctly though, there is a way to register a handler for
particular
2010/6/14 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com:
When you are actually acquiring the e-book it should
probably be a URL for the provider.
So isn't this the same as for a downloaded file the website where you
got it?
--
Tracking recent directories
When you are actually acquiring the e-book it should
probably be a URL for the provider.
So isn't this the same as for a downloaded file the website where you got it?
Most likely, yes.
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification
2010/6/13 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com:
I think that MostUsedDirectories is not what we want. I was assuming it
would be Most/LeastRecentOrigin and Most/LeastPopularOrigin.
Well, again, I believe origin as what it is now (ie. dirname(uri))
should not be exposed in the API
You are assuming that the URIs have a tree-like syntax, which is not
true in general. What if we dropped file:/// and http:// URIs altogether
and used Tracker UUIDs all the way?
Also the download use case we discussed numerous times - If we say that
Origin is where the user was at the event time
I dont think using Tracker UUIDs would make sense atm This will generate
a dependency...
However we could use our own UUIDs but it will require a change the the DB
schema
On Sun, Jun 13, 2010 at 11:46 PM, Mikkel Kamstrup Erlandsen
mikkel.kamst...@gmail.com wrote:
You are assuming that the
2010/6/13 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com:
You are assuming that the URIs have a tree-like syntax, which is not
true in general. What if we dropped file:/// and http:// URIs altogether
and used Tracker UUIDs all the way?
We always need a URI, so that the application has
I disagree with this, first of all because I'm still convinced we
should get ride of origin (especially now that we have wildcards).
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification because you are a member of Zeitgeist
Framework Team,
wild cards wont get us most used folders
On Sat, Jun 12, 2010 at 3:46 PM, Siegfried Gevatter
rai...@ubuntu.comwrote:
I disagree with this, first of all because I'm still convinced we
should get ride of origin (especially now that we have wildcards).
--
Tracking recent directories
I agree with Mikkel that wildcards is a wrong approach...
Adding new resulttypes is the best solution...
On Sat, Jun 12, 2010 at 10:45 PM, Mikkel Kamstrup Erlandsen
mikkel.kamst...@gmail.com wrote:
Let's not mix in the discussions on whether or not we should have
origins.
But what do you
Hi Conrad,
thanks for your feature request. I'm not sure if I understood your request
correctly, but can't your problem be solved by using this (pseudo-) code:
recent_dirs = [dirname($subject.uri) for $subject in
$recent_local_file_subjects]
Markus
** Changed in: zeitgeist
Status: New
I guess this is more of a GUI issue then.
Is there anybody else on the notification list who would care to comment
on whether this could be added to e.g. the new File dialog?
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification because you are
Markus: That could be an idea... But we could also add new ResultTypes
called MostRecentOrigin and LeastRecentOrigin? Then restricting the
query to match only Manifestation.FILE_DATA_OBJECT should also do what
you want. Not a huge deal though, as your suggestion would also work
well... The only
It seems like a good idea to me though... I would say lets go for it
And btw if u sort most_used_dir and set a limit 100 u will get the
100 latest events with unique origins of the subjects sorted my most used
...
On Fri, Jun 11, 2010 at 7:11 PM, Mikkel Kamstrup Erlandsen
21 matches
Mail list logo
