RE: development environments

2003-09-09 Thread Greg Luce
, 2003 5:01 PM To: CF-Talk Subject: RE: development environments In reality, you CAN use FuseBox with Contribute users. You may not be able to break your dsp_ fuses down as much as you might otherwise, but you can certainly do it. Set up your site so that all your dsp_ fuses are in one place

Re: development environments

2003-09-09 Thread Deanna Schneider
The only caveat is that you have to prevent your Contribute users from doing anything between the time you download their work, and push the new application, but that shouldn't be a big deal. Nice thought and all, but we're a pretty far-flung shop, geographically. Our Contribute users are all

Re: development environments

2003-09-09 Thread Deanna Schneider
- Original Message - From: Dave Watts [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Monday, September 08, 2003 6:08 PM Subject: RE: development environments Dave, you've hit on one of the key reasons Deanna is asking. We also are trying to support Contribute users on the same sites

development environments

2003-09-08 Thread Deanna Schneider
We're thinking about how we do development around here, and I'm wondering what other folks do. Right now, we have windows share access to the development server, and we work directly on it. We're thinking that in the future it might be better to have each developer run the development version of

RE: development environments

2003-09-08 Thread Shawn Regan
] Sent: Monday, September 08, 2003 12:42 PM To: CF-Talk Subject: development environments We're thinking about how we do development around here, and I'm wondering what other folks do. Right now, we have windows share access to the development server, and we work directly on it. We're thinking

RE: development environments

2003-09-08 Thread Samuel Neff
-- Blog: http://www.rewindlife.com Chart: http://www.blinex.com/products/charting -- -Original Message- From: Deanna Schneider [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 3:42 PM To: CF-Talk Subject: development

RE: development environments

2003-09-08 Thread Mike Brunt
Deanna, we also use LDAP for authentication and we use MKS for version control. We have three environments Development, QA-Staging and Production. Development is where the developers keep their code base. We use Fusebox as a framework and good planning at the Application Architecture phase

RE: RE: development environments

2003-09-08 Thread Mike Brunt
/charting -- -Original Message- From: Deanna Schneider [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 3:42 PM To: CF-Talk Subject: development environments We're thinking about how we do development around here, and I'm

Re: development environments

2003-09-08 Thread Massimo, Tiziana e Federica
I prefer to have one single development server shared across the team, with people working directly on it. But we are a small team (4 guys). I just would just suggest to avoid DW's checkin/checkout, it's very primitive (can I say it's a joke?), get a real version control system, with versioning

RE: development environments

2003-09-08 Thread Samuel Neff
Message- From: Massimo, Tiziana e Federica [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 4:19 PM To: CF-Talk Subject: Re: development environments I prefer to have one single development server shared across the team, with people working directly on it. But we are a small team (4

RE: development environments

2003-09-08 Thread Ian Skinner
: Samuel Neff [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 1:46 PM To: CF-Talk Subject: RE: development environments Doesn't DW's checkin/checkout require a SCC compatible backing server like VSS or CVS/Igloo? Sam -- Blog: http

RE: development environments

2003-09-08 Thread Dave Watts
Doesn't DW's checkin/checkout require a SCC compatible backing server like VSS or CVS/Igloo? No, it can be used all by itself, as long as everyone's using Dreamweaver (or Contribute). It's very primitive, and essentially consists of Dreamweaver creating .LCK files on the filesystem for you.

RE: development environments

2003-09-08 Thread Barney Boisvert
: 360.647.5351 www.audiencecentral.com -Original Message- From: Samuel Neff [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 1:46 PM To: CF-Talk Subject: RE: development environments Doesn't DW's checkin/checkout require a SCC compatible backing server like VSS or CVS/Igloo

Re: development environments

2003-09-08 Thread Massimo, Tiziana e Federica
No, there is a simple/primitive/joke (depending on who you ask) built in check in/out function in DW. DW can also integrate more mature products such as VSS if you have one. DW only integrates with VSS or Webdav, no other produuct. Once a year, since at least 3 years, I ask for CVS support.

Re: development environments

2003-09-08 Thread Kevin Graeme
in.) -Kevin - Original Message - From: Dave Watts [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Monday, September 08, 2003 4:03 PM Subject: RE: development environments Doesn't DW's checkin/checkout require a SCC compatible backing server like VSS or CVS/Igloo? No, it can be used

RE: development environments

2003-09-08 Thread Barney Boisvert
-Original Message- From: Kevin Graeme [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 2:34 PM To: CF-Talk Subject: Re: development environments Dave, you've hit on one of the key reasons Deanna is asking. We also are trying to support Contribute users on the same sites

Contribute (was Re: development environments)

2003-09-08 Thread Matt Liotta
In reality, you CAN use FuseBox with Contribute users. You may not be able to break your dsp_ fuses down as much as you might otherwise, but you can certainly do it. Set up your site so that all your dsp_ fuses are in one place (probably in a directory structure mirroring your circuit

RE: Contribute (was Re: development environments)

2003-09-08 Thread Barney Boisvert
, 2003 3:17 PM To: CF-Talk Subject: Contribute (was Re: development environments) In reality, you CAN use FuseBox with Contribute users. You may not be able to break your dsp_ fuses down as much as you might otherwise, but you can certainly do it. Set up your site so that all your dsp_

RE: development environments

2003-09-08 Thread Dave Watts
Dave, you've hit on one of the key reasons Deanna is asking. We also are trying to support Contribute users on the same sites. So we are looking for an environment or process that will support the Contribute file management as well as the CF developers. That means we can't use FuseBox or

RE: Contribute (was Re: development environments)

2003-09-08 Thread Matt Robertson
Barney wrote: Ironically, I've found that it's the more technologically adept people that struggle with the content/presentation separation. As have I, but Matt's point is well-taken. People have no trouble with the separation because they've never seen anything like what he's talking about.

Development Environments

2000-11-17 Thread Craig A. Zingerline
Hello, What do most companies do as far as having a team-based development environment? We have a small team of developers sharing multiple projects and do our work on Win98 platforms and map to our NT server through CF Studio to write code. All of our beta sites are put there to make sure

Re: Development Environments

2000-11-17 Thread Scott M. Berry
://www.annex.com/ - Original Message - From: "Craig A. Zingerline" [EMAIL PROTECTED] To: "CF-Talk" [EMAIL PROTECTED] Sent: Friday, November 17, 2000 4:55 AM Subject: Development Environments Hello, What do most companies do as far as having a team-based development e

RE: Development Environments

2000-11-17 Thread Stewart McGowan
you MUST use version control even if one of you works on the code alone, it has many more functions than just file sharing, the ability to roll back to a version that did work, (sometimes days upstream) is invaluable. It can also help you learn how your project progressed and therefore how your

RE: Development Environments

2000-11-17 Thread Duane Boudreau
AM To: CF-Talk Subject: RE: Development Environments you MUST use version control even if one of you works on the code alone, it has many more functions than just file sharing, the ability to roll back to a version that did work, (sometimes days upstream) is invaluable. It can also help