search

mqchau / EECS22L_Project2

GNU General Public License v3.0
0 stars 0 forks source link

Software manual #1

Closed ghost closed 10 years ago

ghost commented 10 years ago

This thread for software manual.

mqchau commented 10 years ago

Ping new people added.

mqchau commented 10 years ago

Ryan, could you try to have a simple layout to put in the Software manual like last time? Buttons don't need to do anything. We'll just put an image on left side and a text box on right side. On top there is a menu with 4 button to choose from:

http://zetcode.com/tutorials/gtktutorial/menusandtoolbars/

Quan.

On Tue, Feb 11, 2014 at 3:08 PM, ericr2 notifications@github.com wrote:

This thread for software manual.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1 .

mqchau commented 10 years ago

A new place to put our Software Manual documents:

https://drive.google.com/a/uci.edu/#folders/0B6hFDKbQXelUODFPcVFGNnE5RGM

Eric, last time we did it by this way: each member writes a part and keep on posting it to this common drive. Each post will get a higher version number.

Quan.

jamiesl commented 10 years ago

Hi all,

I just uploaded v1 of the UserManual into the Google Drive. Please update the usage scenarios and also the back matter. The installation and whatnot part was essentially pasted over from the user manual of the first project.

Thanks, Jamie

mqchau commented 10 years ago

Got v2. Still pending:

Please review the document.

hanchelc commented 10 years ago

Could I ask why we have this following protocol for line detection?

This assumes the image uses constant line spacing or at least consistent font. Are we guaranteed that?

hanchelc commented 10 years ago

Also, I uploaded v3 with the only change being my name spelled correctly. COME ONE, GUYS, "CHENG" WITH AN "E." k thanks. :)

mqchau commented 10 years ago

Line detection is to help you with splitting characters. This is what I learned from Tesseract OCR apps. That app can detect lines like that by themselves but i think we can take that input from user to simplify our program. If we have time we can try to detect lines by ourselves. Lines should be in constant spacing. Just keep in mind there may be empty lines. Consistent font should be OK too. These are codes, not presentations or Word documents.

On Sun, Feb 16, 2014 at 1:22 PM, hanchelc notifications@github.com wrote:

Also, I uploaded v3 with the only change being my name spelled correctly. COME ONE, GUYS, "CHENG" WITH AN "E." k thanks. :)

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35213015 .

hanchelc commented 10 years ago

ahh Okay good. I remember Yasaman's example had one of Doemer's power point slides with a Title in a much larger font and the rest of the text in smaller and the OCR was able to recognize all of it. If it's consistent font, this should be easy. Cool! :D

hanchelc commented 10 years ago

If font size is consistent, then it shouldn't be necessary to ask the user for the 2nd line. Once we find the height of one line, my part can just go down in those increments to the next line with text, right?

mqchau commented 10 years ago

Because we also need to know the spacing between two lines. In the beginning we'll take that input from users, maybe if we can calculate that by ourselves then we can skip that question.

On Sun, Feb 16, 2014 at 1:43 PM, hanchelc notifications@github.com wrote:

If font size is consistent, then it shouldn't be necessary to ask the user for the 2nd line. Once we find the height of one line, my part can just go down in those increments to the next line with text, right?

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35214954 .

hanchelc commented 10 years ago

The spacing should be some multiple (i.e. 1, 1.5, 2, etc) of the line width. I think I can first check single spacing and find the next line down and call Eric's character recognition to ensure that I'm on an actual line, and if I detect some black but do not recognize it as a character (in the case of 1.5 spacing), then I'll change it to 1.5, 2.5, whatever.

rmorrison23 commented 10 years ago

I got the menu bar working and I added in the two-pane view with a sample image in one pane and text in another with Visio. I just need to add actual description of the functionality and I'm done. I'm saying bye to my girlfriend who was visiting, so I'll have it up in a few hours.

Sent from my iPhone

On Feb 16, 2014, at 12:40 PM, mqchau notifications@github.com wrote:

Got v2. Still pending:

Some screenshot of the program: Ryan, could you give us at least 1 screen shot, please? Please review the document.

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

mqchau commented 10 years ago

If you think so you can change that description in the User Manual.

On Sun, Feb 16, 2014 at 1:53 PM, hanchelc notifications@github.com wrote:

The spacing should be some multiple (i.e. 1, 1.5, 2, etc) of the line width. I think I can first check single spacing and find the next line down and call Eric's character recognition to ensure that I'm on an actual line, and if I detect some black but do not recognize it as a character (in the case of 1.5 spacing), then I'll change it to 1.5, 2.5, whatever.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35216812 .

mqchau commented 10 years ago

Thanks Ryan, Please put these as the menu bar:

On the main screen we only need on left side the image and on right side the Text edit area.

Quan.

On Sun, Feb 16, 2014 at 2:00 PM, Quan Quoc Minh Chau mqchau@uci.edu wrote:

If you think so you can change that description in the User Manual.

On Sun, Feb 16, 2014 at 1:53 PM, hanchelc notifications@github.comwrote:

The spacing should be some multiple (i.e. 1, 1.5, 2, etc) of the line width. I think I can first check single spacing and find the next line down and call Eric's character recognition to ensure that I'm on an actual line, and if I detect some black but do not recognize it as a character (in the case of 1.5 spacing), then I'll change it to 1.5, 2.5, whatever.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35216812 .

rmorrison23 commented 10 years ago

Quick question: isn’t stain and wrinkle removal performed in one action rather than two separate ones?

On Feb 16, 2014, at 2:09 PM, mqchau notifications@github.com wrote:

Thanks Ryan, Please put these as the menu bar:

  • File:
  • Open image file
  • Save text file
  • Exit program
  • Preprocessing:
  • Wrinkle removal
  • Stain removal
  • Black white conversion
  • Line boundaries setup
  • Rotation
  • OCR:
  • Perform OCR
  • Post processing:
  • Dictionary settings

On the main screen we only need on left side the image and on right side the Text edit area.

Quan.

On Sun, Feb 16, 2014 at 2:00 PM, Quan Quoc Minh Chau mqchau@uci.edu wrote:

If you think so you can change that description in the User Manual.

On Sun, Feb 16, 2014 at 1:53 PM, hanchelc notifications@github.comwrote:

The spacing should be some multiple (i.e. 1, 1.5, 2, etc) of the line width. I think I can first check single spacing and find the next line down and call Eric's character recognition to ensure that I'm on an actual line, and if I detect some black but do not recognize it as a character (in the case of 1.5 spacing), then I'll change it to 1.5, 2.5, whatever.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35216812 .

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

duongkt commented 10 years ago

no. Some paper might have stains and no wrinkle some might have both, some might have wrinkle only.

On Sun, Feb 16, 2014 at 2:50 PM, rmorrison23 notifications@github.comwrote:

Quick question: isn't stain and wrinkle removal performed in one action rather than two separate ones?

On Feb 16, 2014, at 2:09 PM, mqchau notifications@github.com wrote:

Thanks Ryan, Please put these as the menu bar:

  • File:
  • Open image file
  • Save text file
  • Exit program
  • Preprocessing:
  • Wrinkle removal
  • Stain removal
  • Black white conversion
  • Line boundaries setup
  • Rotation
  • OCR:
  • Perform OCR
  • Post processing:
  • Dictionary settings

On the main screen we only need on left side the image and on right side the Text edit area.

Quan.

On Sun, Feb 16, 2014 at 2:00 PM, Quan Quoc Minh Chau mqchau@uci.edu wrote:

If you think so you can change that description in the User Manual.

On Sun, Feb 16, 2014 at 1:53 PM, hanchelc notifications@github.comwrote:

The spacing should be some multiple (i.e. 1, 1.5, 2, etc) of the line width. I think I can first check single spacing and find the next line down and call Eric's character recognition to ensure that I'm on an actual line, and if I detect some black but do not recognize it as a character (in the case of 1.5 spacing), then I'll change it to 1.5, 2.5, whatever.

Reply to this email directly or view it on GitHub< https://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35216812>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35218966 .

ghost commented 10 years ago

Sorry I've been kind of out of the loop. Anyone doing the index? I could take care of that if no one is on it.

mqchau commented 10 years ago

Index is done. You can add more if you want. Current version is v5. I modified some minor points. The doc looks in good shape now. Quan.

On Sun, Feb 16, 2014 at 6:49 PM, ericr2 notifications@github.com wrote:

Sorry I've been kind of out of the loop. Anyone doing the index? I could take care of that if no one is on it.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35225105 .

mqchau commented 10 years ago

Ryan, just a side question: Did you write the GTK code for this display? If that is the case, you've done around 40% of your job this week.

On Sun, Feb 16, 2014 at 6:52 PM, Quan Quoc Minh Chau mqchau@uci.edu wrote:

Index is done. You can add more if you want. Current version is v5. I modified some minor points. The doc looks in good shape now. Quan.

On Sun, Feb 16, 2014 at 6:49 PM, ericr2 notifications@github.com wrote:

Sorry I've been kind of out of the loop. Anyone doing the index? I could take care of that if no one is on it.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35225105 .

rmorrison23 commented 10 years ago

I wrote the code just for the menu bar options. The image and text panes I added with Visio. I'm going to work on getting the actual image and text panes tonight and tomorrow.

Sent from my iPhone

On Feb 16, 2014, at 6:56 PM, mqchau notifications@github.com wrote:

Ryan, just a side question: Did you write the GTK code for this display? If that is the case, you've done around 40% of your job this week.

On Sun, Feb 16, 2014 at 6:52 PM, Quan Quoc Minh Chau mqchau@uci.edu wrote:

Index is done. You can add more if you want. Current version is v5. I modified some minor points. The doc looks in good shape now. Quan.

On Sun, Feb 16, 2014 at 6:49 PM, ericr2 notifications@github.com wrote:

Sorry I've been kind of out of the loop. Anyone doing the index? I could take care of that if no one is on it.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35225105 .

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

mqchau commented 10 years ago

For the text, you can assume that we give you a char , and for image, we give you an Image Quan.

On Sun, Feb 16, 2014 at 7:23 PM, rmorrison23 notifications@github.comwrote:

I wrote the code just for the menu bar options. The image and text panes I added with Visio. I'm going to work on getting the actual image and text panes tonight and tomorrow.

Sent from my iPhone

On Feb 16, 2014, at 6:56 PM, mqchau notifications@github.com wrote:

Ryan, just a side question: Did you write the GTK code for this display? If that is the case, you've done around 40% of your job this week.

On Sun, Feb 16, 2014 at 6:52 PM, Quan Quoc Minh Chau mqchau@uci.edu wrote:

Index is done. You can add more if you want. Current version is v5. I modified some minor points. The doc looks in good shape now. Quan.

On Sun, Feb 16, 2014 at 6:49 PM, ericr2 notifications@github.com wrote:

Sorry I've been kind of out of the loop. Anyone doing the index? I could take care of that if no one is on it.

Reply to this email directly or view it on GitHub< https://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35225105>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35226163 .

mqchau commented 10 years ago

Hanchel, I think the User Manual is ready. You can submit it tomorrow morning. Quan.

On Sun, Feb 16, 2014 at 10:54 PM, Quan Quoc Minh Chau mqchau@uci.eduwrote:

For the text, you can assume that we give you a char , and for image, we give you an Image Quan.

On Sun, Feb 16, 2014 at 7:23 PM, rmorrison23 notifications@github.comwrote:

I wrote the code just for the menu bar options. The image and text panes I added with Visio. I'm going to work on getting the actual image and text panes tonight and tomorrow.

Sent from my iPhone

On Feb 16, 2014, at 6:56 PM, mqchau notifications@github.com wrote:

Ryan, just a side question: Did you write the GTK code for this display? If that is the case, you've done around 40% of your job this week.

On Sun, Feb 16, 2014 at 6:52 PM, Quan Quoc Minh Chau mqchau@uci.edu wrote:

Index is done. You can add more if you want. Current version is v5. I modified some minor points. The doc looks in good shape now. Quan.

On Sun, Feb 16, 2014 at 6:49 PM, ericr2 notifications@github.com wrote:

Sorry I've been kind of out of the loop. Anyone doing the index? I could take care of that if no one is on it.

Reply to this email directly or view it on GitHub< https://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35225105>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35226163 .

mqchau commented 10 years ago

Hey guys, does anybody knows our team account password?

On Sun, Feb 16, 2014 at 11:06 PM, Quan Quoc Minh Chau mqchau@uci.eduwrote:

Hanchel, I think the User Manual is ready. You can submit it tomorrow morning. Quan.

On Sun, Feb 16, 2014 at 10:54 PM, Quan Quoc Minh Chau mqchau@uci.eduwrote:

For the text, you can assume that we give you a char , and for image, we give you an Image Quan.

On Sun, Feb 16, 2014 at 7:23 PM, rmorrison23 notifications@github.comwrote:

I wrote the code just for the menu bar options. The image and text panes I added with Visio. I'm going to work on getting the actual image and text panes tonight and tomorrow.

Sent from my iPhone

On Feb 16, 2014, at 6:56 PM, mqchau notifications@github.com wrote:

Ryan, just a side question: Did you write the GTK code for this display? If that is the case, you've done around 40% of your job this week.

On Sun, Feb 16, 2014 at 6:52 PM, Quan Quoc Minh Chau mqchau@uci.edu wrote:

Index is done. You can add more if you want. Current version is v5. I modified some minor points. The doc looks in good shape now. Quan.

On Sun, Feb 16, 2014 at 6:49 PM, ericr2 notifications@github.com wrote:

Sorry I've been kind of out of the loop. Anyone doing the index? I could take care of that if no one is on it.

Reply to this email directly or view it on GitHub< https://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35225105>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35226163 .

hanchelc commented 10 years ago

I can submit it but I don't know our team's account password

mqchau commented 10 years ago

Yeah I figured out that nobody knows so I emailed them the manual already.

On Mon, Feb 17, 2014 at 11:34 AM, hanchelc notifications@github.com wrote:

I can submit it but I don't know our team's account password

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35315563 .

hanchelc commented 10 years ago

Yasaman and CheWei will accept it via email? I hope so..

mqchau commented 10 years ago

And also via my personal account on crystalcove.

On Mon, Feb 17, 2014 at 11:41 AM, hanchelc notifications@github.com wrote:

Yasaman and CheWei will accept it via email? I hope so..

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35316149 .

mqchau commented 10 years ago

Alright, they got our submission. No worry about that. Our account is: username: team3 password: 3isacharm

On Mon, Feb 17, 2014 at 11:45 AM, Quan Quoc Minh Chau mqchau@uci.eduwrote:

And also via my personal account on crystalcove.

On Mon, Feb 17, 2014 at 11:41 AM, hanchelc notifications@github.comwrote:

Yasaman and CheWei will accept it via email? I hope so..

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35316149 .

hanchelc commented 10 years ago

Great!

duongkt commented 10 years ago

weird password...

On Mon, Feb 17, 2014 at 12:01 PM, hanchelc notifications@github.com wrote:

Great!

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35317813 .

mqchau commented 10 years ago

I set it up that way.

On Mon, Feb 17, 2014 at 2:41 PM, duongkt notifications@github.com wrote:

weird password...

On Mon, Feb 17, 2014 at 12:01 PM, hanchelc notifications@github.com wrote:

Great!

Reply to this email directly or view it on GitHub< https://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35317813>

.

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35329827 .

ghost commented 10 years ago

So no lecture today, I think. Are we meeting up at 1? or now? or when?

mqchau commented 10 years ago

at 2pm

On Tue, Feb 18, 2014 at 11:19 AM, ericr2 notifications@github.com wrote:

So no lecture today, I think. Are we meeting up at 1? or now? or when?

Reply to this email directly or view it on GitHubhttps://github.com/mqchau/EECS22L_Project2/issues/1#issuecomment-35421948 .