![]() Updated Ace to version 1.1.6.ġ.4.28 - Fix bugs with menus that wrap too soon, particularly in Russian, and bad project file loading.ġ.4.27 - Added Russian translation. hbs extension for Handlebars files.ġ.4.32 - Fixed project restoration bug, and some other small issues with focus and default settings files.ġ.4.29 - Added Groovy support. Added Swedish translation (thanks, Usaki!).ġ.4.33 - Upgrade Ace to 1.1.7, and enable the. Support added for opening Lisp files directly (thanks, rysquash!).ġ.4.34 - Upgrade Ace to latest version. Added a slight delay to the project when autohide is enabled. Add support for Verilog and VHDL files.ġ.4.35 - Fixes a bug with the Files app when tab restore is disabled. Fix a missing dialog string for when files are modified in the background. Added support for Clojure syntax (thanks, Rui!).ġ.4.36 - Fix a bug when the "experimental JS" flag is turned on in Chrome. Fixed Ctrl-D behavior to when no text is selected (thanks, Peter!)ġ.4.37 - Added an option to disable "behaviors," which is the Ace term for auto-completing quotes, brackets, and HTML tags. If you like Caret, leave a review! I love reviews.ġ.4.39 - Updated to the latest version of Ace, some cleanup on API surface.ġ.4.38 - Added Chinese translation (thanks, Nolan!). Looking for Git/Drive/SFTP support? Please read this note: Ĭaret is also 100% open-source: please feel free to contribute code and file bugs via the GitHub repo (see website link on Details tab, or look in the menus for Settings > About Caret). Help documentation is available at the GitHub wiki, including a list of possible keyboard/menu commands: Command palette/smart "go to" functionality Sublime-compatible keymappings, including multiple cursors and selections ![]() ![]() Project view with folder navigation and project-specific settings files (requires Chrome 31) open files directly from the Chrome OS file manager remembers/restores open tabs (requires Chrome 31 for full support) syntax highlighting for many languages, and lots of color themes total offline support-no network connection required The goal of Caret is to provide a missing portion of the Chrome OS developer story: serious programmer tooling without needing to install a second OS and learn Vim. However, these things wouldn't be necessary for a baseline capability.Professional text editing for Chrome and Chrome OS ".easily the best code editor on the Chromebook." - AppStorm ()Ĭaret is a graphical text editor modeled on Sublime Text, running completely offline (no Internet connection required) and capable of opening and saving files anywhere on your hard drive. I definitely wouldn't want a feature like this to hold back something simple like the above features. I'm not personally convinced that this is very useful. There are two big benefits to this: 1) When you revert a page the version tree would look better (and make more sense) to people looking at it from the git side 2) the storage of all that text is much more compact as git only stores differences not a whole copy for each change.įinally, if you want to get really fancy (and expend a LOT more effort) you could enable features such as branching where you can have multiple different versions of pages live at any time, then merge them back together eventually (or not). The next level of complexity that could be added on after this is incorporating git's history to replace the use of the data/attic directory. This basic level of functionality would allow people to clone the repository and keep it on their local machine, edit, and merge back. The difficulty level on this should be fairly easy, because as was mentioned above all the writing is done in central functions. That would give you quick and easy git back-end storage. If the data/pages directory was in git, the only change absolutely necessary would be to commit the change each time something has been written to disk (inside the data/pages directory). ![]() You will also need to change code in a lot of places in DokuWiki as we don't have any file access abstraction for accessing stat information (reading/writing is already done in central functions).ĭiscussion: I'm not sure if this would be as hard as you make it sound. ![]() Hard There are already some wikis based on Git so you don't need to start from zero, but you will have to read and understand a lot of code unless you should already know Git very well, then that task won't be that difficult. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |