hectoronevu / blog

csc 4370 project 2
0 stars 1 forks source link

Status #1

Closed hectoronevu closed 11 years ago

hectoronevu commented 11 years ago

If anyone is uncomfortable with github or coding, let me know. For the presentation, let's try to use this site: prezi.com if anyone has time

For now, everyone create a table in mysql, for example : \ Deleted, see below**

hectoronevu commented 11 years ago

oops, forgot to add passwd varchar(15) as well in the table.

hectoronevu commented 11 years ago

here's my syntax, apparently mysql does not like it if you use any variations of 'index' in your statement: CREATE TABLE main (author VARCHAR (15), title VARCHAR(50), description VARCHAR (100), passwd VARCHAR(15));

hectoronevu commented 11 years ago

uploaded a skeleton of the project, anyone want to take over some of the project requirements?

bmacc commented 11 years ago

yeah. is there a specific part you like me to do? So we don't both work on the something? On Jul 18, 2013, at 4:05 PM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

uploaded a skeleton of the project, anyone want to take over some of the project requirements?

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21210733.

jnesvetailova commented 11 years ago

ok i'll start tonight when i get off work. also i'll take care of making it look prettier


From: bmacc notifications@github.com To: hectoronevu/blog blog@noreply.github.com Sent: Thursday, July 18, 2013 4:35 PM Subject: Re: [blog] Status (#1)

yeah. is there a specific part you like me to do? So we don't both work on the something? On Jul 18, 2013, at 4:05 PM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

uploaded a skeleton of the project, anyone want to take over some of the project requirements?

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21210733. — Reply to this email directly or view it on GitHub.

hectoronevu commented 11 years ago

Just pick one of the requirements and write that you'll work on it so the rest will know.

bmacc commented 11 years ago

Got ya

On Jul 18, 2013, at 19:45, "hectoronevu" notifications@github.com<mailto:notifications@github.com> wrote:

Just pick one of the requirements and write that you'll work on it so the rest will know.

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21223050.

hectoronevu commented 11 years ago

Okay guys, I'm going to post a major update functionality wise:

  1. If you are logged in, you can view the other blogs from the main page
  2. Once logged in, you can post to your blog and see previous postings.
  3. I moved the log in and register forms to their own pages so the home page won't be cluttered.
  4. I moved some links around for better navigation.
  5. The home page layout looks a little different
  6. some other crap i may have forgotten

CREATE TABLE posts (blogID INT, postID INT NOT NULL AUTO_INCREMENT PRIMARY KEY, title VARCHAR(50), content TEXT, date DATETIME);

CREATE TABLE comments (postID INT, commentID INT NOT NULL AUTO_INCREMENT PRIMARY KEY, author VARCHAR(50), content TEXT, date DATETIME);

bmacc commented 11 years ago

Dang it. I did some major changes myself. On Jul 21, 2013, at 12:16 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

Okay guys, I'm going to post a major update functionality wise:

  1. If you are logged in, you can view the other blogs from the main page
  2. Once logged in, you can post to your blog and see previous postings.
  3. I moved the log in and register forms to their own pages so the home page won't be cluttered.
  4. I moved some links around for better navigation.
  5. The home page layout looks a little different
  6. some other crap i may have forgotten

CREATE TABLE posts (blogID INT, postID INT NOT NULL AUTO_INCREMENT PRIMARY KEY, title VARCHAR(50), content TEXT, date DATETIME);

CREATE TABLE comments (postID INT, commentID INT NOT NULL AUTO_INCREMENT PRIMARY KEY, author VARCHAR(50), content TEXT, date DATETIME);

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21304898.

hectoronevu commented 11 years ago

Who volunteers to go on prezi.com and create a presentation there?

hectoronevu commented 11 years ago

If you make some changes and are satisfied with what you have, you can create a new branch in blog and post your code there for the rest of us to see without modifying any in the master branch.

jnesvetailova commented 11 years ago

I'll take care of the presentation and ill work on the layout more tomorrow. I'm going to try to get some code finished as well sorry I've been having a hard time making it work

On Jul 21, 2013, at 0:31, hectoronevu notifications@github.com wrote:

Who volunteers to go on prezi.com and create a presentation there?

— Reply to this email directly or view it on GitHub.

hectoronevu commented 11 years ago

No problems, just update us on your progress, be sure to include a link to the presentation (there should be a share button). I too, have a hard time making anything work, here's to hoping this will be ready for Monday. Also, I would like us to present your project first, is that alright with you guys?

bmacc commented 11 years ago

Thats fine. I sent some code to your gmail. Check it out, let know what, if any of it, can be incorporated in the main code. On Jul 21, 2013, at 12:55 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

No problems, just update us on your progress, be sure to include a link to the presentation (there should be a share button). I too, have a hard time making anything work, here's to hoping this will be ready for Monday. Also, I would like us to present your project first, is that alright with you guys?

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21305176.

hectoronevu commented 11 years ago

I like the layout you did Brian. I'll try to incorporate it before signing off for the night.

bmacc commented 11 years ago

index.php done. On Jul 21, 2013, at 1:01 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

I like the layout you did Brian. I'll try to incorporate it before signing off for the night.

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21305205.

hectoronevu commented 11 years ago

Looks good Brian, I'm stuck on this one bug in comments.php =(

bmacc commented 11 years ago

tell me the bug. I'll help. Sometime you just need a different sit of eyes. On Jul 21, 2013, at 5:34 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

Looks good Brian, I'm stuck on this one bug in comments.php =(

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21307510.

hectoronevu commented 11 years ago

my $postID is not working correctly when I use it:

  1. (example in members.php line 28) When I need to comment, I call comment.php?postID=X, where X is the postID
  2. (example in comments.php line 35) In comments.php, I grab the postID by doing $_GET[postID] but it's giving me notices and showing all the comments instead of the comments sharing postID.

I was able to do this with blogID in index.php line 53 and grabbing blogID in pages.php line 21.

bmacc commented 11 years ago

Ok. I'm gonna close my eyes for a little bit. If you figure it out, let me know so I can work on something else. On Jul 21, 2013, at 5:48 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

my $postID is not working correctly when I use it:

  1. (example in members.php line 28) When I need to comment, I call comment.php?postID=X, where X is the postID
  2. (example in comments.php line 35) In comments.php, I grab the postID by doing $_GET[postID] but it's giving me notices and showing all the comments instead of the comments sharing postID.

I was able to do this with blogID in index.php line 53 and grabbing blogID in pages.php line 21.

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21307637.

bmacc commented 11 years ago

Save this image to the location where your project_2 files are being stored on your codd.[cid:9C3C95A5-92AC-42F6-8D44-7AFB9FDC98A5@hsd1.ga.comcast.net.] On Jul 21, 2013, at 5:57 AM, Brian DaCosta bdacosta1@student.gsu.edu<mailto:bdacosta1@student.gsu.edu> wrote:

Ok. I'm gonna close my eyes for a little bit. If you figure it out, let me know so I can work on something else. On Jul 21, 2013, at 5:48 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

my $postID is not working correctly when I use it:

  1. (example in members.php line 28) When I need to comment, I call comment.php?postID=X, where X is the postID
  2. (example in comments.php line 35) In comments.php, I grab the postID by doing $_GET[postID] but it's giving me notices and showing all the comments instead of the comments sharing postID.

I was able to do this with blogID in index.php line 53 and grabbing blogID in pages.php line 21.

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21307637.

hectoronevu commented 11 years ago

can you attach it in an email, I can't open it from the email link.

bmacc commented 11 years ago

it was attach. I'll send to your gmail On Jul 21, 2013, at 11:07 AM, Brian DaCosta bdacosta1@student.gsu.edu<mailto:bdacosta1@student.gsu.edu> wrote:

Save this image to the location where your project_2 files are being stored on your codd. On Jul 21, 2013, at 5:57 AM, Brian DaCosta bdacosta1@student.gsu.edu<mailto:bdacosta1@student.gsu.edu> wrote:

Ok. I'm gonna close my eyes for a little bit. If you figure it out, let me know so I can work on something else. On Jul 21, 2013, at 5:48 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

my $postID is not working correctly when I use it:

  1. (example in members.php line 28) When I need to comment, I call comment.php?postID=X, where X is the postID
  2. (example in comments.php line 35) In comments.php, I grab the postID by doing $_GET[postID] but it's giving me notices and showing all the comments instead of the comments sharing postID.

I was able to do this with blogID in index.php line 53 and grabbing blogID in pages.php line 21.

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21307637.

hectoronevu commented 11 years ago

thanks, you already sent me that pic in your previous email though.

Digressing, is there suppose to be another set of horizontal and vertical scroll bars wrapped around the blog entries?

bmacc commented 11 years ago

got ya. I wasn't sure if you stored it. Which page are you referencing? On Jul 21, 2013, at 11:53 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

thanks, you already sent me that pic in your previous email though.

Digressing, is there suppose to be another set of horizontal and vertical scroll bars wrapped around the blog entries?

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21312097.

hectoronevu commented 11 years ago

index.php

bmacc commented 11 years ago

yes, thats what I was going for. Since it would mess with the body background image. I created a specific div size, and set overflow to scroll, thinking that once the box is filled, you would be able to scroll. I never actually tested it though. By the way, I'm currently styling comments.php, so don't change too much. If you want I can post what I got so far if you need to mess around with that file. On Jul 21, 2013, at 11:34 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

can you attach it in an email, I can't open it from the email link.

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21311824.

hectoronevu commented 11 years ago

I will be working on showing the number of comments for each post, so I imagine pages.php, members.php, and comments.php will be changed if I get that feature working.

hectoronevu commented 11 years ago

We have two issues regarding functionality left that I see:

  1. Posts and comments have to be in order where the newest are on top, not the bottom as it is now.
  2. If a user is signed on, he should be able to delete his comments and posts.
bmacc commented 11 years ago

Ok, I made some changed to the comments.php, commentsII.php, and style.css. I also created a new file, commentsIV.php. The posting of comments somewhat works now. And I believe the last issue is not with the style sheet. Check it out for me. Form text can be selected now, but when comments are posted they appear to the left(outside of my div), and if you refresh then they appear in the correct location (inside my div). I believe this is where your expertise comes in. On Jul 22, 2013, at 4:09 AM, hectoronevu notifications@github.com<mailto:notifications@github.com> wrote:

We have two issues regarding functionality left that I see:

  1. Posts and comments have to be in order where the newest are on top, not the bottom as it is now.
  2. If a user is signed on, he should be able to delete his comments and posts.

— Reply to this email directly or view it on GitHubhttps://github.com/hectoronevu/blog/issues/1#issuecomment-21329953.

hectoronevu commented 11 years ago

okay, everything looks fine except in comments.php, I have to move the $postID block before including commentsII.php otherwise it would give out notices. I'm gonna take a 30min nap now and see you guys in school. Not sure if the two features left would be done in time, but I'll continue to work on them once I'm on campus.

hectoronevu commented 11 years ago

List of bugs and things to do:

  1. Need to have edit and delete button for each post and comment.
  2. when posting or commenting, page does not refresh itself/show the newest comment, have to manually refresh.
  3. timestamp bug on older posts.
  4. Some pages need to be designed, such as pages.php and members.php