Javascript: Module Pattern vs Constructor/Prototype pattern?

Question

Hi there,

I have been reading a little bit about the Module pattern and i wonder if applicable for what i need to do or should i use the Constructor/protoType pattern.

Basically I am using unobstrusive javascript so i have a reference to my .JS file in my HTML document.

If i understand it correctly then I can call a INIT method (which is badically a public method i can create and return using the module pattern).

In the INIT method i will assign all my click events etc etc...

THis sounds like the perfect pattern, as i don't need to create Objects and inheritance/supertypes etc

From what i understand the Constructor/Prototype pattern is my for create objects and using inheritance i.e. Subtypes of a supertype??

Am i correct here?

So to provide basic unobstrusive javascript the module pattern is ideal??

I would appreciate any feedback with regards to the right direction to take

Thanks in advance

Answer 1

Constructor-functions and prototypes are one of the reasonable ways to implement classes and instances. They don't quite correspond to that model so you typically need choose a particular scheme or helper method to implement classes in terms of prototypes. (Some background on classes in JS.)

The module pattern is typically used for namespacing, where you'll have a single instance acting as a store to group related functions and objects. This is a different use case to what prototyping is good for. They're not really ‘vs’ each other, you can quite happily use both together (eg put a constructor-function inside a module and say new MyNamespace.MyModule.MyClass(arguments)).