Quinten Steenhuis
Quinten Steenhuis
Alternative idea: always create a loop for developers. But that might confuse some developers and is not guaranteed to be what they intended (even if it is 99% of the...
We can always revisit this but closing for now--it's a very specific instance of something that #484 mostly addresses. It's a pretty advanced modularity task and it's not clear the...
Definitely open to you giving this a try. I think first we should address #349 and have it integrated with the configuration system, otherwise I worry it will be relatively...
Relevant to #558
This is a giant task but would be a huge improvement to the Weaver. #299 envisions auto-detection of fields in a PDF and would solve part of this if we...
Note that we should be able to parse a DOCX table and grab the first row as a header row.
I think this is redundant with an issue that I can't find, but one way we should consider to use the Weaver to give a hint that two fields are...
It might be something we let people fix in the Weaver UI, but FormFyxer has to provide an initial label. The example above has a label (table is just the...
One idea is to let people group questions into sections, and auto-generate the review screen to show the text related to those questions. Question: how do we handle the built-in...
Bumping this as I think we have heard in a few places how important it is to have navigation. ~A possible outline that would work for most forms, that the...