Adobe is aware of recently published security issues in the Illustrator CS2 Macintosh version that could potentially cause code execution. An attacker would need to convince a user to open a malicious AI file in Illustrator CS2 on Macintosh to successfully exploit the issue. Adobe recommends that customers exercise caution when receiving unsolicited or suspicious files. Adobe is not aware of any information to indicate that this vulnerability has been publicly used to attack customers.
These issues do not affect Illustrator CS3 or the upcoming Illustrator CS4 release.
More information here.
A blog about Adobe Illustrator and design in general
September 16, 2008
September 15, 2008
ASK MORDY: Limitations between Flash and Illustrator
As they are both lumped together in the category of "vector" applications, one can easily assume that objects can be moved freely between Illustrator and Flash. Unfortunately, that is not the case.
Today's question comes in from Elisabeth:
I work for scientists and make presentations for them in Flash. I create the storyboards to go with them in Illustrator. In doing this I often have to copy and paste text from Flash to Illustrator and instead of text I get vector objects. Is there any way to get around this?
The reality is that when it comes to integration between these two powerhouse applications, there's a big fat "one way" sign, and the arrow points from Illustrator and leads to Flash. Try going from Flash to Illustrator and you're faced with a huge "Do Not Enter" sign instead.
Actually, go back a few versions and you couldn't even find a reliable way to go from Illustrator into Flash. While Illustrator and Flash are indeed both vector-based applications, their graphic engines and the way they export those vectors aren't the same. In fact, if you think about it, Flash was built to display artwork in one place, and one place only -- the Flash Player. Even as recently as Flash 8, importing Illustrator artwork into Flash resulted in some pretty ugly paths. In the CS3 release, Flash actually implemented Illustrator's vector graphics engine under the hood, which finally allowed Flash to interpret and maintain the integrity of each anchor point and respective control handle.
To understand the significance of this, take into account the screenshot that appears above. I drew a circle in Illustrator and copied and pasted it into Flash. The circle on the left is how the circle appears when pasted into Flash CS3. The circle on the right is how the same circle appears when pasted in Flash 8. Sweet, eh? In fact, Flash CS3 is pretty intelligent when it comes to pasting content from Illustrator -- live drop shadows from Illustrator become live editable drop shadows in Flash, gradients come in as gradients instead of bitmaps, clipping masks come in correctly, text become editable -- the list goes on.
Here's the thing though -- the code for bringing artwork into Flash was updated, allowing art to move from Illustrator into Flash, but the code for exporting artwork FROM Flash hasn't changed at all. Meaning that while there's a way to get awesome graphics INTO Flash, there's no way to go the other way around. Hence, if you try drawing a circle in Flash and then copy and paste it into Illustrator, you'll get the same result as you see in the circle on the right, in the above image. Likewise, text is also lost when going the "wrong way".
As I mentioned in a previous post, Fireworks CS4 now shares the same text engine as Illustrator does, making it now possible to move text easily between FW and AI -- but sadly, that isn't the case for Flash.
Looking forward, Flash Player 10 (recently released) does have support for something called FTE (Flash Text Engine -- formerly known by its codename, "vellum"), although support for this isn't available within the Flash application itself just yet. I would guess the hope would be that at some point, the FTE technology and the ATE technology (Adobe Text Engine) found in Illustrator, Fireworks, Photoshop, After Effects, etc, would be able to communicate with each other to allow text to move freely between all of these applications.
To wrap up, my understanding is that MOST people need to bring content from Illustrator into Flash, and so that workflow has a higher priority, and those pain points were addressed first. Workflows where designers need to bring content from Flash into Illustrator aren't nearly as common (although I'll admit I've been hearing more people ask for this lately). But since this workflow isn't as mainstream, it doesn't get a high priority at Adobe. If you're a designer and you feel differently, let Adobe know. Either comment here, or contact Adobe directly with your requests (yes, Adobe actually does listen).
Today's question comes in from Elisabeth:
I work for scientists and make presentations for them in Flash. I create the storyboards to go with them in Illustrator. In doing this I often have to copy and paste text from Flash to Illustrator and instead of text I get vector objects. Is there any way to get around this?
The reality is that when it comes to integration between these two powerhouse applications, there's a big fat "one way" sign, and the arrow points from Illustrator and leads to Flash. Try going from Flash to Illustrator and you're faced with a huge "Do Not Enter" sign instead.
Actually, go back a few versions and you couldn't even find a reliable way to go from Illustrator into Flash. While Illustrator and Flash are indeed both vector-based applications, their graphic engines and the way they export those vectors aren't the same. In fact, if you think about it, Flash was built to display artwork in one place, and one place only -- the Flash Player. Even as recently as Flash 8, importing Illustrator artwork into Flash resulted in some pretty ugly paths. In the CS3 release, Flash actually implemented Illustrator's vector graphics engine under the hood, which finally allowed Flash to interpret and maintain the integrity of each anchor point and respective control handle.
To understand the significance of this, take into account the screenshot that appears above. I drew a circle in Illustrator and copied and pasted it into Flash. The circle on the left is how the circle appears when pasted into Flash CS3. The circle on the right is how the same circle appears when pasted in Flash 8. Sweet, eh? In fact, Flash CS3 is pretty intelligent when it comes to pasting content from Illustrator -- live drop shadows from Illustrator become live editable drop shadows in Flash, gradients come in as gradients instead of bitmaps, clipping masks come in correctly, text become editable -- the list goes on.
Here's the thing though -- the code for bringing artwork into Flash was updated, allowing art to move from Illustrator into Flash, but the code for exporting artwork FROM Flash hasn't changed at all. Meaning that while there's a way to get awesome graphics INTO Flash, there's no way to go the other way around. Hence, if you try drawing a circle in Flash and then copy and paste it into Illustrator, you'll get the same result as you see in the circle on the right, in the above image. Likewise, text is also lost when going the "wrong way".
As I mentioned in a previous post, Fireworks CS4 now shares the same text engine as Illustrator does, making it now possible to move text easily between FW and AI -- but sadly, that isn't the case for Flash.
Looking forward, Flash Player 10 (recently released) does have support for something called FTE (Flash Text Engine -- formerly known by its codename, "vellum"), although support for this isn't available within the Flash application itself just yet. I would guess the hope would be that at some point, the FTE technology and the ATE technology (Adobe Text Engine) found in Illustrator, Fireworks, Photoshop, After Effects, etc, would be able to communicate with each other to allow text to move freely between all of these applications.
To wrap up, my understanding is that MOST people need to bring content from Illustrator into Flash, and so that workflow has a higher priority, and those pain points were addressed first. Workflows where designers need to bring content from Flash into Illustrator aren't nearly as common (although I'll admit I've been hearing more people ask for this lately). But since this workflow isn't as mainstream, it doesn't get a high priority at Adobe. If you're a designer and you feel differently, let Adobe know. Either comment here, or contact Adobe directly with your requests (yes, Adobe actually does listen).
September 11, 2008
Remembering September Eleven
I don't normally post things of a personal nature on this blog, but today is somewhat different. I live out on Long Island, and my home is about 20 miles from downtown Manhattan. Last night, I saw the 9/11 memorial lights in the sky (clearly visible from that distance) and I thought I'd take a moment to document my own memory of that day here.
January 2, 2001 was my first day at Adobe as product manager of Adobe Illustrator. It was an incredibly exciting time for me. By June, after the school year was complete, my family had completed the move from NY to San Jose, CA. A culture shock for all of us for sure, but it was an experience -- the summer of 2001 was wonderful, with us exploring all the beauty of Northern California.
Usually up early, on September 11, I was intrigued by reports on the news of a small plane that had apparently collided with one of the twin towers in NY. By the time I had made it into the Adobe office, it had become clear that things would be changed forever. Adobe's offices at the time were actually two towers (today there are three buildings), and Adobe's buildings are also directly on the approach flight path to SJC (San Jose's airport). Since no one knew what was going on that day, Adobe's security team evacuated everyone from the building, and Bruce Chizen sent out an email for everyone to stay home that day. I returned home to watch in utter horror, together with my family, as the second tower fell. My son (4 years old at the time) asked that we please not watch anymore television, and we spent the remainder of the day at Happy Hollow amusement park -- a small little park -- where the children could be happy and where all the parents could talk and somehow come to terms with what had happened.
On my desk at Adobe, I had a perpetual calendar from the Strathmore paper company (yeah, I'm a paper lover), and since that day, I haven't changed the date on the calendar. It's frozen in time. I also have a friend who used to work in the die cast business, who manufactured those souvenirs that people buy. When I moved out to CA, he was kind enough to ship me a box of NY souvenirs -- die cast models of the Empire State Building, the Statue of Liberty, and the World Trade Center. When I left Adobe in 2004, I packed up my office and shipped it all back to NY. When I opened the box of office items to set up my new office here back at home, I found that the die cast model of the World Trade Center had broken -- one of the towers cracked completely off at the base. Spooky, I know. A photo of both the "frozen" calendar and the broken die cast souvenir, which still grace my shelf in my office today, appears above.
January 2, 2001 was my first day at Adobe as product manager of Adobe Illustrator. It was an incredibly exciting time for me. By June, after the school year was complete, my family had completed the move from NY to San Jose, CA. A culture shock for all of us for sure, but it was an experience -- the summer of 2001 was wonderful, with us exploring all the beauty of Northern California.
Usually up early, on September 11, I was intrigued by reports on the news of a small plane that had apparently collided with one of the twin towers in NY. By the time I had made it into the Adobe office, it had become clear that things would be changed forever. Adobe's offices at the time were actually two towers (today there are three buildings), and Adobe's buildings are also directly on the approach flight path to SJC (San Jose's airport). Since no one knew what was going on that day, Adobe's security team evacuated everyone from the building, and Bruce Chizen sent out an email for everyone to stay home that day. I returned home to watch in utter horror, together with my family, as the second tower fell. My son (4 years old at the time) asked that we please not watch anymore television, and we spent the remainder of the day at Happy Hollow amusement park -- a small little park -- where the children could be happy and where all the parents could talk and somehow come to terms with what had happened.
On my desk at Adobe, I had a perpetual calendar from the Strathmore paper company (yeah, I'm a paper lover), and since that day, I haven't changed the date on the calendar. It's frozen in time. I also have a friend who used to work in the die cast business, who manufactured those souvenirs that people buy. When I moved out to CA, he was kind enough to ship me a box of NY souvenirs -- die cast models of the Empire State Building, the Statue of Liberty, and the World Trade Center. When I left Adobe in 2004, I packed up my office and shipped it all back to NY. When I opened the box of office items to set up my new office here back at home, I found that the die cast model of the World Trade Center had broken -- one of the towers cracked completely off at the base. Spooky, I know. A photo of both the "frozen" calendar and the broken die cast souvenir, which still grace my shelf in my office today, appears above.
September 4, 2008
Making Illustrator and Fireworks Fit
Me love Illustrator long time. I use it for many many things, including web design. I even have an entire video training title dedicated to creating pixel-based graphics with Illustrator.
At the same time, I have always been aware of another application called Fireworks, which admittedly, I've ignored somewhat. Ok, so that isn't really fair. When it was originally released, Fireworks was touted as a crossover application -- it was like one of those vanilla and chocolate swirl soft ice cream cones (yum) -- handling both vector- and pixel-based graphics. Back then, I can't say that I was doing enough web design to care, especially considering that back then, it was also easy enough to use Photoshop and ImageReady (remember that sweet app?) to handle my needs. Fireworks also lacked a sophisticated user interface or advanced text features. I also had trouble adjusting to the drawing tools, again, coming from an Illustrator perspective.
When Adobe and Macromedia merged and Creative Suite 3 was released, there was no FreeHand, but there was a Fireworks and there was an Illustrator. I took another look at Fireworks, considering that I was now doing much more web work. There was some cool stuff to find in Fireworks, but the barriers were still there.
A few months back, Adobe released public betas of some of the CS4 products -- and Fireworks CS4 was included in that. Since then, I've played a lot with Fireworks. Now, with the rest of the CS4 apps on the horizon, I thought it might be a good time to take a closer look at what Fireworks has to offer.
For the first time since I've looked at Fireworks, I can say that I now "get it". I grok FW. Especially when you consider not only the kind of work I do on a daily basis that involves web graphics, but when you also consider that it isn't just about graphics anymore. Web 2.0 standards have given reason for designers to think carefully about how they create content. And it isn't just web stuff either. Designers also work on user experiences and other interactive elements.
First, let's take a look at some of the stuff that Adobe packed into Fireworks CS4:
- A new user interface. If you haven't already seen it, you should take a look at the new user interface in Fireworks CS4. Why? Because it's the new user interface that Adobe has integrated across all CS4 applications. With this new interface, I now feel comfortable in Fireworks. Yeah, it's a small thing, but sometimes these small things mean a lot.
- The Adobe Text Engine. Illustrator, Photoshop, and After Effects all share the same underlying text engine code. Now, Fireworks joins the party, making it possible to move text easily between these Adobe apps.
- PDF Export. It's now easy to create a PDF of your design to send off to a client for review. Sending JPEG files were always a pain, especially for multiple-page designs. Uploading content to a server meant clients couldn't access or review content off-line (or required logins, etc).
These items have certainly removed the barrier -- I can now find my way around Fireworks and using it isn't the frustrating experience it once was. But I'll admit that I was still wondering why I would want to do all my work in Fireworks when I was able to accomplish just about the same stuff in my far more comfortable environment of Illustrator. After all, I could crank stuff out MUCH faster from AI than I ever could in FW. The lightbulb went on when I began to understand the significance of some of the other features that are new in Fireworks CS4:
- CSS and Images Export. As I understand more and more about how the web works, and what Web 2.0 really means, I have come to understand the importance of CSS. One of the key concepts of CSS is being able to understand that content and structure are two very different things (traditional designers always combine the two). To contrast, when you draw a rectangle in Illustrator, you get an image on export. Draw that same rectangle in Fireworks and on export, you get a "div". Even more amazing, Fireworks can even write CSS for auto-expanding elements that stretch to fit content. With Illustrator, I'd design something, slice it into bits and then try my hand at coding it in Dreamweaver. In FW, it just happens. This is SIGNIFICANT. One could argue that Illustrator should have such functionality built in. I for one would love to see it. But at the same time, Fireworks CS4 has it, and I LOVE it. Now I can design stuff and have the code written for me. Isn't that the way it was always supposed to be?
- AIR Authoring. OK, I can hear you all snickering now. Mordy has gone off the deep end. AIR authoring is for developers, not designers. Why would a designer even THINK about writing an AIR application? And the answer is, never. For the same reason as I stated above. Because Fireworks just does it for you. It's literally a mouse click. And so you ask why you'd ever want to create an AIR app. And the answer is that Fireworks has the ability to build interaction into a design. I'm not talking about Flash animation stuff -- I'm talking about building a prototype. Maybe it's a 4 page website. You want your client to see a design mockup and you want it to WORK so that when they click on the buttons, the pages turn, etc. You want rollovers to work. Well, Fireworks was always able to do that. And now, when you need to show the client a comp, you create an AIR app and send it to them. AIR apps run right on the desktop. No need for a browser. No need for an internet connection. Mac, Windows, it's all good. And the comp WORKS. Again, it would be totally awesome if Illustrator could do something like that. But it can't even come close. And FW not only does it, it does it really well.
OK, so after all this, I'll admit I was still not totally sold on Fireworks. After all, I need to repurpose my art all the time. When you're in Illustrator, you can go to the web, to print, to video, and practically to ANY app with no barriers. Fireworks is a one-trick pony -- it's great for designing something specifically for the web, but what do I do if I need to move something into InDesign? Besides, I'm too reliant upon Illustrator.
Well, two things have since caught my eye.
1. Fireworks now does a really awesome job on importing art from Illustrator. In fact, you can use Fireworks CS4 to open native Illustrator files directly. Layers are maintained, text is completely compatible. It's awesome. Basically, I can create my initial designs in Illustrator and bring them right into Fireworks when I'm ready to take it to the next step. So my initial problem of not being comfortable with the drawing environment is a non-issue. I can create art in AI and bring it into FW as needed.
2. Speaking of the drawing environment, Fireworks DOES have some really sweet drawing tools, which are LIVE editing tools. Unlike Illustrator, where once you let go of an object, it becomes a static path, objects created in Fireworks are editable. For example, you can click and drag on a star to change the number of points. You can draw arrows and adjust them as needed, at any time. What a concept. WHY Illustrator can't do this is beyond comprehension, but I have found inner peace. Fireworks has a command in the Edit menu called Copy as Vectors. And wouldn't you know, you can move content from FW right into AI. Of course, the object isn't live once it gets to AI, but it's just as easy to readjust in FW and repaste it into AI again. Go figure -- now I'm using FW to create art that I'm using in Illustrator!
At the end of the day, even beyond the anti-aliasing issues that Illustrator has, I've found reasons to look to Fireworks. Especially when working on designs that require Web 2.0 compatibility. Hopefully, this post will be helpful to those who find that they are at the limits of what Illustrator can do in regard to web and interactive design. If you haven't looked at Fireworks CS4 yet, it's worth heading over to Adobe Labs for a look. At the very least, you'll get some experience with the new CS4 user interface. At the very best, you'll have found a new application in your design tool box.
Got additional comments about Illustrator or Fireworks? Discussion is ALWAYS encouraged!
At the same time, I have always been aware of another application called Fireworks, which admittedly, I've ignored somewhat. Ok, so that isn't really fair. When it was originally released, Fireworks was touted as a crossover application -- it was like one of those vanilla and chocolate swirl soft ice cream cones (yum) -- handling both vector- and pixel-based graphics. Back then, I can't say that I was doing enough web design to care, especially considering that back then, it was also easy enough to use Photoshop and ImageReady (remember that sweet app?) to handle my needs. Fireworks also lacked a sophisticated user interface or advanced text features. I also had trouble adjusting to the drawing tools, again, coming from an Illustrator perspective.
When Adobe and Macromedia merged and Creative Suite 3 was released, there was no FreeHand, but there was a Fireworks and there was an Illustrator. I took another look at Fireworks, considering that I was now doing much more web work. There was some cool stuff to find in Fireworks, but the barriers were still there.
A few months back, Adobe released public betas of some of the CS4 products -- and Fireworks CS4 was included in that. Since then, I've played a lot with Fireworks. Now, with the rest of the CS4 apps on the horizon, I thought it might be a good time to take a closer look at what Fireworks has to offer.
For the first time since I've looked at Fireworks, I can say that I now "get it". I grok FW. Especially when you consider not only the kind of work I do on a daily basis that involves web graphics, but when you also consider that it isn't just about graphics anymore. Web 2.0 standards have given reason for designers to think carefully about how they create content. And it isn't just web stuff either. Designers also work on user experiences and other interactive elements.
First, let's take a look at some of the stuff that Adobe packed into Fireworks CS4:
- A new user interface. If you haven't already seen it, you should take a look at the new user interface in Fireworks CS4. Why? Because it's the new user interface that Adobe has integrated across all CS4 applications. With this new interface, I now feel comfortable in Fireworks. Yeah, it's a small thing, but sometimes these small things mean a lot.
- The Adobe Text Engine. Illustrator, Photoshop, and After Effects all share the same underlying text engine code. Now, Fireworks joins the party, making it possible to move text easily between these Adobe apps.
- PDF Export. It's now easy to create a PDF of your design to send off to a client for review. Sending JPEG files were always a pain, especially for multiple-page designs. Uploading content to a server meant clients couldn't access or review content off-line (or required logins, etc).
These items have certainly removed the barrier -- I can now find my way around Fireworks and using it isn't the frustrating experience it once was. But I'll admit that I was still wondering why I would want to do all my work in Fireworks when I was able to accomplish just about the same stuff in my far more comfortable environment of Illustrator. After all, I could crank stuff out MUCH faster from AI than I ever could in FW. The lightbulb went on when I began to understand the significance of some of the other features that are new in Fireworks CS4:
- CSS and Images Export. As I understand more and more about how the web works, and what Web 2.0 really means, I have come to understand the importance of CSS. One of the key concepts of CSS is being able to understand that content and structure are two very different things (traditional designers always combine the two). To contrast, when you draw a rectangle in Illustrator, you get an image on export. Draw that same rectangle in Fireworks and on export, you get a "div". Even more amazing, Fireworks can even write CSS for auto-expanding elements that stretch to fit content. With Illustrator, I'd design something, slice it into bits and then try my hand at coding it in Dreamweaver. In FW, it just happens. This is SIGNIFICANT. One could argue that Illustrator should have such functionality built in. I for one would love to see it. But at the same time, Fireworks CS4 has it, and I LOVE it. Now I can design stuff and have the code written for me. Isn't that the way it was always supposed to be?
- AIR Authoring. OK, I can hear you all snickering now. Mordy has gone off the deep end. AIR authoring is for developers, not designers. Why would a designer even THINK about writing an AIR application? And the answer is, never. For the same reason as I stated above. Because Fireworks just does it for you. It's literally a mouse click. And so you ask why you'd ever want to create an AIR app. And the answer is that Fireworks has the ability to build interaction into a design. I'm not talking about Flash animation stuff -- I'm talking about building a prototype. Maybe it's a 4 page website. You want your client to see a design mockup and you want it to WORK so that when they click on the buttons, the pages turn, etc. You want rollovers to work. Well, Fireworks was always able to do that. And now, when you need to show the client a comp, you create an AIR app and send it to them. AIR apps run right on the desktop. No need for a browser. No need for an internet connection. Mac, Windows, it's all good. And the comp WORKS. Again, it would be totally awesome if Illustrator could do something like that. But it can't even come close. And FW not only does it, it does it really well.
OK, so after all this, I'll admit I was still not totally sold on Fireworks. After all, I need to repurpose my art all the time. When you're in Illustrator, you can go to the web, to print, to video, and practically to ANY app with no barriers. Fireworks is a one-trick pony -- it's great for designing something specifically for the web, but what do I do if I need to move something into InDesign? Besides, I'm too reliant upon Illustrator.
Well, two things have since caught my eye.
1. Fireworks now does a really awesome job on importing art from Illustrator. In fact, you can use Fireworks CS4 to open native Illustrator files directly. Layers are maintained, text is completely compatible. It's awesome. Basically, I can create my initial designs in Illustrator and bring them right into Fireworks when I'm ready to take it to the next step. So my initial problem of not being comfortable with the drawing environment is a non-issue. I can create art in AI and bring it into FW as needed.
2. Speaking of the drawing environment, Fireworks DOES have some really sweet drawing tools, which are LIVE editing tools. Unlike Illustrator, where once you let go of an object, it becomes a static path, objects created in Fireworks are editable. For example, you can click and drag on a star to change the number of points. You can draw arrows and adjust them as needed, at any time. What a concept. WHY Illustrator can't do this is beyond comprehension, but I have found inner peace. Fireworks has a command in the Edit menu called Copy as Vectors. And wouldn't you know, you can move content from FW right into AI. Of course, the object isn't live once it gets to AI, but it's just as easy to readjust in FW and repaste it into AI again. Go figure -- now I'm using FW to create art that I'm using in Illustrator!
At the end of the day, even beyond the anti-aliasing issues that Illustrator has, I've found reasons to look to Fireworks. Especially when working on designs that require Web 2.0 compatibility. Hopefully, this post will be helpful to those who find that they are at the limits of what Illustrator can do in regard to web and interactive design. If you haven't looked at Fireworks CS4 yet, it's worth heading over to Adobe Labs for a look. At the very least, you'll get some experience with the new CS4 user interface. At the very best, you'll have found a new application in your design tool box.
Got additional comments about Illustrator or Fireworks? Discussion is ALWAYS encouraged!
Subscribe to:
Posts (Atom)