FREE BASIC ADOBE FLASH TUTORIALS BLOG
So now that Adobe has announced the new features surrounding CS5 and Flash, I’d love to hear what you think about the product. I have yet to download the trial and start working with it, but I’ve been doing a lot of reading and it seems to me that Adobe is pushing and expanding Flash more than it ever has before. InDesign for example now integrates a lot of built in Flash pieces to publish animations.
Perhaps what I’m most looking forward to are the actionscript tools. I have yet to see the specifics, but from what I have read there are more tools built in to help write actionscript. I know that has been a major hurdle for most to cross and if there is some help there it would be much appreciated.
So what do you think? what have you read, heard, or experienced that helped you make the choice to upgrade, buy, or wait on CS5?
Just signed up a couple hours ago on Adobe’s site to preview the new CS5, which will be unveiled officially in an hour or so. I’ve read and watched a few of the new features with CS5 (mostly in Photoshop, although I hear that Flash is getting an overhaul as well) that seem pretty promising.
I’ll admit, I still haven’t adopted the latest creative suite version CS4. The jump just didn’t seem worth it enough for me to justify the cost of an upgrade. So I’m interested to see what Adobe has up their sleeve this time. I’ll update this post in a little bit to give you some of my thoughts from what they share about it.
I get questions emailed to me daily on my tutorials and other Adobe Flash questions. Up until now I’ve done my best to answer them back with details in reply emails. I noticed though that many of the questions are similar and I’m confident that the answers to those questions could benefit others who have the same question or problem that aren’t sending an emails, but are still looking for answers.
It’s this reason why I originally wanted to setup a forum to handle those kinds of questions. Someone could pose a question to the community about Adobe Flash and it was my goal to have people help one another with concerns. Particularly those questions that I don’t have answers for.
I setup a forum page originally. It probably wasn’t working properly. I had no idea what I was doing at the time and the forum got 0 interest. Things are different this time and going forward I was wondering what everyone thinks about creating a new forum to handle questions and answers or is it better to handle those issues as blog posts? Both forums and blog posts are interactive and give the chance to get a discussion going on the topic. I have my personal opinions on both, but I really wanted to get your opinion on the difference and how you would prefer to getting answers to questions. So please answer this quick survey with how you feel the better way is to ask, answer, learn from questions about Flash and web development.
If you have any specific questions about this please leave a comment as well. Any feedback would be appreciated. I just want to make this as good as an experience for the viewers of the website as I possibly can. Thanks.
With the new system I’ve built the site on, I can now finally integrate my blog directly in to the site. I previously had a blogspot blog set up kind of as a companion site, but having a separate system made it difficult to remember to check and update. It’s hard to track the traffic and where it’s going from there, and overall didn’t match the feel and brand of the rest of the site.
This way the blog works together more with the site, which I’m very excited about. So please feel free to use it, read it, leave me great comments and I’ll make sure to answer back. I’ll be adding different aspects to the blog from time to time, so please be patient and come back often.
I’ve mentioned this before but when I first created freeadobeflashtutorials.com over 2 years ago it was just me and my new mac whipping things together with Dreamweaver. I knew about browser differences but didn’t have any way to test them on my own, other than borrowing someone’s pc and checking them out in IE while debugging the site. Over the years though I’ve picked up some tools and experience along the way and I am proud to say that I finally got around to fixing the css issues in Internet Explorer. So all you IE users getting to the site, whether it be in 6,7, or 8. We all should now be on the same page.
Browser testing is a pain and any front-end developer’s least favorite part of the process, but it is still very important to do. About half of the viewers of this site are using some version of Internet Explorer and it’s sad to say that for the past 2 years those people have been looking at more or less a broken site. Of course they don’t know it’s broken, they don’t know how it was supposed to look like, but still I’m glad we are all on the same page now.
If you’re wondering about your site and the different ways to test and see things for browser supports there is a lot to learn. If you’re running a mac like me, I highly recommend you picking up some software to run virtual machines and get yourself a copy of windows. Once you got windows going you can download and test for different versions of IE. I have 3 separate virtual machines, one for each major version, but I also use IETester that is really helpful because you don’t have to then switch between the virtual machines.
If you’re looking for the actual differences between browsers, well then that’s a whole bigger issue that can’t be addressed with this single post. I’m sure there are books filled with it. I will recommend though when you start a project to use some sort of css reset. It’s usually just a css file or series of them that override all of the browser specific styles and gets you started on the same playing field. It’s difficult to move an existing project to it, as it typically will change a huge amount of what you’ve done, it is however still possible. This site for example I had to go back and add a reset, There were a bunch of new styles I had to add and change around a bit, but to get everything back on a somewhat level playing field is worth it. Of course there are more things out there that aren’t fixed by a simple css reset, but it will save you some heartache.
Oh well, I have a lot more on this subject, but it’s getting really late, so I’m going to call it a night and just say thank you for all the users who continue to come back to the site to learn more about Flash and web development, even if it looked a little funky in your browser for a little while there. Going forward I still do have a lot of plans for the site, so make sure to come back often for updates on the site.
I’ll admit, it has been a good long while since I’ve gone back over my website freeadobeflashtutorials.com. Almost 2 years now. As stated in my last post, my wife had a baby, we then moved across the country for a great web development job and we’ve been on our toes ever since. So I’m afraid to say my first real project got put on the back burner. I still receive emails almost daily and I do still try to return them when I have a solution for their questions, but adding to the website has always been pushed back on the “things to do” list.
A big reason why it kept on getting pushed back was in the way it was made. I put this site together myself writing out all of the html. Which worked fabulously. It was the beginning of my understanding and using html, CSS, and web publishing and I think it turned out pretty good. As good as it was though it was a pain to update. If I wanted to change any content I would have to do it on every page. If I wanted to add a page or link I would have to recreate the page and add everything in code manually. I will admit a few people have sent me links to post and I never got around to them because they were such a huge pain to add and it wasn’t really on my radar.
My web development experience has come a long way since I created the site and I decided that it’s finally time I put some of that experience to work for my flash tutorials site. Over time the tutorials and site has picked up more and more interest, so I decided it was time to revisit and update the site again.
So today I’m happy to announce the next redesign of Freeadobeflashtutorials.com. In fact I released it today. It’s not a redesign in that it looks different, I tried to keep it visually the exact same as it was before. In fact I’m hoping the visitors who aren’t reading this post never even realized I’ve remade it. It is the first phase laying down the infrastructure of hopefully many updates to come. So although the site looks the same, it’s actually completely different from the ground up from a coding perspective.
The site has been redesigned with a whole new infrastructure to handle my content and updating the site. This puts the foundation in place so that I can now pull in the blog and forum and integrate them much more into the site. I can add links easily on request, add interactive features like comments on the tutorials pages and a contact form to get a hold of me directly. And when some of that is done I’ll get back to creating more simple Flash tutorials.
I’m very proud of the changes and although they don’t seem big now, they will be in the coming weeks. So thank you for reading and come back soon and often to see how the site changes over the coming weeks.
Preloaders indicate the rate at which a file is being downloaded or displayed. This tutorial shows the actionscript 2.0 method to create such a progress bar. Go to the Flash Files section to download the actual .fla file. Make sure to check out the other tutorial on progress bars to help create the correct components.
Viewing and loading files on the web often takes time, especially multimedia. Progress bar preloaders are important to show the viewer that content is coming. This tutorial is the first of two tutorials that will show you how to create and code a preloader. It will show you how to make a graphical and numerical representation of download progress of the file.
swf files loop by default, if the timeline is more than one frame. With simple actionscript you can control and navigate a frame-by-frame animated sequence.