** Project changed: zeitgeist => zeitgeist-dataproviders
--
create an external dataprovider for evolution
https://bugs.launchpad.net/bugs/485698
You received this bug notification because you are a member of
Zeitgeist-Engine, which is subscribed to Zeitgeist Data Providers.
Status in Zeitgeist D
The attached branch has all my experiments, please see evolution/README
for a detailed report.
** Branch linked: lp:~thekorn/zeitgeist-dataproviders/evolution-
dataprovider
--
create an external dataprovider for evolution
https://bugs.launchpad.net/bugs/485698
You received this bug notification
Public bug reported:
Due to a missing pyxpcom package in ubuntu karmic the firefox extension
was hacked by files in the dbus communication process. this is VERY
inefficient. We should use XPCOM instead.
** Affects: zeitgeist-dataproviders
Importance: Undecided
Status: New
--
firef
How can you talk to Zeitgeist over XPCOM? Is there some bridging
mechanism? Otherwise it might be useful to use a real DBus impl. for
Xulrunner http://wiki.github.com/FireRabbit/mozjs-dbus
--
firefox extension: use XPCOM instead of communicating via files
https://bugs.launchpad.net/bugs/488656
Yo
Ah, now I get it. You want to load a Zeitgeist XPCOM component, written
in Python, into Firefox, and then from that component import DBus (or
simply zeitgeist.client.ZeitgeistClient). This component is then used to
implement the extension in Javscript, or am I out on a limb?
--
firefox extension:
Right, this was my initial idea.
But maybe using mozjs-dbus is much easier, I will try it later today.
Thanks for the link.
--
firefox extension: use XPCOM instead of communicating via files
https://bugs.launchpad.net/bugs/488656
You received this bug notification because you are a member of
Zeit
this issue does not really valid anymore since the error comes from our
old firefox plugin
** Changed in: zeitgeist
Status: Triaged => Invalid
--
zeitgeist-datahub crashed with OperationalError in get_items_uncached()
https://bugs.launchpad.net/bugs/437686
You received this bug notificati
** Changed in: zeitgeist
Status: New => Fix Released
--
zeitgeist needs a more powerful testing framework
https://bugs.launchpad.net/bugs/435099
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeit
Public bug reported:
Our DB has some inconsistency when we insert applications:
recently used inserts something like /path/to/app.desktop
while the other loggers use application://app.desktop
WHICH ONE SHOULD IT BE
** Affects: zeitgeist
Importance: Undecided
Status: New
--
incons
** Attachment added: "Screenshot-SQLite Manager -
-home-seif-.local-share-zeitgeist-activity.sqlite.png"
http://launchpadlibrarian.net/36114412/Screenshot-SQLite%20Manager%20-%20-home-seif-.local-share-zeitgeist-activity.sqlite.png
--
inconsistency in DB
https://bugs.launchpad.net/bugs/4887
2009/11/26 Siegfried Gevatter :
> Just app.desktop.
Although I'm not opposed to prefixing application:// if we want to
allow other types of actors, but I'd like to see some use case for
this before we add this complexity.
--
inconsistency in DB
https://bugs.launchpad.net/bugs/488790
You received
Just app.desktop.
--
inconsistency in DB
https://bugs.launchpad.net/bugs/488790
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug description:
Our DB has some inconsistency wh
I'm marking this bug as Won't Fix for Ubuntu since upstream isn't going
to fix bugs in removed files. This should go away when a newer version
lands. Zeitgeist is currently only for testing purposes and therefore
can be expected to be unstable at times.
** Changed in: zeitgeist (Ubuntu)
Sta
I am unsure what to do. I, for one, have several versions of Firefox
installed. To identify which one sending the event we'd need the whole
path to the .desktop file. OTOH getting the correct path to the .desktop
file might not always be easy.
In the .recently-used.xbel apps are identified simply
- recent.py has code to find the .desktop file for an app.
- I'd prefer to have the .desktop file name as that's what seems to
be used by other projects (eg. GNOME Shell) to identify applications.
(However, just using "app" would simplify inserting quite a bit so I
may still change my opinion in
We now have debug statements with timing and count for insert, find, and
get.
** Changed in: zeitgeist
Status: New => Fix Released
--
add more logging statements to the engine
https://bugs.launchpad.net/bugs/488067
You received this bug notification because you are a member of
Zeitgeist-E
Public bug reported:
Zeitgeist 0.2 relayed all incoming events over the bus. This might be a
bit over the top, but apps still need a way to get notified of events
elsewhere in the system.
This bug relates a lot to bug #447417 "Zeitgeist should have any kind of
system to protect users privacy" whe
Public bug reported:
We should cache the full Event objects in an LRUCache (of size something
like 500 or less). We can update the cache in InsertEvents() and
GetEvents(). The primary idea behind it is to massively speed up
GetEvents().
Anyway not hugely important, just an optimization.
** Affec
This bug is mostly about eactly what we want to store in origin, and how
to interpret origin exactly. I am deferring it to 0.3.1 because it's
unrealistic that we get full clarity on this before the weekend.
** Changed in: zeitgeist
Milestone: 0.3.0 => 0.3.1
--
Origin
https://bugs.launchpad.n
Do we really want to block 0.3.0 because of this bug? I would say no,
otherwise we will ship some very untested code if we want to ship 0.3.0
this weekend. I say defer to 0.3.1, it's only a micro API break.
--
Using filters (text match / exclusion / etc)
https://bugs.launchpad.net/bugs/485966
You
I believe Markus' branch was merged and the focus stuff removed for now?
So we can close this bug?
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to
the engine configurable
https://bugs.launchpad.net/bugs/483556
You received this bug notification because you are
Hi there,
We a prepping up for rolling our first development release in the
Zeitgeist 0.3 series (which will lead up to a stable 0.4 eventually).
Our plan is to roll the release this weekend.
So developers, please have a look over launchpad (fx. starting at
https://launchpad.net/zeitgeist/+milest
Lets push this to 0.3.1 then
this is no break to the api so we can roll it out later
2009/11/26 Mikkel Kamstrup Erlandsen
> Do we really want to block 0.3.0 because of this bug? I would say no,
> otherwise we will ship some very untested code if we want to ship 0.3.0
> this weekend. I say defer
I don't think we reached the configurable state yet! we should look into it
though for 0.3.1 so for now we can dismiss it
2009/11/26 Mikkel Kamstrup Erlandsen
> I believe Markus' branch was merged and the focus stuff removed for now?
> So we can close this bug?
>
> --
> [lp:~zeitgeist/zeitgeist/
I really think this should get into 0.3.0 though! I think Siegfried could
get it up an running in a matter of 2 hours! :)
0.3.1 should reduce new features and be all about extending configurability,
fixing bugs and writing new extensions!
2009/11/26 Mikkel Kamstrup Erlandsen
> Public bug reporte
we should really consider this issue again! what do u think?
** Changed in: zeitgeist
Status: Invalid => Incomplete
--
Export extensions and dataproviders into a new package
https://bugs.launchpad.net/bugs/406054
You received this bug notification because you are a member of
Zeitgeist-Eng
If we want to re-instate the old system it is a matter of a few lines.
But that would be a step back IMHO. And writing a full template based
notification system could not be done in two hours by one. It's not a
huge task, but definitely more than two hours :-)
Besides, I really think we should sto
27 matches
Mail list logo
