I just successfully implemented the spell checking plugin for TinyMCE using the instructions here. I got a bit scared, though, by this ending paragraph.
I've had some trouble finding good documentation of the Google Spell
Service and it seems as if it is no longer updated but still
available to developers already using it (which should include the
TinyMCE .Net package even though you haven't used it before). However,
use at your own risk should Google decide to delete it. This is the
only official documentation I can find and that isn't much...
Am I to understand this to mean that the spell checking service used by Moxiecode.TinyMCE.dll points to an unsupported, abandoned api from Google?
EDIT
It seems as though the spell checking is happening via a post to https://www.google.com/tbproxy/spell?... as decribed here.
Is this service documented anywhere?
Related
I come from the world of JavaDocs and love the DX of working on a thoroughly-annotated application after a certain level of complexity.
Being able to hover over and peek all the props (and implied types) of a component with some brief documentation would save me so much time instead of having to open up and read through the whole component. Better yet, running a command to generate a documentation site just like you can with JavaDocs would be dope!
Are there any standards or tools built around creating SvelteDocs? I looked through the VS Code marketplace and didn't see any documentation tooling related to Svelte.
I stumbled upon this question in search of more in-depth documentation for the hover/peek documentation method I've been using. It seems that it is not very well documented (ironically) but it is a part of Svelte language-tools and I've been using it for some time with Svelte for VS Code so I'm sure there was more documentation at some point. The way it's used is as follows in your component. I remember reading somewhere that it needs to be the first thing in your component, but I can't find that source anymore.
<!--
#component
some markdown here
-->
For some reasons the only documentation I can find of it is here. But it provides very nice markdown support so you can craft some very informative hover/peek documentation for your components.
EDIT:
Still can't locate official documentation for the #component commenting feature but realized it is indeed described in the FAQ: https://svelte.dev/faq#how-do-i-document-my-components Does this information belong in the actual docs? Maybe.
After more digging, I found just a couple projects for documenting Svelte.
SvelteDoc Parser -- takes a VueDoc approach, based on JSDoc standards, generates JSON documentation for Svelte components
Svelte-Docs -- documentation in Markdown mixed with Svelte's features, can embed components in the generated doc pages
Both look interesting while taking completely separate approaches to solving the issue of application documentation. Perhaps there's still room to build a CLI-based site generator for the SvelteDoc Parser which could be turned into a VS Code plugin!
It is difficult to find a good one. I recommend
https://github.com/carbon-design-system/sveld
It looks very promising. It offers export in Typescript definitions, JSON and Markdown. In my opinion there is only one critical bug left (Markdown generation) so hopefully it can be used very soon.
I want to set up an open data website with the typo3 cms. For open data I do not know how I can manage with typo3. After a tour on google I found the CKAN API.
My questions: is it possible to integrate them? If not, are there any other solutions with Typo3?
Thank you for your possible answers
I don't know an implementation of the CKAN API and a quick search in the TER (TYPO3 extension repository) never showed any results.
Nevertheless there exists an extension filemetadata which is doing probably partially the requested features. Here the links:
filemetadata on Packagist.org
filemetadata on github.com
For the case that the features are not enough or the structure is not like desired a new extension could be programmed where some basics could be taken from the extension above, at least it could serve as example how some things are done.
It has to be mentioned that some extensions are never registered in TER but only available on github perhaps. So before programming something a deeper search might be advisable.
In former times another extension was common for Digital Asset Management, the extension-key and Name was dam. That extension is not compatible with current TYPO3 versions and taking it as example is probably no good idea as much outdated code had to be adjusted.
Nevertheless the advised example above is not the only possibility, the search for file metadata still shows other extensions that are compatible to current TYPO3 versions 7 and 8 which could be taken as examples. Perhaps changed search-words still let you discover more useful extensions.
The mentioned extension in the top is supported by the TYPO3 core team, the others are provided by other developers. I never compared the extensions and you had to see code or/and features by yourself. So I never endorse any of these solutions as usage is rarely requested.
If you search for the most recent code it's always good to search on github first for the development branch or a release that is not (yet) published in TER. Another source of information is forge.typo3.org, there many extensions are listed too, some even with repository on git.typo3.org, perhaps it's worth it to mention that this source is abandoned by some developers in favor of github.
Technically it would be even possible to extend any found extension and add more features or change something just by another extension - without touching the original extension. But before thinking too far you should first have a look if any found extension could satisfy your needs already.
For further questions that might be already related to coding you should open new question(s) with more detailed explanation and code-examples, even if that doesn't work yet.
EDIT 15th Oct 2018:
Just got a hint about a helpful extension for those purposes: extractor. Additional fields shall go to sys_file_metadata and be a part of the extraction service.
As I never did verified it by myself I can't give further hints in the moment.
Where can I find a developer guide to kibana, that explain me how the system work and all the things i need to know for developing kibana plugin?
Or if someone could publish snippets of sample plugin.
I've started cloning statusPage plugin, but I don't want to do revers engineering to understand the platform.
On the website, the is no type of developer manual.
Thank you
You can refer to the following links to learn How to develop Kibana Plugins:-
http://logz.io/blog/kibana-visualizations/
https://www.timroes.de/2015/12/02/writing-kibana-4-plugins-basics/
The official answer from 6+ months ago seems to be "don't":
We're working to develop an external API but would caution you away
from making custom changes as things still move pretty fast and
internal APIs are likely to change even in patch versions.
Also, "there are no public plugin APIs right now" (8/2015)
Hard to find any information to date. I recommend you to look at the plugin generator released some days ago:
Generator Kibana Plugin Structure
There are two plugins I found where you can have a look at the code to understand the structure. The first is the Sense plugin, the second Timelion. Timelion matches more to the structure of the generator.
Sense Github
Timelion GitHub
I suggest understanding plugin structure and code for traffic plugin (https://github.com/sbeyn/kibana-plugin-traffic-sg) which would be one of the simplest plugins to understand and you could directly add it to your installed plugin folder in kibana and see it working.
Other than that I would also suggest you do read timroes blogs (https://www.timroes.de/2015/12/02/writing-kibana-4-plugins-basics/) for developing kibana plugins
and last I would also suggest using elasticsearch discussion forum for kibana related issues as well for quicker responses:
https://discuss.elastic.co
I have a lot of coding in FreeMarker template files for view layer in my app.
I was wondering if I can set a debug point with Eclipse. Is there any good plugin that I can use to debug FreeMarker template files?
As far as I know, you cannot. A template file is a plain text file that the template engine reads into memory and then uses to produce a document that it writes to the response. It's not actually executable code. You can put a breakpoint in the template engine code and follow along what it replaces and how.
FreeMarker has a debugging API, although it has stuck in experimental state eons ago, mostly because nobody has taken the effort to write a front-end for it (like an Eclipse plugin). Except, I know they have planned to support it under some of the next LifeRay IDE versions. As far as I know they managed with break points, but there's no support for stepping in the FreeMarker API for example.
This is an old question and answering it right now doesn't make sense, but maybe it helps to all those people who often visit this page to find whether there is a way to debug freemarker or not.
As in the earlier answer it was stated that there is an Official API for the debugging, so just to add a little more into it for beginners.
Please refer to this official API and check freemarker.debug package [as official description says - Debugging API; experimental status, might change! This is to support debugging in IDE-s.], it is surely to help.
FreeMarker 2.3.29
I've looked at the GtkSourceView 3 Reference Manual, and I've googled for a while, but I cannot find any mention of why gtk_source_iter_forward_search was dropped from gtksourceview or what should be used instead.
I've also looked at the features link at the gtksourceview website where it lists as a feature: Caseless UTF-8 compliant search.
I've looked at the gedit source ver 3.2.6 (since I know they use gtksourceview), but they seem to be using gedit_document_search_forward, which I'm guessing comes from some other library. So my question is, what happened to the search capabilities in gtksourceview? Is there another library that provides similar functionality to gtk_source_iter_forward_search, or is it now done another way within gtksourceview?
I originally wrote my editor in gtksourceview-2.0, now I am rewriting it using gtksourceview-3.0, and I have an established search forward function based on the gtk_source_iter_forward_search function.
Thanks.
Always browse the source if you want to know these things. I found in this commit that GtkSourceIter was removed because the functionality was moved to GtkTextIter.