I have created on my Talk what a automatic two column generated list would look like:
https://wiki.familysearch.org/en/User_t ... mas_Lerman
In my test, it is less than 15 window pages for this word test. Whereas, the same size window page was 48 pages in the original word list:
https://wiki.familysearch.org/en/Czech_ ... _Word_List
By having it automatically generated, it cut the number of window pages to a third. This is not exactly a 100% good test. Wait, I just tried editing the 'O' section and found a problem. Hmmm, that could be a problem with this. I will have to think about this more. At least you can see what it might look like and how much real estate may be able to be saved.
Alphabetical lists
Moderator: ForbesMM
-
- Member
- Posts: 172
- Joined: Thu Mar 13, 2008 9:54 am
-
- Member
- Posts: 172
- Joined: Thu Mar 13, 2008 9:54 am
The other potential "problem" that I thought about occurs when the window width is too small and the text wraps. Some of the extensions use an unordered list and some others put borders around each set of words in the table to take care of this (kind of, but all the borders add up to taking up valuable space).
This extension would allow three options: number of columns (I am showing 2), border width (showing 0), and percentage table width (showing 100%). If the border is shown, it is around the outside of the table and then a verticle line between the columns. In other words, no horizontal lines between the words. If it were done this way to allow these line, it would take quite a bit more verticle space, processing of the data, and probably RAM on the server.
As I think about it, some of the issues that I have listed may or may not be a problem. I would have to try them out to really test them. It does make me realize that the TOC may need some tweaking as well to allow for custom TOCs (possibly "foreign" characters).
This extension would allow three options: number of columns (I am showing 2), border width (showing 0), and percentage table width (showing 100%). If the border is shown, it is around the outside of the table and then a verticle line between the columns. In other words, no horizontal lines between the words. If it were done this way to allow these line, it would take quite a bit more verticle space, processing of the data, and probably RAM on the server.
As I think about it, some of the issues that I have listed may or may not be a problem. I would have to try them out to really test them. It does make me realize that the TOC may need some tweaking as well to allow for custom TOCs (possibly "foreign" characters).