new FamilySearch Suggestions
- thedqs
- Community Moderators
- Posts: 1042
- Joined: Wed Jan 24, 2007 8:53 am
- Location: Redmond, WA
- Contact:
-
- Community Moderators
- Posts: 3827
- Joined: Thu Jan 25, 2007 11:32 am
- Location: Dundee, Oregon, USA
I'm curious as to what would be the purpose of the plugin, as in what would the plugin do that can't be done with a vanilla browser?thedqs wrote:Maybe a speed enhancement or plugin that works with the site? But if it is a plugin both IE and Firefox have the ability to add plugins.
For speed enhancement, during the early 2007 beta test, the vast majority of the slowness appeared to be the servers, not the browser. (I was using Firefox under Linux on decently-powered but not blazingly-fast hardware.)
- thedqs
- Community Moderators
- Posts: 1042
- Joined: Wed Jan 24, 2007 8:53 am
- Location: Redmond, WA
- Contact:
-
- Community Moderators
- Posts: 3827
- Joined: Thu Jan 25, 2007 11:32 am
- Location: Dundee, Oregon, USA
- thedqs
- Community Moderators
- Posts: 1042
- Joined: Wed Jan 24, 2007 8:53 am
- Location: Redmond, WA
- Contact:
I think so, but I've seen tons of other plugins that could have been done just through an API and some sites that have both. It just allows different ways to interface with the site. Of course the plugin could just be a refined search that uses the local computer a lot more efficently then a web server could by itself.
- David
-
- Senior Member
- Posts: 773
- Joined: Tue Jan 23, 2007 2:03 pm
First, I was not aware of the browser extensions that are available for MSIE, but if there is to be one for NFS, both browsers should be supported. Maybe what we need is not a custom browser, but an extension or two.
I'm thinking along the lines of something that would help the user navigate or do certain things WITHIN the website. I'm thinking that the API is probably going to be for external things and for going back and forth between the user's computer and the site. Almost like maybe a toolbar and some functionality and shortcuts to make the use of the site easier and allow one to do things faster.
Maintenance: If the browser extension were programmed right, all that would have to be done is update small parts of the code rather than do it wholesale, the kind of thing that would and could be done in a day or two, hopefully less. I would not want it to become fatware, and actually cause more problems for everyone than it is worth, that would be counterproductive anyway.
I'm thinking along the lines of something that would help the user navigate or do certain things WITHIN the website. I'm thinking that the API is probably going to be for external things and for going back and forth between the user's computer and the site. Almost like maybe a toolbar and some functionality and shortcuts to make the use of the site easier and allow one to do things faster.
Maintenance: If the browser extension were programmed right, all that would have to be done is update small parts of the code rather than do it wholesale, the kind of thing that would and could be done in a day or two, hopefully less. I would not want it to become fatware, and actually cause more problems for everyone than it is worth, that would be counterproductive anyway.
-
- Community Moderators
- Posts: 3827
- Joined: Thu Jan 25, 2007 11:32 am
- Location: Dundee, Oregon, USA
Java code to process FGR pages from NFS
In case it might be of some use to someone, I have some Java code I wrote that can process Family Group Record pages in HTML saved from the New FamilySearch site. The code modifies the links and such in the HTML to make the page more easily viewable from local disk, including adjusting the links that navigate to the previous and next generation so they will work with local files (assuming the files are named according to the convention the code uses). The code also generates a couple of kinds of pedigree views to facilitate getting to the FGR pages and indexes by first name, last name, and title.
The code is in works-for-me state on LInux using pages from the Spring 2007 NFS beta test.
(Apologies for posting this message in two threads. There doesn't appear to be a cross-posting mechanism in this Forum as there is for Usenet newsgroups.)
The code is in works-for-me state on LInux using pages from the Spring 2007 NFS beta test.
(Apologies for posting this message in two threads. There doesn't appear to be a cross-posting mechanism in this Forum as there is for Usenet newsgroups.)
-
- New Member
- Posts: 30
- Joined: Fri Jan 25, 2008 10:09 am
- Location: Salt Lake City, UT
As far as I understand, there will be no access past 1500 AD, meaning that the royal lines are also disallowed from editing. I've heard rumors that the medieval family history department is working on a master file for royalty and biblical lines, but I haven't heard anything concrete, anyone have more info?rmrichesjr wrote:Another suggestion I just made through "Send Us Feedback" is to consider an official, sanctioned project to do merging and cleanup of Biblical generations. A check in the beta system of people from Adam and Eve to the 12 sons of Jacob/Israel seems to show a huge number of duplicates back this far. With the enormous number of people who link or will eventually link to these ancestors, I hate to think of the (bigger) mess a bunch of fumble-fingered folks like myself could make of these records.
-
- Community Administrator
- Posts: 34419
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.