El Viernes, 14 de Agosto de 2009 06:40:43 Chris Morgan escribió: Guau! Great Work! I like it! Salu2 de jEsuSdA 8)

2009/8/14 Jarosław Foksa <jfoksa@...400...> Why exactly does drupalready.com need authentication? I would say it's like 30% done, a lot of stylings are missing. Hmm... in my opinion it looks too gimmicky. I like clean designs without images all over the place where they're not needed in my opinion (e.g. menus with different images for each item). TODO: Yes, sadly. I personally would do it without any of this as it's just extra clutter to no real benefit. - add SVG Web library (http://code.google.com/p/svgweb/) What would you use it for? In my theme I kept it simple and didn't include any SVG content partially for support, but mainly because I couldn't really justify it. Just because Inkscape is an SVG editor doesn't mean you've got to use SVG for everything on the website... that's a thought, we could have an entirely SVG interface... :P Thanks for providing competition though :-) -- Chris Morgan <chris.morganiser@...400...> I don't need a quote in my signature. It's hard enough surviving as it is without having to find a meaningful quote. Will you forgive me? Or don't you read this bit?

2009/8/14 Jarosław Foksa <jfoksa@...400...> I think that this would do it: User-Agent: * Disallow: / On 08/14/2009 09:56:45 AM, Chris Morgan wrote: I reckon that just scrapping the two-colour headings and menu images would fix it up a lot, but that's just my opinion. Others' should factor into it too. I reckon that in a few months' time, when Windows 7 is out, it will be reasonable to drop support for IE 6 (the only major thing being the PNG alpha filter fix). digg.com could probably drop support without causing any trouble because of their audience; youtube.com is the bigger player, and I reckon it's the one which will decide things more. Normally IE 6 support (or fairly nice degradation) isn't too hard. Good. I don't like gratuitous JavaScript, but there are definitely places where it's useful. Degradation - that's the key. svgweb uses Flash for it, which is going to have fairly high success rates, but it's still quite common to miss it. Unless you can come up with a good use for it, I vote to not use it. I would propose 25 August as a final deadline, after that we would I would propose that we don't place a deadline at all, much less a final deadline. Deadlines are incompatible with open source projects. Also it's necessary to set up at least basic content to see how a theme will work - for example primary links, navigation menu, search. It may be a good idea to request themes by a given date, but it won't work enforcing it. Content transferring can possibly also start before a final decision theme-wise, at inkscape.org. Tomorrow I'm expecting to be able to start work on a Drupal installation on inkscape.org. -- Chris Morgan <chris.morganiser@...400...> I don't need a quote in my signature. It's hard enough surviving as it is without having to find a meaningful quote. Will you forgive me? Or don't you read this bit?

On Fri, 2009-08-14 at 11:04 -0300, bulia byak wrote: Agreed. I have already mentioned to Chris about how we used to have the screenshots randomly show on the homepage. I do think that having this back again would be great in addition to your suggestion below. I think that the banner/header idea rocks. I would go ahead and initiate contact with a some DA users and line up a dozen or so images immediately so we can figure out the best format/look and be good for a year basically. Also, since we are in Feature Freeze and will not be seeing any more UI changes, I will be uploading the screenshots for 0.47 that I lined up over the weekend. Cheers, Josh

I also like the idea, but please no color switching. There is indeed a color switcher module for Drupal, but it may confuse visitors a lot, I don't know any major website that would change color scheme on regular basis. Besides, it would require us to update also Wiki theme (a lot of work) in order to keep it consistent with the homepage (we are not moving Wiki to Drupal, right?). My idea: lets put the image inside some kind of a box or frame, so that even if it has completely different color scheme it would stay consistent with the theme. Here is a sample (just started wokring on it): http://drupalready.com/uploads/2009-08-15-225307_1280x800_scrot.png What do you think? On Fri, Aug 14, 2009 at 4:04 PM, bulia byak<buliabyak@...400...> wrote:

Chris Morgan-10 wrote: Please don't... MediaWiki is the only wiki software I know that doesn't do silly things like AllLinksMustBeWikiWords, has tons of useful features, and almost everyone knows its syntax. Additionally, having a separate wiki allows us to cleanly separate the "official" information on the website from the "contributor area" on the wiki. While we're at it, I have some gripes with the current wiki CSS. Perhaps those problems could be fixed along with the site redesign. 1. The title of the page is not displayed at the top. It feels like something very important is missing. 2. The font is too small. The correct size is the same as on Wikipedia - it's both readable and small enough that a lot of text fits on a screen. 3. The header image at the top of content area takes up too much space, especially on small monitors or toolbar-heavy browsers. It should be hidden on the wiki, or put in the background. Regards, Krzysztof -- View this message in context: http://www.nabble.com/Inkscape-Website-tp24966252p25000186.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.

Chris Morgan-10 wrote: OK, I'm not going to be fundamentalist about it, I just want to know whether moving to Drupal won't degrade anything :) Here are the things that I find useful in Mediawiki: 1. Templates, including table row and table cell templates like used here: http://wiki.inkscape.org/wiki/index.php/GSoC2009_Node_Tool_Rewrite#Featur... 2. Page protection 3. Immutable revision history (so it's not possible to permanently delete anything unless you really want to) 4. Sometimes, reference support is handy, but it's not a must-have I think we'll need to use the Mediawiki API plugin you mentioned if we move to Drupal, because the wiki already contains some content which would be a pain to rewrite. Regards, Krzysztof -- View this message in context: http://www.nabble.com/Inkscape-Website-tp24966252p25008857.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2009/8/15 Jarosław Foksa <jfoksa@...400...>: We can use quite different framing options depending on the piece we're displaying, leaving only two things constant: the size and position of the page content block and the logo/name position. For example: - art like the "cup of tools" from our 0.47 About can be cropped only at the bottom, rising as a "sunset" over the content block but not reaching the top, blending into background on three sides; - art like http://12055.deviantart.com/art/Thinking-Of-Fun-115491184 could be cropped on both bottom and top, taking the entire strip between the content block and the window edge, blending into background on left and right sides; - an even more evenly spread, unfocused piece of art like http://zeh235.deviantart.com/art/inkscape-12267182 or http://rebirthart.deviantart.com/art/One-Day-in-Farm-47515219 could even "spill" down along the edges of the page content block, filling the entire top of page as a background. With this approach we don't need to change the color scheme of the content, but we might change the color of the background outside the content block to better blend it with the current piece. Integrating a piece into the site would requite not only cropping but, likely, opacity masking to fade out the edges, as well as probably some more disruptive changes (for example, http://rebirthart.deviantart.com/art/One-Day-in-Farm-47515219 would be nice to flip horizontally so that the Inkscape logo does not clash with the tree). -- bulia byak Inkscape. Draw Freely. http://www.inkscape.org