Vincent Massol wrote:
............................................................
Reason:
The goal is to reuse the boxMacro in for implementing RssMacro,
Warning
and Error macros. The most complex of them being the RssMacro. So,
a RSS
feed should be rendered as follows:
---------------------------------------
optional image (provided as an URL to an image stored outside the
wiki,
anywhere in the web)
How do you implement this? If it's optional what happens if it's not
specified?
Could you show us an example of using the macro?
See
http://code.xwiki.org/xwiki/bin/view/Macros/RssMacro.
Dan I was actually talking about the Box macro.
My question was: what's your design for providing an image to display
or not. More specifically where can the image come from? If the answer
is: from a document then I think it's too restrictive since we can
have some images located in the skin on the filesystem for ex. Image
the info, error and warning macros. I don't think their images should
come from a document.
Thanks
-Vincent
I'm willing to
preserve the behavior of the old RssMacro as much as possible, except
for the new syntax, of course. So, given the feed's URL, we check
if it has an image or not. Then, we invoke the boxMacro, in
which we
pass as parameters the following: the title is the feed's title (i
don't
know whether there can be RSS feeds without a title, but in the
assumption that there is no title, we don't place anything in this
field), the image is the one we just picked before (if there is one,
of
course; if there isn't, we just don't put anything there). As for the
body, for each article from our feed, we invoke again the boxMacro for
building the "small boxes" in a similar manner, just like I
described in
the previous message.
For more details we can talk tomorrow when I get at the office.
title (which can be a static text or a link to a
web location
containing
the full news article)
This should be optional.
Thanks
-Vincent
As for the time needed for doing this job, I estimate that this will
take about 2 days for implementing it (and another 2-3 days writing
some
tests for it) from the moment I get consent to start working, in the
event that no other issues occur.
See you soon,
Dan