Extension news

And there's some more information which could be interesting in the widget.

Imagine a paginator showing you the number of shown items and the total number of news items:

News 1-10 of 256
11-20 of 256
...

This could be made available via:

{pagination.firstPageItem}
{pagination.lastPageItem}

WidgetController:

$pagination['firstPageItem'] = ($this->currentPage - 1) * (integer)$this->configuration['itemsPerPage'] + 1;

if ($this->currentPage < $this->numberOfPages) {
  $pagination['nextPage'] = $this->currentPage + 1;
  $pagination['lastPageItem'] = $this->currentPage * (integer)$this->configuration['itemsPerPage'];
 } else {
  $pagination['lastPageItem'] = count($this->objects);
}

I'll go push that :)

count can be done in fluid, see searchresult.html

<f:translate key="search-text" arguments="{0:'{f:count(subject:news)}',1:search.subject}" />

but if you add it with the others, it is fine too I guess

I'd also add another language label for that. How is the translation handled?

just add it to locallang or what do you mean?

Add default language is clear. What about translations? Are they manually put into the locallang.xml file or via translation server? I could add german version too if it's done manually.

What is the policy for handling new properties in templates?

Three new properties would be made available in paginator template.

a) Adding them to template would break existing sites, which use unchanged extension templates instead of copies from fileadmin/
b) Adding them not to template would not demonstrate the usage.

I'd choose a), since templating best practice is to always use a copy in fileadmin instead of extension original.

why should there something break? i didn't get it, but we can just add breaking changes to the wiki and later to the manual as I did with 1.2.0.

nevertheless, push the change and I will check it anyways ;)

If we add this to the paginate widget template of the extension:

Item {pagination.firstPageItem} to {pagination.lastPageItem} of {pagination.numberOfItems}

Then anyone who uses the paginate widget will get some new content in hoer website after upgrade:

Item 1 to 10 of 145

Btw. Is there a TS configuration to set custom path to widget template?
I tried:

plugin.tx_news.view {
  widget.Tx_News_ViewHelpers_Widget_PaginateViewHelper.templateRootPath = fileadmin/news-tmpl/Templates/
}

The file itself is placed in: fileadmin/news-tmpl/Templates/ViewHelpers/Widget/Paginate/Index.html

but it didn't work. Could find any info in the wiki or ext docs.

Im running the master von git and it works for me with the following code:
I'd also problems with it, but it was an caching problem. I had to manually clear cache, config.no_cache didn't works here for me - I don't know why...

1 plugin.tx_news {
2     view {
3         templateRootPath = {$fw.path.htmlext}news/textblog/Templates/
4         partialRootPath = {$fw.path.htmlext}news/textblog/Partials/
5         layoutRootPath = {$fw.path.htmlext}news/textblog/Layouts/
6         widget.Tx_News_ViewHelpers_Widget_PaginateViewHelper.templateRootPath = {$fw.path.htmlext}news/textblog/Templates/
7     }
8 }

You have to apply a patch in TYPO3 4.5 to be able to configure a custom widget template.

When we change the paginate widget template, all unpatched 4.5 installations will use the changed template. For most installations, adding new properties is a breaking change.

We need a decision :)

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/8734

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/8734

What about adding a "showcase template" for demonstration, with a big fat warning not to use it in production.