[Slogger] Slogger & Google Desktop

[Joe Walp]

--- Tim Bishop <geodog at cyberdude.com> wrote:
> Welcome back, Joe. Hope the new job is going well.

Thanks.  :-)

That's not the only thing that's kept me away.  I'm still searching
for a new (to me) car.  (My previous one was recently totaled due to
an accident.)
 
> I hope that you are not planning on eliminating the current Google
> Desktop 
> HTML profile -- I have close to a gig of stuff stored in that
> format.

Well, the Google Desktop HTML profile doesn't exist in the official
release.  It only exists in the betas.  As of now, I'm planning for
the next official release not to include the Google Desktop HTML
profile, but the upgrade won't remove or alter your existing
profiles.

Regardless whether I include the Google Desktop HTML profile in an
official release, I'd be happy to send you info required to create
the profile via the UI.

Incidentally, I've been considering creating a file format for saving
profiles so that users and myself can release them separately from
the extension.  That could solve some upgrade headaches.  But coding
validation for everything is a pretty big undertaking.  I want to get
logging-to-bookmark working first.

The development version contains new versions of the "HTML -
Personal" and "HTML - Business" profiles that include optional fields
like $clip and $desc.  They feature some cross-browser client-side
scripts that show the relevant HTML elements only when data exists
and that allow you to toggle visibility of those fields.  It also has
a new version of the "XML Complete" XSL file that features a script
for similarly toggling visibility.

> 
> I'm also really hoping that separate confirm options per profile is
> still 
> on your todo list -- that is the single most frustrating thing
> about the 
> otherwise wonderful slogger extension.

Yes, this has been implemented in my development environment.  It's
actually per-button.  (The Confirm toggling option on the drop-down
menu controls the Main button behavior, and the Confirm behavior for
other buttons is configurable only via the Options dialog.)

I'll release the next snapshot as soon as I've resolved the following
issues:
o Implement a duplicate filter based on the browser history.
o Resolve the issue where pages opened in the background (without
Tabbrowser Extensions) aren't logged.
o Implement a configuration option that allows logging pop-ups but
still excludes frames.  (This could be tricky.)
o Implement a migration routine.