Re: [LogiLogi-list] GUI-dev - link logis pop-over

> > select which link is best for the first part, once clicked. This does
> > however require us to also finish that bit of the code before the
> > release (possibly a stub that just takes the first link returned
> > in the list).
>
> I've been trying to understand LogiLogi and still are trying to
> understand some parts, although I think I understand the main porpuse
> (I hope I do!).

You do, I think :)

> I thought that the first part would take you to a static link, which
> was put by hand, and the right side would show you the logis.
> Don't waste time explaining this now, I'll understand it bit a bit.

I will explain it anyway, also for Miguel...:

If an user puts a link begind LogiLogiLink, like:

"LogiLogiLink":botanics/george_bush

And this is saved. Then when he views the page again, it is parsed
into the following textile (the newline is included for clarity):

"LogiLo(botanics/george_bush)":do:logi/view/botanics/george_bush;
"giLink":do:link/list/1

Where the part between '()', 'botanics/george_bush' is what will 
be shown on mouse roll-over of the first part (LogiLo), and 'giLink'
is the second part of the link, and that is the part that will give
an AJAX-call to en.logilogi.org/do/link/list/1, which will fill up
the drop-down div.

So you don't need to pay any attention to the first part. The second
part is a normal link that through AJAX calls for a drop-down-list

If Miguel adds the RedCloth rule it's his business to make sure that
all links with do: behind the "linktext":-part, like do:link/list/1 
are parsed to link_to :controller => link, :action => list, :id => 1

> Ok, in your second email you said it'd be better to stick with the
> two-part solution, so... do I have to change the code? do you now need
> there to be two links instead of only one?

There will be two, but you only need to take care of the second
(except maybe for things like adding a background-color to make it
clear to the user that it's the second or the first part).

> > It's in there now. I renamed the stylesheet to new_gui_logilogi.css,
> > so untill we integrate it in app/view/layouts/main.rhtml, we have no
> > interference with the old gui.
> >
> > I first kept it separate because for you working on plain html is
> > probably easier. Let me know when you are done with the page-layout
> > (3-column problem maybe too), because I/we can then integrate it.
>
> I spend some minutes yesterday looking for 3columns layouts (although
> I say I wouldn't).
> There are some exelent resources for this like the css-discuss
> tableless layouts list:
> http://css-discuss.incutio.com/?page=ThreeColumnLayouts
> 
> I found some interesting ones but I'll have to look further and test
> them. I also found some that handles what you did in LogiLogi, here
> they are: http://www.pmob.co.uk/temp/3colfixedtest_4.htm
> http://www.pmob.co.uk/temp/3colfixedtest_sourcenone.htm
> http://www.tanfa.co.uk/css/layouts/css-3-column-layout-v1.asp
> 
> But there are also many other great codes arround, like the
> Positioniseverything people  "in search of the One True Layout"
> http://www.positioniseverything.net/articles/onetruelayout/examples
> 
> As  you can see, this is something much talked about, and I believe we
> could enjoy a fluid logilogi if we incorporate this.

I back then also used a Positioniseverything layout to work from. 
So we will get there. But the sticky footer will be tricky.

> Let me work on this later, I'll give priority to the logilogilink first.

Ok.

> What is really bothering me is the logilogilink not working on IE when
> the link is in the middle of a paragraph and it creates a blank line,
> but I'll solve it asap. I might have to add some div, span, but I'll
> fix it.

That's difficult indeed.

I'm a.t.m. still working on the diffing. I encountered some hurdles too.

Wybo