Do that often too. jQuery .data is pretty awesome for use as well.

Load rendering with modules in scripts I do not like. Which you can view when you use say chrome.

One the primary things I learnt at Uni is the Object Oriented Modal of design and Development, MVC etc.

Seperation of the function, display, data being a fundemental point to develop and all the benifits of that.

Also, Your HTML code will weigh more, i.e. a web page riddled with similar code will have a kb size that is a lot larger than necessary. The inline script and css will make the source more dense, search engines have to sift through it to find your actual content.

Your HTML code will never be truely cached but the external dependencies, such as the CSS and JavaScript files, will be cached by the visitor’s web browser after the first visit – this means that instead of loading a lot of superfluous HTML code for every page in your web site the visitor visits, it will quickly retrieve all style and interaction locally from the web browser cache and thus improve perfomance further.

No fall back interaction, and harder to manage, correct and update along with poor attrinbute accessability. Having your scripting in one central location makes your development time more effecient, working on new aspects of the site has no effect on the live site, functions can be wrote once called many times and only when needed. Object coding in Javascript improves performance, management, use and more also.

With these in mind the page load is just longer with inline scripting and the event handling is poorer and then coupled with the other elments mentioned above.

Just better done right BC has runs gzip, you can optimise your code and the server caching of css, script, image files and the browser it just all leads to better perfomance of your site which is also increasingly something google wants to see to rank you well.

From C to jScript to Java, that is a what you do

You are even able to create class's in javascript

http://www.htmlgoodies.com/html5/tutorials/create-an-object-oriented-j avascript-class-constructor.html#fbid=gkA89HyUIS3

Adam,
To start you off in terms of basics....

Have a functions file (I wrote a guide on the Adobe site but BC took their guide section down as it was another place. I got it saved and I will put it as a guide on these forums soon!) where you write your functions. Each function for a job.

Have a Dom.js file where you run the dom in jQuery. One time call. In here you can call a function when to run it.

So say you have the home page slider but that is only home page.

You wrap the function in an if statement that basically is..

If element exists (.length) then run this function.

If the element does not exist the function does not run.

You can lazy load and call scripts, create script library to run (On our sites we have one extra .js at the bottom called to do all our magic) and add plugins easily to a site, lazy load them so they do not run every time you load a page even if not needed....

You can progress to convert everything into objects not just functions.

You can progress still to use classes in javascript..

jQuery has great features to aid in all these areas.....

So much you can do to optimise not just your sites and scripts but how you operate running these methods.

The OO apporach to your work is modular design and development just means you can do more for less and sites are just better.

Penny, smaller the code the better really, Lots of people use jQuery plugins because they do not understand javascript or jQuery that well to get something going. Often 4 lines of code can be done to do the same job.

Some aspects wont work in that sense for web development and more over BC but you can come up with a really nice modal for yourself and BC.

It is actually a bit more load Adam over you think it less http requests
But you are right in a way but I have an awesome BC site framework now which can be more with more time applied to it even further that is not a template for sites but builds your sites with BC pretty awesome.

I seen sites which do the jquery DOM loading 20/3o times because of all the inline scripting! pretty shocking, lol.

You can get it to have one js called in your templates which loads what you need when you need it and all the basics etc and out of the head to reduce the load there. So clean, performs well.

Ecommerce framework fuel offers through the ecommerce websites business has HEAPS of script to fix up BC eCommerce (which has so many issues) along with the standard issues and of course securezone ones all together. More script then I like but I would hate to think the load it would be without some of the above mentioned stuff in play. And that even uses old ways we do things, just a big job to update it at the moment.

Git is awesome, How it works in Coda 2 is awesome BUT.... You do not need it in BC. It is great for huge projects and team environments and big system development but a bit much for BC and I find it slows you down.

Bit to much I think.

With some of the above and applying that to how you build BC in general, which I think literally the Penny has droppoed on that from Penny and sounds like she has some improvements to make on her BC builds already (which will be awesome) you can have great fun building BC sites. I do.

Here you go by the way re-document:

http://forums.adobe.com/docs/DOC-2964

Formed up this evening. You may know a lot or do some or all of it but it a good guide for lots of people hopefully.

There are a few different ones but I call them in the Dom.js but through lazy laoding. They are declared with cache or not and their dependencies if they have them and then call functions / objects on the Dom call.

IF functions call a plugin then the plugin is only loaded when called.

Something else you can do is use getScript in jquery in a function to call another script to use only when you need it in that function.