Thread: A deadly combination

Alright, so Patterns is JavaScript? (no familiarity with it)

But I can help you set up your objects/classes

Basics you probably already know, but its good to use the same terminology so here goes.

It sounds like what you call a "data-store" is an object, and thus each needs a Class to create it:
The Student, The Horse, The Tack and The (Lesson) Recap.


"All four of these require C.R.U.D. (Create, Retrieve, Update, Delete) capabilities."
These look like they are your methods.
"Create" will be handled by a "Constructor" This is a class method that has the same name as the class,
and when you make a new Object of that class the constructor does the work setting its variables.

E.G.

public class Horse
{
 
	private int key; // all your variables would be here and most likely [B][U]private[/U][/B]
 
	public Horse() //This is your create method. you could if you REALLY wanted to, make a "create" method that calls this.
	{
		key = 7; //obviously more complicated, but the idea is there.
	}
 
	public retrieve() //note: first letter of methods are not capitalized. this is ultimately a choice and not syntax, but taught universally.
	{
		// does stuff
	}
 
	public update()
	{
		// does stuff
	}
 
	public delete() Note: Java handles garbage collection during run time, so you may not even need a delete method.
	{
		// does stuff
	}

To elaborate on delete(). methods like this are used in lists and structures.
But, if you wanted to delete a Horse you wouldn't write the delete method in the Horse Class.
Instead if you had a list of your Horse Objects, you would delete your specific Horse (call him Sam) from the list.
If your program has no way to reach Sam ever again, Java garbage collection will handle the rest,
and Sam's space in memory will eventually get reused when needed.

Give me some feed back, and I will continue in the direction you need.
Jonathan

Hi Jonathan. Thanks for the reply.

Actually Patterns are OOP design strategies. You may have heard of terms such as factory pattern, listener pattern, decorator pattern among others.

The Strategy Pattern that I thought might work for my reworked application "defines a family of algorithms, encapsulates each one, and makes them interchangeable. Strategy lets the algorithm vary independently from the clients that use it." (Eric Freeman et. al., Head First Design Patterns, p. 24).

Though wikipedia has a nice writeup the strategy pattern, I found this one more helpful: Strategy Pattern - Web Tutorials - avajava.com

In my case, the family of algorithms is the CRUD algortithms, with the idea that the independent variance are the Horse, Tack, Student and Recap. Or, at least, that was what I was asking.

I was using the term "data-stores" as a token term. They are, as you expected, on a database: mySQL to be exact, running on a local Apache server I downloaded from xampp.

Thanks again for your feedback -- and I certainly will study your code.

Regards,

grNadpa

I haven't heard about Patterns terminology till now, gonna take the day to read up on the links you provided.
I suspect I will not be able to offer any advice until I have familiarized myself with what seems to be a good read.

That's EXACTLY the feedback I was looking for. Thanks.

grNadpa