quote:

---

Now isn't that ugly?

---

quote:

---

Original post by 23yrold3yrold
In "Additional Resources", is it me or is the "Trent Polack's: Game Tutorial #03" link broken?

---

quote:

---

Original post by Anonymous Poster
the idea is nice, but it's taken too far.
you got a little bit carried away with making it "generic" and "configurable" and improving "flexibility" and "reusablity".

---

quote:

---

Original post by Seriema
We'd like to hear your comments on this *hehe good luck*

---

quote:

---

Original post by Seriema

I'm sorry if my last post was a little confusing, it was 02.00 over here What I really wanted to know, using your template method, how would one save a particle system to file and then recreate it? Using our method of interfaces and class hiearchies we solved that by giving each part a "name" (GravityModifier, ColorModifier) and using factories. But how would one do that with templates?..

---

quote:

---

This looks like one of those wonderful ideas that would just never be used in real life.

---

quote:

---

Original post by 23yrold3yrold
I hate Hungarian Notation too ....

---

quote:

---

Original post by 23yrold3yrold
I don't think you mentioned drawing in any way, but that was the best way I could think of (I coded up an Allegro implementation of this last night)

---

quote:

---

Original post by Anonymous Poster
Nice article! I really need to read this book on design patterns!

---

quote:

---

Original post by Anonymous Poster
Probably a dumb question on your code examples: What's that PrepareAction() thing?
It's never really used in any of the example action-policies. I wonder what it might be useful for - initialisation of the action to be performed? Any examples?

---

quote:

---

Original post by Anonymous Poster
very interesting article. Thank you very much for your wonderful ideas, even if they are possibly a litte bit too generous, i think ;-)

greets, smasher1985

---

template <class T>
class bag {
public:
	void clear() { container.clear(); }
	iterator begin() { return container.begin(); }
	iterator end() { return container.end(); }
	size_type max_size( ) const;
	void add(const T& t) { container.push_back(t); }

	template<class F>
	void for_each(F f) {
		for (iterator i = container.begin(); i != container.end(); /* none */) {
			if (F(*it)) {
				swap(*it, container.back()); // does self swapping work?

				container.pop_back();
			}
			else
				++i;
		}
	}
public:
	typedef vector<T> container_type;
	typedef container_type::iterator iterator;
	typedef container_type::size_type size_type;
private:
	container_type container;

};

struct Particle {
	Vec3d pos;
	int life;
};


class ParticleGroup : private bag<Particle> {
	void initialize() {
		// ...

	}

	bool action(Particle& p) { // returns true if the particle is to be destroyed

		// ...

	}

	ParticlGroup() { initialize(); }
	Update() { for_each(boost::bind(ParticleGroup::action, this, _1)); }
	void emit(Vec3d p, int amount) {
		for(int i = 0; i < amount; ++i) add(Particle(p));
	}
};
 

quote:

---

from article
Should we copulate the rendering to the particle system?

---

quote:

---

Original post by Br1
...

---