Structuring a large web application for multiple developers

Question

I have several developers who will start working on the jquery-based web application interface. How can we structure the application so that several developers can work with ui at the same time. The end result for the user will be just one web page, but not all of my client development work in one file. Another team is already working at the back end.

Answer 1

We ended up using Dojo (1.3) for this project, as it had a mechanism for writing modular javascript (dojo.require), which we could not find in jQuery. There are currently several AMD libraries (asynchronous module definitions), such as RequireJS or curl.js, that can be used with jQuery. If I started this project now (instead of 2008), the answer to my question would include using the AMD library and, possibly, the javascript mvc framework. Dojo still has everything, we still use it.

Answer 2

If you start completely from scratch, you can break it down into a standard three-tier architecture.

Ask one person to work on the database structure and create appropriate data access libraries.

-/ , .

jQuery.

, , /, .

Answer 3

, , SCM .

, , javascript , , /, .

Answer 4

, DIV ( ) , CSS JS CSS jQuery , .

CSS , jQuery ( CSS-), "" , .

( ) , CSS JS ( ) gzipping, .

, CSS - , , , .

Answer 5

- , , , .

JavaScript : , , , .

, jonnii, SCM . , , , . git SVN, Windows ( TortoiseSVN, , SCM).

Answer 6

, , , , . - subversion , , , . .:) HTH

Answer 7

, , , MVC MVP. "-" , "" . , " " MVC, .

(Note: I'm NOT a Java developer, C # actually, but you can get an idea)

URL:

    /products/532

With re-writing Url, it will be a "web page" and its compiled "code", for example:

/products/showproduct.jsp?productid=532
/products/showproduct.java (code behind)

But with pages in MVC, this will be:

/Controllers/ProductController.java <- ProductController.ViewProduct(int id)
/Models/ViewModels/Product.java <- Product() class
/Views/Product/Index.html <- very simple display of html.

ProductController searches and retrieves the ViewModel of Product (), hooks up the index view, replaces any displayed variables, and finally, ProductController returns the completed html to the client.

This approach abstracts the logic of the web page into code that can be managed, versioned, merged, forked, etc. in your source repository.