This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Provide i18n for InlineBezierCurveEditor #5553
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
15 changes: 15 additions & 0 deletions
15
src/extensions/default/InlineBezierCurveEditor/Localized.css
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
.bezier-curve-editor .coordinate-plane:after { | ||
content: '{{INLINE_BEZIER_EDITOR_TIME}}'; | ||
} | ||
|
||
.bezier-curve-editor .coordinate-plane:hover:before { | ||
content: '{{INLINE_BEZIER_EDITOR_PROGRESSION}} (' attr(data-progression) '%)'; | ||
} | ||
|
||
.bezier-curve-editor .coordinate-plane:before { | ||
content: '{{INLINE_BEZIER_EDITOR_PROGRESSION}}'; | ||
} | ||
|
||
.bezier-curve-editor .coordinate-plane:hover:after { | ||
content: '{{INLINE_BEZIER_EDITOR_TIME}} (' attr(data-time) '%)'; | ||
} |
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 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 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 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make more sense to move extension-specific strings to each extension?
Eventually, the Extension Manager will have the capability to enable/disable extensions (and I think this should apply to extensions in the default folder as well), so strings for disabled extensions will not get loaded. But, maybe the amount of memory saved is not worth the overhead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really know, but this would be some work as we had to add an nls folder with some subfolders and strings.js (twice, one in root and one in nls). So it maybe would save some memory, but it may also affect the loading performance (more files must be read from disk) and the size of an installed Brackets version.
But we don't need that now cause there aren't any memory problems (systems have much RAM by default).
And also every extensions uses these files for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that it's OK for now, but I just wanted to mention it.