Page MenuHomePhabricator

Add a "preview of the message" button
Open, LowPublic

Description

Wikitext can be transformed in html with REST WM's api
https://en.wikipedia.org/api/rest_v1/#!/Transforms/post_transform_wikitext_to_html_title_revision
So it can be useful to have a preview (live preview ?) of the message before send it

Event Timeline

Petrb triaged this task as Low priority.Sep 2 2017, 10:15 PM

could also just stick it in action=parse

Framawiki renamed this task from Preview the wikitext message to Add a "preview" button of the message.Nov 4 2017, 2:37 PM
Framawiki updated the task description. (Show Details)

I purpose to add this task to Google-Code-in-2017. It needs skills in C++, and if possible in the Qt framework.

A new form was created recently in Huggle (custommessage.ccp/h/ui) : it allows patrollers to send a custom message to editors. The purpose of this task is to add something like a "preview" button to this new form, that shows near the wikitext the render of the message.
The message is written in wikitext, the standard of Mediawiki/Wikipedia for content. The easiest way to get a render is to use a POST request as described here to get HTML equivalent of the wikitext. Finally, yo can print the HTML in the form, probably by creating a web browser instance.
Don't hesitate to ask if we can help you somewhere. When it's good for you, please create a PR on the Github repo.

Framawiki renamed this task from Add a "preview" button of the message to Add a "preview of the message" button.Nov 4 2017, 2:52 PM
Framawiki moved this task from Backlog to Need volunteer on the Huggle board.Nov 4 2017, 3:41 PM
Petrb added a comment.Nov 4 2017, 6:55 PM

interesting task, but not easy. Definitely would require lots of coding. One of the requirements for code-in is that required code should take max 1 hour of work to experienced programmer. I /think/ I could do this in 1 hour, but I am not sure ;)

@Aklapper is that requirement still in place?

@Petrb, @Framawiki: 2 or 3 hours. Better to be safe than sorry.
Could this be broken down into two subtasks somehow? Or requiring a basic proof of concept only in a first GCI task, and proper implementation in a 2nd one?

Looking back, I also think that this task is too complicated for GCI, and we're not even ourselves about what we want. Let's remove this tag here too.