Background: My employer uses Confluence as our knowledgebase wiki, and they've turned on CamelCase links. Since we use a lot of CamelCase in our method names, this results in a lot of extraneous links; we can disable that behavior by wrapping every one of them in {nl:} but that gets tedious and sometimes we miss one. (And since there are many existing pages and not everyone is using it for code discussions, asking IT to change the global setting is a non-starter.)
Question: Is there a way to override the global setting, to mark an individual page in Confluence as not using CamelCase links?
Thanks.
Use the jQuery posted at https://jira.atlassian.com/browse/CONF-7999?focusedCommentId=237514&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-237514
nocamel macro can be made out of it. The poster and myself are using it successfully.
Not that I have found. Here are the Confluence docs on the subject:
http://confluence.atlassian.com/display/DOC/CamelCase%20linking
Shame eh?
I have this same problem. Starting a page with a '{nocamel}' macro sometimes disables it on our Confluence, but apparently does not reliably work all the time. It's not an official macro; it's possible our admin did some custom macro, but I doubt it. Perhaps it's an unsupported feature, but it's worth trying.
There are a couple of relevant Confluence feature requests that you might consider voting up. This one for disabling CamelCase linking in a page:
http://jira.atlassian.com/browse/CONF-7999
And this for disabling CamelCase linking on whole spaces:
http://jira.atlassian.com/browse/CONF-6526
Related
I began a very helpful discussion with Alessandro Pignotti (#alexp-sssup) on
https://gitter.im/leaningtech/cheerpj?at=5f189bf76279c91f420801af
about how to get Java applet byte-code to work with CherrpJ in present-day browsers.
Hopefully the two examples referenced there in this post can serve as a guide to others who might also be struggling with getting the basics of java applet conversion with CheerpJ going.
As I mentioned there I would, I am now putting this follow-up question in stackoverflow:
I was hoping to get this page to work in which I am trying to run the same byte-code with both the <cheerjp-applet> and <applet> tags on the same page. However the page never loads properly. The best I can achieve is (with page loading seeming to hang) to force some hung script to stop, which then often ends up bringing the CheerjP button up, but I have yet to the get button in the original applet to show on the same page (in a java-enabled browser-setup where the legacy applet does work properly from this page). Sometimes the browser completely hangs before even the Cheerpj script gets to work.
So my question is: Is what I am attempting even possible, and if so what could be wrong with this first attempt of mine?
P.S.: The stackoverflow tag [cheerpj] does not exist, so the suggestion on Gitter to use it fails for me: I don't have a reputation of 1500 :( !!! Since a pretty thorough web search has revealed very little in-depth technical discussion about CheerpJ besides what's in the Gitter CheerpJ room I reference at the start of this post, I am not sure how far the attempt to move discussion in to stackoverflow is going to go.
What you are trying to achieve is not supported by CheerpJ. When CheerpJ starts it will automatically replace any <applet>, <object> or <embed> tag containing Java applets and execute them internally. The special prefixed tags, such as <cheerpj-applet> are designed to avoid accidental execution by the native plugin if installed.
We don't plan to support this use case in the future since for the vast majority of users the native Java plugin does not work anymore anyway.
You may consider using two <iframe> tags to get the behavior you want using 2 independent pages.
If not, is there a way to do that with either docx4j or Aspose?
I've stumbled across the question
docx Template Docx4j replacing text in Java. It describes the actual problem I'm facing, which are template variables (like ${some.variable}) breaking across text runs due to spell check. However, his solution won't work well for me. The best solution I could achieve would be to disable (and maybe re-enable) spell check automatically under the hood.
There isn't at this point in time, but you can give feedback on https://officespdev.uservoice.com/ to request it to be added in future updates to the APIs.
Thanks,
Philip, Software Engineer on the Office Extensibility Team
Currently, I am working in a new project and it was difficult for me to understand since there is no comment. I wonder if it is possible to force team members(including me) to add more comments. I would like to automate this ject in jenkins later if possible.
You can run static code checks and their corresponding eclipse plug-ins to enforce comments being made in code.
For e.g. in CheckStyle javadoc can be enforced http://checkstyle.sourceforge.net/config_javadoc.html
Also checkstyle can be easily integrated with Jenkins.
You can also use eclipse java compiler settings for javadoc check.
Go to preferences->java->compiler->javadoc to enforce errors and warnings.
Compiler errors and warnings can be easily reported through continuous build
cheers,
Saurav
I can only recommend to be very, very careful with that. Of course, you may use tools like SONAR, Eclipse Settings and the like to enforce comments.
Buuuuuuuut:
You can easily generate comments (/w Eclipse) and -as you probably
know- generated comment is not use/helpful at all.
In case you add a useful comment and it relies too much on the actual implementation, you also have to maintain it. Whenever the code changes you need to validate if the comment does too. This is often overlooked and creates more confusion then by not having any comment at all. Even though you had a good intention in the first place.
"The Truth Lies In The Code"(tm): You can achieve good to understand and easy maintainable code by working very hard on it. This might help to avoid to need any comment at all. Its not easy (and not always possible), I admit that.
At least "public API" must be documented. That could be a rule of thumb and it seems managable in a large code base.
I would rather spend more time in having good understandable code instead of "forced comments". You may achieve the complete opposite by enforcing it.
Using Sonar/Eclipse Settings to enforce documentation of public API makes sense to me though.
This needs to be implemented at the source control level, not the IDE level.
If you're using git, you can look into git hooks http://git-scm.com/docs/githooks
This will let you write little scripts that will be run when you commit code. You can write a script to check if the commit includes a valid comment. You can also perhaps allow skipping of comments with a "-force" option or something like that.
I would like to disable a read more plugin ( cutof content) in all pages except my main menu pages in joomla
How do I do this
Thanks in advance
I'm not aware of any method that allows for the actual disabling of a plugin for certain pages. Plugins are either on or off, site-wide. This can be seen from the Extensions | Plugin Manager, as well as the SQL database: jos_plugins. With that said, what would be the purpose in disabling a plugin for certain pages? Most plugins, especially those like a "readmore" are typically setup to be activated by a simple code sequence, such as {readmore}path/file.htm{/readmore} and consequently, you can turn the plugin "off" by simply choosing to not use it. Most plugins of that nature provide very little more than essentially "coded access to a CSS class". If you could be more specific on why you need to actually disable the plugin for certain pages, perhaps we'd be better equipped to answer properly.
Depending on the plugin, you could feasibly remove the event trigger that would set the plugin to run, thought it would not be advisable since it would stop that trigger for all plugins and could cause unintended effects.
I am not sure what you mean by "Read more" plugin. You can turn the read more text on and off as a setting in the menu item parameters or in the article itself. Have you tied that?
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.