Re: [Ldsoss] Re: Ldsoss Digest, Vol 39, Issue 23
I spoke with him. Gizmo plugin is called GizmoCall and is flash 9.0 based. There is a Linux version of Flash 9.0 and it should work but the problem is that Flash 9 for Linux needs to take over the sound device which many times it cannot do. I've not played with it enough to know if there is a work around yet. Tom Prince Ensign wrote: I'm really not sure what the Issue is, except that apparently it dosn't work. Gizmo Project and SIPPhone is a great product, BTW, tell him thanks for me :) -James Lee Vann On 30/04/07, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Send Ldsoss mailing list submissions to ldsoss@lists.ldsoss.org mailto:ldsoss@lists.ldsoss.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.ldsoss.org/mailman/listinfo/ldsoss or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of Ldsoss digest... Today's Topics: 1. Re: Re:Gizmo Click to Call SpicyWardWeb (Tom Welch) -- Message: 1 Date: Mon, 30 Apr 2007 07:06:18 -0600 From: Tom Welch [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Subject: Re: [Ldsoss] Re:Gizmo Click to Call SpicyWardWeb To: LDS Open Source Software ldsoss@lists.ldsoss.org mailto:ldsoss@lists.ldsoss.org Message-ID: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed I will forward the issues with the Linux client to the founder and owner of SIP Phone who is a good friend of mine. He also was the founder of Linspire and is a big Linux fan. Tom Prince Ensign wrote: Thanks, the click to call feature works very well. For those of you who don't know, you can use the Gizmo click to call without installing a client on your computer- it runs in the web browser. The voice quality is superb (if you have a fast enough internet connection). I was wondering if it would be possible to make the script work with the Gizmo Project Client software? This would fix the Windows and Mac exclusivity problem, because Gizmo has a Linux client. (I wonder why the web client won't work in Linux?) The web client is great, especially for people who don't want to install more software to simply make a call. -- James Lee Vann Chief Technology Architect www.ensigntech.com http://www.ensigntech.com http://www.ensigntech.com ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org mailto:Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss -- ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org mailto:Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss End of Ldsoss Digest, Vol 39, Issue 23 ** -- James Lee Vann Chief Technology Architect www.ensigntech.com http://www.ensigntech.com ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss -- Tom Welch [EMAIL PROTECTED] (801) 240-1609 (801) 682-5449 - Cell -- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
Re: [Ldsoss] PHP remote development environment
Tom, You might like to do your development/testing online in a separate directory (or virtual host, if you can). This is mostly for after you've released something that is being used. It's a safer way to develop - you won't have to worry what you break when you save a file that might contain a syntax error. Then, get into the habit of copying data into the live directory from your development/testing area(s), or use CVS for revision control. I do a lot of development this way. Because it's online, you can jump from computer to computer. Also, the development/testing enviroment(s) are so similar to the live environment that you won't have to worry about compatibility issues between them. Good luck! Mary On 4/30/07, Thomas Haws [EMAIL PROTECTED] wrote: I guess I neglected to say I am still Windows-bound. That's still no excuse for not setting up a local development environment, but the fact I jump from computer to computer is a good excuse. Here's what I think I will be happy with for the moment: 1. Install WinSCP and Notepad++ (my current editor of choice) on each computer. Edit files remotely almost as though they were local. WinSCP allows me to double-click on remote file(s) to edit it/them, then save and test without closing my editor. 2. Make a pseudo-menu cheat sheet for vi survival that looks and thinks like a Windows/Mac application. Put it on the web so I can always access it in the rare case I need to vi. Tom ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss -- Mary Shaw Internet Consultant http://www.stitchsoft.com ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
Re: [Ldsoss] PHP remote development environment
Well, as I mentioned on this list, I'm hiring an on-call professional consultant to mentor and assist with these things. Perhaps I could have him/her get me set up with SVN. My application is already being used by the executives at my non-profit, so breaking it is not a happy thought. I will work on getting a dev directory and maybe a dev database set up. Thanks for the great reminders and suggestions! Tom On 5/1/07, Bryan Murdock [EMAIL PROTECTED] wrote: On 5/1/07, Mary Shaw [EMAIL PROTECTED] wrote: Tom, You might like to do your development/testing online in a separate directory (or virtual host, if you can). This is mostly for after you've released something that is being used. It's a safer way to develop - you won't have to worry what you break when you save a file that might contain a syntax error. Then, get into the habit of copying data into the live directory from your development/testing area(s), or use CVS for revision control. I would say _and_ use CVS, not _or_. If you aren't using revision control already, you really should, you'll love it. Actually, I wouldn't say use CVS, I'd say use SVN (Subversion), or even better, one of the new distributed revision control systems. Bazaar (bzr) works best on windoze right now, I think. They are a lot easier to get up and running with. An example with bzr (it's a command-line thing only right now) cd c:\path\to\project bzr init bzr add bzr commit -m initial import Now you are ready to make changes to your code. bzr diff will show you what you've changed. bzr commit will commit the changes to the revision history. If you really mess up, you can go back and get previous revisions. Bryan ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss -- Tom Haws 480-201-5476 Have a beautiful day. ___ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
