ulink weekly report - week 7

Events happening in the community are now at Drupal community events on www.drupal.org.
garthee's picture

I have been little busy with applying for industrial training which is required by my degree. However amidst the work I was able to do the following the last week and I would like to make this report as short as possible to save some time. 

What I did in the last week

  1. Extended local caching to support ksearch, so that user can get quicker responses for already searched words
  2. Designed and implemented a server side caching for all the searches that are selected and used by
    the user. For example, if the user searches for “php settings” and got node/11, node/22, node/30 as results and selected node/11 for the link, and chose to remember the results by checking the option, it will be stored in a separate table. When the user requests for “php settings” this will be returned first. Hence user always get the most frequently used option first.
  3. Also I modified and improved few javascript code lines.
  4. Further I added inline api comments for uauto.module and ulink.module to help the developers interested in extending the function through hooks.

What I m going to do next

  1. Writing an illegible and simple but complete description about the project and how to use guide.
  2. Adding readme file for all four modules involved
  3. Adding some demo for the project in testing site.

What Drupal community could do?

  1. They can comment on or suggest how I could improve the cache (local and server side) implementation
  2. Then can comment on or suggest how I could improve the UI, including the aesthetic aspects of it
  3. Then can comment on or suggest on the complete project by start using them and trying every possible options (including the very detailed configurations ulink and uauto provide)

SoC 2007

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week