Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugging improved XForms (manuForma) #59

Open
mMoliere opened this issue Mar 8, 2022 · 2 comments
Open

Debugging improved XForms (manuForma) #59

mMoliere opened this issue Mar 8, 2022 · 2 comments
Assignees

Comments

@mMoliere
Copy link
Contributor

mMoliere commented Mar 8, 2022

General

Creating & Rearranging: THE MOST IMPORTANT ISSUE. In both the history and additions module, I encountered something puzzling. As I was trying to piece together prose text with some tagged items from p-elements, persName-elements etc. and I rearranged elements using the arrow button sometimes the elements and their content were duplicated. This also affects the XML-output that I submitted to your GitHub. (See the duplicate p-elements in the provenance section. One p-element even spilled over to acquisition.)

Performance: You warned us of lag – Sometimes it takes several attempts to load a module. Is there something we can do to mitigate this for the real thing, like add extra RAM?

Attributes: For some attributes the schema provides a list of predefined values. Is there a way to display them when the user clicks on the corresponding field?

Rename : Could you rename the following items in the left pane?

  • “MSS Contents” → “Contents”
  • “MSS Support” → “Support”

Modules

Person:

  • superfluous entry field for persName (id: name1205-8, name1205-9, name1205-10m, name1205-11, name1205-12) – displays concatenation of child addNames.
  • relation: attribute source and child element desc missing.

Contents:

  • I will add @xml:lang to rubric, incipit, finalRubric and colophon to schema and templates.

Support:

  • no measure-field

Layout:

  • height and width fields missing (displayed in Support!)

Binding:

  • could not open

Addition:

  • q-element inside desc not displayed
@wsalesky
Copy link
Contributor

@mMoliere Can you give me a better idea of exactly what issues you had, exactly which elements did not move correctly, and when? All the time? Sometimes? When they are nested? When they are the first or last item? Even some screen shots perhaps? I think the methods I am testing may be simpler then the actual use case scenarios so it could be helpful for me to know exactly what you are doing when you encounter the bug. Sorry for the added work on your side.

@wsalesky
Copy link
Contributor

@mMoliere New version is up, can you take a look. I tested the up/down arrows and I think I caught everything on this list as well. Let me know if I missed anything, or introduced any new bugs.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants