← Back to team overview

elementary-dev-community team mailing list archive

Re: Contractor web services authentication application

 

On Sat, Feb 18, 2012 at 2:17 PM, Daniel Foré <daniel@xxxxxxxxxxxxxxxx> wrote:
> There's no need to have API's for apps to tie directly into. Thats the point of contractor is to not have to do that sort of thing. Once the original app hands off something to a receiving app/service, its work is done. The sending app should never have to know about or care what the receiving app/service is.

That too sounds fine. Right now, I don't have very deep understanding
how apps are going to do it, If the app hands off something to be
shared to twitter and twitter account is not authenticated, then who
should show the "login" window? App or contractor?

> I really feel like we should do our best to have contracts bundled with apps and not as stand-alone packages. Nobody should ever think "Gee i should install the web contracts meta package". Users should simply install Gwibber or Polly for their twitter features, not thinking about the fact that there's a service that ties these apps together.

As per my understanding is, contractor is a separate
application/system which handles sharing and the applications uses it
to sends the data to it so that contractor can share it. If this is
the case then what you talking about bundling in applications is
contractor support. The contracts should be bundled with contractor.
it's like "contractor supports these many contracts".

Yes, contractor, the various contracts and the applications with
contractor integration should all be installed by default. It should
be out of box. The user does not even need to install gwibber and
polly as gwibber's backing library is enough to provide the support
for various contracts. The users should not even care whether gwibber
or polly is providing the sharing service. Basically the sharing
service should work even without gwibber or polly application
installed.

> In other words, users shouldn't know that contractor even exists. It's just an implementation detail.

Yes. Agree


Follow ups

References