[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #29 from ganeshadit...@gmail.com --- going a little off topic here, I think internet explorer cannot be supported in any efficient way, cause of the way text ranges are implemented in it. Both ofkn and pundit are not supported in IE. I ve been going through the code of OFKN for a while now and this dawned upon me just now. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #30 from James Forrester --- (In reply to comment #29) > going a little off topic here, I think internet explorer cannot be supported > in any efficient way, cause of the way text ranges are implemented in it. > > Both ofkn and pundit are not supported in IE. I ve been going through the > code of OFKN for a while now and this dawned upon me just now. In the VisualEditor project we have similar needs for cross-browser range selection and manipulation, and we have used the Rangy library - https://code.google.com/p/rangy/ - which has worked out well for us. Not sure if this is helpful for you? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #31 from ganeshadit...@gmail.com --- (In reply to comment #30) going by the description, it perfectly fits the bill! I mean it has all the methods of firefox available in IE. But the documentation is really very poor man. Its going to take me a while to make heads and tails of this :( -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #32 from Matthew Flaschen --- Richa Jain has been accepted for Google Summer of Code for this project. She is currently investigating OKFN and the store plugin. The below are some thoughts as a starting point: OKFN provides documentation on writing a plugin for storing annotations (https://github.com/okfn/annotator/wiki/Store-Plugin)? The most straightforward approach seems to be implementing that as a MW extension. https://github.com/okfn/annotator-store is an example of how one store works, though of course the MW extension example will be different. One issue is that the API is RESTful. It lets you set a custom prefix, but the syntax is a little different than MW normally uses. One way to do this is to make a normal MW-style API subclass (like https://www.mediawiki.org/wiki/API:Extensions#Creating_API_modules_in_extensions), then hook into the URL routing code to translate the OKFN-style RESTful URLs to calls to the API. Someone may have made a RESTful wrapper of a MW API, or have advice on doing so. It's probably also worth looking at the hooks (https://www.mediawiki.org/wiki/Manual:Hooks) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Tyler Romeo changed: What|Removed |Added CC||tylerro...@gmail.com --- Comment #33 from Tyler Romeo --- (In reply to comment #32) > Someone may have made a RESTful wrapper of a MW API, or have advice on doing > so. I sure hope this exists. The API interface is terrible right now. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #34 from Tyler Romeo --- From Matt's email: > The high-level concept of RevisionDelete applies, but I don't think > directly using it is a good fit. What happens if one comment on a page > is a violation, but the next consecutive 999 are fine? With RevDel, I > think you'd have to remove the bad one, then suppress all 1000 (correct > me if I'm wrong) containing the bad one, leaving no history of how the > good 999 developed. I was thinking one page per comment. > True, but there's existing code (the main one I'm thinking of is AFTv5) > to learn from. Another reason not to use a page is that it constrains > changes. Once we publish the JSON page, there could be bots that rely > on it, rather than the API. If we just use JSON internally, that gives > us flexibility. If we use pages, we could still use JSON only internally. We'd implement a new Content type for annotations and still provide an API module for accessing comments. All that said, I understand the concern with using articles as a storage medium, so I would be fine with either way. I just wanted to make sure we weren't ditching the idea without due consideration. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #35 from Matthew Flaschen --- (In reply to comment #33) > (In reply to comment #32) > > Someone may have made a RESTful wrapper of a MW API, or have advice on doing > > so. > > I sure hope this exists. The API interface is terrible right now. I saw they allow overriding the URL syntax (https://github.com/okfn/annotator/wiki/Store-Plugin#urls), so the main concern is probably less used methods like PUT and DELETE, which needs investigation on both sides (OKFN and MW). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #36 from Tyler Romeo --- (In reply to comment #35) > I saw they allow overriding the URL syntax > (https://github.com/okfn/annotator/wiki/Store-Plugin#urls), so the main > concern > is probably less used methods like PUT and DELETE, which needs investigation > on > both sides (OKFN and MW). AFAIK, if you submit a PUT/DELETE request to the API, it will probably just treat it as a GET request, although I could be wrong and have not tested this. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Randall Leeds changed: What|Removed |Added CC||tilg...@hypothes.is --- Comment #37 from Randall Leeds --- Just popping in to subscribe to CC on this. I'm actively maintaining and improving Annotator for Hypothes.is and am happy to answer any questions or work with you all to close any gaps we need to in order to store annotations in mediawiki. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #38 from richa jain --- Just a note that i have made a repo on github https://github.com/richajain/Prototyping-inline-comments and have done some initial commits. I will be updating this with the progress done at regular time. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 James Forrester changed: What|Removed |Added See Also||https://bugzilla.wikimedia. ||org/show_bug.cgi?id=49603 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #39 from richa jain --- Gerrit is ready and all my github changes are imported. https://git.wikimedia.org/log/mediawiki%2Fextensions%2FAnnotator.git The basic skeleton of where to call the annotations is ready. Now i am starting with the storage of comments. Here are some of my points: 1. Going through the idea of custom table implementation and storing comments in a separate table which takes account of the revision id, user and the range. 2. Creating classes 'create', 'update', 'read', 'delete' for annotations. https://github.com/okfn/annotator/wiki/store-plugin#urls 3. Modify the above urls of OKFN as: prefix: 'api.php' create: '?action=create', etc. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Rob Sanderson changed: What|Removed |Added CC||azarot...@gmail.com --- Comment #40 from Rob Sanderson --- Just to recommend the hypothes.is version of annotator, and to point to the Open Annotation specification for the implementation: http://www.openannotation.org/spec/core/ and http://www.w3.org/community/openannotation/ Hope that helps, and looking forwards to seeing the outcomes. Happy to answer any Open Annotation questions that may come up! -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #41 from Randall Leeds --- We're right here watching, Rob :) I would recommend just focusing on upstream okfn/annotator. We're cranking hard to get everything relevant pushed upstream. Richa, don't hesitate to reach out if you want help testing or have any questions about the annotator code. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #42 from Helder --- See also: * [[Wikipedia:Village_pump_(idea_lab)/Archive_3#Sticky_Notes_for_Easier_Editing]] * [[Wikipedia:Sticky notes]] -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Matthew Flaschen changed: What|Removed |Added Summary|stet-like tool for inline |co-ment-like tool for |comments|inline comments -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #8 from Isarra --- Such articles tend to be protected on some level, though, and the same reasons would probably have to apply to this as well. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Andre Klapper changed: What|Removed |Added Priority|Unprioritized |Low -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Ryan Kaldari changed: What|Removed |Added CC||rkald...@wikimedia.org --- Comment #9 from Ryan Kaldari --- This sounds much more like a separate extension than an enhancement to ArticleFeedback. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #10 from Quim Gil --- This feature request is being considered for https://www.mediawiki.org/wiki/Summer_of_Code_2013#Project_ideas Question: is there a potential mentor willing to help potential students interested in this project? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 shondhi...@rocketmail.com changed: What|Removed |Added CC||shondhi...@rocketmail.com -- You are receiving this mail because: You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #11 from Quim Gil --- A bit of context and braindumping: http://openannotation.org/ http://www.openannotation.org/wiki/index.php/Web_Page_Clients_List Maybe "annotations" is the label we are looking for? Wikipedia articles are not scholarship texts, and inline comments won't be scholrship annotations. Then again... aren't they structurally the same? Point to a specific portion of text and connect a comment, a signature, a timestamp, maybe a link. Another aspect is My Annotations, as part of My Contributions. I guess annotations will need a unique deeplink? And do we get those annotations by default, or should users activate an "Annotated view"? Maybe the latter, it looks like too much extra bytes and clutter for the majority of people interested in the first paragraph and some factoids. Bonus: Are all annotations willing the be seen publicly by default? We won't go for private annotations, but maybe people want to have notes-to-self? Like ToDo post-its for editors, or notes for students preparing their school work. Those would be as public as our User pages: public for those knowing where to look but out of default searches / views. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #12 from Matthew Flaschen --- To follow up, I have decided to act as mentor should the project be selected. I think annotation is a valid term, although comment is also commonly used (e.g. LibreOffice, Google Docs). co-ment seems to use both terms. There should probably be some kind of permalink that shows the comment, but initially that might just be a link to the revision (especially if comments aren't preserved on edit in the first implementation). I don't think they should be shown to readers by default. It would have to be a toggle of some kind. It would be nice to make this available in VisualEditor mode (either just that, or both). The notes to self idea needs further thought. I see the primary use of the extension as collaborative work, but then again people do use userpage for drafts too. If this project moves forward, we may want to continue speccing it out on mediawiki.org. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Matthew Flaschen changed: What|Removed |Added CC||jforres...@wikimedia.org -- You are receiving this mail because: You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #13 from Matthew Flaschen --- James Forrester has indicated that this may be within the scope of VisualEditor, and that he would be receptive to the feature being implemented as part of GSOC. I've CCed him. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Quim Gil changed: What|Removed |Added CC||mas...@wikimedia.org --- Comment #14 from Quim Gil --- More context: Commons has annotations in images: http://commons.wikimedia.org/wiki/Commons:Image_annotations Munaf mentioned annotations at http://www.mediawiki.org/wiki/Micro_Design_Improvements#Annotations -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Nemo changed: What|Removed |Added CC||federicol...@tiscali.it --- Comment #15 from Nemo --- I've linked this bug from https://www.mediawiki.org/w/index.php?title=Feature_map&diff=663816&oldid=566850 where the FSF feature was reported. (In reply to comment #11) > Are all annotations willing the be seen publicly by default? We won't go for > private annotations, but maybe people want to have notes-to-self? Like ToDo > post-its for editors, or notes for students preparing their school work. Looks outside the scope of the request. It's indeed the sort of thing the word "annotation" is usually used for, so let's not call this proposal "annotations" maybe? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #16 from James Forrester --- So, to my mind there are two options here, and I can't quite understand which is being discussed (it appears both): * Is this about surfacing to the editors in some nice way post-VisualEditor roll-out the existing comments for editors - I.e. "" at the top of the Barack Obama article on enwiki? If so, great, and this should probably be moved to the VisualEditor product space. This is definitely needed for VE, but I worry that the scope for functionality is not huge, and it might be limiting. * Is this about building an additional persistent/semi-persistent un-threaded/semi-threaded discussion space on top of pages/revisions(?) like Co-ment and Google Docs? If so, that sounds fun, and something that we're also looking at building for VisualEditor (as part of the real-time collaboration system, potentially), but I wouldn't want us to get in the way of someone building a first pass for GSoC. Doing this for both VE and wikitext at the same would be a really hard UI challenge (they're very different interface concepts), so perhaps limiting it to just one of them for now? Also, there needs to be a really serious discussion about how this would work from a product perspective (threading? how much? how signed? using LQT? why not? where stored? attached to revisions? To pages? to sections of said revision/page? how? etc.) lest it become mammoth. OTOH, this would be very cool as well. Apologies for the confusion on my part. :-) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440
--- Comment #17 from Matthew Flaschen ---
From where I'm coming from, it has nothing to do with the first option (HTML
comments/warnings to editors).
It is meant as a collaboration tool, essentially your second option. I don't
see it as a replacement for long free-form discussion ("this article needs more
reliable sources..."/"it has an undue weight is the following areas"...), but a
targeted form of collaboration around small areas of the article, like co-ment.
I agree a first pass (on MediaWiki.org, etc.) would be useful regardless, even
if not all the code could necessarily be integrated into the permanent
solution. It would allow trying out implementations and UI ideas.
I agree it would probably have to be one interface at first (and maybe ever),
and VisualEditor/Parsoid probably makes more sense.
There would probably have to be limited threading, but flat (these people
commented on this excerpt in this chronological order) would probably be
sufficient. If it gets too elaborate, talk it to the talk page/Flow.
To keep it concise, I would suggest just the username and date (perhaps
auto-formatted to e.g. "3 hours ago" for recent comments), rather than a
signature. I suggest it should show IPs for anons.
I'm not envisioning using LQT, since it seems like if we want to integrate at
some point, Flow would be a better candidate.
It would be most useful attached to pages, automatically invalidating a comment
when an excerpt is altered. But "attached to revision" is probably more
realistic for the first implementation.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #18 from Quim Gil --- This is the end result we are after: Wikipages optionally looking like this (famous examples picked for reference only): http://gplv3.fsf.org/comments/lgpl-draft-1.html (few comments) http://gplv3.fsf.org/comments/gplv3-draft-2.html (really busy) That view would include the possibility to add comments. There is a sandbox to play without registration at http://www.co-ment.com/see/ And a lite version at https://lite.co-ment.com/ PS: group permissions to be taken into account? Maybe not in a prototype for a GSOC student but I can imagine that the same levels of protection (open, registered users, autoconfirmed...) would be desired. For Wikimedia wikis I would require login, a nice reason to register. But this is going too far... :) Also, spam check? Posting external URLs possible or not? Well, this can be endless and again we should define the scope for a GSOC prototype. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Saumya Dwivedi changed: What|Removed |Added CC||saumya.z...@gmail.com -- You are receiving this mail because: You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Tpt changed: What|Removed |Added CC||thoma...@hotmail.fr --- Comment #19 from Tpt --- http://okfnlabs.org/annotator/ is maybe (with some adaptations) a relevant option. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Waldir changed: What|Removed |Added CC||wal...@email.com --- Comment #20 from Waldir --- (In reply to comment #19) > http://okfnlabs.org/annotator/ is maybe (with some adaptations) a relevant > option. Also http://hypothes.is (they seem to build on top of okf's annotator: https://github.com/hypothesis/h#development) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #21 from Quim Gil --- Slightly related: http://homes.cs.washington.edu/~travis/reflect/ With old MediaWiki extension code available: http://www.mediawiki.org/wiki/Extension:Reflect Depends on LiquidThreads, so I don't expect many possibilities of reuse as-is but perhaps you want to have a look. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 Quim Gil changed: What|Removed |Added CC||richa.jain1...@gmail.com --- Comment #22 from Quim Gil --- Just a note to say that Richa Jain has submitted a GSoC / OPW proposal related to this report: https://www.mediawiki.org/wiki/User:Rjain/Proposal-Prototyping-inline-comments There is another student that has submitted a proposal. I will announce it here as soon as there is a public URL. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 ganeshadit...@gmail.com changed: What|Removed |Added CC||ganeshadit...@gmail.com --- Comment #23 from ganeshadit...@gmail.com --- Hey, My name is Aditya and am interested in pursuing this as my GSOC project. After going through the requirements, leaving apart any additional features required. I have outlined two major aspects of this project. 1) Designing the UI. 2) Designing the database. I just want to present my perspective on these two things before I start drafting my proposal. I want to hear your opinion on this. 1)UI When it comes to designing the UI. I think it will be better if we go with a custom build rather than using a ready-made component, cause MediaWiki uses themes and each component should match the theme and a ready made component leaves very little margin for customization ( in-case its a opensource component, then it might as well be modified, but the person designing the theme need to be not only versed with the code of the MediaWiki but as well as the source code of the component, hence I believe a ready made component would constrain the customizability of MediaWiki. http://adityasastry.in.cp-2.webhostbox.net/index.php?title=Special:BlankPage This is a UI mockup I came up with. Its a prototype for a prototype :P I have made an implementation of this for VECTOR theme, but I have placed the CSS and JS for this in the common skins shared.css and the JS in vector.js as of for now. Implementing this for some other theme is very easy. We just need to add a DIV in the theme's php file. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #24 from ganeshadit...@gmail.com --- 2)Databases Allow me to make a very bold statement here that json/xml are ill suited for a project of this nature. Justification: 1) There are many helper classes already written for MediaWiki like sanitizer class(which depends on the databases) load balancer class(Incase one wants to distribute the comments data) and few other classes which implement functionality which is critically needed. Incase one wants to go the XML/JSON way one needs to implement them as well. 2) Maintenance will become an issue. 3)When migrating between hosts one needs to manually select the xml/json files and move them around. MYSQL supports one click export and import functionality for all the tables. I will be making a prototype for databases as well in a couple of days. And here's my idea. Each article is stored as a WikiText string, so as illustrated by my UI the selected text's starting and ending indexes are caught and the article page name is also caught. These three attributes will be used as indexes into a table "Comments" When parsing this wikitext, based on the starting and ending indexes the text will be marked and a link will be provided next to it to access the comments as I have shown. I will be implementing this functionality by tuesday. But for the sake of proposal I will be not using any of the MediaWiki classes for now so you people could test drive it once and based on your feedback I will be making ammendments to my proposal, so please review my work so far :) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #25 from Matthew Flaschen --- (In reply to comment #23) > Hey, > My name is Aditya and am interested in pursuing this as my GSOC project. Thank you for your interest. > Implementing this for some other theme is very easy. We just need to add a > DIV in the theme's php file. Note that this is being proposed as an extension. Thus, you should not need to modify the core skin definition. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #26 from ganeshadit...@gmail.com --- I seem to have butt into the conversation .. I didn't read the comments yet. Apologizes .. Anyways keeping with the conversation, since you guys are discussing interfaces, please checkout my prototype http://adityasastry.in.cp-2.webhostbox.net/index.php?title=Special:BlankPage Instead of the in-page along with article display, I would propose a movable popout as the readability might suffer when you try to squeeze in the comments interface into the article. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #27 from Quim Gil --- Just a note to say that Anthony Chen has submitted a GSoC proposal related to this project: https://www.mediawiki.org/wiki/User:N3c/GSoC_Proposal -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46440] co-ment-like tool for inline comments
https://bugzilla.wikimedia.org/show_bug.cgi?id=46440 --- Comment #28 from Quim Gil --- Another tool for inspiration? http://www.thepund.it/ Java backend but "The Pundit client is a Javascript application based on the Dojo Toolkit http://dojotoolkit.org/ . It works closely with the Pundit server API, allowing the end-user to annotate any kind of web contents." Apparently related with Europeana and funded by the EU. Sounds like open source but after a very few clicks couldn't find sources (busy day etc). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
