openannotation/annotator-annotateit
On Apr 22, 2014 8:42 PM, "Kristof Csillag" wrote:
> Hi,
>
> Is there an example project somewhere which showcases how to properly
> package a plugin for Annotator, which lives in an independent
> repository, and is released via npm / browserify independently of
.
On Apr 22, 2014 10:27 PM, "Randall Leeds" wrote:
> openannotation/annotator-annotateit
> On Apr 22, 2014 8:42 PM, "Kristof Csillag" wrote:
>
>> Hi,
>>
>> Is there an example project somewhere which showcases how to properly
>> package a
On Thu, Apr 24, 2014 at 2:25 AM, Paolo Caminiti wrote:
> When calling the annotator on the whole body is there any reason i would
> go trough the wrapper function, which detach all scripts and breaks some
> pages, instead of just returning the element itself?
>
> I switched from:
>
>@wrapper =
Sounds like maybe the default CSS should do some preservation of whitespace
in the viewer, though.
Care to open an issue about it?
On Apr 24, 2014 12:40 AM, "Gong Huaiyu James (NCS)"
wrote:
> Hi, team:
>
> Just replace shift+enter (chr(13) ) into HTML .
>
> It works for me.
On Apr 26, 2014 10:14 AM, "Kristof Csillag" wrote:
>
> A few more questions.
>
> How do I declare dependencies between plugins? "require()" satisfies the
code dependency, but what I need to check is not the exported objects from
the other plugin, but the presence of the plugin, loaded in the curre
On Fri, May 9, 2014 at 10:41 AM, steph wrote:
> Hi,
>
> I've been working on upgrading from Annotator 1.2 to the 2.0 / master
> branch since the I Annotate Conferece. I was able to pull out many of my
> core hacks previously in place, thanks to getting clarification on
> available events from Ran
I few weeks ago a put in a request to gmane.org, a popular mailing list and
newsgroup archive for free and open source software projects and related
topics.
This list is now archived here:
http://dir.gmane.org/gmane.comp.web.annotator
I've also submitted a request to have the archives ingested, b
Welcome, Davide!
On Tue, May 13, 2014 at 8:14 AM, Davide Suraci wrote:
> Hello,
>
> I need to install annotator with authentication process (for me is very
> important that annotations are only from user-authenticated).
>
Yes. Happy to!
>
> Can anyone suggest to me steps for proper installat
I took a stab at part of #379, the "widget unification" issue I created
after the community call.
Issue: https://github.com/openannotation/annotator/issues/379
Proposal: https://github.com/openannotation/annotator/pull/381
It's my belief that we should attempt to make re-usable components, whether
On Tue, May 13, 2014 at 10:14 PM, Anna Gerber wrote:
> During the hack day at I Annotate I quickly sketched an idea for a logo on
> a post-it note and added it to the bottom of this docpad, drawing
> inspiration from the open source hardware and open source initiative logos:
> https://hackpad.com/
Steph, Andrew, thanks for making and merging those commits to get a news
page up!
I'm totally obsessive about not committing source to the gh-pages and not
commit build artifacts to master, though, so I've gone ahead and push a
master branch that features a new rake task.
Here are the differences
On Wed, May 14, 2014 at 7:02 PM, Steph Skardal wrote:
> Ok, I think I am following your updates now after rereading, Randall.
> However, what this means to me is that every time a blog article is added,
> there will be a commit in both the master branch and gh-pages branch that
> would need to b
We should make one now, to generate the news directory.
I would, but I wanted to leave it to someone else so they could try it out
and make sure I was clear.
```
$ cd _news
$ jekyll build
$ rake ghp
$ git push origin gh-pages:gh-pages
```
On Wed, May 14, 2014 at 7:33 PM, Randall Leeds wrote
I made was
> to stop ignoring news/ in .gitignore on the gh-pages branch.
>
> Whoever has permissions can deploy and the news/ pages should be up there
> now.
>
> And then Andrew can follow-up with additional news articles.
>
> Steph
>
>
>
>
>
>
>
http://docs.annotatorjs.org/en/latest/storage.html
You can write any storage plugin you like.
You may also want to look at: https://github.com/aron/annotator.offline.js
On Sat, May 3, 2014 at 11:33 PM, Mohammad parsaee wrote:
> I use annotator on android device but I can't store them on device
Thanks, Andrew! It feels really good to have these notes available outside
Google and public on the website.
And thank you, Steph, for getting together the codes.
\o/
On May 16, 2014 5:10 PM, "Andrew Magliozzi" wrote:
> Hi Annotator Devs,
>
> Thanks to Steph and Randall, there is now a sweet ne
See the example in the documentation for the Store plugin.
Under "Usage" look at the loadFromSearch option.
http://docs.annotatorjs.org/en/latest/plugins/store.html#usage
On May 31, 2014 4:14 AM, "Prateek Narendra" wrote:
> Is therer any way to get Document.URL from user into GET so that i can
+1 to releasing Range as a separate module.
The best thing around besides ours seems to be Rangy and it unfortunately
seems to be acquiring more stuff, such as a highlighter.
A good Range package would be a great thing for the web dev community.
On Jun 11, 2014 8:18 AM, "Kristof Csillag" wrote:
On Wed, Jun 11, 2014 at 11:50 AM, Randall Leeds wrote:
> +1 to releasing Range as a separate module.
>
> The best thing around besides ours seems to be Rangy and it unfortunately
> seems to be acquiring more stuff, such as a highlighter.
>
> A good Range package would be a g
On Mon, Jun 16, 2014 at 6:14 PM, Robert Sanderson
wrote:
>
> They seem like Selectors? Is there a difference?
>
>
Yes. It is a different thing entirely. It is a Range object, specific to
(X)HTML scripting APIs.
Our specs are currently silent on this, but I've often thought we should
have a Range
On Jun 17, 2014 11:28 AM, "Kristof Csillag" wrote:
>
>
>
> On 2014-06-17 19:28, Randall Leeds wrote:
>>
>> The normalization does two things.
>>
>> One is to move the start or end across adjacent tag edges when there is
no text between them. For i
I just dropped Node v0.8 from the Travis CI configuration.
Twice in the last month I've had to go figure out why the build was failing
only to find that some package we depend on for building bumped their
dependencies and decided to use the newer caret syntax for its
dependencies. This syntax isn'
It's a simple setting we can change in the admin interface for the list.
However, the current setup is the recommended default.
Note that "reply all" should respond to the list.
One reason why this setup is potentially better is that it results in the
original sender being in the To: field. That
Anyone opposed?
Might lower the tooling and learning barrier.
I've been a defender of it and invested some time in the tooling but I'd be
okay moving away from it.
No thought of timing here, re 2.0 or anything. Just taking the temperature.
___
annotato
On Jun 17, 2014 7:07 PM, "Kristof Csillag" wrote:
>
> On 2014-06-11 20:50, Randall Leeds wrote:
> > +1 to releasing Range as a separate module.
>
> Here is the first draft:
>
> https://www.npmjs.org/package/xpath-range
Nice. Hurray!
Notes:
- Vendo
On Jun 17, 2014 11:21 PM, "Riccardo Tasso" wrote:
>
> Just a question: why did you choose xpath instead of css selector which
are parsed by jquery?
>
> Is there a javascript library which parses xpath? If I remember well you
implemented an xpath finder in annotator, but probably it would be useful
On Jun 18, 2014 8:32 AM, "Riccardo Tasso" wrote:
>
> Off Topic: how can I use built-in parsers to get the xpath of a given dom
element and vice-versa?
>
https://developer.mozilla.org/en-US/docs/Introduction_to_using_XPath_in_JavaScript
___
annotator-dev
On Jun 18, 2014 12:20 AM, "Kristof Csillag" wrote:
>
> What do you mean by "switching"?
>
> 1. Deciding to accept new incoming JS code, alongside new incoming Coffee
code?
> 2. Deciding that all new incoming code must be JS?
> 3. Removing all the Coffee, and replacing it all with JS? (Either by
au
On Wed, Jun 18, 2014 at 2:40 PM, Robert Sanderson
wrote:
>
> Dear all,
>
> Below is the result of a discussion between Randall and I regarding my
> Open Annotation tickets.
>
> Simple translations:
>
> * "@context" and "@type" are added.
> * "id" becomes "@id", with a value of the base URL of the
On Jun 19, 2014 12:17 PM, "Kristof Csillag" wrote:
>
>
> On 2014-06-19 18:03, steph wrote:
>>
>> Hi,
>>
>> On 06/19/2014 10:17 AM, Andrew - FinalsClub wrote:
>>>
>>>
>>> Would we be better served for the time being by adding a few examples
to the documentation showing both vanilla JS and Coffeescr
nickstenn (afk, I know) & tilgovi : Finally found a decent
package to integrate the existing test runner with Saucelabs, but requires
the use of grunt. Or rewriting the whole package to not use grunt. Is
grunt a dealbreaker for dev?
I'm not a big fan of Grunt. I've played with it a few times a
On Jun 20, 2014 6:08 PM, "Bill Hunt" wrote:
>
> Thanks Randall - I was checking in on IRC to take the temperature before
bringing it to the list for the larger discussion, but let's jump in!
>
> So, the short version is, we started down the rabbit hole of mocha-sauce,
but found that it doesn't act
On Jun 23, 2014 11:29 AM, "Bill Hunt" wrote:
>
> I spent the morning working with BrowserStack, and it doesn't appear to
be quite as mature as SauceLabs.
>
> You can definitely still run tests in a cloud-based browser as all of the
other services offer, but like Browserling, the failures are not l
I glanced through the admin interface and saw nothing like that. :(
On Jun 24, 2014 2:03 AM, "Nick Stenning" wrote:
>
>
> On Mon, Jun 23, 2014, at 17:26, Aron Carroll wrote:
> > Is there a way we can get the permalink (hosted under
> > https://lists.okfn.org/pipermail/annotator-dev/) for each ema
On Tue, Jun 24, 2014 at 9:03 AM, Robert Sanderson
wrote:
>
> Hi Nick, Randall,
>
> On Tue, Jun 24, 2014 at 2:15 AM, Nick Stenning wrote:
>>
>> On Wed, Jun 18, 2014, at 23:40, Robert Sanderson wrote:
>> > "hasBody" : {"@type" : "cnt:ContentAsText", "chars" :
>> "content-here"}
>> Am I right
We'll have to take a look.
Could be that the way the dependencies are specified this worked at the
time but npm is pulling newer versions that have been released since.
We might just need some version pinning.
In any case, you should be able to just download the last release, already
built, from
On Jun 24, 2014 11:33 PM, "Ernesto Torresin (ML)"
wrote:
>
> On 25/06/2014 02:43, Randall Leeds wrote:
> > We'll have to take a look.
> >
> > Could be that the way the dependencies are specified this worked at the
> > time but npm is pulling
It may be that we should have an announce list, though, if people want a
low traffic way to stay informed about releases.
On Jun 25, 2014 1:35 AM, "Randall Leeds" wrote:
> I don't find the traffic to be too heavy on this list but if we find it to
> be so we could do a -dev
I don't find the traffic to be too heavy on this list but if we find it to
be so we could do a -dev -user split, which is common.
On Jun 25, 2014 1:28 AM, "Ernesto Torresin (ML)"
wrote:
> On 25/06/2014 09:12, Randall Leeds wrote:
> [...]
> >> > The master bran
On Wed, Jun 25, 2014 at 3:55 AM, Ernesto Torresin (ML) <
ewk...@connettivo.net> wrote:
> On 24/06/2014 16:01, Ernesto Torresin (ML) wrote:
> > On 24/06/2014 14:38, Ernesto Torresin (ML) wrote:
> >> On 24/06/2014 13:39, Ernesto Torresin (ML) wrote:
> >>> On 24/06/2014 12:18, Ernesto Torresin (ML) w
A.
I think I know what that is. Thanks.
On Jun 26, 2014 1:12 AM, "Ernesto Torresin (ML)"
wrote:
> On 25/06/2014 23:02, Randall Leeds wrote:
> > On Wed, Jun 25, 2014 at 3:55 AM, Ernesto Torresin (ML)
> > mailto:ewk...@connettivo.net>> wrote:
> >
> >
On Wed, Jun 25, 2014 at 1:50 AM, Ernesto Torresin (ML) <
ewk...@connettivo.net> wrote:
> The traffic is low, but very heterogeneous. Furthermore, when the list
> is named -dev and core developers are available, it is easy to feel
> misplaced when asking for help and OT when wishing to help.
>
> Co
On Jun 30, 2014 11:43 PM, "Ernesto Torresin (ML)"
wrote:
>
> On 01/07/2014 03:09, Steph Skardal wrote:
> > On 6/30/2014 6:10 PM, Randall Leeds wrote:
> >>
> >>
> >> But is it easy to get more ML at li...@okfn.org
> >> <mailto:li
service in multiple browsers.
> * Have the failure data automatically reported back in a team-viewable (or
> ideally publicly-viewable) way.
> * Be able to automate this testing via CI of some sort.
> * Use existing tools as much as possible.
>
>
> On Jun 23, 2014, at 2:52 PM, Randall
The data is kept in the internals of Annotator currently.
The easiest way to get it is to use the highlights Annotator creates:
$('.annotator-hl')
Will get all the highlight elements.
Calling .data('annotation') will give you the annotation itself.
That is the most straightforward way on the c
On Jun 17, 2014 9:14 AM, "Ernesto Torresin (ML)"
wrote:
>
> Reading the code, I see that it is full of such deprecation warnings.
> They seem to always come with a proper rewrapping, so I cannot see yet
> what is the "next" plain way to do things. Well, I'll go on see what I
> can understand. Than
On Jul 3, 2014 4:20 AM, "Ernesto Torresin (ML)"
wrote:
>
> I'm taking note of this... but with annotator 1.2.9 I'm getting that if
> in Firebug console I execute
>
> var hls = $('.annotator-hl');
> var hlanns = hls.data('annotation');
> console.log(hls);
> console.l
Yikes.
That's not good. Would people be opposed to doing this in IRC in the future?
I'm also not particularly fond of this Unhangout app thing grabbing access
to my contacts.
On Tue, Jul 15, 2014 at 9:20 AM, Sarah Bird wrote:
> Sorry I wasn't able to join, the google hangout was full. Looking
Ah, yes!
I remember this change. If I recall correctly, we intended to start moving
toward the new jQuery with that release, and the README was updated to say
that you can use jQuery Migrate if you need to keep using the old version
of jQuery.
But at that time we had no docs, just a wiki. The wik
I think the issue is that `setupPlugins`, which comes from the kitchensink
plugin, is setting up a group of default plugins and options. The Store
plugin is already loaded by the time you try to load it explicitly, with
the default settings for annotateit.
These are the defaults:
```
pluginConf
I think whatever you do is a stopgap for now.
If it helps we can push (I think we already have?) a dev tag to npm.
Build a separate repo for the meteor package that depends on annotator and
you should hopefully get the built files if we're doing our part to upload
the build.
On Sep 6, 2014 11:47
npm dependency for the meteor build. Then npm has the built sources. Meteor
package doesn't know or care about browserify.
If any downstream consumer has to care that we use browserify we're doing
it wrong.
The output is JavaScript.
On Sep 6, 2014 8:54 PM, "Mitar" wrote:
> Hi!
>
> > Mitar, I di
On Sep 8, 2014 1:29 PM, "Bill Hunt" wrote:
>
> Hi everyone,
>
> I've been continuing to work on adding support for older browsers,
focusing on IE back to 8 at the moment. Right now I've got *most* of the
test suite running successfully - using a handful of shims - but I've had
to circle back to w
s.
>
> Ari
>
> On Tue, Sep 9, 2014 at 1:24 PM, Ari Entlich wrote:
>
>> On Sat, Sep 6, 2014 at 9:58 PM, Randall Leeds
>> wrote:
>>
>>> I think whatever you do is a stopgap for now.
>>>
>>> If it helps we can push (I think we already have?) a dev
you
point me to a test and a browser version and ask again?
On Sep 9, 2014 12:56 PM, "Bill Hunt" wrote:
>
> Bill Hunt
> krues8dr.com
> Ph: 20-BILL-HUNT
>202 455 4868
>
> On Sep 8, 2014, at 4:46 PM, Randall Leeds wrote:
>
> On Sep 8, 2014 1:29 PM, "
We already build as a UMD in the output. One step ahead of you all :-D.
I'm not sure what the problem is in this thread anymore.
Is it that xpath-range isn't exported? We used to have Annotator.Range I
think, before we split it out into a separate package. We can definitely
assign it as a propert
s doesn't give you a complete result because XPath gives you the
relative order of siblings having the same tag, but not absolute ordering
of each child in its sibling set.
Also, if you are concerned about screen position, CSS can totally change
that in ways that don't match the structure.
not absolute ordering
of each child in its sibling set.
Also, if you are concerned about screen position, CSS can totally change
that in ways that don't match the structure.
But it should be good enough for some uses.
On Thu, Sep 11, 2014 at 1:57 PM, Randall Leeds wrote:
> I just checked
he other option is simply to expose xpath range as noted in a few ways to
> compare relative positions of annotations outside the context of a rendered
> page.
> On Sep 11, 2014 1:10 PM, "Randall Leeds" wrote:
>
>> We already build as a UMD in the output. One step ahead of
What version of annotator?
On Sep 15, 2014 5:22 PM, "Andre Z." wrote:
> Hi,
> I recently noticed that the viewer is not updated when I hover from one
> annotation to another without hovering over plain text. Does this is proper
> behaviour?
>
> kind regards
>
> ___
On Sep 21, 2014 2:54 PM, "leinfelder" wrote:
>
> Certainly, feature requests need to be triaged to be useful to anyone -
especially the core team. It seems like having those potential items in a
forum like this is a good way to organize and evaluate them through
discussion and informal voting just
I've removed the GitHub rely links from the CC, because apparently those
are pegged to the person who got the notification and every reply looks
like it comes from me.
On Mon, Sep 22, 2014 at 11:36 AM, Ben Leinfelder
wrote:
> Email is fantastic as an alert mechanism.* As an archive, it only work
On Tue, Sep 23, 2014 at 9:33 AM, Willy Bruns wrote:
> Nice,
> Thanks for the link!
>
> Love that Jamie's is configured for easy Heroku deployment.
>
> I'll play with that this evening.
>
> A couple of differences that will be fun to discuss are his use of MongoDB
> instead of Elasticsearch (I won
On Thu, Sep 25, 2014 at 12:09 PM, Sarah Bird wrote:
> Hi Ben,
>
> Just a guess that the . is causing you trouble.
>
> If I do http://annotateit.org/api/search?pid=jscientist
>
> I see your results I think.
>
> This may be related to my old issue (don't have the number off the top of
> my head)
>
On Wed, Sep 24, 2014 at 1:07 PM, Marc-Antoine Lemieux <
m...@marcantoinelemieux.com> wrote:
> Hi guys,
>
> we are currently using Annotator for one of our features at Radialpoint.
> We are currently using code in the master branch (I know I know we are
> crazy...) and we are currently on a UI/UX p
On Thu, Sep 25, 2014 at 1:14 PM, Marc-Antoine Lemieux <
m...@marcantoinelemieux.com> wrote:
> Here's the behavior I am talking about for the overlapping bubbles (
> https://dl.dropboxusercontent.com/u/11784435/Selection_021.png). To be
> clear, there's always only one Editor bubble shown. It's the
On Thu, Sep 25, 2014 at 12:57 PM, Ben Leinfelder
wrote:
> Just a follow-up to say that running the latest annotator-store locally
> did allow me to add and query annotations with the following fields/values
> as expected:
>
> /search?pid=test.2014090915254865302.1
> /search?text=中文 (encoded as %E
On Thu, Sep 25, 2014 at 2:09 PM, Marc-Antoine Lemieux <
m...@marcantoinelemieux.com> wrote:
> I'm still wondering if using master was the right choice at the beginning,
> but since I knew we would mosty certainly want to customize the behavior
> (which we did), the new version seemed to be better
On Oct 10, 2014 9:12 AM, "Robert Sanderson" wrote:
>
>
> This: http://enable-cors.org/
>
> Or, TL;DR ... add a header to the response: Access-Control-Allow-Origin: *
>
If you're using the auth plugin you need to do more than this.
You just also allow credentialed requests and allow the
X-Annota
tl;dr if you don't have user accounts everything should just work. If
you're trying to have user accounts and use the Auth plugin, you will need
to create a token endpoint and it needs to be CORS enabled with credentials.
On Oct 10, 2014 9:57 AM, "Randall Leeds" wrote:
>
On Oct 10, 2014 11:17 AM, "Robert Sanderson" wrote:
>
>
> Proposals:
>
> 1. Tags are about the target(s) of the Annotation, and are thus Bodies
of the annotation.
>
+1
This is not likely to be terribly wrong for most use, I think. It also
means we don't need to migrate existing annotations, ext
On Oct 10, 2014 12:37 PM, "Robert Sanderson" wrote:
>
>
> Okay so we should defer that until there's at least some mapping for
auth, that's both easier and consistent :)
>
Why does it have to be consistent? Shouldn't I, as a developer working with
annotator, be able to choose a representation app
On Fri, Oct 10, 2014 at 2:08 PM, Benjamin Young
wrote:
>
>
> On Fri, Oct 10, 2014 at 2:53 PM, Randall Leeds
> wrote:
>
>> On Oct 10, 2014 11:17 AM, "Robert Sanderson" wrote:
>> >
>> >
>> > Proposals:
>> >
>> > 1. T
On Fri, Oct 10, 2014 at 2:15 PM, Robert Sanderson
wrote:
>
> Hi Ben, Randall,
>
> On Fri, Oct 10, 2014 at 2:08 PM, Benjamin Young
> wrote:
>
>> > 2. User holds the user name of the account, and thus the appropriate
>>> mapping is foaf:nick
>>> >For our use at Hypothesis, the user field is a UR
Another potentially useful direction to go would be to separate the steps
of identifying and highlighting the anchors. It should be possible to use
the selector implementation to get the image element and bounding box
information. With OS integration that'd probably be adjusted for zoom and
pan.
T
On Sun, Oct 12, 2014 at 2:15 PM, Kristof Csillag
wrote:
> On 2014-10-12 18:22, Randall Leeds wrote:
>
> Another potentially useful direction to go would be to separate the steps
> of identifying and highlighting the anchors.
>
>
> In fact that's exactly what we have be
On Sun, Oct 12, 2014 at 2:23 PM, Kristof Csillag
wrote:
> On 2014-10-12 19:50, Nick Stenning wrote:
> > On Sun, Oct 12, 2014, at 18:22, Randall Leeds wrote:
> >> Another potentially useful direction to go would be to separate the
> steps
> >> of identifying an
On Mon, Oct 13, 2014 at 10:34 PM, Tim Casling wrote:
> I have upgraded my annotator JS from 1.2.7->1.2.9.
>
> On #2, edit and delete icons are visible on the annotation. Not sure how
> I missed them!
>
> Any input on #1 and #3 appreciated.
>
For #1, the question of whether you must use search,
In reviewing the current master branch today I came upon two simple
refinements I will try to make this week, but feel free to jump in and do
so yourselves. I hope by laying out the motivation and the philosophy here
it helps us see more places for improvement.
I hacked up an open annotation stora
On Tue, Oct 14, 2014 at 1:09 PM, Tim Casling wrote:
> I think #3 might be an issue with the HTML on my side. It comes from an
> DITA XML->HTML transform and there is some strange ordering of elements. I
> will investigate more, but it appears to be the first heading in the
> document whose stor
On Tue, Oct 14, 2014 at 1:49 PM, Tim Casling wrote:
> So if i understand this correctly: at the moment it retrieves all
> annotations without filtering on url and if it finds a range within the
> document that corresponds to the annotation range, it adds the annotation.
>
> I'm just trying to get
On Fri, Oct 17, 2014 at 10:27 AM, Tim Casling wrote:
> If I wanted to access the store, to generate reports, for example, how
> would I find it and what is the database (sqlite?). Which component is
> doing the storage - is it delegating to elasticsearch?
>
Elasticsearch.
_
On Nov 26, 2014 7:47 PM, "Rick" wrote:
>
> Thanks for the help Bird, your suggestion works great. I see that I
didn't understand the documentation.
>
> I do have another question if you don't mind.
>
> For the PUT and DELETE endpoints, the annotator does not use the
/api/annotator/:id pattern but
On Nov 26, 2014 7:59 PM, "Chris Reeve"
wrote:
>
> Hi, I am about to enter a coding academy (either Hack Reactor or General
Assembly), and have some super-newb questions to ask about the technology
stack. I am very interested in doing an annotations-based project. I went
to the last iAnnotate con
On Nov 26, 2014 11:48 PM, "Rick" wrote:
>
> Does the annotation require and 'id' field?
>
Yes.
___
annotator-dev mailing list
annotator-dev@lists.okfn.org
https://lists.okfn.org/mailman/listinfo/annotator-dev
Unsubscribe: https://lists.okfn.org/mailman/
As far as I know that should work as you expect. Does it not?
On Nov 28, 2014 2:38 PM, "Alexander Wülfing"
wrote:
>
>
> Hi,
>
> my question:
>
> the text inside a div can be annotated. But what if I have certain divs
> and want to specify which content can be annotated (not all divs)? How can
> I
On Jan 30, 2015 1:49 PM, "Robert Casties"
wrote:
>
> Hi Banjamin,
>
> I was having the same problem as Andrew so your information helped me a
lot.
>
> On 26.01.15 15:32, Benjamin Young wrote:
> > I'm guessing your wanting to use the HTTP Storage implementation (since
you
> > mention endpoint confi
On Tue, Jan 27, 2015 at 2:08 AM, Gianpaolo Trotta <
gianpaolo.tro...@gmail.com> wrote:
> Hi.
>
Hello, Gianpaolo.
> I use readiumJS to read ebook.
> I would annotate this ebook but ebook viewer is in an iFrame.
> I add js and css annotator's files in head of iFrame but annotator doesn't
> work m
Annotator does nothing special with double clicks. Do you find that you're
unable to capture them when you have annotator enabled?
On Tue, Feb 17, 2015 at 6:11 PM, Mike Potter wrote:
> Hi all:
> First of all, thanks for such a great project. A friend and I are working
> on a website editor / re
tator was capturing them - are you saying they should be passed through?
>
> Mike
>
> On Feb 17, 2015, at 9:12 PM, Randall Leeds wrote:
>
> Annotator does nothing special with double clicks. Do you find that you're
> unable to capture them when you have annotator enabled?
>
&
I was capturing before
> are no longer being passed to my code, from what I can tell. I assumed that
> Annotator was capturing them - are you saying they should be passed through?
>
> Mike
>
> On Feb 17, 2015, at 9:12 PM, Randall Leeds wrote:
>
> Annotator does nothing s
+1 unless there's some step that requires user intervention for producing
the Jekyll build.
On Feb 23, 2015 12:15 PM, "Benjamin Young" wrote:
> Hi all.
>
> Part FYI and part question below. :)
>
> I've sent in a couple Plugin related PRs lately (which Nick graciously
> merged...thanks Nick!):
> h
Hi, Shauna!
Responses inline:
On Wed, Feb 25, 2015 at 2:15 PM, Shauna Gordon-McKeon
wrote:
> Hi all,
>
> I've been working with the Annotator for the last few days and have
> successfully got it working with my app (using Django & Django Rest
> Framework api). I'd like to be able to link users
Quick response.
I think you understood everything perfectly. As much as we'd like to have
people testing out what will become Annotator 2.0, it's a bit different and
not well documented yet, so I'm hesitant to suggest you move to that.
On the other hand, the 1.2.x branch had a change (almost a ye
On Wed, Feb 25, 2015 at 3:27 PM, Shauna Gordon-McKeon
wrote:
> Sounds great. I'll hold off on messing with the annotator internals,
> then. :)
>
> Do you have any kind of eta on when you'll have 1.2.10 published? I'm not
> in a rush, but it would be good to have an estimate for planning purpos
Dear all,
We've just released Annotator v1.2.10, a maintenance release which is
intended to be the one of the last in the v1.2.x series. It is also the
first release since moving to the Open Annotation organization on GitHub,
an expression of our commitment to support the evolving Web Annotation
s
On Wed, Feb 25, 2015 at 4:15 PM, Shauna Gordon-McKeon
wrote:
> Randall: Sweet! Thanks for being so responsive.
>
You're welcome!
That's done. I sent out the announcement e-mail. Let's hope I got
everything right :).
___
annotator-dev mailing list
anno
+1 Shauna!
On Mar 9, 2015 9:47 AM, "Shauna Gordon-McKeon" wrote:
> We're confirmed. I believe beer and snacks are fine. Are these for all
> attendees? If so, let's provide non-alcoholic drink options as well, so as
> not to be exclusionary towards non-drinkers.
>
> - Shauna
>
> On Mon, Mar 9,
Looking good. Annotator Store expects the id key to be named "id". You may
need to rewrite that key in your API routes.
On Mar 9, 2015 3:13 PM, "Gareth Highnam" wrote:
> This time it gave 200 and gave me some JSON about my existing entries,
> which are a bunch data like so:
>
> {"_id":"54fdf51f18
pying _id from ranges and not the main one, which may be
>> an issue. I'll see what happens if I fix that.
>>
>> As for the URI, it actually does match, but I changed it by hand in the
>> email (because my friend is paranoid). Sorry for the confusion there, good
>>
1 - 100 of 193 matches
Mail list logo
