[xwiki-devs] [Proposal] Computed title depth configuration option
Hi, We've had a user request (Ludovic as a user ;)) to have a config option to decide the header level to consider for a title. Right now we consider only levels 1 and 2 when computing a title from the doc content. Thus I'm going to add a config option named xwiki.title.headerdepth and with a default value of 2 (to have the same behavior as now) and use it in XWikiDocument.getRenderedContentTitle(). Note that this is only for the 2.0 syntax (since it's too hard to do for syntax 1.0 and we're not supposed to bring changes to the 1.0 syntax). Please shout quickly if you're against this. Thanks -Vincent
+1 On Thu, Apr 15, 2010 at 17:46, Vincent Massol <[email protected]> wrote:
Hi,
We've had a user request (Ludovic as a user ;)) to have a config option to decide the header level to consider for a title.
Right now we consider only levels 1 and 2 when computing a title from the doc content.
Thus I'm going to add a config option named xwiki.title.headerdepth and with a default value of 2 (to have the same behavior as now) and use it in XWikiDocument.getRenderedContentTitle().
Note that this is only for the 2.0 syntax (since it's too hard to do for syntax 1.0 and we're not supposed to bring changes to the 1.0 syntax).
Please shout quickly if you're against this.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 On Thu, Apr 15, 2010 at 9:16 PM, Vincent Massol <[email protected]> wrote:
Hi,
We've had a user request (Ludovic as a user ;)) to have a config option to decide the header level to consider for a title.
Right now we consider only levels 1 and 2 when computing a title from the doc content.
Thus I'm going to add a config option named xwiki.title.headerdepth and with a default value of 2 (to have the same behavior as now) and use it in XWikiDocument.getRenderedContentTitle().
Note that this is only for the 2.0 syntax (since it's too hard to do for syntax 1.0 and we're not supposed to bring changes to the 1.0 syntax).
Please shout quickly if you're against this.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1, with 2 remarks: - do you allow setting locally in XWikiPreferences, so that XWiki farm are not globally constrained ? - do you allow 0 to disable searching title in content ? Denis On Fri, Apr 16, 2010 at 07:47, Asiri Rathnayake <[email protected]>wrote:
+1
On Thu, Apr 15, 2010 at 9:16 PM, Vincent Massol <[email protected]> wrote:
Hi,
We've had a user request (Ludovic as a user ;)) to have a config option to decide the header level to consider for a title.
Right now we consider only levels 1 and 2 when computing a title from the doc content.
Thus I'm going to add a config option named xwiki.title.headerdepth and with a default value of 2 (to have the same behavior as now) and use it in XWikiDocument.getRenderedContentTitle().
Note that this is only for the 2.0 syntax (since it's too hard to do for syntax 1.0 and we're not supposed to bring changes to the 1.0 syntax).
Please shout quickly if you're against this.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
On Apr 16, 2010, at 9:41 AM, Denis Gervalle wrote:
+1, with 2 remarks: - do you allow setting locally in XWikiPreferences, so that XWiki farm are not globally constrained ?
No. This is a backward compat thing since we don't want to manager titles this way in the near future. We'll need to revive this thread BTW. The latest discussion I had with Jean-Vincent and Thomas (AFAIR) was to make the title field a textarea (but only 1 line displayed by default) so that we could put scripts in it. And to make it evaluated like the content, not just by old Rendering Interpreters.
- do you allow 0 to disable searching title in content ?
I hadn't thought about this but yes, that should work fine actually (since H0 doesn't exist) :) Thanks -VincentDenis
On Fri, Apr 16, 2010 at 07:47, Asiri Rathnayake <[email protected]>wrote:
+1
On Thu, Apr 15, 2010 at 9:16 PM, Vincent Massol <[email protected]> wrote:
Hi,
We've had a user request (Ludovic as a user ;)) to have a config option to decide the header level to consider for a title.
Right now we consider only levels 1 and 2 when computing a title from the doc content.
Thus I'm going to add a config option named xwiki.title.headerdepth and with a default value of 2 (to have the same behavior as now) and use it in XWikiDocument.getRenderedContentTitle().
Note that this is only for the 2.0 syntax (since it's too hard to do for syntax 1.0 and we're not supposed to bring changes to the 1.0 syntax).
Please shout quickly if you're against this.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Fri, Apr 16, 2010 at 12:09, Vincent Massol <[email protected]> wrote:
On Apr 16, 2010, at 9:41 AM, Denis Gervalle wrote:
+1, with 2 remarks: - do you allow setting locally in XWikiPreferences, so that XWiki farm are not globally constrained ?
No. This is a backward compat thing since we don't want to manager titles this way in the near future.
Sure, but not taking from XWikiPreference has big impact on farms. I have the same issue with the previous compat settings, I have to live with only one options for all my clients, which is obviously not easy to maintain.
We'll need to revive this thread BTW. The latest discussion I had with Jean-Vincent and Thomas (AFAIR) was to make the title field a textarea (but only 1 line displayed by default) so that we could put scripts in it. And to make it evaluated like the content, not just by old Rendering Interpreters.
Yes, if you don't, I will anyway revive a thread about title. There is a major issue imposing title at the top of the document for at least 2 reasons: - site that have been built with the previous case are not always properly fixed by the current removal of doubles, since there may be editorial reason for a difference in the title texts - automated page suffer of this, since the content of the title may depends on a lot of script logic in the page, see ResetPasswordComplete for a simple XWiki exemple, and imagine what it does on more complex applicative site. So, yes, there is many improvement to put in for this. I am currently migrating sites from 1.9 to 2.2 and titles are my main issues. I had to use "display:none" style for some, waiting for something better ! Denis
- do you allow 0 to disable searching title in content ?
I hadn't thought about this but yes, that should work fine actually (since H0 doesn't exist) :)
Thanks -VincentDenis
On Fri, Apr 16, 2010 at 07:47, Asiri Rathnayake <[email protected]>wrote:
+1
On Thu, Apr 15, 2010 at 9:16 PM, Vincent Massol <[email protected]> wrote:
Hi,
We've had a user request (Ludovic as a user ;)) to have a config option to decide the header level to consider for a title.
Right now we consider only levels 1 and 2 when computing a title from
the
doc content.
Thus I'm going to add a config option named xwiki.title.headerdepth and with a default value of 2 (to have the same behavior as now) and use it in XWikiDocument.getRenderedContentTitle().
Note that this is only for the 2.0 syntax (since it's too hard to do for syntax 1.0 and we're not supposed to bring changes to the 1.0 syntax).
Please shout quickly if you're against this.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
On Apr 16, 2010, at 12:22 PM, Denis Gervalle wrote:
On Fri, Apr 16, 2010 at 12:09, Vincent Massol <[email protected]> wrote:
On Apr 16, 2010, at 9:41 AM, Denis Gervalle wrote:
+1, with 2 remarks: - do you allow setting locally in XWikiPreferences, so that XWiki farm are not globally constrained ?
No. This is a backward compat thing since we don't want to manager titles this way in the near future.
Sure, but not taking from XWikiPreference has big impact on farms. I have the same issue with the previous compat settings, I have to live with only one options for all my clients, which is obviously not easy to maintain.
The solution to this is easy: use the new configuration system. However I didn't use it voluntarily since this config option is a backward compat config option right now and I didn't want to "pollute" the new xwiki.properties file with something that will be removed in the future. At the minimum we'd need to agree we want this behavior for the future.
We'll need to revive this thread BTW. The latest discussion I had with Jean-Vincent and Thomas (AFAIR) was to make the title field a textarea (but only 1 line displayed by default) so that we could put scripts in it. And to make it evaluated like the content, not just by old Rendering Interpreters.
Yes, if you don't, I will anyway revive a thread about title. There is a major issue imposing title at the top of the document for at least 2 reasons: - site that have been built with the previous case are not always properly fixed by the current removal of doubles, since there may be editorial reason for a difference in the title texts - automated page suffer of this, since the content of the title may depends on a lot of script logic in the page, see ResetPasswordComplete for a simple XWiki exemple, and imagine what it does on more complex applicative site.
Yes both points are known and they are answers. If you want to revive this thread I suggest we start a new thread.
So, yes, there is many improvement to put in for this. I am currently migrating sites from 1.9 to 2.2 and titles are my main issues. I had to use "display:none" style for some, waiting for something better !
I'm curious to know the use cases where the deduplication compatibility option doesn't work. We'd need to document them in titlevars.vm Thanks -Vincent
Denis
- do you allow 0 to disable searching title in content ?
I hadn't thought about this but yes, that should work fine actually (since H0 doesn't exist) :)
Thanks -VincentDenis
On Fri, Apr 16, 2010 at 07:47, Asiri Rathnayake <[email protected]>wrote:
+1
On Thu, Apr 15, 2010 at 9:16 PM, Vincent Massol <[email protected]> wrote:
Hi,
We've had a user request (Ludovic as a user ;)) to have a config option to decide the header level to consider for a title.
Right now we consider only levels 1 and 2 when computing a title from
the
doc content.
Thus I'm going to add a config option named xwiki.title.headerdepth and with a default value of 2 (to have the same behavior as now) and use it in XWikiDocument.getRenderedContentTitle().
Note that this is only for the 2.0 syntax (since it's too hard to do for syntax 1.0 and we're not supposed to bring changes to the 1.0 syntax).
Please shout quickly if you're against this.
Thanks -Vincent
On 04/16/2010 12:09 PM, Vincent Massol wrote:
make the title field a textarea (but only 1 line displayed by default) so that we could put scripts in it. And to make it evaluated like the content, not just by old Rendering Interpreters.
Why? -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Apr 16, 2010, at 2:04 PM, Sergiu Dumitriu wrote:
On 04/16/2010 12:09 PM, Vincent Massol wrote:
make the title field a textarea (but only 1 line displayed by default) so that we could put scripts in it. And to make it evaluated like the content, not just by old Rendering Interpreters.
Why?
Let's discuss all this in a new thread about the new title strategy we'd like to have. -Vincent
participants (5)
-
Asiri Rathnayake -
Denis Gervalle -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol