Giorgio Maone:
On 15/05/2015 18:14, sajolida wrote:
So we could instead embed the minimum version of the extension
required (maybe div id=extension-version1.0/div or something
like this). Then the extension would know if it's outdated, even if
the HTML code of the page didn't change
Giorgio Maone:
On 12/05/2015 18:54, sajolida wrote:
B. It's not the latest version of the extension. This version is
incompatible with the version of the page. We can't go forward or
otherwise stuff won't work:
- How can we detect that? Through a version number in the URL as you
are
On 12/05/2015 18:54, sajolida wrote:
B. It's not the latest version of the extension. This version is
incompatible with the version of the page. We can't go forward or
otherwise stuff won't work:
- How can we detect that? Through a version number in the URL as you
are proposing? Wouldn't
Oops, I didn't meant to answer this in private. Answering back to the
list...
Giorgio Maone:
On 07/05/2015 18:12, sajolida wrote:
Hi Giorgio,
A few days ago we finished a wireframe of the extension that we believe
is a good start for you to work on. It might still change slightly as we
intrigeri:
sajolida wrote (07 May 2015 16:12:52 GMT) :
The v1 part of the URL corresponds to the version of the extension.
I would suggest giving its own versioning to the URL scheme used by
the extension, instead of re-using the extension's versioning.
Otherwise, we'll have to maintain
On 07/05/2015 18:12, sajolida wrote:
Hi Giorgio,
A few days ago we finished a wireframe of the extension that we believe
is a good start for you to work on. It might still change slightly as we
continue discussing small details of it.
See
Hi Giorgio,
Giorgio Maone wrote (08 May 2015 21:29:44 GMT) :
May I just ask, though, why YAML and not, for instance, JSON?
We already have quite some code to generate, update and validate YAML
documents with a very similar purpose and content. Sticking to YAML
would allow us to re-use some of
Hi,
sajolida wrote (07 May 2015 16:12:52 GMT) :
We also updated the blueprint with some more implementation information.
https://tails.boum.org/blueprint/bootstrapping/extension/
Impressive. I took a look and pushed a few nitpicking changes. A few
comments and suggestions follow:
The v1
Hi Giorgio,
A few days ago we finished a wireframe of the extension that we believe
is a good start for you to work on. It might still change slightly as we
continue discussing small details of it.
See
https://labs.riseup.net/code/attachments/download/759/extension-20150430.fodg.
We also
