Re: Updating the wiki theme.
On Fri, Feb 20, 2015 at 11:18 AM, jan i j...@apache.org wrote: On 20 February 2015 at 13:16, Alexandro Colorado j...@oooes.org wrote: On Fri, Feb 20, 2015 at 4:48 AM, jan i j...@apache.org wrote: On 20 February 2015 at 01:46, Dennis E. Hamilton dennis.hamil...@acm.org wrote: +1 Nice idea and great attention to progressive staging. - Dennis -Original Message- From: acolor...@gmail.com [mailto:acolor...@gmail.com] On Behalf Of Alexandro Colorado Sent: Thursday, February 19, 2015 14:41 To: dev Subject: Updating the wiki theme. I would like to update the wiki theme to the one that we use on the homepage. ATM the wiki theme uses the very old OpenOffice.org, we are going 4-5 years in Apache and still have the same look and feel. I would like to get a new theme on the wiki for current style. Did you find the sources you need, otherwise drop me an email, and I will copy it to you directly. First step should be to 'create' a theme that can be hacked and tested. Then change it to the default by the wiki admin. The old wiki would still be available and enabled by users that preffer the old one, but new theme could become the default once reaching a functional style. I am not soo keen to have multiple themes active on our production wiki, I spent quite some time removing all other themes than the AOO one. Having multiple themes gives 2 problems: - a security problem, if we are not very careful (I will not detail this) - a graphic layout problem, it turns out our setup is very sensitive to small changes like another font, and some of the pages tilt when you do that. You should also be aware that in order to keep our current theme running, I needed to patch some of the core code of mediawiki, it would be nice if a new them could avoid that. I suggest you make yourself a test instance of mediawiki (I can provide what you need of setup info, incl. a dump of the SQL), develop your theme, once you have it, make a couple of screenshot and get acceptance in here. Once it is accepted I am happy to take it, verify it, and install it on the production system. Sounds like a plan to you ? Well that's an issue since like you specify this code is not 'generic' so I wont have details of what it needs to be applied to the production wiki. Well you do need a test installation anyway, where you test your code. I would rather access a snapshot, or a duplicated VM temporarily until the work is done. However the development would be done in a closed fashion which is not the ideal scenario. Infra cannot provide a temporary VM just for this purpose, making that would include DNS, LDAP, Puppet so at least the work of a little day. I can (as I already suggested) provide you a SQL dump. I can also dump the application, allthough it will most likely not run on your vm, due to dependencies of a number of other programs. May I suggest, that you make a naked installation of mediawiki somewhere, build the theme, and let me put it on production. There are basically no need to have our pretty complex production environment just to make a new theme. Last time I worked with the theme, I did it exactly like that. Also would be nice if you could detailed the most obvious pitfalls to know how to get around it. The reason why you need to change code is mainly because Monowiki theme also suffered version changes, and our original theme was based of an older version of the monowiki theme. This scenario is kind of unaviodable, unless is started from scratch. You might be right about the version changes, but I am not convinced, since I had the same problems when I tried to update the theme code. I cannot detail the pitfalls for 2 good reasons: - I have forgotten most of what I did (it is in svn) and why I did it - Most of the things I simply did with try-test methods, I tried at that time not to understand too much of why the theme was so mega complex. I think we would benefit from a clean theme based on the newest version. BTW I found this Changelog from the Wiki which I guess it needs to be updated/reviewed: https://wiki.openoffice.org/wiki/MediaWiki_Configuration rgds jan i. rgds jan i. Please comment. -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389
Re: Updating the wiki theme.
On 20 February 2015 at 01:46, Dennis E. Hamilton dennis.hamil...@acm.org wrote: +1 Nice idea and great attention to progressive staging. - Dennis -Original Message- From: acolor...@gmail.com [mailto:acolor...@gmail.com] On Behalf Of Alexandro Colorado Sent: Thursday, February 19, 2015 14:41 To: dev Subject: Updating the wiki theme. I would like to update the wiki theme to the one that we use on the homepage. ATM the wiki theme uses the very old OpenOffice.org, we are going 4-5 years in Apache and still have the same look and feel. I would like to get a new theme on the wiki for current style. Did you find the sources you need, otherwise drop me an email, and I will copy it to you directly. First step should be to 'create' a theme that can be hacked and tested. Then change it to the default by the wiki admin. The old wiki would still be available and enabled by users that preffer the old one, but new theme could become the default once reaching a functional style. I am not soo keen to have multiple themes active on our production wiki, I spent quite some time removing all other themes than the AOO one. Having multiple themes gives 2 problems: - a security problem, if we are not very careful (I will not detail this) - a graphic layout problem, it turns out our setup is very sensitive to small changes like another font, and some of the pages tilt when you do that. You should also be aware that in order to keep our current theme running, I needed to patch some of the core code of mediawiki, it would be nice if a new them could avoid that. I suggest you make yourself a test instance of mediawiki (I can provide what you need of setup info, incl. a dump of the SQL), develop your theme, once you have it, make a couple of screenshot and get acceptance in here. Once it is accepted I am happy to take it, verify it, and install it on the production system. Sounds like a plan to you ? rgds jan i. Please comment. -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Updating the wiki theme.
On Fri, Feb 20, 2015 at 4:48 AM, jan i j...@apache.org wrote: On 20 February 2015 at 01:46, Dennis E. Hamilton dennis.hamil...@acm.org wrote: +1 Nice idea and great attention to progressive staging. - Dennis -Original Message- From: acolor...@gmail.com [mailto:acolor...@gmail.com] On Behalf Of Alexandro Colorado Sent: Thursday, February 19, 2015 14:41 To: dev Subject: Updating the wiki theme. I would like to update the wiki theme to the one that we use on the homepage. ATM the wiki theme uses the very old OpenOffice.org, we are going 4-5 years in Apache and still have the same look and feel. I would like to get a new theme on the wiki for current style. Did you find the sources you need, otherwise drop me an email, and I will copy it to you directly. First step should be to 'create' a theme that can be hacked and tested. Then change it to the default by the wiki admin. The old wiki would still be available and enabled by users that preffer the old one, but new theme could become the default once reaching a functional style. I am not soo keen to have multiple themes active on our production wiki, I spent quite some time removing all other themes than the AOO one. Having multiple themes gives 2 problems: - a security problem, if we are not very careful (I will not detail this) - a graphic layout problem, it turns out our setup is very sensitive to small changes like another font, and some of the pages tilt when you do that. You should also be aware that in order to keep our current theme running, I needed to patch some of the core code of mediawiki, it would be nice if a new them could avoid that. I suggest you make yourself a test instance of mediawiki (I can provide what you need of setup info, incl. a dump of the SQL), develop your theme, once you have it, make a couple of screenshot and get acceptance in here. Once it is accepted I am happy to take it, verify it, and install it on the production system. Sounds like a plan to you ? Well that's an issue since like you specify this code is not 'generic' so I wont have details of what it needs to be applied to the production wiki. I would rather access a snapshot, or a duplicated VM temporarily until the work is done. However the development would be done in a closed fashion which is not the ideal scenario. Also would be nice if you could detailed the most obvious pitfalls to know how to get around it. The reason why you need to change code is mainly because Monowiki theme also suffered version changes, and our original theme was based of an older version of the monowiki theme. This scenario is kind of unaviodable, unless is started from scratch. rgds jan i. Please comment. -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614
Re: Updating the wiki theme.
I also like a common look feel. Thanks for suggesting and volunteering. Marcus Am 02/19/2015 11:41 PM, schrieb Alexandro Colorado: I would like to update the wiki theme to the one that we use on the homepage. ATM the wiki theme uses the very old OpenOffice.org, we are going 4-5 years in Apache and still have the same look and feel. I would like to get a new theme on the wiki for current style. First step should be to 'create' a theme that can be hacked and tested. Then change it to the default by the wiki admin. The old wiki would still be available and enabled by users that preffer the old one, but new theme could become the default once reaching a functional style. Please comment. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Updating the wiki theme.
On 20 February 2015 at 13:16, Alexandro Colorado j...@oooes.org wrote: On Fri, Feb 20, 2015 at 4:48 AM, jan i j...@apache.org wrote: On 20 February 2015 at 01:46, Dennis E. Hamilton dennis.hamil...@acm.org wrote: +1 Nice idea and great attention to progressive staging. - Dennis -Original Message- From: acolor...@gmail.com [mailto:acolor...@gmail.com] On Behalf Of Alexandro Colorado Sent: Thursday, February 19, 2015 14:41 To: dev Subject: Updating the wiki theme. I would like to update the wiki theme to the one that we use on the homepage. ATM the wiki theme uses the very old OpenOffice.org, we are going 4-5 years in Apache and still have the same look and feel. I would like to get a new theme on the wiki for current style. Did you find the sources you need, otherwise drop me an email, and I will copy it to you directly. First step should be to 'create' a theme that can be hacked and tested. Then change it to the default by the wiki admin. The old wiki would still be available and enabled by users that preffer the old one, but new theme could become the default once reaching a functional style. I am not soo keen to have multiple themes active on our production wiki, I spent quite some time removing all other themes than the AOO one. Having multiple themes gives 2 problems: - a security problem, if we are not very careful (I will not detail this) - a graphic layout problem, it turns out our setup is very sensitive to small changes like another font, and some of the pages tilt when you do that. You should also be aware that in order to keep our current theme running, I needed to patch some of the core code of mediawiki, it would be nice if a new them could avoid that. I suggest you make yourself a test instance of mediawiki (I can provide what you need of setup info, incl. a dump of the SQL), develop your theme, once you have it, make a couple of screenshot and get acceptance in here. Once it is accepted I am happy to take it, verify it, and install it on the production system. Sounds like a plan to you ? Well that's an issue since like you specify this code is not 'generic' so I wont have details of what it needs to be applied to the production wiki. Well you do need a test installation anyway, where you test your code. I would rather access a snapshot, or a duplicated VM temporarily until the work is done. However the development would be done in a closed fashion which is not the ideal scenario. Infra cannot provide a temporary VM just for this purpose, making that would include DNS, LDAP, Puppet so at least the work of a little day. I can (as I already suggested) provide you a SQL dump. I can also dump the application, allthough it will most likely not run on your vm, due to dependencies of a number of other programs. May I suggest, that you make a naked installation of mediawiki somewhere, build the theme, and let me put it on production. There are basically no need to have our pretty complex production environment just to make a new theme. Last time I worked with the theme, I did it exactly like that. Also would be nice if you could detailed the most obvious pitfalls to know how to get around it. The reason why you need to change code is mainly because Monowiki theme also suffered version changes, and our original theme was based of an older version of the monowiki theme. This scenario is kind of unaviodable, unless is started from scratch. You might be right about the version changes, but I am not convinced, since I had the same problems when I tried to update the theme code. I cannot detail the pitfalls for 2 good reasons: - I have forgotten most of what I did (it is in svn) and why I did it - Most of the things I simply did with try-test methods, I tried at that time not to understand too much of why the theme was so mega complex. I think we would benefit from a clean theme based on the newest version. rgds jan i. rgds jan i. Please comment. -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614
Updating the wiki theme.
I would like to update the wiki theme to the one that we use on the homepage. ATM the wiki theme uses the very old OpenOffice.org, we are going 4-5 years in Apache and still have the same look and feel. I would like to get a new theme on the wiki for current style. First step should be to 'create' a theme that can be hacked and tested. Then change it to the default by the wiki admin. The old wiki would still be available and enabled by users that preffer the old one, but new theme could become the default once reaching a functional style. Please comment. -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614
RE: Updating the wiki theme.
+1 Nice idea and great attention to progressive staging. - Dennis -Original Message- From: acolor...@gmail.com [mailto:acolor...@gmail.com] On Behalf Of Alexandro Colorado Sent: Thursday, February 19, 2015 14:41 To: dev Subject: Updating the wiki theme. I would like to update the wiki theme to the one that we use on the homepage. ATM the wiki theme uses the very old OpenOffice.org, we are going 4-5 years in Apache and still have the same look and feel. I would like to get a new theme on the wiki for current style. First step should be to 'create' a theme that can be hacked and tested. Then change it to the default by the wiki admin. The old wiki would still be available and enabled by users that preffer the old one, but new theme could become the default once reaching a functional style. Please comment. -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org