Agreed. If the URI is carefully constructed GAJ (and others) could
even pull out the commit message to show in a tooltip etc... Maybe use
a bzr: URN scheme like
bzr:file:///home/mikkel/myproject/trunk#27
bzr:bzr+ssh://bazaar.launchpad.net/~kamstrup/dee/foobar#68
Or don't use the bzr: URN,
Whether or not a chunk of data is binary or text is 100% in the eye of the
beholder, not a property of how you opened the file.
If you load bonary image data you can str() it without problems in Python (not
before you try and print() it of course :-)). Ie. this will not error:
binary =
I'm not sure what we are fixing here? It's because Python 2.7 doesn't have a
proper representation for a binary data aka an array of bytes. The payload is
an 'ay' and that can be mapped several ways in python-dbus...
I'm not sure if list or str is the better representation here. The crucial
I believe we use the current approach because the 'correct' one fails with
thousands of ids in the arguments
On Dec 7, 2010 3:01 PM, Seif Lotfy s...@lotfy.com wrote:
Seif Lotfy has proposed merging lp:~seif/zeitgeist/use-new-placeholders
into lp:zeitgeist.
Requested reviews:
Zeitgeist
Public bug reported:
What should actors that don't have a .desktop file use as their actor
URI? Currently we use application://$desktop_file_id which is very nice
to wrok with because one can do
g_desktop_app_info_new($desktop_file_id).
I propose we define a similar scheme in our API docs where
This is critical of course. But I am really baffled that not using the
indexes can cause the query to fail altogether. This should not affect
the result set in any way - only the execution time.
I'd really like to see a unit test that catches this error.
Sorry to ruin the party, but I really don't like any of the proposed
solutions. The use cases described in the wiki seems very academic and
more intended on doing some theoretical counting exercises than
solving actual user problems.
Unless we have some crystal clear use cases (fx. a UI mockup
Marking as wontfix since this seems to be the consensus of a majority of
the maintainers
** Changed in: zeitgeist
Status: New = Won't Fix
--
Moving Zeitgeist dbus Bus name from gnome to Freedesktop
https://bugs.launchpad.net/bugs/681887
You received this bug notification because you are
Honestly I don't see what good this bring us except breakage of existing
libs. We could own two names, but that just seems silly. Application
authors should never need to see these namespaces. And it's a
*namespace* nothing more. I'm quite sure distributors and ISVs can see
past this.
FWIW
Mikkel Kamstrup Erlandsen has proposed merging
lp:~kamstrup/zeitgeist/readme-updates into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Big update of the README addressing many of the confusing moments and build
issues Federico reported on the mailing list
--
https
Blueprint changed by Mikkel Kamstrup Erlandsen:
Whiteboard changed:
--- seif 2010-10-27 10:28pm ---
Lets discuss this idea.
Do we want it as a supported extension or do we want to have in the engine.
Or do we want it as a community extension? How relevant is that to our current
work? How
On 15 November 2010 21:08, Siegfried Gevatter rai...@ubuntu.com wrote:
2010/11/15 Michal Hruby michal@gmail.com:
I still didn't understand why would the current_uri be part of event,
isn't it by definition a property of the subject? That way you don't
need to update dozens of events, just
However noble it may be I don't think we stand a realistic chance of
implementing a stable repair function if the DB corrupts at an
undefined point in the upgrade process. There are just *way* too many
variables if we have fx. 4 different DB schemes that can all intermix
and corrupt in different
Oh, and one point in I forgot to add in my previous comment - I don't
want to validate the DB on startup. That's just way too expensive -
and whas in fact one of the primary points when I implemented DB
versioning.
One thing we could do to easily, and almost freely, detect when we are
killed
All of these clever remapping schemes scare me a bit to be honest.
They all seem to imply a non-negligible impact on our query time, and
a considerable amount of logic.
A simpler and more performant scheme, which requires an API break (!),
is to simply add an extra field on our Subject structure
Something looks to be ascrew if an event has multiple subject? But it looks
like that was also the case before this branch..? Do we have a test for this?
Can you re-insert the comment about returning None for missing events - I think
it's nice to note there that it is our API contract.
But
The test you added will pass if no events are found. While a test for template
matching with multiple subjects is also useful, what I meant for a test where
you insert and retrieve an event with 2 subjects, validating that it worked.
--
Added zeitgeist as affected since lp:libzeitgeist now pulls the mimetype
mappings from there.
Archive types we should recognize off the top of my head: tar, zip, and
ar. We also have gz, bz2 which are not strictly archives, but just
compression types, but I wouldn't object if we log them as
A few comments:
* I am not convinced that the perceived improvement is statistically
significant. I haven't done the number crunching, but it's a bit fishy...
* I'd really like to understand *why* it's bad to use the time index here and
why sqlite goes on to use it? Does running ANALYZE
Mikkel Kamstrup Erlandsen has proposed merging
lp:~kamstrup/zeitgeist/extra-mimes into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#626492 Log rar and zip files as archives
https://bugs.launchpad.net/bugs/626492
Adds a bunch of extra mimetype
review approve
I second Siegfrieds comment though. And please make sure the man page is
clear on the subject of debug logging
--
https://code.launchpad.net/~thekorn/zeitgeist/fix-660415-improve-zeitgeist-daemon/+merge/38914
Your team Zeitgeist Framework Team is requested to review the proposed
I really don't think that using binary flags helps usability. On the
contrary. It just leaves the door open for a tonne of new types of bugs.
How about 'LeastRecent | Subjects | Events' what does that do?
Another problem with the flags system is that it severely limits the
number of result types
Marking as Triaged instead of Invalid.
As far as I know; it's not that we don't want to have a solution here,
it's just that with the current software platform (from kernel, libs, to
Python) it's simply not feasible to do in general.
I will not be ready to accept anything that has even the
Taking the LeastRecentSubjects example. I'm going to assume you have
time=0 on the left and time0 on the right: 1, 2, 1, 3, 4.
Then One event for each subject only, ordered with oldest events first
would definitely mean: 1, 2, 3, 4. If we are sorting like RainCT is
proposing then the docstring
Public bug reported:
The recently merged changes to use journal_mode=WAL and adding some
columns to event_view requires schema upgrades.
1) Setting WAL journalling *permanently* makes the DB unreadable with
sqlite 3.6 which is still widely deployed. Notably if I boot back into
Ubuntu Lucid Lynx
+1 for 1.a)
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
review approve
Looks good, i'm just wondering how it fares with an empty db? But I
guess the unit tests will catch this if it's an issue.
--
https://code.launchpad.net/~thekorn/zeitgeist/fix-641100-min-max-use-index/+merge/35786
Your team Zeitgeist Framework Team is requested to review the
I think it's valuable to be able to tell where we use ?-substitution, so I'll
leave that as is. The print statement was a slip of mind, I'll fix that and
then merge. Thanks for reviewing!
--
https://code.launchpad.net/~zeitgeist/zeitgeist/explain-logs/+merge/35334
Your team Zeitgeist Framework
Importance: Medium
Assignee: Mikkel Kamstrup Erlandsen (kamstrup)
Status: Triaged
** Changed in: zeitgeist
Importance: Undecided = Medium
** Changed in: zeitgeist
Status: New = Triaged
** Changed in: zeitgeist
Milestone: None = 0.5.2
** Changed in: zeitgeist
** Changed in: libzeitgeist
Status: Fix Committed = Fix Released
--
zeitgeist-daemon crashed with OverflowError in call_async()
https://bugs.launchpad.net/bugs/559350
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
Mikkel Kamstrup Erlandsen has proposed merging
lp:~zeitgeist/zeitgeist/explain-logs into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#632363 Slow queries: SQL indexes not used
https://bugs.launchpad.net/bugs/632363
Part 1) of our profiling quest
Attached branch lp:~zeitgeist/zeitgeist/explain-logs that implements
part 1) of my battle plan above. Based off Seif's work from his previous
comment
** Branch linked: lp:~zeitgeist/zeitgeist/explain-logs
--
Slow queries: SQL indexes not used
https://bugs.launchpad.net/bugs/632363
You received
@Manish: Right, that will clear all blacklists I am afraid. Which is
also partially why we have this bug open to come up with something which
is easier for apps to handle.
--
Blacklist API sucks
https://bugs.launchpad.net/bugs/612344
You received this bug notification because you are a member of
Review: Approve
Yeah, I like it a lot too.
I am with Siegfried though, the Critical status sounds a bit dramatic. Maybe:
Critical: Used when a bug causes Zeitgeist to
generally not work at all for a large user base.
This could be build failures, frequent crashes,
or loss of key parts of
** Summary changed:
- zeitgeist crash when opening activity journal
+ zeitgeist-datahub crash when opening activity journal
--
zeitgeist-datahub crash when opening activity journal
https://bugs.launchpad.net/bugs/626056
You received this bug notification because you are a member of Zeitgeist
Public bug reported:
THE PROBLEM:
I am seeing query times around 200ms (and 150ms with my latest performance
tweak in trunk), which surprised me as quite slow since my queries where quite
simple. I had expected times around 1-2ms.
Reading up on the sqlite documentation I see that the queries
The document Markus points to seems to indicate that my simple OR query
above would indeed be optimized to use the index. However I am still
pretty convinced that we are not using the indexes in our own queries,
given the speeds I see.
--
Slow queries: SQL indexes not used
Review: Needs Fixing
Well, I disagree with Markus :-) I think it makes perfect sense to include this
- otherwise we have a chicken-and-egg problem.
In theory anyone could set the storage field upon item insertion. It just so
happens that the DS we ship is not feature complete. On top of that,
Mikkel Kamstrup Erlandsen has proposed merging
lp:~zeitgeist/zeitgeist/small-find-events-optimization into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
I was seeing query response times of around 200ms when calling ZG from Unity.
As this seems like a suspiciously
I'd actually guess that the memory was allocated inside sqlite rather
than python-dbus, but that's hard to tell without really profiling it.
--
Large requests increase memory usage considerably
https://bugs.launchpad.net/bugs/624310
You received this bug notification because you are a member of
Come to think of it - the fact that Sezen requests 11k events also
suggests that there is something wrong in the design scope of either
Zeitgeist or Sezen.
Before we loose our selves on an optimization cache-pruning spree (which
may very well consume a lot of development time for some very small
** Changed in: zeitgeist-extensions
Status: Fix Committed = Fix Released
** Changed in: unity
Status: Fix Committed = Fix Released
--
fts doesn't index uris correctly
https://bugs.launchpad.net/bugs/617308
You received this bug notification because you are a member of Zeitgeist
** Also affects: unity
Importance: Undecided
Status: New
** Changed in: unity
Importance: Undecided = Low
** Changed in: unity
Status: New = Triaged
** Changed in: unity
Milestone: None = 2010-08-26
** Changed in: unity
Assignee: (unassigned) = Mikkel Kamstrup
= Triaged
** Changed in: unity
Milestone: None = 2010-08-26
** Changed in: unity
Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)
--
fts extension doesn't support deletes
https://bugs.launchpad.net/bugs/622440
You received this bug notification because you are a member of Zeitgeist
On 19 August 2010 18:55, Seif Lotfy 620...@bugs.launchpad.net wrote:
I would like to have a soltuion where the actor is the environment that
launches tha app and the subject is the app itself...
However his could mess up AJ terribly unless I query for all subjects except
for those of type
On 19 August 2010 18:42, Markus Korn thek...@gmx.de wrote:
As I mentioned already on IRC, although I don't like the idea of having
events without a subject (because it's conceptual: something is happening,
but we don't know what) I think this is the easiest solution for the usecase
of a GIO
Markus, I had a similar idea to begin with, but I don't think that works
for the general case of launching app X with a list of N uris (N=0, 1,
2, 3, ...). To me it would be ugly if launching an app without uri args
is different than launching an app with N uris.
Alternatively we log first the
I am aware that surprisingly many apps screw up the timestamps in
~/.recently-used.xbel. We should just go and fix those apps. I expect
those patches to be easy to make, and also easily accepted upstream as
they should be minimal.
--
Logs 3 events for each recent file
Right now the FTS extension doesn't support deletes. The delete hook was
only added in ZG 0.5.0 and i've not gotten around to adding it in fts
yet.
But I am not sure that could account for you odd results...
--
fts returning strange results
https://bugs.launchpad.net/bugs/617313
You received
Can you find it by searching for '20bar' or some other add string?
I think it's just because we a missing a URL escape somewhere in the
indexer though...
--
fts doesn't index uris correctly
https://bugs.launchpad.net/bugs/617308
You received this bug notification because you are a member of
ok, then this is definitely because of missing URI escaping
--
fts doesn't index uris correctly
https://bugs.launchpad.net/bugs/617308
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Smack-ins.
Status in Zeitgeist
Seif, what makes you believe Tracker doesn't have issues? I can tell you
for sure that they poured a LOT of development effort into making file
monitoring as light as possible. It wont work well if you don't really
take care in how you set all the monitors up.
--
Monitoring for new files
If you put something like this in configure.ac you can access the
ZEITGEIST_EXTENSIONS_DIR variable in your Makefile.am to figure out
where to install the extension:
ZEITGEIST_EXTENSION_DIR=`$PKG_CONFIG --variable=extensiondir zeitgeist-daemon`
AC_SUBST(ZEITGEIST_EXTENSION_DIR)
--
missing
Since Zeitgeist 0.5.0 is now in Maverick I implemented this The Right
Way (TM) for unity-place-files, and it's now in trunk
** Changed in: unity-place-files
Status: Confirmed = Fix Committed
--
Other category displays everything
https://bugs.launchpad.net/bugs/599782
You received this
Well, it's not like its a huge issue. Just a minor cosmetic thing. I
think that maybe the work required to get this nicely hooked in to the
build system doesn't compare to the little gain code-wise...
--
ontology convention inconsistency
https://bugs.launchpad.net/bugs/575449
You received this
Now that we ship a zeitgeist-daemon.pc file you detect the location of
the system extensions dir and install it properly via automake in GAJ. I
think that's the real solution to this problem. or you just being more
explicit in your instructions :-)
--
missing extension folder
On 5 August 2010 23:04, Siegfried Gevatter rai...@ubuntu.com wrote:
2010/8/5 Mikkel Kamstrup Erlandsen mikkel.kamst...@gmail.com:
Apps would use their normal namespaced bus names to construct blacklist
names. Like 'org.gnome.Epiphany.PrivateBrowsing' for the blacklist
template epiphany install
Technically this should not be too hard, but there may be a few devils
in the details. It really boils down to the following change in the
template compilation code:
* If a template string starts with ! replace that ! with a minus,
-.
** Changed in: zeitgeist-extensions
Status: New =
I am pretty much indifferent on TimeRange.always() is. The .is_always()
function is just used in the fts extension to do a slight optimization
in case the time range is irrelevant.
Regarding change of timestamp signature: What's the technical argument
for breaking API (and breaking it in a big
Can you try executing the generated queries directly in talis? Ie.
./talis '(v*) AND (())'
etc... Maybe you're not seeing the entire generated query or
something...
--
fts extension is not expanding stuff correctly in queries
https://bugs.launchpad.net/bugs/614284
You received this bug
** Changed in: zeitgeist
Importance: Undecided = High
** Changed in: zeitgeist
Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)
** Also affects: libzeitgeist
Importance: Undecided
Status: New
** Changed in: libzeitgeist
Importance: Undecided = High
** Changed
For the record: In order to close this bug in Zeitgeist (not libzg) I
think we need to do as Michal suggests; wrap the monitor invocations in
try-catch blocks.
Closing it in libzg is a matter of merging Michal's branch
--
zeitgeist-daemon crashed with OverflowError in call_async()
Looking quickly at fixinf this on the ZG side as well... I am actually
afraid that this is impossible to fix inside Zeitgeist :-S
We dispatch the monitor DBus calls asynchrously, and the bug is somehow
picked up very low in the stack in an async callback before it reaches
Zeitgeist. Indeed I can
** Changed in: libzeitgeist
Status: New = Fix Released
--
Data-sources don't identify themselves to Zeitgeist
https://bugs.launchpad.net/bugs/602864
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Data-Sources.
So if we have 10 clients monitoring the blacklist the daemon it will
result in 10 GetTemplates() calls on the bus? ;-) How about putting the
new list of templates in the Changed() signal? That way there'll be no
extra noise on the buzz when the list changes.
Anyway, I am still not entirely
On behalf of the Zeitgeist team I am proud to announce the immediate
availability of Zeitgeist 0.5.0 also known as the Atomic Flounder.
The release summary reads:
Engine:
- FindEvent*: Event subjects are now joined by a logical AND instead of OR
(LP: #592599).
- Extensions found in the
** Changed in: zeitgeist
Status: New = Fix Released
--
Not loading extensions from ~/.local/share/zeitgeist/extensions
https://bugs.launchpad.net/bugs/610114
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
It may be worthwhile to point at Michal Hruby's datahub rewritten in
Vala. This uses the mimetype-interpretation mappings from libzeitgeist
which are more full featured than the ones we have inside the Zeitgeist
Python codebase.
The work is at: lp:~mhr3/zeitgeist/datahub-vala
** Changed in:
** Changed in: zeitgeist
Milestone: 0.4.1 = 0.5.1
--
Implement storage monitor (devices and connectivity)
https://bugs.launchpad.net/bugs/489194
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
Mikkel Kamstrup Erlandsen has proposed merging
lp:~zeitgeist/zeitgeist/user-extensions into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Implements loading extensions from ~/.local/zeitgeist/extensions. All classes
extension Extension found in any .py file here
** Changed in: unity-place-files
Status: In Progress = Fix Released
--
Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity
Mikkel Kamstrup Erlandsen has proposed merging
lp:~zeitgeist/zeitgeist/sort-by-orig into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#487321 What value should subject.origin have?
https://bugs.launchpad.net/bugs/487321
Implements new ResultTypes
Review: Approve diff and run unit tests
Looks good and all the tests are passing on my end. Good work Markus!
--
https://code.launchpad.net/~zeitgeist/zeitgeist/fix-592599-subject-AND/+merge/30920
Your team Zeitgeist Framework Team is requested to review the proposed merge of
I am with Markus here. You might also want to blacklist files which
contain a seven-letter palindrome in the URI, but only when Jupiter
aligns with Mars - that's up to you! ;-)
'*private*' is not a good use case imho. For instance there is a unity-
private/ directory in the Unity sources. What
Inotify still sucks rest assured :-)
A watch on a dir will only tell us when some unspecified thing happens
to some unspecified file in that directory. We could install monitors
directly on the last N (fx. 100) actual file inodes perhaps, but I am
reluctant to do that - what happens when we
Question #116893 on Zeitgeist Framework changed:
https://answers.launchpad.net/zeitgeist/+question/116893
Status: Open = Answered
Mikkel Kamstrup Erlandsen proposed the following answer:
Sorry for the late reply - summer holidays :-)
The correct way to do this would be to use the DBus
** Also affects: unity-place-files
Importance: Undecided
Status: New
--
Implement storage monitor (devices and connectivity)
https://bugs.launchpad.net/bugs/489194
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
Seif: Quoting myself: In any case this could be done entirely in an
extension - so no new depency unless we want it in the main source
tree.
Can you explain 2) - I can't see why this need be the case...
--
Monitoring for new files
https://bugs.launchpad.net/bugs/602211
You received this bug
Considering Siegfried's comment #23 and Michal's comment #24, and with a
free interpretation of Seif's domain moniker in comment #27 I think we
actually agree more or less on what to put in origin. I'll write a draft
docstring and put up a branch for review.
Watch this space - we may actually be
** Changed in: zeitgeist
Status: Triaged = In Progress
--
Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity Files Place:
** Changed in: zeitgeist
Status: Triaged = Fix Committed
--
delete_event_hook for extensions
https://bugs.launchpad.net/bugs/595919
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
** Also affects: unity-place-files
Importance: Undecided
Status: New
--
Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
Let's get this fixed for 0.4.1
** Changed in: zeitgeist
Importance: Undecided = Low
** Changed in: zeitgeist
Milestone: None = 0.4.1
--
compilation fails for 0.4
https://bugs.launchpad.net/bugs/595577
You received this bug notification because you are a member of Zeitgeist
Framework
I proposed one event_id because the insert hook also only receives one
event.
The idea was simply as a notification mechanism, I am not sure it's a
good idea to allow extensions to bar events from deletion, although I
can't fully see the ramifications of this... We can't use the current
Started on this
** Changed in: zeitgeist
Status: Triaged = In Progress
** Changed in: zeitgeist
Assignee: (unassigned) = Mikkel Kamstrup Erlandsen (kamstrup)
** Branch linked: lp:~zeitgeist/zeitgeist/autoload-extensions
--
Autoload extensions
https://bugs.launchpad.net/bugs/592600
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
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
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
Targetting for 0.4.1 as there is rough consensus
** Changed in: zeitgeist
Importance: Undecided = Medium
** Changed in: zeitgeist
Status: Confirmed = Triaged
** Changed in: zeitgeist
Milestone: None = 0.4.1
--
Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
** Changed in: zeitgeist
Milestone: 0.3.4 = 0.4.1
--
Give zeitgeist.datamodel.DataSource properties
https://bugs.launchpad.net/bugs/513295
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
** Changed in: zeitgeist
Milestone: 0.3.4 = 0.4.1
--
Implement storage monitor (devices and connectivity)
https://bugs.launchpad.net/bugs/489194
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
Milestone: 0.3.4 = 0.4.1
--
What value should subject.origin have?
https://bugs.launchpad.net/bugs/487321
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
Public bug reported:
(Canonical hat on)
For Unity we want to try and group recent files into some categories
like Documents, Images, Video, Presentations, etc, and I've discovered
an unfortunate decision in our template matching algorithm, making this
quite hard to get 100% right.
The deal is
Public bug reported:
(Canonical hat on)
For packaging reasons it would be nice if Zeitgeist would automatically
load all extensions found somewhere on the file system so that we could
ship the FTS extension in a separate .deb for Unity. In theory it's
possible to use the env vars there are, but
From IRC:
thekorn kamstrup, for the other bug, would you be happy with a
--load_all_extensions commandline switch for the daemon?
I am not sure that is good enough, unless we package ZG to always launch
with that. My idea was that simply installing/removing .debs determined
which extensions
Tagetting for 0.4.1 as it seems everyone is more or less on the same
page
** Changed in: zeitgeist
Importance: Undecided = High
** Changed in: zeitgeist
Status: New = Triaged
** Changed in: zeitgeist
Milestone: None = 0.4.1
--
Autoload extensions
Seif: No. Since all the subject templates are ORed together you end up
matching everything. In fact just these two lines match everything:
su1 = Subject.new_for_values(interpretation=!+DOCUMENT)
su2 = Subject.new_for_values(interpretation=!+AUDIO)
So the only way to construct Others would be
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
Hi all,
On behalf of the Zeitgeist team (and our many new contributors!) I am
most delighted to announce the immediate availability of
Zeitgeist-0.4.0.
This new release is packed with new features so we are pretty hyped
about it :-) We are very well on our way to becoming feature
complete in the
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
core_0_1 upgrade script's table columns are reversed
https://bugs.launchpad.net/bugs/587545
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
101 - 200 of 304 matches
Mail list logo
