Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 7 of 7
  1. #1
    New to the CF scene
    Join Date
    Aug 2007
    Posts
    5
    Thanks
    1
    Thanked 0 Times in 0 Posts

    client-side, server-side, database. but which first?

    which one would you do first and in which order?


    1. client-side - gui
    2. server-side - main programs
    3. database - xml, mysql access, flat-files. any data repository.

    in what order would you build these?

  • #2
    Regular Coder croatiankid's Avatar
    Join Date
    Jan 2006
    Posts
    665
    Thanks
    1
    Thanked 12 Times in 12 Posts
    I would definitely do GUI last, don't know about the other two though.

  • #3
    Rockstar Coder
    Join Date
    Jun 2002
    Location
    USA
    Posts
    9,074
    Thanks
    1
    Thanked 328 Times in 324 Posts
    3, 2 and then 1

    You can't build the server program until it has some place to pull and send data. And then you can't really build the client program until you have at least a semi working server app. Then you'll have to probably debug them together.
    OracleGuy

  • Users who have thanked oracleguy for this post:

    bakhtn (08-31-2007)

  • #4
    Regular Coder ralph l mayo's Avatar
    Join Date
    Nov 2005
    Posts
    951
    Thanks
    1
    Thanked 31 Times in 29 Posts
    I always do the client side first. Decide the simplest and most intuitive way to do things, mock it up, refine it to eliminate redunancy, bury obscure options and highlight the most common paths, and then, only when you've got something that looks like you'd actually want to use it, make it work by filling in the middle- and back-end. Doing the backend stuff first is easier for the developer but tends not to benefit the user. Your representation of the data is likely to reflect aspects of your database design instead of the most efficient way to visualize and utilize the data-- which you may not even know until you try it out, ie, by creating the client-side interface.

    Do the database normalization second, and then the server-side scripting in the middle. The whole purpose of the script is to make connections between the client and the database. If you do it before the things it connects you're likely to end up solving a lot of the wrong problems.
    Last edited by ralph l mayo; 09-02-2007 at 12:35 AM.

  • #5
    Master Coder
    Join Date
    Feb 2003
    Location
    UmeŚ, Sweden
    Posts
    5,575
    Thanks
    0
    Thanked 83 Times in 74 Posts
    Have to side with ralph here - in my experience, applications "feel" better if they are designed by first sorting out the user interface (client side front end), then the database (server side back end). And when both those are in place, you do the transport layer, which consists of server programs (server side front end) and the [forms|link uris|AJAX]+ (client side back end) and the debugging of the transport layer on both sides in unison.
    Last edited by liorean; 09-02-2007 at 02:13 PM.
    liorean <[lio@wg]>
    Articles: RegEx evolt wsabstract , Named Arguments
    Useful Threads: JavaScript Docs & Refs, FAQ - HTML & CSS Docs, FAQ - XML Doc & Refs
    Moz: JavaScript DOM Interfaces MSDN: JScript DHTML KDE: KJS KHTML Opera: Standards

  • #6
    Rockstar Coder
    Join Date
    Jun 2002
    Location
    USA
    Posts
    9,074
    Thanks
    1
    Thanked 328 Times in 324 Posts
    I was referring to the actual implementation part of the development cycle. Like once all the specifications and the design has been finalized.

    Otherwise yes, as my peers have pointed out, you'll end up with some hacking on your backend design if you design and implement it before you have a final client side design.
    OracleGuy

  • #7
    Master Coder
    Join Date
    Apr 2003
    Location
    in my house
    Posts
    5,211
    Thanks
    39
    Thanked 201 Times in 197 Posts
    Well, with my limited knowledge, I would suggest a different proposal.

    1. Plan your whole project so that you know how you would like it to be presented. With that done follow this strategy: -

    a. build your db.
    b. build the scripts to gather data from the db and present it in the web page.
    c. style the presentation using CSS

    bazz


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •