Which WYSIWYG editor is used by xWiki? And was it ever using a different one? In which version did it change?
There are two WYSIWYG editors in the current (3.0-milestone-2) release: an older (now deprecated) one based on TinyMCE, and a GWT-based editor developed in-house, introduced in 1.7 (see http://platform.xwiki.org/xwiki/bin/Features/PageEditing#HWYSIWYGeditingmode and http://platform.xwiki.org/xwiki/bin/Features/WysiwygEditor for more details). Back in the very early days of XWiki (2005), there was another editor based on HTMLArea, but it was quickly replaced by TinyMCE.
So, the current editor is not an external one, but a custom developed one, available under the LGPL 2.1 license.
Related
It's just a simple question but couldn't find any helpful solution or hints...I have the current TYPO3 version and watched some videos on YouTube about it and wondered why I have no autocomplete when writing some TypoScript.
I saw it in this video: https://www.youtube.com/watch?v=ZCSIK3lFfwM&list=PL1D69sw7eWECaiqIOLhcSnjgTTjLJdd4I&index=5 at 03:45
Is it possible to do it in the newest version or do I have to use an IDE?
First install the extension ts3editor.
Then you can "activate" auto complete just by pressing CTRL+SPACE. For example, write:
->config.
then press
->"CTRL+SPACE"
then the autocomplete advice/suggestion will pop-up.
I use version 9 and it works fine.
The TYPO3 core offers the extension "t3editor", which is based on CodeMirror and provides syntax highlighting and codecompletion.
I suspect it just isn't activated in your TYPO3 instance. You can check this in the Extension Manager in your TYPO3 backend.
1st edit: As the extension seems to be working in general – please try writing config. on a new line in your editor. The Top Level Objects (e.g. config) aren't auto-completed in the backend, but it should open a box with suggested configurations after you wrote the dot.
t3editor has some restrictions: Nesting isn't supported (see example below). I read it can have problems inside conditions, too.
// This is auto-completed:
config.no_cache = 1
// This isn't:
config {
no_cache = 1
}
In short: t3editor can only help you to a certain degree. It is considered best practice to save all TypoScript (and everything else related to templating) in files into a dedicated templating extension (or sitepackage) and use an IDE. There are TypoScript auto-complete plugins for several editors and IDEs, for example PhpStorm.
If you want more information about using sitepackages, see this video series on YouTube by the offical TYPO3 account, or take a look at my personal templating extension which I use for new websites.
2nd edit: After you wrote you're using the Sprint Release 9.1.0, I was able to test the behaviour in this version and can confirm that code completion won't work in it.
Actually, that seems to be the intended future behaviour of t3editor for the TYPO3 core team. They want to remove this extension in TYPO3 v10 altogether (it's planned to be available on GitHub then). The reason is that they don't recommend to use/save TypoScript directly in the database, but in a separate template extension (see explanation above).
Sources:
TYPO3 Bug tracker, issue #81885
Communication platform TYPO3 Slack, Channel #typo3-cms-coredev, Nov 19th, 2017
So again, I recommend to use an API instead.
When I say CQ5 I mean the version 5.5.
I would like to know the major differences in features.
I have seen AEM 6.0, the core of it is the same as CQ5. I checked out the examples, all the examples are the same, the only difference I found was the UI of WCM i.e. there is a new look and feel for it but you can still switch to the classic mode.
CQ5 still encourages coding in JSP i.e. it still uses scriplets.
Is there any alternative to using Scriptlets in AEM 6.x?
I feel Adobe just changed the look and feel of CQ5 and they have released a new version of it called AEM 6.x
What are the killer features of AEM 6.x that are not there in CQ5 ?
I would recommend you to take a look for release notes
I like below features quite a lot:
A new repository Apache Jackrabbit Oak.
Sightly, a new templating language that way you can avoid scriptlet code to a great extent.
Supporting better user management by delegating the permissions.
Create projects wizard & project templates
The above ones are very few which I have highlighted. There are many more so as per my opinion its not just UI changes so make sure you go through release notes to learn and then justify accordingly.
Long time reader, first time asking a question.
Most of my development work has been in .NET using Visual Studio. Recently I took over maintenance of a website built on PHP and downloaded NetBeans as an IDE.
NetBeans has a very nice CSS property wizard for HTML projects that highlights the CSS rules in use for a particular element and lets you edit the rules directly. However, this doesn't appear to be available for PHP projects, even for pure HTML files within the project. Is that correct, or am I just missing some configuration? I can't seem to find any confirmation either way in the documentation or forums. (It would be unfortunate if it didn't work... it's a really useful feature.)
Thanks,
Terry
If you are referring to the visual CSS editing support that works with Google Chrome and the WebKit browser embedded in NetBeans, then this feature will be available for PHP projects in the upcoming NetBeans 7.4 release. See also this blog post: https://blogs.oracle.com/netbeanswebclient/entry/html5_development_with_java_ee
Hope this helps,
Petr
We are editing lots of pages with text in Confluence version 3.5 but in one good day, we decide to upgrade our system to version 4.3.2. As a result, now, we have big problems with data.
All links in projects start being invalid and markup of text-fields changed, I think it connected with major changes in Confluence.
So now I trying to find way how to update this data and return nice view.
Is there any plugins? Or scripts? Or any default features of Confluence to doing this work.
New Editor
The Wiki Markup editor has been removed in Confluence 4 and replaced with a new XHTML-based editor.
Confluence 4 introduced a Brand New Editor with macro placeholders and a macrobrowser.
By default you won't see wiki markup anymore in the edit mode, but placeholders. There is one wiki macro called Wiki-Markup which u can use to enter wiki markup.
And for users who are very familiar with wiki markup there us an Autoformatting feature, which lets you type wiki markup into the editor and it will "auto-format" the text on the fly.
Have you read Planning for Confluence 4?
Also, please take a look at Migration from Wiki Markup to XHTML-Based Storage Format
Regarding your macros you may try
Re-running Migration or
Re-attempt Migration
The most common reason for content to be in this state is that a non
4.0 compatible macro (or unknown macro) was found on the page.
There are two possible fixes for this situation -
Install a 4.0 compatible version of the macro. See Plugin Development Upgrade FAQ for 4.0.
Edit the page to no longer use the problematic macro.
So as stated i would suggest you look for compatible versions of the macros/plugins and force a re-migratition:
URL: /admin/force-upgrade.action
URL: /admin/unmigratedwikicontent.action
What do you mean by the links are invalid?
What are the tradeoffs of the Eclipse Snippets View vs. editor templates? Why were Snippets introduced in the first place?
Snippets appear to be a custom version of templates, with a view in the perspective and GUI dialogs to prompt for variable values in the template.
The only "new" functionality they have is to offer up their functionality through toolbar items in the editors.
Snippets view is sort of an extension proposed by WTP (Web Tool Platform) for template, more oriented to (web) code formatting, whereas templates help the user enter reoccurring patterns into a text editor.
So at the beginning, Eclipse Templates was a standard eclipse feature which could only be applied for java and javadocs.
Snippets are basically the same, but for other kind of files and were introduced by WTP to fill the same need, but for their own type of files (xml, jps, html, ...)
(and this is, right there, "why snippets were introduced in the first place")
Template does not have their own view, but rather an obscure Preference page (Preferences -> Java -> Editor -> Templates)
You could at the time however write a small eclipse extension in order to make a Template View.
This has been resolved since eclipse3.4M6 (Templates have their own view)
You can also build some custom advanced snippets view
Additionally, the Snippets view was first conceived during the development time frame between Eclipse 1.0 and 2.0, before the content assist templates were anywhere close to being as capable as they now are. That's why it was created, and it simply came into WTP as part of IBM's initial contribution to the project.