User talk:Max34/VDCEditor
User:Max34/VDCEditor.
To add a comment, use the Edit button near the headline of the appropriate section. To create a new section, you can use the Add topic button at the top of this page. Comments on talk pages should be signed with "~~~~", which will be converted into your signature and a timestamp.
Sustainability
(using Template:Message) Hey, I don't mean to be an asshole, since I've already critiqued the {{Page}} template elsewhere, but I do have a few concerns over this extension itself, with the main problem being sustainability. Many people on this wiki (me included) use Firefox, which does not run on chromium like chrome for example, which means that this extension does not work for it. This means you would have to create another version of this extension for it, though I don't imagine that would be too difficult. However the larger concern I have is that this extension is unlikely to work for a sustained period of time without updates. Which is to say, you (or someone else) would need to keep updating this template for presumably the rest of this wiki's existence. And since editing pages using {{Page}} might as well require this, the entire wiki would basically rest upon this extension. None of this is of course a problem if you don't mind updating this for the foreseeable future, and I imagine that you wouldn't have to update it that often anyways, but I still thought to leave a message since this is quite a pressing concern for the future of this wiki. --Wisdurm (talk) 15:09, 6 Jun 2024 (UTC)
(using Template:Message) To be honest, I didn’t know that firefox doesn’t support this extension, I didn’t even think to check. The whole problem turned out to be that the background script is not available there. I was already able to fix this, but I noticed that some of the functionality does not work as it should. In the coming days I will be working on supporting the extension in firefox.
What about supporting templates and working with them... I can’t say anything for sure yet, but I plan to do a kind of manual implementation of templates directly through these templates. Self-written js, one might say. I have already tried to implement something similar and I think it will be quite possible.
To better understand what I’m talking about, I’ll give an example: we have an Emoji template. In the template itself there will be.. the template itself (obviously), as well as a special multi-line comment, something like <!--VDCEditor ShowThisTempateOnlyInNamespaces("* Talk"); <and the following code that adds, for example, a strip with emojis and when clicked on, a ready-made template will be inserted into the text
> -->
Thus, there will be no urgent need for updating. And yes, I foresee questions that this could be used for bad purposes, but I will try to do everything to prevent this from happening. --Max34 (talk) 19:49, 6 Jun 2024 (UTC)
(using Template:Message) By update necessity I meant more as in if the browser or the mediawiki version updates for example and the extension just straight up no longer works, though I doubt it'd be a frequent issue. --Wisdurm (talk) 20:29, 6 Jun 2024 (UTC)
(using Template:Message) Oh, you don't have to worry about that. this is almost not a problem. As I indicated on the extension page, it can also work on other projects based on the MediaWiki engine. I checked and it works quite well even on Wikipedia. Yes, there are differences among other projects, but most of them are minor. Therefore textarea with id "wpTextbox1" on one project remained the same on others.
And one more thing: I rethought my idea with additional template settings for the extension and now it will be implemented in a more familiar form, as a separate template that will simply place the settings in span tags with special ids, and the extension will load these settings through these special id. the only thing that remains is to figure out what settings we need. --Max34 (talk) 6:33, 7 Jun 2024 (UTC)
