I presume that you are thinking of pointing people at that external site from task examples by adding that category. That seems to me to be a major change that would affect many tasks but only benefit some small sample of the RC languages. I would rather have a section on Help:Similar_Sites with a list of sites that allow online code execution.
I suggest you drop a question on Mikes talk page (he is the owner mentioned here Rosetta_Code:About --Paddy3118 (talk) 21:34, 16 October 2014 (UTC)
There is already a similar template for codepad.org, which only supports about a dozen languages. So, what "major change" ? OTOH, a page about online code execution would be useful too. --Hajo (talk) 23:13, 16 October 2014 (UTC)
- Given the questions at the time here we should probably delete them both and add a section to the Similar sites page.
- Better still, could you delete your template and add the site to Help:Similar_Sites/Online_Execution. Thanks. --Paddy3118 (talk) 12:09, 18 October 2014 (UTC)
I already made a page Online code execution. compileonline supports a lot of languages, so that table would be quite large. Also, I don't see how that Help:xxx - construct is supposed to be used. --Hajo (talk) 12:21, 18 October 2014 (UTC)
Hi Hajo, since you are doing so much tidying up I wondered if you would just select the minor edit option when saving these edits if that is all the editing done? It would help me as I scan for other things in others edits. Thanks. --Paddy3118 (talk) 04:43, 23 October 2014 (UTC)
- I second this (I came here to say the same thing :)). I'd almost say that type of change is best done by an automated script/bot (or if done manually just when you happen to be making a near-by edit). I'm not sure what Rosetta Code's policy on users running an editing bot is though. —dchapes (talk | contribs) 18:59, 23 October 2014 (UTC)
Quite a number of output-sections are using "<lang>"-tags instead of "<pre>", also "<tt>", "<code>" and "<div>".
Then, there are cases with no "pre" at all, mis-spellings ("Ouput:"), and scripts of interactive sessions, i.e. a mix of code, input and output.
I think that would be a tough task to automate.
No problem marking those changes as "minor edits". --Hajo (talk) 15:52, 24 October 2014 (UTC)
On your task One-time pad
Hi Hajo, I saw your new task and had some questions that I added to its discussion page. After my comments I noted that you added to the task with the start of an implementation and am now thinking:
- It was probably too early for me to think of writing a language example.
- I am not sure that RC has a template to indicate that the task itself is still a work in progress, not yet ready for other contributors.
Maybe, if the task is still being worked on and you would prefer others to wait awhile then maybe you could add a comment on the Talk page and add Template:Clarify_task at the top ot the draft task. When you are ready for comments/language examples you can remove the Template:Clarify_task, ammend the comment, and leave it as a plain draft task?
P.S. I tend to write example code (off RC), before my first task description on RC and try and leave an initial task description that I hope people will then contribute to as I then leave little time between adding the first language example as I already have it waiting. But that's how I work; YMMV :-)
--Paddy3118 (talk) 07:19, 19 November 2014 (UTC)
TODO: Tasks not implemented.
You are aware of the Tasks_not_implemented_in_this_language link automatically added to each Language category page? In the "Your help needed" block on the right. --Thundergnat (talk) 11:05, 9 April 2018 (UTC) You are right. I noticed too late. -- Hajo (talk) 23:05, 10 April 2018 (UTC)