tag:blogger.com,1999:blog-89438762429767063392024-02-07T09:18:37.610-08:00toraware dot comUnknownnoreply@blogger.comBlogger64125tag:blogger.com,1999:blog-8943876242976706339.post-31987437447330071962020-07-29T21:22:00.001-07:002020-07-29T21:23:03.306-07:00Toraware's App Now Accessible for an Android InstallTwo days ago my toraware app got published in Google's Play Store.<br />
(I needed a Private Policy for my site because children can use it too.)<br />
<br />
For some strange reason, inside the Play Store, upon searching for "toraware", scores of Chinese apps appear in the results well before mine. My app appear somewhere near the bottom of that very long list.<br />
<br />
To get around that problem, I added an image link on my website, in the form of an icon at the bottom right, and now the user can link to the Play Store -- with my app already "found" for him, to have it installed. There's no need for the user to do a search for my app because the my link's API finds the app with pinpoint precision, bringing the user one click away from an install!<br />
<br />
The new Home Page of http://toraware.com today, sporting its new icon link, is shown below:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjppkU0t_LPtPbWi7NHhVvDtGLz4gdiXbt45xLaPSB6SClOU6pvp_rlBq9sQ93NdOFyD5jpjsT-TwwJg_819JP6Tfb2D1pDKDGljdPMYVM9NGspxl0HZhTbUCyykdTHdVEKXyC-I4LA8Qw/s1600/tw+7%253A29%253A20.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1141" data-original-width="765" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjppkU0t_LPtPbWi7NHhVvDtGLz4gdiXbt45xLaPSB6SClOU6pvp_rlBq9sQ93NdOFyD5jpjsT-TwwJg_819JP6Tfb2D1pDKDGljdPMYVM9NGspxl0HZhTbUCyykdTHdVEKXyC-I4LA8Qw/s640/tw+7%253A29%253A20.png" width="428" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<span style="font-size: x-small;">P.S. </span><br />
<span style="font-size: x-small;">The iPhone version will not be pursued. For one thing, it requires a $100 yearly fee. And this website, as well as its app, are free and generate no income. Google's Play Store charges a one-time $25 fee. I think Apple should pay the developers, and not that developers should pay Apple!</span>Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-8943876242976706339.post-50680958507956283982020-07-14T08:48:00.001-07:002020-07-15T16:07:42.150-07:00A Birthday Present from Hashem, 21 Tammuz 5780By divine providence, I managed to upload my <b><span style="color: #990000;">toraware</span></b> app to <b><u>Google Play</u></b> store. It happens to be my birthday, the 21st of Tammuz. It's now in queue, "up for review".<br />
<br />
The Chassidic dictum comes to mind, "<i>Think good; Will be good!</i>"<br />
<br />
Exhibit A:<br />
Source: Transaction with Google Play's Console.<br />
<div class="separator" style="clear: both; text-align: center;">
</div>
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7qsP-CiH4Pp0aEfkRExu5V6fWU-2c40wC_riQcyxa2r7J4z721UXFm-rnzCC_GRdKRQlgggWcPr_L0KpS8VgOyKx5YqCUPiG-JANFwxg-ncDrZQKb58LuXaXvtYCexZIhrvZYF2WiOzY/s1600/google+play+consloe.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="573" data-original-width="1600" height="141" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg7qsP-CiH4Pp0aEfkRExu5V6fWU-2c40wC_riQcyxa2r7J4z721UXFm-rnzCC_GRdKRQlgggWcPr_L0KpS8VgOyKx5YqCUPiG-JANFwxg-ncDrZQKb58LuXaXvtYCexZIhrvZYF2WiOzY/s400/google+play+consloe.png" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><i>It took some hours, but this submission began on my birthday!</i></td></tr>
</tbody></table>
<br />
By divine providence, after an exchange of emails with a responder to one of my posted questions, as I surf the internet for solutions, this contact suddenly points me to a site - his own site - and sure enough, a few days later, I was well on my way to bringing my goal to fruition. More like a dream than a goal. Because I've been for many years coding and hoping this app would end up portable on a handheld device.<br />
<br />
So it happened, that I succeeded following Android's path, after failing to fulfil the Apple Store's pretzel-loop discombobulate requirements. So, Boruch Hashem, and it all happened within a week, and toraware shall be available for download from the <b>Google Play </b>store, where it ought to be catalogued under "REFERENCE" (or perhaps "BOOKS and REFERENCE")<br />
<br />
By the way, the product that helped out immensely (by divine providence!) is by a zealous fellow called George Henne, who runs <a href="https://volt.build/about/">https://volt.build/about/</a>. His web service, which runs from a "cloud": zips your project, uploads to VoltBuilder, and downloads executables for Android or iOS. So here I shout out a <i>thank you</i> to George! (I had visited 3 or 4 other sites promising to do the same; I croaked with each; But his runs like a smooth engine.)Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-25302189516979813122020-03-31T09:25:00.000-07:002020-07-13T02:19:52.054-07:00Thank G-d, Toraware's App is Finally Born!<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIOdM_kPpgtiJSFTbTPgq4dNu9KA4QlfNTvMoKBpzK2niBtrHhNKGOJkWcU5GDtXNMlhYJGfwnAXDhyh78YaUF4PfbpnH8MwzFLbODAcpE3VIInKNMjkkBSkrdiI6FfNbvzmtKM9eCCpM/s1600/TW+APP+image.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="430" data-original-width="661" height="207" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIOdM_kPpgtiJSFTbTPgq4dNu9KA4QlfNTvMoKBpzK2niBtrHhNKGOJkWcU5GDtXNMlhYJGfwnAXDhyh78YaUF4PfbpnH8MwzFLbODAcpE3VIInKNMjkkBSkrdiI6FfNbvzmtKM9eCCpM/s320/TW+APP+image.png" width="320" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<br />
Thank God, that which I started out planning, several years ago, has finally come to fruition. From the start I meant to create code that I could "stuff" into a handheld gadget. That aimed-for gadget then became the smartphone. And since my design always held that end-goal in sight, it made the final metamorphosis of my website code into an app rather easy to accomplish. The image above is the face of my new app!<br />
<br />
It would have been impractical or burdensome to transform my website version into an app because most of its methods are not of practical use. Only its first two search methods have real preacticality for everday use. So I stripped away the impractical and remain with the <b>Find a Word</b> and <b>Find a Phrase</b> methods.<br />
<br />
Those other methods on the website I had added in the course of time just in case somebody has use for these eccentric searches.<br />
<br />
Any learner of Torah would find the Find a Word and Find a Phrase methods extremely handy. There are so many times this app finds relevance in everyday experience. Until today I use my own app almost every day.<br />
<br />
This app is now suitable for deployment onto an Android. Soon enough it may also be suitable for an iPhone, iPad or a Windows mobile gadget.<br />
<br />
It turns out that in the end I did not even need to learn the native languages used by Apple and Android, because other technologies came along to let me bypass these steep learning curves. To master these would have years to learn. As the chasidic saying goes, "think good and it'll therefore turn out good!" I began my project in 2015 or 2016, to be sure, even as Xcode and Android Studio lingered forebodingly on the horizon. Just as I was about 100% completed with my program's code, thank G-d, other easier deployable solutions suddenly came along and showed promise, like PhoneGap, like Chrome developer, the PWA (Progressive Web Application) route, and software products that turned Javascript code into native languages. All of this thankfully vindicated my original choice, namely, <b>to use the browser platform</b> for my code.<br />
<br />
Actually, just now, my program can be downloaded for an Android device. It requires the user to go to a specific site and therefrom download my app. So, I must now still give instructions to people on how to download the code. But soon enough - which I'm presently working on - is to get the software into the app STORES and then my instructions to everbody can be to tell them which store to go to to get it.<br />
<br />
Because apps require responsible handling of distributed code, which requires that a secure server handle the distribution, this move was something I could not yet afford (I live on a small pension). But just then the GitHub website came along and provided me with a website on which to deploy my site securely, security being a key issue for PWA, <b>for free</b>.<br />
<br />
So, for now, here's how you, the reader, can now get this free app.<br />
Using Chrome, type in <b><span style="color: blue;">https://toraware.github.io</span></b>, and<br />
then "<b><span style="color: red;">Add to Home Screen</span></b>".<br />
<br />
Did it ever occur to you "Where in Tora is the first mention of a particular word"?<br />
Or, "How many times does such a word repeat itself in Tanach"? Or, instead of a word, maybe you want information on a set of words or phrase.<br />
<br />
Toraware is a small, free, handy Torah tool with which you can instantly search through Tanach. In 2 or 3 clicks you can find any word or phrase, instantly. If you can do a "Goggle Search", you can easily learn this adept Torah tool to full advantage. And especially for learners of Torah, this reference tool is perfect for you.<br />
<br />
Hope you'll try it, and if you have suggestions or comments, I'd appreciate your feedback.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-7943597925227189372019-07-24T09:25:00.002-07:002020-03-31T08:29:02.259-07:00Consecutive Possukim that Begin with Vov<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_lPodPyVR3MyMj-4BHMnCPv4EFabmw9T-iWmM04_P14tAPlvb5zRVbODK5bUqD-fDxIZzqrZBtpIxKrT6cmiVHohsgQNDbeRYI0zlE0inK086AOukRnjzrvC30WHw4gKSUSuJ-y4ejo4/s1600/Screen+Shot+2019-07-24+at+12.17.26+PM.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="408" data-original-width="1559" height="103" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh_lPodPyVR3MyMj-4BHMnCPv4EFabmw9T-iWmM04_P14tAPlvb5zRVbODK5bUqD-fDxIZzqrZBtpIxKrT6cmiVHohsgQNDbeRYI0zlE0inK086AOukRnjzrvC30WHw4gKSUSuJ-y4ejo4/s400/Screen+Shot+2019-07-24+at+12.17.26+PM.png" width="400" /></a></div>
<br />
Here's an interesting tidbit:<br />
<br />
How many possukim that begin with the letter Vov can you find <u>in succession</u> in Torah?<br />
<br />
Answer: 52<br />
<br />
And how many .. in all of Tanach:<br />
<br />
Answer: 71 (see below)<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYypOM1p0kZnSvFipeaaBNUlWst14LXa6a9Zd6ogWyOJfnjYLQWDpEEMO0-bpUe1o1xKySqlMmcIapyI-OzFiN6nQKXJcKCZAS_TgZFQLVhUp7hzNHma7tbnVvVwXLAG32DwQuV_mqmCU/s1600/Screen+Shot+2019-07-24+at+12.30.13+PM.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="369" data-original-width="1600" height="91" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYypOM1p0kZnSvFipeaaBNUlWst14LXa6a9Zd6ogWyOJfnjYLQWDpEEMO0-bpUe1o1xKySqlMmcIapyI-OzFiN6nQKXJcKCZAS_TgZFQLVhUp7hzNHma7tbnVvVwXLAG32DwQuV_mqmCU/s400/Screen+Shot+2019-07-24+at+12.30.13+PM.png" width="400" /></a></div>
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-55044382391884414052019-07-23T06:37:00.000-07:002019-07-24T09:26:30.576-07:00Version 55 Combines 4 Methods into 2Until now, version 54's Home Page showed 8 methods in total, occupying 8 lines.<br />
<br />
But if more methods were contemplated, the list would become too long to neatly fit on the Home Page.<br />
<br />
So I came up with the idea to combine Roshe Teivot and Sofei Teivot into one method, displacing their choice to the Options Page instead. Similarly, I combined the Roshei Possukim and Sofei Possukim methods into one method, the choice between them being shifted to the Options Page as a choice.<br />
<br />
I thereby saved two lines on Home Page and, in fact, render the program and its display more economical.<br />
<br />
Here now are the new views entailed in these changes:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjH7j3_FGUutDxbmUs3ymOCdzZZ9e2XrrebMvtggZFXx_MwJgnDkgdgF8FO7IFEw8WKzdVrvCAODRreAIdKz0cqLZ1BL9qWOAplU4KhdVfb2JpKrcqKriBmlvxhqQFmguRJeA2fAI_6F-E/s1600/Screen+Shot+2019-07-23+at+2.24.11+AM.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="878" data-original-width="989" height="284" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjH7j3_FGUutDxbmUs3ymOCdzZZ9e2XrrebMvtggZFXx_MwJgnDkgdgF8FO7IFEw8WKzdVrvCAODRreAIdKz0cqLZ1BL9qWOAplU4KhdVfb2JpKrcqKriBmlvxhqQFmguRJeA2fAI_6F-E/s320/Screen+Shot+2019-07-23+at+2.24.11+AM.png" width="320" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMeLwHU8CE17Ncd2mpQXPBnMhf27ZHJbTAtwlNChjiVVFTZ8oCj1FWTzZIJZHmNOPxtQQbZCi65UgLIrBXBhCwXonPTSI4PfDpMwe3dWxcQZcZc0qZTwM7nWAGkQy1bbCnAL4YgaYcitM/s1600/Screen+Shot+2019-07-23+at+2.24.20+AM.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="638" data-original-width="986" height="129" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMeLwHU8CE17Ncd2mpQXPBnMhf27ZHJbTAtwlNChjiVVFTZ8oCj1FWTzZIJZHmNOPxtQQbZCi65UgLIrBXBhCwXonPTSI4PfDpMwe3dWxcQZcZc0qZTwM7nWAGkQy1bbCnAL4YgaYcitM/s200/Screen+Shot+2019-07-23+at+2.24.20+AM.png" width="200" /></a></div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJ2mQV4aJG0LNSAzps1gE0ePZvrOFvp00Sk6Jy9W_t386fhqcLJvt8e_kctRhz86tQH7RXp-p3bk0CmXu6gPFWTfgi5gbTcNi0eo9bHGg5DrNaDwUnjmIdBrc-cizjDOKWlqQqMoxSqbU/s1600/Screen+Shot+2019-07-23+at+2.24.27+AM.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="647" data-original-width="990" height="130" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJ2mQV4aJG0LNSAzps1gE0ePZvrOFvp00Sk6Jy9W_t386fhqcLJvt8e_kctRhz86tQH7RXp-p3bk0CmXu6gPFWTfgi5gbTcNi0eo9bHGg5DrNaDwUnjmIdBrc-cizjDOKWlqQqMoxSqbU/s200/Screen+Shot+2019-07-23+at+2.24.27+AM.png" width="200" /></a><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhMsxsp_avvQ4mQZ_5a4ABV5Gv2hHpYM2V9kYvOkQwC7y8eqPRdg2lEEnxJINTy58DMogPAktvOGN31RCW53rPeSRzJGrykqYAYvVWaf_43kgr_QcrNCj7gUfqwKQM6Z0lu9Pq87uZap6w/s1600/Screen+Shot+2019-07-23+at+2.24.39+AM.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="609" data-original-width="989" height="123" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhMsxsp_avvQ4mQZ_5a4ABV5Gv2hHpYM2V9kYvOkQwC7y8eqPRdg2lEEnxJINTy58DMogPAktvOGN31RCW53rPeSRzJGrykqYAYvVWaf_43kgr_QcrNCj7gUfqwKQM6Z0lu9Pq87uZap6w/s200/Screen+Shot+2019-07-23+at+2.24.39+AM.png" width="200" /></a></div>
<br />
<br />
<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-2156991469156880052019-01-29T20:18:00.000-08:002019-07-04T14:32:50.572-07:00A Significant Step Towards Creating an APPThe next version (54) of toraware was needed to convert toraware.com's website to run as a mobile app.<br />
<br />
The main obstacle had been one of the options for the gematria method where I allow the user to choose between keyboard textual input or numerical input.<br />
<br />
Although from the very beginning of my development I foresaw adapting my website to be suitable for an app, as you can see from the site's navigation paradigm, I did not foresee that this option to display for use of the keyboard would get in the way. Because deploying the site as is would have the site's keyboard and the smartphone's keyboard both be on display the same time.<br />
<br />
In other words, I had created a pop-up keyboard feature that would be intrusive to the user of a mobile gadget when his screen pops up a 2nd keyboard, besides his usual mode of keyboard entry. So I had codeo my way out of this problem.<br />
<br />
(The two images below demonstrate that troublesome 3rd option still existing in version 53, one that I originally introduced when it wasn't very common to have Hebrew language input readily available on the casual user's computer screen. It's the one that reads, "How will you enter the value?")<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: left; margin-right: 1em; text-align: left;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj3pb71Xue872RRchgL-sHoNB3k91ezyllfqHsRA32BG9J3aiSt7DMXUW3ZKJGNPJ-gbtmPnzzZAdsc7FstsiFa46fpNuwGNzrKgds9cidF5C82vEtyfzDLq-sMdyomzOPcUVm_Dg3YHmw/s1600/gmOPT1.png" imageanchor="1" style="clear: left; display: inline; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="2" data-original-height="636" data-original-width="710" height="178" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj3pb71Xue872RRchgL-sHoNB3k91ezyllfqHsRA32BG9J3aiSt7DMXUW3ZKJGNPJ-gbtmPnzzZAdsc7FstsiFa46fpNuwGNzrKgds9cidF5C82vEtyfzDLq-sMdyomzOPcUVm_Dg3YHmw/s200/gmOPT1.png" width="200" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><b><i>User can enter a number directly</i></b></td></tr>
</tbody></table>
<table cellpadding="0" cellspacing="0" class="tr-caption-container" style="float: right; margin-left: 1em; text-align: right;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgepjQXvNiGlM-vyAzMeVKZMRGNRzXWyQ2xtZs686SaiSYa3GLBhjgCxOPlcZ64612l0dJvw9LCFUdTaU_P0OQPJEJ_rqI9W7l6Fl_2LK26MH5Qqpj-rrb93rm3MQe4bZ5HuXNPkd9iGWM/s1600/gmOPT2.png" imageanchor="1" style="clear: right; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="2" data-original-height="850" data-original-width="708" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgepjQXvNiGlM-vyAzMeVKZMRGNRzXWyQ2xtZs686SaiSYa3GLBhjgCxOPlcZ64612l0dJvw9LCFUdTaU_P0OQPJEJ_rqI9W7l6Fl_2LK26MH5Qqpj-rrb93rm3MQe4bZ5HuXNPkd9iGWM/s200/gmOPT2.png" width="166" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><b><i>Keyboard pops up on this option</i></b></td></tr>
</tbody></table>
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
In effect, I had coded myself into a design dilemma. But then I realized how to easily remedy the situation. I could simply suppress all keyboard display on my part, leaving the user with only his own gadget's keyboard for entry, and all I had to do was identify - inside the program's code itself, <b>whether the input was numeric or textual</b>. Problem solved with some change of code, is all.<br />
<br />
Here's how the new Options Page for the Gematria Method looks like now. <b>Note how the 3rd set of options on this page has been bypassed</b>.<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGGPsA-4aZZVWGxjBMaH1Ny62n0XpgKnQfDs7s_yNP2pz1qeDQON9ZVzmch0ubH5HDu1nI5IVYSQGkv5CFx_0I6SMW2Ucl0PTqCmr7Z5Dx9gYUDNjY_XSs1i-us49uxpVF5PVaC8ADD6w/s1600/gmOPT3.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="2" data-original-height="572" data-original-width="716" height="255" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGGPsA-4aZZVWGxjBMaH1Ny62n0XpgKnQfDs7s_yNP2pz1qeDQON9ZVzmch0ubH5HDu1nI5IVYSQGkv5CFx_0I6SMW2Ucl0PTqCmr7Z5Dx9gYUDNjY_XSs1i-us49uxpVF5PVaC8ADD6w/s320/gmOPT3.png" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><b><i>User can now enter EITHER text OR a number in the same field</i></b></td></tr>
</tbody></table>
With this significant change in place, app creation will probably be rather simple.<br />
<br />
These changes, in fact, relieved the size of the download by more than 20K bytes.<br />
<br />
Inasmuch as this new version is to expedite navigation to a working app, the previous version remains deployed as the version in production.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-61115886670255589402018-11-29T08:15:00.002-08:002018-11-29T08:44:28.136-08:0010 Ways to Search for a Word in TanachHere's a shot of the Options Page in the toraware website, after making the choice to "<b>Find a Word</b>" on its Home Page. <br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipzSxOx8BQgDUmIuzwNM9_Vx39121krlEmTZtm7I8dbWGwL-zG96S2avEfNHqWCCXjbb5horohCT0r4s7fk4xayfUQ0FP7sfsVQ6dAImg4i1xfi5YpE2m1mf-6VMLEmQX0wRHyBhUgkFU/s1600/optionsFindWrd.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="894" data-original-width="726" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEipzSxOx8BQgDUmIuzwNM9_Vx39121krlEmTZtm7I8dbWGwL-zG96S2avEfNHqWCCXjbb5horohCT0r4s7fk4xayfUQ0FP7sfsVQ6dAImg4i1xfi5YpE2m1mf-6VMLEmQX0wRHyBhUgkFU/s320/optionsFindWrd.png" width="260" /></a></div>
<br />
Look how many ways you can search for a word in Tanach at toraware.com: One subset of options has two options while the other subset offers 5 options, so altogether you have 10 combinations to search with. Not that you'd use them all, but they're there in case you need them.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-90778406445661072102018-11-21T00:03:00.000-08:002018-11-28T17:15:50.942-08:00A Speedy Way to Explore TorahHow often do you want to know, on a moment's notice, where a word, or verb, first appears in Torah? Or, is there such a name found in Torah at all? Or how many times does a phrase or word exist in all of Torah or Tanach?<br />
<br />
Sure you can do a search and find your answer on the internet, but that’s still a rather burdensome task. That is, at best, you can still find that word, phrase or verb after a few minutes of surfing and clicking. <br />
<br />
There are plenty of sites with such facilities to navigate through, but you’ll still spend way too long – so you’d never even try to satisfy your momentary curiosity because the delay isn’t worth it. Even a few minutes when your doing something else, like cooking or eating, can be too troublesome so you let your spontaneous curiosity waste away.<br />
<br />
But that’s because you don’t know of the <i>Toraware</i> app that gives you rather immediately in the palm of your hand the answer to your sudden urge to know or explore or validate.<br />
<br />
In two clicks, the first to open the app from its Home Icon, and the second to click on “Find a Word” or on “Find a Phrase”, and you’re ready to type in the letters formed in your mind, and a 3rd click then brings you immediate visual results. Three clicks is all it takes in most cases.<br />
<br />
With the use of only two buttons, and typing the word you're thinking of, in a matter of seconds, you get immediate results. Each click on the “GO” button can scan through all of Tanach in a second, or two seconds, and display the list of results.<br />
<br />
By default, that’s the way it works. But each search method (and there are 10) also sports a different set of options, so you can, if you want, come up with unique ways to find what you’re looking for.<br />
<br />
For instance: Suppose you want to know the number of times Moshe is mentioned in Torah.<br />
<br />
(As a side note, names are easy to catch in Hebrew text in that they always are either mentioned by themselves, with no extra attached letters, or the attached letters always are placed in front of the name. That makes it easy to program a search that focuses on the suffixes of words.)<br />
<br />
So you use the method “Find a Word” (1st click). On the next page, the Options Page, the best option to choose would be: “ENDS with my letters” (2nd click). Now type in the 3 letters משה, and hit the “Go” button (3rd click). Every single word in Torah (the default search range is already set from בראשית to זאת הברכה) that has as its last 3 letters the letters you typed in (“משה”) immediately appears in a list before you (the Results Page). The number of such “hits” is 721.<br />
<br />
Now, not all these hits are good hits. For example, many in the list include the irrelevant word “חמשה”, because this word too ends in those 3 letters. So you have to be clever with use of this tool, to devise a way to narrow in on your answer.<br />
<br />
So let’s now search how many times the letters “ חמשה” are found. Then we can subtract this number from 721. So you hit the “Back” button; The options you selected previously remain as is, so all you do now is type in the word “חמשה” and press “Go”. You get 72 hits. So now we know that from the 721 results we have 72 to take away, leaving now 649 alleged times Moshe is mentioned. You’re left with all significant hits, such as:<br />
משה<br />
במשה<br />
למשה<br />
ומשה<br />
ובמשה<br />
etc., all of which are mentions of משה.<br />
<br />
Besides being clever, however, you also have to be lucky, lucky to have learned Torah. I learned this the hard way, unaware of two such mentions in Torah, by once publishing a faulty blog post; I had missed these two words. But I now know of the two times these same 3 letters have a different meaning, so the real answer is 647. There are two false positives among the results list, which whittles it down from 721 to 649, and then to 647. In Shmot 12:4 it means “less than one calf”, and in Devarim 15: 2 it means “creditor”. Of course these two words are pronounced differently in Torah but the <i>Toraware</i> tool doesn't inspect pronunciations.<br />
<br />
This search can be further explored, if the range is set to all of Tanach (just extend the Range on the opening Home Page, which defaults to the Torah limits). Now the 3-letter search yields 920 hits. Let’s subtract how many times the insignificant ending “חמשה” is found, That’s 150. Thus we get 920 – 150 = 770. Don’t forget two of these we know are false positives, so our final total becomes 768! Let’s not forget that in Tanach there may be other words besides חמשה that might throw us off, but personally I doubt it.<br />
<br />
P.S. I wrote about this previously, over <a href="https://hezbos.blogspot.com/2014/01/correction-number-of-mentions-of-moses.html" target="_blank"><b>here</b></a>, although back then the <i>Toraware</i> tool hadn’t been as useful as it has become presently, in its 54th version.<br />
<br />
P.S. Ever wonder how many times Jerusalem is expressly mentioned in Torah, or in Tanach? I discuss that <a href="https://torawaredotcom.blogspot.com/2018/03/how-many-times-does-jerusalem-appear-in.html" target="_blank"><b>here</b></a>.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-51580045934419880522018-11-18T19:03:00.000-08:002019-02-06T13:52:00.871-08:00Found a Bug in the New Options of the "Find a Word" MethodSuppose you seek the letters בח, and the program comes across the word במזבח.<br />
<br />
My logic was: If the Bais yields a hit, as it does, on the 1st Bais in במזבח,<br />
then I'll search for the letter ח next.<br />
<br />
If these letters are grouped together, then the "BOUND" qualification is true. But here, because the first ב and the ח are not grouped together, I get a false result -- because there's another ב in the word that does have a ח bound to it, which I fail to detect.<br />
<br />
I'm back at the drawing board and must resort to deploying the 49th version until I resolve this bug.<br />
<br />
<b><span style="color: #990000; font-size: x-large;">UPDATE:</span></b> (11/20/18):<br />
Redid the code (more modular and less complicated) and now, thank G-d, it's flawless. Reinstalled as <u>Version 53</u>.<br />
<br />
The Options Page of the "Find a Word" method is now, again, like this:<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhdQMg2TdFp8x8zosKtEgAUKpumYqHhlUtgV7TpJfByB9ypzFjnb3z2sprLASbTnb-SJNMzXj5AMarz8O_r1rkveH6b_I29uZpHGl48CSg_PKe28Hn1v5XetBGw2V48tkzxbAQCcZhn7UU/s1600/new+options.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="908" data-original-width="724" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhdQMg2TdFp8x8zosKtEgAUKpumYqHhlUtgV7TpJfByB9ypzFjnb3z2sprLASbTnb-SJNMzXj5AMarz8O_r1rkveH6b_I29uZpHGl48CSg_PKe28Hn1v5XetBGw2V48tkzxbAQCcZhn7UU/s320/new+options.png" width="255" /></a></div>
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-71864456711259163532018-10-23T14:23:00.001-07:002018-11-21T19:53:52.410-08:00Some Torah NumerologyHere's an interesting numerlogy: If you begin reading the 1<sup>st</sup> chapter of Genesis (in the original<br />
Hebrew language) and find the first T (ת in Hebrew). The first occurrence of this letter is the last letter of the very first word (בראשית). Then skip the next 49 letters to read the 50<sup>th</sup> letter as vav (ו). You continue this way two more times, every 50<sup>th</sup> letter, to obtain the word Torah, “תורה,” the Hebrew word for the first five books of the Bible (the Pentateuch).<br />
<br />
(You'll find too, that from that 1<sup>st</sup> Tav in Genesis, were you to skip therefrom over 132 letters, i.e, every 133<sup>rd</sup> letter therefrom, you'd also arrive at the same word, Torah. I only checked up to the skip value of 250; So there may well be more such, but larger, equidistant-skip findings.)<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjz2_0_qPHGsd-ctR8tTLvkLexF8F_RncFt8jF5S7_AOcF6D-czdUe73IRSuL1I-OszqeqNkHlUogDbCPFMNh8FCcMxBpNPjtNgPOpZbo9NYrmx942aWJBlNbEq0K8woTu-F9e9SR2F528/s1600/skip132.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="394" data-original-width="1062" height="119" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjz2_0_qPHGsd-ctR8tTLvkLexF8F_RncFt8jF5S7_AOcF6D-czdUe73IRSuL1I-OszqeqNkHlUogDbCPFMNh8FCcMxBpNPjtNgPOpZbo9NYrmx942aWJBlNbEq0K8woTu-F9e9SR2F528/s320/skip132.png" width="320" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhWsG_3DsnGsrGtqXfm4_yumAYdY9uWy5WVhda5ZY3h7wtLyJDxZqUtd97qjLCGN1RqeiWkWQ8ApIss-dTs2FXkSDzLsGlchJQiWT2LELFcMPLBOHQ2USdnQBYuOR_wPbnzuZ3wWYlnkLo/s1600/skip49.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="384" data-original-width="1108" height="111" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhWsG_3DsnGsrGtqXfm4_yumAYdY9uWy5WVhda5ZY3h7wtLyJDxZqUtd97qjLCGN1RqeiWkWQ8ApIss-dTs2FXkSDzLsGlchJQiWT2LELFcMPLBOHQ2USdnQBYuOR_wPbnzuZ3wWYlnkLo/s320/skip49.png" width="320" /></a></div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-71036218880229934852018-09-03T12:25:00.003-07:002018-11-21T19:52:53.661-08:00Yet Another Option for FIND A WORD Method<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTbXnENmeDKcmRcWP8Iq_-5spww4chFgoccmPwZrwahPE3MRXpZ3pj6sDmuD16AvxL7dpg1B1pXJcw5n8H7Tme6pZoSp3GiTfpGuvZNkc-sW6hiABaSvgUWjqeo5YlGDEHACqdhK-hyS0/s1600/LettersAttached+option.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1039" data-original-width="806" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTbXnENmeDKcmRcWP8Iq_-5spww4chFgoccmPwZrwahPE3MRXpZ3pj6sDmuD16AvxL7dpg1B1pXJcw5n8H7Tme6pZoSp3GiTfpGuvZNkc-sW6hiABaSvgUWjqeo5YlGDEHACqdhK-hyS0/s400/LettersAttached+option.png" width="310" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<br />
The "<b>Find a Word</b>" method now has yet another new option to help you find the word you seek. (With all these options you now have available, you'd be hard-pressed <i><b>not</b></i> finding the word you want.)<br />
<br />
This new option is called "<b>my letters in SEQUENCE</b>". It means it'll find all words that contain your input string of letters in sequence, i.e., back to back. (The radiobutton's label should read<br />
"<i>my letters INCLUDED in SEQUENCE</i>"<br />
but I was short on space, so I compromised on the wording.)<br />
<br />
For example, if you wish to find a word containing the letters "ראש" in sequence within a word, then the word "בראשית" would show up (given, of course, that you set your Search Range to include Parshah בראשית within your scope.<br />
<br />
Now at version 52.<br />
<br />
(Not that all combinations are of equal significance, but each new option actually multiplies the number of combinations available. Having added one to the lower set of options, of which there now are 5, along with the two options in the upper set, now gives the user <i>10 combinations</i> of options and corresponding results.)Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-63129860153761476822018-08-28T21:15:00.000-07:002018-09-05T06:41:18.163-07:00New Option for "Find a Word" Method<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZUeGGGCW5Ba3-iwxPydQDw924MOJLSQb_9tElDwjI5K7N5fzRlPd48qQHphByOs1Dx9EvEds6z88L6ceijRg2p2yxo_LKKO63eHJWiBrhyQNol20tC3hmrKmvkf9Ig9rPnA5DyacJ00g/s1600/MyEndLetters.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="401" data-original-width="756" height="169" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZUeGGGCW5Ba3-iwxPydQDw924MOJLSQb_9tElDwjI5K7N5fzRlPd48qQHphByOs1Dx9EvEds6z88L6ceijRg2p2yxo_LKKO63eHJWiBrhyQNol20tC3hmrKmvkf9Ig9rPnA5DyacJ00g/s320/MyEndLetters.png" width="320" /></a></div><br />
Often, in looking up a Hebrew word in Tanach, the word may have prefixed letters attached to it because in Hebrew these additional letters act as additional words, unlike in English where extra words are used rather than elongating the word with prefixed letters.<br />
<br />
For example, "to Moses", "and Moses", "like Moses", "with Moses", "via Moses", "at Moses", "and by Moses", etc. -- all these terms comprise only one word in Hebrew word. Hebrew accomplishes this simply by affixing a letter or two in front of the word, extending the length of the word by one or two or more letters.<br />
<br />
To ignore these prefix letters for your search, which you often consider insignificant, it is now possible to use <b><i>"Find a Word"</i></b> using a new option, now introduced, namely, letting you specify <b>"My ENDING Letters".</b> Insignificant prefix letters can thus be ignored to find your word.<br />
<br />
So, in this example, if you were just looking for words that contain Moses, you can specify "משה", use the option "My ENDING Letters", and words ending with your 3-letter word will show up without having to know beforehand exactly what insignificant letters begin the word.<br />
<br />
With this option you'll get hits such as:<br />
<div style="text-align: right;">למשה</div><div style="text-align: right;">במשה</div><div style="text-align: right;">ומשה</div><div style="text-align: right;">ממשה</div><div style="text-align: right;">ובמשה<br />
כמשה</div><br />
Now at version 51. <br />
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-21924745029473235902018-06-14T20:32:00.002-07:002018-09-05T06:45:15.537-07:00Hit-Limit Reminder Installed<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkfLfUVGwZRg2gcKjTTRoIaE0XbGAz7JEuWb90qVh5qmsbut9gYTFTsL_zJVXAy8S698bk7brRW0BfUoIrUsiSuRcFe_ivut7zFoYRfKmAfxxozD4-z0X19WqlAuHqD1BSNTEW6yRZOJs/s1600/tw+shot.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="282" data-original-width="432" height="130" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkfLfUVGwZRg2gcKjTTRoIaE0XbGAz7JEuWb90qVh5qmsbut9gYTFTsL_zJVXAy8S698bk7brRW0BfUoIrUsiSuRcFe_ivut7zFoYRfKmAfxxozD4-z0X19WqlAuHqD1BSNTEW6yRZOJs/s200/tw+shot.png" width="200" /></a>Version 50 of Toraware now sports at the end of the Results List a line of text in case the hit-limit count was encountered. This would now remind a user there might, in fact, be more results forthcoming were he to just increase his hit-limit count. Without this text-line-reminder, the user may well not realize he came to the end of the list prematurely.<br />
<br />
<br />
Now at version 50. Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-25581032270329100812018-03-24T22:12:00.001-07:002018-11-21T20:09:57.489-08:00How Many Times is "JERUSALEM" Mentioned in Tanach?The answer may surprise you. Expressly, <b><i>never</i></b> in Torah. That's not so surprising since the Jews entered Eretz Yisrael in 2488, whereas Torah chronicles what happened during the prior 40 years in the desert.<br />
<br />
In Nach, however, it appears no less than <b><i>669</i></b> times! Imagine that.<br />
-------<br />
<b><span style="color: #990000; font-size: x-small;"><i>Options Page:</i></span></b><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiCFk-AQOyNw3y_df62jbKoiyEsMkqb-5tcVlfb3uZnybuUhMtrP7EjcPpLi5BOI2zpD9Rzt5llW3AH422jinMYtUH494uSmxOlsPmM6pypP4dsoYYrXHaoXx_kQ47K6ADwqbscixIeQxA/s1600/delete+me+3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="832" data-original-width="716" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiCFk-AQOyNw3y_df62jbKoiyEsMkqb-5tcVlfb3uZnybuUhMtrP7EjcPpLi5BOI2zpD9Rzt5llW3AH422jinMYtUH494uSmxOlsPmM6pypP4dsoYYrXHaoXx_kQ47K6ADwqbscixIeQxA/s320/delete+me+3.png" width="273" /></a></div>
<br />
<b><span style="color: #990000; font-size: x-small;"><i>Results Page:</i></span></b><br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwOEhwpnINJ7s0hRYLmCC8TVWkON8l_t9gxX66bP9SP1_rqb6DkdhfWpfQJPKAr4kUkL-JfXDEL2_yQzB20B_8FfmemY6IkPGS-T-Midwlj5oyMFCgHzmfSWsUi4LecTPNBbFiuy2PlR4/s1600/delete+me+2.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="502" data-original-width="1040" height="154" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwOEhwpnINJ7s0hRYLmCC8TVWkON8l_t9gxX66bP9SP1_rqb6DkdhfWpfQJPKAr4kUkL-JfXDEL2_yQzB20B_8FfmemY6IkPGS-T-Midwlj5oyMFCgHzmfSWsUi4LecTPNBbFiuy2PlR4/s320/delete+me+2.png" width="320" /></a><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<div style="text-align: center;">
<b>:</b><br />
<b>|</b><br />
<b>:</b></div>
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiSqtz_HmGN61odRd0fNQ9il5XMaeu6ASo7y7OOAyPCIyJ8a8f9p7tfI1LkDuL5ZjPtRTobhFGxcWVmqbXnpDe0GdxH7YIDpGFzPNtCeKMbBTRvuRB-D_YW76o3mmtKFEWoUcByYtMZq2o/s1600/delete+me+1.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="316" data-original-width="1072" height="117" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiSqtz_HmGN61odRd0fNQ9il5XMaeu6ASo7y7OOAyPCIyJ8a8f9p7tfI1LkDuL5ZjPtRTobhFGxcWVmqbXnpDe0GdxH7YIDpGFzPNtCeKMbBTRvuRB-D_YW76o3mmtKFEWoUcByYtMZq2o/s400/delete+me+1.png" width="400" /></a><br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-992327665302722342018-03-21T17:57:00.002-07:002018-03-21T18:20:27.652-07:00New Option for "Find a Word" MethodThe <b><i>Find a Word</i></b> method now has a new option, which allows the user to specify the leading letters of a word for his word search.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7hADDlnk4wEJb5PTAPL9W4Dk-oJ-FMfGP-i17z_o5ac25SKv6YOYh5665rQEAskGaRH_pq_yGHOC6VjVS2y_V6P7G6-OeoX3yJtOQiRH00YOjtFxC3MpofVnpLhXyEaAl3_UGaNN1Xgo/s1600/delete+me.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="386" data-original-width="786" height="157" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7hADDlnk4wEJb5PTAPL9W4Dk-oJ-FMfGP-i17z_o5ac25SKv6YOYh5665rQEAskGaRH_pq_yGHOC6VjVS2y_V6P7G6-OeoX3yJtOQiRH00YOjtFxC3MpofVnpLhXyEaAl3_UGaNN1Xgo/s320/delete+me.png" width="320" /></a></div>
<br />
In effect, this method now has 6 choices for ways to search out a word.<br />
<br />
This deployment constitutes version 50.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-33805177641898758212018-01-17T10:56:00.001-08:002018-09-05T08:12:36.077-07:00Methods Roshei & Sofei Possukim - CorrectedThanks to a friendly user of my website, I came upon a bug in two methods I thought were simple pieces of code, but in fact they needed correction. This is the 2nd time she found a bug! <b><i>Thank you again Zahava P.!!</i></b><br />
<br />
Ever since I expanded the database, from just Torah to now include the entire Tanach, a variety of issues suddenly arose that I was made aware of only later.<br />
<br />
Previous methods regarded the Torah database to be one big book, where Parsha borders were ignored. If results spanned from one Parsha into another another, that was okay.<br />
<br />
But with the expanded Tanach as my new database, some methods or option (gematria's "successive possukim") no longer make sense. Now, borders between books became significant.<br />
<br />
For example, in a gematria search with the “successive possukim” option selected, it makes no sense if the gematria result began in one book and the rest of the gematria was found in the next. To illustrate, if the last verse in Torah comprised one part of the gematria, and the rest of the gematria was found in verses of the next book, Yehoshua, this "hit" would make little sense.<br />
<br />
(My screw-up came up because I had to allow for spanning to occur for the books Shmuel A & B, Divrei Hayomim A & B, Ezra & Nehemia, and Melachim A & B, and this code was incorrect.)<br />
<br />
This same problem exists in methods such as “Equidistant Letter Sequence”, “Sofei Possukim” and "Roshei Possukim". Because in each of these methods, the results found might span from one book across into the next, and such spanned results have no good purpose.<br />
<br />
I coded my way out of this “new” problem in 3 situations but I could not do so with the “Equidistant Letter Sequence” method. This code as it is is already quite complex so I just couldn't. Instead, I simply put the burden on the user, forcing the user to specify proper borders for his search region. The "Range" parameter can easily be set right by the user on the Home Page.<br />
<br />
I'm sorry I could not code my way out of the “Equidistant Letter Sequence” method and had to resort to issuance of an error to bypass this inability. It's awkward because the same error ought to pop up for “Sofei Possukim” and "Roshei Possukim", because these too make no sense were results to span across separate books. But here this situation can no longer happen because I code it so that spanning will not take place.<br />
<br />
Here's the error that shows for the “Equidistant Letter Sequence” method when the range parameters must first be properly specified:<br />
<br />
<div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQmdXRWYvKISLRLmBZ3ev7sGUmE5Wg78_5VcCjH8Bmce40DA4Ytkg_rcgIeMkZ7TzS0jVvk3AGfGQViOJRbAfey2BgOaHeUxmAemjKRaTp_p2gFmPpcMBEVqGwhyphenhyphenTuWtAFPVjsp7KvyDg/s1600/ELS+error.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="739" data-original-width="1028" height="230" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQmdXRWYvKISLRLmBZ3ev7sGUmE5Wg78_5VcCjH8Bmce40DA4Ytkg_rcgIeMkZ7TzS0jVvk3AGfGQViOJRbAfey2BgOaHeUxmAemjKRaTp_p2gFmPpcMBEVqGwhyphenhyphenTuWtAFPVjsp7KvyDg/s320/ELS+error.png" width="320" /></a></div><br />
<br />
<br />
<span style="font-size: x-small;"><i>(With this correction, and with what I did to streamline "Find a Phrase", I believe the entire program is now 100% well and accurate, ב׳׳ה.)</i></span><br />
<br />
Now at version 48.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-16437694995837694202017-12-11T20:41:00.001-08:002018-09-05T08:10:06.996-07:00"Find a Phrase" -- A Powerful Tool in its Own RightThis (46th) version of Toraware’s search program sports a new “<b>Find a Phrase</b>” rendition. The earlier version had some problems. Now the code is extremely streamlined, bound to yield quick, accurate results.<br />
<br />
This method searches words in the same order as the user enters them (separated by spaces), thus the use of the word “phrase”.<br />
<br />
Unlike “Find a Word”, where there’s an option to match the letters in any order, in “phrase” searching your words are assumed to be in their natural (same) order, as well as the letters you stipulate. The "Find a Word" method searches for one word only. The "Find a Phrase" method seeks multiple words in a verse.<br />
<br />
“Find a Phrase” options offers 4 ways to search.<br />
<br />
<b><i>1)</i></b> You can seek words with only part of the words you’re seeking. E.g., you can search צם, and the word in the verse מצרים would register as a “hit” - under the "INCLUDE my letters" option.<br />
<br />
<b><i>2)</i></b> You can specify the words you want should be exactly as keyed in. This is the "ONLY my letters" option.<br />
<br />
<b><i>3)</i></b> & <b><i>4)</i></b> You can also specify in either of the above searches that you want your words in adjacent sequence ("Consecutive words" option); Or you can opt for "Not necessarily", where the words could be found with other words intervening, i.e., they'll appear in the verse, but not consecutively.<br />
<br />
As always -- <u>read the title of the Results Page to remind you which options you specified</u>; You needn't go back to the Options Page to see.<br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtEhK87TLtLf4wGyQB4wUfw3pndsfFiTTXL7Z9zGhtFU1KHsT77AfSUYAzjLw0rxzAygJCZsa6SqgyY7R5KDdLOIS1yfQjS8GOvgzD6NaGkyFJgdte6fJ4drFp4PNfyh3QYgnzsSAOrNo/s1600/alef+to+chet.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="1100" data-original-width="1332" height="165" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtEhK87TLtLf4wGyQB4wUfw3pndsfFiTTXL7Z9zGhtFU1KHsT77AfSUYAzjLw0rxzAygJCZsa6SqgyY7R5KDdLOIS1yfQjS8GOvgzD6NaGkyFJgdte6fJ4drFp4PNfyh3QYgnzsSAOrNo/s200/alef+to+chet.png" width="200" /></a>Suppose you want to find where in Tanach we have 8 words in a possuk with the following letters in them, respectively:<br />
א ב ג ד ה ו ז ח<br />
<br />
You'd get the results shown on the right (click image to enlarge it).<br />
<br />
Note: How you spell your own words for the search is important because you do NOT need to include all letters of the word. For example, often the letter “vov”, the grammatical letter with the sound “Oh” (or “oy” according to others) is absent, so it’s best to exclude it. E.g., if you search for יעקוב you'll miss יעקב, but if you search for יעקב, you'll get them all. As long as the main letters of the root are in the word, this search can find the phrase.<br />
<br />
This fix I believe renders the search engine just as I initially conceived it to work fine. Perhaps now, if free time avails itself, I'll try convert it to a mobile app. As you can see from my compact design, button placements and functionality, I had that very goal in mind from the very beginning. Although for now I'm real happy for this website version. It's a good little tool that I myself often use.<br />
<br />
Now at version 46.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-6915432173094880692017-11-13T21:49:00.001-08:002018-01-17T12:04:32.158-08:00Awkward Results May Appear (now fixed)<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh7rNOD8EfBXwOHHmqoVl-IivBTUlIwsuUD-bnhUKlCuuaNfS4Har_BwY-x2iu7Hs3MsDdPseZnqSBTFCGJZLXYuhBdrsIg1XmRTa5pbEyj31zC0SsGLyjpvyaZGHO-T0Pi2gMvN2IGQRE/s1600/tw-blog+bug.png" imageanchor="1"><img border="0" data-original-height="946" data-original-width="1403" height="432" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh7rNOD8EfBXwOHHmqoVl-IivBTUlIwsuUD-bnhUKlCuuaNfS4Har_BwY-x2iu7Hs3MsDdPseZnqSBTFCGJZLXYuhBdrsIg1XmRTa5pbEyj31zC0SsGLyjpvyaZGHO-T0Pi2gMvN2IGQRE/s640/tw-blog+bug.png" width="640" /></a><br />
<br />
As I expanded the database from just Torah to include the rest of Tanach, a logical dissonance erupted in my code unnoticed until now.<br />
<br />
Of all methods available on Home Page, a few new methods added later may yield some results, or matches, that make little sense depending on the Range parameters the user can set on Home Page.<br />
<br />
Let’s say the user sets his Range so that he searches the entire Tanach. In other words, he sets the Start of his Range to “<i>Bereishis</i>” and the End of the Range to “<i>Divrei Hayomim B</i>”. <br />
<br />
Now suppose he chooses the method of “Roshei Possukim”. Suppose too the last verse in one book - together with the first verse of the next book - score a match (a “hit”). Were these verses within the bounds of Torah, i.e., anywhere between the 1st and last <i>chumash-parsha</i> inclusive, then that’s fine. All results would make sense.<br />
<br />
But suppose the last verse in Joshua - together with the “next” verse, which would be the first verse in the book “Shoftim” that I had juxtaposed to the Joshua book, comprise a match? What good would that result be? None from a logical standpoint. As long as juxtaposed books comprise a unit, as do the 5 <i>Chumashim</i>, or the pair of books Shmuel A and B (or also Melachim A and B and Divrei Hayomim A and B), then results than span across these books still can be considered worthy. <br />
<br />
But searching say, Joshua and Shoftim, or any other juxtaposed books that are separate entities, shouldn’t show such results in the first place.<br />
<br />
Methods like “Find a word”, “Find a Phrase” or “Bookends” still apply as before, and make full sense - no matter what range is set by the user.<br />
<br />
But methods such as “Gematria” - run under the specific option of “successive possukim” (see image below), <u>where multiple verses comprise the match</u>, spanning separate books makes no sense. Similarly, the methods “Equidistant Letter Sequence”, “Roshei Possukim” and “Sofei Possukim”, where more than one possuk make up the result, spanning books ought to be prevented.<br />
<br />
Well, I haven’t yet figured how to modify the code.<br />
<br />
Here's an example of such an awkward match or "hit" (Options Page and Results Page are shown):<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQ0t_Zt5aLm7CxvrIR1rPh0HbBWW0qmf384-pxlh0vV8nKRayYq4LlRHaZMNqNmIf76vJadKjBu63bMgAXWcepvadD4TU6lcXqTtDHFhPL21vYirtLsU0GEh_5O3RHGMOWhg4GjOCxdRc/s1600/tw-blog+bug+3.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="632" data-original-width="530" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQ0t_Zt5aLm7CxvrIR1rPh0HbBWW0qmf384-pxlh0vV8nKRayYq4LlRHaZMNqNmIf76vJadKjBu63bMgAXWcepvadD4TU6lcXqTtDHFhPL21vYirtLsU0GEh_5O3RHGMOWhg4GjOCxdRc/s200/tw-blog+bug+3.png" width="167" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhsduRQJFeZS9pe2ZrqgLbObKiJzjgQDjvuwRZmFmN315AVBBjANeeuC2c4NTKPRZ7S6RrjsJDJzdQlCynoSav4YHvftLCgfQL4kyILd-5X5aSjAfy-0YxtxN1RREkb75LRA_I1-sIUOOo/s1600/tw-blog+bug+2.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="246" data-original-width="1166" height="67" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhsduRQJFeZS9pe2ZrqgLbObKiJzjgQDjvuwRZmFmN315AVBBjANeeuC2c4NTKPRZ7S6RrjsJDJzdQlCynoSav4YHvftLCgfQL4kyILd-5X5aSjAfy-0YxtxN1RREkb75LRA_I1-sIUOOo/s320/tw-blog+bug+2.png" width="320" /></a></div>
Notice the result is comprised of two verses whose gematria add up to 3828. These are the last verse in Tehillim plus the next verse, which is the first verse in Yeshayahu! This is an awkward "hit", to be sure, and completely insignificant.<br />
<br />
<h2 style="text-align: center;">
<span style="font-size: x-large;"><b><span style="color: red;">UPDATE:</span></b> <b>1/17/18</b></span></h2>
Glad to say these changes have been made - to remove awkward results. My post dated 1/17/18 (<a href="https://torawaredotcom.blogspot.com/2018/01/methods-roshei-sofei-possukim-corrected.html" target="_blank">link</a>) explains it all.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-60803149237958341502017-10-15T20:45:00.000-07:002018-01-21T12:21:34.145-08:00The Simple Storyboard Underlying Toraware.comToraware's website has a simple paradigm. It has only 3 pages. Yet this minimal set of pages runs many powerful searches with instant results. It's a compact, streamlined multi-tool for searching Tanach (a Jewish "Swiss army knife").<br />
<br />
The Home Page offers a list of methods to search by. There you can change the range of text to search. And there you can set the number of "hits" you want to display.<br />
<br />
Page 2 is the Options Page. Because each category has its own options, the user can here override the default settings. Here too is where the user's input is taken.<br />
<br />
Page 3, the Results Page, shows all the "hits" for the method and options the user chose. The title on this page summarizes the method and options chosen, so the user need not remember them or go back to see what they were.<br />
<br />
<b><i>It works like, and appears like, a mobile app in a smartphone.</i></b><br />
From page 2 the user can return to page 1.<br />
From page 3 the user can return to page 2.<br />
<br />
<span style="color: #5fade9; font-size: large;"><b> METHODS OPTIONS RESULTS</b></span><br />
<span style="font-size: x-large;"><b><span style="color: blue;">________ <==> ________ <==> ________ </span></b> </span><br />
<span style="font-size: x-large;"> <b><span style="color: blue;">Home Options Results</span></b></span><br />
<span style="font-size: x-large;"> <b><span style="color: blue;">Page Page Page</span></b></span><br />
<br />
<br class="Apple-interchange-newline" />
Page 1) A choice of methods to query by; And two global options.<br />
Page 2) Options available for that chosen method. Here the user enters his input.<br />
Page 3) Shows matching results, each hit detailed in a list.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-38096473824682299182017-10-01T09:33:00.002-07:002017-10-01T09:33:38.303-07:00A Little "Bug" Detected and Fixed<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1-twthqseJrN6nHiL8HFSdiosY9GigsDJdCvLPrS_9nnxs_pyiKrcwBp3BVdTfI6SXUf7HR9XweUEEodv9cEyUEBK1vt-zvfLDV-fcdsntScvZK_DVUAQyMLOuip93ENY2Ddc_VG5Odw/s1600/_delete.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" data-original-height="532" data-original-width="770" height="138" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1-twthqseJrN6nHiL8HFSdiosY9GigsDJdCvLPrS_9nnxs_pyiKrcwBp3BVdTfI6SXUf7HR9XweUEEodv9cEyUEBK1vt-zvfLDV-fcdsntScvZK_DVUAQyMLOuip93ENY2Ddc_VG5Odw/s200/_delete.png" width="200" /></a></div>
The result-page to the left shows the title incorrectly rendering (after using the search method of "possuk's gematria factors"). Therein, instead of displaying the sum of the letter input correctly, javascript placed an "NaN" there instead.<br />
<br />
This now stands corrected.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-36720726927239178062017-07-10T22:43:00.001-07:002017-08-02T12:30:24.226-07:00Navigational Buttons RepositionedThe Results Page (which displays the “hit list”) presented a problem when that list contained many hits, because scrolling down to view more hits <b><i>hid</i> the Back button</b> that was situated <u>near the top</u> of the browser’s window.<br />
<br />
In that case, new users would probably hit the <i><b>browser's</b></i> back button if they wished to return to Home Page or to the Options Page -- instead of scrolling back up using <b><i><u>my</u></i></b> "Back button"! Using the <i>browser's</i> Back icon expels the user from toraware.com, besides losing the user's place and the options he/she selected.<br />
<br />
Because this site was designed to eventually also be used also on a mobile device, it was created with a simple two-button navigational system, operable only with the two buttons the program itself provides dynamically. <br />
<br />
So how was the problem solved? By not requiring the user to scroll up to the top of the list to bring the button into view. The Back button now is always in view. No more scrolling up to see it is necessary.<br />
<br />
One swift, simple change fixed the problem. Two or 3 lines of CSS3 code did the trick. The buttons are now "anchored” to the bottom of the browser's window, always present. Hopefully this will <i>help prevent the user from hitting the browser's navigational buttons</i>.<br />
<br />
~ ~ ~ ~<br />
<br />
Another minor change was introduced as well: The "geometric possukim" options now have a 3rd option, where both square and triangular features are shared by the same possuk. (It turns out this combination always yields only possukim that are <u>triangular of 8</u> and <u>square by 6</u>.)Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-38164844472380326502017-06-04T12:40:00.002-07:002017-07-16T10:35:05.099-07:00New Kri/Ksiv Option Delayed<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiwTzmMGK14r1rbUncSR2qcBTU-wjcp5issDuO9_wTCmbXtGqkI8OtnApGLd8S89jRrQasodFshXm5Fr3cx11W5cCgLTBtaQjqucZRn8K37f8Lo8od7ORyWmvwTe0sLyS0AD0snhuoVRic/s1600/tw+kri+added.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="611" data-original-width="610" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiwTzmMGK14r1rbUncSR2qcBTU-wjcp5issDuO9_wTCmbXtGqkI8OtnApGLd8S89jRrQasodFshXm5Fr3cx11W5cCgLTBtaQjqucZRn8K37f8Lo8od7ORyWmvwTe0sLyS0AD0snhuoVRic/s320/tw+kri+added.png" width="319" /></a></div>
Tanach, after all, comes in two versions. So far, the only database available is the Ksiv version.<br />
<br />
Toraware wants to provide the option to also search the Kri database. I would have added this to the Home Page as the 3rd global parameter, in addition to Range and HitLimit parameters (see red arrow).<br />
<br />
But I ran into technical problems. How do I dynamically modify an external file's reference? The additional database will now sit in reserve until I figure this out. Apparently the use of "jQuery" will resolve this obstacle, but this will take time to learn, if I get to it. I also don't know if I should use two SCRIPT tags to require initial download of both files.<br />
<br />
But my failure turned out to be a blessing in disguise. During creation of the new Kri database, I found several mistakes I had made in the original Ksiv database. The amount of corrections was significant. (Wherever more than one kri-ksiv instance occurred in the same possuk, there I erred in my original editing.)<br />
~~~~~<br />
The Home Page display meanwhile also got a slight facelift, in my attempt to present the Search Range as more intuitive to the first-time user.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-44819525946557556552017-05-17T21:26:00.001-07:002018-01-21T00:45:05.942-08:00Known Potential Errors Not Yet Adjusted For<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoYVtJh2Mbf5jEKcKjgpRu_uR7ASja5jY0PZu1frn7l6IkDH-4dalC4Y5VNpumHWklkamYSIpy4fMsqwFqe2m8FAm_tkEURc_CpIT1pIuBa2Alw_2nvh3RmMYtYBgFlljukBCTH1XrrVM/s1600/tw2.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="176" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoYVtJh2Mbf5jEKcKjgpRu_uR7ASja5jY0PZu1frn7l6IkDH-4dalC4Y5VNpumHWklkamYSIpy4fMsqwFqe2m8FAm_tkEURc_CpIT1pIuBa2Alw_2nvh3RmMYtYBgFlljukBCTH1XrrVM/s320/tw2.png" width="320" /></a><br />
There are 6 quirks of Tanach I have not yet managed to accommodate in my search program. There are the 5 quirks of the "<b><i>piska</i></b>" being in the middle of a possuk, and one quirk where a "<b><i>sofit</i></b>" letter appears in the middle of the word, instead of at its end.<br />
<br />
There are a few verses in Torah configured peculiarly because each verse actually consists of two verses combined into one. The two parts together make up the whole verse, even though in concept the two verses could be considered logically distinct from the other, but for some reason this is how it is. (The asterisked verse in the illustration shows such an instance.)<br />
<br />
This notation, that “there-should-have-been-a-break-between-verses-here” (between component verses), is called a “piska”. In Torah, the piska physically manifests as spatial breaks in written scripture, either as a {פ} or as a {ס}.<br />
<br />
There are 3 piskas in Torah, and 2 more in Yehoshua. Here are their locations:<br />
<br />
<b>1)</b> beraishis 35:22<br />
<b>2)</b> bamidbar 26:1<br />
<b>3)</b> devarim 2:8<br />
<b>4)</b> yehoshua 8:24<br />
<b>5)</b> yehoshua 4:1<br />
<br />
These grammatical quirks result in two component logical segments physically occupying one verse.<br />
<br />
When I first designed my database, it never occurred to me two component verses could be "squeezed into" one physical verse.<br />
<br />
How woud this effect results? Suppose, for example, you seek a gematria where the result will be a whole possuk. Were any of the piska component verses also hold this value -- I’d miss it -- because I don’t test component verses. I deal only with the whole physical verse.<br />
<div>
<br /></div>
Ideally component verses should also be subject to individual examination. But it’s too late to patch this up now to accommodate these possible extra contributions to search results. Even now I wouldn’t know how to design my database without overloading the program with a lot of extra code. It would horribly slow things down to check every verse -- when only 5 verses in all of Tanach have this quirk.<br />
<br />
To this minor degree (and to the extent where these may be relevant), my search results would suffer from less than the full set of possible results.<br />
<br />
The 6th quirk that might render a wrong result is in Yeshayahu, chapter 9, possuk 6. The first word (<b>לםרבה</b>) has its 2nd letter as a "mem sofit" instead of being written as למרבה.<br />
<br />
In the meantime, rather than change the configuration of my entire database as I originally conceived it, as well as the necessary changes in code that would entail, I'd rather just "live with" this source of potential error.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-51336058026232074122017-05-10T19:42:00.001-07:002018-09-05T08:47:08.839-07:00New Method of Multi-Word Search Introduced<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj9bNy16V9grSx5ZK-UFWLOWGO3aqDJfmfdlSWLJ_CqHwX6oi6rrnUxS8B1aaPourdzFjSo5rO_5LzfCIGiyPJVIeLjwpMGIi5G_Hip_bFAkIhDMwmi-u43LtD4ROC9f_2M3dm5JuDd3I8/s1600/_delete.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" data-original-height="416" data-original-width="656" height="126" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj9bNy16V9grSx5ZK-UFWLOWGO3aqDJfmfdlSWLJ_CqHwX6oi6rrnUxS8B1aaPourdzFjSo5rO_5LzfCIGiyPJVIeLjwpMGIi5G_Hip_bFAkIhDMwmi-u43LtD4ROC9f_2M3dm5JuDd3I8/s200/_delete.png" width="200" /></a></div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfC1ik_f2KAsMUIEmVO_YJN6ihj-IF0pslMk7hSSzENsuqeY7S6ZuAlZljpWgre2NcKDRG108k6pudcUMYrPZgLbmgRUDXbZ2sx8gUsT8l2y-UVbBhvTB3s5h460_DcwsKzNfehwWURi0/s1600/tw.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhfC1ik_f2KAsMUIEmVO_YJN6ihj-IF0pslMk7hSSzENsuqeY7S6ZuAlZljpWgre2NcKDRG108k6pudcUMYrPZgLbmgRUDXbZ2sx8gUsT8l2y-UVbBhvTB3s5h460_DcwsKzNfehwWURi0/s320/tw.png" width="204" /></a><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Rather than complicate the Find a Word method by asking how many words in a verse are being sought, I introduced the new search method <b>Find a Phrase</b> as a separate multi-word method. Nor do I plan to combine them in the future because each method comes with different options.<br />
<br />
Unlike the single-word search, this multi-word search has no "reverse order" or "any order" option.<br />
<br />
The only proviso for word entry for this new method is to separate the user's words with a space between them. This proviso is always on display just above the user-entry field.<br />
<br />
Finally, as of yet there is an important caveat as far as the matched results that are found is concerned, and this caveat is explained in the trailing Post Script.<br />
<br />
<div>
<b>---------------------------------------------------</b></div>
<span style="color: blue;"> </span><br />
<span style="color: blue;">Example 1</span>:<br />
I read in the Rebbe's Maamarim that "יציאת מצרים" is mentioned in Torah 50 times (the same count as the 50 "שערי בינה"). So how would I locate these 50 mentions? This new method provides a way. I can type in two words; The 1st will be letters from the root verb "to go out", namely, "צא"; And the 2nd word will be the name "מצרים". As follows:<br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgutLL4F-3MCO9gi_iSylXseg2zZwsmrR6ddYb9x1w6_3cl78Hp4u8GIyvV_Bn09RSRbhY-NZMmsuaucNrCPfDnX3uvI7AOqLZwkhcF31HgcQsTSbPkskbtsrWWCaWqQz4TjBhFwpSJc54/s1600/DELETE+1.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="229" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgutLL4F-3MCO9gi_iSylXseg2zZwsmrR6ddYb9x1w6_3cl78Hp4u8GIyvV_Bn09RSRbhY-NZMmsuaucNrCPfDnX3uvI7AOqLZwkhcF31HgcQsTSbPkskbtsrWWCaWqQz4TjBhFwpSJc54/s320/DELETE+1.png" width="320" /></a><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
This set of options results in 82 hits. Probably most of the 50 hits show up in the result list this way, although at least 32 will have to be eliminated. Below you see the last 8 hits. Of these, #77 is a false hit and would not count. The others here seem to be hits.<br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgmP6MEe6fu2FqrnsneI49jFBYvkS4H7HVd24z59815IudZgmnAkQMItmDNMKOROTC5dNEP8exXNMJxLFToUqPI9NMOwCngIYXS8oSSp3jqTg4p4MIToFFzzoZqFFA2BLRkCuZO8zeQ0Pk/s1600/DELETE+2.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgmP6MEe6fu2FqrnsneI49jFBYvkS4H7HVd24z59815IudZgmnAkQMItmDNMKOROTC5dNEP8exXNMJxLFToUqPI9NMOwCngIYXS8oSSp3jqTg4p4MIToFFzzoZqFFA2BLRkCuZO8zeQ0Pk/s400/DELETE+2.png" width="365" /></a><br />
<div>
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Below, you see the first 8 hits of the above search. The first 5 hits also can be eliminated.<br />
<br />
Notice I set the 2nd option to "<b>not consecutive</b>". That's because the verb and its object, the name, needn't be adjacent words. Other words can be wedged in between the verb and the name, as is evident in #8.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoXxguG5d-1eeo2diARFy_h84hOTLDEUmfueLtUNNcsKbidlANjiZWfy1zaNqj4rsKc8dh0V5akr7gQsqZeLkrYR_kTt3zT54MHgeT75PVm0XdYcC4S59XUU5t4JLCM5VkL-BDROKQ8_A/s1600/DELETE+1.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoXxguG5d-1eeo2diARFy_h84hOTLDEUmfueLtUNNcsKbidlANjiZWfy1zaNqj4rsKc8dh0V5akr7gQsqZeLkrYR_kTt3zT54MHgeT75PVm0XdYcC4S59XUU5t4JLCM5VkL-BDROKQ8_A/s400/DELETE+1.png" width="362" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<br />
But mention of "יציאת מצרים" can also occur where the <u>name</u> precedes the <u>verb</u>. Using only the option set we used above, as well as the user's entry, would certainly miss detection of this less common form of speech.<br />
<br />
So below is the other thing you can do to catch more of the 50 mentions this way. <b><i>Note here the user's two-word entry is reversed from what it was before!</i></b> This will yield results the above search would miss. Of 7 hits, #6 (see below) probably also qualifies as one of the 50 mentions.<br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhK7VN7ceOOp1bz1jRuycCBuAs0m7PIgXUKcZhET09UD8gZM3y0VKpTqXLSNPBcTsRWp1uMY6EFKlKEzOCe5lgo_oQXJ5Nz9vZMex_o-yR_tyYWrf50eVxul-tsfU-p04wzmCJ90WYkc4I/s1600/DELETE+2.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="229" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhK7VN7ceOOp1bz1jRuycCBuAs0m7PIgXUKcZhET09UD8gZM3y0VKpTqXLSNPBcTsRWp1uMY6EFKlKEzOCe5lgo_oQXJ5Nz9vZMex_o-yR_tyYWrf50eVxul-tsfU-p04wzmCJ90WYkc4I/s320/DELETE+2.png" width="320" /></a><br />
<br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1kFusIecMCJcrUSmwq0Kp_ZulUWpyiDiXLTl9NtYzlyDymqZdXml4BUwcNXpCIocSu0x4x6SstoTXKcgDrhf9V16ZjX0bfrLI2nDvhN6m82aa690SJyXdobbHgB2sO6WzMMp1OD-izsA/s1600/DELETE+2.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="56" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1kFusIecMCJcrUSmwq0Kp_ZulUWpyiDiXLTl9NtYzlyDymqZdXml4BUwcNXpCIocSu0x4x6SstoTXKcgDrhf9V16ZjX0bfrLI2nDvhN6m82aa690SJyXdobbHgB2sO6WzMMp1OD-izsA/s400/DELETE+2.png" width="400" /></a><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1kFusIecMCJcrUSmwq0Kp_ZulUWpyiDiXLTl9NtYzlyDymqZdXml4BUwcNXpCIocSu0x4x6SstoTXKcgDrhf9V16ZjX0bfrLI2nDvhN6m82aa690SJyXdobbHgB2sO6WzMMp1OD-izsA/s1600/DELETE+2.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><br />
</a><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1kFusIecMCJcrUSmwq0Kp_ZulUWpyiDiXLTl9NtYzlyDymqZdXml4BUwcNXpCIocSu0x4x6SstoTXKcgDrhf9V16ZjX0bfrLI2nDvhN6m82aa690SJyXdobbHgB2sO6WzMMp1OD-izsA/s1600/DELETE+2.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><br />
</a><br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<b>---------------------------------------------------</b><br />
<span style="color: blue;"><br />
</span><br />
<span style="color: blue;">Example 2</span>:<br />
Suppose you want to locate “יעקב יעקב”, where or if it exists anywhere in Tanach.</div>
Just type in both words, choose among 2 options (= 4 scenarios), and hit GO.<br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3HBanZoOsmJdAV9uNOtt1TqB1zFc_qkBo6AufqgWVGhJMvPE3eUZvd0aS2krh3geRhDvWh9lheAp-pAEnaaFirxbXoJZHPtqgWk_NVvy-ShjXsRPssQYTdEf52fShKKv6czbVdRjr9UM/s1600/DELETE+3.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="227" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3HBanZoOsmJdAV9uNOtt1TqB1zFc_qkBo6AufqgWVGhJMvPE3eUZvd0aS2krh3geRhDvWh9lheAp-pAEnaaFirxbXoJZHPtqgWk_NVvy-ShjXsRPssQYTdEf52fShKKv6czbVdRjr9UM/s320/DELETE+3.png" width="320" /></a><br />
<br />
The above set of options and user entry yield the single hit:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGYiCj7ybGLjbNLGHzX9OW5bvDNG8eRSlV0f2nwpTK85eDvPRX58-apquqelbvXbpbT1QOpF_dfVO0TahxgSD0uU-fcx3mDAYqK4ZOZwgTtTblO8FFi3Pd_XHB4E7XXJclNh1LHzaheqc/s1600/DELETE+4.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="88" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGYiCj7ybGLjbNLGHzX9OW5bvDNG8eRSlV0f2nwpTK85eDvPRX58-apquqelbvXbpbT1QOpF_dfVO0TahxgSD0uU-fcx3mDAYqK4ZOZwgTtTblO8FFi3Pd_XHB4E7XXJclNh1LHzaheqc/s400/DELETE+4.png" width="400" /></a></div>
<br />
<div>
<br />
<br />
<br />
<br />
<br /></div>
<b>---------------------------------------------------</b><br />
<span style="background-color: white; color: #444444; font-family: Arial, Tahoma, Helvetica, FreeSans, sans-serif; font-size: 13px;">Now at version 42.</span><br />
<b><br /></b>
<i><b><span style="color: #660000;">P.S. </span></b></i><br />
<i><b><span style="color: #660000;">This method may miss hits if more than one hit</span></b></i><i><b><span style="color: #660000;"><i> <u>in the same possuk</u></i> is available. Only the first hit in that possuk will be reported while the rest, if they exist, will go unreported. This simplifies the code immensely. Although this method can be tweaked to include all matches, I leave this code in place, as is (at least for now) because it is still a powerful search method.</span></b></i><br />
<br />
<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8943876242976706339.post-39092691558749219272017-01-21T18:14:00.002-08:002017-05-10T20:01:44.971-07:00toraware.com Home Page Adds Hebrew MarkingsHome page now sports Hebrew too, a new “facial”:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg93tjNkiD1kBS5jKkgH0USidYV7l7nhfWSPffOP94Gfw5zHS-X681o3223z7cxWYEGI8JyPzvTx0hS-x4wrq01Y3t108jJQNxN7eEi1gm83WjMOXeN9mvFSnSzkpbeTty1KV0pBZyr7lA/s1600/TW000.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg93tjNkiD1kBS5jKkgH0USidYV7l7nhfWSPffOP94Gfw5zHS-X681o3223z7cxWYEGI8JyPzvTx0hS-x4wrq01Y3t108jJQNxN7eEi1gm83WjMOXeN9mvFSnSzkpbeTty1KV0pBZyr7lA/s400/TW000.png" width="265" /></a></div>
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
_________________________________<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiEPzSvqorDfpqlMGK0cl937Jop0av-sGIxkYg65v0MqhX8pBYLa7tKIQ2dGr79b1RsC1gUce0gd-jVTuagdWlXOzzNAJ1E67IHbsLTuGakTudviugzwMW38AalwY-AdWjfHaL2HJ96w8g/s1600/tw000.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="196" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiEPzSvqorDfpqlMGK0cl937Jop0av-sGIxkYg65v0MqhX8pBYLa7tKIQ2dGr79b1RsC1gUce0gd-jVTuagdWlXOzzNAJ1E67IHbsLTuGakTudviugzwMW38AalwY-AdWjfHaL2HJ96w8g/s320/tw000.png" width="320" /></a></div>
Unknownnoreply@blogger.com0