IRC Archive for channel #xwiki

r4tune - (00:01): where is it writing "Recent changes" ?
r4tune - (00:02): i commented out the include recent changes document
r4tune - (00:02): but it still has the title
r4tune - (00:03): got it
r4tune - (00:03): heh
degro left #xwiki at 00:35
r4tune - (00:46): http://localhost:8080/xwiki/bin/view/XWiki/DefaultSkin?viewer=recyclebin
r4tune - (00:46): its broken
r4tune - (00:46): heh
r4tune - (00:51): xwiki is god
r4tune - (00:51): i don't need a window manager
r4tune - (00:51): just xwiki
r4tune - (00:58): $msg.get("xe.home.title")
r4tune - (00:59): where is this coming from
r4tune - (00:59): is there a WYS... way to edit it?
r4tune - (00:59): or should i just run a velocity script in a sandbox or something
r4tune - (00:59): xe.home.title value that is
r4tune - (01:10): edit inline form on main page doesn't edit anything
r4tune - (01:11): it shows the page rather than the source
bblfish joined #xwiki at 01:18
r4tune - (01:21): bblfish: hi
r4tune - (01:22): $msg.get("xe.home.title")
r4tune - (01:22): where are these properties kept
r4tune - (01:22): and how do you change them>
r4tune - (01:22): ?
sdumitriu - (01:23): r4tune: These are translated messages
sdumitriu - (01:23): The values are found in the server
r4tune - (01:23): is the a way to edit them without directly editing the db?
sdumitriu - (01:23): Inside webapps/xwiki/WEB-INF/xwiki-core-2.x.jar/ApplicationResources.properties
sdumitriu - (01:24): You can override them in a wiki document
r4tune - (01:25): so http://localhost:8080/xwiki/bin/webapps/xwiki/WEB-INF/xwiki-core-2.x.jar/ApplicationResources.properties
sdumitriu - (01:25): No, that's an URL
sdumitriu - (01:25): It's on the filesystem
r4tune - (01:25): aaaah
sdumitriu - (01:25): Inside a jar arhive
r4tune - (01:26): thanks
r4tune - (01:26): you know i never wanted to learn java
r4tune - (01:26): but i lm loving twiki so much
r4tune - (01:26): i might have to learn it...
r4tune - (01:26): xwiki
sdumitriu - (01:26): Wait
r4tune - (01:26): mea culpa
sdumitriu - (01:26): You don't have to edit the translations
r4tune - (01:26): i know
sdumitriu - (01:27): You can just remove that and replace it with plain text
r4tune - (01:27): now i know what it is i just won't use it as my title
r4tune - (01:27): yeah
r4tune - (01:27): but it is handy to know there might be properties i do want to changer
sdumitriu - (01:27): Just delete $msg.get, and write "This is so cool"
sdumitriu - (01:27): http://platform.xwiki.org/xwiki/bin/view/DevGuide/InternationalizingApplications
r4tune - (01:27): heh
r4tune - (01:27): i think it's going to mostly replace KWIN as my method of operation
r4tune - (01:28): since it has {{python{{
r4tune - (01:28): :D
sdumitriu - (01:28): Are you in USA?
r4tune - (01:28): uk
sdumitriu - (01:28): Oh
sdumitriu - (01:28): Then why are you up so late?
r4tune - (01:28): moving my stuff out of kbasket into xwiki
r4tune - (01:29): with the {{python}} I can have it do all sorts of cool stuff
r4tune - (01:29): it's like... an OS
r4tune - (01:30): :)
r4tune - (01:30): I'll publish my iT related notes on the web more as likely sometime too on xwiki
sdumitriu - (01:31): Well, most developers are up during the day, but mostly me and cjdelisle are up at night
sdumitriu - (01:32): So you're not likely to get answers so late
sdumitriu - (01:32): Sorry
r4tune - (01:42): hey it'm reading your api guide
r4tune - (01:42): and i don't know jack about java
r4tune - (01:42): but i know quite a few other languages
r4tune - (01:42): so it's not that challenging
r4tune - (01:42): i do have to change those properties too
r4tune - (01:43): or the "breadcrumb" still displays welcome to your wiki as the back links
r4tune - (02:01): doesn't xwiki be available to python?
r4tune - (02:01): nope it is
sdumitriu - (02:08): WDYM?
r4tune - (02:08): i must have made a typo i was trying to make my "Python" space list all the pages in it
r4tune - (02:08): but i done it now
r4tune - (02:08): http://pastebin.com/H1NMLLfv
sdumitriu - (02:10): nuvolari: Ping
r4tune - (02:34): damn
r4tune - (02:34): what's java doing
r4tune - (02:34): it's hit my ulimit
sdumitriu - (02:36): Which ulimit?
r4tune - (03:03): process
r4tune - (03:05): the anti (:(){ :|:& };:) one
sdumitriu - (03:08): Well, it shouldn't
sdumitriu - (03:09): It creates just one process
sdumitriu - (03:09): But with a lot of inner threads
sdumitriu - (03:09): Does ulimit also count threads?
sdumitriu - (03:09): I thought it only counted real processes
abusenius left at 03:26 (Ping timeout: 240 seconds
sdumitriu left at 03:27 (Ping timeout: 276 seconds
r4tune - (03:54): it does only count real process afaik
r4tune - (03:54): possibly it wasn't the process limit
r4tune - (03:54): but fork was failing
r4tune - (03:54): and killing proceses made it work
r4tune - (03:55): i've got 2 gig of ram and 12 gig of swap
r4tune - (03:55): so i don't know what else it could have been than process limit preventing the forking
r4tune - (04:10): can you put spaces in spaces?
r4tune - (04:11): like a tree structure
r4tune - (04:20): !search tree
venkatesh joined #xwiki at 04:37
florinciu left at 05:28 (Quit: Leaving.
florinciu joined #xwiki at 05:29
r4tune left at 05:44 (Remote host closed the connection
bblfish left at 05:58 (Ping timeout: 276 seconds
florinciu1 joined #xwiki at 06:26
florinciu left at 06:27 (Ping timeout: 245 seconds
mflorea joined #xwiki at 06:56
vmassol joined #xwiki at 07:51
Enygma` joined #xwiki at 07:56
vmassol left at 08:00 (Quit: Leaving.
tmortagne joined #xwiki at 08:30
silviar joined #xwiki at 08:34
silviar left at 08:50 (Ping timeout: 240 seconds
evalica joined #xwiki at 08:55
silviar joined #xwiki at 09:00
sburjan joined #xwiki at 09:03
asrfel joined #xwiki at 09:14
arkub joined #xwiki at 09:21
silviar left at 09:28 (Quit: Leaving.
silviar joined #xwiki at 09:28
sburjan_ joined #xwiki at 09:30
sburjan left at 09:31 (Read error: Operation timed out
jvdrean joined #xwiki at 09:31
silviar left at 09:33 (Ping timeout: 264 seconds
silviar joined #xwiki at 09:33
sdumitriu joined #xwiki at 09:43
sburjan_ - (09:43): hello sdumitriu
venkatesh left at 09:44 (Quit: Leaving
venkatesh joined #xwiki at 09:44
sdumitriu - (09:45): Hi sburjan
sburjan_ - (09:45): I've seen you fixed some bugs I reported
evalica1 joined #xwiki at 09:45
sdumitriu - (09:45): Yes
sburjan_ - (09:45): regarding the one about floating the Admin Page elements
sburjan_ - (09:45): the Open Office server breaks the design in some ways
sburjan_ - (09:46): let me show you a screenshot
sburjan_ - (09:47): http://imagebin.org/114838
evalica left at 09:47 (Ping timeout: 265 seconds
sburjan_ - (09:47): at least this is how my FF renders it on my resolution
sburjan_ - (09:50): don;t know how this could be fixed in order to keep the search where it is
sdumitriu - (09:53): I might have forgotten to commit a line, I'll check
sburjan_ is now known as sburjan ([email protected]
vmassol joined #xwiki at 10:01
sdumitriu - (10:03): Indeed, I forgot one line
lucaa joined #xwiki at 10:03
bblfish joined #xwiki at 10:03
sdumitriu - (10:06): sburjan: Should be fixed now, thanks for reporting
sburjan - (10:06): with pleasure
evalica1 left at 10:29 (Read error: Connection reset by peer
evalica joined #xwiki at 10:29
vmassol - (10:51): tmortagne: good morning
tmortagne - (10:51): vmassol: hi
vmassol - (10:51): do you remember the jira issue for specifying the query string and anchor as part of a link parameter?
vmassol - (10:51): (I can't find it but I'm pretty sure we had one)
vmassol - (10:52): (or maybe not)
tmortagne - (10:52): hmm not sure we have a jira issue specifically for it, it's possible it was part of the comments of another one
tmortagne - (10:53): let me check
sdumitriu - (10:53): Hi guys
sdumitriu - (10:54): How about using (* or ((* as a wiki comment syntax?
vmassol - (10:54): sdumitriu: you should comment on the jira issue
vmassol - (10:54): at one point I wanted something more generic
vmassol - (10:55): with semantic properties
vmassol - (10:55): entering meeting
tmortagne - (10:56): vmassol: can't find anything, i think we have nothing and was just suggested in some conversations
Enygma`1 joined #xwiki at 10:57
Enygma` left at 10:57 (Ping timeout: 240 seconds
Enygma` joined #xwiki at 11:00
vmassol - (11:00): tmortagne: ok
vmassol left at 11:01 (Quit: Leaving.
Enygma`2 joined #xwiki at 11:02
Enygma`1 left at 11:02 (Read error: No route to host
venkatna joined #xwiki at 11:04
sburjan - (11:04): sdumitriu, : could you fix the XWIKI-5433 before M2 release ?
lucaa left at 11:05 (Ping timeout: 276 seconds
Enygma` left at 11:05 (Ping timeout: 272 seconds
venkatesh left at 11:06 (Ping timeout: 255 seconds
venkatna left at 11:10 (Quit: Leaving
tmortagne - (11:21): i have lots of issues with redirect actions like save&view or login since csrf is in platform
tmortagne - (11:21): i get blanck pages with nothing in the log
jbrBridge left at 11:23 (Quit: jbrBridge
jbrBridge joined #xwiki at 11:23
tmortagne - (11:24): but the action itself works
tmortagne - (11:25): hmm actually wait i think it's a FF4 bug actually
tmortagne - (11:25): yep that's it sorry for that
tmortagne - (11:26): the last nightly build of FF does not seems to work very well
sdumitriu - (11:29): sburjan: Done XWIKI-5433
sburjan - (11:29): thanks
evalica left at 11:30 (Read error: Connection reset by peer
Enygma`2 left at 11:31 (Quit: Leaving.
Enygma` joined #xwiki at 11:31
evalica joined #xwiki at 11:31
sburjan - (11:32): sdumitriu, : these fixer are also committed for the 2.4.1 ?
venkatesh joined #xwiki at 11:35
Enygma` left at 11:56 (Quit: Leaving.
Enygma`1 joined #xwiki at 11:56
evalica1 joined #xwiki at 11:57
tmortagne - (11:58): cjdelisle: is it expected that we can't put any script in codeToExecute field of configurable obejcts ?
tmortagne - (11:58): objects
tmortagne - (11:58): currently it's impossible because of nested script protection
evalica left at 11:59 (Ping timeout: 276 seconds
cjdelisle - (11:59): codeToExecute is evaluated with velocity #evaluate
cjdelisle - (12:00): It wasn't expected that you'd be able to put groovy into it because that would require weeks of security review.
tmortagne - (12:00): cjdelisle: i'm nottalking about groovy
tmortagne - (12:00): this fielmd contains wiki syntax
tmortagne - (12:00): so i was expecting it to work like wiki syntax and used {{velocity}} macro in it
tmortagne - (12:01): it seems very wrong to me that it force velocity in it
cjdelisle - (12:02): Perhaps we could consider later on adding syntaxToRender
florinciu1 left at 12:02 (Quit: Leaving.
florinciu joined #xwiki at 12:03
sdumitriu - (12:06): sburjan: Only 2.5M2
cjdelisle - (12:06): re "wrong that it force velocity": That is how all of the fields work, they interpret as velocity so that the entry can be $msg.get...  That is a copy of what was used for document titles.
arkub left at 12:07 (Ping timeout: 255 seconds
tmortagne - (12:07): the other field are only velocity but this one also support wiki syntax
sburjan - (12:07): sdumitriu, : shouldn't we fix these minor stuff in 2.4.1 too ? I guess we'll have to release 2.4.1
tmortagne - (12:07): so there is a mix of two things
tmortagne - (12:08): wiki syntax also support inserting script
tmortagne - (12:08): it should have been done like wiki macros
cjdelisle - (12:09): "the other field are only velocity" no the velocity is placed into the document and thus rendered as syntax as well.
cjdelisle - (12:09): (except in the case of the document title.)
tmortagne - (12:09): since this field is supposed to be what you use when you need a custom admin page it should work like a page for me
cjdelisle - (12:11): It's not difficult to render text in that field but to change it's behavior would be an api break.
cjdelisle - (12:12): And it would mean we need to decide what exactly the test is for when to use velocity #evaluate and when to use $doc.getRenderedContent
tmortagne - (12:15): for me it's pretty simple, when it's wiki syntax it does note make sense to use #evaluate since it's not velocity content
cjdelisle - (12:17): So any time a value is pasted into the page, it should not use #evaluate.
tmortagne - (12:17): what you mean by "pasted into the page" ?
cjdelisle - (12:18): The title for example is taken from the title field, run through #evaluate and then it ends up in the page.
tmortagne - (12:18): it depends how you defined your field i don't see what the user action has do do with it
cjdelisle - (12:18): Thus the title is evaluated as velocity then rendered as syntax.
tmortagne - (12:19): no it's not
tmortagne - (12:19): templates does not support wiki syntax
tmortagne - (12:19): and the title is not inserted into document content but in the UI
cjdelisle - (12:20): Hmm. no not that title.
cjdelisle - (12:20): <property>
cjdelisle - (12:20): <heading>$msg.get('core.register.title')</heading>
cjdelisle - (12:20): </property>
cjdelisle - (12:20): ^^ from RegistrationConfig.xml
cjdelisle - (12:21): Configurable has a line somewhere which says:
tmortagne - (12:21): ok but again as i said it only depends how you defined your fields
tmortagne - (12:21): if it's wiki syntax it's wiki syntax
tmortagne - (12:21): if it's not supposed to be wiki syntax then you don't use it the right way
cjdelisle - (12:21): = $obj.get('heading') =
cjdelisle - (12:22): err no.
cjdelisle - (12:22): = #evaluate($obj.get('heading')) =
cjdelisle - (12:22): that's it.
tmortagne - (12:22): for me
tmortagne - (12:22): = #evaluate($obj.get('heading')) =
tmortagne - (12:22): does not make any sense
cjdelisle - (12:22): The heading property is evaluated as velocity.
tmortagne - (12:22): either you use #evaluate and you escape the result either you don't use it
cjdelisle - (12:23): Then it goes into the page content and is eaten by the renderer.
tmortagne - (12:23): if it's a title i don't see why you allow wiki syntax in it
cjdelisle - (12:23): How would I prevent it?
cjdelisle - (12:24): Here is the exact code:
cjdelisle - (12:24): #set($heading = $app.getValue('heading', $configurableObj))
cjdelisle - (12:24): #if($heading &amp;&amp; $heading != '')
cjdelisle - (12:24):   == #evaluate($heading) ==
cjdelisle - (12:24): #end
cjdelisle - (12:25): The only way I can see to avoid something being rendered as syntax is to wrap it in an {{html}} macro
tmortagne - (12:25): you can prevent it if you want to, i don't remember you proposing anything or even asking what to do for this use case, we already talked about that and there is ways to not interpret wiki syntax
cjdelisle - (12:26): oh yes, you could use {{{
cjdelisle - (12:26): (and hope the content didn't contain }}} )
tmortagne - (12:26): i already described several times ways to implements an escapeWiki tool
tmortagne - (12:27): it's very easy and it works whatever the content
cjdelisle - (12:27): It depends on whether the content is in a {{code}} mcaro, an {{html}} macro or an {{{ block.
cjdelisle - (12:28): You have different things to escape.
tmortagne - (12:28): i'm talking about wiki syntax excaping
tmortagne - (12:28): it depends on nothing
cjdelisle - (12:29): But it won't work for escaping content of a macro.
tmortagne - (12:29): if you are in {{code}} macro you don't want to escape wiki syntax you want to escape specifically {{/code}}
cjdelisle - (12:29): Thus you need one escape function per macro.
tmortagne - (12:29): and anyway know what you have around you here
tmortagne - (12:29): so i don't see what this have to do with your use case
cjdelisle - (12:30): The question was when do we evaluate velocity and when do we render syntax?
tmortagne - (12:30): and i already answer that question
cjdelisle - (12:30): Never velocity, always syntax.
cjdelisle - (12:31): correct?
tmortagne - (12:31): and it has nothing do do with where you do that
tmortagne - (12:31): whay would you interpret something that sos not velocity
tmortagne - (12:31): ?
florinciu left at 12:31 (Ping timeout: 245 seconds
tmortagne - (12:31): "Never velocity, always syntax." i never said that
tmortagne - (12:31): again what i said is: if it's wiki syntax then render syntax, if it's velocity then evaluate
cjdelisle - (12:31): Ok then not "Never velocity, always syntax."
tmortagne - (12:32): I really don't see the complexity
cjdelisle - (12:32): So you propose examining the content each time and trying to detect what to do?
tmortagne - (12:32): no i don't
tmortagne - (12:32): you know the content
tmortagne - (12:33): you are implementing configurable UI, you know what your object is containing
tmortagne - (12:33): also there is already types for it in object anyway
tmortagne - (12:33): look at the property definition
cjdelisle - (12:33): The content is whatever the implementer puts in the object. It's up to them to define it.
tmortagne - (12:33): it's indicated if it's wiki syntax, plain text...
tmortagne - (12:34): it's part of the class definition
tmortagne - (12:34): that's what the WYSIWYG is looking at for example
tmortagne - (12:34): to know it we should show it or let the field as plain text
cjdelisle - (12:34): A part which is not intrinsic to the class IMO but that's another matter.
cjdelisle - (12:35): Ok, so if we know the answer for all testArea props then what's the answer for string props?
tmortagne - (12:35): i don't agree with you, you define what is your object fields types and define if it's wiki syntaxe or something else is part of the content type
tmortagne - (12:36): IMO string props should not contains wiki syntax
tmortagne - (12:36): if you allows wiki syntax you allow a bigger content
tmortagne - (12:36): otherwise it's unusable
proyvind left at 12:36 (Ping timeout: 276 seconds
cjdelisle - (12:36): Ok, then we have a rule. "Text areas are defined by what they say, strings are always velocity and never syntax."
proyvind joined #xwiki at 12:37
abusenius joined #xwiki at 12:38
cjdelisle - (12:39): Would you like to deprecate codeToExecute and add syntaxToRender or similar?
tmortagne - (12:40): we could have codeToExecute and customContent maybe
tmortagne - (12:41): to make it more clear how it's supposed to be used
cjdelisle - (12:41): I'm happy with that.
tmortagne - (12:42): sometime you want to execute some velocity with the standard UI and sometime you want a custom UI so i think we should separate the two concepts
vmassol joined #xwiki at 12:52
vmassol left at 12:55 (Client Quit
lucaa joined #xwiki at 13:09
vmassol joined #xwiki at 13:09
lucaa left at 13:12 (Read error: No route to host
lucaa1 joined #xwiki at 13:12
lucaa1 left at 13:25 (Ping timeout: 265 seconds
cjdelisle - (13:35): Is there any reason why PR should be needed by edit*.vm?
sdumitriu - (13:36): None at all
cjdelisle - (13:37): I'll dropPermissions() for now, later we should have a "trusted boot" type system for ascending to PR when the document content begins rendering.
sburjan - (13:38): sdumitriu, : the issue with log4j is present in today's build too
sdumitriu - (13:38): sburjan: OK, I'll look
sdumitriu - (13:39): cjdelisle: inline edit might need PR
sdumitriu - (13:40): Since it does render the content
cjdelisle - (13:40): That makes sense. I'll leave inline.vm alone then.
evalica1 left at 13:46 (Read error: Connection reset by peer
evalica joined #xwiki at 13:48
evalica left at 13:51 (Read error: Connection reset by peer
evalica joined #xwiki at 13:52
sdumitriu - (13:55): nuvolari: Ping
arkub joined #xwiki at 14:03
venkatesh left at 14:13 (Ping timeout: 240 seconds
lucaa joined #xwiki at 14:54
vmassol - (14:57): tmortagne and others: so WDYT about moving query string and anchors for links to documents to link parameters? (e.g. [[label>>whatever?queryString#anchor]] to [[label>>whatever||queryString="…" anchor="…"]]. That's for XWiki syntax 2.1 of course? If some of us agree here I'll send a vote
sdumitriu - (14:58): +1
vmassol - (14:58): the advantage is to remove any need for escaping in links
sdumitriu - (14:58): Actually not quite
sdumitriu - (14:58): If I think better about it, it means custom meaning for some parameters
sdumitriu - (14:59): What does anchor mean for a mailto link?
vmassol - (14:59): the params could be valid only for a given link type
vmassol - (14:59): and be ignored for others
sdumitriu - (14:59): How do users enter that in the WYSIWYG? You really think that they know what a QS is?
vmassol - (14:59): I don't think we have to give meanings to these params for all cases
vmassol - (15:00): sdumitriu: well how do they do that now?
sdumitriu - (15:00): They just paste the full link
vmassol - (15:00): nope
sdumitriu - (15:00): Which they copied
vmassol - (15:00): we're talking about link to documents
vmassol - (15:00): not urls
sdumitriu - (15:00): Only to documents?
vmassol - (15:00): urls would stay urls
sdumitriu - (15:00): OK then
sdumitriu - (15:01): Let me rethink
vmassol - (15:01): the cons is that it's a little bit longer to type
vmassol - (15:01): than before
vmassol - (15:01): but it's more semantically correct I think
vmassol - (15:01): s/semantically/syntactically/
vmassol - (15:02): (less magic)
vmassol - (15:02): we could even group queryString and anchor together as extraData or something neutral like this
sdumitriu - (15:02): OK, +1
vmassol - (15:03): we probably need to fine tune it so I'll send a proposal mail
sdumitriu - (15:03): mflorea: Try to change the color theme to "Inner dark" and then use the WYSIWYG. Can you do something about it?
vmassol - (15:11): proposal sent
vmassol - (15:11): sdumitriu: I call them parameters rather than queryString, makes it less technical and less related to URL
vmassol - (15:11): s/call/called/
vmassol - (15:12): if someone can think of a better name, it's most welcome
vmassol - (15:12): first we need to decide if that's what we want
tmortagne - (15:15): vmassol: big +1
mflorea - (15:27): sdumitriu: are you referring to the background color of the rich text area? It is forced to white on purpose.
sdumitriu - (15:28): OK, but the text color should be forced as well
sdumitriu - (15:28): Since that way it's white text on white background
vmassol - (15:30): tmortagne/sdumitriu/others: please reply to the proposal mail re queryString/anchor. I'm ready to continue the work I've started but I need to know what we want to do, so I'm a bit blocked by this FTM.
vmassol - (15:30): thanks
tmortagne - (15:30): vmassol: that's what i'm currently doing ;)
vmassol - (15:30): cool
vmassol - (15:30): :)
mflorea - (15:31): sdumitriu: maybe the best option is to use the content background color and the content text color (I suppose they exist) from the current theme in the RichTextArea.css
sdumitriu - (15:35): I remember there was a discussion about this some time ago
sdumitriu - (15:35): Maybe it was before color themes were introduced, so this information was not available
mflorea - (15:36): yes, it was before, and we talked about separating the rules that affect only the content from the skin and to include only them in wysiwyginput.vm
sdumitriu - (15:37): I guess now you can use the color theme information
mflorea - (15:37): yes, I can
mflorea - (15:38): so there is a variable for content background color and content text color, right?
sdumitriu - (15:38): Yes
mflorea - (15:38): great
sdumitriu - (15:38): You have to add something like:
sdumitriu - (15:39): #template('colorThemeInit.vm')
sdumitriu - (15:39): And then you have:
sdumitriu - (15:39): $theme.pageContentBackgroundColor
sdumitriu - (15:39): $theme.textColor
mflorea - (15:41): cool, let me do this change
nuvolari - (15:45): sdumitriu: pong
sdumitriu - (15:46): Hi nuvolari
sdumitriu - (15:46): Remember http://jira.xwiki.org/jira/browse/XE-542 ?
abusenius left at 15:46 (Ping timeout: 272 seconds
nuvolari - (15:47): sdumitriu: hmm, was quite some time ago, but I recall a little bit
sdumitriu - (15:47): Well, the idea is that it's an issue which should be resolved by tweaking the httpd configuration
sdumitriu - (15:48): Do you still have that problem?
r4tune joined #xwiki at 15:52
r4tune - (15:52): !search todo
r4tune - (15:53): which one of those is the best?
nuvolari - (15:53): sdumitriu: I will have to doublecheck for you. I think it was with my personal setup. The office one is fine
asrfel left at 15:53 (Quit: Leaving.
tmortagne - (15:54): r4tune: depends what you search
r4tune - (15:54): I'm looking for a "to-do" list to put on it
tmortagne - (15:54): but pretty sure it's not http://www.xwiki.org/xwiki/bin/view/Macros/Todo which is a macro used in xwiki.org only and not a documentation
tmortagne - (15:55): http://code.xwiki.org/xwiki/bin/view/Macros/TodoMacro sounds like what you want then
r4tune - (15:55): thanks
tmortagne - (15:55): http://code.xwiki.org/xwiki/bin/view/Macros/ contains all the known XWiki macros
tmortagne - (15:55): could be http://code.xwiki.org/xwiki/bin/view/Applications/TodoApplicationDownloads too which is a bit older
tmortagne - (15:56): the same way http://code.xwiki.org/xwiki/bin/view/Macros/ contains macro, http://code.xwiki.org/xwiki/bin/view/Applications/ contains applications
r4tune - (15:57): what about this one: http://code.xwiki.org/xwiki/bin/view/Applications/ExtendedTodoApplicationDownloads
tmortagne - (15:58): r4tune: looks like another one yes (lot of theses applications are actually contributions from users everywhere so i really don't know them at all)
tmortagne - (15:58): note that the right page is http://code.xwiki.org/xwiki/bin/view/Applications/ExtendedTodoApplication
tmortagne - (15:59): http://code.xwiki.org/xwiki/bin/view/Applications/ExtendedTodoApplicationDownloads is just the download page
tmortagne - (15:59): but since the search here only show 5 results it's not always perfect
vmassol - (16:06): tmortagne: we use \ as the escape char for macro params right?
tmortagne - (16:07): vmassol: no we use ~ AFAIK since like for any wiki syntax
tmortagne - (16:07): s/since like/like/
cjdelisle - (16:07): I'll be /awayish for the rest of the day. Have a good one.
abusenius joined #xwiki at 16:14
lucaa left at 16:20 (Ping timeout: 245 seconds
silviar left at 16:28 (Read error: Connection reset by peer
abusenius left at 16:36 (Read error: Operation timed out
sburjan left at 16:37 (Ping timeout: 265 seconds
kwoot joined #xwiki at 16:51
kwoot - (16:53): so if I try to get a build environment and did a subversion checkout of trunk...
kwoot - (16:53): and i do a mvn clean install...
kwoot - (16:53): should i get an error: missing commons-net:commons-net:jar:2.1
kwoot - (16:53): when I can only find version 2.0 on the internet?
tmortagne - (17:02): kwoot: which version of XWiki are you trying to build ? 2.1 version is actually a bad version that has been wrongly put in maven repositories and then removed and we reverted to 2.0 in the current branch and trunks
tmortagne - (17:03): hmm maybe not in the branch actually
tmortagne - (17:03): i'm checking
tmortagne - (17:05): indeed 2.4-SNAPSHOT is still wrong
kwoot - (17:05): I would like to build the current development version. The 'living on the edge'  release :-)
tmortagne - (17:06): ho then you should not have any issue
tmortagne - (17:06): it's has been fixed for 2.4-SNAPSHOT
tmortagne - (17:06): 2.5 sorry
tmortagne - (17:06): 2.5-SNAPSHOT
kwoot - (17:06): maybe my checkout is wrong
tmortagne - (17:07): look at http://dev.xwiki.org/xwiki/bin/view/Community/SourceRepository
tmortagne - (17:08): you should co http://svn.xwiki.org/svnroot/xwiki/platform/trunks
tmortagne - (17:08): for the plaform part
tmortagne - (17:09): and http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk
tmortagne - (17:09): for XE
kwoot - (17:09): ok. doying both now in an empty dir.
tmortagne - (17:11): sdumitriu,vmassol : WDYT is the best idea ? creating a 33.1 version of the root pom ? applying XWIKI-5427 on 2.4 (that's the only modification incompatible with 2.4 branch)
tmortagne - (17:13): i you did not follow the conversation the issue is that XWIKI-5403 as been applying only on trunks
tmortagne - (17:14): but 2.4 branch has the same issue which makes it impossible to build
kwoot - (17:14): ok. thanks for the build hints. I have to go make supper for a kid and try the build later on after the download is finished. thanks.
kwoot - (17:17): hm. still the same error. well, I am going to make dinner and look later. till then.
sdumitriu - (17:18): tmortagne: I think it's safe to use 34 in 2.4
sdumitriu - (17:18): The only other change is de-listing the flickr plugin
sdumitriu - (17:19): But this setting is overwritten in enterprise-web pom, anyway
tmortagne - (17:19): indeed
tmortagne - (17:20): and i doubt anyone is using web-standard directly and even if one does there is probably even less people who care about this plugin
tmortagne - (17:20): changing 2.4 parent pom then
mflorea - (17:37): sdumitriu: I added the color theme velocity var to RichTextArea.css and now yuicompressor-maven-plugin fails to minify it. I see that some js and css files from web/standard are excluded in the yuicompressor-maven-plugin configuration because they contain velocity. Isn't there any workaround?
sdumitriu - (17:37): There should be
florinciu joined #xwiki at 17:39
evalica left at 17:53 (Read error: Connection reset by peer
evalica joined #xwiki at 17:54
r4tune left at 17:58 (Remote host closed the connection
sdumitriu - (18:02): mflorea: Can you paste the exact error you get when minifying that file?
sdumitriu - (18:03): Normally it should work, for example resources/uicomponents/search/search.css is correctly minified
mflorea - (18:03): sdumitriu: "java.lang.IllegalArgumentException: Illegal group reference" but I can avoid it by removing the {} (formal velocity reference notation)
abusenius joined #xwiki at 18:04
mflorea - (18:04): $!var works fine, $!{var} fails
tmortagne - (18:04): ha that was it, just seen this error on hudson
tmortagne - (18:04): (did not followed your conversation)
mflorea - (18:04): :)
sdumitriu - (18:04): mflorea: You don't need to be that careful when using the color theme
sdumitriu - (18:05): colorThemeInit makes sure that the returned values are always valid
mflorea - (18:05): ok
mflorea - (18:05): so just $var should be fine right?
sdumitriu - (18:05): Yes
mflorea - (18:05): ok, fixing RichTextArea.css
venkatesh joined #xwiki at 18:17
vmassol left at 18:22 (Quit: Leaving.
arkub left at 18:24 (Quit: Leaving
Enygma`1 left at 18:34 (Ping timeout: 240 seconds
tmortagne - (18:37): mflorea: WDYT about http://jira.xwiki.org/jira/browse/XWIKI-5496 ?
tmortagne - (18:37): should not be too hard to do for the rendering side
mflorea - (18:41): tmortagne: it would be great if the rendering would support it. Currently, on my side, I'm handling the content as any other macro parameter, and on the server side I set it's type to StringBuffer (I know.. :) ) just to differentiate between large strings and short strings. It should be really easy to change this to use the type provided by the rendering.
tmortagne - (18:46): ok good then, i will try think about something nice for it this week if i can find some time. The tricky thing for the WYSIWYG will be to take care or inline macro with XDOM content. It will have to do the same hack than all theses macros (we reeeely need inline parsers...)
mflorea - (18:48): what's exactly the problem with inline macro with XDOM content? by in-line you mean not standalone right?
mflorea - (18:48): or are you referring to nested macros
mflorea - (18:49): brb
tmortagne - (18:50): yes i mean not standalone
tmortagne - (18:51): that means the content itself is standalone
tmortagne - (18:51): i.e. any standalone element is forbidden
tmortagne - (18:51): s/is standalone/is inline/
evalica left at 18:52 (Quit: Leaving.
evalica joined #xwiki at 18:53
DrPoO joined #xwiki at 19:09
jvdrean left at 19:22 (Quit: Leaving.
lpereira joined #xwiki at 19:29
evalica left at 19:29 (Quit: Leaving.
evalica joined #xwiki at 19:30
venkatesh left at 19:42 (Ping timeout: 240 seconds
evalica left at 19:54 (Read error: Connection reset by peer
evalica joined #xwiki at 19:54
evalica1 joined #xwiki at 19:58
evalica left at 19:59 (Ping timeout: 255 seconds
evalica1 left at 20:23 (Quit: Leaving.
venkatesh joined #xwiki at 20:34
jvdrean joined #xwiki at 20:39
jvdrean left at 20:39 (Client Quit
degro joined #xwiki at 20:43
degro left at 20:44 (Client Quit
venkatesh left at 20:53 (Ping timeout: 252 seconds
r4tune joined #xwiki at 20:56
florinciu left at 20:59 (Quit: Leaving.
r4tune - (21:25): i tried to connect to your jabba thing but it didn't work
r4tune left at 21:30 (Remote host closed the connection
DrPoO left at 22:10 (Remote host closed the connection
lpereira left at 22:15 (Quit: Leaving.
r4tune joined #xwiki at 22:16
r4tune - (22:49): the job schedulers just a built in crontab right?
florinciu joined #xwiki at 22:59
sdumitriu - (23:10): r4tune: Yes, an inner crontab
r4tune - (23:21): 3 lines of paste ok?
r4tune - (23:21): ahh np i think i solved it
mflorea left at 23:22 (Quit: Leaving.
r4tune - (23:23): how do you guys who script it a lot go about it tho
r4tune - (23:23): cause im sitting in the sandbox and just keep editing and using preview
r4tune - (23:23): i bet you do something much more sensible
sdumitriu - (23:25): r4tune: There are tools that can help
sdumitriu - (23:25): 1: XEclipse, but it hasn't been very maintained lately
r4tune - (23:25): you mean like textaid
sdumitriu - (23:25): 2: WebDAV
r4tune - (23:25): so i can edit it in vim
r4tune - (23:25): webdav
r4tune - (23:25): that sounds good
sdumitriu - (23:26): 3: That Firefox extension that was mentioned
sdumitriu - (23:26): But yeah, WebDAV + vim should work
r4tune - (23:26): sorry if i end up making something cool and infest your java with {{python}} everywhere :P
sdumitriu - (23:26): Unfortunately, it's good only for the content of the page
sdumitriu - (23:26): It doesn't work for object properties
r4tune - (23:27): got a link/example of webdav+vim? i got the chome equivilent of that firefox extension but it's still too annoying
r4tune - (23:27): does it just support webdav access to content?
vmassol joined #xwiki at 23:30
sdumitriu - (23:30): I use it with kate
r4tune - (23:30): !search webdav
sdumitriu - (23:31): Just open webdav://localhost:8080/xwiki/webdav/ in konqueror or dolphin
r4tune - (23:31): kioslave
r4tune - (23:31): ill have to make a little proxy kate is ok but i'm a vim addict
sdumitriu - (23:33): Well, vim + webdav should really be a vim question
r4tune - (23:34): it works out of the box
r4tune - (23:35): i can just browse it in conquerer
r4tune - (23:35): and it provides a proxy to vim
r4tune - (23:35): leet
r4tune - (23:36): how do you get all the instances of a class?
r4tune - (23:36): i got the class
r4tune - (23:36): but can't see in the api how to get it's instances
vmassol left at 23:40 (Quit: Leaving.
sdumitriu - (23:42): $xwiki.searchDocuments(", BaseObject obj where obj.name=doc.fullName and obj.className = 'My.Class'")
sdumitriu - (23:42): Or use the query service
sdumitriu - (23:42): (I still have to learn how to use that one)
r4tune - (23:48): vim supports editing over webdav itself to it doesn't need the kioslave
r4tune - (23:48): thanks

{{/code}}