Re: Updating WineWiki Theme?

2013-03-16 Thread Francois Gouget
On Fri, 15 Mar 2013, André Hentschel wrote:
[...]
> Please open bugs for them so they can be fixed later.

Done:

* Bug 33230 - The Wiki produces ugly tables
  http://bugs.winehq.org/show_bug.cgi?id=33230

* Bug 33231 - Wiki: Trouble sending notification emails
  http://bugs.winehq.org/show_bug.cgi?id=33231


-- 
Francois Gouget   http://fgouget.free.fr/
  145 = 1! + 4! + 5!


Re: Updating WineWiki Theme?

2013-03-15 Thread Kyle Auble
On Friday, March 15, 2013 7:45 PM, André Hentschel wrote:

> What i'd like is that you first upgrade the theme for now, whatever changes 
> it may need.
> For this task don't care about search fields, tables, sponsoring, ...
> The result should be a wine wiki with the same quality and/or bugs as we have 
> now, just with a new look.
> After that is pushed and running and you fixed remaining bugs with the new 
> look, you can then start fixing other bugs,
> changes things (keep in mind to talk to Jeremy Newman) and upgrade the wiki 
> software itself.

Sounds like a good plan. I've been testing the new theme with a v1.9
install of Moinmoin, but I should be able to create a branch and
backport that to v1.5 pretty easily.

After that, I can work on the tweaks and we can look into upgrading
the underlying software. Dimi mentioned that he has some
maintenance scripts written up, and I also have some on my
Bitbucket account so getting the tarball up again and converting
the data shouldn't take too long.

- Kyle




Re: Updating WineWiki Theme?

2013-03-15 Thread André Hentschel
Am 15.03.2013 04:17, schrieb Francois Gouget:
> * A default table is totally ugly: it has no border and no cell padding 
>   so it does not look like a table at all, just text appearing at random 
>   on the page. Here is an example:
>   http://wiki.winehq.org/FrancoisGouget
> 
> * During the preview the tables look nothing like after the preview. In 
>   fact they look good enough during the preview, it's only on the final 
>   page that they get ugly. This makes the preview totally useless as far 
>   as tables are concerned :-(
...
> Oh, and the Wiki seems to have trouble sending emails(*) so saving 
> changes is super slow. But that's probably not something you can do 
> anything about.

Please open bugs for them so they can be fixed later.

Am 14.03.2013 20:58, schrieb Kyle Auble:
> I did want to ask for input on a few things:
> 1. Should we just keep Moinmoin's search, replace it with the custom
>   Google search, or offer both?

For now keep it as it is.

> 2. How about the icon? I can get the standard WineHQ one to display
>   fine, but I'm not sure about which approach to take. Essentially, do
>   what's simplest for us, or should I make it play well with other
>   themes too?

The simplest approach sounds good :)

> 3. Finally, the credits are currently just text links. In the future
>   though, if Dimi wanted to, we could have a "sponsored by Lattica"
>   banner like the Codeweavers ones on the other pages.

Should not be a problem...

What i'd like is that you first upgrade the theme for now, whatever changes it 
may need.
For this task don't care about search fields, tables, sponsoring, ...
The result should be a wine wiki with the same quality and/or bugs as we have 
now, just with a new look.
After that is pushed and running and you fixed remaining bugs with the new 
look, you can then start fixing other bugs,
changes things (keep in mind to talk to Jeremy Newman) and upgrade the wiki 
software itself.

-- 

Best Regards, André Hentschel




Re: Updating WineWiki Theme?

2013-03-14 Thread Francois Gouget
On Thu, 14 Mar 2013, Kyle Auble wrote:
[...]
> I did want to ask for input on a few things:
[...]

Sorry, I don't have anything useful to contribute on these.

However since this is about the Wiki theming I'll mention a problem I 
ran into last week-end: tables. There are two problems with them:

* A default table is totally ugly: it has no border and no cell padding 
  so it does not look like a table at all, just text appearing at random 
  on the page. Here is an example:
  http://wiki.winehq.org/FrancoisGouget

* During the preview the tables look nothing like after the preview. In 
  fact they look good enough during the preview, it's only on the final 
  page that they get ugly. This makes the preview totally useless as far 
  as tables are concerned :-(

In the page I was working on I worked around this by specifying CSS 
styles for every single cell. The resulting wiki source code is pretty 
ugly but at least the result looks like tables.

http://wiki.winehq.org/WineTestBotVMs#hw_tables


Oh, and the Wiki seems to have trouble sending emails(*) so saving 
changes is super slow. But that's probably not something you can do 
anything about.



(*) I get:
Status of sending notification mails:
[en] fracting: Connection to mailserver 'mail.lattica.com' failed: (101, 
'Network is unreachable') 

-- 
Francois Gouget   http://fgouget.free.fr/
   RFC 2549: ftp://ftp.isi.edu/in-notes/rfc2549.txt
IP over Avian Carriers with Quality of Service




Updating WineWiki Theme?

2013-03-14 Thread Kyle Auble
Hi everybody,

Although my hiatus was longer than expected, I've been making progress
with updating the wiki code over the past few days (spring break is a
very good thing).

My workflow is a bit non-linear so I want to sort my changes into
patches first, but fingers-crossed, I'll be pushing them to my
Bitbucket account by the weekend.

I did want to ask for input on a few things:
1. Should we just keep Moinmoin's search, replace it with the custom
  Google search, or offer both?
2. How about the icon? I can get the standard WineHQ one to display
  fine, but I'm not sure about which approach to take. Essentially, do
  what's simplest for us, or should I make it play well with other
  themes too?
3. Finally, the credits are currently just text links. In the future
  though, if Dimi wanted to, we could have a "sponsored by Lattica"
  banner like the Codeweavers ones on the other pages.

After I get the theme together & test it some more on different
browsers, I can look into migrating the data to the newest Moinmoin
version.

-Kyle