Adobe Web Products - Was: [Casper] (no subject)

[Ernst, Craig S.]

The formerly known as Macromedia products are integrated with the suites. The biggest dependency is the licensing database that manages all the applications. That is the common part to all of them, whether it's CS3 Design Premium or CS3 Web Standard (which only adds Fireworks and Contribute to what's already in Design Premium).

The issue, and I'm sorry if I'm repeating, is the licensing database, it's not really designed to handle modular packaging, well. The other shared files aren't really a big issue.

For example, let's say you wanted to deploy CS3 Design Premium. Ok, so you pack up CS3 Design Premium and push it out. Now you decide you want to add in the two pieces of CS3 Web Standard, so you make a pack of those, and then deploy that. Well, you broke your Design Premium install because the licensing database was overwritten that had the Design Premium license information in it with a licensing database that only has Web Standard information.

How do you get around that, well that's why we have to make an Adobe-Required package out of both suites. We have to install Design Premium and install Web Standard, fire up all the applications, enter the licenses for both suites, and then pack it. We break out the applications into packages and leave the rest as the Adobe-Required pack. Now we can deploy just what the end user wants. If they want Dreamweaver and Photoshop I can push out DW, PS, and the Required pack (mainly to save disk and bandwidth). Keep in mind that they are still eating up a Design Premium license.

Now if this method doesn't sit well you can do some xml scripting (I think) of some sort (it's what the installers do when you install the software) to handle updating the licensing database correctly to deploy packages if you didn't want to pack them all together, but I don't know anything about that. It all boils down to the licensing database (that's the problem) and if you plan to use multiple licenses. If not, no worries.

Craig


On 6/11/07 7:01 AM, "Daniel Farnworth" <daniel.farnworth at thecreativepartnership.co.uk> wrote:

Just following up from this, now that Adobe own all the old Macromedia
products, how does this affect packaging of Flash, Web Studio etc?

Does it follow, that these now rely on the same common files and shared
libraries that the other CS apps (Pshop etc) do?

Should we follow the same procedure no matter what Suite?

Cheers
Dan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.intermedia.net/pipermail/casper/attachments/20070611/1bdb9ce9/attachment.htm