![]() Both? The last one? And what happens with intermediate versions? What about versioning and a rollback? With real-time editing by several editors at the same time, the question arises as to who gets the credits. This is important, among other things, because the currency in Wikipedia is the edits. So far, the Wikipedia has followed the principle of “one change, one author”. The fact that simultaneous writing (real-time editing) is not yet available in Wikipedia and for MediaWiki has to do with specific problems of the Wikipedia communities. The MediaWiki VisualEditor basically has everything you need today. The TinyMCE we have used so far is technologically outdated in this respect. But this is the new technology you use when a new editor is developed. This is a very simplified and shortened presentation. This opens up many fancy possibilities: Comments, colored markers and more Since everything now runs independently of HTML, you can now use your own logic – independent of HTML – to ensure that the markups are placed in the correct position without errors. The clou: Only at the end of all calculations an HTML page is assembled. and into a second layer, which notes markings, e.g.Here only the text to be displayed is edited, together with a position specification. The MediaWiki VisualEditor now separates everything into two areas: A lot of things can get broken very quickly. With HTML, this is terribly complicated, because the tags must be nested symmetrically. Suppose you want to comment (“annotate”) a part of text. You don’t know if the cursor is inside the tag or outside, for example if a word is written in bold.Īnd this need for tagging causes problems. This means that the author writes a text, and the editor sets special characters in the background: the HTML tags. Back to TinyMCE: This editor writes HTML in the background. The developers of Etherpad and Google Docs copied the basics. Technically, the problem is basically solved. We had already drawn attention to this development three years ago. For example, simultaneous writing, as known from Google Docs: several authors can edit the content simultaneously. The VisualEditor also offers many technological possibilities for the future. VisualEditor paves the way to real-time editing But for the BlueSpice users and for our customers this is now an ideal solution. And there are some functions in BlueSpice that we would like to add. Unfortunately, table editing is not yet at the level we would like to see. Up to now, templates were a function for authors with in-depth knowledge, because their use was not supported and you had to understand Wikitext in order to use them. This is very convenient and will fundamentally change and support the use of templates in the Wiki. So you don’t have to go to the Wiki code editor anymore. And it gets even better: You can change the content in the respective template directly from the editor. In contrast to the current version in BlueSpice, templates are not only displayed as an uneditable tag, but you can see the template in edit mode as it looks published. For example you can edit templates very comfortable. There are many features that we have long wished for.The developers once ran all articles through the editor to find errors. This VisualEditor is stable and is tested against the entire Wikipedia.The editor has been developed natively for MediaWiki, is technologically based on completely different procedures than TinyMCE and is directly tailored and optimized for use with MediaWikiText.With the release of BlueSpice 3 we have delivered the new MediaWiki VisualEditor to our customers. The new visual editor came with BlueSpice 3 ![]() With the delivery of the MediaWiki VisualEditor this very time-consuming work is no longer necessary and we can finally turn our attention to new topics. ![]() Nevertheless, in recent years we have continued to work on a Wiki code parser that provides this translation service. This means that it does not necessarily meet the common formal requirements for a conversion. And vice versa, WikiText is very error-tolerant. There are several possible ways to achieve the same thing. The challenge in adapting an HTML editor to MediaWiki is that this conversion is not unique. For MediaWiki, however, the input must also be converted into wiki code. Editors like Tiny offer a word-like interface (“Rich Text”) and convert the input into HTML. WordPress and many other open source projects use this editor.īut at MediaWiki you face a special challenge with every editor, even with TinyMCE. BlueSpice 2 was delivered with a TinyMCE editor, probably the most used HTML editor on the web. ![]()
0 Comments
Leave a Reply. |