I have gone through some of the ASP.Net tutorials here. I have also been going through an ASP.Net/C# book. I am going to try to build a simple application based on what I learned. I have a design document that defines the database tables, page layouts, flow,
etc. Now, I am ready to start coding. But, what page do I start with? Here is my simple application description:
There will be a Login page. After a user logs in, the next page that opens will display a list of motorcycles that the user owns.
Each row on the Motorcycle List page will have a button to open a new page with a list of trips made on the motorcycle clicked.
So, what page do I code first? Do I code sequentially? Login -> Motorcycle List page -> Trip List page.
Or, do I code the Motorcycle List page and Trip List page to retrieve dummy data from the database, tie these two pages together (that is, code the button on the Motorcycle List page to open the Trip List page and retreive trips based on the Motorcycle ID.)
Then, code the Login page to open the Motorcycle List page and retreive a list of motorcycles associated with the user.
How does one go from a design to coding?
I know that this is a simple application and can probably be built in either of the two ways I described. But, what about a bigger application with a lot more pages and functionality? How does one break down a design and figure out how to build the application?
it's depend on each people. for me, i prefer to code the code-behind first and design after. start with the first page, and go trought other. start programming with clean-code way if you just start learning programming (it will save you more time after :D)
for your kind of website, if you want page security, start with the login page to test your security meanwhile you do other page.
A lot of people go from Business/DB logic to UI. But, really its a personal choice. Since, you are just beginning, I would suggest to start from Login page and related Business logic and so on.
---------------------------------------------------------------------------
Hope this helps, if it does then mark it as answer
Rohit
blog sweet blog
I don't know how your general coding skills are but there are a number of options.
Based on what you wrote in your question I would suggest you start out with setting up your database. Setting up the database and creating the tables usually gives you some feeling of what your application will be like when you talk about the data. Cause
you will probably have relations between the tables.
Add some sample data to it so you can verify the database structre.
So once you are done setting up your database / tables the next step would be to retreive the information from the database into your webapplication. I would not suggest you start of with the login panel, but just start with the simple list of motorcycles.
Cause you didn't yet wrote the login page you do not have to worry about filtering out the correct records for the user that is logged on. But in this stage you can just focus on getting your data shown inside your webapplication.
Once you've got that right you might wanna continue with the detail page / trip list page, so that your application is working as it should without the login part.
And last you will add the login part, and apply the login credentials on the other tables.
Hope this helps.
Matthijs Koopman
Please mark my reply as answer if you found it help full
Yes - That is how the book develops pages and the application: From the database tables to the stored procedures to the business objects to the UI pages. It makes a lot of sense when I see it done that way.
Your suggestion as follows seems like the best way for me to proceed. The motorcyle page/data seems like the central part of the application.
"So once you are done setting up your database / tables the next step would be to retreive the information from the database into your webapplication. I would not suggest you start of with the login panel, but just start with
the simple list of motorcycles. Cause you didn't yet wrote the login page you do not have to worry about filtering out the correct records for the user that is logged on. But in this stage you can just focus on getting your data shown inside your webapplication.
Once you've got that right you might wanna continue with the detail page / trip list page, so that your application is working as it should without the login part."
Ken_Ohio
Member
3 Points
16 Posts
Going from design to code: How does one build a web application page by page?
Nov 10, 2012 01:28 PM|LINK
I have gone through some of the ASP.Net tutorials here. I have also been going through an ASP.Net/C# book. I am going to try to build a simple application based on what I learned. I have a design document that defines the database tables, page layouts, flow, etc. Now, I am ready to start coding. But, what page do I start with? Here is my simple application description:
There will be a Login page. After a user logs in, the next page that opens will display a list of motorcycles that the user owns.
Each row on the Motorcycle List page will have a button to open a new page with a list of trips made on the motorcycle clicked.
So, what page do I code first? Do I code sequentially? Login -> Motorcycle List page -> Trip List page.
Or, do I code the Motorcycle List page and Trip List page to retrieve dummy data from the database, tie these two pages together (that is, code the button on the Motorcycle List page to open the Trip List page and retreive trips based on the Motorcycle ID.) Then, code the Login page to open the Motorcycle List page and retreive a list of motorcycles associated with the user.
How does one go from a design to coding?
I know that this is a simple application and can probably be built in either of the two ways I described. But, what about a bigger application with a lot more pages and functionality? How does one break down a design and figure out how to build the application?
ketthos
Member
243 Points
98 Posts
Re: Going from design to code: How does one build a web application page by page?
Nov 10, 2012 02:29 PM|LINK
it's depend on each people. for me, i prefer to code the code-behind first and design after. start with the first page, and go trought other. start programming with clean-code way if you just start learning programming (it will save you more time after :D)
for your kind of website, if you want page security, start with the login page to test your security meanwhile you do other page.
goodluck
Rohit Kukret...
Participant
1663 Points
320 Posts
Re: Going from design to code: How does one build a web application page by page?
Nov 10, 2012 03:07 PM|LINK
A lot of people go from Business/DB logic to UI. But, really its a personal choice. Since, you are just beginning, I would suggest to start from Login page and related Business logic and so on.
Hope this helps, if it does then mark it as answer
Rohit
blog sweet blog
m.koopman
Participant
1372 Points
294 Posts
Re: Going from design to code: How does one build a web application page by page?
Nov 10, 2012 04:21 PM|LINK
I don't know how your general coding skills are but there are a number of options.
Based on what you wrote in your question I would suggest you start out with setting up your database. Setting up the database and creating the tables usually gives you some feeling of what your application will be like when you talk about the data. Cause you will probably have relations between the tables.
Add some sample data to it so you can verify the database structre.
So once you are done setting up your database / tables the next step would be to retreive the information from the database into your webapplication. I would not suggest you start of with the login panel, but just start with the simple list of motorcycles. Cause you didn't yet wrote the login page you do not have to worry about filtering out the correct records for the user that is logged on. But in this stage you can just focus on getting your data shown inside your webapplication.
Once you've got that right you might wanna continue with the detail page / trip list page, so that your application is working as it should without the login part.
And last you will add the login part, and apply the login credentials on the other tables.
Hope this helps.
Please mark my reply as answer if you found it help full
Ken_Ohio
Member
3 Points
16 Posts
Re: Going from design to code: How does one build a web application page by page?
Nov 10, 2012 06:50 PM|LINK
Matthijs:
Yes - That is how the book develops pages and the application: From the database tables to the stored procedures to the business objects to the UI pages. It makes a lot of sense when I see it done that way.
Your suggestion as follows seems like the best way for me to proceed. The motorcyle page/data seems like the central part of the application.
"So once you are done setting up your database / tables the next step would be to retreive the information from the database into your webapplication. I would not suggest you start of with the login panel, but just start with the simple list of motorcycles. Cause you didn't yet wrote the login page you do not have to worry about filtering out the correct records for the user that is logged on. But in this stage you can just focus on getting your data shown inside your webapplication.
Once you've got that right you might wanna continue with the detail page / trip list page, so that your application is working as it should without the login part."
Thanks to everyone for all the replies.
m.koopman
Participant
1372 Points
294 Posts
Re: Going from design to code: How does one build a web application page by page?
Nov 10, 2012 09:25 PM|LINK
Please mark my reply as answer if you found it help full
Ken_Ohio
Member
3 Points
16 Posts
Re: Going from design to code: How does one build a web application page by page?
Nov 11, 2012 05:29 PM|LINK
Thanks.
I wlil definitely post something here if I have any questions.
K