Contractor is not integrated in Granite

Bug #826139 reported by Mario Guerriero
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Granite
Fix Released
Undecided
Unassigned

Bug Description

Granite needs a class to manage Contractor in an easy way.

xapantu (xapantu)
Changed in granite:
status: New → Confirmed
xapantu (xapantu)
Changed in granite:
status: Confirmed → In Progress
xapantu (xapantu)
Changed in granite:
status: In Progress → Triaged
summary: - Contractor is not integrated in Granite
+ extended-actions is not integrated in Granite
description: updated
Revision history for this message
Danielle Foré (danrabbit) wrote :

Lucas, at the developer meeting we had decided to stick with Contractor and not switch to Extended Actions.

summary: - extended-actions is not integrated in Granite
+ Contractor is not integrated in Granite
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

...and investigate using a format inside .desktop files, similar to ayatana quicklists

Revision history for this message
xapantu (xapantu) wrote : Re: [Bug 826139] Re: Contractor is not integrated in Granite

Ah, sorry, I thought we wanted to use extended-actions, sorry :)

@Sergey: regarding this, I thought we could have a little script (in
python?) which is run each time we install a new package (there is a
postinstall script in the packaging, right?), and which update a cache. The
cache would be in /var/cache/contractor, and the files there would be some
contracts so we can avoid changing a lot of things in contractor itself.

Opinions?

2011/12/22 Sergey Davidoff <email address hidden>

> ...and investigate using a format inside .desktop files, similar to
> ayatana quicklists
>
> --
> You received this bug notification because you are a member of
> elementary Pantheon team, which is the registrant for Granite.
> https://bugs.launchpad.net/bugs/826139
>
> Title:
> Contractor is not integrated in Granite
>
> Status in Granite Framework:
> Triaged
>
> Bug description:
> Granite needs a class to manage Contractor in an easy way. Or it might
> be better with extended-actions.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/granite/+bug/826139/+subscriptions
>

description: updated
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

Like for desktop file cache? Yeah, makes sense, but I think we should use a database instead of plain text (otherwise it's not cache at all). This way we can split Contractor in two parts: something like update-desktop-database that builds the DB and a client that gets data from the DB.

The DB building part should use XDG_DATA_DIRS and look in a custom directory (e.g. fallback_contracts in the xdg data dir) if there are no contractor entries in the desktop file.

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

And the "little script" will probably be in Vala ;)

xapantu (xapantu)
Changed in granite:
status: Triaged → Fix Committed
Changed in granite:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.