Re: [xwiki-users] [xwiki-devs] XWiki Logo Challenge, Round 2
IMO it's a bit too late to give -1 for a logo that passed the first round. Is it less readable now? 16 was voted by 11 community members (including myself) in the first round. Do we count less than people from outside the project? If we want a community-chosen logo then we should let the community choose. If we want a logo that is good for marketing then we should find a branding company to do it for us. Thanks, Marius I completely agree with Marius, I would also add that since this is a Community project, it should have a Community logo ! Since 16 has receive many votes now, and that I also agree with Vincent, Ludovic and others, it is not readable enough, I have made an alternative design: W-angle. My feeling was that the W is difficult to read, so my proposal try to keep the style and reworked it. There is also small changes in spacing, and a different powered by button. Here is almost all that was requested in a proposal with this variable: http://dev.xwiki.org/xwiki/bin/download/Community/LogoChallengeRound2/16%2Dwangle%2Ddefault.png I really hope that if the logo 16 is chosen, my proposal could help in mitigating the disappointment of those that really find it unacceptable. WDYT ? Denis -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [xwiki-devs] XWiki Logo Challenge, Round 2
On Apr 13, 2010, at 3:39 PM, Marius Dumitru Florea wrote: Hi all, Guillaume Lerouge wrote: Hi, On Tue, Apr 13, 2010 at 00:41, Ludovic Dubost ludo...@xwiki.com wrote: +1 for 4A and I'm at this point very -1 on 16 because of the W which has a missing arm.. I can't read XWiki in it.. I'd like to react about this: at this stage I share Ludovic's feeling. I had people from outside the project look at the 16 logo and they weren't able to read XWiki in it. I'm afraid that while stylistically interesting, this logo is too unreadable for mainstream use - unless we don't expect anyone to understand the XWiki logo that is. I'm feeling pretty close to giving it a -1 too if its readability isn't improved. I know I might be going against the flow here but we're about to make a significant choice here and I don't want us to regret it. Any thoughts? IMO it's a bit too late to give -1 for a logo that passed the first round. Is it less readable now? No but if you check none of us voted for it and there was no rule for giving -1 (I would have given it otherwise since I didn't like it in the first round. That said I was pretty sure nobody would vote for it when I saw it. I was wrong it seems ;)). BTW the problem of readability was raised even in the first round but not much was done about it (or I didn't see it). 16 was voted by 11 community members (including myself) in the first round. Do we count less than people from outside the project? If we want a community-chosen logo then we should let the community choose. If we want a logo that is good for marketing then we should find a branding company to do it for us. errr? We *definitely* want a logo that is good for marketing! That's the main point (the only point?) of having a logo. When users log into some website and see this logo we want them to know the site is using XWiki (if they can't read it, they won't even be able to google it if they like it and want to find more about this project). It seems you're opposing marketing and community. I don't know why. This is all about marketing. The whole xwiki.org is about marketing (i.e. make people want to use XWiki). Otherwise we'd just publish the sources with no documentation at all. Thanks -Vincent PS: I'm not saying that we should revote or remove that logo. I'm just giving a strong opinion that the logo is unreadable and is going to cause a lot of confusion. I would like to see that fixed if that logo is selected by the vote. Thanks, Marius Guillaume Ludovic Le 12/04/10 16:44, Sergiu Dumitriu a écrit : On 04/12/2010 04:30 PM, Thibaut Camberlin wrote: My corrected vote is +1 for 12A. 12A has been retired and is no longer a valid option. Please choose another one. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [xwiki-devs] XWiki Logo Challenge, Round 2
Readability is better, but for me upper right backgoing serif for w seems unnecessary. In place of (ascii art): \// \ /\\/\/iki only in this way: \/ /\\/\/iki Then X can be bigger and w can be aligned with k. What do you think? Valdis I completely agree with Marius, I would also add that since this is a Community project, it should have a Community logo ! Since 16 has receive many votes now, and that I also agree with Vincent, Ludovic and others, it is not readable enough, I have made an alternative design: W-angle. My feeling was that the W is difficult to read, so my proposal try to keep the style and reworked it. There is also small changes in spacing, and a different powered by button. Here is almost all that was requested in a proposal with this variable: http://dev.xwiki.org/xwiki/bin/download/Community/LogoChallengeRound2/16%2Dwangle%2Ddefault.png I really hope that if the logo 16 is chosen, my proposal could help in mitigating the disappointment of those that really find it unacceptable. WDYT ? Denis ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Quoting in macro calls
Hi,
I tried to call a macro passing a text which contains both, single and double
qoutes
{{macro para='this is Developer's Guide in german' /}}
{{macro para=this is Developer's Guide in german /}}
Both way fails because either quote or apostroph needs to be escaped.
I tried usual technics
- doubling: failed
- escaping with \ : failed
- escaping with \\ : failed strange. introduced a line break?
What is the right way to escape character?
Stefan Bachert
http://gwtworld.de
__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen
Massenmails.
http://mail.yahoo.com
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [xwiki-devs] XWiki Logo Challenge, Round 2
Hi all, How about this alternative: http://dev.xwiki.org/xwiki/bin/download/Community/LogoChallengeRound2/16-variation.png. I think that the W is readable now. Raluca. On Wed, Apr 14, 2010 at 11:06 AM, Valdis Vītoliņš valdis.vitol...@odo.lv wrote: Readability is better, but for me upper right backgoing serif for w seems unnecessary. In place of (ascii art): \// \ /\\/\/iki only in this way: \/ /\\/\/iki Then X can be bigger and w can be aligned with k. What do you think? Valdis I completely agree with Marius, I would also add that since this is a Community project, it should have a Community logo ! Since 16 has receive many votes now, and that I also agree with Vincent, Ludovic and others, it is not readable enough, I have made an alternative design: W-angle. My feeling was that the W is difficult to read, so my proposal try to keep the style and reworked it. There is also small changes in spacing, and a different powered by button. Here is almost all that was requested in a proposal with this variable: http://dev.xwiki.org/xwiki/bin/download/Community/LogoChallengeRound2/16%2Dwangle%2Ddefault.png I really hope that if the logo 16 is chosen, my proposal could help in mitigating the disappointment of those that really find it unacceptable. WDYT ? Denis ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Quoting in macro calls
On Wed, Apr 14, 2010 at 10:44, stefan bachert stefanbach...@yahoo.de wrote:
Hi,
I tried to call a macro passing a text which contains both, single and double
qoutes
{{macro para='this is Developer's Guide in german' /}}
{{macro para=this is Developer's Guide in german /}}
Both way fails because either quote or apostroph needs to be escaped.
I tried usual technics
- doubling: failed
- escaping with \ : failed
- escaping with \\ : failed strange. introduced a line break?
What is the right way to escape character?
Escaping character in xwiki/2.0 syntax is ~ and not backslash.
{{macro para='this is Developer~'s Guide in german' /}}
{{macro para=this is ~Developer's Guide~ in german /}}
Stefan Bachert
http://gwtworld.de
__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
gegen Massenmails.
http://mail.yahoo.com
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
--
Thomas Mortagne
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] TWiki Syntax HTML
Hi, On Tue, Apr 13, 2010 at 19:56, Meng Wu meng...@yahoo.com wrote: Hey all, The TWiki syntax doesn't seem to fully support HTML elements like pre, u, nop, and links (they aren't rendered at all or rendered incorrectly). However, basic syntax minus these tags such as verbatim, bullets, etc, work. Enabling these HTML elements is essential because we are migrating documents from the twiki and need them to be rendered correctly. We've added twiki 1.0 to the xwiki.cfg file and selected the syntax in the edit UI, but I read on the mailing list that the syntaxes aren't entirely implemented yet. So are html elements simply not supported yet, and if not, what do I need to do to enable them? TWiki parser is actually a Doxia (http://maven.apache.org/doxia/) parser. Here is what you can do to improve it: * improve existing parser: - finish/fix doxia bridge which convert doxia events into XWiki events . That basically mean finish http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwiki-rendering-syntaxes/xwiki-rendering-syntax-doxia/src/main/java/org/xwiki/rendering/internal/parser/doxia/XWikiGeneratorSink.java - report any bug not caused by the bridge but part of the real parser to Doxia guys (and eventually provide patch to them) * rewrite it in Wikimodel (http://code.google.com/p/wikimodel/) for which the bridge is complete * rewrite it with pure XWiki api (implementing org.xwiki.rendering.parser.StreamParser) Thanks, Felix ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users -- Thomas Mortagne ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [xwiki-devs] XWiki Logo Challenge, Round 2
I don't particularly like the recent alternative suggestions, the w is either getting unwieldy or too wide, losing its original impact, and I'd drop my +1 for it in those cases. To add my hack, what if: a) the X was made bigger and put behind the Wiki part b) the w was a full W (straighter, not spread out) c) the k was a full k (add the vertical line) ... then it might be more readable while still retaining a logo quality? I didn't vote for 4 because I agree with some others: a) the pencils do imply drawing more than collaborative writing; b) it seems to be lacking that professional logo quality. But maybe we're forcing something that shouldn't be forced. Could it be that *none* of the proposed logos fit what you're after, and we're just choosing from the best options presented? Trevor On Wed, 14 Apr 2010 11:58:54 +0300 Raluca Stavro wrote: Hi all, How about this alternative: http://dev.xwiki.org/xwiki/bin/download/Community/LogoChallengeRound2/16-variation.png. I think that the W is readable now. Raluca. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] getURL returns full URL with 'http://' prefix on a virtual site
When I address XWiki on a virtual site from outside the local net, the
function getURL returns a full string prefixed with 'http://'. If I work
from the local net with its true URL (http://server:8080/xwiki), this
function returns short URL beginning with '/xwiki/'.
As a result of this, the standard space control HTML code on the main page
is generated invalidly as velocity tries to convert textual URLs to links.
The same situation exists on several XWiki pages, e.g., Blog.
I studied the page source (/xwiki/bin/edit/Main/Spaces?editor=wiki) and
found the following:
##...
{{html wiki=true}}
##...
div class=spSpaceName[[${space}${space}.WebHome]]/div
div class=xshowonhover spSpaceActions
## Link to the space index.
$xwiki.getURL('Main.SpaceIndex', 'view',
$xwiki.getSkinFile('icons/silk/book_open.gif')
The first link is programmed with [[ ... ]], but the second link is
programmed directly as . In the second link, the getURL() producing
'http://' prefixed result blows the HTML code out.
The remedy was simple: {{html wiki=false}} and replace [[ ... ]] by . But
this exists on a lot of XWiki pages and should be corrected everywhere.
Why the getURL() gives different results depending on the way to access the
site? Is there a configuration parameter or any other method to correct
this.
On the xwiki.org site, the getURL obviously gives the necessary URL
beginning with '/xwiki'.
The problem exists on different XWiki versions (2.0 and later) on fresh
installations.
May be I should announce this as an error in XWiki sources to be corrected?
--
View this message in context:
http://n2.nabble.com/getURL-returns-full-URL-with-http-prefix-on-a-virtual-site-tp4902779p4902779.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Reverse proxy problems
Hi, I recently deployed XWiki Enterprise behind an Apache HTTP server acting as a reverse proxy. This was done in order to map the XWiki web interface into our intranet namespace and to perform SSL termination. To get this working, I had to resort to a few hacks and workarounds due to the fact that not all parts of XWIki Enterprise seem to be friendly towards reverse proxies. A workable solution was eventually achieved through config file changes and the addition of some Apache URL rewrite rules (e.g. redirect all requests for http://foo.com/xwiki/bar; to https://foo.com/xwiki/bar;). Today, I had to deploy another XWiki instance behind an Apache HTTP server, again for reasons of namespace consolidation and SSL termination. However, this time I do not have as much freedom as I had on the previous server and are finding myself stuck at this point. Examples of specific issues are that URLs of skin resources are served using the HTTP (i.e. insecure) protocol and some redirects are generated for the local address instead of the proxied address (e.g. login page from unauthorised and default post login redirect page). I'm not looking for particular solutions to these issues as much as trying to establish how likely I am to get this right and whether I'm trying to fit a square peg into a round hole. Specific questions as follows: 1. Did anyone manage to successfully deploy XWiki behind an HTTP reverse proxy without resorting to hacks and workarounds ? If so, please share some information about the magic configuration. Does the problem, perhaps, lie with Apache's reverse proxy module or its interaction with XWiki ? 2. Is my expectation to have XWiki working behind an HTTP reverse proxy misplaced ? If not, and XWiki does intend to support this, are the issues I describe above well known or should I report them somewhere ? Also, what can I do to help and contribute to such an effort ? 3. Are these issues due to the platform or the layers above it (e.g. skins and apps) ? Does the platform provide a right way that the layers above it can use to generate URLs that would always work correctly through a reverse proxy ? BTW, thanks for a great product! Regards, Gerhard -- Gerhard Esterhuizen Director Yila Consulting (Pty) Ltd PO Box 50461, Waterfront 8002, South Africa Phone: +27 82 370 9737 Fax: 086 549 5635 gerh...@yilaconsulting.com align. architect. execute. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] [xwiki-devs] XWiki Logo Challenge, Round 2
Trevor Russ wrote: I don't particularly like the recent alternative suggestions, the w is either getting unwieldy or too wide, losing its original impact, and I'd drop my +1 for it in those cases. To add my hack, what if: a) the X was made bigger and put behind the Wiki part b) the w was a full W (straighter, not spread out) c) the k was a full k (add the vertical line) ... then it might be more readable while still retaining a logo quality? I didn't vote for 4 because I agree with some others: a) the pencils do imply drawing more than collaborative writing; b) it seems to be lacking that professional logo quality. But maybe we're forcing something that shouldn't be forced. Could it be that *none* of the proposed logos fit what you're after, and we're just choosing from the best options presented? I'm looking at http://en.wikipedia.org/wiki/X and http://www.symbols.com/encyclopedia/09/index.html . There are some X representations which could have been the starting point for the XWiki logo (e.g. the Egyptian hieroglyph column, Phoenician S, Greek Xi, Braille or Morse code for X). I would have liked to see a logo proposal consisting of an easy to remember symbol that is not visually related to the latin X, even if it didn't had a lot of meaning. Thanks, Marius Trevor On Wed, 14 Apr 2010 11:58:54 +0300 Raluca Stavro wrote: Hi all, How about this alternative: http://dev.xwiki.org/xwiki/bin/download/Community/LogoChallengeRound2/16-variation.png. I think that the W is readable now. Raluca. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
