Re: [Ldsoss] Bounties, BarCamps, etc.
On Mon, Jul 10, 2006 at 04:21:02PM -0600, Jesse Stay wrote:
I'd love to pick it up, but the process may be a slow one - I've got 2
contractual things going on at the same time right now. Let me know what
you've got and I'd love to build a client for it.
The whole webservices thing is built on Gedcom.pm. It hasn't had a
proper release yet, but you can access my subversion repository at
http://pjcj.sytes.net/svn/Gedcom/ It seems to work quite well for me,
and a couple of other people have reported success, but it will no doubt
need some work when a real client starts to use it.
At the moment it uses apache 2 and mod_perl, though I suspect this could
be changed without too much hassle if you wanted to.
If you don't already have these available, or if you would prefer to
have a separate installation for this work (which is what I do), there
is a build script in the install directory which will build perl,
apache, mod_perl and all the perl modules required. If subversion is a
problem, I also have a later version of the build script I have used on
another project which will also install zlib, openssl, and subversion,
along with svk. Let me know if you would like it.
I recommend using svk for the version control since the repository is
sitting on a server in the laundry room (it helps to dry the clothes)
behind a wireless link and a cable modem, but any subversion client
would do. (The server and link are actually quite reliable, but svk is
nice for offline hacking anyway.) Let me know if you would like write
access to the repository. The client doesn't have to live there, but
it's open to you if you would like that.
When everything is installed, make test will run the current tests,
make restart starts the server and make stop stops it.
Hopefully that's enough to get you going. There are some docs in the
WebServices module and I'd be pleased to try and explain what I have
done and why.
Thanks a lot for thinking about this. I'm looking forward to seeing
where it can go. Don't worry about the speed of progress. It won't be
slower than what I've been doing recently. And maybe others would be
interested in joining the effort?
Read access on the repository is open to anyone, and I'd be happy to
give write access to anyone who wants to push changes back. So if
anyone else has been dying to try out this newfangled ajax thing, here's
your chance!
--
#!/usr/bin/perl
$^=q;@!~|{krwyn{u$$Sn||n|}j=$$Yn{uQjltn{ 0gFzD gD, 00Fz, 0,,( 0hF
0g)F/=, 0 L$/GEIFewe{,$/ 0C$~ @=,m,|,(e 0.), 01,pnn,y{ rw}
;,$0=q,$,,($_=$^)=~y,$/ C-~@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
Yes, you'll get on quite well with Gedcom.pm, I think ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
___
Ldsoss mailing list
Ldsoss@lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss
RE: [Ldsoss] LDS Opencontent Directory
Justin R Findlay wrote: On Fri, Jul 07, 2006 at 09:53:53AM -0600, Christopher Phillips wrote: ... Copyright law is seriously b0rk. You have my sympathy for having to regularly deal with it's insanely restrictive terms. According to the New York Times, the verb to bork might be defined as to destroy a judicial nominee through a concerted attack on his character, background and philosophy. (http://www.iht.com/articles/1993/01/13/topi_3.php) Remember Judge Bork? He probably would have been one of the best Supremes... Applying the definition of the word b0rk to Christopher's use of the word regarding copyright, I would have to also agree that copyright is being destroyed through a concerted attack on [its] character. I further agree that copyright opponents are completely vicious and unfair in their attack. ;-) Shane Hathaway wrote: OTOH, copyright law is the foundation for open source software. It clearly has value when applied correctly. Finally, someone realizes the basis for OSS working! Steve ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
Re: [Ldsoss] Bounties, BarCamps, etc.
The whole webservices thing is built on Gedcom.pm.It hasn't had a
proper release yet, but you can access my subversion repository athttp://pjcj.sytes.net/svn/Gedcom/It seems to work quite well for me,and a couple of other people have reported success, but it will no doubt
need some work when a real client starts to use it.Excellent! I'm on your mailing list, and I've used it in developing a gedcom parser app for my extended family before. I'm very aware and impressed with your work! I've heard about the webservices stuff - I'm excited to try it out!
At the moment it uses apache 2 and mod_perl, though I suspect this couldbe changed without too much hassle if you wanted to.
Why would I try anything else? ;-) My license plate does say USEPERL after all.
I recommend using svk for the version control since the repository issitting on a server in the laundry room (it helps to dry the clothes)behind a wireless link and a cable modem, but any subversion clientwould do.(The server and link are actually quite reliable, but svk is
nice for offline hacking anyway.)Let me know if you would like writeaccess to the repository.The client doesn't have to live there, butit's open to you if you would like that.Haven't tried svk yet, but after Jesse Vincent mentioned it being integrated with RT I'm anxious to give it a whirl.
Again, it will be slow progress, but if anyone else is interested in getting their hands dirty with AJAX, let me know and maybe you can help push it forward faster. For those not having done any AJAX that want to learn, might I recommend the Manning book, AJAX In Action - it really gets you in a good mindset for well-written AJAX code.
Jesse-- #!/usr/bin/perl$^=q;@!~|{krwyn{u$$Sn||n|}j=$$Yn{uQjltn{ 0gFzD gD, 00Fz, 0,,( 0hF 0g)F/=, 0 L$/GEIFewe{,$/ 0C$~ @=,m,|,(e 0.), 01,pnn,y{ rw} ;,$0=q,$,,($_=$^)=~y,$/ C-~@=\n\r,-~$:-u/ #y,d,s,(\$.),$1,gee,print
___
Ldsoss mailing list
Ldsoss@lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss
Re: [Ldsoss] LDS Opencontent Directory
On Tue, Jul 11, 2006 at 06:30:16AM -0600, Steven H. McCown wrote: Applying the definition of the word b0rk to Christopher's use of the word regarding copyright, I would have to also agree that copyright is being destroyed through a concerted attack on [its] character. I further agree that copyright opponents are completely vicious and unfair in their attack. ;-) I don't understand why you want to mischaracterize me as a copyright opponent. If there's anything I oppose about copyright it is unmitigated greed and corruption on the part of unscrupulous holders being rewarded by nefarious laws. Finally, someone realizes the basis for OSS working! I submit that I have a good idea of how OSS copyright works. Justin ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
Re: [Ldsoss] LDS Opencontent Directory
I think that using existing repositories is a great idea whenever possible, especially for any type of content that might have values to a bigger audience. However I think there is enough LDS themed content that a completely separate directory would be helpful in order to facilitate the setup of an LDS folksonomy to organize information and make the information more accessible. I am not referring as much to coding projects as I am to things like LDS clip art, object lessons, chapters from books, audio recordings, music, etc... Right now you can go to http://www.commoncontent.org/ and do a search for content tagged 'LDS' or go through the categorial hierarchy to maybe find a religion category with a LDS subcategory, but that would likely be the end of the line. However, with an LDS specific directory you could tag things more specifically and have a more specific hierarchy setup- i.e. Church History -- Prophets -- Spencer W. Kimball... The structure for this type of project could be setup fairly quickly, the time consuming part would be gathering, organizing and tagging content as it came in or preferably setting up a way that the community could self organize. ChristopherOn 7/11/06, m0smith [EMAIL PROTECTED] wrote: Rather than creating an LDS only repository, why not use the alreadyexisting repositories like sourceforge?For family history relatedprojects, the audience for most any project will expand beyond theWasatch Mountains.You could tag a project as LDS if you think its of interest.I already have several projects on sourceforge, includingone called topoged. ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
Re: [Ldsoss] LDS Opencontent Directory
Besides being only for code, sourceforge isn't a model of user friendliness that you would expect Sunday school teachers will need in a site. I'm a proponent of using existing content repositories where possible (not reinventing the wheel). The downside is that sites like commoncontent.org, like any public place, will have a wide range of viewpoints and opinions on every topic, including some LDS-tagged material that wouldn't be appropriate for inclusion in a Sunday school lesson. For an example, type Mormon into Google Video, YouTube, or Del.icio.us. It would be a hassle to minutely examine every article, but some general control over content might be a good reason to do an LDS-specific repository. On Jul 11, 2006, at 11:41 AM, Christopher Phillips wrote: I think that using existing repositories is a great idea whenever possible, especially for any type of content that might have values to a bigger audience. However I think there is enough LDS themed content that a completely separate directory would be helpful in order to facilitate the setup of an LDS folksonomy to organize information and make the information more accessible. I am not referring as much to coding projects as I am to things like LDS clip art, object lessons, chapters from books, audio recordings, music, etc... Right now you can go to http://www.commoncontent.org/ and do a search for content tagged 'LDS' or go through the categorial hierarchy to maybe find a religion category with a LDS subcategory, but that would likely be the end of the line. However, with an LDS specific directory you could tag things more specifically and have a more specific hierarchy setup- i.e. Church History -- Prophets -- Spencer W. Kimball... The structure for this type of project could be setup fairly quickly, the time consuming part would be gathering, organizing and tagging content as it came in or preferably setting up a way that the community could self organize. Christopher On 7/11/06, m0smith [EMAIL PROTECTED] wrote: Rather than creating an LDS only repository, why not use the already existing repositories like sourceforge? For family history related projects, the audience for most any project will expand beyond the Wasatch Mountains. You could tag a project as LDS if you think its of interest. I already have several projects on sourceforge, including one called topoged. ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
Re: [Ldsoss] Bounties, BarCamps, etc.
You might consider the new AJAX Framework that Google has released: http://developers.slashdot.org/article.pl?sid=06/05/17/127214http://developers.slashdot.org/article.pl?sid=06/05/17/127214 Google released a new http://code.google.com/webtoolkitAJAX framework based on Java. From Google's mouth: Google Web Toolkit (GWT) is a Java software development framework that makes writing AJAX applications like Google Maps and Gmail easy for developers who don't speak browser quirks as a second language. This impressive framework promises to make AJAX available to the masses and is one more step towards Google becoming the de facto http://news.com.com/2102-1012_3-5877197.html?tag=st.util.printInternet platform provider. I've been burned too many times with javascript not working cross-browser. Code that I develop that works fine under Firefox has bugs that are difficult to find (for me at least) under IE. I recently had a situation where code that ran fine under IE6 just stopped working one day even though I had made no changes to my code. I assume it was due to an automatic IE update. To test my javascript code I have one machine running IE5.5, one running IE6.0, one running IE7beta, and I wish I still had a Mac machine to test on. With Flex I get a stable VM that's on 95% of browsers where I don't have to worry about browser compatibility. I agree an open platform would be better, but overall it seems like a reasonable trade-off. Also, Flex apps can be made to look cooler due to the built-in graphics effects, like fade - and one of the things I'd like to do is create some online genealogy games someday. I'd consider OpenLaszlo (www.openlaszlo.org) if enough people were interested. --- Bill Pringle work: [EMAIL PROTECTED] http://www.unisysfsp.com http://www.unisys.com home/school: [EMAIL PROTECTED] http://www.personal.psu.edu/~wrp103 http://CherylWheeler.com ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
Re: [Ldsoss] Scout Tracking
On Monday 10 July 2006 10:04 am, Tom Welch wrote: I've used Dia in the past for Linux. I've not used Umbrello but it looks like it should do the trick just fine. Also, to model the data, have you given MySQL Workbench http://dev.mysql.com/downloads/workbench/1.0.html a try? thanks - I will try dia. gety Here are my comments on your data table. Take them for what they are worth...about a nickel and two pennies. * As a general note: If you want to allow for synchronization between a local system and a remote system then all of your primary keys should be in the form of a guid (I use varchar(32)). Most DB's have an auto-increment type for ints and these are used as primary keys but you can't synchronize as easily .. especially if you are allowing for a multi-user system because two keys could get the same value. If your is not to allow for synchronization then I'd let the DB handle the auto-assigning of the primary key. my plan is to use a varchar field as a membership number - good catch - I completely forgot a variable I can use as a common number between dbs. I have been planning to use the record_id as only a local number and to use the auto-increment feature for all the record_ids . The system will be multi-user. * On the people_table, why do you have birthdate and also birthmonth, birthyear and date. It seems that birthdate would handle it and any programming language you use could extract the month/year easily. the date field in each field is to doc when a record was created - that permits versions . I am not sure why I felt the need to doc creation dates. I think the date field will be used to document changes, track other info to prevent complains about data errors. * On the address_table, what is the date field for? Also do we think that we will have multiple addresses for people and so need to keep a separate table for them? I agree if this is to be expected then it would be more efficient to have the addresses in a separate table. Multiple addresses - sure . we have youth living in multiple homes (divorce, boarding schools, etc ), unlisted addresses (shipping address, po box) and other situations. * What is the date field on the phone_table used for? In fact, all tables have a date field. I'm not sure their purpose. I just want to know how old a phone number is - people change phone number every day AND without telling me. If I know how old the number is and what type it is (cell, landline) I can guess the probability of finding a good number when someone has multiple phone numbers * On the Emergency Contact section, I can see that you intend to have a small link table linking boys to their parents or other contacts. My comment here is that it may be a bit of overkill to force the user to enter in all parents and other people that act as emergency contact information into the DB. What I mean is that if I enter in a boy's information (address, phone number, etc) I then have to enter in the same information for his parents so that I can link the boy to the parent. What you end up with is two records with basically the same information. It may be more efficient to create a family table which would consist of the last name of the family and then the address, phone numbers, etc. Then have a family members table which you enter in family members (first name, birthdates, etc). This way you are not double or triple entering in the address. emergency contacts are not always the parents . I also need to add an emergency release passphrase to permit someone to gain emergency guardianship of a youth. * On the authorization_table, why do you have two password fields? You will need to ask for the user to enter in the password twice but that is to just verify that it is entered in correctly. I have the 2 fields to allow the use of a 2 stage password. the 2 stage is not required - it is just available * On the authorization_table, I recommend that you lose the userid and use the email address to verify and allow the user to login. emails change and can be extracted from mailing lists. Using a userid is just a way to obsure part of the info needed to login. * On the Image and Picture tables, would it make more sense to store the data in a blob in the DB instead of having a link to a file? Links are easily broken. I prefer to store images as files - I still do not trust databases as much as I trust filesystems. Also keeping the images as non-blobs keeps the database smaller and allows access to the images with multiple tools (outside of the database). Broken links can be recovered if the pathname/filename naming convention has enough info. Good start Oscar. It is a start. I'll
