moving Silva Image to a extension

Reported by Jan-Wijbrand Kolman on 2004-07-22
12
Affects Status Importance Assigned to Milestone
Silva
Wishlist
Unassigned

Bug Description

We might want to consider moving Silva Image (with all of its manipulation
functionality etc.) into a seperate Silva Extension, and keep a very lightweight
image asset in the core. That way we can safely depend on PIL for this
extension, where the core's dependencies are kept to a minimum.

(A cool idea, that's actually Martijn's :)

This might also relate to the existing ideas on refactoring the assets in Silva.

Christian Zagrodnick (zagy) wrote :

This sounds like a very good idea! The image asset is sort of ... strange due to
the automatic degrading.

Sylvain Viollon (thefunny) wrote :

This is core feature that is used by everybody. Lot of code in Silva have already been refactored. With a bit more work we could rename it to silva.core.content (base classes) and silva.app.content (actual content, link, image, toc, ghost).

Changed in silva:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers