Composer Preview

MikeJones

HasanMerkit isn't that pretty much the same thing but more then this extension? Is there a need for this one to work with that one?

010101

HasanMerkit This extension is meant to be used if you do not want to use the WYSIWYG/rich text editor. That extension already lets you toggle between WYSIWYG and the plain text editor. Thus, essentially, it has built in preview mode.

In short, there are no plans to make this compatible with the rich text extension.

010101

v1.1.9

A new version has been published. This version is even more minimal. It no longer messes with as much of core's CSS.

Removed more unnecessary CSS left over from the original version

MikeJones

010101 nice! excited to update!

artificialflow

Hello

I'm currently testing this extension
There is a difference between creating a post and editing one.

When you create the post, the preview happens within editor.
While editing.. the preview is outside the editor(I think this is the default behaviour of Flarum).

What your thoughts about it?

TB54

artificialflow There are several discussions about that, but I think (throught this extension or in flarum core) than a preview outside the box even when creating a message would be more logical and ergonomic. But no idea how difficult it would be to code or heavy to run.

I talked a little more about this here: https://discuss.flarum.org/d/7152-no-preview-when-starting-a-new-discussion/22

artificialflow

TB54 Okay, thank you.

I'll dig more on standard editor. I want to know if editing preview comes from framework or markdown extension.

I see many people use WYSIWYG / Rich Text Editor

CyberGene

I tested this and there are some serious problems with it. For instance, embed a big picture in your post. The preview is not scrollable and the picture is displayed on top of the composer buttons, so you can't turn off the preview anymore and you get stuck. You can't do anything from this point on except to discard the entire post and start from scratch. That makes it unusable. I'm on Safari for Mac.

Wlork

I saw that there were several changes in developers, I would like to know if the extension is still supported ? 🙂

Wlork

I'm sorry to ask again.

I would like to install this extension but if it becomes incompatible with the next versions of Flarum then it's useless....

jslirola

Wlork I have it installed in my forum for a long time, it continues to work under version 1.7.2

Wlork

jslirola Thank you.

And for the next versions of Flarum, there is a guarantee that this extension still works ? 🙂

clarkwinkelmann

Wlork when an extension doesn't store any data, I don't think you need to worry about future compatibility. If it breaks you can simply disable it until a replacement is found or made. No reason to miss out on a feature just because the extension might not be compatible with a future Flarum version. It might just as well remain compatible, or someone else might develop an even better one in the meantime and you can simply swap out.

For extensions that do store data or user preferences, then yes, support, future proofing, export and data compatibility between extensions is extremely important.

Wlork

clarkwinkelmann Thank 🙂

I installed it but I quickly noticed an annoying issue.

When you click on "Preview" button on the creation of a discussion, if you don't switch to the editor mode, it stays blocked.
So when you reply to a discussion, it's impossible to switch. It'ss necessary to create a discussion and to put back the editor mode to unblock....

I hope I made clear 🙂

splitbrain

@010101 The github repository currently has issues disabled (probably because it was a fork). It would be helpful to be able to properly track issues as mentioned by Wlork, could you enable the issues tab?

010101

Hello! Thanks for letting me know. I haven’t had time lately to visit the lovely Flarum community. I’ll enable issues. And, I encourage pull requests or for someone to take over this extension because I’m not sure how active I’ll be here going forward. I don’t currently run a Flarum powered forum. Which was the main reason I tried contributing.

010101

v1.2

Merged @Nearata pull request #1 (🙏)

ref: https://discuss.flarum.org/d/29761-composer-preview/41
clear interval, otherwise they stack
update dependencies

Wlork

010101 Thank you for fixing this bug so annoying 🙂

I don't know what a pull request is.... That why I reported the problem here 🙂

Wlork

I've encountered a small issue with CSS in phone when you reply in discussion.

Without Composer Preview :

With Composer Preview :

As you can see, the title is offset by one line. Nothing serious, but annoying because it takes more space on mobile....

Thank you.

010101

Wlork

I don’t have a live or local installation of Flarum right now. But, you could try pasting this CSS/LESS into your custom CSS within your admin appearance settings. Then, try adjusting things. I don’t know what it could be. This extension uses very little CSS to try and avoid things like that. You could try changing positioning from absolute to relative. And/or try changing bottom 0 to something else. And/or try adding rules. I’m sorry, but I can’t offer more than that at this time. 😔

.Composer {
	.Composer-preview {
		&.hidden {
			display: none;
	   }
		position: absolute;
		z-index: 1020;
		background-color: @body-bg;
   }
}
.TextEditor {
	textarea.hidden {
		visibility: hidden;
   }
}
@media (prefers-color-scheme: dark) {
	.Composer {
		background-color: @body-bg;
		color: @text-color;
   }
}
@media (max-width: 767px) {
	.visible.Composer:not(.minimized)::before {
		opacity: 0;
   }
	.visible.Composer:not(.minimized) .item-title {
		text-align: center;
   }
	.item-preview-discussion {
		padding: 0 0 2px 0 !important;
   }
}
.Composer {
	background-color: @body-bg;
}
.Composer-preview.Post-body::after {
	font-family: "Font Awesome 5 Free";
	content: "\f06e";
	position: absolute;
	bottom: 0;
	font-size: 30px;
	opacity: 0.4;
}

Those are the only CSS rules this extension adds.

Wlork

010101

In the browser developer tools, the blank space above the title is : .item-preview-discussion

I don't know how to solve the problem 🙁

« Previous Page