Archive for the ‘Dev Hours’ Category

« Older Entries

Finally, a proper kde 4.2

Wednesday, March 11th, 2009


Originally uploaded by Framed Geek

Bosen dengan Gosonx yang ngobrolin Gnome? :p Ya, mari kita ramaikan lagi dunia dengan KDE 4.2 yang totally shiny. Precioussss

You see, plasmoid bisa dibuat dengan Python, Ruby dan Javascript. UI building memang belum friendly. Antara memang widget-nya belum komplit atau saya yang kurang akrab dengan API Plasma. Buktinya plasmoid RSSNow bisa tampil cantik.

Oke sonx, kutunggu du.. eh, skrinsutmu ..

Tags: , ,
Posted in Dev Hours | 1 Comment »

Morning Coffee: Prioritise Your Reading List

Tuesday, February 3rd, 2009

Ever feeling overloaded with informations? Techmeme, engadget, mashable, readwriteweb, etc. Which one to read first?

Let’s welcome MorningCoffee! MorningCoffee is your great assistant, giving you priorites which information to digest first. Given a list of feed URLs, MorningCoffee will come up with a scored reading list. The top most is the one generate the most buzz.

For this prototype MorningCoffee uses FriendFeed visibility scoring. Item which appears more in FriendFeed will have higher score. An item may appear in FriendFeed when people share it from Google Reader, delicious, and others.

This scoring is pretty simple at the moment. But it will likely be updated to cater comments, likes, and hides in FriendFeed.

UI is rather too dull. A proper title and hiding the URL may be the closest milestone. Paging will follow soon.

Tags: ,
Posted in Dev Hours | No Comments »

Four Tips on Designing SOLR Schema

Wednesday, August 20th, 2008

However similar SOLR to a database, designing schema for each of them has a distinct difference.

  • SOLR is optimized to search purpose, on the other hand, database was commonly design to store (related) data
  • SOLR has a custom behaviour when storing and querying data, ie: indexing behaviour and query behaviour.

So how is it to design schema in SOLR?

  1. Cover all basic data. Make sure to index everything you need to search onto. Indexing more data won’t hurt, storage is cheap.
  2. Cover common search behaviour. Do you search over several fields? Dismax query type sometime does fit your need as it is searching word by word. Store in one field or multifield? Or both? SOLR has copyField feature.You can use it for store concatenated values.
  3. Work on the relevancy and scoring. Setup proper score boosting to your search query. You may found a necessity to ignore score or to use FunctionQuery to tweak scoring or filling a “formula” field, ie: linear, product, sum, etc.
  4. Practise make perfect. Gather feedback from your users, check what search is work and what is not.

FAQ (to be answered soon):

  • Why SOLR, is database not enough?
  • Would it be fair to compare database to Lucene?

Photo by estherase

Tags: , , ,
Posted in Dev Hours, One Post Per Day | No Comments »

« Older Entries