Well it knows where to find things like the php, ruby, python, perl interpreters since they are most always in the path on linux. And if you click to preview in browser it gets the paths correct. Thats about the only noticeable differences. We have a windows box that is running vnc server that we remote connect to to test in IE. That works out well.
-Kevin- On Fri, May 2, 2008 at 11:31 AM, Nathan Lane <[EMAIL PROTECTED]> wrote: > Thanks Kevin. I'm going to try it on Linux. The biggest problem with using > Linux right now as our development environment is that a huge chunk of our > customers are Windows users, which automatically means Internet Explorer. > We've though of running a "parallels" sort of setup, but haven't tried it > out yet, in which we'd probably run VMWare Server for Linux and a Windows XP > image. Does Komodo set up more fully on Linux? > > On Fri, May 2, 2008 at 11:26 AM, Kevin Carter <[EMAIL PROTECTED]> wrote: > > > I've been using Komodo for about a year now and love it. It is a little > > finicky on windows (but so is apache and php). You wouldn't of had to tell > > Komodo where your php interpreter was had it been within your path. But that > > isn't something php sets up by itself on windows. Most likely your problem > > with apache is that windows uses \ as its directory separator and apache > > uses /. It works awesome on a Linux desktop. For basics really all you need > > to do is create a new project within wherever your code is. > > > > -Kevin- > > > > > -- > Nathan Lane > Home, http://www.nathandelane.com > Blog, http://nathandelane.blogspot.com > _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
