Set up text editor

[ijmccallum]

Had a look through some options, this one looks pretty good: https://github.com/Alex-D/Trumbowyg

[ijmccallum]

In fact - I should put together a requirements table and run through more editors to find the best suited, more work but probably worth it! Details to go into this page: https://github.com/WikiLogic/WikiLogic/wiki/Editor

[DouglasUT2018]

Just to check - Sunday at 10am for meeting? Was going to text you now but its late for you and on a school night!

The editor can be extremely simple plain text. Cant think of any punctuation or styles (bold, italics, etc) they would need. Might be worth exploring the rest of the UI and getting back to this.

On 20/06/2016 20:57, Iain J McCallum wrote:

In fact - I should put together a requirements table and run through more editors to find the best suited, more work but probably worth it! Details to go into this page: https://github.com/WikiLogic/WikiLogic/wiki/Editor

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/WikiLogic/WikiLogic/issues/212#issuecomment-227251555, or mute the thread https://github.com/notifications/unsubscribe/ABYvnkbw1bdOxECLm3wF_rjjXgt_4JwHks5qNvC6gaJpZM4I6D4G.

[ijmccallum]

added some comments! http://www.wikilogicfoundation.org/wiki/index.php?title=UI#Critique_of_current_layout Got to specify which time zone you're meaning! 10amUS / 3pmUK - that would work! Yeah - no bold / italic / etc. I've added an editor plugin as it would allow us to skip writing any code to manage text input directly. My plan is to remove the normal buttons (already done!) and add our own, eg the fallacy tagger or linking dictionary terms. If the tagger is only applying to part of a statement we need a way to manage which part. The editor I've got turns the text of a claim into a much more easily handled data structure, as opposed to reading it off the DOM (which is a nightmare). Also, the editor will let us turn editing on/off without having to play around with hacking html input's (which is what i was doing before). Massive plus to the editor I've got - it allows us to extend to different languages :D I'm not looking at that in detail yet - just a nod to the future, might be able to hook into the way it does that and use it to power the language used throughout the rest of the UI. We will have to build our own eventually, but that'll be a bit down the road.

Date: Wed, 22 Jun 2016 00:00:57 -0700 From: notifications@github.com To: WikiLogic@noreply.github.com CC: assign@noreply.github.com Subject: Re: [WikiLogic/WikiLogic] Set up text editor (#212)

Just to check - Sunday at 10am for meeting? Was going to text you now

but its late for you and on a school night!

The editor can be extremely simple plain text. Cant think of any

punctuation or styles (bold, italics, etc) they would need. Might be

worth exploring the rest of the UI and getting back to this.

On 20/06/2016 20:57, Iain J McCallum wrote:

In fact - I should put together a requirements table and run through

more editors to find the best suited, more work but probably worth it!

Details to go into this page:

https://github.com/WikiLogic/WikiLogic/wiki/Editor

—

You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub

https://github.com/WikiLogic/WikiLogic/issues/212#issuecomment-227251555,

or mute the thread

https://github.com/notifications/unsubscribe/ABYvnkbw1bdOxECLm3wF_rjjXgt_4JwHks5qNvC6gaJpZM4I6D4G.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.

[DouglasUT2018]

See red

On 22/06/2016 13:10, Iain J McCallum wrote:

added some comments! http://www.wikilogicfoundation.org/wiki/index.php?title=UI#Critique_of_current_layout Responded. Great we clear this up now. Want the meeting to be only the stuff not easily communicated by emails. I am thinking we share screen and sketch ideas out for 30 minutes? Not sure if best to do that on pen and paper or photoshop or some UI design software online? Got to specify which time zone you're meaning! 10amUS / 3pmUK - that would work! Oh i thought you said /my /moon set. I am good with that! Yeah - no bold / italic / etc. I've added an editor plugin as it would allow us to skip writing any code to manage text input directly. My plan is to remove the normal buttons (already done!) and add our own, eg the fallacy tagger or linking dictionary terms. Remove normal buttons is nice! Dont think we need to add our own. Think we should use dictionary API that picks up and defines every word by default - the user cant pick to have some words not defined. They can specify the meaning when the dictionary offers many. For example there will be a small 7 beside it to show its the 7th definition on the list and also cool if mouse over automatically now picks the 7th definition to show to users. Also they can add more definitions to fit their specific need. obviously Oxford dictionary wont allow us to write to their database so we need to have out own that expand on theirs or even write a one of code to pull in all the data from an online dictionary? Probably illegal though... Dont think you would ever use the fallacy tag on the same screen as the text editor. You only apply them to existing nodes that shouldn't be edited or the links between nodes that dont have text. If the tagger is only applying to part of a statement we need a way to manage which part. If a statement has a part that is fallacious and a part that is not, it needs broken down. As suggested in wiki, there will be a break apart button which allows you to separate them out. You can then correctly apply the fallacy tag to the failed part only.

The editor I've got turns the text of a claim into a much more easily handled data structure, as opposed to reading it off the DOM (which is a nightmare). Also, the editor will let us turn editing on/off without having to play around with hacking html input's (which is what i was doing before). Massive plus to the editor I've got - it allows us to extend to different languages :D I'm not looking at that in detail yet - just a nod to the future, might be able to hook into the way it does that and use it to power the language used throughout the rest of the UI. We will have to build our own eventually, but that'll be a bit down the road. Language is a huge consideration. Not looked at it yet, but long term i think we cannot afford to have multiple languages in the same way as everyone agreed science has to have only one dominant language. This solves many issues in one shared centralised database of knowledge and reasoning. Saying that, English is particularly bad for logical thinking so maybe if this takes of we will decide on another dominant language? Also, the first challenge is to get a large group of people accepting this so why restrict our market? Maybe we release in all major languages and see if it takes of anywhere then build on that.

Date: Wed, 22 Jun 2016 00:00:57 -0700 From: notifications@github.com To: WikiLogic@noreply.github.com CC: ijmccallum@hotmail.co.uk; assign@noreply.github.com Subject: Re: [WikiLogic/WikiLogic] Set up text editor (#212)

Just to check - Sunday at 10am for meeting? Was going to text you now

but its late for you and on a school night!

The editor can be extremely simple plain text. Cant think of any

punctuation or styles (bold, italics, etc) they would need. Might be

worth exploring the rest of the UI and getting back to this.

On 20/06/2016 20:57, Iain J McCallum wrote:

In fact - I should put together a requirements table and run through

more editors to find the best suited, more work but probably worth it!

Details to go into this page:

https://github.com/WikiLogic/WikiLogic/wiki/Editor

—

You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub

https://github.com/WikiLogic/WikiLogic/issues/212#issuecomment-227251555,

or mute the thread

https://github.com/notifications/unsubscribe/ABYvnkbw1bdOxECLm3wF_rjjXgt_4JwHks5qNvC6gaJpZM4I6D4G.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/WikiLogic/WikiLogic/issues/212#issuecomment-227724184, or mute the thread https://github.com/notifications/unsubscribe/ABYvntmkiGzWcR_CkMHOLa5aPIvo9LT4ks5qOSZMgaJpZM4I6D4G.