topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Thursday April 25, 2024, 1:07 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ewemoa [ switch to compact view ]

Pages: prev1 ... 104 105 106 107 108 [109] 110 111 112 113next
2701
Find And Run Robot / Re: suggestion: open plugins folder
« on: November 26, 2008, 05:36 AM »
I wanted something like this as well [1] -- as a work-around I made an alias "pluginaliases" that gives various options:

pluginaliases
1000>>>pluginaliases>->Open Plugins Folder | explorer.exe %FARRDIR%\Plugins>n>List Plugins | restartsearch aplugins>n>Reload Plugins | restartsearch goreload


I have a hotkey that brings up FARR and sets the text to "pluginaliases".

Admittedly, this may not help in locating the specific folder under which FARR is looking for Plugins...


[1] I'd also like an alias for bringing up the Plugin Manager dialog -- may be there is one and I just haven't found it :)

2702
Attached, please find the latest.

Some changes include:

Fubscript/fscript.js:
  • checking for existence of plugin search, trigger, and receive functions before attempting to call them

3 plugins are bundled with this archive:
  • colors
  • Akete
  • Mixer - this is a repackaging of Webgrab

ecaradec, I had a question about some of the code in FSubScript/fscript.js -- specifically the .showSettings() and .settingsChanged() lines that sit outside of the for () {} constructs, but as I was composing this post, I think I figured out that I was confused, so please disregard the comments there :)

2703
You can get it for free at http://www.asamanthinketh.net/ (they just want your email address but they look like good guys). If that's too much for you, Amazon will gladly ship it to you for a few bucks: http://www.amazon.co...-Allen/dp/087516000X

FWIW, I noticed a Wikipedia page for the book and found a couple of links there to free digital versions:

http://www.gutenberg.org/etext/4507
http://www.favourban...u/as_a_man_thinketh/

2704
Some additional notes:

  • parseArgs is described a bit in some of the searches - I think I came across it 8 times (search for 'usage' among the searches)
  • There is at least one search that defines multiple forms - blingo.xml

That's it for the moment -- 100 searches is enough for one session (only 300 to go!), don't you think?  ;)

2705
Post New Requests Here / Re: IDEA: Simple line by line truncator
« on: November 23, 2008, 08:14 AM »
I guess the following may not be that useful but FWIW, I used to do something w/ similar results using the commands kill-rectangle and yank-rectangle in Emacs.

2706
Question 3.2 of the DQSD FAQ seems to have some detailed information regarding forms and how they fit in with creating your own searches.  A portion of 3.2 follows:

  • Take a look at the original HTML form for the search, and create your own HTML form to do the same thing, but where you make all the input fields hidden instead of visible (i.e., change the type to "hidden"). Be sure to be explicit about the "action" of the form (it has to be an absolute URL).
  • Write a JavaScript function that takes one text parameter and assigns values the hidden fields of your form, and then submits it. By convention, if the text parameter is blank, you should open a window into a useful page that helps you launch the search -- typically the home page of the search. If there are multiple fields in the form, then your JavaScript should use a regular expression of some kind to pull apart the single text field to fill in the multiple form fields. The easiest way to do this is with the 'parseArgs' function, which will handle the parsing for optional 'switches' and their values.
  • Paste your new HTML form and your new JavaScript function into its own XML file (SEARCHNAME).xml - copy the bits of xml from an existing search xml file - and include the attribute indicating your JavaScript function name, a short name for the search, a long description, a link to a description of the search engine, your name, and so on. Be sure to follow XML rules - all your attributes need to be quoted, remember the trailing slash in the INPUT tag, etc...

At the end of 3.2, concerning the xml file there is the following:

  • Your search will be callable using the function="..." name. E.g., if function="foo" then you can do the search saying "foo bar". So pick a good short name for your JavaScript function.
  • Every search's NAME attribute will be displayed if the search is put on the menu, so keep it short and descriptive, like a menu item.
  • If you include a LINK attribute, then the link will appear in the ? help box for the search.
  • The DESCRIPTION attribute is also included in the ? help box.
  • The CATEGORY attribute defines the name of the category in which the search appears in the ? help box.
  • The CONTRIBUTOR attribute is for your name, and the EMAIL attribute is for your email address.

A casual browsing of some of the searches have turned up the following regarding pieces of the xml file:

  • name
  • category
  • contributor
  • link
  • email
  • description
  • form
  • script
  • copyright
  • created_by

"copyright" and "created_by" don't appear to serve technical purposes and the rest of the bits seem like they are described at least a bit.

Regarding the dqsd-specific javascript functions, I started making a list of candidates.  I'm not confident about these yet, but FWIW, here's what I've got so far (this was done by manual inspection of various searches):

  • nullArgs
  • parseArgs
  • submitForm
  • setSearchWindowText
  • openSearchWindow

2707
Attached, please find an attempt at recursively searching for fsubscript.js to a limited depth.

Some changes include:

Fubscript/fscript.js:
  • onInit() - local function processFolder(), local variable maxdepth
  • likely more unknown bugs :)

For testing purposes, I put the colors subdirectory inside a subdirectory of the FSubScript directory.

2708
Attached, please find attempt after mouser's corrective suggestions  ;)

Some changes include:

Fubscript/fscript.js:
  • onSearchBegin() - hopefully fixed problems and made clearer
  • fixed and modified types: CLIP=6; ALIASFILE=7;
  • likely more unknown bugs :)

Recursively searching for fsubscript.js to some depth has not been implemented yet.

2709
I hope ecaradec has gotten his hands on a version of FARR that can do ForceResultFilter :)

Attached, please find the latest attempt.

Some changes include:

Fubscript/fscript.js:
  • onSearchBegin() - let me sum up, no, there is too much...Use the source Luke!
  • wrapper function forceResultFilter()

colors/fsubscript.js:
  • More colors
  • Change value for grey
  • Change to arguments of emitResult() in search()

Both:
  • other things I forgot
  • likely more unknown bugs :)

Revision control, anyone?

2710
Living Room / Re: Tech News Weekly: Edition 47
« on: November 22, 2008, 06:40 AM »
Thanks again Ehtyar!

10. I wonder if PayPal will install some kind of automated checking...
23. Bottled water from Mars, anyone?  ;)

2711
Living Room / Re: Gmail launches themes
« on: November 21, 2008, 07:49 AM »
Certainly are easier on the eyes
:Thmbsup:

2712
Find And Run Robot / Re: "Open folder" of a file in the search result?
« on: November 20, 2008, 06:54 AM »
Does the following help at all?

https://www.donation...windowoperations.htm

Note that Control-R can bring up the context menu as well.

2713
Attached is a "sketch" of further ideas -- I think mouser may be the only one with a FARR that can execute the code appropriately (I know I don't have one yet).

Some changes include:

Fubscript/fscript.js:
  • onSearchBegin() requests FARR to 'filteron' based on regular expression matching results -- when regex supplied by plugin

colors/fsubscript.js:
  • Doesn't filter any more

Both:
  • other things I forgot
  • likely more unknown bugs :)

Regarding why search stops -- I don't have a clear memory of the reasons.  I think it might have had something to do with FARR's current behavior for non-FScript plugins, but it's probably best for mouser to answer this question :)

2714
Attached is a further refinement after discussion with mouser.  Check it out...or not  ;)

Some changes include:

Fubscript/fscript.js:
  • Stops searching if there is an exact match for a plugin
  • Defined more postprocessing options
  • Renamed ADDSCORE to ADD_SCORE

colors/fsubscript.js:
  • An additional color -- grey
  • Regular expression handling of sorts
  • In plugins["colors"].search(), emitResult() is called w/ different args -- see source for details

Both:
  • other things I forgot
  • likely more unknown bugs :)

2715
Living Room / Re: Thumb trackball wanted
« on: November 18, 2008, 11:17 PM »
It's true it was expensive -- though I believe I picked it up for less at Amazon -- but I've been a pretty happy user of it.  Perhaps I should try a thumb-based one sometime -- I may not have given one a fair chance (just casual attempts of models on display).

2716
It's a first attempt, but attached, please find an experiment with FSubScript's fscript.js and colors' fsubscript.js.

The idea here is to provide the plain plugin invocation syntax of "name" rather than "fssc +name".

I'm probably missing some important things, but may be the code is worth something ;)


P.S. I have limited screen space so I've reformatted -- hope that isn't a problem.

2717
I've replaced my skeleton functions with those you did. Thanks.

Cool! I hope they work ;)

The querynokeyword would probably a bit different from the farr one. I'll have to remove the whole "fssc +pluginAlias". If you do it I'll integrate it.

In addition to what mouser mentioned earlier in this thread, he gave me some hints on the idea of being able to invoke FSubScript plugins w/o using "fssc +pluginAlias" syntax but rather "pluginAlias" syntax.  I am investigating this a bit and hope to report back with some results on this before too long.

Also the FARR querynokeyword seem broken : It always return the same thing as the queryraw.

I got the feeling querynokeyword seems broken too -- some of my querynokeyword-not-working experience is summarized at:

https://www.donation....msg136530#msg136530

2718
Developer's Corner / Re: Calculus lifesaver
« on: November 17, 2008, 06:51 PM »
I watched the interview (introducing the book and videos) and part of the first lecture (2 hours long!).  Although I kept missing small bits of the audio in the first lecture, what I saw seemed pretty decent to me.  I'm especially interested in the author's coverage of the process of figuring out problems -- perhaps it will hint at Polya's "How to Solve It".

I noticed that the first chapter of the book can be downloaded from the book's website if you want to get a sense of the book first-hand -- though you can also see bits of it (in lower quality) via Amazon's "Look Inside".  The book is pretty big -- over 700 pages...

Thanks for sharing this, Target!

2719
Living Room / Re: Thumb trackball wanted
« on: November 17, 2008, 06:38 PM »
I wish I had a thumb tackball. I tried to use one that had the ball in the center, but I did't like it. I need my scroll wheel.

I thought a trackball with a ball in the center wouldn't work out too -- but I found a Kensington one that has a scroll ring around the ball and although it took a bit of getting used to, I'm happily adjusted to it now :)

http://us.kensington.com/html/2200.html

2720
There might be bugs. There are centainly bugs.

onSearchBegin() in FSubScript/fscript.js
Perhaps the following line:

  plugins.search(querykey, isExplicit, queryraw, modifier, triggermethod);

should be something like:

  plugins.search(querykey, isExplicit, queryraw, querynokeyword, modifier, triggermethod);



2721
I improved the now renamed FSubScript.

As an exercise in reviewing plugin functionality, understanding FSubScript a bit better, and becoming more comfortable w/ gvim, I filled in more of the skeleton functions in fscript.js:

a piece of FSubScript/fscript.js
function setStatusBar(txt) { FARR.setStrValue("statusbar", txt); }
function setSearch(txt) { FARR.setStrValue("setsearch", txt); }
function setSearchNoGo() { FARR.setStrValue("setsearchnogo", txt); }
function stopSearch() { FARR.setStrValue("stopsearch"); }
function hideWindow() { FARR.setStrValue("window.hide"); }
function showWindow() { FARR.setStrValue("window.show"); }
function toggleWindow() { FARR.setStrValue("window.toggle"); }
function setRichEditMode(txt) { FARR.setStrValue("window.richeditmode", txt); }
function setRichEditHeight(height) { FARR.setStrValue("window.richeditheight", height); }
function setRichEditWidth(width) { FARR.setStrValue("window.richeditwidth", width); }
function setShowAllMode() { FARR.setStrValue("setshowallmode"); }
function exit() { FARR.setStrValue("exit"); }
function reportError(txt) { FARR.setStrValue("reporterror", txt); }
function setCliboard() { FARR.setStrValue("clipboard"); }
function pasteClipboardToLastActiveWindow(txt) { FARR.setStrValue("PasteClipboardToLastActiveWindow", txt) }
function displayAlertMessage(txt) { FARR.setStrValue("DisplayAlertMessage", txt); }
function displayAlertMessageNoTimeout(txt) { FARR.setStrValue("DisplayAlertMessageNoTimeout", txt); }
function displayBalloonMessage(txt) { FARR.setStrValue("DisplayBalloonMessage", txt); }
function execWebbrowserEmbededJavascript(txt) { FARR.setStrValue("EmbeddedWb.ExecJavascript", txt); }

function paste(txt) { FARR.setStrValue("launch", "paste " + txt); }
function copyClip(txt) { FARR.setStrValue("launch", "copyclip " + txt); }
function restartSearch(txt) { FARR.setStrValue("launch", "restartsearch " + txt); }
function doSearch(txt) { FARR.setStrValue("launch", "dosearch " + txt); }
function doSearchOnTrigger(txt) { FARR.setStrValue("launch", "dosearchontrigger " + txt); }
// txt: text with \n as newlines
function showMemo(txt) { FARR.setStrValue("launch", "showmemo " + txt); }
function showFile(filename) { FARR.setStrValue("launch", "showfile " + filename); }
function showFileRTF(filename) { FARR.setStrValue("launch", "showfilertf " + filename); }
function showFileHTML(filename) { FARR.setStrValue("launch", "showfilehtml " + filename); }
function showHTML(txt) { FARR.setStrValue("launch", "showhtml " + txt); }
// txt: url
function htmlViewURL(txt) { FARR.setStrValue("launch", "htmlviewurl " + txt); }
// txt: searchedit, mainpanel
function setFocus(txt) { FARR.setStrValue("launch", "setfocus " + txt); }
// txt: list, memo, html, user, spreadsheet
function setViewMode(txt) { FARR.setStrValue("launch", "setviewmode " + txt); }
function pcommand(txt) { FARR.setStrValue("launch", "pcommand " + txt); }
function setSize(minwidth, minheight, maxwidth, maxheight) {
  FARR.setStrValue("launch", "setsize " +
                   minwidth + ", " + minheight + ", " +
                   maxwidth + ", " + maxheight);
}
// XXX: bool: 0 or 1?
function setHTMLSafe(bool) { FARR.setStrValue("launch", "sethtmlsafe " + bool); }
function showPleaseWait(txt) { FARR.setStrValue("launch", "showpleasewait " + txt); }
function hidePleaseWait() { FARR.setStrValue("launch", "hidepleasewait"); }
//function alert(txt) { FARR.setStrValue("launch", "alert " + txt); }
function sleep(ms) { FARR.setStrValue("launch", "sleep " + ms); }


Don't know if they work, but perhaps it will save ecaradec some drudgery  ;)

2722
For your question in the plugin about the settings : One way to create options is to send a autohotkey executable, however you can do it the way you like. You need to send a message WM_USER+1 to the window name FScript/FSubScript. Autohotkey program can do this. However an IE with a registered custom protocol could do it to. UI in javascript is a bit tricky. I think I like the autohotkey solution the more.

Wow, thanks for responding to a question I put in the plugin's source!

At the moment, it seems enough to just use FARR's User Variable support for configuring Akete, but perhaps as time goes on I'll change my mind about this :)

2723
I put together a FSubScript plugin - Akete.

Briefly, this allows one to customize launching of files via FARR.  A user can specify a file-extension -> executable association [1] via FARR's User Variable support.  The archive contains a README.txt with details.


[1] Live free of the registry -- long live portable apps :)

2724
Thanks ecaradec for:

function onProcessTrigger(path, title, groupname, pluginid, thispluginid, score, entrytype, args)

I am having more luck experimenting with file associations being handled by FARR (overriding / ignoring registry-based settings)  :Thmbsup:

2725
IIUC, I had a similar difficulty trying to package a plugin for FARR.

What I ended up doing was to have an initial step of cd-ing in to the folder containing what I wanted to have compressed (as mentioned by SirSmiley) and also to have the resulting file created outside of the folder containing the contents to be compressed.  What follows is a sketch with some details.

If "test" is the name of the folder containing things to compress, the following is the sort of command line that worked for my case (assuming I run the command in the parent folder of "test"):

cd test && 7z.exe a -tzip ..\test.zip -r .\*

To verify the results, I used the Open menu item in the File menu of 7-zip File Manager on the test.zip file -- I also extracted the test.zip file using the "7-zip" -> "Extract Here" menu item from the Windows Explorer context menu successfully.  The version of 7-zip I am using appears to be 4.5.7.

I tried basically what SirSmiley mentioned w/ success too:

c:\test>7za.exe a test.7z -r *

The result was a test.7z file in my C:\test folder -- I also verified its contents using the two methods mentioned above.

Pages: prev1 ... 104 105 106 107 108 [109] 110 111 112 113next