Ingo Rammer wrote:
>
> Hi,
>
> again some questions/proposals ... the last two are for the "more involved"
> ...
>
> WebPagePortlet)
> I'm currently working on this portlet (mostly because it's what i currently
> need). It seems to me that others did as well. If nobody's opposed I'd like
> to "collect" the various sources (already got Steve's) and try to "merge"
> them, taking the best features out of the different versions and adding
> what's still missing. [Please send only sources which are already under
> apache's license]
>
> Steve's portlet is a little messy (i.e. 10 times as many code as needed,
> because there is already the URL-Class in Java, which does the
> relative-mapping of two different urls) but gave me a good starting point.
>
> Features I'd like to implement are:
> * Rewriting of HREFs to point to the original servers
> * Rewriting of IMG SRCes to point to the original servers
> * Optional local caching of images (which must be explicitly turned on ...
> just thinking about legal reasons for this)
> .. this would also place the need for a "jetspeed disk-cache-access via
> HTTP-GET" .. any ideas for this?
> * Probably closure of all opened <table>s for layout-consistency with
> JetSpeed
> * Optional removal of all Java-Script-Code (and all
> "onSomething="-Attributes in Tags) .. for security reasons
> * (Probably) Optional removal of all Java applets (or rewriting them) ...
> for security reasons
> * (Probably) Optional removal of all ActiveX-Controls ... again for security
> reasons
>
> Contrib)
> What's the general attitude regarding new Portlets? Is there a possibility
> to share them with others (even though some features are still missing) via
> CVS [probably using a "contrib" package or something similar] or shall I put
> the sources on some webpage ... for the daring?
>
I think that if the portlet answers a general need (and that seems to be the
case for this portlet), it's best put under the "/modules" directory of
Jetspeed CVS.
This directory content is not built by default in Jetspeed and needs to be
recompiled manually but this may be perfected quite easily by defining
a build.xml file in each module and writing a "modules" target in the
main build script.
> Licensing)
> Are we able to use code, that's under SPL (Sun's Public License)? There
> seems to be a Lexer for HTML in Sun's Brazil project which should do parts
> of what we need here.
>
I don't know if these licenses are compatible with BSD type licenses but
Jon can certainly answer this, he knows everything about licenses... ;)
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
