wax-prosemirror issueshttps://gitlab.coko.foundation/wax/wax-prosemirror/-/issues2024-02-12T11:58:48Zhttps://gitlab.coko.foundation/wax/wax-prosemirror/-/issues/97Draft: record changes to images in suggestion mode2024-02-12T11:58:48ZDione Mentisdione@coko.foundationDraft: record changes to images in suggestion mode<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
## Proposal
<!-- A precise statement of the proposed feature. -->
Recorded suggested changes for these actions:
1. Insert image
2. Delete image
3. Insert image caption
4. Delete image caption
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->2024 week 6 and 7ChristosChristoshttps://gitlab.coko.foundation/wax/wax-prosemirror/-/issues/50Add regex search to find and replace2023-11-20T14:37:29ZChristinaTrompAdd regex search to find and replaceThis issue is duplicated in the Ketida repo: https://gitlab.coko.foundation/ketida/ketida/-/issues/586
<!-- Required. Provide a general summary of the issue in the title above -->
## Context
Regex search is so incredibly useful for th...This issue is duplicated in the Ketida repo: https://gitlab.coko.foundation/ketida/ketida/-/issues/586
<!-- Required. Provide a general summary of the issue in the title above -->
## Context
Regex search is so incredibly useful for the editorial process. Especially in OEN when authoring and editing is expected to be done in the editor. For example it's amazing for an editor to be able to find all four digit numbers separated by a hyphen with any four digits following them, to help make sure all dates are separated by an En dash instead of a hyphen. 6 hours just turned into 30 minutes of work.
There are many other examples where regex is amazing and I'm sure in time more and more editors will become acquainted with it.
## Proposal
Add regex search and replace to the editor find and replace, which can be turned off and on. By default it's off.
Add basic regex guidance in the docs.
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->https://gitlab.coko.foundation/wax/wax-prosemirror/-/issues/46Improve support for ordered and unordered lists2023-11-28T09:44:00ZChristinaTrompImprove support for ordered and unordered lists## Context
This issue is duplicated in the Ketida repo https://gitlab.coko.foundation/ketida/ketida/-/issues/574
Currently these are the only two buttons relevant to lists in the Wax editor:
![Screen_Shot_2022-12-12_at_14.26.38](/uplo...## Context
This issue is duplicated in the Ketida repo https://gitlab.coko.foundation/ketida/ketida/-/issues/574
Currently these are the only two buttons relevant to lists in the Wax editor:
![Screen_Shot_2022-12-12_at_14.26.38](/uploads/7d01968552e23a34333b8d5bfaa3090c/Screen_Shot_2022-12-12_at_14.26.38.png)
Currently you can create a very basic nested list in the editor by following these steps:
1. Click the list icon (ordered or unordered) which creates the first item
2. Type some text into the first item
3. Hit enter to get a second item
4. Click the list icon again, to nest the second list item
The problem is, for ordered lists, the resulting list is like this, and the PagedJS templates export this as WYSIWYG where the numbering is the same as in the editor shown below.
![Screen_Shot_2022-12-12_at_13.12.07](/uploads/bdcef63f24044d1c7d49665d71c937a7/Screen_Shot_2022-12-12_at_13.12.07.png)
1. an issue for ordered lists is that if a paragraph or teacher refers to point 1, there are multiple point 1s so it doesn't make sense.
2. another issue is that for ordered and unordered lists is that you can't subsequently create points in the unnested part of the list (in the example above there is no intuitive way to unnest point 3 to make it a continuation of the previous level of the list). The workaround for this in the editor is to create the full unnested list (1, 2, 3), then add nested points within it by hitting enter on the 'parent' item and clicking the list icon again to nest children (nested items) within it, but that's not intuitive in the authoring process because it requires you to create all the 'parent' items first instead of writing the list top to bottom.
3. another issue for ordered lists is the lack of support for roman numerals, alphabetical lists, and other similar list handling which appears in a lot of textbooks.
4. Lastly, it's impossible to continue numbering when the list is split by explanatory paragraphs that are not part of the list.
## Proposal
Add advanced list handling:
- [ ] Dropdown list for types of bullets in unordered lists
- [ ] Dropdown list for types of 'numbers' in ordered lists (like roman numerals; A, B, C etc.)
- [ ] Add 'Continue numbering' and 'Restart numbering' options
- [ ] Add an ident and unindent button that allows you to shift part of the list right (to be nested) and left (to get unnested)
To give further context to how this is handled by other editors (not intended to be copied, rather just for context because it's a common feature in WYSIWYG editors), for example MS Word and Google Docs handle advanced lists like this:
![Screen_Shot_2022-12-12_at_13.27.00](/uploads/2706cc5cc43f2cec34ca0713c0404caa/Screen_Shot_2022-12-12_at_13.27.00.png)
![Screen_Shot_2022-12-12_at_13.20.03](/uploads/2532c9fde280af207454a49fe5e8a206/Screen_Shot_2022-12-12_at_13.20.03.png)
![Screen_Shot_2022-12-12_at_13.19.48](/uploads/d8e9b0d6b0b30bed02284d89afb3ccc7/Screen_Shot_2022-12-12_at_13.19.48.png)
![Screen_Shot_2022-12-12_at_13.19.34](/uploads/f0d9eea6c8d01c87a201bc98574d4f8d/Screen_Shot_2022-12-12_at_13.19.34.png)
## Design
[Include sketch or wireframes of the UI changes necessary for this feature]
## Implementation (if applicable)
[A description of the steps to implement the feature.]
## Alternative approaches (if applicable)
[Include any alternatives to meet this use case.]
## Open issues (if applicable)
[Links to and a discussion of related issues, if applicable.]Adam Hydeadam@coko.foundationDione Mentisdione@coko.foundationRyan Dix-PeekChristinaTrompAdam Hydeadam@coko.foundationhttps://gitlab.coko.foundation/wax/wax-prosemirror/-/issues/38Cannot use toolbar to undo ordered lists2021-11-15T05:59:30ZRyan Dix-PeekCannot use toolbar to undo ordered lists**Issue description;** as a user editing a manuscript in Wax clicking on the ordered lists (numbered/bulleted) toolbar plugins to *un-order* list does nothing. If an ordered list is imported or styled as such in Wax the user should be ab...**Issue description;** as a user editing a manuscript in Wax clicking on the ordered lists (numbered/bulleted) toolbar plugins to *un-order* list does nothing. If an ordered list is imported or styled as such in Wax the user should be able to use the ordered list tools to revert the ordered styling to paragraph text.
Reference; [Kotahi repo issue with an example](https://gitlab.coko.foundation/kotahi/kotahi/-/issues/697#note_71473).https://gitlab.coko.foundation/wax/wax-prosemirror/-/issues/36Applying image styles in Wax editor2021-10-11T11:45:40ZRyan Dix-PeekApplying image styles in Wax editor**Description;** currently specific images styling cannot be applied in the Wax editor, only captions can be added.
Use cases:
- Pagination; certain images are required to span the whole page in case of multi-column layouts, and other i...**Description;** currently specific images styling cannot be applied in the Wax editor, only captions can be added.
Use cases:
- Pagination; certain images are required to span the whole page in case of multi-column layouts, and other images remain within a column.
- Push an image into the margin with a class like `.margin-top` or `.margin-bottom`
- When certain images are to be treated in the same way, for example. The opening image of each chapter should take the full width of the page. In this case you'd want to apply a class to the image, e.g. `.chapter-opener` and then define the styles for that class in the stylesheet.
- When you're doing "print refinement" and you want control over an image to improve the layout of the pages, so it's done on a case by case basis. Here's where the float rules come in handy to override the rule that set for all figures
The current solution is to identify images by assigning a custom style using the Wax editor. A proposed solution is to apply a CSS class in Wax so that the CSS template in pagedjs can apply a style targeted to images only.