Printable View
Yes, and you can do it with KM 6.2 and AS1 without any problems:Quote:
Originally Posted by ghol
http://forum.necromanthus.com/necrof...um=2&topic=169
Of course, anything on this world can be improved.:cap:
In this case you can use CopyPixels, you can generate the gradient mask at runtime, and so on.
:mrpimp:
I did not know, and thanks for let us know here.
An example of using the Display List (which you could not do with 6.2) might help understand we will have a completely new way to construct our websites and movies and all the possibilities and opportunities we never had until now are now open as food for thought and design.
For instance. WIlberts componenets. What we had is what we had in 6.2. We could exploit their methods and properties and be creative but what it was is what it was. In KM7, you will be able to in effect extend and twist his components in ways you never could before...if you embrace AS3 :)
This is a new List component Wilbert created. It loads a list of fake items . Using the display list I add a child to the list....a labelscroll component in this case. It is part of the list. Added at runtime and allows itself to be manipulated fully as it is a child of the list.
This example lets you remove it from the list at runtime.
http://krazyaboutpizza.co.uk/List_AddChild.swf
This is just a small, small example of the things we will be able to do now. Trust me...we will have two distinct camps after final....those who utilize AS1 and those who utilize AS3 and the Exchange will have to address it but it will be great fun and a massive boost up for the platform in general IMO :)
KM7 will introduce a lot of you to the concept of reparenting. No more do we attachMovie and all with AS3, we utilize the Display List instead and it makes adding and removing items easy peasy.
It also lets us reparent items already on the Display List in one fell swoop....addChild called on an existing child automatically removes the child from the source container (removeChild) and reparents it to where you direct it:
http://krazyaboutpizza.co.uk/Reparenting_KM7.swf
If I have a movie with two lists with instance names of "l1" and "l2" and a labelscroll component with an instance name of "ls" I can swap it as a child easily
l1.addChild(ls); (ls is removed from l2 and reparented to l1)
or
l2.addChild(ls);(ls is removed from l1 and reparented to l2)
Remember....these are simple demos. Your children can be anything you dream up :D
Word of the day: Reparenting :)
Nice example Chris.
You are right, the display list makes a lot of things possible that weren't possible before like reparenting.
What I consider to be a disadvantage is that there's no way to destroy an object besides removing all references to it and hope the GC will pick it up. It still feels a bit strange to me a movieclip removed from the stage still keeps running.
The mysterious modern GC....hahaha. Many a blogger has attempted to make sense of it. Even now.
Yes, the GC doesn't always make sense.
Here's another example showing some of the flexibility of the new components.
Presumably that list can be populated externally, which would make it very useful as a shoping cart display.
The difference that is that in the AS3 example the reflection is part of the image because it is a child of it in the hierarchy and doesn't require any code nor does it require a mask which has it's own limitations like the need to embed fonts if masking dynamic text.Quote:
Originally Posted by necromanthus
YES!Quote:
Originally Posted by Stoke Laurie
It means wasted memory and wasted processing power.Quote:
Originally Posted by w.brants
That's true Wilbert.Quote:
Originally Posted by w.brants
I was playing with AS3 before the release of Adobe Flash 9 (CS3) and I can tell you for sure: there're many "strange" and buggy features.
The Garbage Collector approach is one of them.
I know that Bret, but most of the KM users need the AS1 approach.Quote:
Originally Posted by blanius
And I gave them a simple one. ;)
Now coming back to AS3:
AS2 was not popular at all, and I have the feeling AS3 cannot become popular.
For many reasons. Only few of them:
- there're big syntax differences & methods between AS1 and AS3.
Many people don't feel comfortable to work with it.
- almost no one is going to update an old (complex) website containing hundreds or thousands of AS1 lines.
A lot of work for almost nothing (the performance boost is not spectacular in case of "basic" things)
- AS3 components are running much faster.
But how many KM users are using components and who is ready to update the entire application in order to use the new components?
- many KM users already asked me if "flash 9 - AS1" is going to be available in KM7.
Bob, are you here? :cap:
Now to conlude: AS3 is an excellent choice for any NEW project.
As long as the flash developer is able to learn & understand it.
Necro you make good points, I think most people can learn AS3. If I can it can't be too hard. I'm not great with it but I've managed to get things done.
I'd never rebuild anything AS1 to AS3 but everything new will be.
I'm not that pessimistic about AS3 Remus :)
I believe in time AS3 will become more popular for the simple reason Adobe is "forcing" us to use it. Flash Player 9 didn't offer much new things besides the AS3 scripting language. Flash Player 10 will offer new functionality when it comes to creativity like custom filters and 3D rotation of flat objects that can only be used when the AVM2 is targeted.
You are right the syntax differences are big and it will take time to learn AS3. I know most KM users aren't experienced scripters but Bob integrates the new components into the gui. Also besides supporting the listener approach Adobe uses, I also added support to most components for the old way. So when a user adds an AS3 button component, it will be possible to use a syntax likeI don't know what "flash 9 - AS1" should be :confused:Code:button1.onClick = function(){
mc1.visible = false;
}
There's no reason to export as swf9 when using AS1 since the new functionality is only available when using AS3.
If you mean using AS1 to target AVM2, that would almost be impossible. The way objects on stage are organized using the display list is so different that I don't think that would be possible but maybe I'm missing something.
Your final conclusion is absolutely right.
AS3 is most useful for new projects. If a KM user wants to learn it or not is a personal choise. If you don't need the new features Flash Player 9 (and later on 10) have to offer, there's no need to switch. If you want to use those new features there's just no choise thanks to Adobe.
How can you be optimistic when AS4 is knocking on your door?Quote:
Originally Posted by w.brants
:smoov:
See the attached image.Quote:
Originally Posted by w.brants
A tip: certain "tasty" FlashPlayer 9 features (related to FLV, network, etc) can be used only if the SWF is exported as version 9.
The features are independent of AS1, AS2 or AS3 and, also, they're independent of the Virtual Machine.
cheers
Ahhh ... I forgot to mention a very important thing:
"FP9 - AS1" would be the best way for the KM users to update their projects.
And the first step to "FP9 - AS3", of course. :p
When I opened the door nobody was there :DQuote:
Originally Posted by necromanthus
Well, serious Remus, if you know a site with detailed information, you are welcome to share it since I would find it interesting to read.
All I can find about AS4 is that it will be based on ECMAScript 4 but even that is still being worked on. Also from what I read is that it would be an evolution of AS3. I can't imagine Adobe making drastic changes again in such a short period of time. Of course they can but it would affect their credibility and the risk of losing users to MS Silverlight.
I tried to open a couple of doors at Adobe for you, but all of them are locked.Quote:
Originally Posted by w.brants
They all have the same big sign: NDA :D
Now seriously, there is a big chance to see (test) the first beta later this year.
And they're going to release it next year for sure.
Why so soon?
MS Silverlight is one of the reasons. :D
cheers (and keep up the great work there).
p.s.
Starting with KoolMoves v9, you'll get 3 export options:
AS1, AS3 and AS5.
Do you really need AS2 and AS4?
:mrpimp:
LOL :) :) :) :) :) :)Quote:
Starting with KoolMoves v9, you'll get 3 export options:
AS1, AS3 and AS5.
Do you really need AS2 and AS4?
Not sure where this is going, as someone who has pushed the capabilities of Koolmoves from the start, I thought you would be keen on the upgrade Remus, but unless I read you wrong, you're saying the upgrade isn't worth it to the average KM user. I think the answer lies in who is the average KM user, are they on average more comfortable with gui based features than the background power of actionscript? if so, then the future power of KM relies on the quality of its' components, and their ease of use. I believe Wilberts' video and sound player ensured the success of v6. Maybe a study in their creation so that others could contribute would not only relieve some of the pressure on Wilbert, but also add a diversity to KM use. I believe there are several in the community who would contribute if they had some guidence.
I would like to revisit the early days of KoolMoves when Johnnie (you will see his name on some of the threads) had a big influence on the technical direction of KoolMoves. He pushed me to add action scripting around 2001. At the time it didn't make any sense. Very few of our users used action scripting. It required a major allocation of our limited resources to implement action scripting and took many years to get most of it in place. The way the story turned out is that action scripting in itself was not so important but it provided a technology foundation that spawned motion scripts starting with Hilary, components, filters, preloaders, etc. -- all the cool features of KoolMoves. It may not be possible to understand the implications of AS3 for the future functionality of the product at this time. One avenue that I can see right now is 3D. Also, it will be possible to create effects which are computationally more sophisticated than we currently have in place. To stay competitive, we need to go down this path.