What are my options?

dokko · 17 Jan 2010 at 15:45

I want to create a computer component selector (which basically allows basic users to select components such as GFX card etc...and get the right motherboard to go with it) which will be hosted in a webpage, the selector will start off with AMD or Intel, then cut out the components that won't work with their choice, right untill they have a full PC. (A bit like Crucials memory selector but for a whole computer)

I want the interface to be graphical an not just dropdowns showing lists of data. Like a tree flowing down starting at CPU

What language and tools should i be looking at for something like this?

I also want to create a questionnaire which will determine what type of PC they are looking for, for example a HTPC and if so do not show full sized cases and MB's, can i link all three together? Component selector, questionnaire and the one database (which will hold all the data on a certain component)?

I've been told VB.net would be a good way to create the component selector though i've never used it, i have done VB and was ok with that though.

Thanks for your time.

dangerstat · 17 Jan 2010 at 15:50

Anything dynamic would be fine, PhP, JSP etc.... All you really need to do there is work out how to map things together (so DDRIII -> DDRIII supporting motherboards etc..) which is just a case of some sort of hashmap

dokko · 17 Jan 2010 at 16:12

dangerstat said:
Anything dynamic would be fine, PhP, JSP etc.... All you really need to do there is work out how to map things together (so DDRIII -> DDRIII supporting motherboards etc..) which is just a case of some sort of hashmap

Dynamic for the questionnaire and selector? So just use a normal MySQL DB, should i stay away from access?

dangerstat · 17 Jan 2010 at 16:15

dokko said:
Dynamic for the questionnaire and selector? So just use a normal MySQL DB, should i stay away from access?

Stay away from Access.

A MySQL database with a PhP interface would do the job with no problems what so ever.

dokko · 17 Jan 2010 at 16:48

dangerstat said:
Stay away from Access.

A MySQL database with a PhP interface would do the job with no problems what so ever.

Php for the interface, as in the component selector? I had some trouble with PHP and OOD, i was ok until then, i really could get my head around it (just like Java)

dangerstat · 17 Jan 2010 at 17:19

dokko said:
Php for the interface, as in the component selector? I had some trouble with PHP and OOD, i was ok until then, i really could get my head around it (just like Java)

Essentially PHP will be the "bit" that connects to the MySQL database runs your queries and displays the results. I dunno what OOD is. PHP is easy you can get to grips with in a matter of hours TBH

dokko · 17 Jan 2010 at 17:21

dangerstat said:
Essentially PHP will be the "bit" that connects to the MySQL database runs your queries and displays the results. I dunno what OOD is. PHP is easy you can get to grips with in a matter of hours TBH

OOD - object oriented design.

Just like Java, all objects. I understand it now, but don't like using the techniques associated with it.