logilogi-list Mailing List for LogiLogi - Software Libre for the Web (Page 17)

On Thu, May 15, 2008 at 5:47 PM, Wybo Wiersma <wy...@lo...> wrote:
> I've just committed a first version of a fix for the rounded-corners
> problem...
>
> After evaluating different options, I found them all to have problems:
> - niftycorners: the new version did not support borders
> - curvycorners: does not allow text in the curved parts of the corners
>  (esp annoying with the toolbar)
>
>   ---------------
>  / no text here    \
> | only here          |
>
> - TCCB: has the same problem as curvycorners with the curved part and
>  works with hand-made images
>
> So I brew something myself that works with 1 image that is set as the
> background of the div dynamically via javascript (it reads the DOM css
> for background- & border-color & border-width, etc...). And it is
> generated on-demand by RMagick...
>
> Optimalizations in the sense of caching the images (really easy with
> rails, just storing them in the url-location that the controller would
> otherwise receive), and adding one extra footer div for closing the
> images (so divs with various heights use the same image) are there
> too already.
>
> I still need some tweaking to do, and the toolbar-menu is currently
> not working, but more tomorrow.
>
> greetings,
>
> Wybo
>
> PS: Miguel, was it not the case that now, or very soon, you are
> fulltime on LogiLogi as your internship-project ?
>
Indded, I have my two last exams tomorrow, sorry I was not able this
week. I will take this weekend off to rest and I'll see you all monday
for my first day at fulltime on LL =)

> PPS: I will be away with the student-association this weekend, and
> this evening I will be at a local meeting for perl/scripting
> programmers (Perl Mongers).
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> LogiLogi-list mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logilogi-list
>



-- 
Miguel Lezama

I've just committed a first version of a fix for the rounded-corners
problem...

After evaluating different options, I found them all to have problems:
- niftycorners: the new version did not support borders
- curvycorners: does not allow text in the curved parts of the corners
  (esp annoying with the toolbar)

   ---------------
 / no text here    \
| only here          |

- TCCB: has the same problem as curvycorners with the curved part and
  works with hand-made images

So I brew something myself that works with 1 image that is set as the
background of the div dynamically via javascript (it reads the DOM css
for background- & border-color & border-width, etc...). And it is 
generated on-demand by RMagick...

Optimalizations in the sense of caching the images (really easy with
rails, just storing them in the url-location that the controller would
otherwise receive), and adding one extra footer div for closing the 
images (so divs with various heights use the same image) are there 
too already.

I still need some tweaking to do, and the toolbar-menu is currently
not working, but more tomorrow.

greetings,

Wybo

PS: Miguel, was it not the case that now, or very soon, you are
fulltime on LogiLogi as your internship-project ?

PPS: I will be away with the student-association this weekend, and
this evening I will be at a local meeting for perl/scripting 
programmers (Perl Mongers).

I've just deleted all spam, and it seems Manta is spam-free thanks to
the spam-filter so far...

And I also tested it in IE7, and it works there too!

There are still some glitches with the layout in IE-7 and even in FF,
but that's because Bruno and I are in the middle of fixing the
rounded-corners-problem once and for all...

I will be online for the Nijmegen-pplz now,

Wybo

There it is, the spam-protection. It does not use capcha's and it is
bullet-proof, that is not rocket-proof, but the current spam-bots it
should easily keep at a distance...

It relies on:
 * Spam-bots not running JS, nor evaluating CSS
   - JS needed for getting the right submit-url (without it, it's
     http://MyShinyMetalAss/kiss)
 * Spam-bots using JS harvesting the page/form immediately (within 0.5 secs)
   - submit-url is replaced with a delay
 * Spam-bots submitting stuff to all fields
   - there's a css-hidden honey-pot field that errs if filled
 * Spam-bots submitting forms faster than humans (within 5 secs)
   - error if submitted within 5 secs
 * Spam-bots harvesting submit-urls, and later using them
   - submits after 2 or more days give an error
   - submits from a different session give an error

I have not tested it in IE, but I will do so on tuesday morning, when
I will also update the live version with everything committed so
far...

As after all the user is king, and capcha's suck. Imagine having to do
one with every logi created... We can't do such things to users!

Also quite some good news today on IRC, of Bruno & Miguel tackling the
rounded corners in IE! :)

/me will work on some more fixes tomorrow,

Wybo

On Fri, May 9, 2008 at 10:36 AM, Wybo Wiersma <wy...@lo...> wrote:
>> Hi all,
>>
>> As I commented before, I wanted to redraw the current UI in svg so
>> we're all able to work over a common file to exchange ideas, do
>> proposals or whatever. Also maybe this is of any help for Bart and
>> Thierry...
>
> Really cool, and quite a beautiful & detailed copy. Did you make it
> for any specific SVG-program ? As there are sometimes small
> compatibility-issues...
>
> If not, or if for InkScape, we could all use that program.
>
Yes, InkScape, so 100% :)

> Hope you will work on the rounded-corners for IE next :)
>
Yes I will, and now that I can work from home I'm more confortable too...

>> At least we have the elements already there to move arround, change
>> colors, etc...
>
> Cool, it works indeed, down to the smallest detail! :)
>
>> Well, sorry I got distracted with this today, I'll get back on track tomorrow :)
>
> Happens, and I am also distracted with a lot more mundane issues, like
> arranging all travel & accomodation-stuff for the conferences (fun, but
> really a pain without a credit-card), setting up & checking backup-
> scripts for Manta, doing the dishes of days and days ago, and more such
> things... :)
>
> I am almost done with a bullet-proof form-spambots-protection for Manta
> (without using capcha's), by the way, as we are getting real spam-issues
> now...
great!

>
> Wybo
>
>> later.
>>
>> --
>> Bruno
>

later...


-- 
Bruno

> Hi all,
> 
> As I commented before, I wanted to redraw the current UI in svg so
> we're all able to work over a common file to exchange ideas, do
> proposals or whatever. Also maybe this is of any help for Bart and
> Thierry...

Really cool, and quite a beautiful & detailed copy. Did you make it
for any specific SVG-program ? As there are sometimes small
compatibility-issues...

If not, or if for InkScape, we could all use that program.

Hope you will work on the rounded-corners for IE next :)

> At least we have the elements already there to move arround, change
> colors, etc...

Cool, it works indeed, down to the smallest detail! :)

> Well, sorry I got distracted with this today, I'll get back on track tomorrow :)

Happens, and I am also distracted with a lot more mundane issues, like
arranging all travel & accomodation-stuff for the conferences (fun, but
really a pain without a credit-card), setting up & checking backup-
scripts for Manta, doing the dishes of days and days ago, and more such
things... :)

I am almost done with a bullet-proof form-spambots-protection for Manta
(without using capcha's), by the way, as we are getting real spam-issues
now...

Wybo

> later.
> 
> -- 
> Bruno

Hi all,

As I commented before, I wanted to redraw the current UI in svg so
we're all able to work over a common file to exchange ideas, do
proposals or whatever. Also maybe this is of any help for Bart and
Thierry...

At least we have the elements already there to move arround, change
colors, etc...

Well, sorry I got distracted with this today, I'll get back on track tomorrow :)

later.

-- 
Bruno

On Thu, May 8, 2008 at 5:08 PM, Wybo Wiersma <wy...@lo...> wrote:
>> > Also we are having an issue with the lower margins of the modal-box
>> > and indentation in front of form-elements (for example in the create
>> > logi elsewhere wizzard)...
>>
>> I'll check this.
>
> Ok.
>
Still couldn't find the solution, will look over this later tonight.

>> >> > (Also in FF)
>> >> > http://sourceforge.net/tracker/index.php?func=detail&aid=1958742&group_id=78643&atid=553990
>> >>
>> >> This I couldn't find where to fix it, couldn't even find where the
>> >> code for validating forms is :( The problem here is that when the
>> >> error ir raised, the div added and the input inside are moved outside
>> >> of the <p> and that's why it gets moved. I don't know well how this
>> >> works, this should be fixed by some of our JS gurus... :)
>> >
>> > Curious... It surely is done by rails in some way...
>> >
>> > Anyone willing to take up this very interesting bug ?
>>
>> I would go for it, but doing grep -Hnr searches couldn't find any
>> reference to FieldWithErrors apart from the css, so I don't know where
>> to start, but I could keep trying. If anybody can point where errors
>> are processed that would help.
>
> Searching my gem-dir I found it to be set in:
>
> lib/action_view/helpers/active_record_helper.rb, line 6, inside the
> actionpack-gem.
>
> Still I think it is anyway bad practice to use p's for spacing in
> forms, so we'd better change that, then the problem will also be
> fixed... (I added these p's in the first place, but that was in the
> hurry before the release...)
>
I'll fix this.

> I will also be working on a set of example-texts for on LogiLogi, so
> people can get a feel for how it works... & also I and a good friend
> of mine who's a philosopher will have a discussion on Manta as of some
> time next week...
>
looking forward the first LL discussion... :)

> Wybo
>
>> Later.
>>
>>
>> --
>> Bruno
>



-- 
Bruno

> > Also we are having an issue with the lower margins of the modal-box
> > and indentation in front of form-elements (for example in the create
> > logi elsewhere wizzard)...
>
> I'll check this.

Ok.

> >> > (Also in FF)
> >> > http://sourceforge.net/tracker/index.php?func=detail&aid=1958742&group_id=78643&atid=553990
> >>
> >> This I couldn't find where to fix it, couldn't even find where the
> >> code for validating forms is :( The problem here is that when the
> >> error ir raised, the div added and the input inside are moved outside
> >> of the <p> and that's why it gets moved. I don't know well how this
> >> works, this should be fixed by some of our JS gurus... :)
> >
> > Curious... It surely is done by rails in some way...
> >
> > Anyone willing to take up this very interesting bug ?
> 
> I would go for it, but doing grep -Hnr searches couldn't find any
> reference to FieldWithErrors apart from the css, so I don't know where
> to start, but I could keep trying. If anybody can point where errors
> are processed that would help.

Searching my gem-dir I found it to be set in:

lib/action_view/helpers/active_record_helper.rb, line 6, inside the
actionpack-gem.

Still I think it is anyway bad practice to use p's for spacing in
forms, so we'd better change that, then the problem will also be
fixed... (I added these p's in the first place, but that was in the
hurry before the release...)

I will also be working on a set of example-texts for on LogiLogi, so
people can get a feel for how it works... & also I and a good friend
of mine who's a philosopher will have a discussion on Manta as of some
time next week...

Wybo

> Later.
> 
> 
> -- 
> Bruno

As these things better go to the list, I respond here... :)

> Hi wybo, 
> 
> While I was viewing the logilogi (public release), I find it nice.
> But to a right handed person, I would expect the administration bar
> and navigation bar in the left top. And the editor box to the right.
> The layout now is fine, but it may be a bit different from the
> convention. (Just an personal idea, no big deal )

In the old layout & old version of LogiLogi we had menu's on both
sides of the logi...

Still when Andrew (last year's Gip-team) sent in his UI-proposal it
already had the menu on the right. I bilieve he based it back then on
the Usabillity-research done by Audi
(http://jodi.tamu.edu/Articles/v04/i01/Kalbach/) in 2003. 

Their arguments & results seemed at least sensible enough to follow
them. The main-ones being that the user's attention is more on the
content when the menu is on the right, and that the scroll-bar is on
the right side, and so the mouse does not have to move that far from
the scrollbar to the menu....

But a good remark/question...

Wybo

> Feng

> > That might be a good solution. Miguel, do you think setting the width
> > of spans/divs to their current width is possible ?
> 
> Indeed

So you think it is possible, great! Could you do it ?

Wybo

> Although on the svn version is ok, on the public version all the
> overbox functionalities are not working. I'll not add it as a bug
> since it's working on the svn.

This sucked indeed. Totally unexpected it appears that the modalbox
for some reason does not work when hosted under a different, or higher
up domain...

And to prevent browsers swithching from en.logilogi.org to
es.logilogi.org from downloading all JS again, I had set the
asset_host property of Rails, and this wrecked modalbox...

When I came back from the party (which was great by the way! :) I saw
this mail and tried to fix it, and then just commented out the
asset-host bit. Really weird that this does not work, as it's not such
an unusual thing to use separate hosts for static files...

Wybo

> -- 
> Bruno

> Hi Wybo,
> 
> The logi-length warning-code works fine now by IE7. And we also disable
> the submit button if the logi is too long.

Great! I love it.

I've added styling for the messages, and renamed the warning id to
length_warning to prevent confusion with the warning-class.

(I've also tested my changes in IE7)

> By the way, we want to work on the new user story next week, there are
> several of them in the tracker, but all with relatively lower priority.
> Which one would you suggest for now?

I think the link-deletion is most important now... I've increased it's
priority-score to 4.

https://sourceforge.net/tracker/index.php?func=detail&aid=1942260&group_id=78643&atid=898717

Also see this added comment:

---

Some weeks after posting this I think that showing the logi-body in
the modalbox, with the links parsed in there just like on normal view
but now with clickable remove-crosses in there and no info (like found
logi, yes, no) besides the link, would also work, and be a whole lot
more userfriendly...

---

I might add another this weekend, clarifying things more...

So if you like, you two can claim this task :)

Wybo

> Steffen en Feng

Wybo Wiersma wrote:
> Steffen and Feng, your logi-length warning-code works wonderfully :)
> 
> I did test it in IE7, and there's still some issue there of it not
> showing, but as you said in the commit-message, you had not tested it
> yet... :) 
> 
Hi Wybo,

The logi-length warning-code works fine now by IE7. And we also disable
the submit button if the logi is too long.

By the way, we want to work on the new user story next week, there are
several of them in the tracker, but all with relatively lower priority.
Which one would you suggest for now?

Steffen en Feng

On Wed, May 7, 2008 at 6:11 PM, Wybo Wiersma <wy...@lo...> wrote:
> Steffen and Feng, your logi-length warning-code works wonderfully :)
>
>  I did test it in IE7, and there's still some issue there of it not
>  showing, but as you said in the commit-message, you had not tested it
>  yet... :)
>
>  I also committed fixes for 3 things:
>
>  All js-files, except tinymce, are now cached together in one file.
>  This should speed up loading-times a bit (less requests). We still
>  have no compression however.
>
>  Clicking a different-language page now works, and does no longer show
>  without the editor-window.
>
>  Saving a logi with multiple, not yet existing tags, now also works...
>  (previously it was resolved on save to only the content-tag).
>
>
>  > > Now on the agenda are rounded corners for IE7 (can be via nifty
>  > > corners if you wany, or an other solution)...
>  >
>  > About niftycorners, it doesn't work with floated elements that don't
>  > have a fixed width. A fix for this could be to set a fixed width via
>  > javascript. We actually only need this for tags, and only for IE, so
>  > if it's possible it could be considered a as a solution.
>
>  That might be a good solution. Miguel, do you think setting the width
>  of spans/divs to their current width is possible ?
>

Indeed

>
>  > > Some more IE & layout-bugs:
>  > > http://sourceforge.net/tracker/index.php?func=detail&aid=1958739&group_id=78643&atid=553990
>  >
>  > fixed.
>
>  Cool...
>
>  Now still the Openid submit form still seems to be not that well
>  aligned...
>
>  Also we are having an issue with the lower margins of the modal-box
>  and indentation in front of form-elements (for example in the create
>  logi elsewhere wizzard)...
>
>
>  > > (Also in FF)
>  > > http://sourceforge.net/tracker/index.php?func=detail&aid=1958742&group_id=78643&atid=553990
>  >
>  > This I couldn't find where to fix it, couldn't even find where the
>  > code for validating forms is :( The problem here is that when the
>  > error ir raised, the div added and the input inside are moved outside
>  > of the <p> and that's why it gets moved. I don't know well how this
>  > works, this should be fixed by some of our JS gurus... :)
>
>  Curious... It surely is done by rails in some way...
>
>  Anyone willing to take up this very interesting bug ?
>
>
>  > > Also it would be good if we started to generate ideas on what we want
>  > > to show on the front-page, in terms of new-logi-lists with or without
>  > > snippets, top-lists, etc... See this tracker task (also 2 pplz from
>  > > the Nijmegen-team working on it):
>  > >
>  > > http://sourceforge.net/tracker/index.php?func=detail&aid=1958650&group_id=78643&atid=898717
>  >
>  > I'm interested in this too, I'll be thinking about this and would like
>  > to hear others ideas too!
>
>  'k :)
>
>  I will give mine last, as not to set the stage for the debate...
>
>  Wybo
>
>  PS: I will be at the student-association tonight... To attend a
>  relaxing, wild party, after these crazy, but fun & rewarding devving
>  days... (& to get fresh for more, & manta's growth... :)
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Don't miss this year's exciting event. There's still time to save $100.
>  Use priority code J8TL2D2.
>  http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________
>  LogiLogi-list mailing list
>  Log...@li...
>  https://lists.sourceforge.net/lists/listinfo/logilogi-list
>



-- 
Miguel Lezama

Although on the svn version is ok, on the public version all the
overbox functionalities are not working. I'll not add it as a bug
since it's working on the svn.

-- 
Bruno

On Wed, May 7, 2008 at 1:11 PM, Wybo Wiersma <wy...@lo...> wrote:
> Steffen and Feng, your logi-length warning-code works wonderfully :)
>
> I did test it in IE7, and there's still some issue there of it not
> showing, but as you said in the commit-message, you had not tested it
> yet... :)
>
> I also committed fixes for 3 things:
>
> All js-files, except tinymce, are now cached together in one file.
> This should speed up loading-times a bit (less requests). We still
> have no compression however.
>
> Clicking a different-language page now works, and does no longer show
> without the editor-window.
>
> Saving a logi with multiple, not yet existing tags, now also works...
> (previously it was resolved on save to only the content-tag).
>
>> > Now on the agenda are rounded corners for IE7 (can be via nifty
>> > corners if you wany, or an other solution)...
>>
>> About niftycorners, it doesn't work with floated elements that don't
>> have a fixed width. A fix for this could be to set a fixed width via
>> javascript. We actually only need this for tags, and only for IE, so
>> if it's possible it could be considered a as a solution.
>
> That might be a good solution. Miguel, do you think setting the width
> of spans/divs to their current width is possible ?
>
>> > Some more IE & layout-bugs:
>> > http://sourceforge.net/tracker/index.php?func=detail&aid=1958739&group_id=78643&atid=553990
>>
>> fixed.
>
> Cool...
>
> Now still the Openid submit form still seems to be not that well
> aligned...
>
> Also we are having an issue with the lower margins of the modal-box
> and indentation in front of form-elements (for example in the create
> logi elsewhere wizzard)...
>
I'll check this.

>> > (Also in FF)
>> > http://sourceforge.net/tracker/index.php?func=detail&aid=1958742&group_id=78643&atid=553990
>>
>> This I couldn't find where to fix it, couldn't even find where the
>> code for validating forms is :( The problem here is that when the
>> error ir raised, the div added and the input inside are moved outside
>> of the <p> and that's why it gets moved. I don't know well how this
>> works, this should be fixed by some of our JS gurus... :)
>
> Curious... It surely is done by rails in some way...
>
> Anyone willing to take up this very interesting bug ?

I would go for it, but doing grep -Hnr searches couldn't find any
reference to FieldWithErrors apart from the css, so I don't know where
to start, but I could keep trying. If anybody can point where errors
are processed that would help.

Later.


-- 
Bruno

Steffen and Feng, your logi-length warning-code works wonderfully :)

I did test it in IE7, and there's still some issue there of it not
showing, but as you said in the commit-message, you had not tested it
yet... :) 

I also committed fixes for 3 things:

All js-files, except tinymce, are now cached together in one file.
This should speed up loading-times a bit (less requests). We still
have no compression however.

Clicking a different-language page now works, and does no longer show
without the editor-window.

Saving a logi with multiple, not yet existing tags, now also works...
(previously it was resolved on save to only the content-tag).

> > Now on the agenda are rounded corners for IE7 (can be via nifty
> > corners if you wany, or an other solution)...
>
> About niftycorners, it doesn't work with floated elements that don't
> have a fixed width. A fix for this could be to set a fixed width via
> javascript. We actually only need this for tags, and only for IE, so
> if it's possible it could be considered a as a solution.

That might be a good solution. Miguel, do you think setting the width
of spans/divs to their current width is possible ?

> > Some more IE & layout-bugs:
> > http://sourceforge.net/tracker/index.php?func=detail&aid=1958739&group_id=78643&atid=553990
> 
> fixed.

Cool...

Now still the Openid submit form still seems to be not that well
aligned...

Also we are having an issue with the lower margins of the modal-box
and indentation in front of form-elements (for example in the create
logi elsewhere wizzard)...

> > (Also in FF)
> > http://sourceforge.net/tracker/index.php?func=detail&aid=1958742&group_id=78643&atid=553990
>
> This I couldn't find where to fix it, couldn't even find where the
> code for validating forms is :( The problem here is that when the
> error ir raised, the div added and the input inside are moved outside
> of the <p> and that's why it gets moved. I don't know well how this
> works, this should be fixed by some of our JS gurus... :)

Curious... It surely is done by rails in some way...

Anyone willing to take up this very interesting bug ?

> > Also it would be good if we started to generate ideas on what we want
> > to show on the front-page, in terms of new-logi-lists with or without
> > snippets, top-lists, etc... See this tracker task (also 2 pplz from
> > the Nijmegen-team working on it):
> >
> > http://sourceforge.net/tracker/index.php?func=detail&aid=1958650&group_id=78643&atid=898717
>
> I'm interested in this too, I'll be thinking about this and would like
> to hear others ideas too!

'k :)

I will give mine last, as not to set the stage for the debate...

Wybo

PS: I will be at the student-association tonight... To attend a
relaxing, wild party, after these crazy, but fun & rewarding devving 
days... (& to get fresh for more, & manta's growth... :)

On Tue, May 6, 2008 at 10:46 AM, Wybo Wiersma <wy...@lo...> wrote:


> Now on the agenda are rounded corners for IE7 (can be via nifty
> corners if you wany, or an other solution)...
>
About niftycorners, it doesn't work with floated elements that don't
have a fixed width. A fix for this could be to set a fixed width via
javascript. We actually only need this for tags, and only for IE, so
if it's possible it could be considered a as a solution.

> Some more IE & layout-bugs:
> http://sourceforge.net/tracker/index.php?func=detail&aid=1958739&group_id=78643&atid=553990
>
fixed.

> (Also in FF)
> http://sourceforge.net/tracker/index.php?func=detail&aid=1958742&group_id=78643&atid=553990
>
This I couldn't find where to fix it, couldn't even find where the
code for validating forms is :( The problem here is that when the
error ir raised, the div added and the input inside are moved outside
of the <p> and that's why it gets moved. I don't know well how this
works, this should be fixed by some of our JS gurus... :)

> Also it would be good if we started to generate ideas on what we want
> to show on the front-page, in terms of new-logi-lists with or without
> snippets, top-lists, etc... See this tracker task (also 2 pplz from
> the Nijmegen-team working on it):
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1958650&group_id=78643&atid=898717
>
I'm interested in this too, I'll be thinking about this and would like
to hear others ideas too!

> In all good work Bruno,
>
> Wybo
>
>> --
>> Bruno
>

greetings.

-- 
Bruno

On Tue, May 6, 2008 at 10:46 AM, Wybo Wiersma <wy...@lo...> wrote:
>> Well, that's most of the big news, I find the way to make it work...
>> was actually not much work, it just worked out... I've found
>> position:relative to solve many IE problems. We can say now that LL is
>> fully-functional with IE7!!
>
> WoW bruno, you fixed the mother of all bugs! The IE7 tags-problem! :)
>
>> Here is my report on this and other changes:
>>
>>  * Why do you use width: 100%, and clear:both in #logi_bottom_meta
>> div.tags. I set the width to a fixed size. The clear:both is for the
>> visited float:right span, that coused troubles.
>
> Ok. Then the fix works. I don't remember setting it to a %-with. I
> bilieve you introduced this in revision 797 ;)
>
Yes I did, I was repeating your question there... :)

> Good that it's fixed-width again.
>
>>  * Links: I've made some small changes to links site-wide (commented
>> out old styles). I'm trying to unify the meaning of link styles. I
>> tried to understand the logic of current styles but couldn't find it.
>> Are underlined just for links to logis? I would suggest to think about
>> this and make a specification of styles and their minning. By now I
>> did the following:
>>    * I set all a:hover colored the same (including tags)
>>        * I changed background:hover of tabs (I personally didn't liked the
>> dark blue back) to beheive like tool-bar
>>    * kept underlined for logi/sidebar links, while I don't think it
>> makes much sense since in the sidebar there are mixed link-types. Also
>> note that the index pages don't have underline. I think at least a
>> general pattern should be links-to-logi underlined, and that would be
>> most of the links but the system links. Maybe that was the intention
>> on the beggining.
>
> I think that's ok & a good idea. Links to logi's underlined, other
> links not (still missing the signup for new account link).
>
>>  * IE prfs and tag-editing fixed! They where not working for me, still
>> disapearing. I managed to make it work applying position:relative to
>> the components, check out the ie.css. I wanted to separate the default
>
> Good fixes! )
>
>> and IE styles, but don't know why couldn't. I had to duplicate the
>> styles on both stylesheets. I wanted to set the common styles as
>> default and the specific ones at the ie.css (as always) but it
>> strangelly didn't work, I'll check this again later.
>
> Ok. Strange indeed. Maybe it has to do with the div-hierarchy, and
> which parts are specified.
>
> E.g. sometimes
>
>  div.specifig div.something {
>    setting
>  }
>
> Overrides
>
>  div.something {
>    setting
>  }
>
> But then of course all div-hierarchy lines are equal here in this
> case... Weird bug...
>
>>  * also adding links on IE is working now after the changes I made,
>> don't really know why this could happend, but I think it was not
>> working when I started to work and now it is... :)
>
> Cool! :)
>
>> IE bugs (us):
>>  * on the prefs-edit if nothing is changed and submited, site brakes
>> for that user -- filed bug.
>
> Cool, is probably a general bug and not IE-related...
>
>> It's late again, hope to get to meet you'all at the party. Greetings!
>
> Still not seen you pplz, while we are having some virtual cake for you
> pplz :)
>
I didn't get to the party, I'm sorry about that, I really wanted to be there...

>> ps:
>> question: where will power go when voting for a logi created by anonymous?
>
> It will go to dev/null, that is no one gets any power for it...
>
>> proposal: for spam, we should fight it smart, with LL power! :)
>
> Indeed... :) and luckily it's only one message still...
>
> In all great work, great fixes!
>
> Now on the agenda are rounded corners for IE7 (can be via nifty
> corners if you wany, or an other solution)...
>
> Some more IE & layout-bugs:
> http://sourceforge.net/tracker/index.php?func=detail&aid=1958739&group_id=78643&atid=553990
>
> (Also in FF)
> http://sourceforge.net/tracker/index.php?func=detail&aid=1958742&group_id=78643&atid=553990
>
I'll work on this tonight.

> Also it would be good if we started to generate ideas on what we want
> to show on the front-page, in terms of new-logi-lists with or without
> snippets, top-lists, etc... See this tracker task (also 2 pplz from
> the Nijmegen-team working on it):
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1958650&group_id=78643&atid=898717
>
> In all good work Bruno,
>
Thanks Wybo.

> Wybo
>
>> --
>> Bruno

Later!
-- 
Bruno

> Hi, just a quick suggestion now that we are online...
> 
> we should take care of crowlers, maybe we should fine-tune our
> robots.txt for them not to crawl the site so often as we might not
> have that much resources at first...

Might be needed, but on the other hand we don't have that much content
yet for the crowlers to choke on...

(the previous version, with the old UI was indeed hammered by
crowlers, but no such thing seems to be happening now...)

> anyway, what I think we should do for sure is to keep them off the
> edge version: http://www.google.com/search?q=site%3Aedge.logilogi.org

Indeed, good mention... I will change it.

> on the other hand, the site seem friendly to crowlers... :)

:)

> I just didn't wanted to forget about this.

ty,

Wybo

> laterz!
> 
> -- 
> Bruno

> Well, that's most of the big news, I find the way to make it work...
> was actually not much work, it just worked out... I've found
> position:relative to solve many IE problems. We can say now that LL is
> fully-functional with IE7!!

WoW bruno, you fixed the mother of all bugs! The IE7 tags-problem! :)

> Here is my report on this and other changes:
> 
>  * Why do you use width: 100%, and clear:both in #logi_bottom_meta
> div.tags. I set the width to a fixed size. The clear:both is for the
> visited float:right span, that coused troubles.

Ok. Then the fix works. I don't remember setting it to a %-with. I
bilieve you introduced this in revision 797 ;)

Good that it's fixed-width again.

>  * Links: I've made some small changes to links site-wide (commented
> out old styles). I'm trying to unify the meaning of link styles. I
> tried to understand the logic of current styles but couldn't find it.
> Are underlined just for links to logis? I would suggest to think about
> this and make a specification of styles and their minning. By now I
> did the following:
>    * I set all a:hover colored the same (including tags)
> 	 * I changed background:hover of tabs (I personally didn't liked the
> dark blue back) to beheive like tool-bar
>    * kept underlined for logi/sidebar links, while I don't think it
> makes much sense since in the sidebar there are mixed link-types. Also
> note that the index pages don't have underline. I think at least a
> general pattern should be links-to-logi underlined, and that would be
> most of the links but the system links. Maybe that was the intention
> on the beggining.

I think that's ok & a good idea. Links to logi's underlined, other
links not (still missing the signup for new account link).

>  * IE prfs and tag-editing fixed! They where not working for me, still
> disapearing. I managed to make it work applying position:relative to
> the components, check out the ie.css. I wanted to separate the default

Good fixes! )

> and IE styles, but don't know why couldn't. I had to duplicate the
> styles on both stylesheets. I wanted to set the common styles as
> default and the specific ones at the ie.css (as always) but it
> strangelly didn't work, I'll check this again later.

Ok. Strange indeed. Maybe it has to do with the div-hierarchy, and
which parts are specified.

E.g. sometimes

 div.specifig div.something {
    setting
 }

Overrides

 div.something {
    setting
 }

But then of course all div-hierarchy lines are equal here in this
case... Weird bug...

>  * also adding links on IE is working now after the changes I made,
> don't really know why this could happend, but I think it was not
> working when I started to work and now it is... :)

Cool! :)

> IE bugs (us):
>  * on the prefs-edit if nothing is changed and submited, site brakes
> for that user -- filed bug.

Cool, is probably a general bug and not IE-related...

> It's late again, hope to get to meet you'all at the party. Greetings!

Still not seen you pplz, while we are having some virtual cake for you
pplz :)

> ps:
> question: where will power go when voting for a logi created by anonymous?

It will go to dev/null, that is no one gets any power for it...

> proposal: for spam, we should fight it smart, with LL power! :)

Indeed... :) and luckily it's only one message still...

In all great work, great fixes!

Now on the agenda are rounded corners for IE7 (can be via nifty
corners if you wany, or an other solution)...

Some more IE & layout-bugs:
http://sourceforge.net/tracker/index.php?func=detail&aid=1958739&group_id=78643&atid=553990

(Also in FF)
http://sourceforge.net/tracker/index.php?func=detail&aid=1958742&group_id=78643&atid=553990

Also it would be good if we started to generate ideas on what we want
to show on the front-page, in terms of new-logi-lists with or without
snippets, top-lists, etc... See this tracker task (also 2 pplz from
the Nijmegen-team working on it):

http://sourceforge.net/tracker/index.php?func=detail&aid=1958650&group_id=78643&atid=898717

In all good work Bruno,

Wybo

> -- 
> Bruno

Because my IE problem I couldn't test it, but any way, good work
Bruno(pelequie pa los amigos)!

see you all on irc this afternoon!

On Tue, May 6, 2008 at 10:14 AM, Bruno Sarlo <bs...@gm...> wrote:
> Well, that's most of the big news, I find the way to make it work...
>  was actually not much work, it just worked out... I've found
>  position:relative to solve many IE problems. We can say now that LL is
>  fully-functional with IE7!!
>
>  Here is my report on this and other changes:
>
>   * Why do you use width: 100%, and clear:both in #logi_bottom_meta
>  div.tags. I set the width to a fixed size. The clear:both is for the
>  visited float:right span, that coused troubles.
>   * Links: I've made some small changes to links site-wide (commented
>  out old styles). I'm trying to unify the meaning of link styles. I
>  tried to understand the logic of current styles but couldn't find it.
>  Are underlined just for links to logis? I would suggest to think about
>  this and make a specification of styles and their minning. By now I
>  did the following:
>    * I set all a:hover colored the same (including tags)
>          * I changed background:hover of tabs (I personally didn't liked the
>  dark blue back) to beheive like tool-bar
>    * kept underlined for logi/sidebar links, while I don't think it
>  makes much sense since in the sidebar there are mixed link-types. Also
>  note that the index pages don't have underline. I think at least a
>  general pattern should be links-to-logi underlined, and that would be
>  most of the links but the system links. Maybe that was the intention
>  on the beggining.
>   * IE prfs and tag-editing fixed! They where not working for me, still
>  disapearing. I managed to make it work applying position:relative to
>  the components, check out the ie.css. I wanted to separate the default
>  and IE styles, but don't know why couldn't. I had to duplicate the
>  styles on both stylesheets. I wanted to set the common styles as
>  default and the specific ones at the ie.css (as always) but it
>  strangelly didn't work, I'll check this again later.
>   * also adding links on IE is working now after the changes I made,
>  don't really know why this could happend, but I think it was not
>  working when I started to work and now it is... :)
>
>  IE bugs (us):
>   * on the prefs-edit if nothing is changed and submited, site brakes
>  for that user -- filed bug.
>
>  It's late again, hope to get to meet you'all at the party. Greetings!
>
>  ps:
>  question: where will power go when voting for a logi created by anonymous?
>  proposal: for spam, we should fight it smart, with LL power! :)
>
>  --
>  Bruno
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Don't miss this year's exciting event. There's still time to save $100.
>  Use priority code J8TL2D2.
>  http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________
>  LogiLogi-list mailing list
>  Log...@li...
>  https://lists.sourceforge.net/lists/listinfo/logilogi-list
>



-- 
Miguel Lezama

Hi, just a quick suggestion now that we are online...

we should take care of crowlers, maybe we should fine-tune our
robots.txt for them not to crawl the site so often as we might not
have that much resources at first...

anyway, what I think we should do for sure is to keep them off the
edge version: http://www.google.com/search?q=site%3Aedge.logilogi.org

on the other hand, the site seem friendly to crowlers... :)

I just didn't wanted to forget about this.

laterz!

-- 
Bruno

Well, that's most of the big news, I find the way to make it work...
was actually not much work, it just worked out... I've found
position:relative to solve many IE problems. We can say now that LL is
fully-functional with IE7!!

Here is my report on this and other changes:

 * Why do you use width: 100%, and clear:both in #logi_bottom_meta
div.tags. I set the width to a fixed size. The clear:both is for the
visited float:right span, that coused troubles.
 * Links: I've made some small changes to links site-wide (commented
out old styles). I'm trying to unify the meaning of link styles. I
tried to understand the logic of current styles but couldn't find it.
Are underlined just for links to logis? I would suggest to think about
this and make a specification of styles and their minning. By now I
did the following:
   * I set all a:hover colored the same (including tags)
	 * I changed background:hover of tabs (I personally didn't liked the
dark blue back) to beheive like tool-bar
   * kept underlined for logi/sidebar links, while I don't think it
makes much sense since in the sidebar there are mixed link-types. Also
note that the index pages don't have underline. I think at least a
general pattern should be links-to-logi underlined, and that would be
most of the links but the system links. Maybe that was the intention
on the beggining.
 * IE prfs and tag-editing fixed! They where not working for me, still
disapearing. I managed to make it work applying position:relative to
the components, check out the ie.css. I wanted to separate the default
and IE styles, but don't know why couldn't. I had to duplicate the
styles on both stylesheets. I wanted to set the common styles as
default and the specific ones at the ie.css (as always) but it
strangelly didn't work, I'll check this again later.
 * also adding links on IE is working now after the changes I made,
don't really know why this could happend, but I think it was not
working when I started to work and now it is... :)

IE bugs (us):
 * on the prefs-edit if nothing is changed and submited, site brakes
for that user -- filed bug.

It's late again, hope to get to meet you'all at the party. Greetings!

ps:
question: where will power go when voting for a logi created by anonymous?
proposal: for spam, we should fight it smart, with LL power! :)

-- 
Bruno