On Feb 13, 1:34 pm, Heiko Hees <[email protected]> wrote:
> First of all we probably will have to hack the handling of the  
> [[Image:]] construct to support external 
> links:http://meta.wikimedia.org/wiki/Help:Images_and_other_uploaded_files#Link
> we currently don't if I got the source 
> right:http://code.pediapress.com/hg/mwlib/file/71009b0f6bc2/mwlib/mwapidb.p...
> ( note to self: what about the involved attribution issues?)
>
> It then depends, whether 15K is enough for most of the graphviz  
> descriptions and  can be handled by the majority of servers, PHP and  
> MediaWiki deployments.
>
> If so, construct an URL like the 1st one in your example 1), put it  
> into an image construct [[Image:Pic.jpg|link=<your url>]], return this  
> from your function in tagext.py and patch the extension to directly  
> return an image from this URLs location based on the parametrized data.
>
> If there are problems with the 15K limit, hash the graphviz-
> description, construct an URL like the second one in your example 1)  
> put it into an image construct [[Image:Pic.jpg|link=<your url>]],  
> return this from your function in tagext.py and patch the extension to  
> directly return an image from this URLs location based on the  
> parametrized data. In this case you'll probably depend on a cached  
> version of this image. Also there obviously needs to be a consistent  
> mapping of the graphviz description and the md5 hash. You could  
> implement this approach as a fallback if the former exceeds the GET  
> size limit.
>

Ok. That sounds great. I think I'll try the hash+fallback approach.

Thanks for the info, I think this is enough to get me started!

V/r,

Ryan Lane
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"mwlib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/mwlib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to