JS/JQ Shopping Cart

Quote:

---

Originally Posted by Komakech

Okay, let's see. Better because divs and spans are actual elements that can easily be manipulated by Javascript/jQuery. Plus you have full control over positioning, styling etc.. Divs and spans are easier to handle in general.

Tables do not style as easily, are harder to manipulate the data/element using Javascript/jQuery.

The only plus of tables if at all is they take 20 seconds to make if you use Dreamweaver.

In terms of the same output, technically you are incorrect, they output the same because you do not have a design for it. It's the most basic thing ever, white with black text... But now every website you ever go to do either has to be white with black text and no formatting or you need to spend the time to learn how to use HTML properly. Especially when HTML5 becomes a standard...

All the best,
Richard Komakech.

---

I was not directing my question towards tables. I know tables are the shittest thing ever and are from the likew 1980's. If I was going to do the site properly I'd use div tags for everything and not even think about using tables. But as what I needed it for - it was an easy option to use.

Quote:

---

Originally Posted by Matt Clarke

I was not directing my question towards tables. I know tables are the shittest thing ever and are from the likew 1980's. If I was going to do the site properly I'd use div tags for everything and not even think about using tables. But as what I needed it for - it was an easy option to use.

---

Quote:

---

Originally Posted by Matt Clarke

Please elaborate how his way is far better than the way I set mine out.

---

Did I not do that? You set your out in tables, I elaborated how it was a bad method compared to the industry standard method?!

It was an easy method but makes anything Javascript/jQuery related that little bit harder... But if you don't want to listen to our advice it's probably worth closing this thread since our help is being turned down...

All the best,
Richard Komakech.

Quote:

---

Originally Posted by Komakech

Did I not do that? You set your out in tables, I elaborated how it was a bad method compared to the industry standard method?!

It was an easy method but makes anything Javascript/jQuery related that little bit harder... But if you don't want to listen to our advice it's probably worth closing this thread since our help is being turned down...

All the best,
Richard Komakech.

---

Lol, mate. Your advice is not being turned down, I'm asking why my methods are not as good etc. I appreciate the advice and help and by saying that tables make it harder to update the tables in JS/JQ then I also take that into account. But as of yet I have no idea how to go about making what I want without re-structuring the page with div tags.

his help is being turned down. he needs to come up with a script he attempted and cant quite get it working then we will help. we cant just create it for you thats what google is for.

as for tables? dont underestimate tables, they are more powerful then you think. yea they are horrible for styling a webpage but for organizing data its the way to go and for styling the table its self is the same as other tags with more control (ex table, tr, td)

Quote:

---

Originally Posted by holthelper

his help is being turned down. he needs to come up with a script he attempted and cant quite get it working then we will help. we cant just create it for you thats what google is for.

as for tables? dont underestimate tables, they are more powerful then you think. yea they are horrible for styling a webpage but for organizing data its the way to go and for styling the table its self is the same as other tags with more control (ex table, tr, td)

---

I have previously attempted scripts for me to work with. I'll give it another go if need be - but I posted the thread thinking that it'd be some sort of basic stuff in JS which I could get to grips with like defining '1' inside the field as a variable = to '£1.00' or something then having the JS update the page when the field updates. I'll do a little more research myself as it seems I cant really gain the help I'm looking for.

Thanks to those whom replied and gave some sort of advice.

I would help you, but since it's homework, I'd rather you do it on your own.. lol ur much older then me, so you should be able to get it if i can.
Also, if you ever need help in the future for non-school related stuff, lemme know :)

Quote:

---

Originally Posted by Toxic998

I would help you, but since it's homework, I'd rather you do it on your own.. lol ur much older then me, so you should be able to get it if i can.
Also, if you ever need help in the future for non-school related stuff, lemme know :)

---

It's not really homework. It's something I'm building into my site which is not compulsory. I want to do it as it's a nice feature to have. It does not state inside of the Unit Specification that I have to do this. Thanks for the nice gesture though!

Quote:

---

Originally Posted by Matt Clarke

Please elaborate how his way is far better than the way I set mine out. We all have different ways of doing things but all output the same thing. Just because he uses the industry standard way of coding doesn't mean that it's going to be any better or worse than mine.

---

The code I write I can understand later in the future, and so can other developers who looks at it. There is a reason smart people get together and set industry standards. How are you ever going to tell what is crap and what is good code if you don't know the right way to do things? You must properly indent, separate control-code (javascript) from template code (html/css). You even want to separate HTML from CSS. No inline styling, and especially no inline control-code. It becomes an unmanageable mess. Why do you think I couldn't give you a simple 2 sentence answer? I can't be bothered to look through javascript when it's mixed in with all the template code.. I mean, it's just a huge headache. That's why "my" way (not even my way- it's someone else's way that I adopted for sanity reasons) is better than any thoughtless or unmanageable way. I'm not saying any other way is bad- it has to be manageable.

For example: I don't want to fuck around with onReadyStateChange or onLoad with all the different browsers whom do not agree on many essential features on the web. By putting all of my JavaScript code at the bottom of the <body> tag, I completely avoid that ugly boilerplate. Of/c, jQuery has a $.ready() function which works in every browser, but still..

Quote:

---

Originally Posted by Toxic998

I would help you, but since it's homework, I'd rather you do it on your own.. lol ur much older then me, so you should be able to get it if i can.
Also, if you ever need help in the future for non-school related stuff, lemme know :)

---

Helping people with homework is a bad thing? Nobody said you had to do it for him.

Quote:

---

Originally Posted by Matt Clarke

It's not really homework. It's something I'm building into my site which is not compulsory. I want to do it as it's a nice feature to have. It does not state inside of the Unit Specification that I have to do this. Thanks for the nice gesture though!

---

If you really want help with this, send me a private message with your Skype/MSN details and I shall go through it with you when we are both online. Make sure you have the files to hand to send me and TeamViewer installed.

I feel we have reached a stage in this thread where no one wants to help you and it's just becoming spam on the Coders Paradise section, for that reason I shall help you.

But be ready to conform your code to the proper way or I shall discontinue my help.

All the best,
Richard Komakech.