Search: concept

Thxs 09:20 <cjd> has joined #xwiki 09:20 <Ramona> has quit 09:28 <tmortagne> Pbas: you are passing the wrong context 09:28 <tmortagne> contex variable is a ScriptContext and the method expect a XWikiContext 09:28 <tmortagne> so that would be xcontext.context 09:29 <tmortagne> (xcontext binding is a public com.xpn.xwiki.api.Context and the method want the more protected XWikiContext) 09:29 <Pbas> Ok thxs I will give a try (I don't understand very well what is context in doc :-( ) 09:30 <tmortagne> not sure what you means by "context in doc" 09:30 <tmortagne> the method want the XWiki context because it's needed to manipulate the database 09:31 <Pbas> In a lot of method there are "protected XWikiContext context The current context, needed by the underlying protected object" but didn't found an explication what it is 09:31 <Pbas> perhaps a java concept? 09:32 <Pbas> or xwiki concept? 09:32 <tmortagne> it's the XWiki context as it's name indicate so yes a XWiki concept :) 09:32 <tmortagne> it contains things like current wiki, current user, etc. 09:32 <tmortagne> contextual information 09:32 <cjd> hehe the "context" is an object which follows you through the current http request/response cycle and then is deleted 09:32 <tmortagne> and among other things it's needed when you need to access the XWiki database 09:33 <cjd> I had no idea what it was either when I started with XWiki 09:34 <Pbas> It is an important things to use xwiki api but doc about this missing in my opinion 09:34 <tmortagne> in more public/script oriented APIs it's hidden but its still here 09:35 <tmortagne> API taking this XWikiContext are mostly old things which are replaced when we all the API related to document manipulation is a big jump 09:35 <cjd> Context objects are not only confined to XWiki, it's a design pattern in software dev, irronically this is the only link I can find about it... http://c2.com/cgi/wiki?

Thxs 09:20 <cjd> has joined #xwiki 09:20 <Ramona> has quit 09:28 <tmortagne> Pbas: you are passing the wrong context 09:28 <tmortagne> contex variable is a ScriptContext and the method expect a XWikiContext 09:28 <tmortagne> so that would be xcontext.context 09:29 <tmortagne> (xcontext binding is a public com.xpn.xwiki.api.Context and the method want the more protected XWikiContext) 09:29 <Pbas> Ok thxs I will give a try (I don't understand very well what is context in doc :-( ) 09:30 <tmortagne> not sure what you means by "context in doc" 09:30 <tmortagne> the method want the XWiki context because it's needed to manipulate the database 09:31 <Pbas> In a lot of method there are "protected XWikiContext context The current context, needed by the underlying protected object" but didn't found an explication what it is 09:31 <Pbas> perhaps a java concept? 09:32 <Pbas> or xwiki concept? 09:32 <tmortagne> it's the XWiki context as it's name indicate so yes a XWiki concept :) 09:32 <tmortagne> it contains things like current wiki, current user, etc. 09:32 <tmortagne> contextual information 09:32 <cjd> hehe the "context" is an object which follows you through the current http request/response cycle and then is deleted 09:32 <tmortagne> and among other things it's needed when you need to access the XWiki database 09:33 <cjd> I had no idea what it was either when I started with XWiki 09:34 <Pbas> It is an important things to use xwiki api but doc about this missing in my opinion 09:34 <tmortagne> in more public/script oriented APIs it's hidden but its still here 09:35 <tmortagne> API taking this XWikiContext are mostly old things which are replaced when we all the API related to document manipulation is a big jump 09:35 <cjd> Context objects are not only confined to XWiki, it's a design pattern in software dev, irronically this is the only link I can find about it... http://c2.com/cgi/wiki?

<sorinello> has quit 02:56 <sorinello> has quit 03:32 <sdumitriu> has quit 03:33 <sdumitriu> has joined #xwiki 06:00 <Denis1> has joined #xwiki 06:03 <Denis> has quit 07:03 <Ramona2> has joined #xwiki 08:09 <vmassol> has joined #xwiki 08:16 <msmeria> has joined #xwiki 08:24 <msmeria1> has joined #xwiki 08:25 <msmeria> has quit 08:37 <Ramona2> has quit 08:38 <msmeria> has joined #xwiki 08:38 <Ramona2> has joined #xwiki 08:40 <msmeria1> has quit 08:43 <msmeria> has quit 08:58 <KermitTheFragger> has joined #xwiki 09:03 <Ramona2> has quit 09:06 <msmeria> has joined #xwiki 09:07 <cjd_firewall> has joined #xwiki 09:16 <msmeria> has quit 09:23 <msmeria> has joined #xwiki 09:25 <gsmeria> has joined #xwiki 09:26 <tmortagne> has joined #xwiki 09:40 <gdelhumeau> has joined #xwiki 09:41 <msmeria1> has joined #xwiki 09:42 <msmeria> has quit 09:43 <woshilapin> has joined #xwiki 09:45 <gsmeria> has quit 09:46 <gsmeria> has joined #xwiki 09:48 <msmeria1> has quit 09:49 <msmeria> has joined #xwiki 10:13 <Ramona2> has joined #xwiki 10:15 <vmassol> gdelhumeau: it seems that commons/rendering 7.2 is not on maven central yet 10:16 <gdelhumeau> indeed I had troubles with that last week 10:16 <vmassol> good morning btw :) 10:16 <gdelhumeau> good morning :) 10:17 <Denis1> good morning 10:17 <Denis1> is now known as <Denis> 10:17 <gdelhumeau> gdelhumeau 10:17 <gdelhumeau> on sonatype: Last operation failed with 3 notifications 10:17 <gdelhumeau> Missing MD5: '/org/xwiki/commons/xwiki-commons-observation-local/7.2/xwiki-commons-observation-local-7.2-javadoc.jar.md5' 10:18 <Denis> I am having a first look at 7.2 release, and I am very puzzled by the fact that I cannot see the children of a inexistent WebHome, while at the same time I can administrer that inexistent page… seems we have blow up some concept too fast ! 10:20 <vmassol> IMO that's a mistake, we shouldn't be able to administer a non existing page 10:20 <vmassol> I don't see any issue of concept though 10:20 <vmassol> I'd create a jira issue for that 10:20 <Denis> you can administer it but not see children 10:20 <Denis> current creating the jira` 10:21 <gdelhumeau> I don't know 10:21 <Denis> that said, administration of and children of something that does not exists looks very odd for a final user 10:21 <gdelhumeau> the WebHome could not exist, but there could be some terminal pages 10:21 <vmassol> I agree that they should go together 10:21 <gdelhumeau> and since we don't have administer space, it make sense to administer... the non existent page 10:22 <vmassol> either they are allowed or they fordbidden for both of them 10:22 <gdelhumeau> from the core PoV 10:22 <gdelhumeau> from the user PoV, it's weird indeed 10:22 <vmassol> administer is ok IMO if the page rights is not shown 10:22 <vmassol> ie you can only administer children 10:22 <vmassol> well not even sure, need to think more :) 10:23 <vmassol> anyway I agree there's an issue and we need to decide 10:23 <Denis> XWIKI-12628 10:23 <Denis> but could be evolved as needed 10:24 <Denis> actually, we have a regression 10:26 <Denis> there is lots of weird situation with missing WebHome, including the fact that you can, (you need to) reach them (if you want to administer them) 10:26 <Denis> for the user PoV this is really weird and not pleasing 10:27 <vmassol> commented 10:32 <Denis> and replies 10:32 <gsmeria> has quit 10:33 <gsmeria> has joined #xwiki 10:34 <Denis> please, note that it is bad to have ML discussion in Jira issues, it seems to happen more and more, and so, let's create a ML thread about this !

<sorinello> has quit 02:56 <sorinello> has quit 03:32 <sdumitriu> has quit 03:33 <sdumitriu> has joined #xwiki 06:00 <Denis1> has joined #xwiki 06:03 <Denis> has quit 07:03 <Ramona2> has joined #xwiki 08:09 <vmassol> has joined #xwiki 08:16 <msmeria> has joined #xwiki 08:24 <msmeria1> has joined #xwiki 08:25 <msmeria> has quit 08:37 <Ramona2> has quit 08:38 <msmeria> has joined #xwiki 08:38 <Ramona2> has joined #xwiki 08:40 <msmeria1> has quit 08:43 <msmeria> has quit 08:58 <KermitTheFragger> has joined #xwiki 09:03 <Ramona2> has quit 09:06 <msmeria> has joined #xwiki 09:07 <cjd_firewall> has joined #xwiki 09:16 <msmeria> has quit 09:23 <msmeria> has joined #xwiki 09:25 <gsmeria> has joined #xwiki 09:26 <tmortagne> has joined #xwiki 09:40 <gdelhumeau> has joined #xwiki 09:41 <msmeria1> has joined #xwiki 09:42 <msmeria> has quit 09:43 <woshilapin> has joined #xwiki 09:45 <gsmeria> has quit 09:46 <gsmeria> has joined #xwiki 09:48 <msmeria1> has quit 09:49 <msmeria> has joined #xwiki 10:13 <Ramona2> has joined #xwiki 10:15 <vmassol> gdelhumeau: it seems that commons/rendering 7.2 is not on maven central yet 10:16 <gdelhumeau> indeed I had troubles with that last week 10:16 <vmassol> good morning btw :) 10:16 <gdelhumeau> good morning :) 10:17 <Denis1> good morning 10:17 <Denis1> is now known as <Denis> 10:17 <gdelhumeau> gdelhumeau 10:17 <gdelhumeau> on sonatype: Last operation failed with 3 notifications 10:17 <gdelhumeau> Missing MD5: '/org/xwiki/commons/xwiki-commons-observation-local/7.2/xwiki-commons-observation-local-7.2-javadoc.jar.md5' 10:18 <Denis> I am having a first look at 7.2 release, and I am very puzzled by the fact that I cannot see the children of a inexistent WebHome, while at the same time I can administrer that inexistent page… seems we have blow up some concept too fast ! 10:20 <vmassol> IMO that's a mistake, we shouldn't be able to administer a non existing page 10:20 <vmassol> I don't see any issue of concept though 10:20 <vmassol> I'd create a jira issue for that 10:20 <Denis> you can administer it but not see children 10:20 <Denis> current creating the jira` 10:21 <gdelhumeau> I don't know 10:21 <Denis> that said, administration of and children of something that does not exists looks very odd for a final user 10:21 <gdelhumeau> the WebHome could not exist, but there could be some terminal pages 10:21 <vmassol> I agree that they should go together 10:21 <gdelhumeau> and since we don't have administer space, it make sense to administer... the non existent page 10:22 <vmassol> either they are allowed or they fordbidden for both of them 10:22 <gdelhumeau> from the core PoV 10:22 <gdelhumeau> from the user PoV, it's weird indeed 10:22 <vmassol> administer is ok IMO if the page rights is not shown 10:22 <vmassol> ie you can only administer children 10:22 <vmassol> well not even sure, need to think more :) 10:23 <vmassol> anyway I agree there's an issue and we need to decide 10:23 <Denis> XWIKI-12628 10:23 <Denis> but could be evolved as needed 10:24 <Denis> actually, we have a regression 10:26 <Denis> there is lots of weird situation with missing WebHome, including the fact that you can, (you need to) reach them (if you want to administer them) 10:26 <Denis> for the user PoV this is really weird and not pleasing 10:27 <vmassol> commented 10:32 <Denis> and replies 10:32 <gsmeria> has quit 10:33 <gsmeria> has joined #xwiki 10:34 <Denis> please, note that it is bad to have ML discussion in Jira issues, it seems to happen more and more, and so, let's create a ML thread about this !

I actually could use the concept. 13:46 <vmassol> RodrigoXwiki: yes spaces are still there in the model 13:47 <vmassol> you should read this: 13:47 <vmassol> http://platform.xwiki.org/xwiki/bin/preview/Features/ContentOrganization 13:47 <vmassol> then if you still have questions then report them here as we'll need to improve that doc!

Foswiki also had the webs concept for this. 13:55 <vmassol> "how it translates to the interface now, there's many options".

14:10 <vmassol> ClemensR: sure but OTOH it would totally confuse everyone else 14:11 <vmassol> (since you'd need to explain the concept of spaces and how it's different from nested pages) 14:11 <ClemensR> yeah, I know, maybe name it "top level pages" ?

I actually could use the concept. 13:46 <vmassol> RodrigoXwiki: yes spaces are still there in the model 13:47 <vmassol> you should read this: 13:47 <vmassol> http://platform.xwiki.org/xwiki/bin/preview/Features/ContentOrganization 13:47 <vmassol> then if you still have questions then report them here as we'll need to improve that doc!

Foswiki also had the webs concept for this. 13:55 <vmassol> "how it translates to the interface now, there's many options".

14:10 <vmassol> ClemensR: sure but OTOH it would totally confuse everyone else 14:11 <vmassol> (since you'd need to explain the concept of spaces and how it's different from nested pages) 14:11 <ClemensR> yeah, I know, maybe name it "top level pages" ?

My translation bundle, from where I want to overwrite the key is probably loaded before so it doesn't have any effect. 10:53 <mflorea> I was thinking to "force" loading my translation bundle on demand, but it is also loaded on wiki, so it doesn't work (the location manager probably detects that the bundle is already loaded and doesn't do nothing). 10:54 <mflorea> my last resort is to define a separate bundle that contains only the key I want to overwrite and load this on demand in the places where the key is used 10:58 <tmortagne> TranslationBundle API have the concept of priority but all wiki based bundle provide the same priority, need to add a priority field in TranslationDocumentClass 11:00 <tmortagne> "it doesn't work" not sure what you means here 11:00 <tmortagne> you change from wiki to on demand and it's not taken into account ?

we can't specify a priority for a document translation bundle, at least not from the wiki page 11:07 <tmortagne> (10:58:47 AM) tmortagne: TranslationBundle API have the concept of priority but all wiki based bundle provide the same priority, need to add a priority field in TranslationDocumentClass 11:08 <mflorea> that would be nice 11:08 <mflorea> and would fit my use case 11:08 <tmortagne> yes, mostly forgot about it 11:08 <tmortagne> plus it's pretty easy to do 11:09 <tmortagne> if you want to look at it it's in AbstractDocumentTranslationBundle 11:09 <tmortagne> right now it does setPriority(DEFAULTPRIORITY_WIKI); but ideally it should look at the document first 11:09 <ImRG> has quit 11:09 <mflorea> ok, on my side I need it for procedure flavor, which is still depending on 8.4 so I can't use the latest version yet 11:10 <ImRG> has joined #xwiki 11:11 <tmortagne> creating a jira issue for it, looks like I forgot 11:14 <evalica> has joined #xwiki 11:18 <ImRG> has left #xwiki 11:31 <Enygma`> has joined #xwiki 11:32 <Enygma`1> has joined #xwiki 11:32 <Enygma`2> has joined #xwiki 11:36 <Enygma`> has quit 11:36 <mflorea> tmortagne: document translation bundles loaded on demand don't seem to have priority over those loaded on wiki.

My translation bundle, from where I want to overwrite the key is probably loaded before so it doesn't have any effect. 10:53 <mflorea> I was thinking to "force" loading my translation bundle on demand, but it is also loaded on wiki, so it doesn't work (the location manager probably detects that the bundle is already loaded and doesn't do nothing). 10:54 <mflorea> my last resort is to define a separate bundle that contains only the key I want to overwrite and load this on demand in the places where the key is used 10:58 <tmortagne> TranslationBundle API have the concept of priority but all wiki based bundle provide the same priority, need to add a priority field in TranslationDocumentClass 11:00 <tmortagne> "it doesn't work" not sure what you means here 11:00 <tmortagne> you change from wiki to on demand and it's not taken into account ?

we can't specify a priority for a document translation bundle, at least not from the wiki page 11:07 <tmortagne> (10:58:47 AM) tmortagne: TranslationBundle API have the concept of priority but all wiki based bundle provide the same priority, need to add a priority field in TranslationDocumentClass 11:08 <mflorea> that would be nice 11:08 <mflorea> and would fit my use case 11:08 <tmortagne> yes, mostly forgot about it 11:08 <tmortagne> plus it's pretty easy to do 11:09 <tmortagne> if you want to look at it it's in AbstractDocumentTranslationBundle 11:09 <tmortagne> right now it does setPriority(DEFAULTPRIORITY_WIKI); but ideally it should look at the document first 11:09 <ImRG> has quit 11:09 <mflorea> ok, on my side I need it for procedure flavor, which is still depending on 8.4 so I can't use the latest version yet 11:10 <ImRG> has joined #xwiki 11:11 <tmortagne> creating a jira issue for it, looks like I forgot 11:14 <evalica> has joined #xwiki 11:18 <ImRG> has left #xwiki 11:31 <Enygma`> has joined #xwiki 11:32 <Enygma`1> has joined #xwiki 11:32 <Enygma`2> has joined #xwiki 11:36 <Enygma`> has quit 11:36 <mflorea> tmortagne: document translation bundles loaded on demand don't seem to have priority over those loaded on wiki.

<vmassol> has quit 01:13 <abusenius_> has joined #xwiki 01:14 <MasterPiece> has quit 01:16 <MasterPiece> has joined #xwiki 01:16 <MasterPiece> has quit 01:16 <MasterPiece> has joined #xwiki 02:42 <abusenius_> has quit 02:59 <daemoen> has joined #xwiki 02:59 <daemoen> good, there are some folkss here :) 03:34 <cjd> has quit 03:38 <daemoen> did 7.* replace the concept of spaces with 'subwikis' ? I can't find how and where to set spaces at all. 03:44 <cjd> has joined #xwiki 03:48 <daemoen> lo cjd 03:52 <cjd> hi 03:54 <daemoen> Is there updated documentation for how to administer 7.4.1 ?

<vmassol> has quit 01:13 <abusenius_> has joined #xwiki 01:14 <MasterPiece> has quit 01:16 <MasterPiece> has joined #xwiki 01:16 <MasterPiece> has quit 01:16 <MasterPiece> has joined #xwiki 02:42 <abusenius_> has quit 02:59 <daemoen> has joined #xwiki 02:59 <daemoen> good, there are some folkss here :) 03:34 <cjd> has quit 03:38 <daemoen> did 7.* replace the concept of spaces with 'subwikis' ? I can't find how and where to set spaces at all. 03:44 <cjd> has joined #xwiki 03:48 <daemoen> lo cjd 03:52 <cjd> hi 03:54 <daemoen> Is there updated documentation for how to administer 7.4.1 ?

12:12 <tmortagne> the name of the thing you were referencing 12:13 <tmortagne> but this is related to what is configured in each page as it's parent 12:13 <tmortagne> so it's depends a lot on what the page configuration 12:13 <tmortagne> the top menu alway lead you to the main page of each element 12:13 <tmortagne> (at least in the default skin) 12:14 <altker1281> I am using the default skin. 12:15 <tmortagne> vmassol: still the "Could not find artifact org.xwiki.platform:xwiki-platform-tool-jetty:pom:5.0.3-SNAPSHOT" according to the log 12:16 <altker1281> I think Foswiki does a bit better job with their 'Breadcrumb' concept. Their left bar is equivalent to the XWiki "Dashboard". 12:19 <tmortagne> vmassol: sounds like packager plugin only look at local repository and it does not trigger a dependency on xwiki-platform-tool-jetty 12:19 <tmortagne> at least this artifact is not in the maven local repository 12:22 <altker1281> xwiki does a much better job with user administration and contorl 12:22 <altker1281> control 12:26 <vmassol> tmortagne: yes this is why I was thinking we were missing a dep in the pom 12:26 <altker1281> tmortagne, vmassol : Thank you again both for your help. 12:26 <vmassol> but I can't reproduce it locally 12:26 <vmassol> (with a cleaned local repo) 12:26 <vmassol> altker1281: if you have a link to foswiki's breadcrumb concept that would help 12:26 <tmortagne> vmassol: I guess the build is not always done in the exact same order 12:27 <altker1281> vmassol: 12:28 <altker1281> vmassol: http://foswiki.org/Sandbox/WebHome 12:28 <tmortagne> vmassol: actually I think it's different 12:28 <vmassol> tmortagne: putting a9 offline to debug it on the agent 12:28 <tmortagne> not that simple I mean 12:28 <altker1281> vmassol: You can see the "You are here: Foswiki > Sandbox Web > WebHome (date)" 12:28 <vmassol> altker1281: that's the same concept as xwiki, no?

12:30 <vmassol> yes 12:31 <altker1281> Yeah. Now I get the concept, but before I kept on trying to go the drop downs at the top (WIKI, SPACE) 12:31 <altker1281> I think the breadcrumb should appear above the outside that has "Export" and "More Actions" 12:32 <vmassol> would be interesting that at some point you send us an email on the user lists to provide some ideas for improvements 12:32 <vmassol> that helps us a lot 12:32 <vmassol> (altker1281) 12:32 <altker1281> Will do!

12:12 <tmortagne> the name of the thing you were referencing 12:13 <tmortagne> but this is related to what is configured in each page as it's parent 12:13 <tmortagne> so it's depends a lot on what the page configuration 12:13 <tmortagne> the top menu alway lead you to the main page of each element 12:13 <tmortagne> (at least in the default skin) 12:14 <altker1281> I am using the default skin. 12:15 <tmortagne> vmassol: still the "Could not find artifact org.xwiki.platform:xwiki-platform-tool-jetty:pom:5.0.3-SNAPSHOT" according to the log 12:16 <altker1281> I think Foswiki does a bit better job with their 'Breadcrumb' concept. Their left bar is equivalent to the XWiki "Dashboard". 12:19 <tmortagne> vmassol: sounds like packager plugin only look at local repository and it does not trigger a dependency on xwiki-platform-tool-jetty 12:19 <tmortagne> at least this artifact is not in the maven local repository 12:22 <altker1281> xwiki does a much better job with user administration and contorl 12:22 <altker1281> control 12:26 <vmassol> tmortagne: yes this is why I was thinking we were missing a dep in the pom 12:26 <altker1281> tmortagne, vmassol : Thank you again both for your help. 12:26 <vmassol> but I can't reproduce it locally 12:26 <vmassol> (with a cleaned local repo) 12:26 <vmassol> altker1281: if you have a link to foswiki's breadcrumb concept that would help 12:26 <tmortagne> vmassol: I guess the build is not always done in the exact same order 12:27 <altker1281> vmassol: 12:28 <altker1281> vmassol: http://foswiki.org/Sandbox/WebHome 12:28 <tmortagne> vmassol: actually I think it's different 12:28 <vmassol> tmortagne: putting a9 offline to debug it on the agent 12:28 <tmortagne> not that simple I mean 12:28 <altker1281> vmassol: You can see the "You are here: Foswiki > Sandbox Web > WebHome (date)" 12:28 <vmassol> altker1281: that's the same concept as xwiki, no?

12:30 <vmassol> yes 12:31 <altker1281> Yeah. Now I get the concept, but before I kept on trying to go the drop downs at the top (WIKI, SPACE) 12:31 <altker1281> I think the breadcrumb should appear above the outside that has "Export" and "More Actions" 12:32 <vmassol> would be interesting that at some point you send us an email on the user lists to provide some ideas for improvements 12:32 <vmassol> that helps us a lot 12:32 <vmassol> (altker1281) 12:32 <altker1281> Will do!

:)) 13:44 <evalica> k - I'll read it 13:44 <vmassol> the only downside, is that we're starting to need even more a UI for managing versions 13:45 <tmortagne> vmassol: this field does not exist in XWiki Repository, it's a extensions.xwiki.org customization 13:45 <evalica> I will never go out of business with this UI field :) 13:45 <tmortagne> so XWIKI-9642 is not really true 13:45 <vmassol> evalica: until we invent direct brain to brain communication ;) 13:46 <vmassol> tmortagne: ok 13:46 <vmassol> thanks 13:46 <vmassol> too bad that this concept of ExtensionVersionClass doesn't exist in platform 13:46 <vmassol> (platform = XWiki Repository app) 13:47 <vmassol> any reason why?

14:04 <vmassol> or if some title is badly displayed 14:05 <vmassol> the alternative is to remove the concept of "works or not" and just keep the notes field 14:05 <tmortagne> well it's not that simple, if you have an extension working since a specific version you might end up with a very bad grade because someone put 0 for a previous version 14:06 <tmortagne> it depends what we really want to display here 14:06 <vmassol> for ex on http://extensions.xwiki.org/xwiki/bin/view/Extension/Sequence+Diagram+Macro we have a green tick 14:07 <vmassol> to indicate it "works" iwth XE 6.0.1 14:07 <vmassol> but the concept is fuzzy 14:07 <tmortagne> yes but this field is usally here to indicate since when you can use that extension 14:07 <vmassol> I think what we want to show is for a user who wants to install this extensiosn whether he'll have some surprise or not 14:07 <tmortagne> it was not really meant to indicate you if it's good 14:07 <vmassol> what's the point of testing then?

:)) 13:44 <evalica> k - I'll read it 13:44 <vmassol> the only downside, is that we're starting to need even more a UI for managing versions 13:45 <tmortagne> vmassol: this field does not exist in XWiki Repository, it's a extensions.xwiki.org customization 13:45 <evalica> I will never go out of business with this UI field :) 13:45 <tmortagne> so XWIKI-9642 is not really true 13:45 <vmassol> evalica: until we invent direct brain to brain communication ;) 13:46 <vmassol> tmortagne: ok 13:46 <vmassol> thanks 13:46 <vmassol> too bad that this concept of ExtensionVersionClass doesn't exist in platform 13:46 <vmassol> (platform = XWiki Repository app) 13:47 <vmassol> any reason why?

14:04 <vmassol> or if some title is badly displayed 14:05 <vmassol> the alternative is to remove the concept of "works or not" and just keep the notes field 14:05 <tmortagne> well it's not that simple, if you have an extension working since a specific version you might end up with a very bad grade because someone put 0 for a previous version 14:06 <tmortagne> it depends what we really want to display here 14:06 <vmassol> for ex on http://extensions.xwiki.org/xwiki/bin/view/Extension/Sequence+Diagram+Macro we have a green tick 14:07 <vmassol> to indicate it "works" iwth XE 6.0.1 14:07 <vmassol> but the concept is fuzzy 14:07 <tmortagne> yes but this field is usally here to indicate since when you can use that extension 14:07 <vmassol> I think what we want to show is for a user who wants to install this extensiosn whether he'll have some surprise or not 14:07 <tmortagne> it was not really meant to indicate you if it's good 14:07 <vmassol> what's the point of testing then?

<sdumitriu> has quit 01:03 <sdumitriu> has joined #xwiki 01:12 <sdumitriu> has quit 01:15 <sdumitriu> has joined #xwiki 02:32 <Denis> has quit 04:30 <Denis> has joined #xwiki 04:55 <polx> has quit 05:02 <polx> has joined #xwiki 05:51 <Denis> has quit 07:24 <polx> has quit 07:47 <polx> has joined #xwiki 07:48 <msmeria> has joined #xwiki 08:02 <evalica> has joined #xwiki 08:21 <evalica> has quit 08:22 <evalica> has joined #xwiki 08:23 <sburjan> has joined #xwiki 08:36 <polx> has quit 08:37 <polx> has joined #xwiki 08:38 <polx> has quit 08:51 <vmassol> has joined #xwiki 08:54 <Denis> has joined #xwiki 08:59 <polx> has joined #xwiki 09:02 <polx> has quit 09:07 <polx> has joined #xwiki 09:26 <polx> has quit 09:26 <polx> has joined #xwiki 09:31 <polx> has quit 09:41 <polx> has joined #xwiki 10:01 <gdelhumeau> has joined #xwiki 10:11 <vmassol> good morning 10:11 <vmassol> I'm starting to have a bit too many stashes… https://gist.github.com/vmassol/6410379 10:14 <camil7> has joined #xwiki 10:16 <KermitTheFragger> has joined #xwiki 11:19 <Slashman> has joined #xwiki 11:48 <vmassol> gdelhumeau: just thought about something btw 11:48 <vmassol> (good morning) 11:48 <gdelhumeau> hi 11:48 <vmassol> if we replace the concept of "wii" by that of "subwiki" then we have a lot of APIs that are going to be wrong 11:48 <vmassol> starting with our Entity Reference API 11:48 <vmassol> for example WikiReference would not be correct anymore 11:48 <vmassol> (it should be SubWikiReference) 11:49 <vmassol> I'm realizing this since I'm currently updating the new model to replace what I had so far: Server —> Wiki and Wiki —> SubWiki ... 11:50 <vmassol> I wonder if it's a good idea 11:54 <vmassol> we have tons of API with the name "wiki" 11:54 <vmassol> WikiComponentScope.WIKI for ex (just to cite another one) 11:55 <vmassol> WikiDeletedEvent to cite another one, etc 11:55 <vmassol> seen how many such API we have I'm wondering if it's wise to make this change at least at the API level 11:55 <vmassol> I'm sending a mail on this 11:56 <gdelhumeau> ok 11:56 <gdelhumeau> I have made a commit on my private repo where I have only changed the UI 11:56 <gdelhumeau> but it could be problem if the API is not consistent with the UI 12:45 <camil7> oh, spam 12:47 <camil7> feel back to remove my version of rollback - currently i looks like have written the "platform" homepage which is definitely not the case :) 13:06 <sburjan> Hello everybody.

<sdumitriu> has quit 01:03 <sdumitriu> has joined #xwiki 01:12 <sdumitriu> has quit 01:15 <sdumitriu> has joined #xwiki 02:32 <Denis> has quit 04:30 <Denis> has joined #xwiki 04:55 <polx> has quit 05:02 <polx> has joined #xwiki 05:51 <Denis> has quit 07:24 <polx> has quit 07:47 <polx> has joined #xwiki 07:48 <msmeria> has joined #xwiki 08:02 <evalica> has joined #xwiki 08:21 <evalica> has quit 08:22 <evalica> has joined #xwiki 08:23 <sburjan> has joined #xwiki 08:36 <polx> has quit 08:37 <polx> has joined #xwiki 08:38 <polx> has quit 08:51 <vmassol> has joined #xwiki 08:54 <Denis> has joined #xwiki 08:59 <polx> has joined #xwiki 09:02 <polx> has quit 09:07 <polx> has joined #xwiki 09:26 <polx> has quit 09:26 <polx> has joined #xwiki 09:31 <polx> has quit 09:41 <polx> has joined #xwiki 10:01 <gdelhumeau> has joined #xwiki 10:11 <vmassol> good morning 10:11 <vmassol> I'm starting to have a bit too many stashes… https://gist.github.com/vmassol/6410379 10:14 <camil7> has joined #xwiki 10:16 <KermitTheFragger> has joined #xwiki 11:19 <Slashman> has joined #xwiki 11:48 <vmassol> gdelhumeau: just thought about something btw 11:48 <vmassol> (good morning) 11:48 <gdelhumeau> hi 11:48 <vmassol> if we replace the concept of "wii" by that of "subwiki" then we have a lot of APIs that are going to be wrong 11:48 <vmassol> starting with our Entity Reference API 11:48 <vmassol> for example WikiReference would not be correct anymore 11:48 <vmassol> (it should be SubWikiReference) 11:49 <vmassol> I'm realizing this since I'm currently updating the new model to replace what I had so far: Server —> Wiki and Wiki —> SubWiki ... 11:50 <vmassol> I wonder if it's a good idea 11:54 <vmassol> we have tons of API with the name "wiki" 11:54 <vmassol> WikiComponentScope.WIKI for ex (just to cite another one) 11:55 <vmassol> WikiDeletedEvent to cite another one, etc 11:55 <vmassol> seen how many such API we have I'm wondering if it's wise to make this change at least at the API level 11:55 <vmassol> I'm sending a mail on this 11:56 <gdelhumeau> ok 11:56 <gdelhumeau> I have made a commit on my private repo where I have only changed the UI 11:56 <gdelhumeau> but it could be problem if the API is not consistent with the UI 12:45 <camil7> oh, spam 12:47 <camil7> feel back to remove my version of rollback - currently i looks like have written the "platform" homepage which is definitely not the case :) 13:06 <sburjan> Hello everybody.

group_id=170 "looking for older versions" 14:31 <tmortagne> gdelhumeau: there is the concept of old stable in http://enterprise.xwiki.org/xwiki/bin/view/Main/Download 14:31 <tmortagne> (always been) 14:31 <vmassol> we could add a 3rd download on the download page but I don't like it too much 14:31 <tmortagne> same as in API pages 14:31 <vmassol> since it doesn't push users to upgrade 14:32 <tmortagne> vmassol: again it would not be the first time we would have 3 downloads 14:32 <vmassol> except that our strategy so far is only 2 versions: stable and milestones/rc 14:32 <vmassol> we're not 100% clear on this 14:33 <vmassol> we need to decide if we want to officialize the concept of 14:33 <vmassol> "latest version from the previous cycle" 14:33 <tmortagne> I think we always apply it so we would make it official 14:33 <vmassol> and then always have 3 verisons to download 14:33 <tmortagne> (and it's even more important when the cycle change the version of Java) 14:34 <vmassol> sending email and then we can update our docs on dev.xwiki.org 14:34 <tmortagne> s/would/could/ 14:40 <vmassol> I wonder if we really need to support the latest stable from the current cycle... 14:41 <vmassol> anyway let's assume we do for now 14:41 <vmassol> sending email now 14:41 <tmortagne> I think we do, if we release a 8.0 that is unusable I don't think we can let it like this until we release 9.0 14:42 <vmassol> you mean 8.1 not 9.0 14:42 <tmortagne> yes 14:42 <vmassol> actually not even 8.1 14:42 <vmassol> but 8.1M1 14:42 <tmortagne> no 14:42 <tmortagne> we can't advertise 8.1M1 as the stable to replace 8.0 14:42 <tmortagne> so you have to wait for 8.1 14:43 <vmassol> advertising a X.0 release a stable is also kind of an issue… but yes ok… 14:47 <polx> has joined #xwiki 14:54 <lucaa> has quit 14:55 <lucaa> has joined #xwiki 14:58 <gdelhumeau> so, what should I do?

group_id=170 "looking for older versions" 14:31 <tmortagne> gdelhumeau: there is the concept of old stable in http://enterprise.xwiki.org/xwiki/bin/view/Main/Download 14:31 <tmortagne> (always been) 14:31 <vmassol> we could add a 3rd download on the download page but I don't like it too much 14:31 <tmortagne> same as in API pages 14:31 <vmassol> since it doesn't push users to upgrade 14:32 <tmortagne> vmassol: again it would not be the first time we would have 3 downloads 14:32 <vmassol> except that our strategy so far is only 2 versions: stable and milestones/rc 14:32 <vmassol> we're not 100% clear on this 14:33 <vmassol> we need to decide if we want to officialize the concept of 14:33 <vmassol> "latest version from the previous cycle" 14:33 <tmortagne> I think we always apply it so we would make it official 14:33 <vmassol> and then always have 3 verisons to download 14:33 <tmortagne> (and it's even more important when the cycle change the version of Java) 14:34 <vmassol> sending email and then we can update our docs on dev.xwiki.org 14:34 <tmortagne> s/would/could/ 14:40 <vmassol> I wonder if we really need to support the latest stable from the current cycle... 14:41 <vmassol> anyway let's assume we do for now 14:41 <vmassol> sending email now 14:41 <tmortagne> I think we do, if we release a 8.0 that is unusable I don't think we can let it like this until we release 9.0 14:42 <vmassol> you mean 8.1 not 9.0 14:42 <tmortagne> yes 14:42 <vmassol> actually not even 8.1 14:42 <vmassol> but 8.1M1 14:42 <tmortagne> no 14:42 <tmortagne> we can't advertise 8.1M1 as the stable to replace 8.0 14:42 <tmortagne> so you have to wait for 8.1 14:43 <vmassol> advertising a X.0 release a stable is also kind of an issue… but yes ok… 14:47 <polx> has joined #xwiki 14:54 <lucaa> has quit 14:55 <lucaa> has joined #xwiki 14:58 <gdelhumeau> so, what should I do?

11:52 <vmassol> no IMO you could use it now 11:52 <vmassol> it's just that the blog app has not been updated when we introduced the icon set concet 11:52 <vmassol> *concept 11:53 <Pbas> but font awesome are tiny and not exactly like bootstrap icone 11:53 <vmassol> sure it means that the blog will only have silk and font awesome ATM 11:53 <vmassol> but that seems the best to me 11:53 <vmassol> because that's what we have right now for apps no?

11:56 <Enygma`> has quit 11:56 <gdelhumeau> vmassol: there is no inheritence concept, only a fallback to silk, but that would be a nice to have 11:56 <vmassol> Pbas: if you name the icon set then you don't obey the admin setting 11:56 <gdelhumeau> I don't plan to support glyphicon for the reason I've mentioned above 11:57 <vmassol> but we can't say that gdelhumeau 11:57 <vmassol> since we use it already :) 11:57 <gdelhumeau> you know what I mean 11:57 <gdelhumeau> not in Skin App 11:57 <vmassol> but then we have the issue raised by Pascal 11:57 <vmassol> that the app icons cannot match the icons of the skin 11:57 <gdelhumeau> yes glyphicon is a bit different than F-A 11:57 <vmassol> how do we solve this issue?

11:52 <vmassol> no IMO you could use it now 11:52 <vmassol> it's just that the blog app has not been updated when we introduced the icon set concet 11:52 <vmassol> *concept 11:53 <Pbas> but font awesome are tiny and not exactly like bootstrap icone 11:53 <vmassol> sure it means that the blog will only have silk and font awesome ATM 11:53 <vmassol> but that seems the best to me 11:53 <vmassol> because that's what we have right now for apps no?

11:56 <Enygma`> has quit 11:56 <gdelhumeau> vmassol: there is no inheritence concept, only a fallback to silk, but that would be a nice to have 11:56 <vmassol> Pbas: if you name the icon set then you don't obey the admin setting 11:56 <gdelhumeau> I don't plan to support glyphicon for the reason I've mentioned above 11:57 <vmassol> but we can't say that gdelhumeau 11:57 <vmassol> since we use it already :) 11:57 <gdelhumeau> you know what I mean 11:57 <gdelhumeau> not in Skin App 11:57 <vmassol> but then we have the issue raised by Pascal 11:57 <vmassol> that the app icons cannot match the icons of the skin 11:57 <gdelhumeau> yes glyphicon is a bit different than F-A 11:57 <vmassol> how do we solve this issue?