Re: [LogiLogi-list] Wedding & my work on the back-end of Manta.

> > These work beautifully now!
> >
> > Would it be possible also to automatically close the link-drop-down after
> > the mouse leaves the drop-down-div ?
> >
> 
> There are two possibilities:
> * on_mouse_over / mouse_out
> * on_click / on_click_anyware_else_outside
> 
> The easy way should be mouse_over/out but Miguel knows about this.

Mouse-over I think is the most beautifull solution, although it could
become quite system-intensive. So if on_click / mouse_out is not
possible, I think we should go for on_click / on_click_outside + the
close-link we have now.

> > >  * Page-width - I believe you are talking about the body width, as I
> > > see the old LogiLogi has a fixed width. I don't think this is the best
> > > idea as it wont be fluid, but we could try to make it not fixed but
> > > proportional to the width of the screen, so if you have a big screen
> > > the body wont get lost in the middle with lots of white space on the
> > > sides...
> >
> > I have mixed feelings about this. As it is well known that pages that are
> > less wide are easier to read... So there is something to say for both
> > approaches...
> 
> Ok, The best should be some kind of multiple columns layout depending
> on screen size! that would be great. Anyway, it would be nice to make
> some kind of max-width, but I'll have to search for browser
> compatibility...

I think that will be too funky to be priority for now.

> Do you prefere it to be fixed size? like the old one? It's a second.

That's ok. Fixed, and down-sizing if the screen is smaller.

> > >  * Menu-width - I'll get the menues back as they were, it's just a second.
> >
> > Ok.
> >
> > About the new version 1; The side-borders probably are a design-choice ?
> > I think I need some time to get used to them. Maybe if they became
> > symmetric (having them for page-elements & menu on the right side) could
> > be nice too.
> 
> Ok, This where tries. I also asked myself whether the "incoming links"
> list items would be nested lists. Also what would the context be, more

The incoming links will be nested lists.

> kind of keyword/tag clouds...

Context will be indeed tag-clouds in nested-list form (with all logi's
that share all thags with the current location under their primary tag).

> > About my own work: I'm a bit entangled at the moment in upgrading the
> > configuration-system (for storing settings in the database) and also
> > adding minor upgrades to the link-system in order to be able to
> > beautifully handle page-elements. I hope to be able to make a commit
> > later tomorrow, but it could become some time after that.
> 
> Where do page-elements come from? are they standard or just tags
> asigned to text sections?

They are separate logi's, tagged with an element-tag as their primary
tag. Just about working on that now.

So if you create a page at some_page/menu, it will be included as the
left menu when visiting the some_page.

> > The new layout can be integrated really soon now.
> 
> Please guide me with wich files to modify and I'll do it if you
> prefere, if not go ahead and please modify it coping my html.

Would be great if you could do it, as I am still facing quite a bit of
work for getting the config- and element-stuff done.

The main file is at app/views/layouts/main.rhtml, css at
public/stylesheets. Other, more arcane parts are in app/views/logi.

The url-bar is somewhere else, but I'll do that one as it is quite
mixed with ruby.

> > What, in your view, would be the best place on the page to show the
> > ratings (from the different peer-groups), and the rating-UI ?
> 
> I'll think about this. I'll have to read again the Docs... any
> guidance will be much appreciate about what would be available
> information for the page, logis, peer groups, etc, related to a
> certain article.

An article is a logi.

Logis can be voted on by peer_groups. This should be possible
somewhere on the page. I was thinking about above the blocks on the
right.

Besides this it has a creation- and last-edit-time. A creator, and
many editors. And more.

> I'm not sure if it's the right approach, but I believe that if we
> guide the user with popovers (display box/globe on mouseover) on
> links, words/concepts, images, user names, etc, etc, and the user can
> at some point customize (in quick preferences for example) which level
> of information he wants to be displayed.

Would be cool. Seems not too complicated too.

> Is there a rating for every item of the boxes in the page? (incoming
> links, contexts, page elements)

Only logi's can be rated. So everything that is a logi can (elements +
the page itself). But it's ok if elements can only rated if visiting
them as a page (at some_page/menu, instead of as the menu shown left
to some_page).

> I'd really like to re-think about the entire UI once Manta is up and
> running and the information starts to flow.

That'd be possible, but I agree that for now it's faster to stick with 
the current design.

As you see I didn't make it to commit tonight. Tomorrow I'll be away
all day doing work as a member of a commission that is responsible for 
checking the quality of other universities, so it'll have to wait ('ll 
probably be on wednesday or thursday).

But our Manta is going to be great!,

Wybo