I am currently building a Google form to help gauge a competency of our staff members. While building the Google forms you’re given several options when creating your question type, 9 to be exact. (text, paragraph text, multiple-choice, checkboxes, choose from a list, scale, grid, date and time I’m a definite novice when it comes to scripting with a simple understanding of different coding languages which helps me sift through the scripts so please bear with me.
So here’s my question, how would I add a paragraph text to the existing multiple-choice script in the Google form and is it possible?
Here’s a quick test question example we would like to apply to current Google form script:
Question: Do you have experience in handling cash?
Multiple-choice question: Yes or no? (Please explain your answer) <--- this is where I would like to add a script that would allow me to also include a paragraph text just below the multiple question.
I know I can organically create the entire test by adding landing pages as an option after choices made but this means creating a new page for every single question throughout the test with my 40 questions this means building 40 questions with 40 page landings would sound like a massive pain in the ass.
This may be an easy question for somebody out there but I’m sure it’s not going to be for most as I believe Google locks down the default scripting in new forms. My only hope is that the existing Google form that I create essentially belongs to us so re-scripting to add a paragraph text box may not be that big of a deal after all.
Per this discussion, there is currently no way to modify the action of Google Forms controls:
Google FormApp Customisation
If you have the time to get to grips with the UiApp, then you should probably do so, since (as you have discovered) Google Forms are extremely limited in terms of what can be achieved with them.
Additionally, Google handles the data transactions via a background service which makes any adjustments post-contruction liable to cause significant problems with your process. For example, adding a new control 1/2 way down your form will insert a new column at the end of the responses spreadsheet, and attempting to move that will create a 'ghost' column which can't be removed. Similar issues will be encountered with removing rows etc.
If the system you are working on is anything more than trivial, Google Forms are not the way to go. But if you feel it can do what you need, then Bryan P's comment from yesterday is probably the way to go :)
Related
I have a task to complete at work that I already completed once. The issue is Outlook and HTML templates. I created a large table that will be used as a pricing table for our customers but the issue is people don't know how to use html even when I dummy proof it with step by step instructions. I have attached the exact layout I need to produce to get some help with advice on what solution will be best for me to use. I have proposed the LiveCycle Designer by Adobe but I feel I am getting a snobby response from even suggesting this. PLEASE HELP! I have don't this 4 times using Acrobat Pro and the client hates it. I also redid it as an HTML template with Outlook specific code so it doesn't get mangled if it is forwarded to others.
Ok I need a reputation of 10 to post a picture so I will describe it the best I can. Let me know if I can send the image to anyone willing to help?
The table has an image header then Title and report date with a input text field next to it. Under this begins the table is has 12 columns and 29 rows. Each cell needs to be expandable in case the clients types in more characters and the form expands to show all the text in each cell. I would like everything to adjust to this.
I told them to use a Excel document but they said no. Then I suggested to just have each cell be larger so there is no need to have them be expandable. They shot that down as well due to the look of it. I really don't think I can pull this off without Adobe's Livecycle Designer.
So over the past couple of weeks I've been working on trying to create a way of using google forms as a kind of editable pdf. The idea is to have it be used as a group work order wherein the various people involved fill out the information pertaining to them as they acquire it. Now I know this isn't exactly what forms are designed to do, but it seems to mostly be working.
The way I have it right now is that the initial user creates the initial response, which triggers a script on the form submission, that sends out an editable link via email to all of the contributors to the form. Then whenever a contributor has information to add, they merely have to follow the link, make the change, submit the form and another email gets sent off alerting everyone of the edit.
The only problem with the system, however, comes when two users are filling out the edit link at the same time. At that point the collision resolution (or potentially a lack of collision resolution) for the edit link appears to kick in. The first user will submit and the form gets updated correctly, but once the second user submits, their changes override the changes of the first user. Looking at this from a user standpoint this would be highly confusing. Their change would appear to have been registered correctly, but in reality have been overwritten and discarded.
Now the ideal solution would be that the only changes that are overridden by the second user are those that actually have values in them. I.e. if user one answers question A, and user two answers question B, and both answer question C, only question C is actually overridden, instead of A and C.
I initially thought that perhaps I could compare the two form responses and find some way of doing the collision detection on my own, but there seems to be no way to edit the actual form responses, to change the data on the edit link to match. (Changing the spreadsheet values does not actually have any impact on the edit link itself)
So my question really boils down to is there a way to get this collision detection to work the way I am intending it to? And if there isn't any way to do that, what would be the best way to trigger off a warning email when a collision does happen so that the users would at least know that something went wrong?
I need a client side HTML form builder I can implement into my project to give my users to ability to add/edit form design and field properties as desired. I am using Telerik Kendo just to provide some background and I have a basic form, however if the user needs additional fields, or even additional labels I want them to be able to edit their own forms.
I found Jot Forms and dozens more (http://www.jotform.com) but that does not work for me. All fields are in a vertical fashion. I need the users to be able to drop a field, move it around where ever they need.
So in the end, I need a form builder I can use in my project where users can create and use alternate forms. They need to be able to drag, drop the form element anywhere on the page and of course edit the properties as necessary.
If there is anything out there I would really appreciate some help on this.
I appreciate the constructive feedback. I have ventured into discovering what it would take to build one of my own.
I found most form builders already done out there that I demoed would build a beautiful form. As long as your desired form is simple. As I tested I found complex forms would require additional coding on the back end. Something most users don't know how to do, and something that would be a support nightmare.
I so far have found that the JQuery UI draggable, droppable, etc. features will provide me with ample tools do build my own. So far I have a proof of concept where I can drag items onto a workspace. The nice thing is that I can incorporate HTML code specific to my Javascript framework, Kendo. We use it at work and it has nearly everything including drag and drop. Just not functional in a way where I could see building a form builder.
I am learning all of this as I go, so thank you for commenting and please forgive me if I sound inexperienced. I am, but I am not afraid and in fact love to get my hands dirty with new stuff.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
IS there a way to test CSS and HTML? For instance: sometimes some of the notices get affected by some CSS changes. I don't want to be testing all the notices by hand every time I do a change.
Thanks
It's very difficult to automate testing of layout. But it's not too difficult to drastically cut down the time and effort involved so that you can do it manually, but very quickly.
You could try Blink Testing.
I've heard of it used for websites like this.
Write a script that walks through your website, visiting as many pages as you can think of.
At each page, take a screen shot.
Combine all the screen shots into a 'movie' with just a second or two for each screenshot.
Now, each day you can 'play' the movie and watch it for any issues.
You could even extend bcarlso's approach but replace the MD5 check with a visual check. Each page gets displayed for 1 second - first the known good, then the new. You could alternate them a few times so any obvious errors will appear as a flicker.
A website with hundreds of pages can be checked like this in a matter of a few minutes. You may not think this will provide enough time to find issues, but it is remarkably efficient in identifying obvious problems with your website.
Any pages that have major layout problems will pop out at you as they don't match the same pattern as all the other pages.
I am assuming that the issue that you're trying to test would be that the CSS changed in some incompatible way with the layout causing, for example, text to be truncated or otherwise visually "broken". If that's the case, then I would say that there isn't a good way to test the aesthetics of a page at this time. One of the primary benefits of TDD and CI is quick feedback so that you know something is broken before it gets to production. Not knowing much context around your environment and how those changes make it into your app it's hard to suggest solutions, but here is an example of a potential non-traditional option:
Put a commit hook into your repository that let's everyone on the team know via an e-mail when someone changes some CSS. Preferably with a diff of the CSS. This would give the team a heads up to keep an eye out for layout problems.
We started an experiment to use WATIR to walk some of the main screens in the app and take a picture using ImageMagik (essentially a screenshot) and store it in a "Last Known Good" folder. Every day re-run the script on a clean install of the app and data and place the images in a "Current" folder. At the end of each run use an MD5 to compare the images and alert on changes. Have the QA team review a list of flagged screenshots and if the change was acceptable (for example, a field was added as part of a feature) then copy "Current" to "Last Known Good". Unfortunately we didn't get our experiment finished so I don't know if it will work well. I'm concerned about the brittleness of screenshots as "assertions".
Hope that helps!
I believe Selenium can test your frontends for you. Specifically for browser compatibility testing, take a look at Selenium RC.
If you'd simply like to make sure you're contents are in the right contents etc. etc. you can create a simple testing suite that's going to be making GET requests to your website. When you receive all the content you can run it through a validation template like xslt. Well formed html will usually be able to be matched against xslt's or xsd's. It is not ideal but if you're only worried about the structure of your website and not the styling you'll be able to achieve it this way.
A change to CSS should not affect the behaviour of a page, only it's appearance, so I'm not sure that Selenium would be much help for this.
I'm going to take a guess that you are trying to avoid problems such as elements being misplaced on the page so that they are not readable. If so, you would probably need some kind of OCR-based tool, but I don't know one off-hand to suggest.
However, it may be to better to invest your effort in preventing this kind of problem in the first place. If your layout is easily broken, maybe you need to refactor your CSS to something simpler.
I'm a non-developer building a simple Access 2003 database for an NGO that works in developing countries. I would like to provide in-app help (what certain fields mean, for example) in a number of forms and on the switchboard. I'm not sure about the best way to do this - not just on a technical standpoint but to increase user-friendliness. The users are usually using MS Access for the very fist time, and have only basic computer use knowledge.
I don't want to cram the forms with help text, so I'm thinking of adding little question mark buttons that pop up a separate form with just help text. Is that wise?
I've also noticed a Help Context ID property, but it looks complicated (I'm looking for something as simple as possible to implement, so that the help text can be edited as easily as possible by others in the future). I think this is where I'd start if this were the way to go: http://support.microsoft.com/?kbid=209843
This may need to be translated, etc, so again, the simpler the better.
Thanks!
I've built such a system using tables and forms in the FE. You can get an idea by reviewing some of the screen shots at http://www.granitefleet.com/ScreenShots/index.htm I only created general help describing processes where something on a setup form can affect this form. So the user will know where to ge to change something around.
If you haven't built your forms yet, put that information in the table design, using each field's Description. That will propagate through your forms, and will be displayed on the Status Bar whenever a user click in that field.
If your forms are already done, use the [Status Bar Text] and/or the [ControlTip Text] property of your controls.
Just train your users or write once that they should read the Status bar if they need more explanation.
KISS (keep it simple and simple)
Great question. I think the real solution to reducing the amount of work that you need to do is to work really hard on having a simple, clean UI. In the real world there are very few people who have the patience or inclination to read the manual or search the contextual help even in the face of being stuck.
I know this is slightly off topic from the question but if you look at this website for example it keeps the number of things you can do on anyone 'screen' down to the minimum and everything has a tool tip (ControlTip Text in msaccess). Even if site this was in Japanese, I thin i could navigate around it fairly easily and that is because of its simplicity. (I couldn't answer any questions though :P)
Jakob Neilsen has a great site on usability
" I think the real solution to reducing the amount of work that you need to do is to work really hard on having a simple, clean UI. In the
real world there are very few people who have the patience or
inclination to read the man*emphasized text*ual or search the
contextual help even in the face of being stuck.*
Regarding this, it really depends on the application. It is overly simplistic to assume that every application can have all the information it needs to be operated just by having a simple clean UI, especially if in the name of being simple, there are alot of useful features that are not included. In certain complex applications, people will simply need to have patience and read the information available or they will waste a lot of time guessing. It is better to have have information at the press of a button than have them asking for it once they figured out that they are wasting time figuring it out with no help. I agree that many apps are way more complicated than they need to be.