How would one go about adding paging to the NodeJS REPL? I'm building a simple command line app in NodeJS and want to be able to page through output (similar to how the MySQL console lets you page through query results) using less or more as filter programs.
I don't necessarily need the search functionality: just the pausing of the scroll (so I don't have to scroll up to see what's happened) and the ability to cancel the output (so I can quit the output on page 2 of 2000).
Related
I'm refactoring js plugin for chrome.
Its mostly based on jQuery with q and handlebars libraries.
For now there is 30k lines of code (2k in background page).
Is it better to include more logic in background or in content-scripts?
If for example I move most of functions to background page, and call them through chrome.runtime.sendMessage with callbacks.
Currently there are about 5k messages send between bg and content-scripts in one plugin run and it takes about 2 min.
Will moving help performance or will it crash it?
Writing guides in Google Docs and sharing them with other people as read-only is great. However, even when formatting it without the "Print Layout" option (the first toggle option under View menu), every viewer opening the document will see it in Print Layout, i.e. with half-empty pages before each page break. This is very annoying.
Is there any way to default the Print Layout to be switched OFF when a read-only viewer opens a Google Doc? Here are 2 ways for which I'm hoping:
via a URL parameter, so that the link I share determines the document will open with a switched-off Print Layout;
in Google Apps Script, with something like function onOpen(){ DocumentApp.getActiveDocument().setPrintLayout(false); }
(except setPrintLayout() does not seem to exist right now).
I'm mostly interested in the web browser version, and in the mobile app too (though less).
There's a similar question over there (with screenshots).
And there's a discussion dating back when switching off Print Layout in read-only Google Docs was not yet possible (it is, now, though only manually).
Currently I am working on J2ME App and I am facing command issue in j2me.
When I am adding any command on form its coming under options, not coming directly on screen.
Command selCommand = new Command("Select");
This select command is not coming directly on screen, options is coming on screen then click on option command then Select command is coming.
I want Select command on screen instead of option.
High Level GUI coding in JavaME doesn't let you decide how a Command should be displayed.
The same code may display a Command directly on the screen on some devices, but under Options on other devices. So don't have any control of that.
Your best chance is to look into priorities. By setting a high priority on your Command, you may be lucky that it displays directly on the screen instead of under Options. It is not something you should count on though, since it's not required by the specification, but I suspect at least many devices would do that.
J2ME doesn't let you allow to add commands on Screen it will come in menu but we can set priority to command so that they can be visible in left or right side.
even if you want to add command on Screen you have to use buttons.
Container containerbtn;
Button btnsel = new Button("Select");
containerbtn.addComponent(btnsel );
this.addComponent(containerbtn);
I've an xpages in which i set some fields to filter documents, with an autocomplete in one of these.
At the end, a button make a pdf based on this query fields (onClick action), and the pdf is presented to be saved or open.
Ad this point, autocomplete doesn't work anymore, i need to reload the xpage to make autocomplete active again, but i loose all other field values set in previous search.
Is it possible to keep autocomplete alive?
My guess is that you serve up an PDF directly from the page and no in a separate window. This will make the XPage to stall and will wait for a timeout of some kind.
I usually on the pdf generation button add this on a js timeout.
XSP.allowSubmit()
That usually works in the cases I have encountered.
Problem solved!
Just set the type ahead mode to Partial instead of Full
Thanks everyone
I write automated tests for a website. One of the tests needs to press Ctrl+S and type some letters to save a webpage including CSS/JS. The test should require Firefox to have window focus for those several seconds to be able to type the filename and click "Save" (currently XDoTool is used for pressing keys and clicking the mouse).
Sometimes I run the tests on my computer. I don't want to occasionally type something or change the window focus while the page is being saved, so I want to prohibit changing focus for those several seconds when those mouse clicks/key presses are running.
It's not possible to do it at the Webdriver level (a tool that I use for controlling the browser), so I think I should do it at the OS level. Can I prohibit the user from changing window focus or typing anything for a period of time? It may look like:
prohibit user from typing keys/change window focus
save page
allow user to type/change window focus
I guess that another way to achieve the desired effect would be to run Firefox and your automated tests on a nested X server (xf86-video-nested/Xephyr/Xnest).
$ Xnest :1
$ export DISPLAY=:1.0
$ firefox http://something/to/test &
$ your-test-script
Since the nested X server has it's own idea of the focused window, moving the focus on your desktop shouldn't affect it.
(If you don't actually need to see the test progressing, you could use a dummy X server (xf86-video-dummy/Xvfb/Xfake) instead)