Bootstrap utility 1.0 #13
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ross-spencer
force-pushed
the
bootstrap-utility-1.0
branch
from
a2766bd to
7309bc9
Compare
PUID and MIMEType were not being output correctly. A mix of copy and paste errors and an oversight!
Standard signature now outputs:
* {format-name}-{format-version}-signature-file.xml
Container signature now outputs:
* {format-description]-{format-puid}-{today's-date}.xml
We had some left over JavaScript after simplifying the clone method and so this is removed here. The form field offsets are also reset to zero which is more intuitive for those that want to set them explicitly.
We reduce some of the default percentages in Skeleton web-framework to present a more condensed layout.
ross-spencer
force-pushed
the
bootstrap-utility-1.0
branch
from
0ec49a5 to
85efed6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To workaround #3 we now forward the request to a locally running copy of the signature development utility 1.0. The code is in the PHP folder and the new bootstrap piece converts the signal from the new web form into legacy compatible sequences. The PHP code has not been changed other than to send the XML back to the caller slightly differently. 1.0 is a well-proven application and so users should be able to take confidence in the output of this work.
This work won't be merged as-is just yet. I think we'll keep it in a workaround branch, possibly a new release.
Notes on installation are: here.
Connected to #3