I'm used to Wikipedia's Wiki, and now that I'm using TWiki at work I really miss the ability to discuss a page outside the page but still on TWiki.
Have I missed a button or link somewhere? Is this possible?
In MediaWiki (Wikipedia and the like), every page has a discussion page associated with it. This is not the case in TWiki, at least not by default. The administrator can built something similar, but as a user, all you can do is manually create and link discussion topics.
I think you can reuse the template code in http://foswiki.org/Extensions/TalkContrib on foswiki - I've not used TWiki in years, but foswiki is a compatible fork.
Sven
Related
If correct, Google introduced Google's NoCaptcha ReCaptcha on december 3th. More information can be found on their official blog.
After reading their story, they refer to their good old ReCaptcha site. Seemingly this has been renewed. So I created an account and started testing. However, I already stumble on two questions that don't seem to be answered on their own site. Google-ing results in old and mostly useless information about the "old" ReCaptcha module.
The thing is not responsive. This seems weird to me. I know I can make it responsive or use a framework or something to do so. But all the HTML / CSS is generated by the plugin itself. Is there some universal solution for this, or Am I missing something?
Sometimes clicking the checkbox is all that's needed, but often I still get the old misformed pictures that are still hard to read. In other words, sometimes it looks like nothing has changed. Is this normal, or is this thing not fully released yet?
Does anyone know or recommend a method for a simple way to convert a site into a different language. I just need the site to change from spanish to english and vice versa, but the site will load in spanish first. Perhaps a plugin is available? Most of the content is dynamic and the site is being developed with Concrete5 CMS. Any ideas would be appreciated. Thank you.
I think you need to install an add-on for this. Check out Internationalization, it's free: http://www.concrete5.org/marketplace/addons/internationalization/
Here is a YouTube video showing it in action, so you can quickly see if it's what you had in mind: https://www.youtube.com/watch?v=Hd936iaDLqw&feature=player_embedded
You need some automatic translation tool (since you said your content is dynamic).There are many in internet, you just have to search for "Automatic translation API".
I recommend you using the Google Translate one.
I downloaded and started playing with CEF, but there doesn't seem to be any docs for it. Not even a working wiki… Am I missing something?
Most of the documentation is in CEF's header files. The binary distribution comes with docs generated from those files. It's well documented in terms of amount of content written, but I had a lot of trouble while learning to use it. The project's Wiki page contains a lot of useful content as does the cefclient sample program.
The CEF3 API documentation can be found at http://magpcss.org/ceforum/apidocs3/
and CEF1 API docuemntation can be found at http://magpcss.org/ceforum/apidocs/. These two links can be found on the Chromium Embedded framework (CEF) wiki home page: https://bitbucket.org/chromiumembedded/cef/wiki/Home
You didn't provide a link to CEF, so I Googled it, and found the project's Web site, which features a prominent link to their wiki.
The wiki has several pages, but the first one that jumped out at me is the General Usage page that shows how to create a "fully functional embedded browser window using CEF".
So I'm not sure where you were looking, but yes, it looks like you were missing something (grin). The wiki documentation is right there.
How can I quickly produce a report of a website in the format:
Page Name.
- Links within the page
Page Name.
- Links within the page
Any programming or scripting language will do.
Although I prefer a solution on Windows, we have all of: Windows, Mac and Linux platforms available in the office.
Just looking for a way to do it without much fanfare.
There might be tools able to do this for you, but it isn't all that hard to put together yourself. One possible solution would be to...
Use wget (can be found for Windows) to download all HTML files, and
use some xpath tool or grep with regexps to get the title and the links from the pages.
///Jens
There are loads of link analysers that will do exactly that. Here's the first I found in Google.
For something a little more interesting, Don Syme did a great F# demo in which he wrote a really simple asynch URL processing class. I can't find the exact link, but here's something similar from an F# MVP. You would need to adapt it to pull out links, and recursively follow them if you want nesting.
As background, I currently develop for a university, and we have problems with departments demanding "web 2.0 content" and accessibility requirements.
How do really big sites that are JavaScript based deal with 508 Compliance? Some sites degrade, and others require enabling JavaScript. How much impact does one decision have versus the other?
Also, in a realistic sense, how much development time should be devoted the accessible versions of sites versus the "main" versions?
I'm a blind developer and find it possible to use many Web 2.0 sites - this is most certainly possible.
Firstly, I strongly advise against making a separae accessible site, regardless of how many people advise you to do this. This is bad practice and will end up being more work, even if it initialy seems simpler.
Next, try to use progressive enhancement (particularly if this is a new site). Code the site without any Javascript; it's not just accessibility which benefits. Then, in your OnLoad() go through and attach Click events to the anchor tags; this way if you have Javascript you'll see the Ajax version, otherwise you will have a full page refresh and see another HTML page.
Luckily, there is a new standard, WAI-Aria (www.w3.org/WAI/intro/aria.php) which makes this much simpler. You attach attributes to HTML tags to identify the semantics of an Ajax control, for example. The only problem with Aria is that it only works with newer screen readers and web browsers. The university may well require the site be accessible to people running older software.
I'm a screen reader user and often use Javascript enabled sites. Javascript is not an accessibility issue, the way it is used can be. For example if the site uses javascript that requires the use of a mouse and doesn't have keyboard alternatives it will not be 508 compliant. An example of a site that uses Javascript and is accessible is stackoverflow.com. The only feature that isn't accessible is the ability to determine if you have accepted an answer to a question. I would take a look at the links in Annie's answer. All the blind college students I know use a fairly modern browser with Javascript enabled, Lynx is no longer popular in the blind community. If you want to try using a screen reader a good open source one for windows can be found at
http://www.nvda-project.org/
and it works well with firefox. If you want to try using the web with out Javascript install the Noscript addin.
Sites don't have to disable JavaScript to be accessible. Many sites use ARIA roles to work better with screen readers. There's a giant list of articles on accessible AJAX applications here. You could try something like AxsJAX.