Re: [LogiLogi-list] Commited changes, logis-box working IE

On 11/17/06, Wybo Wiersma <wy...@lo...> wrote:
> > > No, the link-splitting happens server-side, that's why links like this
> > > one are already split in the output (that will be input for RedCloth):
> >
> > Ok, so my code will stay as it is now.
>
> It would be really neat if you added a wrapper function around the
> Javascript, so the following:
>
> <span class="logilogi_link">
>   <a href="#left_side">
>     <span class="first_half_link"
>       title="This is the first half of the link">LogiLo</span><span class="second_half_link"
>       id="second_half_link"
>       title="this is the second half of the link"
>       >giLink
>     </span>
>   </a>
>   <span class="logis_box" id="LogiLogiLink">
>   </span>
> </span>
>
> Would become:
>
> <span class="logilogi_link">
>   <a href="#left_side">
>     onload-function that adds the stuff that fits in above like
>     dropDownLogiLink('LogiLo','giLink','en.logilogi.org/link/list/5','link16')
>   </a>
>   <span class="logis_box" id="link16">
>     maybe the div here too
>   </span>
> </span>
>
> The 3d argument is the place where the ajax-call should go to fill up
> the drop-down span/div.
>
> The 4rd argument, and 'link16' span-id refer to this link being the
> 16th link-cluster in the Logi currently being shown, as this will be
> always unique, while LogiLogiLink does not need to be (word could be
> occurring twice with different links behind it....)
>
Ok, this is the poing where server side mixs with client side. I
suggest to make the most in Server Side and print it plain, so there
will be less work for javascript (supose 30 logilogilinks in a page),
and also non-javascript browsers will still be able to work.
We will work on this and commit the code. I hope we can work on the
textile part too.

> > > Actually first the idea was to only place it around the second part on
> > > the server, and leave the first part as a normal link, but I really
> > > like what you did with the background-colors, so we will keep it your
> > > way.
> >
> > Ok, I'm glad you liked the two colors, I just got the concept from
> > your top bar, which as I can see it, talks a lot about LogiLogi, and
> > represents very well the nature of LogiLogi, as far as I understand.
>
> It makes things clear indeed, and it looks good too. The border of the
> drop-down & bg-color however might be changed to match the menu's, and
> in the dropdown there will be links (with green background, like for
> received in incoming links) and below those listings of logi's with
> their score and a white background (like for logi in incoming, but not
> with borders inbetween).
>
Ok, I'll adapt this things to feet the current design.

I'd like to fully understand the working, the future ideas, and really
understan the flow of LogiLogiManta, and then I'd like to work on the
UI as a whole, but now I'll just stick to your design. I'm telling
this becouse while trying to test some 3columns layout I found that
there were things that should change for this to work, and when one
concept changes, it makes many other to change too, and then it will
take too much time, and I really don't know at the moment if any
change is for better, as I didn't see the current UI workin (in
Manta).

> > About the links, RedCloth and the html, still have some questions,.
> >
> > I'm not understanding the process between the text I enter in the edit
> > mode and the output, and if we make some things clearer it will help
> > me to understand better what you and Miguel are trying to do.
> > For what I understand, this are the steps:
> >   * I enter some text in the edit mode "Hello LogiLogi!" but I want to
> > make "LogiLogi" a logilogilink, so this would be the final text I
> > enter:
> >
> > Hello "Logi(botanics/george_bush)":do:logi/view/botanics/george_bush;"Logi":do:link/list/1;!
>
> No, happily enough not, that would be horrible.
>
> You will enter:
>
> Hello "LogiLogi":botanics/george_bush;!
>
OOOOkk.. Sorry I got confused. Now this is much more like a Wiki link
(but with much more knowledge/logi behind it ;)

> >   * The next step, is RedCloth, which understands that LogiLogi is a
> > "dual" link and executes the "do:" parts of both halves of the link.
>
> The next step is the textile= method of LogiVersion. That one will
> filter out the links (without relation to RedCloth), and store them
> in the db.
>
> Then on viewing (for editing they will come back out as they came in)
> links are parsed back in as dual, like what you started with above:
>
> Hello "Logi(botanics/george_bush)":do:logi/view/botanics/george_bush;"Logi":do:link/list/1;!
>
> > The first "do:" of the link is telling RedCloth to create a link to
> > "botanics/george_bush". The second part will make the "list". (what is
> > the "1" for in "link/list/1"?)
>
> No the second part tells it to create the link for the AJAX-call.
> Actually RedCloth will have to parse the dual links as one match,
> because otherwise it would not be possible to add the javascript-
> code around both parts.
>
> The "do:"-part tells it to feed the other parts into the rails
> link_to method to get the link.
>
> >   * Then the next step would be a "view" output, where RedCloth would
> > parse the link template I've made and insert the variables, like this:
> >
> > <a href="logi/view/botanics/george_bush">
> > <span class="first_half_link" >Logi</span>
> > <span class="second_half_link">Logi</span>
> > </a>
> > <span class="logis_box">
> > <ul>
> > <li>
> > <a href="botanics/definitions/Bush">Bush (botanics)</a> score: 0.62
> > </li>
> > <li>
> > <a href="people/presidents/george_bush">George W. Bush (president)</a>
> > score: 0.52
> > </li>
> > </ul>
> > </span>
>
> Not quite, the span will not be filled up yet with the scores. That
> only happens through AJAX when the user clicks the second part of the
> link (otherwise it would be quite database-intensive).
>
> Note that Rails has beautifull functions for calling through AJAX (like
> link_to_remote), so you don't need to re-invent the wheel on this,
> although we cannot use it right-away because it combines link-generation
> and adding the Javascript for the AJAX-call.
>
Ok, I'll have to re-read this many times, then the mantadocs, then
read this again, then some more ruby, then read this again, and then I
might understand it better. Thanks for the explanations, but I just
don't know enough Ruby/Textile/Javascript/LogiLogi to get a clear line
of the process step by step, but I'll get there soon.

> > I'm pasting this code here to make it clear.
> > Could you explain this shortly how is it in a grafical way?
>
> I hope I made it a bit less unclear...
>
> > By the way, today I was going through the trunk and saw the doc/LICENCE.TXT
> > Using GPLv3_draft from the beggining is a very smart move and I
> > believe it should have value, dough it could have bugs, so that's the
> > danger of Beta testings... ;)
>
> I think that in this case GPL v2 has more "bugs" for web-use,
> because it does not allow extra clauses that also consider running
> it on a webserver to be spreading it, and thus requiring one to
> release the sourcecode. Also I appended the Afferro-GPL at the
> bottom, which is GPL v2 + simmilar clauses sanctioned by the FSF.
>
> > After released you could use GPL plain and that would mean the
> > latest version.
>
> I would rather not have the code under GPL v2 or later, because that
> would mean people can choose version 2, and thus create a closed
> version of LogiLogi that they simply share with no-one, but just run
> on their servers.
>
> Also the GPL v3 will come out in it's final version soon, maybe even
> just before Manta goes live.
>
Yes! I was talking about the same you said. I was talking about the
release of the GPLv3. When it's released you could use just GPL as the
licence, but GPLv3 will be the same. I also see you've been around
licenses and probably know more about it than I do.

> > Also, Manta should be in the Savanna as a GNU project when it's
> > released. Don't you think? I could work on that too if you think so,
> > but with time.
>
> I don't think it is necessary because we are already on both
> Sourceforge and RubyForge, which offer simmilar services.
>
> Of course we might move there simply because GNU is closer to the core
> of Free Software, or because their services are better, but as far as
> I can find it they don't provide Subversion at the moment.
>
You are right. I should have said "could" in stead of "should".
There also is the http://directory.fsf.org/

> > Also, I have this bookmark that could be of any help (in the remote
> > case you didn't know about it) http://rubyvote.rubyforge.org/
>
> Looks good. But for Manta voting we have quite specialized needs
> (like peer-groups, differing voting-weights and storage of results
> in ActiveRecord), so it will be better and faster to do this from
> scratch.
>
> Editing pages will not yet be finished today. I'm sorry but there were
> some unforseen problems with the diffing. They are all resolved now,
> but this took a day. The linkless_textile= method works, but the link-
> list setter, and textile= method has not been tested yet.
>
> I will be away from the web for the weekend (a promise made weeks ago,
> to look after the house and the dogs of a friend of mine who lives
> on an island off the coast not far from here (where I once lived for
> half a year), and does not have an i-net connection fast enough to
> code at comfortable speed through an ssh connection). I will use that
> time to do some reading I still need to do for a few courses.
>
> Maybe I will be doing a small commit in an hour or so, but it won't
> be as big as page-editing yet.
>
> I'll be back on Monday morning.
>
> Have a nice weekend all,
>
> Wybo
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> LogiLogi-list mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logilogi-list
>

List! enjoy your weekend!

-- 
Bruno