|
|
I have assigned this to Salman for v11 so he can review current usability. While I don't think we should be adding pixel/border-level specificity, it should be easy, even default, for things to space nicely. With current attachment options (if simplified attachment UI is not turned on) it should already be possible to set reasonable spacing and alignment. If simplified attachment UI is turned on it should at least be sane. But, attachments are a complicated negotiation between 3 different use cases - proper content authoring, simple attaching for collaboration, standalone image posting. And a negotiation between Comcode and full WYSIWYG HTML authoring - and here sane HTML could potentially be getting mangled. I wrote the attachment code, so Salman should be able to review with a fresh perspective. |
|
|
Also Anomalous1 if you could put up a video somewhere illustrating your problem, it would help us get a better perspective. |
|
|
RunonText1.png (173,854 bytes) |
|
|
When adding the article, there is an image editor popup that allows me to narrow it down to a reasonable size. However, there is no option to create any open space to the right or to the bottom of the article so that the image is separated from the text by a few pixels. In short, the text is "connected" with no empty pixels between the text and the image. It would be nice if there were a default spacing to the right to keep the image and text separate, or nicer still if there was an option to include empty space by pixel count on the right and bottom at least, or perhaps on all four sides in case the photo is wrapped in different positions. Thus, the photo editor or image editor may have an option to create a space included "X" number of pixels. I included a shot of a JCE Editor which shows how the positioning of the photo also has an option for blank spaces or pixels around the photo, with individual boxes for top, bottom, left and right. A number can be inserted and that many pixels will then separate the image from the text. I hope that makes sense :/ I cannot even begin to imagine the complexities of coding for such an amazing CMS ... my cousin can but he says I should just be grateful ... VERY GRATEFUL ... for the masterpiece that is COMPOSR.
RunonText2.png (144,251 bytes)
ImageProperties2.png (169,779 bytes)
ImageProperties.png (174,603 bytes)
JCEEditor.png (116,247 bytes) |
|
|
JCE Editor is interesting. It's based on TinyMCE. Thanks for the screenshots. We're pretty much committed to CKEditor, and committed in not getting actively involved in CKEditor development. The version 4 we use (probably) reaches end of life in a couple of years, and we'll need to either upgrade to CKEditor 5 - which loses the ability to edit arbitrary HTML, something we currently rely on - and has a non-Open Source license - or we'll need to choose a new editor. So maybe we will revisit the WYSIWYG decision, but for now there's nothing going to happen there other than maintaining our CKEditor integration. That said, I have just handled having a default image margin via 0003769. You don't get to edit individual edges or specify pixels as it comes in from a CSS class, but it should work for most users. More advanced users can always edit the HTML/CSS by hand. |
- Anonymous
