We are getting more and more activity each day and have changed a few things to better accomodate users and also make things easier for us to maintain. The changes are as follows:
1. Replaced the WordPress contact form with a dedicated Contact page. This Koolmoves contact form uses a RichTextEditor component to allow users to format their email message and also allows them to easily post linkable text. All emails are sent and arrive as they are written in the RTE and the form itself uses a combobox to let users choose the subject of their email message.
2. I finally added the source code downloads to a dedicated page here. This section helps us track what is popular and will help guide us for future submissions. Just about everything we offer is GNU and leaves a lot of freedom for us as well as end users. As promised I’ve also setup a Flex download category to maintain links of mine from my previous Flex websites other people linked to.
3. The “Confirmed Classes” dedicated page here has been removed. The classes that we have confirmed (or received confirmation on) to work with the KM7/AS3 compiler will now be maintained in a special forum in our wpBBS forum here. This lets us link out to them and still lets users give some feedback (which the dedicated page did not allow) if they wish. This forum is reply only and open to all registered forum users.
4. I’ve added code to standardize our personal version of our opensource wpBBS forum. Our forum now supports thread locking, pinning, user post new levels (if a user does not have the privileges to post a new thread…it is a reply only forum) and user post reply levels (in cases where we simply want to put information out and disallow new threads and replies similar to the Flashkit “News” forum making it a read only forum). I am adding private messaging to our forum as well and will introduce and explain how that works when the coding is finished and added. Sounds are also being added to the forum.
Thanks to all who have made themselves known btw. We love feedback and appreciate the efforts on the part of those who have taken part in what is going on here. We also are seeing more Koolmoves blogs and websites being built and applaud their effort toward the platform. We don’t want the KM-Codex to be the best Koolmoves related website…we simply want to be one of MANY websites dedicated to the software and community. The more this platform gets talked about…the more it comes up in search engines spurring users who have never heard of it to maybe take a look at what it has to offer.
My understanding is that Bob Hartzell is focusing mainly on the KM7 compiler supporting as many existing popular AS3 classes as it can and using the AS3 Animated Gif class authored by Kevin Weiner & Thibault Imbert as a base, he has now added Animated Gif support to the beta. By attrition, the more capable Bob codes the compiler, the more classes it will support by default and just by him adding support for this one class it may be that many other classes are now also supported. Trial and error with all kinds of classes combined with the feedback the KM community gives to Bob is paying off large dividends and each beta build ends up being more and more powerful due to this joint effort and his outstanding programming abilities.
The complete list of new additions for the 7.0.4 build are as follows:
1. Fixed export of movie clip in symbol library with same class name as an external class 2. Fixed case sensitivity issue associated with package file names 3. Fixed problem with type mismatch message associated with use of ‘new’ with a locally defined variable 4. Fixed assorted AS3 issues so org.gif classes and some other classes now run 5. Fixed display of Movie Overview after a button is deleted 6. Added bitmaps, sounds, binaries tabs to F11 symbol library
A lot of Flash users utilize Paypal HTML shopping carts for listing multiple items even though their shops themselves are coded as Flash objects. While this is all fine and good, I’ve always found it a bit odd visually since it breaks continuity and is a coding choice rather than something that is forced by Paypal itself. If your site is full Flash and you are running a Paypal shop I’m a much bigger fan of only sending users to Paypal on checkout and handling the cart itself internally as part of your Flash shop. This example shows you how to do just that with Koolmoves 7 and AS3.
This example uses a psuedo datagrid to display cart items. The items themselves are pushed to the cart with simple buttons. The main goal of the example is to show the mechanics of the Flash cart itself, adding and removing items from the cart, formatting currency totals (USD) for display and POSTing the cart itself to Paypal using AS3. As far as pushing the items themselves, you can do so in any fashion you wish (via lists, buttons or any other means you prefer). Normally I would hide the cart itself until something is added to it or tween it into view as things are added by tracking the main array length. You could also code a “View Cart” button somewhere in your flash page that calls up the cart if it contains items. It is constantly visible in this example only for effect.
Flash carts can pretty much doing anything their HTML counterparts can from using option fields to supporting shipping costs or sales tax and this core example can be expanded upon easily to fit your shop needs.
This example is available for download in the Source Code section.
Using the same movie from the FlashVars example this one instead uses ExternalInterface for both Inbound and Outbound container communication. This example shows ExternalInterface sending variables into an embedded movie for frame navigation and the embedded movie itself communicating back to the containers javascript using ExternalInterface to set the window location and window title to match the section chosen.
While none of this is groundbreaking with External interface being supported by earlier versions of Actionscript, to my knowledge there are no earlier examples at the KoollExchange and certainly none usin AS3 scripting.
All code is in the “Source Code” section and a running example is here.
If you are using Internet Explorer 6, or older. We highly suggest that you seek out an alternative or newer web browser, to bring your web surfing experience up to current standards.
