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

I just committed some more IE-fixes, some more cleanups (introducing a
panel_content_padding) and a start with styling the boxes of the wizzard...

(I broke the logi toolbar a bit but will fix it soon...)

> for the peergroup select box, I'm working on it, we could use a simple
> select for the upcomming days if you will, I'll look into this
> approach and style it
> http://weblog.morosystems.cz/ostatni/dropdown-xhtml-css-javascript-replacement-of-classic-selectbox#komentare

Looks good, and have been on IRC about it yesterday evening... Hope it works
out, but if not; a drop-down menu styled like a button will do too for now...

> Yes, frustrating, but we're already on the way... Although I would
> have like to launch the 22, it was really not possible, and the
> process of them to adopt logilogi will take time.

I guess it is true it was not possible... Still about a week before
the deadline it still seemed feasable... But anyway, we missed it and
nothing we can do about that now... the most important thing is to 
make the site good now, and ready for launch within weeks... :)

> About this, I have some thoughts already about how to work with the
> muniato people, what they need and what they will need to move to
> logilogi, and this is a great oportunity to understand the needs of
> this and other groups, but we'll talk about this more extensivelly
> later. I'd also like you Wybo to be able to view how they work,
> although it's in spanish, but I will keep you informed.

Indeed, very interested in what they are currently doing.

And about needs, I think we should get a launch now first on the basic
functionality for the main site, and then we can improve it from
there...

> > I think it seems a good idea if we have an abstract box-class, that
> > has 1em margins on the left side and at the top. If we then make all
> > panels, headers, etc, also be of this class, and modify the colums a
> > bit, then we have good and stable padding for the various panels and
> > blocks everywhere...
> >
> > What do you think of this Bruno ?
> 
> Very good... now we see clearly that's the approach and how we can
> solve most layouts like that. So this box will have all current
> diferent parts as an option? like with_tabs, with_header for_edit?

Indeed worked out well :)

"parts" were not given as options, but a base box class for margings, and 
then panels for the coloring and borders, and within those a content_padding 
div for the padding and in those the content...

I also added some comments to the CSS on this...

For this weekend I will be to a dutch island with some friends... When I said
I'd join them I hoped we would have had a successfull launch this week, so it
would be some happy relaxing; now I guess it's just a short intermezzo beteen
the happy devving that will bring us a launch within weeks :)

Will be back on sunday evening,

Wybo

> later...
> 
> -- 
> Bruno

Wybo,

for the peergroup select box, I'm working on it, we could use a simple
select for the upcomming days if you will, I'll look into this
approach and style it
http://weblog.morosystems.cz/ostatni/dropdown-xhtml-css-javascript-replacement-of-classic-selectbox#komentare

I'll be out tomorrow...

talk to you all later.

On Wed, Sep 24, 2008 at 5:14 PM, Bruno Sarlo <bs...@gm...> wrote:
> On Wed, Sep 24, 2008 at 2:50 PM, Wybo Wiersma <wy...@lo...> wrote:
>> I just finished hooking up the ratings via rjs. They also work in IE7
>> and in Firefox 2... :)
>>
> great :)
>
>
>> the author that changed it, but probably without his avatar, small or
>> big... (while the newly created logis are a different matter and are
>> like news, where the snippet is usefull to see what's new)
>>
>
> Ok, right.
>
>> you said you would... I mean reconsidering font-sizes seems to me to
>> clearly to be something for after launch...
>>
>
> sure...
>
>> And about sticking to the svg; I thought that is handy, so we both,
>> when styling know what to do, without us working into different
>> directions again... So I'd propose that if we want to do something
>> different from the svg, we first propose it in the svg and discuss
>> it...
>
> ok :)
>
>>
>> Also I guess I still was a bit disappointed / stressed out because we
>> missed the Muniato deadline, even regardless of the very long days I
>> made to make it...
>>
>
> Yes, frustrating, but we're already on the way... Although I would
> have like to launch the 22, it was really not possible, and the
> process of them to adopt logilogi will take time.
>
> About this, I have some thoughts already about how to work with the
> muniato people, what they need and what they will need to move to
> logilogi, and this is a great oportunity to understand the needs of
> this and other groups, but we'll talk about this more extensivelly
> later. I'd also like you Wybo to be able to view how they work,
> although it's in spanish, but I will keep you informed.
>
>> ---
>>
>> I think it seems a good idea if we have an abstract box-class, that
>> has 1em margins on the left side and at the top. If we then make all
>> panels, headers, etc, also be of this class, and modify the colums a
>> bit, then we have good and stable padding for the various panels and
>> blocks everywhere...
>>
>> What do you think of this Bruno ?
>>
>
> Very good... now we see clearly that's the approach and how we can
> solve most layouts like that. So this box will have all current
> diferent parts as an option? like with_tabs, with_header for_edit?
>
> later...
>
> --
> Bruno
>



-- 
Bruno

On Wed, Sep 24, 2008 at 2:50 PM, Wybo Wiersma <wy...@lo...> wrote:
> I just finished hooking up the ratings via rjs. They also work in IE7
> and in Firefox 2... :)
>
great :)


> the author that changed it, but probably without his avatar, small or
> big... (while the newly created logis are a different matter and are
> like news, where the snippet is usefull to see what's new)
>

Ok, right.

> you said you would... I mean reconsidering font-sizes seems to me to
> clearly to be something for after launch...
>

sure...

> And about sticking to the svg; I thought that is handy, so we both,
> when styling know what to do, without us working into different
> directions again... So I'd propose that if we want to do something
> different from the svg, we first propose it in the svg and discuss
> it...

ok :)

>
> Also I guess I still was a bit disappointed / stressed out because we
> missed the Muniato deadline, even regardless of the very long days I
> made to make it...
>

Yes, frustrating, but we're already on the way... Although I would
have like to launch the 22, it was really not possible, and the
process of them to adopt logilogi will take time.

About this, I have some thoughts already about how to work with the
muniato people, what they need and what they will need to move to
logilogi, and this is a great oportunity to understand the needs of
this and other groups, but we'll talk about this more extensivelly
later. I'd also like you Wybo to be able to view how they work,
although it's in spanish, but I will keep you informed.

> ---
>
> I think it seems a good idea if we have an abstract box-class, that
> has 1em margins on the left side and at the top. If we then make all
> panels, headers, etc, also be of this class, and modify the colums a
> bit, then we have good and stable padding for the various panels and
> blocks everywhere...
>
> What do you think of this Bruno ?
>

Very good... now we see clearly that's the approach and how we can
solve most layouts like that. So this box will have all current
diferent parts as an option? like with_tabs, with_header for_edit?

later...

-- 
Bruno

I just finished hooking up the ratings via rjs. They also work in IE7
and in Firefox 2... :)

To come back to our short small discussion of yesterday, Bruno, yup
recent changes are different from new logis, and I only displayed them
as snippets, so we had something up there, and the display should be
more like that on the changes tab; A list, with title, logi-url and
the author that changed it, but probably without his avatar, small or
big... (while the newly created logis are a different matter and are
like news, where the snippet is usefull to see what's new)

And about changing font-sizes, I mean I am not against non-drastic
font-size changes, but I fear it could break things, if done globally. 
Also I found it a bit strange that you were talking about changing 
font-sizes (and links) yesterday, while many things like the peergroup 
dropdown, the border and the toolbar were still unfixed, days after 
you said you would... I mean reconsidering font-sizes seems to me to
clearly to be something for after launch...

And about sticking to the svg; I thought that is handy, so we both,
when styling know what to do, without us working into different
directions again... So I'd propose that if we want to do something
different from the svg, we first propose it in the svg and discuss
it...

Also I guess I still was a bit disappointed / stressed out because we
missed the Muniato deadline, even regardless of the very long days I
made to make it...

---

Anyway, about the underlying CSS of the UI, I think we could abstract
some things to make the UI less brittle, especially concerning
margins / padding...

I think it seems a good idea if we have an abstract box-class, that
has 1em margins on the left side and at the top. If we then make all
panels, headers, etc, also be of this class, and modify the colums a
bit, then we have good and stable padding for the various panels and 
blocks everywhere...

What do you think of this Bruno ?

I might try to do this tomorrow, as the back-end & hooking up work is
largely done now for basic launch functionality, so I can spend my
time cleaning and helping out like a good housekeeper... :)

greetings,

Wybo

PS: I will be at the student-association this evening as we have an
introduction-ceremony for new members, back tomorrow...

PPS: Hope the list works now, as it did not work well for some days
now...

> Excellent work Wybo!
> 
> Finally I didn't had much time to work, but I have some code already
> almost working for the tabs.

Great :)

(still the tabs were already working, weren't they ?, or did you mean
the tags ? :)

> I will try to commit it tomorrow, I have some time to work on between
> 11:30 and 13:30.

Good. Looking forward to it, even if it will be this evening,

About my commit of yesterday, with the cleaned up controller logic.
Some part of the weaving_out of links and remarks might look a bit
over-complex for what we do with it now, but it's there like that for
2 reasons:

- Firstly; in the older version of Manta, before we had tinymce it was
  supposed that when editing links, this happened via a wiki-like
  syntax, and that allowed adding multiple links at the same time...
  So the code that could do more than it needed to, was still around.
- Secondly; after we've got the UI all working and launched around the
  end of september with the wizzards and all, it might be a nice idea
  to also add an expert-mode for inserting things, that allows one to
  add links [[like this|The/Tags]], or comments [[like this|Really
  good writing here :)]].

I know this may be superfuous at this stage, and a nightmare for
newbies (therefore expert mode), but as I plan on using logilogi quite
extensively soon, I would find it very handy to have such a short-cut, 
and probably others too...

But as said we only will do things like this when everything is
working perfectly and user-friendly via wizzards, but as the code was
around anyway, it seemed good to leave it in the controllers with
Super Cow Powers, even if we don't milk them yet fully... :)

> I am going to sleep early today as this morning it was very hard  :)

Sleep, the commit of each day's code, the bugfree devver's bath :)

(a fork from Shakespeare's :)

> Waiting for Bruno comments on Uytopias presentation.

Indeed Bruno :)

We want to know more than the few lines from IRC :)

Wybo

PS: I'm working on the rating-stars today...

> Greetings,
> 
> Miguel

Excellent work Wybo!

Finally I didn't had much time to work, but I have some code already
almost working  for the tabs.
I will try to commit it tomorrow, I have some time to work on between
11:30 and 13:30.

I am going to sleep early today as this morning it was very hard  :)

Waiting for Bruno comments on Uytopias presentation.

Greetings,

Miguel




On Mon, Sep 22, 2008 at 5:45 PM, Wybo Wiersma <wy...@lo...> wrote:
> I just committed the integration into insert of links and commenting
> logis (+ some cleanups in the controllers agian)...
>
> Still there's one but, but it's not a big one :)
>
> Because I could not yet really find the js for it, I set the links to
> a static text for now. So for now you can only add one pre-set link,
> and it is Logi_Logi/Panda. And commenting logis will have the link
> Logi_Logi/Gui_Duck...
>
> But besides that, it all works, and I think this is relatively easy to
> fix from the javascript once the tags adding works...
>
> Wybo
>
> PS: I will be having dinner with friends tonight, will try to be back
> early, but might get late too... esp as we are not making the deadline
> anymore, I thought it was time for some socializing again; still back
> tomorrow in full force... :)
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> LogiLogi-list mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logilogi-list
>

I just committed the integration into insert of links and commenting
logis (+ some cleanups in the controllers agian)...

Still there's one but, but it's not a big one :)

Because I could not yet really find the js for it, I set the links to
a static text for now. So for now you can only add one pre-set link,
and it is Logi_Logi/Panda. And commenting logis will have the link
Logi_Logi/Gui_Duck...

But besides that, it all works, and I think this is relatively easy to
fix from the javascript once the tags adding works...

Wybo

PS: I will be having dinner with friends tonight, will try to be back
early, but might get late too... esp as we are not making the deadline
anymore, I thought it was time for some socializing again; still back
tomorrow in full force... :)

2 Mails have not arrived on the list so far, hope this one does...

We are making great progress with devving:
http://edge.logilogi.org

& A note to Miguel:

I tried to integrate remarks first, but did not succeed as focus is
mysteriously lost when doing setContent on line 251 of
application.js... it simply stops executing js there without an 
error so far I can find out...

Anyway great work so far on the wizzard,

Wybo

>
> PS: What do you think of the star/crosses with only 3 colors ? Red for
> awarded crosses, yellow for awarded stars, and grey for all not red or
> yellow...
>

it's good, I'll do it.

-- 
Bruno

> let's work toghether over a list of this type, deleting whats done,
> adding what we see is left.

Ok :)

TODO

Core
 * xapian working ok? (done)
 * not existing data
   * main
   * logi
   * user homepage
   * group homepage
   * help (need layout with sections pointing to logilogi-help-logis)

UI assembly with trunk
 * finish logi view, browsing, search
 * create basic html for editing logi
 * rest of the pages layouts, basically under the same structure,
   navbar various columns
 * translation. First define all text in english and pass it asap to
   the muniato list, somebody would do the translation

Javascript
 * logi edition (and tags with the logi)
 * selection tool working crossbrowser?

MAYDO

 * usergroups; probably not feasable before 23rd, only peergroups

---

Being in time for the deadline might still be possible, but it may be
hard, especially in getting it upto standard in the details,

Wybo

PS: What do you think of the star/crosses with only 3 colors ? Red for
awarded crosses, yellow for awarded stars, and grey for all not red or
yellow...

Great work both of you!

Tomorrow I have to go to the university only in the morning, so I will
be working on LL the all afternoon,

Wybo, are you going to be on the IRC?




On Thu, Sep 18, 2008 at 10:32 PM, Bruno Sarlo <bs...@gm...> wrote:
> let's work toghether over a list of this type, deleting whats done,
> adding what we see is left.
>
> Core
>  * xapian working ok?
>  * not existing data
>   * main
>   * logi
>   * user homepage
>   * group homepage
>   * help (need layout with sections pointing to logilogi-help-logis)
>
> UI assembly with trunk
>  * finish logi view
>  * create basic html for editing logi
>  * rest of the pages layouts, basically under the same structure,
> navbar various columns
>  * translation. First define all text in english and pass it asap to
> the muniato list, somebody would do the translation
>
> Javascript
>  * logi edition
>  * selection tool working crossbrowser?
>
> --
> Bruno
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> LogiLogi-list mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logilogi-list
>

let's work toghether over a list of this type, deleting whats done,
adding what we see is left.

Core
 * xapian working ok?
 * not existing data
   * main
   * logi
   * user homepage
   * group homepage
   * help (need layout with sections pointing to logilogi-help-logis)

UI assembly with trunk
 * finish logi view
 * create basic html for editing logi
 * rest of the pages layouts, basically under the same structure,
navbar various columns
 * translation. First define all text in english and pass it asap to
the muniato list, somebody would do the translation

Javascript
 * logi edition
 * selection tool working crossbrowser?

-- 
Bruno

I just committed remarks with spam protection... Earlier today I added
llcorners to the remarks, recent votes and comments... Works well, at
least here :)

Also did some cleanups in templating, and it is now very easy to add
new boxes to the UI without code-duplication, via render :layout =>
'application/panel_with_header', etc...

I am away now for some hours; a dinner in the city and then a local
perl-programmers meeting... Will be back before 11:30 to do some more
devving tonight,

greetings,

Wybo

> > Maybe grey for not awarded stars / crosses, red for awarded crosses,
> > yellow for awarded stars. And as when voting we differentiate between
> > the average vote and the vote given by the user, we need no more
> > colors...
> 
> Ok, I didn't know what colors to put so I put some provisory... shocking red :)
> 
> Ok, what colors would this be? blue for user vote? the color should
> apear when mouseover and when showing user rating.

Maybe a paradigm-switch here too :) But we only need 2 colors (or 3 if
we want to make crosses red).

This first because when only showing ratings (like in the contenders list) 
the user is not supposed to be able to change them...

Secondly because in the bar in which the user can vote, we show the
average vote separately from the user's vote... Showing is just 2
colors, but because the user-vote is just the vote by the user, it can
be grey before he voted, and colored when he mouses over & is done...

(possibly when mouse-overing his vote it can change again if we want
to allow vote-changes...)

3-colors are only custom for when the stars are display of average and
thing to vote with at the same time...

Or am I missing something ?

Wybo

> let me know and I'll do it. There will still be 3 colors, grey, yello, and user.
> 
> >
> > Wybo

> > I just committed some more wireing up and integration. The
> > new_logilogi.html is now integrated in the trunk :)
> >
> > (hope we can work on the trunk now...)
> 
> it seems that my best way to work will be on my server on the LL
> trunk... I'll be working there.

'k Great, I'm now awake & devving again too :)

> > Some bits may not have been copied over, especially regarding the
> > secondary tabs, as I did not know what to do with those...
> >
> > I also made a start with hooking up remarks, but while doing that, and
> > really already when adding the commenting logis, I ran across the
> > naming of the bordered boxes, especially the different colored ones
> > (those that should be differently colored in line with the svg)...
> >
> > Now most start with class="logi_current logi", and that may not be
> > neatest... Now I bet you already planned on changing that, but maybe
> > we should give all the boxes the same name, like border_box, or
> > something, and then determine the color via the css, based on the div
> > they are in... (just like we do with the primary tabs)
> 
> Well, all works this way. The rounded corners are always the same lt,
> rt, rb, lb, but change the image depending on the context they are
> applied.

'k Good, still yesterday the colors were still the same...

> The logi_current is a special case where the log border is different,
> the rest are just logis.

Will await your commit, and fix the class name for commenting logis
and remarks if you had no time for it.

> the other aspect to take in count is that the corners that simulate
> transparency are different for each box. On the nav-bar are dark blue,
> in the sidebar soft, in the logi-borders white...

That makes it indeed more complicated, but it is neccesary...

> > (except maybe for the current logi, or the selected contender)
> >
> > This would make the styling clean, and really separate from the
> > html (and allow putting the code needed for the box in a single
> > layout partial, just like app/views/application/round_box.html.erb
> > for the rounded boxes)...
> >
> > So if you like it that way, you can do it...
> 
> Right now, there are different ways I create the rounded corners, so I
> don't think we can do this globally.

'k

> > I also did an attempt of fixing the min_height keeper in the current
> > logi, with an overflow: auto, but it required setting the width of the
> > logi_body manually... dunno if there is a better solution, as this one
> > also breaks the border of the current logi...
> 
> I corrected this on the commit of early yesterday. I added a grey div
> so you can see it, then we color it white.

It was not working, as when there was less text it sticked through the
bottom of the current logi box...

Hm... When checking it now, it seems to be working in new_logilogi.html,
strange, as it did not work when added to the trunk... Must have
missed something on integration...

> > In all fixes I did I sticked closely to the SVG, and I am using
> > Firefox 3.0.1 on linux for it... Hope it is not too different from the
> > other Firefoxes...
> 
> I'm starting to work on the trunk right now :) See you in a coupple of hours.

I'm there :)

Wybo

> Greetings
> 
> -- 
> Bruno

On Wed, Sep 17, 2008 at 2:54 PM, Wybo Wiersma <wy...@lo...> wrote:
> I just committed some more wireing up and integration. The
> new_logilogi.html is now integrated in the trunk :)
>
> (hope we can work on the trunk now...)

it seems that my best way to work will be on my server on the LL
trunk... I'll be working there.

>
> Some bits may not have been copied over, especially regarding the
> secondary tabs, as I did not know what to do with those...
>
> I also made a start with hooking up remarks, but while doing that, and
> really already when adding the commenting logis, I ran across the
> naming of the bordered boxes, especially the different colored ones
> (those that should be differently colored in line with the svg)...
>
> Now most start with class="logi_current logi", and that may not be
> neatest... Now I bet you already planned on changing that, but maybe
> we should give all the boxes the same name, like border_box, or
> something, and then determine the color via the css, based on the div
> they are in... (just like we do with the primary tabs)
>
Well, all works this way. The rounded corners are always the same lt,
rt, rb, lb, but change the image depending on the context they are
applied.

The logi_current is a special case where the log border is different,
the rest are just logis.

the other aspect to take in count is that the corners that simulate
transparency are different for each box. On the nav-bar are dark blue,
in the sidebar soft, in the logi-borders white...

> (except maybe for the current logi, or the selected contender)
>
> This would make the styling clean, and really separate from the
> html (and allow putting the code needed for the box in a single
> layout partial, just like app/views/application/round_box.html.erb
> for the rounded boxes)...
>
> So if you like it that way, you can do it...

Right now, there are different ways I create the rounded corners, so I
don't think we can do this globally.

>
> I also did an attempt of fixing the min_height keeper in the current
> logi, with an overflow: auto, but it required setting the width of the
> logi_body manually... dunno if there is a better solution, as this one
> also breaks the border of the current logi...
>

I corrected this on the commit of early yesterday. I added a grey div
so you can see it, then we color it white.

> In all fixes I did I sticked closely to the SVG, and I am using
> Firefox 3.0.1 on linux for it... Hope it is not too different from the
> other Firefoxes...
>

I'm starting to work on the trunk right now :) See you in a coupple of hours.

Greetings

-- 
Bruno

On Wed, Sep 17, 2008 at 3:18 PM, Wybo Wiersma <wy...@lo...> wrote:
> I just forgot one thing, or rather 2 things;
>
> First of all it's great how far we already are with the UI and how
> well it behaves on things like resizing and such; really good work! :)
>
thanks Wybo, good to hear that!

> And one small thing; the color of the stars and crosses when mouse-
> overing are maybe not the best ones, as red is associated with
> negative/minus, and might thus be more suitable for the crosses...
>
> Maybe grey for not awarded stars / crosses, red for awarded crosses,
> yellow for awarded stars. And as when voting we differentiate between
> the average vote and the vote given by the user, we need no more
> colors...

Ok, I didn't know what colors to put so I put some provisory... shocking red :)

Ok, what colors would this be? blue for user vote? the color should
apear when mouseover and when showing user rating.

let me know and I'll do it. There will still be 3 colors, grey, yello, and user.

>
> Wybo
>



-- 
Bruno

I just forgot one thing, or rather 2 things;

First of all it's great how far we already are with the UI and how
well it behaves on things like resizing and such; really good work! :)

And one small thing; the color of the stars and crosses when mouse-
overing are maybe not the best ones, as red is associated with
negative/minus, and might thus be more suitable for the crosses...

Maybe grey for not awarded stars / crosses, red for awarded crosses,
yellow for awarded stars. And as when voting we differentiate between
the average vote and the vote given by the user, we need no more
colors...

Wybo

I just committed some more wireing up and integration. The
new_logilogi.html is now integrated in the trunk :)

(hope we can work on the trunk now...)

Some bits may not have been copied over, especially regarding the
secondary tabs, as I did not know what to do with those...

I also made a start with hooking up remarks, but while doing that, and
really already when adding the commenting logis, I ran across the
naming of the bordered boxes, especially the different colored ones
(those that should be differently colored in line with the svg)...

Now most start with class="logi_current logi", and that may not be
neatest... Now I bet you already planned on changing that, but maybe
we should give all the boxes the same name, like border_box, or 
something, and then determine the color via the css, based on the div
they are in... (just like we do with the primary tabs)

(except maybe for the current logi, or the selected contender)

This would make the styling clean, and really separate from the
html (and allow putting the code needed for the box in a single
layout partial, just like app/views/application/round_box.html.erb 
for the rounded boxes)... 

So if you like it that way, you can do it...

---

I also did an attempt of fixing the min_height keeper in the current
logi, with an overflow: auto, but it required setting the width of the
logi_body manually... dunno if there is a better solution, as this one
also breaks the border of the current logi...

---

In all fixes I did I sticked closely to the SVG, and I am using
Firefox 3.0.1 on linux for it... Hope it is not too different from the
other Firefoxes...

greetings,

Wybo

PS: I might come online again late tonight if it's still early enough
:) I have a documentary and discussion-evening with friends tonight,
and it might get late... In any case I will be back tomorrow morning
for a good day of devving (but no more integration as changes to the
trunk from now on)...

First of all miguel, I hope you got ll to work on your OSX...
(tried to make up something of the chat-conversation, but I fear my
Spanish is too bad).

I just integrated the new_logilogi.html, that is largely. However
unless you have to work on windows or something and cannot run
logilogi, I think improvements should be made next time directly in
trunk, as the little extra work there saves a lot of hassling with
re-integrating stuff later on again... (1,5 hour spent now, and still
not entirely done).

Also this allows you to commit early and often, and me to do a fix
here and there, as now I basically have to wait for you to add / fix
things as we might be working on the same bits (& we don't really have
that time with the deadline of the 20th / 23rd & at the pace we're now
working...)...

Still some questions:
http://logilogi.svn.sourceforge.net/viewvc/logilogi/docs/ui-designs/html/new_logilogi.html?r1=1102&r2=1114

Around line 288 / 280 what did you do here ? As the secondary tabs are
not at all related to main, changes, etc, but to search, browse, etc
like in the old file.

---

#main #secondarytabs_main,
#logis #secondarytabs_logis,
#changes #secondarytabs_changes, #groups
#secondarytabs_groups,
#users #secondarytabs_users, #help #secondarytabs_help {

---

Around line 516 / 523 you renamed the secondary tabs to stuff like
secondarytabs_full_text_search, while in the trunk it is 
secondarytabs_search, as the tab-text is search there too...

Some bits still don't look equal, like the comment-logi having the
avatar above the title in the merged version, and some margin problem,
but I will fix it in the trunk and commit it in my next commit...

(& when committing the integration for the first time some small
things were also fixed, like absolute paths for images & I also now
renamed the sidebox-images in rounded to box, for consistency)

greetings,

Wybo

After some IRC-chatting I think we came to a much improved version.
The file can be found in the docs svn, named:
docs/ui-designs/UI_proposal_D_editing_wizzard_softblues.svg

> > Besides, I think that because of the width of the new logi wizzard we
> > cannot have it embedded at the bottom for remarks, so always have
> > commenting logis via this little wizzard. Also I think the eye-candy
> > idea of replacing the surroundings with the wizzard won't work for the
> > same reasons (and having just the logi in the middle to select a bit
> > from and then the commenting logi to add below is neater...), so it's
> > in the middle now...
> 
> First of all I like it, but I see some problems. Also I'm starting to
> enjoy this creative process we are all doing. We propose opposite

Indeed, the creative process is :)

> There ara two problems I see now with the new-logi overlaping the
> other. First the one that convinced me, as you said that you cannot
> read the rest of the logi, and I think this will be a problem.

Indeed...

> The other is that I don't like to move the log arround anymore.
> Although it's clear and it would work, I really liked the approach of
> keeping the logi static and moving things arround, it was kind of a
> strong concept. On the other hand, it would be nice to make a entire
> UI layout where the logi is at the center, but... not now the time to
> thing about that :)

Hm, indeed, so centered for wizzards might be a good middle-ground...

> Other potential problem I see is the comment, remark, link tabs being
> a bit out of sight. At first I think this tabs could be right on top
> of the wizzard, as this is the only part that would change when the
> tabs change, but this need to be thinked in global.

Indeed that was/is a good idea and move we made now...

> Those are the problems I see, but still, this is already a great
> approach and we have just to decide little problems.

:)

> > Idea is to have this new logi box also when editing a logi, but then
> > without the check.
> 
> I love the compact logi creation wizzard we'll have, and the tag
> addition, removal and verification is very neat :)

:)

Hope, u Miguel can make this and agree with it ?

At least now with the logi in the center, and the tabs for what to
insert below it the different modes (view, edit, insert) come out 
nicely :)

> We'll talk this at the #logilogi now :) Although with some problems,
> the overlaping option seems rasonable, and maybe it centered too, but
> I would like to meditate this a little bit more... not much :)

We did, & hopefully came to better results in your view too, Miguel...

greetings,

Wybo

PS: I was unable to do as much as I'd liked today, as there was still
some work left with the painting today to do for me. But now we're
done, and I'm in my student-room in Groningen again. The comming days
will be for me living undisturbed like a hermit & coding all day; to
get things done for the muniato project :)

(except for some evenings maybe, like tomorrow evening when I have the
documentary & discussion evening again...)

On Tue, Sep 16, 2008 at 8:13 AM, Wybo Wiersma <wy...@lo...> wrote:
> The new logi here overlaps, just like in Bruno's proposal, but I added
> a check for existing logis, and a little tabbed tool at the top for
> selecting wheither to add a logi, a link or a remark.
>
> Besides, I think that because of the width of the new logi wizzard we
> cannot have it embedded at the bottom for remarks, so always have
> commenting logis via this little wizzard. Also I think the eye-candy
> idea of replacing the surroundings with the wizzard won't work for the
> same reasons (and having just the logi in the middle to select a bit
> from and then the commenting logi to add below is neater...), so it's
> in the middle now...
>

First of all I like it, but I see some problems. Also I'm starting to
enjoy this creative process we are all doing. We propose opposite
things, and after that you start making tests with my proposal and I
start making with yours. I'm more convinced about the new-logi-editing
should be at the right now than at the middle. I already thought we
have it decided, but this las proposal has many variations, that would
go for the logi on the right side too.

There ara two problems I see now with the new-logi overlaping the
other. First the one that convinced me, as you said that you cannot
read the rest of the logi, and I think this will be a problem.
The other is that I don't like to move the log arround anymore.
Although it's clear and it would work, I really liked the approach of
keeping the logi static and moving things arround, it was kind of a
strong concept. On the other hand, it would be nice to make a entire
UI layout where the logi is at the center, but... not now the time to
thing about that :)

Other potential problem I see is the comment, remark, link tabs being
a bit out of sight. At first I think this tabs could be right on top
of the wizzard, as this is the only part that would change when the
tabs change, but this need to be thinked in global.

Those are the problems I see, but still, this is already a great
approach and we have just to decide little problems.

> Tags are added via an add-tag button, just like in the navigation/query-
> bar. This makes the check possible, and when in the tagg-add-textfield:
> - enter adds the just typed tag
> - backspace in the empty field removes the previous tag
> It is just as easy as a normal text-field with added advantage of easy
> checks and auto-completion for existing tags...
>
> Idea is to have this new logi box also when editing a logi, but then
> without the check.
>

I love the compact logi creation wizzard we'll have, and the tag
addition, removal and verification is very neat :)

> We might by the way consider having the new logi not overlapping, but
> going there via an anchor when selecting some bit of text. At least
> otherwise we must not make it disappear & lose all data when the user
> selects (or wants to select) a different snippet of text, as that
> would be hugely frustrating; selecting a bit, typing a whole logi,
> then wanting to add or remove a word in the selected snippet and
> losing all work...
>
it would be good to have some temp memory, drafts :)

> Hope we can move to a better wizzard in this way :)
>
> (maybe what we also could do is have the user to select a bit of text,
> then via anchor to the tabbed tool-thingy, which is now below the logi
> & then allow him to fill in the fields for the new one, but don't know
> about this...)
>

I didn't understand this well...


We'll talk this at the #logilogi now :) Although with some problems,
the overlaping option seems rasonable, and maybe it centered too, but
I would like to meditate this a little bit more... not much :)

greetings

-- 
Bruno

I just committed a - hopefully - improved version of the commenting
logi editing... The overlapping one.

The new logi here overlaps, just like in Bruno's proposal, but I added
a check for existing logis, and a little tabbed tool at the top for
selecting wheither to add a logi, a link or a remark.

Besides, I think that because of the width of the new logi wizzard we
cannot have it embedded at the bottom for remarks, so always have
commenting logis via this little wizzard. Also I think the eye-candy
idea of replacing the surroundings with the wizzard won't work for the
same reasons (and having just the logi in the middle to select a bit
from and then the commenting logi to add below is neater...), so it's
in the middle now...

Tags are added via an add-tag button, just like in the navigation/query-
bar. This makes the check possible, and when in the tagg-add-textfield:
- enter adds the just typed tag
- backspace in the empty field removes the previous tag
It is just as easy as a normal text-field with added advantage of easy
checks and auto-completion for existing tags...

Idea is to have this new logi box also when editing a logi, but then
without the check.

We might by the way consider having the new logi not overlapping, but
going there via an anchor when selecting some bit of text. At least
otherwise we must not make it disappear & lose all data when the user
selects (or wants to select) a different snippet of text, as that
would be hugely frustrating; selecting a bit, typing a whole logi,
then wanting to add or remove a word in the selected snippet and
losing all work...

Hope we can move to a better wizzard in this way :)

(maybe what we also could do is have the user to select a bit of text,
then via anchor to the tabbed tool-thingy, which is now below the logi
& then allow him to fill in the fields for the new one, but don't know
about this...)

Wybo

On Mon, Sep 15, 2008 at 12:43 PM, Wybo Wiersma <wy...@lo...> wrote:
> Still some small things to fix there too, but we're rolling :)
>
> (I did fix the page-width, and some small things)
>
> Bits of the page are now in the files that changed today. Especially a
> big chunk in app/views/logis/show.html.erb, but also in contenders,
> etc...
>
I'm checking out the trunk on this PC and moving them to my laptop and
hopefully running it there :)

> ---
>
> A question, why not DOCTYPE Strict ? As that normally gives less
> trouble & hacks in IE...
>
Well, I used the same template I'm using for other sites. I took it
from a django template I think, but if it works better in strict,
let's do it. I'm willing to make the html standards compilant, and
have those little friendly icons :)

greetings
-- 
Bruno

> Hi all,
> 
> I commited some modifications as talked yesterday with Wybo, so now
> the logitools works as spected. Still, coloring, fonts and others
> still need to be done, probably tomorrow.

Good work, overall, and with the changes you point out here (+ maybe
the tabs) it should look really good soon :)

I committed a first stage of integration, you can view it by visiting
http://logi-manta.org:3000/Logi_Logi on your local machine...

Still some small things to fix there too, but we're rolling :)

(I did fix the page-width, and some small things)

Bits of the page are now in the files that changed today. Especially a
big chunk in app/views/logis/show.html.erb, but also in contenders,
etc...

---

A question, why not DOCTYPE Strict ? As that normally gives less
trouble & hacks in IE...

Will do some more this evening,

Wybo

> Greetings.
> 
> -- 
> Bruno