eZ Community » Forums » eZ Publish 5 Platform » RichText vs XmlText
expandshrink

RichText vs XmlText

RichText vs XmlText

Wednesday 23 April 2014 6:03:15 pm - 11 replies

Hi guys,

I caught a glimpse of a new kid on the block that intrigues me very much : the RichText field type.

I didn't dive deep in the code or event played with it but it seems it is kind of an alternative to our good old eZXmlText using the latest version of TinyMCE. I did not find a corresponding legacy datatype though...

Can you tell us more about it ? What are the plans with it ? What's the current state ? Can I use it ? Can I use it ?

Thursday 24 April 2014 9:15:39 am

It seems that's apart of last community version. If someone knows if that will be integrated in 5.3 EE version ?? Something replacing 'old eZXmlText' would be a good news...

Thursday 24 April 2014 3:41:46 pm

Hi Benjamin,

RichText is completely new field type. It uses Docbook variant for its internal format and XHTML for editing side. Conversion from XmlText format is also provided, so there should be some kind of a migration path.

Now I have to disappoint... server side of implementation in new kernel is ~99% complete, but as you noticed, there is no corresponding legacy datatype yet. Also editor is not implemented, what you saw of TinyMCE is used only for testing and demo purposes and we actually might end up using something else. So despite core being pretty much done, this is not usable yet. A lot of work on the editor remains to be done and it will not be ready for 5.3.

But maybe 5.4 will see it in action happy.gif Emoticon

You are of course welcome to check it out and play with it, there are quite some examples in the tests.

- Petar

Modified on Thursday 24 April 2014 3:42:04 pm by Petar Španja

Thursday 24 April 2014 4:54:51 pm

Hi Petar and thanks,

so what's the purpose of this new feature? Is it some kind of test on how things could evolve?

Friday 25 April 2014 8:42:39 am

Hi Benjamin,

as I already said, it is not finished yet. The purpose of having it in the codebase is not to have it fall out of sync with rest of the code.

- Petar

Modified on Friday 25 April 2014 8:44:28 am by Petar Španja

Friday 25 April 2014 9:10:14 am

Petar, I was asking about the initial intent: what use cases does it mean to fulfill? I understand it is a work i progress, I only miss the big picture. You didn't say if it is meant to replace ezxmltext in the long run happy.gif Emoticon

Friday 25 April 2014 10:06:27 am

Okay then happy.gif Emoticon The idea is to replace XmlText, for several reasons, probably most important one being XHTML editor. Aside from that new internal format based on Docbook fixes some shortcomings of XmlText and gives us really nice base to add new functionality. At the moment only existing XmlText functionality is covered and new stuff will probably come only after the migration from XmlText.

As this was implemented from scratch we did not have to carry baggage from Legacy Stack. All formats (internal, input and output) have schemas and are validated. We will probably add more input formats later on, but it is too early to go into the details on that part.

Hope this clears it up a bit happy.gif Emoticon

Friday 25 April 2014 12:03:19 pm

Hi Petar, 

thanks for this detailed answer. That's pretty exciting news and I'll have a deeper look as soon as I can happy.gif Emoticon

Thursday 29 January 2015 3:34:00 pm

I think moving to the new fieldType is a smart move on your behalf. I have a couple of questions however:

1) Will there be a conversion script which allows old eZXML fields to be automatically converted in to the new RichText fieldType.

2) Do you intend to provide default outputhandlers so we can render these data with attribute_view_gui or content_view_gui operators?

There are quite a number of customers who are moving some of their sites partially to a setup on symfony , but who would still like to use the new Editorial Interface for the older legacy. Is this something that you intend to support for the new RichText editor? 

Looking forward to the coming releases!

Thursday 29 January 2015 4:20:18 pm

1) Yes this will as mentioned by Petar take over for XMLText, so migration is planned. Time wise first version will be in place before the first stable of eZ Platform, so sometime during the spring.

2) Well this does not support legacy, however if your talking about this being possible to render in twig, yes. In similar way as the Platform stack version of XMLText. 

New UI and legacy will not be supported side by side officially by eZ, but we have made done the initial effort (legacy-bridge) for this scenario to be possible to archive with some additional community contributions down the road. Some more information is found in the blog post that went out yesterday on link above.

Modified on Friday 30 January 2015 9:18:46 pm by André R

Wednesday 21 October 2015 2:28:34 pm

Quote from André R :

1) Yes this will as mentioned by Petar take over for XMLText, so migration is planned. Time wise first version will be in place before the first stable of eZ Platform, so sometime during the spring.

I guess you have more information about that by now. Can you tell us what we can expect for the stable release ?

A script to convert XMLText in RichText ? A "on the fly" conversion allowing us to use the new editor with XMLText fieldtype ?

Quote from André R :

New UI and legacy will not be supported side by side officially by eZ, but we have made done the initial effort (legacy-bridge) for this scenario to be possible to archive with some additional community contributions down the road. Some more information is found in the blog post that went out yesterday on link above.

Is it still valid ?

 

Thanks !

Saturday 24 October 2015 10:44:13 pm

> Is it still valid ?
yes, and nothing new there, no implementation exists for RichText for legacy. 

> I guess you have more information about that by now. Can you tell us what we can expect for the stable release ?
For the first stable release we hope to have migration guide for XmlText covered, there is some support for conversion already, but we need to document it. There are also some edge cases for old XMLText content  that we also need to work on, and probably some we are not aware of that we will need help from testers to identify.

Modified on Saturday 24 October 2015 10:44:55 pm by André R

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from