where does an implemenation of IFilter really come from?
It has to be different for specific locale's?
So that you can have one markup file and filter it with X filters for X
locales?
johan
Matej Knopp wrote:
Okay, small update.
New interface
public interface IFilter {
public abstract
Hi.
I know this is little off topic but I'd like to ask if anyone know an
easy way to generate web pages from template within eclipse.
Recently I started thinking about internationalizing my application and
realized, that most of the strings to translate are actually in html
files. So
What I wanted to do was having a one markup (like Page_src.html) that
would look like
html
$(item1)
/html
and properties for different languages that could be used as model to
generate Page_en, Page_sk, Page_de, etc. These pages would be generated
statically from ide. But I don't want it
I personelly like the idea of using wicket as pre-processor or
templating engine. The reason is that I stay with wicket and that you
don't have to learn another technique. Though velocity is easy to
use. The pre-processor of course has the disadvantage that changes to
the files are not picked up
problem with caching: we read the markup file, separate them into raw
markup and wicket tags. That sequence of elements - we call it
MarkupStream - is cached, not the file content itself. Hmmm but if the
you return different resources (generated from templates) for
different locales, styles, etc
I have done some basic stuff.
I have UrlFilterResourceStream class with function
String filter(String source) {
...
}
that can be used to process the markup files before the actual markup
parsing.
All you have to do is add
ResourceStreamLocator locator;
public
Okay, small update.
New interface
public interface IFilter {
public abstract String filter(String source);
}
So I've something like this in my application:
ResourceStreamLocator locator;
IFilter filter;
public ResourceStreamLocator getResourceStreamLocator() {
if(locator == null) {
