[Yanel-dev] [Bug 7055] [wanted1.0+] offer at least 2 layouts for from-scratch realms

Guillaume Déflache guillaume.deflache at wyona.com
Fri Jun 26 08:18:27 CEST 2009


Hi!

Prabodh Upreti a écrit :
> [...]
>  >>As a second design I would suggest for simplicity/expendiency as none 
> of us are
>  >>UI designers that we just borrow Yulup's here: http://www.yulup.org/
>  
> I looked at the following page under yulup:  http://demo.yulup.org/ .  
> There are some simple straight forward pages under that link.  I hope 
> that is the sample you are talking about here.  That is great if it is 

I thought specifically of http://www.yulup.org/ where this bluish 
rounded-corners menu lies.

> ok to just grab one from there. My only question is if layout 1 has 
> navigation, muti-language support etc, do you think we need to have 
> something similar to that for layout 2.

Personally I think this design is nice because if has an horizontal 
navigation instead of a vertical one, which emphazizes can the layout is 
not set in stone.
So IMHO we should have navigation for both designs, and mabe also 
multi-language support if this is not too much additional work (if this 
leads to much duplication please don't bother but tell us about it) as 
we would already have all the content for the 1st layout anyway.


> For my part, I started tweaking around with the CSS and the XSL 
> file. Basically change background color, change font and move some items 
> around.  Problem is, it is not radically different from layout 1.  My 
> plan was to have a horizontal dhtml navigation but that is taking some 
> time. 

Sure, that's why I suggested Yulup's layout. Maybe we should replicate 
the menu bar in subpages (unlike Yulup), at least hiding the selected 
section. But again don't put too much time on it.


> Please advice me the best route to take here and I will do that.

See above.


>  >>For caching issues we should just make sure that both sets of 
> images/CSS are
>  >>accessed thru different URLs and all should be fine I guess.
> The only problem here is we are expecting 
> http://localhost:8080/yanel/from-scratch-realm/en/index.html  to server 
> layout 1 and 2 based on the earlier session setting.  If browser caching 
> is turned on link 
> http://localhost:8080/yanel/from-scratch-realm/en/index.html  may not 
> properly reflect the earlier requeset i.e. 
> http://localhost:8080/yanel/from-scratch-realm/en/index.html?xslt-version=1  
> .
>  
> Here I was just planning to not cache this content by adding <META 
> HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE" /> to the xsl.

That's okay. That should probably be Yanel's job to calculate the final 
document's Last-Modified/ETag given the generation process resources', 
which I suppose we do not do correctly/at all ATM. Maybe add a XXX here 
if you can make sure who should do the correct thing/what it should be.


> On a different note, do you think I should be sending this kind of 
> information via email or just adding it to bugzilla.  This will help me 
> in the future.

Generally speaking I'd say everything that could lead to discussions is 
better done thru E-mail, but both are fine if you cross-reference the 
thread with the bug.
For example design discussions should definitely be done on the 
mailing-list but non-far-reaching implementation issues are OK on the bug.
And for bugs that are defects and not features, well everything that 
brings us nearer to fixing it (as opposed to wishes and proposals of 
redesign/refactoring/any kind of reconsideration) should go in the bug.

Cheers,
    Guillaume


More information about the Yanel-development mailing list