Since I have my Discovery Park Internship, I couldn't attend the lab but I got to know from my friend Dharmil what happened in the lab. The team went over what the Design reviewers told us. The comments, suggestions and other information. We had to do this because we felt it was worth giving it a whole lab so that we can decide on what to in the future. The team was divided into further small teams to accomplish the tasks in a much more efficient way. I was asked to do not only the UI but also collaborate with the C# team( the core functionality) .
The experience was really good , to work with the C # team.
In the team meeting I was collaborating the functionality team dynamically. I was assigned to update the default default.aspx. I had to write the code for the default, this is what the user will see no matter if he has account or not.
Below you can find the code of the particular file.
<input id="expandAll" type="button" value="Expand All" />
<input id="collapseAll" type="button" value="Collapse All" />
<asp:Repeater runat="server" ID="eventsList" OnItemDataBound="eventsList_ItemDataBound">
<HeaderTemplate>
<ul class="jobsTemplate eventsHeader">
<div><div style = "margin-left: 35px; display: inline;">Name</div> <div style = "margin-left:45px; display: inline;">Location</div><div style = "margin-left: 80px; display: inline;">Date</div><div style = "margin-left: 155px; display: inline;">Time</div></div>
</ul>
</HeaderTemplate>
<ItemTemplate>
<ul class = "jobsTemplate events">
<li><a class = "expand"><img src = "/Images/expand.gif" alt = "Expand Jobs" /></a></li>
<li><%# DataBinder.Eval(Container, "DataItem.Name") %></li>
<li><%# DataBinder.Eval(Container, "DataItem.Location") %></li>
<li><%# DataBinder.Eval(Container, "DataItem.StartdateTime", "{0:f}") %> - <%# DataBinder.Eval(Container, "DataItem.EnddateTime", "{0:t}")%></li>
</ul>
<asp:Repeater runat="server" ID="jobsList">
<HeaderTemplate><div class = "jobsList"></HeaderTemplate>
<ItemTemplate>
<ul class = "jobsTemplate jobs">
<li><%# DataBinder.Eval(Container, "DataItem.Name") %></li>
<li><%# DataBinder.Eval(Container, "DataItem.StartdateTime", "{0:f}")%> - <%# DataBinder.Eval(Container, "DataItem.EnddateTime", "{0:t}")%></li>
<li><%# DataBinder.Eval(Container, "DataItem.Maxpeople") %></li>
<li><%# DataBinder.Eval(Container, "DataItem.Description") %></li>
</ul>
</ItemTemplate>
<FooterTemplate></div></FooterTemplate>
</asp:Repeater>
I had to do the repeater class but it was a lot of work because it was a two repeater classes.
So, it took a lot of time to figure out how the repeater class works.
But at the end of the meeting, the default.aspx was partially done.
Friday, October 29, 2010
Friday, October 22, 2010
Team Meeting - week 8
We met in Epics lab as usual. We had to do a lot of things this meeting because we were just done with the design review. We had a lot of tasks to be done. I have created the edit.aspx in the Admin/Event folder. It had to do with a lot of text boxes , bounds on the length of text boxes.
It had to deal with a lot of the look of it since I have to do the UI part of the whole website ( Dharmil, Dan also helped me). I got the basic functionality of the edit.aspx but the major problem was it was not organised. So , I had to work on fixing how it looks. Finally at the end of the meeting I was able to come up with a pretty decent look.
It had to deal with a lot of the look of it since I have to do the UI part of the whole website ( Dharmil, Dan also helped me). I got the basic functionality of the edit.aspx but the major problem was it was not organised. So , I had to work on fixing how it looks. Finally at the end of the meeting I was able to come up with a pretty decent look.
Thursday, October 21, 2010
Lab -WEEK 8
We had our Design Review today. Jason, Jay, Dharmil, Dan presented on this day.
Jason started with the introduction of the presentation and then Dharmil was going through he screen shots of past 8 weeks. Dan explained about the databases and Jay went through use cases.
We presented for a very long time, all the people asked us a lot of questions.
Myself and John were talking down all the comments and suggestions we have got.
I think the presentation was satisfactory , we have to make a lot of changes to the existing site and also to the code.
These were all the queries and suggestions we have got.
VM
Clarify, did you need to deliver this or next October?
What database type did you use last semester?
Have you checked the MySQL with CFRC? What is required?
Area code for phone number
Can you edit the events or jobs?
Time, user, job, cell phone, home phone for event list
Suffix, Jr. for family members
How will family members sign up?
FamilyID, call it memberID
Missing actor for “random visitors”
We don’t know about rooms for UPRC
Don’t go into building a website without designs
Show CFRC sketches
Use cases, etc.
For printing size, change style sheets
Test in extra-large font
Some usability, w2c, blind test, color blind
What will they have two years from now?
Resolution upgrades
OS upgrades
Question slide is messed up
Requirements document?
Get follow ups
Use presentation examples that make sense for not tech savvy:
Five use case tables, not one
Simple as possible
Take screen drawings. Step1a, step1b
Add more diagrams: unified model, activity, community, class (UML 2.0)
Information protection, continue to take steps
PII standards
Have a certificate, “we are PII certified” so people trust using their information
How do you update project partner? Be crystal clear communication wise with the project partner. Do you need support people? Training?
Keep William Oakes up to date. New stakeholder. Send him email with updates.
Plan for successful delivery, have team test database problems now.
Jason started with the introduction of the presentation and then Dharmil was going through he screen shots of past 8 weeks. Dan explained about the databases and Jay went through use cases.
We presented for a very long time, all the people asked us a lot of questions.
Myself and John were talking down all the comments and suggestions we have got.
I think the presentation was satisfactory , we have to make a lot of changes to the existing site and also to the code.
These were all the queries and suggestions we have got.
VM
Clarify, did you need to deliver this or next October?
What database type did you use last semester?
Have you checked the MySQL with CFRC? What is required?
Area code for phone number
Can you edit the events or jobs?
Time, user, job, cell phone, home phone for event list
Suffix, Jr. for family members
How will family members sign up?
FamilyID, call it memberID
Missing actor for “random visitors”
We don’t know about rooms for UPRC
Don’t go into building a website without designs
Show CFRC sketches
Use cases, etc.
For printing size, change style sheets
Test in extra-large font
Some usability, w2c, blind test, color blind
What will they have two years from now?
Resolution upgrades
OS upgrades
Question slide is messed up
Requirements document?
Get follow ups
Use presentation examples that make sense for not tech savvy:
Five use case tables, not one
Simple as possible
Take screen drawings. Step1a, step1b
Add more diagrams: unified model, activity, community, class (UML 2.0)
Information protection, continue to take steps
PII standards
Have a certificate, “we are PII certified” so people trust using their information
How do you update project partner? Be crystal clear communication wise with the project partner. Do you need support people? Training?
Keep William Oakes up to date. New stakeholder. Send him email with updates.
Plan for successful delivery, have team test database problems now.
Lab meeting( 5 through 7)
I could not attend these labs because I had to attend a seminar at the same time. I spoke to William about this earlier as well. I didn't attend the lab meeting -5 because I had an exam. I got some information from Dharmil so as what was happening in labs.
"The below content is taken from Dharmil's blog as reference. "
In lab -6 , my team mates installed MySQL on their computers. Jason added the two MySQL connectors for C# in Pivotal tracker. They added some new UI's(which is my part) to the Pivotal tracker.
In lab-7, Jay,Dharmil, Daniel volunteered to give the Design review presentation on the next lab.
ER diagrams was too much confusing for the customers, so they thought of a new idea which looked something like this:
Basically they went in detail over what they can do for the presentation. They have assigned certain jobs to an individual.
1. Dharmil would cover the screenshots,
2. Daniel would do ERD since he came up with it
3. Jay would do the USE Cases
4. Jason would do the Intro and Conclusion since he knows the Volunteer Management project the best
2. Daniel would do ERD since he came up with it
3. Jay would do the USE Cases
4. Jason would do the Intro and Conclusion since he knows the Volunteer Management project the best
So, my team is ready to give the presentation in the next lab.
Lab meeting -4
I have attended the lab 4 which was held on September 23 rd in ARMS. We have discussed a lot of things in the lab.
I have added two new CSS files
1) Default.css
2)style.css
Below is the code for Default.css
@charset "utf-8";
/* CSS Document */
/* General */
*
{
margin: 0;
padding: 0;
}
html
{
height: 100%;
font-size: 62.5%;
}
body
{
height: 100%;
background: #DEDEDE url('../img/bg2.gif') repeat-x 0 0;
text-align: center;
font: 1.2em Verdana, Arial, Helvetica, sans-serif;
position: relative;
width: 900px; min-width: 900px;
margin: 0 auto;
padding-bottom: 60px;
}
a:link, a:visited
{
color: #007099; text-decoration: underline;
}
a:hover
{
text-decoration: none;
}
.noscreen
{
display: none;
}
.cleaner
{
clear: both;
height: 0;
font-size: 0;
visibility: hidden;
}
/* Skip menu */
.hidden
{
position: absolute;
top: -10000px;
left: 0;
width: 1px;
height: 1px;
overflow: hidden;
}
abbr, acronym, span.abbr
{
border-bottom: 1px dotted black;
cursor: help;
}
/* Wrapper */
#wrapper {width: 900px; margin: 40px auto 60px auto; border: 4px solid #FEFEFE; border-bottom: 0; display: table;}
/* Header */
.header {width: 900px; height: 100px; margin: 0 auto; position: relative; text-align: left; background-color: #007099;}
/* Headings */
h1 {color: #FFF; font: 2.8em Georgia, "Times New Roman", Times, serif; padding-top: 14px; margin: 0 0 11px 30px;}
h1 a:link, h1 a:visited {color: #FFF; text-decoration: none;}
h1 span {border-bottom: 1px solid #66A9C2; padding-bottom: 2px;} h1 span#color {color: #FEB125; border: 0;}
h2 {font: 1.8em normal Georgia, "Times New Roman", Times, serif; background: url('../img/b.gif') no-repeat 0 50%; padding-left: 23px; margin-bottom: 5px; letter-spacing: 1px;}
h3 {font: 1.3em Georgia, "Times New Roman", Times, serif; background: url('../img/h3-bg.gif') repeat-x 0 60%; letter-spacing: 1px; margin-bottom: 3px;}
h3 span {background: #FFF; padding: 2px 8px; margin-left: 20px; background-color: #FFFFC7; border-left: 4px solid #FFF; border-right: 4px solid #FFF;}
.col-l h3 {font: bold 1.1em Verdana; background: #0085B6 url('../img/h3-bg2.gif') repeat-x 0 0; color: #FFF; text-align: center; padding: 7px 0; letter-spacing: 0;}
/* Paragraphs */
p {line-height: 1.9; margin-bottom: 14px;}
p#about {font-size: 1.2em; line-height: 1.2; margin: 0 0 0 30px; color: #FEFEFE}
p#backlinks {position: relative; top: -56px; font-size: 0.9em; color: #656565;} p#backlinks a, p#backlinks a:visited {color: #656565;}
p#backlinks a:hover {color: #151515;}
/* Page */
.page {width: 900px; margin: 0 auto; text-align: left; background: #FFF url('../img/content-bg.gif') repeat-y 0 0; color: white;}
.col-l {float: left; width: 23%; background-color: #DDECF1; border-top: 1px solid #578B9E;}
.col-r {float: right; width: 100%;}
.col-l-in {margin: 0 0 0 0;} .col-r-in {margin: 1.2em 2em 2em 1.2em;}
.bodyContent
{
color: Black;
}
/* Article */
.article {background-color: #DDD; border: 1px solid #AAA; padding: 5px 12px 27px 12px; margin: 14px 0 14px 0; position: relative; _width: 619px;}
.article-zebra {background-color: #E6FFD2; border: 1px solid #B5E390; padding: 5px 12px 27px 12px; margin: 8px 0 14px 0; position: relative; _width: 619px;}
.article p, .article-zebra p {line-height: 1.5; margin-bottom: 3px;}
.article a.more, .article-zebra a.more {position: absolute; bottom: 7px; right: 10px; line-height: 1;} /* Read more positioning */
.article a.more, .article a.more:visited, .article-zebra a.more, .article-zebra a.more:visited
{background-color: #343434; color: #FEFEFE; padding: 5px 7px; text-decoration: none; border: 1px solid #606060; font-size: 0.9em;}
.article a.more:hover, .article-zebra a.more:hover {text-decoration: underline;}
/* Gallery */
.gallery {width: 99%; margin: 18px 0 0 0;}
.gallery img {border: 1px solid #AAA; margin-right: 12px;}
.gallery a:hover img {border: 1px solid #505050;}
/* Menu */
#menu-box {
width: 99.7%;
position: absolute;
right: 1px;
bottom: 1px;
background-color: #353535;
border: 1px solid #5A5A5A;
border-bottom: 0;
}
ul#web {list-style: none; text-align: right; margin-right: 30px;}
ul#web li {display: inline; color: #FFF;}
ul#web li a#first {border-left: 1px solid #505050;}
ul#web li a, ul#web li a:visited {float: right; display: block; color: #FFF; padding: 10px 26px; border-right: 1px solid #505050;}
ul#web li a:hover {text-decoration: none; background-color: #505050;}
ul#web li a.active {background: black !important;}
ul.menu {list-style: square; list-style-position: inside; margin: 8px 0 12px 16px;}
ul.menu li {margin-bottom: 9px;}
ul.menu li a, ul.menu li a:visited {color: #101010; text-decoration: none;}
ul.menu li a:hover {color: #181818; text-decoration: underline; background: 0;}
/* Footer */
#footer {width: 900px; height: 50px; margin: 0 auto; background-color: #222222; border-bottom: 4px solid #FEFEFE; border-top: 2px solid #909090;}
#footer a:link, #footer a:visited {color: #FFF; font-weight: normal;}
#footer ul {list-style-type: none; color: #FFF; padding: 16px 0 0 14px; text-align: left; float: left; width: 430px; }
#footer ul li {float: left; display: inline; white-space: nowrap;}
#footer ul li a, #footer ul li a:visited {margin: 0 6px;}
#footer p {float: right; text-align: right; color: #FFF; padding: 10px 10px 0 0; line-height: 1.2;}
/* Searching form */
form.searching {width: 252px; position: absolute; top: 18px; right: 2px;} form.searching fieldset {border: 0;}
input.search {width: 150px; border: 1px solid silver; letter-spacing: 1px; padding: 4px 7px;}
form.searching input.hledat {letter-spacing: 1px; font-weight: bold;}
form.searching label {display: none;}
/* Standard form */
.formTable td {text-align: right; padding-right:2px;}
.label
{
float: left;
text-align: right;
}
.input
{
float: left;
text-align: left;
}
Below is the code for print.css
@charset "utf-8";
/* CSS Document - print style sheet */
body {
background-color: #FFFFFF;
font-family: Arial, Helvetica, sans-serif;
}
h1, h2, h3, h4, h5, h6 {font-family: Verdana, Arial, Helvetica, sans-serif; color: #595959;}
h1 {font-size: 15pt;}
h2 {font-size: 13pt;}
h3, h4, h5, h6 {font-size: 11pt;}
p {line-height: 1.3; font-size: 11pt;}
a:link, a:visited {
text-decoration: underline;
font-weight: bolder;
color: #000000;
}
a img {border: 1px solid #595959;}
.hidden {
position: absolute;
top: -10000px;
left: 0;
width: 1px;
height: 1px;
overflow: hidden;
}
form.searching, #menu-box , ul.menu, .col-l h3, #footer, br {
display: none;
}
John added image and also copy right at the bottom of the website.
Daniel put some Place holders for body and footer. Dharmil renamed the CSS files to the appropriate naming convention. Jason completed the file structure.
I have added two new CSS files
1) Default.css
2)style.css
Below is the code for Default.css
@charset "utf-8";
/* CSS Document */
/* General */
*
{
margin: 0;
padding: 0;
}
html
{
height: 100%;
font-size: 62.5%;
}
body
{
height: 100%;
background: #DEDEDE url('../img/bg2.gif') repeat-x 0 0;
text-align: center;
font: 1.2em Verdana, Arial, Helvetica, sans-serif;
position: relative;
width: 900px; min-width: 900px;
margin: 0 auto;
padding-bottom: 60px;
}
a:link, a:visited
{
color: #007099; text-decoration: underline;
}
a:hover
{
text-decoration: none;
}
.noscreen
{
display: none;
}
.cleaner
{
clear: both;
height: 0;
font-size: 0;
visibility: hidden;
}
/* Skip menu */
.hidden
{
position: absolute;
top: -10000px;
left: 0;
width: 1px;
height: 1px;
overflow: hidden;
}
abbr, acronym, span.abbr
{
border-bottom: 1px dotted black;
cursor: help;
}
/* Wrapper */
#wrapper {width: 900px; margin: 40px auto 60px auto; border: 4px solid #FEFEFE; border-bottom: 0; display: table;}
/* Header */
.header {width: 900px; height: 100px; margin: 0 auto; position: relative; text-align: left; background-color: #007099;}
/* Headings */
h1 {color: #FFF; font: 2.8em Georgia, "Times New Roman", Times, serif; padding-top: 14px; margin: 0 0 11px 30px;}
h1 a:link, h1 a:visited {color: #FFF; text-decoration: none;}
h1 span {border-bottom: 1px solid #66A9C2; padding-bottom: 2px;} h1 span#color {color: #FEB125; border: 0;}
h2 {font: 1.8em normal Georgia, "Times New Roman", Times, serif; background: url('../img/b.gif') no-repeat 0 50%; padding-left: 23px; margin-bottom: 5px; letter-spacing: 1px;}
h3 {font: 1.3em Georgia, "Times New Roman", Times, serif; background: url('../img/h3-bg.gif') repeat-x 0 60%; letter-spacing: 1px; margin-bottom: 3px;}
h3 span {background: #FFF; padding: 2px 8px; margin-left: 20px; background-color: #FFFFC7; border-left: 4px solid #FFF; border-right: 4px solid #FFF;}
.col-l h3 {font: bold 1.1em Verdana; background: #0085B6 url('../img/h3-bg2.gif') repeat-x 0 0; color: #FFF; text-align: center; padding: 7px 0; letter-spacing: 0;}
/* Paragraphs */
p {line-height: 1.9; margin-bottom: 14px;}
p#about {font-size: 1.2em; line-height: 1.2; margin: 0 0 0 30px; color: #FEFEFE}
p#backlinks {position: relative; top: -56px; font-size: 0.9em; color: #656565;} p#backlinks a, p#backlinks a:visited {color: #656565;}
p#backlinks a:hover {color: #151515;}
/* Page */
.page {width: 900px; margin: 0 auto; text-align: left; background: #FFF url('../img/content-bg.gif') repeat-y 0 0; color: white;}
.col-l {float: left; width: 23%; background-color: #DDECF1; border-top: 1px solid #578B9E;}
.col-r {float: right; width: 100%;}
.col-l-in {margin: 0 0 0 0;} .col-r-in {margin: 1.2em 2em 2em 1.2em;}
.bodyContent
{
color: Black;
}
/* Article */
.article {background-color: #DDD; border: 1px solid #AAA; padding: 5px 12px 27px 12px; margin: 14px 0 14px 0; position: relative; _width: 619px;}
.article-zebra {background-color: #E6FFD2; border: 1px solid #B5E390; padding: 5px 12px 27px 12px; margin: 8px 0 14px 0; position: relative; _width: 619px;}
.article p, .article-zebra p {line-height: 1.5; margin-bottom: 3px;}
.article a.more, .article-zebra a.more {position: absolute; bottom: 7px; right: 10px; line-height: 1;} /* Read more positioning */
.article a.more, .article a.more:visited, .article-zebra a.more, .article-zebra a.more:visited
{background-color: #343434; color: #FEFEFE; padding: 5px 7px; text-decoration: none; border: 1px solid #606060; font-size: 0.9em;}
.article a.more:hover, .article-zebra a.more:hover {text-decoration: underline;}
/* Gallery */
.gallery {width: 99%; margin: 18px 0 0 0;}
.gallery img {border: 1px solid #AAA; margin-right: 12px;}
.gallery a:hover img {border: 1px solid #505050;}
/* Menu */
#menu-box {
width: 99.7%;
position: absolute;
right: 1px;
bottom: 1px;
background-color: #353535;
border: 1px solid #5A5A5A;
border-bottom: 0;
}
ul#web {list-style: none; text-align: right; margin-right: 30px;}
ul#web li {display: inline; color: #FFF;}
ul#web li a#first {border-left: 1px solid #505050;}
ul#web li a, ul#web li a:visited {float: right; display: block; color: #FFF; padding: 10px 26px; border-right: 1px solid #505050;}
ul#web li a:hover {text-decoration: none; background-color: #505050;}
ul#web li a.active {background: black !important;}
ul.menu {list-style: square; list-style-position: inside; margin: 8px 0 12px 16px;}
ul.menu li {margin-bottom: 9px;}
ul.menu li a, ul.menu li a:visited {color: #101010; text-decoration: none;}
ul.menu li a:hover {color: #181818; text-decoration: underline; background: 0;}
/* Footer */
#footer {width: 900px; height: 50px; margin: 0 auto; background-color: #222222; border-bottom: 4px solid #FEFEFE; border-top: 2px solid #909090;}
#footer a:link, #footer a:visited {color: #FFF; font-weight: normal;}
#footer ul {list-style-type: none; color: #FFF; padding: 16px 0 0 14px; text-align: left; float: left; width: 430px; }
#footer ul li {float: left; display: inline; white-space: nowrap;}
#footer ul li a, #footer ul li a:visited {margin: 0 6px;}
#footer p {float: right; text-align: right; color: #FFF; padding: 10px 10px 0 0; line-height: 1.2;}
/* Searching form */
form.searching {width: 252px; position: absolute; top: 18px; right: 2px;} form.searching fieldset {border: 0;}
input.search {width: 150px; border: 1px solid silver; letter-spacing: 1px; padding: 4px 7px;}
form.searching input.hledat {letter-spacing: 1px; font-weight: bold;}
form.searching label {display: none;}
/* Standard form */
.formTable td {text-align: right; padding-right:2px;}
.label
{
float: left;
text-align: right;
}
.input
{
float: left;
text-align: left;
}
Below is the code for print.css
@charset "utf-8";
/* CSS Document - print style sheet */
body {
background-color: #FFFFFF;
font-family: Arial, Helvetica, sans-serif;
}
h1, h2, h3, h4, h5, h6 {font-family: Verdana, Arial, Helvetica, sans-serif; color: #595959;}
h1 {font-size: 15pt;}
h2 {font-size: 13pt;}
h3, h4, h5, h6 {font-size: 11pt;}
p {line-height: 1.3; font-size: 11pt;}
a:link, a:visited {
text-decoration: underline;
font-weight: bolder;
color: #000000;
}
a img {border: 1px solid #595959;}
.hidden {
position: absolute;
top: -10000px;
left: 0;
width: 1px;
height: 1px;
overflow: hidden;
}
form.searching, #menu-box , ul.menu, .col-l h3, #footer, br {
display: none;
}
John added image and also copy right at the bottom of the website.
Daniel put some Place holders for body and footer. Dharmil renamed the CSS files to the appropriate naming convention. Jason completed the file structure.
Saturday, October 16, 2010
Team meeting - 7
Myself, Dharmil and John met in the Epics lab and we started working on various issues.
I started working on sitemap ( control-flow)
John worked on the Epics logo that we have to put on the website.
Dharmil was working on site master.
My part of site map, This is the first time that I am working on the site map of any website. So, I had to do a lot of research on how to code the site map. I looked through the site maps of many websites. I have interacted with John to draw a flow chart of the control flow of the website. I have printed the code of a small site map code of some website and tried to understand how the control flow works. I got some idea of how it was working. I coded a bit on the lab but I promised to finish the coding by next day noon. I finished the whole site map code the next day. The whole process took me about three hours. ( since it is the first time)
This is the code I came up with:
<?xml version="1.0" encoding="utf-8" ?>
<siteMap xmlns="http://schemas.microsoft.com/AspNet/SiteMap-File-1.0" >
<siteMapNode url="~/" title="Home" description="Home Page" roles="none" >
<siteMapNode id="P1" url="~/default.aspx" title="Home" description="Home Page"> </siteMapNode>
<!-- <siteMapNode url="~/default.aspx#" title="Event Calendar" description="Event Calendar" /> -->
<siteMapNode id="P2" url="~/login.aspx" title="Login" description="Login" />
</siteMapNode>
<siteMapNode id="P3" url="~/signup.aspx" title="Create Account" description="Create Account" />
</siteMapNode>
<siteMapNode id="P4" url="~/forgotpassword.aspx" title="Forgot Password" description="Forgot Password" />
<siteMapNode id="P5" url="~/viewevent.aspx" title="View Event" description="View Event" roles="none" /
</siteMapNode>
<siteMapNode id="P6" url="~/activate.aspx" title="Activate Account" description="Activate Account" roles="none" />
</siteMapNode>
<siteMapNode id="P7" url="~/Admin/" title="Home" description="Admin Home">
<siteMapNode url="~/Accounts/default.aspx" title="Account" description="Account" />
<siteMapNode url="~/Accounts/edit.aspx" title="Edit Account" description="Edit Account" roles="none" />
<siteMapNode url="~/Accounts/create.aspx" title="Create Account" description="Create Account" roles="none" />
</siteMapNode>
<siteMapNode url="~/Events/default.aspx" title="Event" description="Event" />
<siteMapNode url="~/Events/edit.aspx" title="Edit Event" description="Edit Event" roles="none" />
<siteMapNode url="~/Events/create.aspx" title="Create Event" description="Create Event" roles="none" />
</siteMapNode>
<siteMapNode url="~/Admin/account.aspx" title="Account1" description="Account1" roles="none" />
<siteMapNode url="~/Admin/changepassword.aspx" title="Change Password" description="Change password" roles="none" />
<siteMapNode url="~/Admin/default.aspx" title="Default" description="Default" roles="none" />
<siteMapNode id="P8" url="~/Volunteer/" title="Volunteer" description="Volunteer Home">
<siteMapNode url="~/account.aspx" title="Account2" description="Account2" />
<siteMapNode url="~/changepassword.aspx" title="Change Password" description="Change password" roles="none" />
<siteMapNode url="~/default.aspx" title="Default" description="Default" roles="none" />
</siteMapNode>
</siteMapNode>
</siteMap>
I have committed the code. It was found that this code resulted in some problems , it had some bugs.
But I tried my level best to come up with a solution.
John was editing the logo so as to fit in the website. Dharmil and John faced problems with the size of the picture and also the way how it looks. John did some picture editing and Dharmil got it working.
This is what we did in the team meeting.
Friday, October 8, 2010
Team meting-6
Today we ( John, myself, Dharmil) were continuing in what we did in the last team meeting.
John was working on the Family.cs file
Myself and Dharmil were working on the UI part of the login.aspx
It was a pretty simple piece of code, but we had a small issue in getting it to look in the right format.
We tried different formats( tables, doing it manually), finally we fixed with the table format.
We put it to the centre and we had a small button for Login. Here is the code for it :
<%@ Page Title="" Language="C#" MasterPageFile="~/Site.Master" AutoEventWireup="true"
CodeBehind="login.aspx.cs" Inherits="Volunteer_Management.login" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" runat="server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="body" runat="server">
<div class="login">
<form action = "login.aspx"></form>
<center>
<table>
<tr>
<td>Email:</td>
<td><asp:TextBox ID="emailTextBox" runat="server"></asp:TextBox></td>
</tr>
<tr>
<td>Password:</td>
<td><asp:TextBox ID="passwordTextBox" runat="server"></asp:TextBox></td>
</tr>
</table>
<asp:Button ID="loginButton" runat="server" Text="Login" onclick="submit_Click" />
</center>
</div>
<div class="warning">
<asp:Label ID="loginWarningLabel" runat="server" Text=""></asp:Label>
</div>
</asp:Content>
John was working on the implementation of the family.cs
This was all we did in this team meeting.
Saturday, October 2, 2010
Team Meeting-5
Since I am unable to attend the labs because of a time conflict with one of my classes. So, I have informed this to William and took his permission to skip the labs and compensate for them by working for the amount of time I missed the lab. So, I used to take frequent inputs from my friend Dharmil , so as to know what happened in the lab. In this way at least I have an idea of where the project is.
As usual the lab meeting was held in EPICS lab. I usually attend the team meeting on Fridays because I will be busy on other days. Apart from me John and Dharmil attended the meeting.
The following is the code for the sitemaster page
I have coded the sitemaster page layput as per discussed in the previous lab. We had some good ideas on the lay out of the website. Finally we chose one and then I coded for the chosen layout. After I was done with the coding part, we had a problem with the page.Suppose we want to put some information on the site, the information was getting overlapped with the footer and at time header as well. So we figured out we were missing a "content Place Holder". So we included the content place holder . We also made some necessary changes to the CSS file in the Styles folder. Later we tested it several time to make sure we have the information in the appropriate place.
John worked on the skeleton classes. He wrote the skeleton classed in the App_code folder so that other team members can work on the logic of that. It was a one hour meeting and we have made a decent progress in one hour time.
As usual the lab meeting was held in EPICS lab. I usually attend the team meeting on Fridays because I will be busy on other days. Apart from me John and Dharmil attended the meeting.
The following is the code for the sitemaster page
<div id="menu-box">
<ul id="web">
<li><a href="#">Extra</a></li>
<li><a href="#">Contact</a></li>
<li><a href="#">Single User</a></li>
<li><a href="#">Family</a></li>
<li><a href="#">Calender</a></li>
<li><a class="active" id="first" href="">Home</a></li></ul>
</div>
</div>
<!-- Header end -->
<hr class="noscreen" />
<div id="skip-menu">
</div>
<div class="page">
<div class="col-r">
<div class="col-r-in">
<div class="bodyContent">
<asp:ContentPlaceHolder ID="body" runat="server">
</asp:ContentPlaceHolder>
</div>
</div>
</div>
<div class="cleaner">
</div>
</div>
<!-- Page end -->
<div id="footer">
<ul>
<li><a href="">Home</a>|</li>
<li><a href="#">Calender</a>|</li>
<li><a href="#">Family</a>|</li>
<li><a href="#">Single User</a>|</li>
<li><a href="#">Contact</a>|</li>
<li><a href="#">Extra</a>|</li>
<li><a href="#" onclick="print();" title="Javascript needed for a Print">Print</a></li>
</ul>
I have coded the sitemaster page layput as per discussed in the previous lab. We had some good ideas on the lay out of the website. Finally we chose one and then I coded for the chosen layout. After I was done with the coding part, we had a problem with the page.Suppose we want to put some information on the site, the information was getting overlapped with the footer and at time header as well. So we figured out we were missing a "content Place Holder". So we included the content place holder . We also made some necessary changes to the CSS file in the Styles folder. Later we tested it several time to make sure we have the information in the appropriate place.
John worked on the skeleton classes. He wrote the skeleton classed in the App_code folder so that other team members can work on the logic of that. It was a one hour meeting and we have made a decent progress in one hour time.
Subscribe to:
Posts (Atom)
