<span class="Apple-style-span" style="font-family: Arial, sans-serif; font-size: 13px; line-height: 19px; "><div><span class="Apple-style-span" style="font-family: Arial, sans-serif; font-size: 13px; line-height: 19px; ">If we are going to make significant changes to the wiki skin, it would probably serve us to base those on the pending default MediaWiki software and skin.</span></div> <div><span class="Apple-style-span" style="font-family: Arial, sans-serif; font-size: 13px; line-height: 19px; "><br></span></div>MediaWiki 1.16 beta has been announced, <a href="http://lists.wikimedia.org/pipermail/mediawiki-announce/2010-March/000089.html">http://lists.wikimedia.org/pipermail/mediawiki-announce/2010-March/000089.html</a>, with new features supporting skin changes. They also will be introducing features to support a new default skin, Vector, developed by the Wikimedia Usability Initiative, <a href="http://usability.wikimedia.org/wiki/Main_Page">http://usability.wikimedia.org/wiki/Main_Page</a>.</span><div> <span class="Apple-style-span" style="font-family: Arial, sans-serif; font-size: 13px; line-height: 19px; "> </span></div><div><span class="Apple-style-span" style="font-family: Arial, sans-serif; font-size: 13px; line-height: 19px; ">From the project blog, <a href="http://techblog.wikimedia.org/2010/01/babaco-enhancments/">http://techblog.wikimedia.org/2010/01/babaco-enhancments/</a>,</span><div> <font class="Apple-style-span" face="Arial, sans-serif"><span class="Apple-style-span" style="line-height: 19px;"><span class="Apple-style-span" style="font-size: 13px; "><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; "> Among the changes which have been made are many improvements in interactivity and aesthetics, but the most critical change is using an HTML iframe element together with a special design mode that modern browsers support, in favor of the previous HTML textarea. This paves the way for developing a rich editing experience with collapsible templates and syntax highlighting, as well as provides a foundation on which a WYSIWYG editor may eventually be built upon.</blockquote> <div><br></div><div> --Fred</div></span></span></font><br><div class="gmail_quote">On Sat, Mar 13, 2010 at 7:33 AM, Bernie Innocenti <span dir="ltr"><<a href="mailto:bernie@codewiz.org">bernie@codewiz.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Thu, 2010-03-11 at 19:00 -0700, Josh Williams wrote:<br> <br> > The content pane is set to a max width of 1020px and is fluid at smaller<br> > widths. You're suggesting it should be wider right? Could you attach a<br> > screen shot for both problems?<br> <br> </div>Here we go:<br> <br> <a href="http://wiki-devel.sugarlabs.org/go/Welcome_to_the_Sugar_Labs_wiki" target="_blank">http://wiki-devel.sugarlabs.org/go/Welcome_to_the_Sugar_Labs_wiki</a><br> <br> <br> Why do we need to limit the maximum horizontal size at all? If I like<br> the page to be laid out narrower, I can always resize the browser<br> window :-)<br> <br> Perhaps we need to set a minimum width below which the page starts<br> looking bad due to excessive wrapping. But hard-coded dimensions often<br> bother people with hand-held devices.<br> <br> Is there an easy way for web designers to check compatibility across<br> multiple browsers? I remember seeing a website that would take<br> screenshots of any url with multiple browsers. I forgot its name.<br> <div class="im"><br> <br> <br> > I haven't actually styled the tables yet. The tables will overflow<br> > horizontally on the live wiki now. You're only noticing this happen<br> > because the font size is larger forcing the overflow. I can make the<br> > font size smaller in the tables if you think the tables break at an<br> > unreasonable width.<br> <br> </div>That would be useful imho.<br> <div class="im"><br> <br> > > Note that I have a very high DPI display and therefore I configure my<br> > > browsers with bigger than normal fonts. Most sites survive this, but a<br> > > few break.<br> ><br> > I think a screen shot will help for this one too. Thanks for the feedback.<br> <br> </div>Please refer to the same screenshot I sent. It's not a Chromium specific<br> issue, the layout is similarly odd in Firefox.<br> <br> To reproduce it, go to the font settings and enlarge the default fonts.<br> <div class="im"><br> <br> > I'm contemplating removing the borders from the main content area. I've<br> > attached a screen shot of this. I think it's more inline with<br> > Christian's design for <a href="http://sugarlabs.org" target="_blank">sugarlabs.org</a> and it also avoids some rendering<br> > issues browse has with borders.<br> ><br> > Any input on this direction would be great.<br> <br> </div>I like it borderless! Like Frederick, I also feel that it would be good<br> to have some elements reminiscent of the Sugar UI, but only as long as<br> we can balance it with aesthetic needs. I met plenty of people who told<br> me that our old skin was awful.<br> <div><div></div><div class="h5"><br> --<br> // Bernie Innocenti - <a href="http://codewiz.org/" target="_blank">http://codewiz.org/</a><br> \X/ Sugar Labs - <a href="http://sugarlabs.org/" target="_blank">http://sugarlabs.org/</a><br> <br> </div></div></blockquote></div><br></div></div>