Right now im in phase of trying out Linotype FEX 2 Pro trial version. So there would be no problem at all to buy any of these updates for me. Well, the situation is that, that i already own a Fusion 11 license (for both Mac an Win) and also a FAP 3 license. The newer CS4 plug-ins do not work with the free FEX 1.2.3. FEX is pretty seamless and worth a try though.īTW, tested the FEX upgrade work-around on my home MBP and it doesn't work, so don't waste your time if you know about it. Personally, I went with FAP since it's a more mature, proven program and I need to make sure our stations are productive and not bogged down with issues. So, I would recommend avoiding Fusion, which I know there are content users, but with over 16 years in advertising and being a long-time Suitcase user, it just never was a good program compared to others. We bought FAP4 multi-seat licenses at 40% cross-grade discount (same as FAP3 to FAP4 price). I asked if they had upgrade or competitive/cross-grade pricing and they do. Told them I was a previous user forced to go to Fusion. I feel this is the king of font managers and requires little to no babysitting.Ĭons: None except for price, more expensive than FEX, but. Pros: Loved this before, demo was awesome. Still a young program and involves some interactions (less than Suitcase). $40 for limited time (50% off)Ĭons: Free not compatible with CS4, must use paid version. Pros: Good as a free program, better as paid (demo'd). Also requires 10.5 which we are on 10.4.11 and that upgrade isn't an option at the moment. Now to this past 2 weeks, as i said we upgraded to CS4 so I started researching before doing it company-wide. On my personal MBP, I use(d) FontExplorerX (FEX) and was surprised at how good it was for being free. Again, while Extensis did improve it, I really hated using Fusion (since we paid for multiple seats). When we upgraded to CS3, we had to go with Suitcase Fusion since FAP was not compatible yet. Moved to FontAgent Pro (FAP) and was extremely happy, few problems over many years. Used Suitcase since Adobe kill theirs and hated every minute of it. I've personally used all of these over many years. They just seemed to care more about their product and providing a good experience.We just upgraded to CS4 so this is a fresh subject for me. I always preferred their solution to the Extensis offerings myself. Good news is, I think there is a separate pkg in the download for just the plug-ins that I was able to push via ARD at the time that would fix that. I had made the mistake once or thrice of doing the installs in the reverse order. (Hmm, was it a burger?)Īs for the CS plug-ins, I can say that FontAgent Pro has always been pretty good at recognizing the installed applications and injecting the plug-ins into the proper locations, as long as Adobe CS and/or QXP are installed before the FAP Client of course. I'm lucky I remember what I ate for lunch yesterday. Unfortunately, actual memories of what I did are very fuzzy. Not sure about the server credentials and AD link. I seem to recall that I was able to bake a registered version into my crude imaging setup at the time, so I would say its probably possible to deploy a license file as part of your package. This was version 3 I believe and I touched a little on version 4. I worked with FontAgent Pro Client and Server some years ago, but it was before my Casper Suite using days, so no real automated deployment. Is this something the users will need to handle (oy, I hope not as not all users are admins). How is the serial number handled for client/server environments.or is it one of those "don't worry about it, the server is the only thing that needs to be licensed" jobbies?Īlso, is the Client for FAP Server.pkg intelligent enough to look for existing Creative Suite and QuarkXPress applications so it can install the required Plug-In or Xtension? The preupgrade/preinstall/postinstall/postupgrade scripts in Client for FAP Server.pkg only seem to shut down the running process and remove old versions. I'm fairly certain they'll ask us to package/deploy preconfigured to point to the FAP Server so I'm hoping someone here can enlighten us on what files (or commands?) need to be put into our wrapper so when we deploy it the users will not be prompted for the FAP Server address (FQDN). Pushed to logged off computer without a problem. A quick peek at the Client for FAP Server.pkg raises no flags, it's actually a pretty clean package. A few of the groups we support use FontAgent Pro 5 (server/client), so we're looking at packaging it for distribution.
0 Comments
Leave a Reply. |