Thesaurus

The first part of the Thesaurus is done. I was surprised at how many Thesauri exist online that can be used without needing to pay royalties. Is that a word 'Thesauri'? Anyway, the database is loaded with all the word to word synonym connections of the words that exist in the book. Tonight, I'll be separating the index program out from the Virtual Urantia system and making it stand alone. After it's ready, I'll create the different operating system versions. I can do Linux, Windows, Symbian and Maemo, so it's still only in downloadable form and only capable of running on systems I can use directly. Sorry Apple guys, I don't have an Apple machine yet. Wished Native Client was up and running, I'd have it running everywhere from the net but it's difficult to tell when they'll have it ready. I'm guessing within 2011.

Also I've separated the index lookup system in smaller chunks using tabs so that a smaller screen can accommodate using the lookups on small cell phone screens. If I'm not done tonight, certainly in the next few days. I'll then place it on the Virtual Urantia site for download.

Indexing Indexing Indexing

I'm back from creating the next level of the automation system on the commercial side and am working on the index of the book. After having so many problems crop up from attempting to place the Jerusem Circles into the Virtual Urantia Book, I've decided I'd better wait till technology catches up to me and do something I'm familiar with.

There are several ways of indexing that I'm excited about. The first, of course, is working. Selecting a group of words and I immediately show how many times it appears in the book and give you all the references in a table and all the paragraphs with the word(s) highlighted. So on to the next step. First a thesaurus of the book. I can program that tonight, I hope. Then a reconnection of words to words based on the book's thesaurus so that the index engine can connect and show those. For example: If you select the word 'house', it'll show you all the places where abode shows up also and so on throughout all the thesaurus connections. Gotta do some thinking on how to select out words that are meaningless to the search.

Secondly. I'll work on the quotes around a group of words after that. Tricky if you use thesaurus words as in quote replacements but can be done. Next, instead of paragraphs, select by page and last but not least, search word to word distances, that is, if you're looking for 'home' and you type '1000' in the distance box, the system will give you all the words typed in that exist within 1000 words from each other.

Everything I've done for the English translation will work for the French, Spanish, Russian etc. I've tried indexing the French edition, quite a few problems. It's doable though, Spanish and Russian too.

Till I've left this planet, I'll be doing this stuff.

Still Waiting

How long before Native Client and Lighthouse for Native Client release the version that allows databases, 3d and Internet connections between computers is really a guessing game. Until then, I'll be working on the automation side of the system and making significant progress there. From their blogs and code review site, it looks good.

Here's a thought though, when I place the English version of the index on the Internet, I could have the Google translator do a translation for a few dozen languages. This would not be a translation of the actual Urantia Book in that language but simply a word for word translation matching the English page information in the English version. Not sure how useful that could be but I think it could be done pretty easily. Just a thought.

Break time

I'm working on the automation side of the system so theres not much news to blog about except, of course, that I'm waiting on Native Client to release it's first beta. The last release had very little I could use to further the Virtual Urantia system along.

When I realized that very few people were willing to download and install the system, it became clear to me that it had to work on the net without installation. I began to concentrate on how to get it working there. After a few failed tries with 3d platforms running on the net, I began to feel that maybe it would take decades to get it working.

The problem, you see, is that no system existed on the net that would allow the system to run properly on the net. The only system viable was Active X on Microsoft Windows. I'm a cross platform kind of guy, that is, what I develop has to run across multiple types of computers so I won't create software that is that limited to only Windows. I am committed to this decision.

Imagine my excitement when I found that Google was releasing a cross platform client that would take my software and run it across multiple types of computers, even cell phones based on the ARM processor brain.
So now I am playing a waiting game with this Native Client system. When they release, I'll be able to take the Virtual Urantia system and place it on the net. After looking at some the work on the initial non protected tests they ran on this Native Client, I am certain it will work.

Till then, I'll concentrate on the utilitarian side of the system, which will allow me to release a fully animated and automated 3d view of your home, business, building, human body or Power Plant over the Internet. I am quite confident it will help the world see in ways we could only dream of, the world of sensors mixed with artificial intelligence and 3d.

Break Time

Did some preliminary work to see what kind of problems I'd have creating a word index for the french and spanish version. Turns out it's minimal so I plan on having a go at that as soon as the English version is working well. I'm taking a break away from the Urantia side of  the system now to concentrate on the automation side. The 3d menu is working well so everything is on track for Native Client.

Menu Pictures

Most of the menus are working now. Buttons appear at the bottom of the screen that can be clicked to do various things on the screen. These are all in 3d.They appear and disappear depending on which buttons are clicked. A small button appears at the bottom right of the screen when the screen is touched. When it's touched, the menu  appears and disappears.

Wow, it sure takes a long time to create the little pictures on the top of the buttons. I'll be working on some effect when they're clicked.

Figured out how to present the word index screen on small cell phone screens. When searching for a word in the book, just a few things will appear on screen relating to the word(s) chosen. First a list of all words in the book that changes as they type in the words in an edit box.

Also next to the edit box is the amount of paragraphs, the combination of words appear in the book. All these are working and are instantaneously updated.

They'll be three more windows that appear. The reference table showing paper, section, subject and is clickable.

The third window will be a list of paragraph with all text with words searched for highlighted.

The fourth screen is the full book text. Here using a tree, you can jump immediately to any section of the book.

These work just fine in the desktop world but not on a small screen so each screen is separated according to function.

Soon now, Native Client will give me the power to do this. There will be problems at first. One big one will be the time it takes to show the initial program screen whenever I update the program.

Until Google supports separating the programs in pieces, the entire program will download the first time its accessed. To keep that from hindering the user, I'll place revisions on new separate pages. That way, you'll know you have a small wait time for the latest changes to take effect. When they have upgraded to this capability, the wait will be shortened significantly.

Want to mention that I can see very few issues with indexing and using the index with different languages. The program will work pretty easily when creating for Spanish, French or whatever.

Menus,menus, menus

Well, I'm still waiting for Native Client to release it's file and 3d version so I'm creating the menu system that will work on mobiles and desktops alike. That means you can't put a lot of information on the screen at the same time. For instance: If you have a word to look up in the book, the small amount of real estate on the phone keeps you from putting all the references for that word on the screen so a compromise is needed.

First you put the information on just the word like how many times it appears in the book and maybe a small list box that shows all the words in the book and stopping at the closest word being typed in so they know how to type in what's already in the book along with a couple of buttons, one for direct references in a list and the other for paragraphs where they appear.

When they press the button for paper, section and paragraph references then you then place that list on the screen. If press the button for direct paragraph references then you put all those paragraphs on the screen where they appear together and highlight the words chosen. Here we can put a button to enlarge or shrink the text. You really need that feature on a small screen, especially when you ask for the whole book to read. Those settings are saved locally so that whatever computer you're on, it'll remember the text size.

Anyway, I have the scene selection, scene design, system help  and the like on screen with buttons on the bottom of the screen that can scroll when there are more menu items than what can show. there's a few bugs left but I'm sure I'll be handling them in the next few days.

I hope they release 3d at the same time as file access as the menus are all 3d based buttons. I still don't have any pictures on them (textures as they call them), just the text below the buttons so I'll have to get that working after I have a stable menu system.

Also wanted to mention. I think I can create an Spanish and French index pretty easily using the same software so I think I'll have those on a different URL page. We'll see.

Nothing but fun here.