Control | Upload Studio MX 2004 extends site management functionality to each software, taking into account the team's requirements for versioning, as with Dreamweaver, new versions of Flash and fireworks are added to the Site file management feature. However, the site functionality of the Fireworks MX 2004 is consolidated in Dreamweaver MX 2004, which means that the two can only work together, and separate fireworks MX 2004 cannot manage site files. Here's a quick look at the file versioning and FTP management in fireworks MX 2004.
first, the establishment of the site
Maybe some friends have noticed the file Management button in the FW,
But a lot of people will find it's grey and unusable, this is because we have not established a usable site, or our current file is not in an identifiable site, using the FW site management function, first must establish a FW identifiable site, and this site is built by DW to do, So let's start by building a site in the DW. FW requires that the site established in the DW must contain a definition of a remote site, as shown in the following figure:
In addition, FW can only recognize remote sites defined by FTP or local/network transfer mode, and other transport-defined sites cannot use the FW file management feature. So we can only choose the FTP or Local/network way to define, we use the FTP method here to define. The method is simple, just define the FTP address of the remote site, username and login password, as shown below:
Second, the Enable file check in and check out option must be checked to use version control of the file, that is, check in/check out. Check out name represents the name of the owner of the file.
What needs to be explained is that if you use the Local/network way to define a remote site locally, please remember not to use the same directory with your local site, otherwise FW edit the file will cause file unusable, graphics information lost.
Ii. Check out of the document
OK, after defining the remote site folder, we open a file contained in this site, at which point we can see that the Site Management button in FW can be opened.
At this point, you can select Check out, so you can check out the file from the server and pass the relevant owner information to the remote server, as shown in the figure:
Then we switch to DW, open the Site Management window, find the file just edited, we can see the file owner's information has been shown,
Remote folder:
Local folder:
At this point the file has been marked as Mengjue by FW, it is like other members of the team to pass a message, the file is being Mengjue edit, do not modify.
Third, check in of the file
When the file is modified, you can use the check in command to transfer the file back to the remote server.
Now let's take a look at the remote folder:
The checked out flag behind the logo.png has disappeared, which means that no one is currently operating on the file, and others can modify the file.
Look at the local folder again:
At this time the logo.png in front of a small lock, indicating that this file has been modified on the server side to prevent you from making changes to the local files, the next time you modify the file, you need to check out the file from the server to be back before you can unlock the local file.
iv. FTP Management of files
Well, the file version management is so simple. Let's look at the FTP feature in FW again.
This is simpler, get is to retrieve the file from the server side, put is to upload the local files to the server side. As if there is nothing to say, the overall feeling of the speed of the FTP general, but FW FTP management is to deal with a number of small graphics files, so the speed of transmission can be counted.
I am just a personal site for the function of the introduction, in fact, this feature was originally for the team work and custom-made, so when the team uses this function, you will realize its true meaning, each of the files on the server will have editor information, so that you can have a clear understanding of the ownership of the document. The loss of information that has often been caused by multiple edits of the same file will not happen again.
