I have 3 sections within a form. Is it possible to open a specific section using Lotus Script?
If the answer is no, then are there any tricks to do that?
No simple way, exists: #formula and LotusScript don't give finer grain than collapse expand all sections.
The only way is to send keys (controlling the keyboard by using DLL as explain by Richard in the bellow remark). You make a goto field to the field (not in the section) before the section and then send the number of "below key" needed to navigate to the section, then send "+" (which expand the section).
You can get creative with the hide when's. Can you be a little more specific about what you're wanting?
Related
I have a question about Ultimate Special Offers plugin. Has anybody used it?
The problem is that this plugin sets the table with discounts in a special place where it wants. In my case, it shows up under the "add to cart" button. But I want it to appear above the button. How can I regulate the place where the table shows up?
You have two choices. One is to dig into your theme and move the table yourself. If you right-click the element displaying the table while having your browser console open, you will spot where it is in the HTML that makes up your page. Now click the Add to cart button, and see where it is. Memorize the name of the button, and now look for that in your product.liquid page. Chances are, the plugin itself has some liquid, so you can cut it out of the page, and move it the before the add to cart button in the liquid.
If all that seems like a mountain to climb, just ask the makers of the plugin to do it for you. It is a simple task for them, and should take them a minute to do. If they choose to ignore you, I would call them out as unreliable, and try a different plugin, from a company that will help you with your simple task.
I've been assigned to a software development task for a excel like editor. Basically the editor is working on 2-dimensional data, should have the basic editing features such as add/remove rows/columns, edit cells, undo redo etc.
Please point me some good design patterns for this type of job, Thanks!
Rather than trying to figure out all design patterns for a project in advance, wait until you run into a specific design issue and think about patterns that address that issue.
That being said, the features you list here do call out the likelyhood that you'll be wanting to use the Command pattern, so that each possible operation (add column, add row, remove column, edit cell, etc.) is supported by a command object, and enabling undo/redo for your commands with additional help from the Memento pattern.
Depends on context of use.
You could check out some common usage guidelines for tables here: http://www.oracle.com/webfolder/ux/middleware/richclient/index.html?/webfolder/ux/middleware/richclient/guidelines5/tblInteraction.html
Very often users want an Excel-like UX for table data manipulation, including actual export to Excel. You can provide for edit, sort, add row, enlarge, etc. If the user is editing in a table try that guideline. It's intended for enterprise users, so customize accordingly.
HTH
I'm trying to create a toolbar button that inserts a footer (including some buttons) into the current mail.
As far as I know, theres no way to create and modify buttons directly with Lotus Formula, so I'm trying to copy/paste from another document. I can't use a mail template because I need the text to be inserted in replies.
This is what I have assembled from online examples:
#PostedCommand([FileOpenDatabase]; "SERVER" : "mailbox.nsf" ;
"($All)" ; "" ; 1 ; 1 ) ;
#PostedCommand([OpenDocument] ; "" ; "34884517EED80C33C125A999005301D4") ;
#PostedCommand([EditDocument]) ;
#PostedCommand([EditGotoField] ; "Body" ) ;
#PostedCommand([EditSelectAll]) ;
#PostedCommand([EditCopy]) ;
#PostedCommand([FileCloseWindow]) ;
#PostedCommand([FileCloseWindow]) ;
#PostedCommand([EditPaste])
This works inconsistently, depending on what I am looking at when pressing the button.
Sometimes it opens a search box with the actual text of the mail pasted in it. It does seem to close the new mail.
I'm especially confused because many commands don't take any arguments, eg FileCloseWindow. How do I control the "context" of the commands or check for success?
It feels like doing automation with SendKeys - fire off a chain of commands and hope that nothing unexpected happens. Of course, I am a total noob with Lotus Formula, so I may be doing this totally wrong. Any help is appreciated.
You may want to use Alan Lepofsky's free "Paste Information" application.
The Notes database "Paste Information" serves as the repository for the content you wish to reuse. Move the cursor to the position where you want to insert the text, click on the "Paste Information" Toolbar icon and then choose the document (aka. text) to insert.
http://www.alanlepofsky.net/alepofsky/alanblog.nsf/dx/paste-information-application
There really isn't a good solution for this using formulas. You'll be stuck in the SendKey-like world you describe.
If you can modify the mail template even a little, you could add a form to it that includes your text and buttons, instead of grabbing it from a central database. Then you could automate creating a new document based on that form, copying the contents, etc. That could help the automation work consistently and perhaps more quickly since it would be getting the resource from within its own database.
You could also then add a shared action button to all the mail forms (memo, reply, etc) that runs this formula, which would make distribution a lot easier.
I'm afraid even with LotusScript, this is an impossible task because you can't insert rich text into a UI document ( or at least not in the version I am running ).
Have two questions.
Make the search filter form non modal.
Allow searching by pressing enter key instead of having to press the Find button.
thanks.
sachin,
Your question seems to be more of a statement, but if you're looking for various options for jqgrid, take a look at:
http://www.trirand.com/jqgrid/jqgrid.html#
New in Version 3.5 > Integrated Search Toolbar
This allows you to interactively search and it respects the Enter key.
However, you lose operators... but I suppose you could modify the code that's given to add something similar back in (or bundle your operator in with the text....ie, user enters "> 400" rather than "400", but this poses security risks)
I was wondering if it was ever ok not to have a submit button (Ok, Go or Search for example) near a search box in Web pages.
I know that hitting enter is much faster and that it will perform the search.
However, is it an accepted convention for the average non tech savvy user or only for the tech community?
For example, the search box here at stackoverflow doesn't have a submit button, but I don't think anyone is complaining (and I sure don't).
On the other hand, someone suggested using Google as an example: would people notice if the buttons were removed?
I just started reading Don't Make Me Think by Steve Krug and he mentions that every search box should have something that tells me I can click on it to launch the search.
Your thoughts?
Why you should have a button:
Not everyone knows they can hit
enter, so you are leaving some less
savvy people out in the cold.
Some devices like phones and consoles may not have a way to submit without a button. The PC based browser is still dominant but don't assume it is the only way people access your site.
You may not have a button if (both conditions must be satisfied):
Your audience is tech savvy (as on SO)
You provide a visual cue that the search box actually is a search box
By adding text inside it mentioning it should be used to search
By adding an icon inside the box
Generally I would think that hitting enter is a shortcut to submit rather than the primary means.
I think it depends on your target market. If you are StackOverflow it's not too hard too think they know how to use a browser (using a back button on a browser to navigate is a similair design convention) and pressing Enter = submit for search.
However if your target market is say mechanics (no offence to mechanics) that don't use a browser/computer often then look at how Google does it (and they target the broadest scope) - they have a button to submit.
There is a middle ground you could look at, which is have a water mark like StackOverflow which tells users "Click here, type in search values and press enter to search" - or something like that (hopefully shorter) where you actually catering for users of all levels.
Whether or not a button is required depends on the audience. Here are issues to consider:
Technically oriented users may not need a button and will usually not have to think about hitting enter to submit a search request.
Conversely non-technical people may not even know it is possible to hit enter to submit a search request. So no amount of thinking might work for them.
There may be technology limitations that require a button. If you expect your audience to be browsing your form from a platform that does not provide an implicit way to submit a search request then you may need to provide an explicit button.
So essentially you need to know your audiences and determine where the edge cases lie and how critical they are. Using SO as an example, it is directed at technical users so an explicit button probably isn't required. However for a site like google where you need to be accessible to every single user using every possible platform, a clear explicit search button is a must.
"Don't Make Me Think" - so gimme a button.
There will always be someone using the application for the first time; don't make them think either. And your screen shouldn't be so fussy that it is impossible to fit the button in comfortably - that would indicate a different set of problems.
I think for a non-tech person some sort of submit button is needed. Think about people who don't use computers very much. They often click all of the buttons needed instead of hitting enter because they don't realize enter does the same thing. My opinion...if it isn't for tech guys only then it should be as simple as possible.
It depends on your audience. Steve's audience is everybody. Majority of which are so far from IT you'd need a telescope to see them. If your auditory is a single user, you might skip all clues: button (with or w/o names), in-box label.
For my own login window I leave two fields: no labels, no buttons, no javascript to tell you which one is which. But that's not a public project.
A while ago there was an article on Smashing Magazine about this.
There were some alternatives like a looking glass or another icon, but basically there is always a button, or something which represents it.
Having a button makes it clearer that the text field is a search field. Merely having the text field itself indicate this in its contents is unsufficient.