Add new Publisher application #42
Merged
Conversation
This file contains 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
This embodies the features of kart and kart-sign for now, and will encompass kate-dist and kart-show soon, as well as features more directly related to the richer GUI of the publisher (e.g.: keeping track of projects, avoiding json configurations).
cute-the-niini
added
c:kernel
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.
The Publisher is a new Kate-cartridge-based application for creating Kate cartridges. The main advantages over the command-line-based
kartapplication right now are that the Publisher is fully sandboxed (using the same sandboxing as other Kate cartridges), and it's hooked to the Kate key store to automatically sign cartridges with the appropriate ECDSA key associated with the user's domain.This is a pretty bare-bones implementation of the Publisher, though. The configuration is still provided as a JSON file following the
kartconfiguration. There's a rich GUI for describing the cartridge's configuration coming in the next release, but it requires a fair amount of effort so I'm skipping it for this one.The Publisher is the recommended way of creating cartridges for Kate, but the command line applications will be kept for strict automation purposes until the Headless Kate feature is implemented (which will allow interacting with cartridges programmatically through typed APIs while being subject to the same sandboxing and capability security expectations as regular GUI cartridges).
Note that there are some kernel changes rolled up in this one that were required to expose some new features required by the Publisher.