I have created a form using the "Create Form" option in MediaWiki with few text areas to fill in by the user. I wanted to enable the option of save and continue wherein a user can save the form after filling it partially, and then continue adding/editing the information.
I used the Extension:Checkpoint to fulfill the same. The extension provides the option when creating/editing a normal page in mediawiki, but not when
Adding new information in a form or
editing old form using "Edit with Form" option
Searched a lot on ways to be able to use the same, but failed. Also tried using the standard input tag: save and continue, but it just creates text, and no button.
Is there a way to get the functionality to work (did I miss something), or implement it in another way?
Thanks in advance.
The Save and Continue option as a matter of fact can be easily implemented without the use of the Extension:Checkpoint.
The standart input tag is defined within mediawiki which provides the user to provide different input options at the end of a page or a form.
The following different tag values are allowed:
"save" (for the "Save page" button)
"preview" (for the "Show preview" button)
"save and continue" (for the "Save and continue" button - this lets users
save the page without leaving the form)
"changes" (for the "Show changes" button)
"summary" (for the "Summary" text field)
"minor edit" (for the "This is a minor edit" checkbox)
"watch" (for the "Watch this page" checkbox)
"cancel" (for the "Cancel" link)
"run query" (for the "Run query" button in query forms)
The save and continue option can be easily used as follows:
{{{standard input|save and continue}}}
at the end of the page where you want the option.
It works as follows:
the button is not activated (appears as normal text) unless you type or change something in the form or page. As soon as you make even a slight change, the button is activated, to function just as every other button.
hence it might look as if the tag didn't work when it actually does. :)
PS: I still can't understand why the extension doesn't work on forms when it was designed keeping in mind the option of 'editing forms'.
Related
This should be a really simple thing that for some reason I can get to work.
I have an MS Word document which has a drop-down field. If I double-click it - a dialog comes up to add or remove things from the drop-down field.
I just need to be able to get out of this mode so that the drop-down field behaves like it should from a user's point-of-view rather than from a design point-of-view. Basically I just need it to display the items rather than a dialog to allow me to add and remove the items.
According to what I've read, it looks like I should be able to do this by going to Developer, and then toggling the Design Mode button. This doesn't work; whether the Design Mode button is on or off I still can't get it to just act like a drop-down.
Thanks much
It sounds like you're using a legacy form field dropdown. For those to operate as a dropdown, you must protect the document for forms:
On the Developer tab, click on Restrict Editing. The Restrict Editing task pane opens.
In the task pane, check the box beside Allow only this type of editing in the document.
In the next dropdown, choose Filling in forms.
Click on Yes, Start Enforcing Protection.
Protected forms don't allow text to be edited in protected sections. In those areas, only form fields allow you to enter text. If that's too restrictive, look into Content Controls, which don't require document protection.
I have a Browsing carousel in my Action that opens a new page. From that page, I want to give the user an option to either continue on the website or to close the website and go back to the Action.
If they select the option to go back - how can I send them back to the Action?
You can't "go back" to the Action in the same way as if you clicked on a back button in the browser.
However, you can create a link on the page that you're showing the user that will re-start the Action or re-start it with a particular "deep linked" Intent. If you maintain the state of the user when they leave your Action, you can restore that state when they return, but that is up to you to manage.
To create a link to start the Action go to your Action console, select the "Actions" navigation on the left, and then the right arrow for the Intent that you want to be able to link to.
Towards the bottom of the screen that comes up, you may need to click on the "Links" header to expand that section, and then turn the switch on for "Would you like to enable a URL for this Action?"
The section will expand to prompt you for a Link Title (which is required, but not really used for anything) and will show you an HTML code snippet with the link. You are allowed to change this link however you want, but you must use a link - you can't do something clever like try to redirect to that page.
I am trying to get my head around GWT Activities and Places. And I am not sure how to implement a specific functionnality.
Let's assume here that I am also using MVP, and that my Activities are my Presenters.
Say I have an activity (let's call it activity A) (and its corresponding view) that is displaying a list of customers. The user can click on a "create customer" button in the view.
What I want to do is this: I want a "create customer" dialog to pop up on top of the current activity when the user clicks on the button. I also want all logic related to said dialog to be separated, so it can be reused later.
For example, the same dialog could be reused in a "create invoice" activity. So the user could click a similar "create customer" button in the "create invoice" activity, and be presented with the same dialog as used earlier.
Now, if I understand it correctly, I do not want to goTo() a new place, since it would terminate the current activity "list customers" or "create invoice".
I have thought about defining a "CreateCustomerPresenter" and a "CreateCustomerDialog" (which would be the corresponding view", and having my "list customers"/"create invoice" Activities (reminder: they also are my Presenters) extend the "CreateCustomerPresenter", but I don't know if it would be a wise idea...
What is the recommended way of reusing logic+view associated with a dialog in the context of an activity?
There are several valid approaches, but the one I usually prefer is this: Not to treat dialogs as places (activities) at all.
Reasoning: A place means, that you can reach it via bookmarks/browser history. Let's say I'm on the customer list, and I click "edit customer", a dialog opens. Do I want to "go back" to the list when I click the browser back button? And will the dialog open again when I click the browser forward button? I doubt it, and believe that a user wants to use the browser buttons to go back/forward entire 'pages' within the app (i.e. a concept that feels to the user like a page), but not open/close dialogs within the page.
I have done exactly this very recently.
The approach I took was to create an activity/view in the usual way for the content of the dialog. To launch, create the activity/view to embed in the dialog - I termed this a sub activity. Create the modal dialog and then call start on the sub-activity passing in the dialog content as the panel. In the main activity I then redirected the mayStop, stop etc to the sub-activity.
The tricky part was handling the dialog closing and passing control back to the main activity. I ended up adding a listener to the dialog and firing events on the event bus which were picked up my main activity. I am not 100% happy with this but it does work.
I have not used it but I think that GWTP supports this and other ways of creating sub-activities out-of-the box.
I have a Microsoft Access form which I use for entering client information:
First name
Last name
etc..
My problem is when I tab away from the Access Form to view the information which needs to be entered, the focus is lost in access. I need to click the form with the mouse to regain the focus.
This is very annoying!
Any help here?
AS far as I know, the focus of an access object is lost when you clic anything outside the object... that includes forms.
I can suggest you two ways of tacling this:
Use a control (combo box or list box) inside your form, so you can view the data you need.
Use a "pop up" form: you can create a form with the data you need, and a button inside your main form that opens this "pop up" form. You can specify in VBA if you want your form to open as a pop-up... if I remeber correctly, is something like this:
...
docmd.openform("frmYourForm",,,acDialog)
...
Hope this helps you
I am trying to develop a quiz application using LWUIT resource editor and am having great difficulty.
I have created two Forms 'GUI1' and 'GUI2' .
GUI1 displays the following:
A question(in the form of a TextField)
5 RadioButtons belonging to the same group
A Button which says 'OK'
GUI2 displays the following:
A TextField
A Button to go back to GUI1
Now the problem is:
Initially GUI1 is displayed. When the user chooses a RadioButton , I wish to know which RadioButton was selected. If that RadioButton was indeed the correct answer, then when the user clicks on the 'OK' Button on GUI1, I wish to display the text 'correct' in the TextField on GUI2 and then display the GUI2.
If the user chose the wrong answer, then I wish to display the text "Wrong" in the TextField on GUI2 and then display the GUI2.
How can this be done with resource editor? I am very foxed. Please help.
I wish to refer to the TextField on GUI2 when I am currently on GUI1. How can this be done with resource editor? Writing a manual code for all this would be very time consuming.
Ok I will try to explain the best I can.
When you design the first Form GUI1 the five RadioButtons must be in the same group. I don't know how to do that in the resource editor (I think there is a field called ButtonGroup in the RadioButton, but I can't remeber). What I would do is take the five RadioButton by code in the before method of GUI1 and add them to a ButtonGroup element.
With ButtonGroup you can know which element is selected using ButtonGroup.setSelectedIndex(). When you press the Button take this value and act as appropriate to the situation.
If you don't understand anything please tell me and I will try to help you.
Is not a hard thing to do. There must be a way to do it with the Resoruce editor but at the moment I don´t know how.
As Shai mentioned, the best thing to do is to use listeners to set the "state" of the buttons on clicking them and when you move to the next form you just retrieve the state of the previous text field.
Manual code may actually be faster for you, do most of the UI in the resource editor and transfer to a form that is written manually. That way you have full control over your objects and transfer back into the GUI builder form when needed.