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.
-dallan
Does the pedigree manager have to be in Flex? Why not AJAX out of curiosity? AJAX is much more open IMO, and promotes others to learn how you wrote the code.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jesse Stay
Sent: Monday, July 10, 2006 1:32 PM
To: LDS Open Source Software
Subject: Re: [Ldsoss] Bounties, BarCamps, etc.
Jesse
On 7/10/06, Dallan Quass <[EMAIL PROTECTED]> wrote:I'm willing to do open-source programming and even sponsor open-source
programming for family history. I'd like to get responses on what people
think is the most effective way to get started. Here are some ideas; I'm
interested in feedback on these ideas and other ideas.
(1) BarCamps. I could attend and help sponsor the BarCampUtah that Phil
Burns is putting together if others interested in doing open-source
programming for family history are planning to attend.
(2) Monthly meetings. I could possibly organize a monthly meeting where
people could get together to coordinate work on open-source family history
projects. The meeting could either be in-person (Utah Valley, with food),
or online (Skype/IRC).
(3) Bounties. A bounty is a small payment offered for someone to develop a
particular feature on an open-source project. I could offer bounties for
example on a MediaWiki (Wikipedia) <flickr> tag handler that would display
thumbnails of images from flickr on wiki pages, a MediaWiki <blog> tag
handler to display the posts from a blog (rss feed), or an online
(implemented in Macromedia Flex) pedigree manager.
-dallan
_______________________________________________
Ldsoss mailing list
Ldsoss@lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss
--
#!/usr/bin/perl
$^=q;@!>~|{>krw>yn{u<$$<Sn||n<|}j=<$$<Yn{u<Qjltn{ > 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
