Request for feedback: Minimal TinyMCE implementation

[mcdaniels]

@marty: I don’t want to be impatient, but can you give any timeline for resolving this? First there was some moaning because the tinymce modified the fonts and now the users moan about the removed lines ;-).

[marty]

@mcdaniels All I can say is that KW-2860 is currently in reviewing.

[mcdaniels]

@marty: just need some info concerning the fix: https://stash.kopano.io/projects/KW/repos/kopano-webapp/pull-requests/813/overview. So this is an WebApp “problem”. (and is fixed?)

[marty]

@mcdaniels Resolved in WebApp indeed.

[mcdaniels]

@marty: So, I will have to wait till it is available in the final DEB repository? (or is there a faster and secure way?)

[marty]

@mcdaniels Yes you have to wait for the new final if you don’t want to run master.

[mcdaniels]

@marty: is it possible to use the webapp-packages from master, although you are using final for the rest, or will it mess up things?
PS: Tried the latest nightly of the webapp yesterday (in my testlab) in combination with minimal tiny and the paragraphs worked as they should do. :-)

[marty]

@mcdaniels

Potentially it can break things.
For example, if some code in WebApp is modified and no backward compatibility is added.

Test it, and see if you’re comfortable to update.

[mcdaniels]

@marty: in my private environment it is no problem, but here (130 Users) I can’t test all things users do with it. ;-)

Is it possible to tell, how long it will take until the webapp with the fix will be in “final”?

@marty: so the fix was not a small one concerning the minimal tiny. Would have been nice, if there was some kind of “Hotfix”.

[marty]

@mcdaniels
The minimal tiny plugin is not yet in the stage to provide hotfixes for.
If you not comfortable running WebApp master and plugins from the final repo, then you shouldn’t do it.
That is totally fine, but in this case, you’ll have to wait for the next release.

[mcdaniels]

@marty: hm… I thought, that the problem was not the editor and that it was “in” the webapp. So I wished a hotfix for the webapp. :-)

[marty]

@mcdaniels Yes we’re not hot fixing WebApp for that plugin, yet

[mcdaniels]

@marty: Thats a pity, cause the minimal tiny solves a lot of our problems, but not in the state it is now, cause of the webapp problem (paragraphs). I wonder how other users are handling these problems, which use the Web/Deskapp and the tiny / minimal tiny editor.

[marty]

Keep an eye on the announcement topic. We’re currently wrapping up some tickets we would like to have in the next release.
So the next release is rather sooner than later.

[marcus.bauch]

Hej!

The font in tables (Header aso.) are not in the default-font in Settings/Mail…looks like Times or so…

[marty]

@marcus-bauch Did you copy this from another application?

[marcus.bauch]

Hej Marty.

No. This ist handcrafted ;-)

[edit]

Should this plugin removed from plugins if WebApp 3.5.0.2047+85.1 (or newer) is installed?
With this version of WebApp the tables come up correct in the mail-composer, but when it is sent there is a different font…

Configured is Tahoma.

[/edit]

[marty]

@marcus-bauch Which client is used on the receiver side?

[marcus.bauch]

@marty

I use DeskApp (on Windows 8.1 (de)) v2.19. But it’s the same with pure WebApp (3.5.0.2047+85.1) and e.G. Chrome, or Linux Mint (lmde2 Cinnamon)/Firefox

Composer:

After sending (outbox):

Recipient (for tests to GroupWise 2014R2 Web-Client. Here, you see, “Table Test” is not centered)

…or GroupWise FatClient

Maybe this is the same failure as in signatures. If i dumpout a signature AFTER a user edit his/her signature the HTML-code is malformed like

<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"></span></p>
<p style="font-family: 'Times New Roman'; font-size: medium; margin: 0px; padding: 0px;"><span style="font-size: 10pt;">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Marcus Bauch...</span></p>
<p></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><br /></span></p>

…original imported (setdefaultsignature.py) signature was:

<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><b>Herzliche Gr&uuml;&szlig;e von Marcus</b></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif; color:green;">{%firstname}&nbsp;{%lastname} | {%department}</span></p>

[mcdaniels]

Is it still recommended to use the minimal tiny mce editor, if you do not want to have formatting issues in emails, or can we meanwhile use the standardeditor?

Thanks!