[annotator-dev] Annotator on mobile (Riccardo Tasso)
Gong Huaiyu James (NCS)
jamesh at ncs.com.sg
Wed Oct 30 10:25:33 UTC 2013
Hi, Riccardo Tasso:
Please try the following URL on your mobile device, It works on android chrome and iPAD. But if you select the same quoted text, the new add button not working.
http://aron.github.io/annotator.touch.js/index.html?force
For my case, for the PC desktop version, I don't want to use touch.js plugin.
I just do this :
if(/Android|webOS|iPhone|iPad|iPod|BlackBerry|IEMobile|Opera Mini/i.test(navigator.userAgent) ) {
$('#content').annotator().annotator('addPlugin', 'Touch', {
force: true,
useHighlighter: false
});
}
It means only the mobile device to add this mobile plugin.
Thanks
James
-----Original Message-----
From: annotator-dev-bounces at lists.okfn.org [mailto:annotator-dev-bounces at lists.okfn.org] On Behalf Of annotator-dev-request at lists.okfn.org
Sent: Wednesday, 30 October, 2013 6:08 PM
To: annotator-dev at lists.okfn.org
Subject: annotator-dev Digest, Vol 30, Issue 16
Send annotator-dev mailing list submissions to
annotator-dev at lists.okfn.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.okfn.org/mailman/listinfo/annotator-dev
or, via email, send a message with subject or body 'help' to
annotator-dev-request at lists.okfn.org
You can reach the person managing the list at
annotator-dev-owner at lists.okfn.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of annotator-dev digest..."
Today's Topics:
1. Re: Branching v2.0.x (Randall Leeds)
2. Re: Branching v2.0.x (Nick Stenning)
3. Annotator on mobile (Riccardo Tasso)
4. Re: Branching v2.0.x (Robert Casties)
5. Re: Annotator on mobile (Nick Stenning)
6. Re: Annotator on mobile (Riccardo Tasso)
----------------------------------------------------------------------
Message: 1
Date: Tue, 29 Oct 2013 21:16:31 -0700
From: Randall Leeds <tilgovi at hypothes.is>
Subject: Re: [annotator-dev] Branching v2.0.x
To: Ed Summers <ehs at pobox.com>
Cc: "annotator-dev at lists.okfn.org" <annotator-dev at lists.okfn.org>
Message-ID:
<CAFmY2k+m+jG45B985Cuemco-GKc3EhFnkajc704-fq7ra_KDjw at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
First we would need to resolve the remaining differences between the annotator model and the open annotation model.
Then JSON-LD can be added in various places at any time.
As you probably are aware, JSON-LD makes it possible to interpret JSON with a linked data context. Last I checked, the framing abilities of JSON-LD were insufficient to process annotator JSON into open annotation JSON-LD in one step, due to the body and target resources being flattened into the annotation object.
At this point, I'm convinced the model should change. For instance, it disambiguates the meaning of tags on annotations. Right now I feel they're ambiguous, referring either to comment or the target. If the tags were the annotation body, rather than a field on the annotation, they would more clearly apply to the target.
If we get the shape of the model right, contextualizing it with JSON-LD can be done in plugins of various sorts, such as for a storage plugin that interfaces with JSON-LD endpoints.
I think we may as well expose the context. Annotator code would just ignore the context and continue using the friendly names for properties. But I'm not sure it makes sense to add any processing weight to the annotator core for JSON-LD.
What do you think?
On Tue, Oct 29, 2013 at 7:09 PM, Ed Summers <ehs at pobox.com> wrote:
> Is it worthwhile considering JSON-LD and OpenAnnotation for v2.0? I
> know that OpenAnnotation is mentioned quite a bit w/r/t Hypothes.is
> and it seems like JSON-LD would possibly fit in fairly well with the
> annotator.
>
> //Ed
>
> On Tue, Oct 29, 2013 at 6:20 PM, Randall Leeds <tilgovi at hypothes.is>
> wrote:
> > In the interest of moving forward toward Annotator v2 I've just
> > forked
> the
> > current master branch to two branches: v1.2.x and v2.0.x.
> >
> > I would like to propose that maintenance fixes only land on v1.2.x.
> > We should make a release there shortly with anything that's landed
> > since the last tag.
> >
> > We should aim to land Nick's WIP branch on v2.0.x.
> >
> > Kristof Csillag will follow up over the next few weeks with e-mails
> > proposing changes to v2.0.x that integrate work we've done at
> > Hypothes.is which may break backward compatibility.
> >
> > In this way, we can continue to support the existing formats and
> ecosystem
> > and make rapid changes to v2.0.x, stabilizing over time until we
> > feel we
> can
> > tag v2.0.0.
> >
> > I wanted a way to start landing changes upstream without worrying
> > about v1.2.x compatibility. That way we don't have to land the WIP
> > branch with tons of other changes and call it v2.0.0 immediately. We
> > can iterate to
> > v2.0.0 but things can be landed instead of staying on side branches
> > indefinitely.
> >
> > Happy Annotating,
> > R
> >
> > _______________________________________________
> > annotator-dev mailing list
> > annotator-dev at lists.okfn.org
> > http://lists.okfn.org/mailman/listinfo/annotator-dev
> > Unsubscribe: http://lists.okfn.org/mailman/options/annotator-dev
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/annotator-dev/attachments/20131029/753b3e56/attachment-0001.htm>
------------------------------
Message: 2
Date: Wed, 30 Oct 2013 09:22:05 +0100
From: Nick Stenning <nick at whiteink.com>
Subject: Re: [annotator-dev] Branching v2.0.x
To: Randall Leeds <tilgovi at hypothes.is>
Cc: "annotator-dev at lists.okfn.org" <annotator-dev at lists.okfn.org>
Message-ID: <5270C1AD.6020907 at whiteink.com>
Content-Type: text/plain; charset=UTF-8
Randall Leeds wrote:
> In the interest of moving forward toward Annotator v2 I've just forked
> the current master branch to two branches: v1.2.x and v2.0.x.
Hi Randall,
Saw this -- great, and this is absolutely what I intended to do as soon as we pushed out 1.2.8, which I'm happy to do now, but if it's possible to integrate your source map packaging stuff, I'd been keen to do so.
> I would like to propose that maintenance fixes only land on v1.2.x.
> We should make a release there shortly with anything that's landed
> since the last tag.
>
> We should aim to land Nick's WIP branch on v2.0.x.
Agreed, but this now leaves us with three branches -- master, v1.2.x and v2.0.x. I think we only need two at any one time, and my preference would be to fork v1.2.x immediately after releasing 1.2.8, and then merge in the wip branch and have master become the unstable 2.0.x development branch.
Alternatively, if we're worried that people will check out master and be confused by the potentially unstable state of the repo, then we can keep 1.2.x on master until such time as we're willing to promote a 2.0.x branch to master, and only then fork a release branch for support of the 1.2.x series? Meanwhile, formalise the development on the v2 stuff on a 2.0.x branch as you've created.
My strong preference is for the first of these two options, as it puts the v2 work front and center. Opinions
> Kristof Csillag will follow up over the next few weeks with e-mails
> proposing changes to v2.0.x that integrate work we've done at
> Hypothes.is which may break backward compatibility.
Sounds good.
> In this way, we can continue to support the existing formats and
> ecosystem and make rapid changes to v2.0.x, stabilizing over time
> until we feel we can tag v2.0.0.
Agreed.
> I wanted a way to start landing changes upstream without worrying
> about v1.2.x compatibility. That way we don't have to land the WIP
> branch with tons of other changes and call it v2.0.0 immediately. We
> can iterate to v2.0.0 but things can be landed instead of staying on
> side branches indefinitely.
>
> Happy Annotating, R
Thanks for doing this and getting this stuff moving. I spent another few hours last night cleaning up the WIP branch, and the resulting changes in the nature of the tests (both for Annotator core and the Store
plugin) are very encouraging -- it's much more obvious that we're doing real unit testing now, rather than some kind of spaghetti testing that crosses every available unit boundary.
It's probably only another few hours until it's mergeable.
-N
------------------------------
Message: 3
Date: Wed, 30 Oct 2013 09:54:50 +0100
From: Riccardo Tasso <riccardo.tasso at gmail.com>
Subject: [annotator-dev] Annotator on mobile
To: annotator-dev at lists.okfn.org
Message-ID:
<CAEb3+w0uwK5hXxkPna2aGmBToYvr-9_V+AhYZhWa44rweCRL5w at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi, I'm new to annotator and I'm interested in adopting it for my project.
I tried this demo: http://okfnlabs.org/annotator/demo/
And it fits perfectly my needs.
Anyway I tried it with my mobile phone (Android 4.2) and with two different browser (Browser and Chrome) and it seems it's not possible the insertion of new annotations (while the existing ones are correctly visualized).
It is anyhow possible using a mobile device (tablet, phone, ...) to add new annotations with annotator?
Cheers,
Riccardo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/annotator-dev/attachments/20131030/9ba24544/attachment-0001.htm>
------------------------------
Message: 4
Date: Wed, 30 Oct 2013 10:11:23 +0100
From: Robert Casties <casties at mpiwg-berlin.mpg.de>
Subject: Re: [annotator-dev] Branching v2.0.x
To: annotator-dev at lists.okfn.org
Message-ID: <5270CD3B.7060002 at mpiwg-berlin.mpg.de>
Content-Type: text/plain; charset=ISO-8859-1
On 30.10.13 09:22, Nick Stenning wrote:
>> I would like to propose that maintenance fixes only land on v1.2.x.
>> We should make a release there shortly with anything that's landed
>> since the last tag.
>>
>> We should aim to land Nick's WIP branch on v2.0.x.
>
> Agreed, but this now leaves us with three branches -- master, v1.2.x
> and v2.0.x. I think we only need two at any one time, and my
> preference would be to fork v1.2.x immediately after releasing 1.2.8,
> and then merge in the wip branch and have master become the unstable
> 2.0.x development branch.
I would prefer this solution too since its what I would assume from a development project - checkout trunk at your own peril - but maybe I'm just old school ;-)
>> I wanted a way to start landing changes upstream without worrying
>> about v1.2.x compatibility. That way we don't have to land the WIP
>> branch with tons of other changes and call it v2.0.0 immediately. We
>> can iterate to v2.0.0 but things can be landed instead of staying on
>> side branches indefinitely.
Great, keep the new stuff coming.
Cheers
Robert
--
Dr. Robert Casties -- Information Technology Group Max Planck Institute for the History of Science Boltzmannstr. 22, D-14195 Berlin
Tel: +49/30/22667-342 Fax: -299
------------------------------
Message: 5
Date: Wed, 30 Oct 2013 10:33:51 +0100
From: Nick Stenning <nick at whiteink.com>
Subject: Re: [annotator-dev] Annotator on mobile
To: Riccardo Tasso <riccardo.tasso at gmail.com>
Cc: annotator-dev at lists.okfn.org
Message-ID: <5270D27F.7040605 at whiteink.com>
Content-Type: text/plain; charset=UTF-8
Hi Riccardo,
Check out the Annotator Touch plugin:
https://github.com/aron/annotator.touch.js
Best,
Nick
Riccardo Tasso wrote:
> Hi, I'm new to annotator and I'm interested in adopting it for my project.
>
> I tried this demo: http://okfnlabs.org/annotator/demo/
> And it fits perfectly my needs.
>
> Anyway I tried it with my mobile phone (Android 4.2) and with two
> different browser (Browser and Chrome) and it seems it's not possible
> the insertion of new annotations (while the existing ones are correctly
> visualized).
>
> It is anyhow possible using a mobile device (tablet, phone, ...) to add
> new annotations with annotator?
>
> Cheers,
> Riccardo
>
> _______________________________________________
> annotator-dev mailing list
> annotator-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/annotator-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/annotator-dev
------------------------------
Message: 6
Date: Wed, 30 Oct 2013 11:08:00 +0100
From: Riccardo Tasso <riccardo.tasso at gmail.com>
Subject: Re: [annotator-dev] Annotator on mobile
Cc: annotator-dev at lists.okfn.org
Message-ID:
<CAEb3+w0-c=prbQoZph1R8XB36hmnYmAnE8-zr_MH8HqRQdm8Ng at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Thank you Nick,
that seems exactly what I need.
Cheers,
Riccardo
2013/10/30 Nick Stenning <nick at whiteink.com>
> Hi Riccardo,
>
> Check out the Annotator Touch plugin:
>
> https://github.com/aron/annotator.touch.js
>
> Best,
> Nick
>
> Riccardo Tasso wrote:
> > Hi, I'm new to annotator and I'm interested in adopting it for my
> project.
> >
> > I tried this demo: http://okfnlabs.org/annotator/demo/
> > And it fits perfectly my needs.
> >
> > Anyway I tried it with my mobile phone (Android 4.2) and with two
> > different browser (Browser and Chrome) and it seems it's not possible
> > the insertion of new annotations (while the existing ones are correctly
> > visualized).
> >
> > It is anyhow possible using a mobile device (tablet, phone, ...) to add
> > new annotations with annotator?
> >
> > Cheers,
> > Riccardo
> >
> > _______________________________________________
> > annotator-dev mailing list
> > annotator-dev at lists.okfn.org
> > http://lists.okfn.org/mailman/listinfo/annotator-dev
> > Unsubscribe: http://lists.okfn.org/mailman/options/annotator-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/annotator-dev/attachments/20131030/c4b083b4/attachment.htm>
------------------------------
_______________________________________________
annotator-dev mailing list
annotator-dev at lists.okfn.org
http://lists.okfn.org/mailman/listinfo/annotator-dev
Unsubscribe: http://lists.okfn.org/mailman/optionss/annotator-dev
End of annotator-dev Digest, Vol 30, Issue 16
*********************************************
More information about the annotator-dev
mailing list