20 Nov
2008
20 Nov
'08
7:07 p.m.
On Nov 20, 2008, at 4:11 PM, Asiri Rathnayake wrote:
On Thu, Nov 20, 2008 at 8:30 PM, Asiri Rathnayake
<
asiri.rathnayake(a)gmail.com> wrote:
You should have a design that allows to plug any number of filtering
strategies (FilterStrategy interface) and implement 2 for now:
StrictFilterStrategy
NoopFilterStrategy (or some other name)
I think we can implement the moderate one later on after we start
using the tool and get user feedback.
At least I think it would be good to have those 2 fully done first.
Thanks
-Vincent
On Thu, Nov 20, 2008 at 8:17 PM, Asiri Rathnayake
<
asiri.rathnayake(a)gmail.com> wrote:
Again, may be we should introduce another level of style filtering.
So we
have 3 levels of filtering. Hi Guillaume,
I can't help you much from the technical perspective. Re styles
that can
+ same question for image height & width... I'm asking these
questions
because I think that sort of information should be preserved,
otherwise the
document will look really strange after import.
be
directly mapped to XWiki 2.0 syntax, I think they should be
converted to
use
that syntax. To summarize my opinion:
- When strict filtering is activated (conversion to XWiki 2.0
syntax)
- Only style attributes that can be directly mapped to wiki syntax
element should be kept
- This means that NO (% ... %) should appear
Is that fine with everyone?
Just came into my mind, what about alignments ? (of texts, images
and the
like ?) Do you think they should also be ripped off when strict-
filtering
is on ?
1. Strict filtering (Filter everything, a.k.a not a
single (%%))
2. Moderate (Filter styles as much as possible but try to preserve
those
formatting elements which makes the document look appealing, like
alignment,
image height & width etc.)
3. Filter nothing.
This is just an idea.
- Asiri