It seems to work fine for me. I made a couple of little changes (changed “txt” for “text” so that you wouldn’t use a reserved work and swapped Sprite for MovieClip since you didn’t use any of the MovieClip methods). Here’s what I got:

Here’s the Client code I used:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

package 
{
	import flash.display.Sprite;
 
	public class Client extends Sprite
	{
		private var tBtn:Sprite=new TextButton("AS3 Design Patterns",0xcc0000);
 
		public function Client()
		{
			tBtn.x=100,tBtn.y=100;
			addChild(tBtn);
		}
	}
}

It looks like a reusable hunk of code to me, and with just a tweak or two, it programs to the interface (Sprite) and not the implementation (TextButton).

Thanks,
Bill

Beg your pardon again

Curro

My button is based on my artistic skills–in other words, zilch! Any creative idea you have for a button would be most welcomed.

Thanks,
Bill

Ha Ha! Actually, it’s more like not hitting your head against a brick wall — feels so good when you stop!

Would you like something like your existing button only “punched up?” — more 3D looking for example, or something completely different? Give me a visual direction and I’ll be glad to oblige.

Barbara

Glad to hear from you. When you solve your own programming problem is that the same as recursion? Yuk, yuk.

Thanks for the button offer, and if you’re still game, I could use something to replace the ugly Play button I made all by myself!

Kindest regards,
Bill

Never mind, I figured it out :-) If you are using movie clips from the library and you move their corresponding classes to a to a folder, you have to put the path to the folder in the symbol properties in the class box! So obvious, yet I had never run across this problem before. I tried dot notation and it worked!

Barbara

P.S. I’ll still make you a button or an icon if you want — I’m sure to panic again at some future time :-)

If you can solve this one for me, just describe a piece of artwork and I’ll do it for you (if within my powers). You will have earned it. Did you ever hear the expression “pride goeth before a fall?” I thought I had written the ultimate, wonderful, complete, working pattern design for my story project – and in a way, I have. Then I tried to divide it up into packages… Oh woe!

Background: commandStory is based on the command pattern, except instead of making it possible to repeat an action (such as incrementing a counter by pressing a button), commandStory makes it so one action triggers another in order from the beginning of the story to the end. The idea was to make it possible to encapsulate each action (I called them pages) in its own command/receiver pair and then to have a number of these pages encapsulated in a chapter. I wanted separate chapters so I could clean up after each chapter and also possibly implement chapter buttons for the user. The invoker class does most of the work. Instead of having just an execute() function (onBeginPageEvent()), it also has a setup() function (onTurnPageEvent()), that sets up each action via its command/receiver pair and then routes things back to the invoker which then sends out each execute() command to the same command/receiver pair.

I actually accomplished most of this. The demo starts with a chapter 1 button you press, and a red circle appears. Click on the red circle and it moves along the stage and triggers a scene change. You hear whistling. Then a bird head appears in the tree. Click on the bird head and the whole bird pops out of the tree. Drag the bird and he flaps his wings. If you drag him near the left border of the stage, a fly appears. When you touch the fly with the bird’s mouth, the fly disappears and the bird smiles. A few seconds later, a cloud appears. If you touch the cloud to the bird’s body, it registers a hit and a few seconds later you’re in chapter 2 – more objects moving across the stage. I did all this to test and see if I could encapsulate each action in a command/receiver pair – sounds, dragging, hits, etc – which I could.

So what is the problem? This story is going to have many chapters with many pages each, and I assumed it would be easy to put each chapter and possibly each page in its own package. I tried very many things, but I can’t get past an initial road block: If I put Chap_01.as in its own package, chapter_01, and label it correctly as such and put an import statement in TableOfContents.as (import chapter_01.*;), the methods in Chap_01 won’t run. I get an error message: TypeError: Error #1006: run is not a function. (“Run” is the name of the method I am trying to run in Chap_01.) I can run a trace statement from within TableOfContents.as such as trace(chap_01) and it works, but the methods of Chap_01 are apparently not available for some reason. Any help you can give me will be greatly appreciated and if you want a button or an icon or even a banner and I can provide it, just name it. Here’s the link.

http://www.bitsong.com/forPosting/packageProblem/packageProblem.html

Barbara

Barbara

Executing commands generally result in some well-known behavior (not behavior that varies). So, it is a good idea to have multiple commands to move the square/circle by different amounts ( e.g. MoveBall5Command, MoveBall10Command etc. etc.)

However, you don’t need multiple receivers. The command “knows” the receiver. So, you can call the setSizeOfStep method before moveBall from the MoveBallCommand.

For example for a MoveBall10Command class, the execute method will be:

1
2
3
4
5

public function execute():void
    {
        receiver.setSizeOfStep( 10 );
        receiver.moveBall();
    }