Author Archives: Mengyun

About Mengyun

A 3rd-year Computer Science Student.

Screencasts for 2011 Spring

Crystal Lok Koo

Kahlil Amlani

Mark Striemer

Mengyun Kong

Steve Sutcliffe

Teresa Hume

Advertisements

Status Report – Mar 13

Mark

Status

* Added some finishing touches to the floating banners
* Started trying to implement OAuth

Next Steps

* Hopefully get the floating banners shipped out!
* Continue to work on OAuth

Roadblocks

* None this week

Steve

status

-fixed memory leak problem
-lots of testing
-created diffs
-uploaded code for review

next steps

-correct code that has been reviewed
-continue to create diffs

roadblocks

-just waiting for code to be reviewed

Crystal

Status

– Fixed up a few bugs through testing
– Cleaned up my code and adding comments
– Not sure how to do the documentation for my web api resource
– Couldn’t fix this one bug

Next Steps

– Fix this one bug (will ask during meeting)
– Document my resource
– Talk to mentor for a new project and start working on it (so excited!)

Road Blocks

– Felt ill this week

Teresa

Status

– still working on the templates
– was able to successfully add new content using an extension

Next Steps

– write up the documentation
– finish with the templates (not sure how far to break them down – could go very fine grained)

Roadblocks

– nothing really

Mengyun

Status

– work with dictionary api
– learn about js,jquery and ajax and .js with rb
– write js with my api

Next steps

– continue with js
– implement api’s update

Road Blocks

– write $(“.someclass”).action(), but it doesn’t select all that class.

Kahlil

Status

– Implemented non-unique element changes to JSON part of the models.

– Started working on screenshots XML, made good progress

– Researched on how to get code snippets into an XML format

– Worked out the XML hierarchy for code snippets

Next Steps

– Fix road blocks dealing with code snippets

– Complete xml for screenshots

Road Blocks

– Don’t know how to get all the parameters I need for code snippets

Meeting Minutes – Mar.6

  • Kamlani got the XML stuff to work. Christian gave him some guidance on JSON
  • Teresal fixed the loader had a good start into breaking up the templates, getting close to finishing
  • Steve solved some questions with his project with the help of Christian
  • Mike and Christian helped Menyun with webAPI problems confusing her
  • Crystal and Mark were not at the meeting
  • E-mail may be a better way than IRC to get Christian in the next few days.

A tiny performance test on Spell Error Highlight

– First, I edited the diffutils.py, using log_timed wrapping highlight functions at line 599 and 600 to help log the time cost.

– Then, created a new review request on my local reviewboard, with a large diff generated from “git diff –full-index release-1.5.2 reviewboard/webapi/tests.py >test.diff” (The diff contains 434 changes and more than 4000 lines and quite a lot strings and comments)

– went to the diff page of that request after restart local server and got log of time like this: pastie.org/1588416

– The time costs are: 1) Fetching: 3.739708 seconds; 2) Patching: 0.36519s; 3) Highlight: 2.814533s; 4) Generating diff chunks: 2.34845s

– For this diff, when not using the filter for spell errors, pastie.org/1590548

the time costs are : 1)Fetching: 1.310890 seconds; 2) Patching: 0.27146s; 3) Highlight: 1.431874s; 4) Generating diff chunks: 2.231105s

 

– tried another diff of reviewboard/webapi/resources.py, contains 176 changes, near 5000 lines and quite a lot strings and comments

– log of time like this: pastie.org/1588433

– The time costs are: 1) Fetching: 3.641606 seconds; 2) Patching: 0.19239s; 3) Highlight: 2.627750s; 4) Generating diff chunks: 0.267105s

– For this diff, when not using the filter for spell errors, pastie.org/1590563

the time costs are : 1)Fetching: 1.351361 seconds; 2) Patching: 0.37602s; 3) Highlight: 1.203272s; 4) Generating diff chunks: 0.263907s

 

Status Report – Jan 30, 2011

Teresa Hume

Status

  • Working on Themes UI – built a simple Themes tab with a bunch of CharFields for editable options
  • Figuring out django & python by building a mini-website

Next Steps:

  • Keep getting the hang of django & python
  • Build a custom form that is more appropriate for color-selection (will want an actual color-picker and have it link to the corresponding CharField) -> Label ColorSelector TextField RestoreDefaultButton
  • Build a colorSelector (seen some in .js, but not sure how to link javascript components into django yet)
  • Figure out how to actually implement the themes change (likely using stylesheets)

Roadblocks:

  • Having some trouble posting a review this morning, I believe it is because I pushed to my github fork before post-review?
  • Issue 1632… there doesn’t seem to be a clean way to fix this (or at least not one that I can see)
  • Other classes (Assignments and Midterms are starting to close in…)

Steve Sutcliffe

Status

  • prepared & presented a presentation about Review Board to staff & students at the U
  • read up on Python
  • finally figured out what Django is doing with the base/label commands and python’s role in all that
  • (discovered that noargs in Django doesn’t mean noargs!)
  • initial prototype for the Django Management Command prompt

Next steps

  • Continue to learn python & django a bit more
  • Finalize the prototype for the fill-db command

Roadblocks

  • The cross-over between django & python in the Django management command is very grey, it seems to incorporate some python-related features will be very tricky, haven’t had much luck so far.
  • Documentation on django management command is not that great
  • Need some guidance from a python-django pro in adding ParseCommand arguments to Django’s seemingly limited implementation of the option_list

Kahlil

Status

  • Completed set up of my environment for extensions
  • Fixed a bug in extension code and submitted it for review (was then accepted)
  • Fixed up some documentation in hooks.py for extensions, submitted this for review
  • Started learning extension code, and was able to add a button in the Review area in my local environment.
  • Started to learn more about Python

Next Steps

  • Continue to learn about Python and get some more direction about my extension
  • Learn about the Python and XML framework
  • Learn about how to retrieve the review board dif details
  • My plan for developing the XMLExport extension, is to first understand how XML works and then start to look into how I can apply it to what the Review Board framework offers. As far as a timeline, I don’t really have enough information to put a firm date on when I will complete the task.

Roadblocks

  • Need some help in learning about the review board framework

Crystal

Status:

  • Working on Quick Search Feature, researching through how it’s going to work, what is needed
  • Continuing working with the mentors to figure out the best way to do this

Next steps

  • Reading lots on REST API
  • Getting familiar WEBAPI Resource that ReviewBoard has
  • Figure out how to implement this and where to start
  • Deciding what exactly to search for ex: user name, IDs, review request titles, descriptions etc…

Roadblocks

  • Lost last weekend to Edmonton and being very ill while I was there. After returning to Vancouver, spent 2 days sick in bed. I’m feeling much better but I had to use the last couple of days to get through the backlog of homework and catching up while I was sick. I should be back in order by Sunday.

Mengyun

Status

  • continue learning python & django
  • have a quick of look on documents on pygments
  • look into spell checking (articles and implements)
  • try to have a general idea on javascript
  • have a draft plan for semester

Next steps

  • make the plan reasonable (what need to do and the timelines)
  • start to work on the first task (possibly will be a simple spell check)
  • need more knowledge on djbelts/django/python and Reviewboard itself

Roadblocks

  • lack of knowledge on codebase of rb
  • time management for 5 courses as well as rb..(already drop 1..so 4+RB now)

Mark

Status

  • Looked into the post-commit UI.
  • I’m planning on talking to ChipX86 today to see what I will actually be working on because the post-commit UI may not work out with just me now.

Next steps

  • I will be talking to ChipX86 today before I keep working on my project.

Roadblocks

  • Finding a project to actually get done is tough!

Code Sprint Day 2

What’s going on
  • Post my first review! It’s for Issue1571
  • Note for memorizing: 0) (pull from master) make changes; 1) git commit for the issue; 2) git push to the branch on my fork; 3) post-review it; 4) edit it on web
  • In Issue1571: 1) adjust the table to fit the screen; 2) resize the fileinput widgets in forms.py; 3) fail to control the fileinput to fit the screen; 4) resize it to be fine under 800×600 under firefox; *)  it works well under chrome. Need to be tested with IE and Safari.
  • interested in  spell checking and got nice guidance from ChipX86

Next

  • Edit the description for review of issue 1571
  • Do some initial research in spell checking and set some reasonable milestones for the next months

 

My Status on Jan 21,2011

What I’ve done

  • Got the idea of reviewboard. Set it up locally and went through some crash when adding a repository.
  • learnt how the urls.py works and the regular expressions as well as read about MVC (MTV) and templatetags in django.
  • Tried to reproduce the problem on Issue 1632 but failed to on demo.reviewboard.org (1.6 alpha 0 dev)
  • Continued to solve Issue 1571 (still keep trying).

What I’ve tried on Issue 1571:

  • edit reviews.css with the width of the object but the “choose file” filename still is getting short.
  • suspect it is what django does. so track to the forms.py but not sure to how to edit the feature there.

Plan

  • try to do more and learn more on Issue 1571
  • know more about how the whole project’s goal and plan
  • have a direction where I’m going to dive into