I have a qualtrics survey in 2 languages (English/Spanish), but the language option is appearing on all the pages. Is there a way to only have the language option on the first page so that participants don’t switch back and forth from languages? I have checked the qualtrics support groups but so far no luck. They provide some type of Javascript or code but it hasn’t worked so far.
Related
I'm a volunteer for a not-for-profit project committed to conceiving a "way" to easy (considering the user audience not used to browse websites) and make attractive the registration of a new user on the home page Joomla website 3.9.
After a web search and a look in the Joomla section of the extensions on the related, I've just found that one of the possible options that meet my requirements is a free extension that enables the user to signup with a social account (Twitter, Facebook, etc.): SLogin.
I've found that the category under which I may look for a suitable extension is: Tutorial or website tour. But all of the ones I find on the web are not free.
If I was in the shoes of a user not familiar with registering a new account on a website, maybe I'd expect to find a guided procedure with popup windows or more than one webpage with plenty of information on any single step involved in the user creation.
I wonder if there is a template or extension (free) or any other option (not custom developed) that may do that job; I'm open to any suggestions based on the requirements above.
Try BreezingForms - https://extensions.joomla.org/extension/breezing-forms/
I think it allows you (even in the free version) to create custom forms, as complex as you need (multi-page, etc.) and then port them into Joomla! user creation.
You're gonna need to hunt around on their forums/support to find out how to do this exactly because it's been a long time since I've used BreezingForms.
This post on their forum has a user asking the same question and I think they answer it conclusively: https://crosstec.org/en/forums/3-breezingforms-for-joomla/123224-how-to-make-login-and-registration-forms-with-breezingforms-pro.html
Good luck and have fun!
In addition to the options already mentioned, I've evaluated and finally selected a Joomla template with a slideshow extension on top that repeatedly displays the required number of slides to show how to register and/or login.
One of those slides will feature two buttons that will open a modal window to register or log in.
I am just finishing my latest app but I am straggling with the About page implementation.
How should I create About Dialog or About Page in Windows Phone?
I do not want to use just a plain page with text, because it doesn't look professional. Is there a standard way of doing this? An About page/dialog provided within the framework, for example?
There are many ways you can do this. The best would be if you could download a few of the popular free apps to see how exactly have they implemented it, to get a few ideas.
I prefer to go in one of the following 2 directions:
Custom styled page, that includes icons, developer details, some legal details (which controls did you use, under which licenses etc.) You can even use a pivot page, and then split the details about you, and legal details (and any other details) to multiple pivot items.
Use a popup from Coding4Fun toolkit. Scroll down for a sample of how it looks.
I've had this idea bouncing around in my head, and I decided I'm going to do it and learn a little in the process.
Okay, if you don't mind, I'm going to pitch my website project to you.
It is based on collaboration, so I thought MediaWiki would be the best place to start, but I don't know where to go from here. I also checked out SemanticMediaWiki and SemanticForms, but it doesn't seem to do what I want.
My project is a site revolving around Multiple Choice Adventures. There are already sites that do this, like http://editthis.info/choose_your_own_adventure/Main_Page but I aim to have it entirely user friendly.
On that site, users must employ wiki markup effectively and set up the links manually. That's functional and effective, but I want it to be totally user friendly.
I want the links and content submission to be a fluid process with no worrying about wiki markup.
Here's what I want:
A user creates a top level page. A new story. (Possibly a category?) He titles it "Knights and Princesses".
He is asked to fill in the story text. He writes, "You are a handsome knight with a brand new sword. A dragon is swooping towards you."
He saves the page.
The page now contains the title, the story text, and a link/button saying "Add a new story branch".
A second user comes along. He reads this page, and clicks "Add a new story branch".
He is prompted to fill in a form. Absolutely no technical markup or manual editing.
He fills in his chosen title "Run Away".
He fills in his story text "The dragon chases you as you flee, but you concentrate on running as fast as you can. You notice a rabbit hopping along side you."
He saves the page.
Two things happen.
1: The previous page is automatically updated. Above the link "Add a new story branch" a new link appears, titled "Run Away". This new button links to the new page.
2: The new page is published with the title, the story text, and also a link/button saying "Add a new story branch".
Anyone can come along, click that button, write a new page, and the links will be added seamlessly. No need for messing with editing the page and adding wiki markup or URLs.
In addition, I hope to have the ability to categorize stories by adult content,and have a method to police and filter that.
I hope to have the ability for the original authors of a new story to define what the permissions will be, i.e. "Authorized users only", "anyone can edit", "only registered users".
I hope to have the ability for only original authors to lock certain pages from being edited.
I hope to have the ability for authors to make stories private for a select group of users.
I hope to enable users to edit story text without seeing nasty code and markup.
Am I dreaming here, or is this possible with MediaWiki? I am only experienced in Joomla and MediaWiki.
Do I need to learn a web framework? (Rails, Django, Pylons, etc) Where do I start? Are there solutions that are already geared toward my project?
Thanks for the advice!
This definitely sounds doable. Did you know that one of the original iterations of Mahalo.com was built on mediawiki? Mediawiki is very flexible software, and with a little bit of technical know-how and time you will have no problem accomplishing this.
In fact, I bet if you made it an open source project others would help you.
If you want heavy access control (access control lists, extra privileges for the creator of the pages etc.) then MediaWiki is not a good match.
If you want easy-to-use WYSIWYG editing which does not hinder collaboration, then it is again not a good match (though it is coming along, and I am not sure there is a good match currently).
For the automatic creation of links, I think Semantic MediaWiki is the right tool. You need to define a precedes-follows relationship, use semantic forms or something similar to create new pages which reference the current page as predecessor, and list the names of following pages on the bottom of each page.
I was looking at the Firefox Add-ons Manager UI (pictured below) and really liked the expandable list used to show settings or properties for each add-on.
Firefox Add-ons Manager http://uploads.tech-buzz.net/Firefox3Beta3ComingonMonday_859/get_addons.png
I liked it enough to want to include something similar in one of my applications. The problem is, I don't know, exactly what the control is called (it doesn't seem to be "expandable list"), nor do I know if there is an implementation available for use in my own application (so I wouldn't have to reinvent the wheel.)
This isn't the first time that I've seen some cool piece of UI and wanted to incorporate it into something I'm working on, but have had no idea if I would have to design it from scratch. So I generally end up reworking my UI to use standard UI widgets to save time.
This got me thinking, is there some place that has a catalog of a bunch of UI widgets with names and what platforms/languages they are implemented for/in?
UPDATE
Turns out this control is called a Rich List Box, and it seems to only be implemented in XUL.
To answer your question, no, there isn't a universal catalog anywhere, though MSDN is as good a place as any to find definitions of most common UI elements.
The specific widget you ask about is generally called an accordian (wikipedia)
I am a software developer working with different ERPs based on different platforms. Java is one of them. I've decided to learn Eclipse RCP. I am trying to understand the basics of Eclipse RCP regarding its views and editors concept.
Working with other platforms I don't care how to make a form in GUI. All the forms in my application can show data say from a DB or save this data back into the DB. And I don't care if a form shows the list of entities or a detailed info about an entity.
Here, in Eclipse RCP, I see that a form can reside in a view or in an editor. What is the difference between them? I would like to hear these differences from a business point of view, please. Or maybe these differences can be explained only in terms like "editor cannot have its own toolbar"? I would like to understand the purposes or common usages as a user not as a developer.
Thank you.
The wiki has a goof FAQ on this topic
There is generally only one instance of a given view per workbench page, but there can be several instances of the same type of editor.
Editors can appear in only one region of the page, whereas views can be moved to any part of the page and minimized as fast views.
Editors can be in a dirty state, meaning that their contents are unsaved and will be lost if the editor is closed without saving.
Views have a local toolbar, whereas editors contribute buttons to the global toolbar.
Editors can be associated with a file name or an extension, and this association can be changed by users.
Some advanced use are mentioned
here, about the ability to reuse an editor for several types of file.
or there, for linking to an editor
Views can have a different organization than editor: see fast view.
In broad terms:
Use editors for the main editable "documents".
Document lifecycle (open/dirty/save/close) fits neatly with editors.
Use all sorts of rich controls, hyperlinks, etc. It doesn't have to be a text editor.
Use views to provide optional supplementary analysis/manipulation of the document in the current editor.
Use views for other (often cross-document) navigation, analysis, search results, etc.