Re: [LogiLogi-list] User-interface starting to take shape

> This is the last project I've been working on, is not finished yet.
> 2flowers.com The project desing, UI and some other things are made by
> me, and the programing including all Javascript, PHP and so AJAX is
> made by my team partner Miguel (I'll tell him to join the list and
> introduce himself).

Will be great to welcome him here too!

> I'll download later today the files from the SVN at SF.net and take a
> look. Ruby should be no problem to understand, but I'll appreciate any
> guidance.

~ Ruby ~

Ruby is not difficult to read, for reading it, the main thing to get 
used to, are all the somearray.each do |element| end constructions. 
A good concise crash-course in ruby is:
http://ruby.brian-schroeder.de/course/slides.pdf

~ Getting Manta up and running ~

If you are on Linux it's a matter of installing ruby gems, and with gem: 
rails, and tzinfo, rubyzip, RedCloth and diff/lcs.

You'll also need mysql running. If you're on Debian or Ubuntu, besides 
ruby you'll need libzlib-ruby, libyaml-ruby and rdoc before downloading
and installing the ruby gems program.

gem install rails --include-dependencies

Installs Rails.

~ UI ~

The UI is still more of an outline than anything near a finished user 
experience...

Also much of the UI has to be still filled in. Like a javascript
div dropdown for when one clicks the second part of a word (showing a
list of the links that are behind it, with their matching logis and
scores), is still something that is not in there yet.

Of course for that first the RedCloth rule to parse these links from
the textile is needed (something I hope Saurabh likes to create with
us).

You might also have a look at this plan from a previous post (the
archive lags behind quite a bit) for splitting up LogiLogi in 
separate webservices and using javascript to re-combine them (but it
does not seem to me that this is feasable for Manta already):

---

It comes down to splitting LogiLogi up into 2 parts (for a start). The
first part will, based on the url of tags the user visited, return a
list of possible document_id's, the javascript will then call the
second part for ratings given to the document_id's, and then sort them
by rating, and call the first part again for the full document
belonging to the best id, which will then be set in the body-div.

In this way the rating-server can be different from the url/document-
server, and the user can choose which rating-server to use.

Of course there are posibillities for implementing this server-
side, but the beauty of the javascript solution is that it really
separates them.

---

Let us know when you have Manta up and running (and if you encounter
any problems you can of course also let us know ;-)

Wybo

> Thanks again for the news!