Topic: Working in Dreamweaver

[Peter Thalmann]

Hi list,

I was just trying editing files for a site in dreamweaver. I have the choice of editing localy or directely on the server. But an ftp to the primary directory where the site is stored does not work. So , how can I ftp into the primary directory, the site's root , and work in dreamweaver ? Even timesyncro does not work, dreamweaver complains not being able to syncronise?

Cheers,

Peter Thalmann

[Pat Erler]

both errors mean the same - you didn't login correctly into the server (maybe just a wrong pw).

use these settings (dreamweaver MX):

Access FTP
FTP Host: yourhost
Host Directory: /primary/html/
Login: admin
Password: youshouldknow


that's it...

PAT

[J.C. Meijers]

If you're interested, we're working on a set of Dreamweaver MX extensions for integration between Dreamweaver MX and E-smith (control panel and control functions through DW floaters, site profile integration, auto-ibay creation upon new site definition, etcetera).

Although these are extensions which we are doing for internal usage sofar, if there is enough of a base for this we can release them on the Macromedia Exchange.

I don't know if other people use E-smith as a staging ground for development through DW, if you use Dreamweaver and E-smith; we're interested in your experiences.

[Pat Erler]

J.C. Meijers wrote:
>
> If you're interested, we're working on a set of Dreamweaver
> MX extensions for integration between Dreamweaver MX and

> I don't know if other people use E-smith as a staging ground
> for development through DW, if you use Dreamweaver and
> E-smith; we're interested in your experiences.
although i don't use e-smith as a test server for my DW projects, we use it as our in-office server. so, if you need a beta tester, contact me by email, i'm interested, yes...

regards

PAT

[J.C. Meijers]

I have to say that we do not have a policy for external beta testing, so I doubt we could do anything there for now. I'll take it up with my team anyway to see if something is possible anyway.

We use e-smith a bit differently: while we use e-smith as team specific in-office servers we rely on Dreamweaver which we have extended ourselves to work as a work environment besides being our core development IDE, we run Outlook in a Dreamweaver floater and any other application which may be needed (long live multi monitor setups). But e-smith/DW integration has come up only after we figured out how to control and instantly deploy apache servers or remote boxes through Dreamweaver (just try running another apache instance next to e-smith-httpd). So we can set all environment variables on a project specific basis, and that is where DW/e-smith integration began. Our goal is to provide our teams with a set of e-smith servers which can be controlled through DW on all levels while A) not interfering with e-smith specific settings and B) still being able to create and run parallel apache instances with corresponding environment variables.

But to be honest, this was not what e-smith was intended for so we have yet to decide (after hearing from Mitel what is legally allowed) whether we will pursue integrated development/work environment integration with e-smith or other server appliances/applications.