Does leksah support any kind of plugins? Will it? Does it have any plugins built in, such as hlint, hoogle, pl, djinn? If not, is there an easy way to integrate these things?
Does leksah support any kind of plugins?
Current version not.
Will it?
I am working on a major restructuring, to build Leksah from plugins from the very base.
https://github.com/leksah/billeksah/wiki
Unfortunately this project may take some more time to reach delivery,
but hope it will pay off.
Does it have any plugins built in, such as hlint, hoogle, pl, djinn?
It has simple support for lookup of hoogle docs.
If not, is there an easy way to integrate these things?
Help is very welcome.
Well someone ought to answer. Here's my best guesses:
Does leksah support any kind of plugins?
Nope
Will it?
It's open source (GPL 2)...get to it! (Doesn't look like this feature is on any roadmap or anything.)
Does it have any plugins built in?
According to the manual page 32:
With the Docu button you can initiate an external search in a browser with e.g. Hayoo
or Hoogle, depending on the configuration in the Preferences.
That's about all I could find.
Related
I have been using Laurent Treguier's Uncrustify extension but it has been recently unpublished. (https://marketplace.visualstudio.com/items?itemName=LaurentTreguier.uncrustify&ssr=false#overview)
Any insights about this? Is this temporary or not? Do I have an "uncrustify formatting" alternative? I mean, my company requires us to use uncrustify and I would like to avoid going back to sublime for this sole reason.
That's a terribly good question.
Do anyone knows why Uncrustify was removed from VSCode and if it will get back?
I switched to external formatters extension (https://github.com/SteefH/vscode-external-formatters).
I've found crustless by Software Ape to be a good enough alternative.
It's very basic, but does the job.
How do we add our own plugin. Lets say a new add-on or feature which can be installed and used. How do we develop that? I am sorry i am new to this.
Kindly help
Depending on your needs, I suggest you check out:
https://documentation.bloomreach.com/14/library/concepts/open-ui/introduction.html
You can also create various plugins more like the native functionality. Adding such to essentials is described here:
https://documentation.bloomreach.com/14/library/essentials-plugins/overview.html
That doesn't tell you how to create a plugin however. Essentials is just a helper application, the plugin can be various things from services, to configuration, to document types, to hst components... All of that requires some knowledge of the internals of the system. Look around the documentation, you can see how to create various things like workflows, perspectives, and more.
A plugin is no more than a collection of code and configuration bundled together. It could be a frontend thing or a backend thing. So I can't simply tell you how to create them. It can be quite difficult, depending on what you want, to create a plugin. Look into the code of some plugins, you will see that it is basically a java project with some configuration that can be found by the system on startup.
You might want to ask more specifically on what exactly you want to develop. That could lead to more specific advice. It can be daunting when you are starting to work with the cms. With experience it does start to make sense.
I have a plugin's resource codes and I want to edit. Because I want to change plugin's prefix but it isn't possible unless edit plugin. I tried edit with Eclipse but I had a lot of errors.
If you have source codes of some plugins, there meight be a problem, that they are using some api for example WorldEdit api, but you don't have it added in your project. You have to look into code and find out what they use. Then download the api and add it in Build Path - Right Click the project->Build bath->add external Jars. I hope this will help.
You may be getting errors from imports, API's, etc.
The best way to change this is to contact the developer of the plugin, who has the project themselves. It's not a good idea to change code unless you have full permission; but I will still tell you some possible ways to fix it.
Your imports may be faulty, check those.
Actually REVIEW the code yourself– Don't mess around with things you don't know what they do.
CHANGE YOUR PACKAGE NAMES (This got me before, simple mistake)
If there are comments in the code, use those to your advantage
Google your errors.
If you are new to Java, don't skip to changing code already. TRUST ME. Learn all you can before skipping to other "higher level" developer styles.
Like I said, these are vague and simple ways to fix it; the best way to have your feature implemented is to contact the developer.
*I understand that this thread is old; I'm just saying this because there are currently no answers that describe this for other Google travelers of the internet.
I'm about to start devlopment of a new website and want to use yeoman/grunt to speed up development/testing. However the site needs to be build with limited CMS functionallty with a flatfile cms such as http://getkirby.com/. Now I'm a little confused as to how to use these tools together?
Anyone had previous experience with this or have any tips?
Thanks
I have a Kirby site with a grunt taskrunner for developement-stuff. I use coffeescript, sass, minification, linting, autoprefixer etc. You could have a look at my current grundfile.coffee or an earlier version of my gruntfile.coffee. I guess they are a good start point - you could pick some tasks you need, and add your own stuff.
But i'm not sure if it answers your question, because all this is nothing Kirby-specific, except the file-paths. So if this is no help, you could specify your question/issue.
Our small team of 3-4 developers uses a wiki for documentation and collaboration. I'm trying to put together a list of some solid extensions which would help make it better. We are using MediaWiki, but if you know of a good extension/plug-in for another platform I'd like to hear about that too. Thanks.
Here is my list so far:
Geshi for syntax highlighting.
FCKeditor
TagAsCategory
Promising Extensions that don't work w/ MediaWiki 1.15.0
CategoryEditor
IssueTracker
Two things come to mind:
Bug tracking tool integration
SCM tool integration
For MediaWiki there are already
Bugzilla integration:
http://www.mediawiki.org/wiki/Extension:BugzillaReports
SVN integration:
http://www.mediawiki.org/wiki/Extension:SVNIntegration
The whole list of extensions is here
Well, I think that a good starting point would be to check what we use at mediawiki.org, because this is a Development Wiki :)
My first choice would be CodeReview of course. It's not pretty, but it's very useful. See how we use it: it allows to integrate a SVN into the wiki, to add comments on code, tag commits, and put statuses on it.
At MediaWiki, we use new/verified/ok chain, adding fixme/reverted/resolved/deferred when things go wrong; but you're free to use your own statuses here.