Re: Dashboard?

2007-11-28 Thread kim wroblewski
I played with dashboard over the summer.
Here is where I left off:
http://www.geocities.com/kimwroblewski/dashboard/Minidash-0.0.1.tar.bz2.x

The idea was to make a minimalist dashboard.
Hope that helps

What is Mini-dashboard?
1)Passively tracks what the user is doing right now.
2)Fires rules for matched behavior.
Tried to remove all the layers of abstraction
and assumptions of what dashboard is for.

--separate projects not in minidash-
3)one matched behavior could be to fulfil a goal.
4)Widgets that display information.
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard?

2007-11-22 Thread Joe Shaw
Hi Nils,

Welcome back!  Nice to see you again. :)

On 11/21/07, Nils Erik Svangård [EMAIL PROTECTED] wrote:
 * libdashboard - Or as its better known, a C library that generates
 valid, parseable clues. This is not only critical since most plugin
 authors aren't going to want to spend the time validating that mono
 can deserialize all their XML. But because we can generate bindings
 for most every other language once we have them in C.

I actually think this is the wrong thing to do.  This is something we
explicitly avoided the first time around with Dashboard, and was a
large reason why we were able to instrument as many applications as we
did.

The problem with creating a library and making people use it is that
it introduces a new library dependency.  That's extra work for the
maintainers of the software, developers, and packagers of the
software, and for something as immature and experimental as Dashboard,
they simply won't do it.

So the way we did it originally was to include a fully self-contained
.c file which people would #include into their project, and all the
functionality could be included as a simple patch.

Ok, that was a long setup, but I think it might even be easier today:
with inotify, we don't even really need a programmatic IPC mechanism
-- we can just drop XML files into a watched directory and the
Dashboard can pick them up automatically.  For projects which already
use D-Bus, that's a viable alternative as well (but not the sole one
-- no adding D-Bus to projects which don't already use it, because,
again, added dependencies).

 * Real Bug/Performance Testing/Fixing - This is a huge one, Dashboard
 is still pre-alpha, and mostly proof of concept. While the code base
 could be brought up to production level, it needs tons of cleanup.

The amount of Dashboard code there is sufficiently small enough that
it can either be used as a starting point, as a good chunk of
reference code to look at, or redone completely.

I would strongly encourage unit and automated regression tests for
this sort of thing; it's something we haven't been particularly good
about in Beagle and it has clearly hurt us.

 Is there more stuff that have to be done?

Well, there isn't a UI for it, so that's a big amount of work. :)
It's unclear to me exactly how to present results most usefully to
users.  The decaying method we had before was a fairly simplistic way
of doing it.  Some machine learning would probably be pretty useful
here.

 Is anybody working on dashboard?

Sadly, I don't think so.  There were some patches sent to the list,
and I believe some were committed, but nobody has really taken
ownership of the project, which is what it really needs at this point.

Joe
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard?

2007-11-21 Thread Kevin Godby
Hello.

As far as I know, no one is currently actively working on Dashboard.
However, that's about to change in the next couple months.

My dissertation topic (which is effectively implementing Dashboard)
has been approved, so I'll start working on that at the end of the
current semester (December).

The last time I downloaded the Dashboard code from the Google project
site, it crashed at run-time.  I think the libwnck API has changed
sufficiently to break the C# bindings.  It's also using the old dbus
bindings instead of the new NDesk dbus bindings.  There seemed to be a
few bugs dealing with disposing of connections and backends when one
tried to exit Dashboard.  Aside from that, it appeared to work.

I welcome any help anyone wants to provide in getting Dashboard up and
running again.  I'll be collecting more of my thoughts and plans on
Dashboard in the next month or so and will be sure to post to the
list.

--Kevin Godby [EMAIL PROTECTED]

On Nov 21, 2007 4:13 AM, Nils Erik Svangård [EMAIL PROTECTED] wrote:
 Hello!

 I followed the development of dashboard with great intrest a couple of
 years back.
  I located the google code page for dashboard, which listed theese
 things to be done:

 * libdashboard - Or as its better known, a C library that generates
 valid, parseable clues. This is not only critical since most plugin
 authors aren't going to want to spend the time validating that mono
 can deserialize all their XML. But because we can generate bindings
 for most every other language once we have them in C.

 * Real Bug/Performance Testing/Fixing - This is a huge one, Dashboard
 is still pre-alpha, and mostly proof of concept. While the code base
 could be brought up to production level, it needs tons of cleanup.
 This is where an army of open source dev's can help the most, compile
 and install dashboard from SVN, then just play with it, and every time
 it crashes, track down why, and try to make it sane. This is long,
 slow, tedious, and thankless work, but it is an absolute necessity if
 people want to start using dashboard, as even simple race cases will
 crash dashboard most of the time.

 * Mappings/Rules - You have to be a little more familiar with the
 Beagle/Dashboard code base to help out with this, but we need them for
 a huge spread of plugins, and almost everything beagle can
 generate./li/ul/ul


 Is there more stuff that have to be done?
 Is anybody working on dashboard?

 /nisse

 --
 Nils-Erik Svangård
 E-Mail: [EMAIL PROTECTED]
 MSN: [EMAIL PROTECTED]
 Skype: schweingaard
 Mobil: +46-(0)70-3612178
 ___
 Dashboard-hackers mailing list
 Dashboard-hackers@gnome.org
 http://mail.gnome.org/mailman/listinfo/dashboard-hackers

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard-hackers Digest, Vol 41, Issue 22

2007-09-27 Thread Dirk Uys
On 9/26/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
 Send Dashboard-hackers mailing list submissions to
   dashboard-hackers@gnome.org

 To subscribe or unsubscribe via the World Wide Web, visit
   http://mail.gnome.org/mailman/listinfo/dashboard-hackers
 or, via email, send a message with subject or body 'help' to
   [EMAIL PROTECTED]

 You can reach the person managing the list at
   [EMAIL PROTECTED]

 When replying, please edit your Subject line so it is more specific
 than Re: Contents of Dashboard-hackers digest...


 Today's Topics:

1. Re: time and date in
   ./beagle/Indexes/IndexingService/Index/PrimaryIndex/_xxx.cfs (D Bera)
2. eating cpu with a queue full of http urls (Brian J. Murrell)


 --

 Message: 1
 Date: Tue, 25 Sep 2007 14:01:10 -0400
 From: D Bera [EMAIL PROTECTED]
 Subject: Re: time and date in
   ./beagle/Indexes/IndexingService/Index/PrimaryIndex/_xxx.cfs
 To: armin schaefer [EMAIL PROTECTED]
 Cc: dashboard-hackers@gnome.org
 Message-ID:
   [EMAIL PROTECTED]
 Content-Type: text/plain; charset=ISO-8859-1

  i just had a look at my
  ./beagle/Indexes/IndexingService/Index/PrimaryIndex/_xxx.cfs
  - File and was wondering about the timestamps.

 What timestamps ? These are lucene data files. Do you mean strings in
 those files of the form mmddhhmmss ?

  It looks like:
  mmddhhmmss

 Just for reference, beagle stores its timestamp in that string format.

  is this correct?
  It would mean i worked on 23th december last year, and for sure i don't.

 I am all confused. Please elaborate.

 - dBera

 --
 -
 Debajyoti Bera @ http://dtecht.blogspot.com
 beagle / KDE fan
 Mandriva / Inspiron-1100 user


 --

 Message: 2
 Date: Wed, 26 Sep 2007 09:22:16 -0400
 From: Brian J. Murrell [EMAIL PROTECTED]
 Subject: eating cpu with a queue full of http urls
 To: dashboard dashboard-hackers@gnome.org
 Message-ID: [EMAIL PROTECTED]
 Content-Type: text/plain; charset=us-ascii

 I'm running beagle 0.2.18-0ubuntu2 on Ubuntu gutsy.  beagled seems to
 start it's indexing just fine and moves along well until it gets to a
 point of eating near 100% of one of my cpu cores and the scheduler queue
 looks something like:

 Scheduler:
 Count: 1464
 Status: Executing task
 Delayed 0 (25/09/2007 2:33:05 PM)
 /home/brian/.evolution/mail/imap/[EMAIL PROTECTED]/folders/INBOX/summary



 Pending Tasks:
 1 Immediate 0 (25/09/2007 2:40:54 PM)
 http://www.google.ca/search?q=mythweathersourceid=navclient-ffie=UTF-8rlz=1B3GGGL_en___CA228

 2 Immediate 0 (25/09/2007 2:40:56 PM)
 http://www.mythtv.org/docs/mythtv-HOWTO-18.html

 3 Immediate 0 (25/09/2007 3:44:02 PM)
 http://en.wikipedia.org/wiki/foo

 4 Immediate 0 (25/09/2007 3:44:12 PM)
 http://en.wikipedia.org/w/index.php?title=fooredirect=no

 5 Immediate 0 (25/09/2007 3:44:15 PM)
 http://en.wikipedia.org/wiki/bar

 6 Immediate 0 (25/09/2007 3:48:39 PM)
 http://en.wikipedia.org/wiki/Category:foobar

 7 Immediate 0 (25/09/2007 3:48:52 PM)
 http://en.wikipedia.org/wiki/Category:foo

 8 Immediate 0 (25/09/2007 3:48:56 PM)
 http://en.wikipedia.org/wiki/foo

 9 Immediate 0 (25/09/2007 3:51:19 PM)
 http://en.wikipedia.org/wiki/foo

 10 Immediate 0 (25/09/2007 3:52:05 PM)
 http://en.wikipedia.org/wiki/bar

 11 Immediate 0 (25/09/2007 3:52:24 PM)
 http://en.wikipedia.org/wiki/foo

 12 Immediate 0 (25/09/2007 4:09:55 PM)
 http://games.slashdot.org/article.pl?sid=07/09/25/1437249from=rss

 13 Immediate 0 (25/09/2007 4:10:25 PM)
 http://slashdot.org/article.pl?sid=07/09/25/1240249from=rss

 14 Immediate 0 (25/09/2007 4:18:03 PM)
 http://apple.slashdot.org/article.pl?sid=07/09/25/1136228from=rss

 15 Immediate 0 (25/09/2007 4:20:22 PM)
 http://yro.slashdot.org/article.pl?sid=07/09/25/1149205from=rss

 16 Immediate 0 (25/09/2007 4:35:54 PM)
 http://hardware.slashdot.org/article.pl?sid=07/09/25/0155219from=rss

 17 Immediate 0 (25/09/2007 4:38:56 PM)
 http://it.slashdot.org/article.pl?sid=07/09/25/0148247from=rss

 That queue doesn't seem to change over time, so something certainly
 appears stuck and spinning.

 I run Firefox as my browser with v0.6 of the Beagle Indexer plugin.

 Ideas?

 b.

 --
 My other computer is your Microsoft Windows server.

 Brian J. Murrell
 -- next part --
 A non-text attachment was scrubbed...
 Name: not available
 Type: application/pgp-signature
 Size: 189 bytes
 Desc: This is a digitally signed message part
 Url :
 /archives/dashboard-hackers/attachments/20070926/4f5cfc76/attachment.bin

 --

 ___
 Dashboard-hackers mailing list
 Dashboard-hackers@gnome.org
 http://mail.gnome.org/mailman/listinfo/dashboard-hackers


 End of Dashboard-hackers Digest, Vol 41, Issue 22
 *

___

Re: Dashboard Dbus Frontend

2007-08-15 Thread kim wroblewski
Neat.  The idea is that all of this information would come up as a
notification on the side?

Thanks,
Yes, each tile is its own notification popup on the side.
It's nice how the dashboard popups integrate and inter-mix with other
notifications like logins and warnings.

I think it is interesting that the layout is completely based on the quality
of the information sent.
Dashboard presents prioritized information.
Notify has logic that displays information.

There is one visual field, but there are many sources of information.
Even if the visual field is multi-dimensional, complex or changing:
Dashboard can concentrate on following the task at hand as clued by the
user's apps.
Notify can concetrate on displaying priority information.

The dashboard currently states when the tile should be shown and taken down.
It says:
What information is shown.
What priority it is.
What type it is.

A popup is a stackable block that can contain widgets tailored to displaying
'types' of information.
Current types are:
* text
* picture
* url, with an application chooser
* button, that executes a callback function

Is there an application which would be impossible to make with popups?

Could a text editor be made where each dialogue box was a specified popup
box to appear at a given location in a given context? And for the file
dialogue box to appear when it was appropriate? The easiest set of rules is
to say the box should be shown at all times in all cases.

(a)unobtrusive to the user
(b)a dedicated Dashboard UI is pretty useful on its own as well.

The easy answer is, 'dedicated' means stable across space and time. And
dashboard currently says when a popup-tile goes up and comes down.

The hard answer is, Dashboard need not be a second class citizen.

A Beagle-Filter for scoring how we view images is the same as a set of rules
that lays-out graphical information popups, only running in the other
direction.

image - priority list
prioritized list - image

The rules I am using in my Image Filter are taken from classical image
composition. Constraint rules such as:
1)The most important element takes up the greatest area.
2)The most important element has the greatest value contrast.
3)The most important element has the most saturation.
4)The most important element has complimentary colors at it's boarder.
5)The circle has a higher visual attention score than a square.
6)pop-art icons score higher than foreign shapes.
7)progressions of space divisions, or gradients have an attention gradient
8)symmetry develops visual tension.
9)golden ratios develops visual relaxation.
10)tangency develops visual tension.
11)a subsection of color is relative to it's context
etc.
*For pictures you look at day-in and day-out, you can add rules of
reinforcement-association, as your autonomic reactions learn instinctual
responses for locations and behaviors. Thresholds above which increases
attention scores.

From what I have seen, previous tries at dynamic UI layout were unable to
apply such constraint rules effectively because it did not 'know' the task
at hand, and the priority of interest for that task.

Or if it was given the task priority, the constraint-rules were lacking any
real expert knowledge and it was more of an academic exercise. Maybe a
system dedicated to collecting such contextual task information is prime to
drive such a layout machine.

Circuit board layout seems no more complicated than plotting
information-layouts.

If it sees that your going to put your glass down, it pops up a coaster.
If it sees that your typing C# code, it alerts you the food store closes in
30 minutes.
If it sees that your watching a movie, it takes down the clock popup.

The intrusion is the priority.

The human body has both more thoughtful motives and autonomic reactions.
They compete for your attention.

Right now we have 95% app/5% toolbar ratio.
The 95% is used to show search engine results, and web-design layouts.

When Dashboard starts firing notifications of more interest than going to a
public search engine, or website directly, it will command more screen
realestate.

For example, I'm sick of checking my bank account with the human
web-interface. It's a terrible interface to return a single integer. Can we
put in a Beagle Filter for 'web screen-scrapers'?
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard Dbus Frontend

2007-08-13 Thread Joe Shaw
Hi,

On 8/12/07, kim wroblewski [EMAIL PROTECTED] wrote:
 Here is a screenshot of a notify popup frontend to Dashboard that reuses the
 gnome thumbnails:

 http://geocities.com/kimwroblewski/dashboard/dashboard-popups-thumbs.jpg

 This removes all graphical dependencies from Dashboard.

Neat.  The idea is that all of this information would come up as a
notification on the side?

I think there's utility to this, although I think that a dedicated
Dashboard UI is pretty useful on its own as well.  One of the biggest
challenges to Dashboard is how to present the UI such that it is (a)
unobtrusive to the user but (b) readily accessible.  There is also an
open question of how to present some information to a user who might
find it interesting but who might also not go out looking for it; that
seems like it would conflict with (a) above.

By the way, thanks for the work you've been doing on Dashboard!  It's
nice to see that someone is picking up the project again and hacking
on it.

Joe
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard Icons

2007-08-10 Thread kim wroblewski
A guess of the top of my head WRT images: they're probably not being
disposed, so the image data is never being freed.

Yep, the original pixbuf was not being disposed of after it was scaled down.
As usual the source of the problem was me.

--
dashboard
all pixbufs set to null, text labels only
virtual memory MiB, Residient Memory Mib
clue1: 321.0, 50.2
clue2: 321.5, 51.3
clue3: 321.9, 51.9
clue4: 324.1, 52.4
clue5: 324.3, 53.0
clue6: 324.6, 53.6
clue7: 325.0, 54.2
clue8: 325.2, 55.2
--
dashboard
prescaled 50x50 pixbufs
virtual memory MiB, Residient Memory Mib
start: 205.7, 27.9
clue1: 320.8, 48.7
clue2: 321.0, 48.9
clue3: 321.1, 49.1
clue4: 322.0, 49.9
clue5: 322.0, 49.9
clue6: 323.5, 50.5
clue7: 323.5, 50.6
clue8: 323.5, 50.7
-
dashboard
full size / GC.Collect
resident memory
start: 28.0
clue1: 54.4
clue2: 51.2
clue3: 25.6
clue4: 300-17.1
clue5: 51.6
clue6: 19.4
clue7: 28.1
clue8: 28.4
-
dashboard
fullsized pixbuf input
virtual memory MiB, Residient Memory Mib
start: 269.7, 27.9
clue1: 514.3, 223.4
clue3: 601.2, 245.9
clue4: 617.7, 303.1
clue5: 446.4, 108.3
clue6: 520.7, 214.1
clue7: 629.9, 262.7
clue8: 590.5, 217.3
-
dashboard
all pixbuf thumbnails fullsize
Heap-Shot at clue4
typeInstancesMemorySizeAvg.Size
string  8,521 582,216  68
System.Collections.Hashtable/Slot[] 105  197.304  1,879
Sytem.MonoType7,102 170,448  24
Glib.Signal1,920 138,240  72
System.Reflection.MonoMethod2,832 113,280  40
Dashboard.Client.Tiles.Filetile464  66,816   144
Gtk.Image928  66,816   72

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard Icons

2007-08-09 Thread kim wroblewski
Maybe low memory had something todo with the odd behavior of LoadMimeIcon.
I can't recreate the error now.
I had several processes that maxed out my memory.
All thumbnails and icons are sucessfully displayed intermixed.


dashboard memory usage with 50x50 thumbnails only:
start0: 205.9,  28.1
clue 1: 407.5, 129.4
clue 2: 529.3, 217.2
clue 3: 549.6, 235.6
clue 4: 609.9, 182.7
clue 5: 609.9, 221.1
clue 6: 608.9, 208.9
clue 7: 609.9, 220.7
clue 8: 609.9, 223.1


dashboard with icons only:
start0: 226.3, 37.4
clue 1: 261.1, 53.7
clue 2: 325.9, 55.0
clue 3: 326.2, 55.6
clue 4: 328.7, 56.7
clue 5: 329.5, 57.7
clue 6: 330.0, 58.9
clue 7: 330.4, 59.8
clue 8: 330.5, 60.8
clue 9: 331.4, 61.5
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard Icons

2007-08-09 Thread Joe Shaw
Hi,

On 8/9/07, kim wroblewski [EMAIL PROTECTED] wrote:
 Maybe low memory had something todo with the odd behavior of LoadMimeIcon.
 I can't recreate the error now.
 I had several processes that maxed out my memory.

What are these numbers, VSize and RSS?

Those are obviously huge; you'll probably want to use the heap-buddy
and heap-size profilers to see what the heck is going on there.

A guess of the top of my head WRT images: they're probably not being
disposed, so the image data is never being freed.

Joe
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard Design Questions and Other Stuff

2006-10-18 Thread Andrew Ruthven
On Thu, 2006-10-19 at 00:28 -0400, Kevin Kubasik wrote:
 Hey, I was just hacking around with dashboard again tonight and I was
 looking into more frontends and I just started to realize how much
 duplicate information were gonna have flying around so I wanted to bring
 up a few points.

Its great to see someone picking it up again.  Good stuff.

 My first point is, that while the window stuff is really cool. (I love
 that dashboard can be workspace aware etc) but we need to have a better
 fallback, since at the moment, if a cluepacket goes in with a bad
 window, the UI just crashes. Duh, most of dashboard is proof of concept
 at the point and its really just being revived now, but still that makes
 stirring up interest in 3rd parties very difficult, and makes it hard to
 get that 'cool, and almost useful factor working for us.

Surely this is part of making Dashboard more robust and able to take
whatever crap is thrown at it and do the right thing.

Perhaps it is time to start thinking about writing some test framework
as well.  :(

 My other question is how we want to handle frontends when the program
 offers no realistic interface for doing this? Will we have another
 daemon such as beagle to crawl/watch files? On the same note, writing a
 gaim plugin has been rough, as getting that compliant xml out of C is a
 little beyond me. But watching dbus for the gaim events and using that
 is really easy, do we want to do that? If so, how exactly do I proceed
 in making this fit into the current dashboard framework.

Why do we need another daemon for crawling/watching files?  I thought
that was the intention of Beagle.  Beagle is intended to index all the
various bits and pieces and Dashboard queries it.  Dashboard could then
generate more cluepackets based on the results from Beagle.

Hopefully Dashboard will be able to make use of the same viewers (ie,
Gaim logs) as Beagle provides.

Can you not use the old Gaim plugin that used to exist?  Have things
moved on to much since then?  (I wouldn't be surprised if that is the
case!)  And if there are issues with generating the XML from C, then it
is something we should be providing in a library.  This would
(hopefully) ease the acceptance by third parties.

 I realize this is pretty much directed at fredrik, but I figured since
 the mailing list is still called dashboard-hackers I could get away with
 it. ;)

Beagle can't hide his origins!

Cheers!

-- 
Andrew Ruthven, Wellington, New Zealand
At home: [EMAIL PROTECTED]   |  This space intentionally
 |left blank.

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard-hackers Digest, Vol 28, Issue 30

2006-09-03 Thread Pierre Östlund

Tom Lofts skrev:
I have the same problem, so installed and ran the patch - output is 
below.


Might the problem be something to do with the fact my thunderbird 
folders are in a none standard location (/media/mine/Tom/Mail/Local 
Folders)?


Cheers,

Tom
I'm noting a very strange behaviour here and my last patch is yet not 
giving me enough information to troubleshoot this (man is this 
frustrating). So... I've created a patch that should print enough 
information to figure out what's (not) going on.


The problem itself can be traced to somewhere near the IndexFile-method, 
which is supposed to create an IndexableGenerator that indexes all mails 
(or what's supposed to be indexed). This leaves us with aprox. three 
different outcomes:

1. The internals that handle which accounts to index contains a bug
2. The account type associated to a certain file is not supported or not 
activated (might be parsing errors when reading Thunderbird's preference 
file)

3. Reported file size of files to index are zero

My guess would be that we land somewhere near number one in the list 
above. This time though, debugging should be a lot easier. Non-standard 
file location could be the reason, but there's no reason it should.


Thanks!

Pierre

PS. Joe: It would be very kind of you if you could commit this patch. 
This patch includes everything from the old patch and some new stuff. 
Thanks! DS.
--- Util/Thunderbird.cs	22 Aug 2006 19:59:36 -	1.3
+++ Util/Thunderbird.cs	3 Sep 2006 17:17:19 -
@@ -747,18 +747,19 @@
 
 try {
 	string key = reg.Match (line).Result (${key});
+	Match m = id_reg.Match (key);
 
-	if (key.StartsWith (account.account)) {
+	if (key.StartsWith (account.account)  m.Success) {
 		if (Debug)
-			Logger.Log.Debug (account.account: {0}, id_reg.Match (key).Result (${id}));
+			Logger.Log.Debug (account.account: {0}, m.Result (${id}));
 
-		accounts.Enqueue (id_reg.Match (key).Result (${id}));
+		accounts.Enqueue (m.Result (${id}));
 	}
 
 	tbl [key] = reg.Match (line).Result (${value});
 } catch (Exception e) { 
 	if (Debug)
-		Logger.Log.Debug (e, ReadAccounts 1:);
+		Logger.Log.Debug (e, ReadAccounts 1);
 }
 			}
 			
@@ -783,7 +784,7 @@
 		(string) tbl [id + .directory], Convert.ToInt32 ((string) tbl [id + .port]), type, delimiter));
 } catch (Exception e) {
 	if (Debug)
-		Logger.Log.Debug (e, ReadAccounts 3:);
+		Logger.Log.Debug (e, ReadAccounts 3: {0}, e);
 	continue;
 }
 			}

--- beagled/ThunderbirdQueryable/ThunderbirdIndexer.cs	4 Aug 2006 03:24:51 -	1.1
+++ beagled/ThunderbirdQueryable/ThunderbirdIndexer.cs	3 Sep 2006 17:17:20 -
@@ -106,6 +106,9 @@
 			
 			foreach (string path in root_paths) {
 foreach (TB.Account account in Thunderbird.ReadAccounts (path)) {
+	if (Thunderbird.Debug)
+		Logger.Log.Debug (Processing {0} ({1}), account.Server, account.Path);
+	
 	if (Shutdown.ShutdownRequested)
 		return;
 	
@@ -129,6 +132,11 @@
 		public void IndexAccount (TB.Account account)
 		{
 			TB.Account stored_account = GetParentAccount (account.Path);
+			
+			if (Thunderbird.Debug) {
+Logger.Log.Debug (Request to index: {0} ({1}) {2}, 
+	account.Server, account.Path, (Directory.Exists (account.Path) ? Ok : Failed));
+			}
 
 			// We need to act upon changes made to accounts during Thunderbird runtime.
 			// The user might change from plain to SSL, which leads to a new port number
@@ -136,12 +144,21 @@
 			if (stored_account == null  Directory.Exists (account.Path)  supported_types [account.Type] != null) {
 account_list.Add (account);
 IndexDirectory (account.Path);
-//Logger.Log.Info (Indexing {0} account {1}, account.Type.ToString (), account.Server);
+
+if (Thunderbird.Debug)
+	Logger.Log.Debug (Indexing {0} account {1} ({2}), account.Type.ToString (), account.Server, account.Path);
 			
-			} else if (stored_account == null  File.Exists (account.Path)  supported_types [account.Type] != null) {
-account_list.Add (account);
-IndexFile (account.Path);
-//Logger.Log.Info (Indexing {0} account {1}, account.Type.ToString (), account.Server);
+			} else if (stored_account == null  File.Exists (account.Path)  supported_types [account.Type] != null) {
+try {
+	account_list.Add (account);
+	IndexFile (account.Path);
+} catch (Exception e) {
+	Logger.Log.Error (e, Failed to index {0}: {1}, account.Path, e.Message);
+	return;
+}
+
+if (Thunderbird.Debug)
+	Logger.Log.Debug (Indexing {0} account {1} ({2}), account.Type.ToString (), account.Server, account.Path);
 
 			} else if (stored_account != null 
 (stored_account.Server != account.Server ||
@@ -152,6 +169,9 @@
 account_list.Remove (stored_account);
 account_list.Add (account);
 
+if (Thunderbird.Debug)
+	Logger.Log.Debug (Removed: {0}, Added: {1}, stored_account.Path, account.Path);
+
 // 

Re: Dashboard-hackers Digest, Vol 28, Issue 30

2006-08-31 Thread Pierre Östlund
Richard Corbin skrev:
 Gentlemen:

 I installed Beagle 0.2.8 from http://us.ubuntu.cafuego.net/ specifically 
 for its Thunderbird support. At first I didnt see the Thunderbird 
 backend. Eventually I figured out that I had to also install the 
 beagle-backend-evolution (even though I dont use evolution). But after 
 two days of indexing, there are still zero Thunderbird emails indexed 
 (and there should be several thousand). I would add that I moved the 
 folder that contains the emails to another partition, but made all 
 necessary configuration changes in Thunderbird, which works fine.
   
This is probably the same bug as noted a couple of days ago. You should 
check out this e-mail:

http://mail.gnome.org/archives/dashboard-hackers/2006-August/msg00085.html

I can't really fix this until someone tries out the patch in the mail 
above and publish the more extended debugging data. If someone could try 
it out, it would be very appreciated.

Thanks!

Pierre
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard-hackers Digest, Vol 28, Issue 30

2006-08-31 Thread Tom Lofts

I have the same problem, so installed and ran the patch - output is below.

Might the problem be something to do with the fact my thunderbird 
folders are in a none standard location (/media/mine/Tom/Mail/Local 
Folders)?


Cheers,

Tom

Pierre Östlund wrote:

Richard Corbin skrev:
  

Gentlemen:

I installed Beagle 0.2.8 from http://us.ubuntu.cafuego.net/ specifically 
for its Thunderbird support. At first I didnt see the Thunderbird 
backend. Eventually I figured out that I had to also install the 
beagle-backend-evolution (even though I dont use evolution). But after 
two days of indexing, there are still zero Thunderbird emails indexed 
(and there should be several thousand). I would add that I moved the 
folder that contains the emails to another partition, but made all 
necessary configuration changes in Thunderbird, which works fine.
  

This is probably the same bug as noted a couple of days ago. You should 
check out this e-mail:


http://mail.gnome.org/archives/dashboard-hackers/2006-August/msg00085.html

I can't really fix this until someone tries out the patch in the mail 
above and publish the more extended debugging data. If someone could try 
it out, it would be very appreciated.


Thanks!

Pierre
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

  


060831 1855025150 06845 Beagle DEBUG: Starting Beagle Daemon (version 0.2.7)
060831 1855025474 06845 Beagle DEBUG: Running on Mono 1.1.13.6
060831 1855025481 06845 Beagle DEBUG: Command Line: 
/usr/local/lib/beagle/BeagleDaemon.exe --bg
060831 1855025609 06845 Beagle  WARN: Extended attributes are not supported on 
this filesystem.  Performance will suffer as a result.
060831 1855025630 06845 Beagle DEBUG: Unable to establish a connection to the X 
server
060831 1855031938 06845 Beagle DEBUG: Starting main loop
060831 1855031960 06845 Beagle DEBUG: Beginning main loop
060831 1855031969 06845 Beagle DEBUG: Starting messaging server
060831 1855032323 06845 Beagle DEBUG: Starting QueryDriver
060831 1855034351 06845 Beagle DEBUG: Found index helper at 
/usr/local/lib/beagle/beagled-index-helper
060831 1855034877 06845 Beagle DEBUG: Found 2 backends in 
/usr/local/lib/beagle/Backends/EvolutionBackends.dll
060831 1855035243 06845 Beagle DEBUG: Running Thunderbird backend in debug mode
060831 1855035247 06845 Beagle DEBUG: Found 1 backends in 
/usr/local/lib/beagle/Backends/ThunderbirdBackends.dll
060831 1855035900 06845 Beagle DEBUG: KMail folders not found. Will keep trying 
060831 1855036412 06845 Beagle DEBUG: Starting Inotify Backend
060831 1855050464 06845 Beagle DEBUG: KonqCacheDir: /var/tmp/kdecache-tom/http
060831 1855050621 06845 Beagle DEBUG: Found 10 backends in 
/usr/local/lib/beagle/BeagleDaemonLib.dll
060831 1855050636 06845 Beagle DEBUG: Reading mapping from filters
060831 1855050903 06845 Beagle DEBUG: Loading user-configured static indexes.
060831 1855050908 06845 Beagle DEBUG: Found 0 user-configured static indexes..
060831 1855050910 06845 Beagle DEBUG: Waiting 60 seconds before starting 
queryables
060831 1855050922 06845 Beagle DEBUG: Starting Scheduler thread
060831 1855050940 06845 Beagle DEBUG: Starting Inotify threads
060831 1855051091 06845 Beagle DEBUG: Daemon initialization finished after 1.91s
060831 1856050967 06845 Beagle DEBUG: Starting queryables
060831 1856050972 06845 Beagle DEBUG: Starting backend: 'EvolutionDataServer'
060831 1856050982 06845 Beagle DEBUG: Starting backend: 'EvolutionMail'
060831 1856050989 06845 Beagle DEBUG: Starting backend: 'Thunderbird'
060831 1856051001 06845 Beagle DEBUG: Starting backend: 'KMail'
060831 1856051020 06845 Beagle DEBUG: Starting Evolution mail backend
060831 1856051041 06845 Beagle DEBUG: Starting backend: 'Files'
060831 1856051062 06845 Beagle DEBUG: Adding root: /home/tom
060831 1856051139 06845 Beagle DEBUG: Starting KMail backend
060831 1856051150 06845 Beagle DEBUG: KMail directories (local mail) 
/home/tom/.kde/share/apps/kmail/dimap not found, will repoll.
060831 1856051039 06845 Beagle DEBUG: Starting Thunderbird backend
060831 1856051644 06845 Beagle DEBUG: Starting mail crawl
060831 1856055879 06845 Beagle DEBUG: Will index mbox 
/home/tom/.evolution/mail/local/Inbox
060831 1856056025 06845 Beagle DEBUG: Opening mbox Inbox
060831 1856056209 06845 Beagle DEBUG: Overall percent is 0
060831 1856056230 06845 Beagle DEBUG: Mail crawl finished
060831 1856056232 06845 Beagle DEBUG: Evolution mail driver worker thread done 
in .52s
060831 1856060194 06845 Beagle DEBUG: account.account: 1
060831 1856060509 06845 Beagle DEBUG: Inbox: Finished indexing 1 messages
060831 1856060524 06845 Beagle DEBUG: account.account: 2
060831 1856060528 06845 Beagle DEBUG: account.account: 3
060831 1856060532 06845 Beagle DEBUG: account.account: 4
060831 1856060535 06845 Beagle DEBUG: account.account: 5
060831 1856060538 06845 Beagle DEBUG: account.account: 7
060831 

Re: Dashboard-hackers Digest, Vol 28, Issue 30

2006-08-30 Thread Richard Corbin
Gentlemen:

I installed Beagle 0.2.8 from http://us.ubuntu.cafuego.net/ specifically 
for its Thunderbird support. At first I didnt see the Thunderbird 
backend. Eventually I figured out that I had to also install the 
beagle-backend-evolution (even though I dont use evolution). But after 
two days of indexing, there are still zero Thunderbird emails indexed 
(and there should be several thousand). I would add that I moved the 
folder that contains the emails to another partition, but made all 
necessary configuration changes in Thunderbird, which works fine.

What have I done wrong?

Cordially,
Richard

Here is the log (after I executed command beagled --replace 
--allow-backend Thunderbird)


060830 1934409248 05726 Beagle DEBUG: Starting Beagle Daemon (version 0.2.8)
060830 1934409461 05726 Beagle DEBUG: Running on Mono 1.1.13.6
060830 1934409468 05726 Beagle DEBUG: Command Line: 
/usr/lib/beagle/BeagleDaemon.exe --replace --allow-backend Thunderbird --bg
060830 1934409589 05726 Beagle DEBUG: Established a connection to the X 
server
060830 1934413140 05726 Beagle DEBUG: Starting main loop
060830 1934413184 05726 Beagle DEBUG: Beginning main loop
060830 1934413191 05726 Beagle DEBUG: Starting messaging server
060830 1934413357 05726 Beagle DEBUG: Attempting to replace another beagled.
060830 1934413363 05726 Beagle DEBUG: Sending Shutdown
060830 1934425303 05726 Beagle DEBUG: Starting messaging server
060830 1934425336 05726 Beagle DEBUG: Starting QueryDriver
060830 1934425381 05726 Beagle DEBUG: Found 0 backends in 
/usr/lib/beagle/Backends/EvolutionBackends.dll
060830 1934425890 05726 Beagle DEBUG: Found index helper at 
/usr/lib/beagle/beagled-index-helper
060830 1934425951 05726 Beagle DEBUG: Found 1 backends in 
/usr/lib/beagle/Backends/ThunderbirdBackends.dll
060830 1934426001 05726 Beagle DEBUG: Found 0 backends in 
/usr/lib/beagle/BeagleDaemonLib.dll
060830 1934426011 05726 Beagle DEBUG: Reading mapping from filters
060830 1934426127 05726 Beagle DEBUG: Loading system static indexes.
060830 1934426137 05726 Beagle DEBUG: Found 0 system-wide indexes.
060830 1934426151 05726 Beagle DEBUG: Found 0 user-configured static 
indexes..
060830 1934426153 05726 Beagle DEBUG: Waiting 60 seconds before starting 
queryables
060830 1934426167 05726 Beagle DEBUG: Starting Scheduler thread
060830 1934426210 05726 Beagle DEBUG: Starting Inotify threads
060830 1934426316 05726 Beagle DEBUG: Loading 
Beagle.Util.Conf+IndexingConfig from indexing.xml
060830 1934426497 05726 Beagle DEBUG: Loading 
Beagle.Util.Conf+DaemonConfig from daemon.xml
060830 1934426519 05726 Beagle DEBUG: Loading 
Beagle.Util.Conf+SearchingConfig from searching.xml
060830 1934426644 05726 Beagle DEBUG: Loading 
Beagle.Util.Conf+NetworkingConfig from networking.xml
060830 1934426661 05726 Beagle DEBUG: Loading 
Beagle.Util.Conf+WebServicesConfig from webservices.xml
060830 1934426699 05726 Beagle DEBUG: Daemon initialization finished 
after 1.35s
060830 1935240718 05726 Beagle DEBUG: Caught ResponseMessageException: 
Connection refused
060830 1935240722 05726 Beagle DEBUG: InnerException is SocketException 
-- we probably need to launch a helper
060830 1935240732 05726 Beagle DEBUG: Launching helper process
060830 1935240937 05726 Beagle DEBUG: IndexHelper PID is 5746
060830 1935245972 05726 Beagle DEBUG: Found IndexHelper (5746) in .50s
060830 1935426227 05726 Beagle DEBUG: Starting queryables
060830 1935426228 05726 Beagle DEBUG: Starting backend: 'Thunderbird'
060830 1935426242 05726 Beagle DEBUG: Starting Thunderbird backend
060830 1935428216 05726 Beagle DEBUG: Indexing 2 (2) Thunderbird 
account(s) spread over 1 profile(s)
060830 1935428219 05726 Beagle DEBUG: Thunderbird backend done in 0.197053s

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard-hackers Digest, Vol 25, Issue 3

2006-05-05 Thread ivo welch

I do not know much about the beagle internals, but there are very nice
imap libraries in perl, that would make it a 1-hour affair to write a
program that downloads all emails from an imap server and hands them
to beagle...

On 5/4/06, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:

Send Dashboard-hackers mailing list submissions to
dashboard-hackers@gnome.org

To subscribe or unsubscribe via the World Wide Web, visit
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]

You can reach the person managing the list at
[EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than Re: Contents of Dashboard-hackers digest...


Today's Topics:

   1. Re: beagle imap handling? (David Aveiro)
   2. Re: beagle imap handling? (Joe Shaw)


--

Message: 1
Date: Wed, 03 May 2006 17:03:28 +0100
From: David Aveiro [EMAIL PROTECTED]
Subject: Re: beagle imap handling?
To: dashboard-hackers@gnome.org
Cc: Joe Shaw [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1

Joe Shaw wrote:
 The obvious downside to having your mail program cache data locally is
 that it uses some additional disk space, but if it's a true cache it
 should be able to clean itself up from time to time.  Otherwise, it's
 probably a bug in the mail reader.

Yes that's precisely my problem, I have about 1GB of email (tens of
thousands of files - Maildir format), and having that replicated is a lot :)

What do you mean by cache clean itself? Evolution cleans the cache after
a while (like erases mails from cache that aren't viewed for a long time)?

If beagle had indexed all cached emails and then they disappear from
cache but beagle can still search for it, that would be ok for me...

But I would need to first somehow make evolution fetch all messages from
IMAP server and put them in cache... Ideas for this?

David


--

Message: 2
Date: Wed, 03 May 2006 12:07:51 -0400
From: Joe Shaw [EMAIL PROTECTED]
Subject: Re: beagle imap handling?
To: David Aveiro [EMAIL PROTECTED]
Cc: dashboard-hackers@gnome.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain

Hi,

On Wed, 2006-05-03 at 17:03 +0100, David Aveiro wrote:
 Yes that's precisely my problem, I have about 1GB of email (tens of
 thousands of files - Maildir format), and having that replicated is a lot :)

Yeah.  I am in a similar boat.

 What do you mean by cache clean itself? Evolution cleans the cache after
 a while (like erases mails from cache that aren't viewed for a long time)?

Well, a cache should only make things more efficient, it shouldn't be
strictly necessary.  As a colleague of mine once said, A cache that
never cleans up after itself isn't a cache, it's a leak.  I don't know
if Evolution cleans up after itself in low disk situations.

 If beagle had indexed all cached emails and then they disappear from
 cache but beagle can still search for it, that would be ok for me...

Yeah, I would be fine with Beagle having some way to signal to the mail
clients, Hey, I'm interested in this email, can you pull it down for
me?  But scale is always a problem.  That's probably fine for 1, 2, 20
emails, but if Beagle is consistently asking for 40,000 emails it'll
saturate your network connection.

 But I would need to first somehow make evolution fetch all messages from
 IMAP server and put them in cache... Ideas for this?

I believe if you right click on the folder, go to Properties, and check
the Copy folder content locally for offline operation checkbox it will
do it.  If you have local filters you run on messages I think that will
do it as well.  And of course if you actually read the mail, that will
also cache it locally.

Joe



--

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


End of Dashboard-hackers Digest, Vol 25, Issue 3



___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard Compile Render Fixes

2006-03-16 Thread Joe Shaw
Hi,

On Wed, 2006-03-15 at 14:16 -0800, Matt Jones wrote:
 I fixed up dashboard so that it builds again. Most of the fixes involved
 replacing dashboard's gnome bindings with those from official *-sharp
 packages, updating -sharp packages to -sharp-2.0 packages, and updating
 the beagle api.
 
 I've tested the beagle backend with the file and email renderers.

These look good, I think they're fine to commit in light of the current
state of things. :)  So, go ahead.

 The path to the beagle UiUtil dll (for some gnome convenience functions)
 is hardcoded to /usr/lib/beagle/UiUtil (as it's not exposed in a pkg
 config file).

It'd be good to add that, if you wanted to whip up a beagle patch for
that.

 This wasn't really intended as a final solution - I'm actually in the
 process of rewriting dashboard to use the beagle-search UI, use beagle
 as a sole backend, and respond via d-bus rather than a tcp port. I might
 have a prototype available somewhere (probably gnomecvs) possibly this
 weekend.

I'm not totally sold on the beagle-search UI for dashboard, but it is
probably a decent first step.  One thing we realized with Dashboard is
that having different layouts and colors did a good job of naturally
segmenting the content and drawing attention to the different parts.

I don't think that using Beagle as the sole backend is a good idea
anymore.  I know I had advocated that in the past and I think the
current state of the Dashboard source represents my move in that
direction, but Beagle doesn't seem like the right place to do things
like Bugzilla or GeoSites queries.

D-BUS is probably a decent idea because it's becoming more common, but
the reason why we did it over a TCP socket is because it doesn't require
any additional libraries.  There's no dependency to add; you simply
#include the C file, pepper a few function calls in your app and you're
magically instrumented for dashboard.  That's not something to be taken
lightly.

 I was curious - what features did people find really useful about
 dashboard / what did they find annoying? Personally, the clue-chaining
 was really cool (i have some ideas on improving this i want to try out),
 which is the main reason I'm working on this.

I found the cluechaining to be the most useful and interesting part to
work on.  Getting focus right is also pretty tricky, especially when
you consider that there are different contexts within applications
(current mail you're viewing in Evo, current tab selected in Firefox,
gaim, gedit, etc.)

Joe

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard Compile Render Fixes

2006-03-16 Thread Matt Jones
Hi - 

I've attached a patch against beagle-0-0.pc.in to add UiUtil.dll to the
exported libs, and committed a fix to dashboard to use the pc definition
instead of hard-coding it.

On Thu, 2006-03-16 at 16:14 -0500, Joe Shaw wrote:
 These look good, I think they're fine to commit in light of the current
 state of things. :)  So, go ahead.

Done.

  This wasn't really intended as a final solution - I'm actually in the
  process of rewriting dashboard to use the beagle-search UI, use beagle
  as a sole backend, and respond via d-bus rather than a tcp port. I might
  have a prototype available somewhere (probably gnomecvs) possibly this
  weekend.
 
 I'm not totally sold on the beagle-search UI for dashboard, but it is
 probably a decent first step.  One thing we realized with Dashboard is
 that having different layouts and colors did a good job of naturally
 segmenting the content and drawing attention to the different parts.

I agree with you on this point - I was planning on using the beagle
frontend for expediency purposes.

 I don't think that using Beagle as the sole backend is a good idea
 anymore.  I know I had advocated that in the past and I think the
 current state of the Dashboard source represents my move in that
 direction, but Beagle doesn't seem like the right place to do things
 like Bugzilla or GeoSites queries.

Agreed. Active queries would not be handled by beagle. 

 D-BUS is probably a decent idea because it's becoming more common, but
 the reason why we did it over a TCP socket is because it doesn't require
 any additional libraries.  There's no dependency to add; you simply
 #include the C file, pepper a few function calls in your app and you're
 magically instrumented for dashboard.  That's not something to be taken
 lightly.

Perhaps a combination? Now that so much software in gnome is providing
d-bus bindings of some sort, it seems that it would be a better choice
in terms of unification to provide a dbus mechanism for interaction.

Thanks,
--Matt Jones
? po/stamp-it
Index: beagle-0.0.pc.in
===
RCS file: /cvs/gnome/beagle/beagle-0.0.pc.in,v
retrieving revision 1.7
diff -u -p -r1.7 beagle-0.0.pc.in
--- beagle-0.0.pc.in	13 Jan 2006 19:53:00 -	1.7
+++ beagle-0.0.pc.in	16 Mar 2006 22:40:41 -
@@ -6,5 +6,5 @@ [EMAIL PROTECTED]@/beagle
 Name: Beagle
 Description: We Index Your Life
 Version: @VERSION@
-Libs: -r:${dlldir}/Beagle.dll -r:${dlldir}/Util.dll
+Libs: -r:${dlldir}/Beagle.dll -r:${dlldir}/Util.dll -r:${dlldir}/UiUtil.dll
 
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard Compile Render Fixes

2006-03-15 Thread Kevin Kubasik
linked Identities is a big one, noticing that I'm reading my friends
blog, and hes online type stuff. (A tough example, but yeah) In
addition to remote queries (such as pulling up bugzilla bugs from an
email that has bugs listed etc) you might want to look into galago
some and pirate some of the cool statusy-dbus stuff going on there. We
had it in the original best interface, but lost it in our current
move.

Just a few of my random thoughts.

Cheers,
Kevin Kubasik

On 3/15/06, Matt Jones [EMAIL PROTECTED] wrote:
 Hi -

 I fixed up dashboard so that it builds again. Most of the fixes involved
 replacing dashboard's gnome bindings with those from official *-sharp
 packages, updating -sharp packages to -sharp-2.0 packages, and updating
 the beagle api.

 I've tested the beagle backend with the file and email renderers.

 The path to the beagle UiUtil dll (for some gnome convenience functions)
 is hardcoded to /usr/lib/beagle/UiUtil (as it's not exposed in a pkg
 config file).

 This wasn't really intended as a final solution - I'm actually in the
 process of rewriting dashboard to use the beagle-search UI, use beagle
 as a sole backend, and respond via d-bus rather than a tcp port. I might
 have a prototype available somewhere (probably gnomecvs) possibly this
 weekend.

 I was curious - what features did people find really useful about
 dashboard / what did they find annoying? Personally, the clue-chaining
 was really cool (i have some ideas on improving this i want to try out),
 which is the main reason I'm working on this.

 Thanks,

 --Matt Jones


 ___
 Dashboard-hackers mailing list
 Dashboard-hackers@gnome.org
 http://mail.gnome.org/mailman/listinfo/dashboard-hackers






--
Cheers,
Kevin Kubasik
http://blog.kubasik.net/
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard

2005-11-23 Thread Joel M
Can't you say it is a monitoring matching system against beagle for 
things you are doing currently.

Indexed data related to data you are using NOW?!

//Joel

Meulemeester Jan Dante wrote:


so if beagle is the file backend for dashboard then you can compare best
to dashboard only in a minor form or what?

greetings

Op wo, 23-11-2005 te 20:27 +0100, schreef giskard:
 


Il giorno mer, 23/11/2005 alle 20.09 +0100, Meulemeester Jan Dante ha
scritto:
  


What is the value that dashboard can give gnome users more than what
beagle can give them?



beagle support : BugzillaBackend.cs  GaleonBookmarksBackend.cs 
GoogleBackend.cs

ManPagesBackend.cs RhythmboxLibraryBackend.cs RSSBackend.cs
?

afaik beagle is the FILE backend of dashboard, i'm wrong?

  

Little information for users on the net about Dashboard although I 
heard

of it for more then a year now. For what there is to read
(http://www.nat.org/dashboard/) i think it would be great to have a
always on side-bar. But aren't these things explained on the slides and
the site possible with beagle if it uses better ui, sorting (project
holmes)



at the moment (imo) also holmes is not actively developed.
  


I can't really see the difference.



i see the difference :)
  



___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers



 




___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard

2005-11-23 Thread Joel M

Thats good toughts..
I whould be interested in hacking some on holmes
I just did this crappy Tomboy action, and I feel that I can do more.

It looked like it was just a hack fest nothing more :)


Meulemeester Jan Dante wrote:


well to quote someone before me on this list: hopefully it won't die in
CVS maybe there's need for a team that works on use cases,
usability, .. for dashboard, no coding yet. So Beagle can focus partly
on the advice of that team. Having those would be easyer for future
developpers of dashboard for coding.

greetings

Op wo, 23-11-2005 te 22:49 +0100, schreef giskard:
 


Il giorno mer, 23/11/2005 alle 21.56 +0100, Meulemeester Jan Dante ha
scritto:
   


so if beagle is the file backend for dashboard then you can compare best
to dashboard only in a minor form or what?
 


Best will be part of dashboard..at the moment, imho, is only a useful
tool to use beagle instead of waiting someone that will fix dashboard

   


greetings
 



___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers



 



___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Holmes (was Re: Dashboard)

2005-11-23 Thread Jon Trowbridge
On Wed, 2005-11-23 at 23:10 +0100, Joel M wrote:
 I whould be interested in hacking some on holmes
 I just did this crappy Tomboy action, and I feel that I can do more.
 
 It looked like it was just a hack fest nothing more :)

Good news: Holmes is being actively worked on inside of Novell.  We were
initially not able to make the work public for complicated (and boring)
reasons that aren't worth explaining.  The issues have have mostly been
sorted out, and I don't think it will be too much longer before the code
ends up in GNOME CVS along with the rest of Beagle.

-J




___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard frontend status?

2005-10-31 Thread Nat Friedman
On Mon, 2005-10-31 at 21:00 -0800, Alex Graveley wrote:
 Hi,
 
 Does anyone know anything of the current status regarding the various 
 dashboard frontend patches/plugins?  As in, do they still work at all?

Most have bitrotted, including Gaim and Evolution.  A few of them are
actually in vitro and probably still work, like the Abiword plugin.  

In the last few months I've several times started writing a simple
rules-based expert-system like Dashboard on a per-task basis, using your
focus-tracking code and some of those frontend patches.  No
cluechaining, no magic ranking, just simple rules like:

When I'm reading email, show

- other unread emails from the sender
- recent emails sent to the sender
- recent IM conversations with the sender
- recent blog entries from the sender
- highly-relevant recently viewed web pages related to
the email body
- highly-relevant recently viewed documents related to
the email body

When I'm browsing the web, show

- highly-relevant recently viewed documents related to
the page content
.
.
.

Etc.

I don't know if you're interested in reviving Dashboard, but if I were
to do it now, that's how I'd start.

Nat


___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard frontend status?

2005-10-31 Thread Nat Friedman
On Tue, 2005-11-01 at 00:53 -0500, Nat Friedman wrote:
 I don't know if you're interested in reviving Dashboard, but if I were

Dammit.  As soon as I hit Send I wished I'd used the word reanimating
instead of reviving.

Nat


___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


Re: Dashboard frontend status?

2005-10-31 Thread Nat Friedman
On Tue, 2005-11-01 at 00:53 -0500, Nat Friedman wrote:

 actually in vitro and probably still work, like the Abiword plugin.  

Also this should have been in utero.

Bed time,
Nat


___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers


previous Beagle as Web-Service Discussion Re: Dashboard integration into distributed enviroments

2005-04-16 Thread Srikant Jakilinki
Hi Daniel,
Please find below a discussion on these lines before. Apparently, the 
guy who started it was also Daniel :-)

I suppose that you meant something similar. Or if it is different, 
please let us know so that we can carry the discussion forward. In 
particular, if you have any use cases or scenarious.

I too think that Dashboard has quite a powerful framework in Beagle to 
do some wonderful things :-)

---
Regards-Cheers-Sincerely,
Srikant
http://sriks6711.blogspot.com
http://www.dcs.gla.ac.uk/~sriks
Maybe there is some truth about the mysticism in our part of the world 
that makes the complicated worth pursuing
-=-Sriksisms powered by Life, TagZilla and QOTD-=-

 Original Message 
Subject: Re: beagled Web Service Interface prototype working!
Date: Wed, 19 Jan 2005 02:57:32 -0700
From: Vijay KN [EMAIL PROTECTED]
To: dashboard-hackers@gnome.org, [EMAIL PROTECTED]
Daniele,
I agree - these are some cool ideas. The distributed environment can
allow peer-to-peer searching of Beagle services, within collaboration
teams in an intranet and with some security support added, sharing
information across Beagle services on the Internet.
I will look into the mDNSResponder stuff along with other discovery
mechanisms for discovering Beagle Web service.
Keep the ideas coming !
thanks
Vijay
 Daniele Bellucci [EMAIL PROTECTED] 01/19/05 3:42 AM 
Good catch ;)
it would be nice to use the web service in a multiuser machine.
For example a linux box with multiple account could expose
this web service, and each user can issue a separate query
on his home directory.
Another cool idea is to use the webservice on a distributed
environment where every machine expose its own web service for beagle.
Web services discovery could be handled by using the excellent
mDNSResponder since there is a plan to full integrate it in the
Gnome Environment, and a .NET binding has been cooded too.
IMHO this should be a great catch.
Il giorno mar, 18-01-2005 alle 12:09 -0700, Vijay KN ha scritto:
 Hi Folks!

 Today I finally got the Web Service interface to beagled working.
The
 Glib dependencies in dbus-sharp library prevented me from using dbus
IPC
 between the web service and beagled - so I had to resort to .Net
 remoting for now. The web service is in the form of beagled.asmx
webapp
 and needs XSP for now (until we add a httpListener within beagled).

 I have included two web service methods :
 1. beagledQuery - the full featured interface that can be invoked
via
 SOAP
 2. simplebeagledQuery - simpler interface that takes a searchString
 (like best) which can be invoked both via SOAP and a web browser
 (HTTP-Get)
 The web service limits the no. of results to the first 20 results
 received from beagled.

 Attached is a screen-shot of the Firefox browser screen showing
results
 from the web-service for search term 'document'.  A screenshot is
also
 posted at
 http://beaglewiki.org/index.php/BeagleScreenshots?version=26 . Note
 that this 'TestForm' in the browser is more to get a feel for the
 webservice interface - and is not meant to provide browser access to
 beagled per se.

 I will submit the web service protoype code soon. Comments welcome.

 cheers
 Vijay
DANIEL hoggan wrote:
Dashboard will be one of those aplications that will change the way 
people use their desktop.

So obviously intigration into a networked distributed enviroment would 
be an important and necessary development for dashboard, especially for 
office and enterprise enviroments.

In these enviroments dashboard should be the central focal point for all 
and any projects, tasks, events, contacts, etc, especially an 
implementation where it could check callers to an office against a file 
i,e social services, so that any information could be updated there and 
then and any information that the users of dashboard had on the caller 
would be visable.

_
It's fast, it's easy and it's free. Get MSN Messenger today! 
http://www.msn.co.uk/messenger

___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers