[ghns] [Inkscape-devel] inkscape community site
myselfhimself at free.fr
Sun Jun 1 05:05:35 PDT 2008
this is adressed to Frank because I think you may answer to that easily, but
maybe anyone could comment on this.
I'm writing about the opendesktop api especially for it's blenderstuff
version if there's one.
So to recall about my project, I'm working on a client for Blender which
could interact with several blender repositories (including blenderstuff.org)
to be able to browse for objects, fetch some and upload other to
repositories. I intend to have a central server which tries to lookup the
various repositories periodically and update its cache of (which object -
can be found where) pairs. The client queries the central servers which
looks into its cache and gives links to the client for : image previews &
details of objects, direct links to download the objects.
These days I'm listing the various attributes that each repository provides
for the objects it stores. So preview picture is something I was concerned
looking at this for example taken from the LIST function of the online API:
there seems to be 3 kinds of previews :
then for the preview1 tag : there are b) thumbnails at the top and c)big
pictures in the middle (screenshots 1,2,3 from the add content online form)
Is there a standard size for those types of previews ? I can guess that
there's one fixed size for type b) but no for the others.
What's the real difference between preview of class a) and previews of class
Looking at : http://api.kde-apps.org/V1/GET/72739 with an excerpt below :
<downloadname1>Binary + Source</downloadname1>
comment on the above dump : preview1,2 and 3 contain exactly the same url,
which leads to a dhtml pages with the thumbnail images as smallpreviewpic*
and the same big images as previewpic*.
The page linked in preview* elements contains items listed right after in
the xml file and parsing the html would require additional work for coders.
I can understand that some people may want to embed this html page into some
htmlview widget, so I'd suggest completely replacing the preview* tags by a
single <previewshtmlpage> which would encompass the html page url.
in the case of blender repo client usage of remote repositories, we would
like to have 1 thumbnail of fixed size (to avoid having to resize it on the
client side) per item if provided, and at least one big image (if possible
at a specific size as well) that would be showed if a user wants more
details. I wish this (1 link to thumbnail + 1 link to big image) pack
existed be in each entry elements of the xml returned by LIST(), I think
that it was the aim of preview1 and previewpic1 except that preview1 leads
So in short, I would propose for each items, to have direct links within the
- for the LIST() output : <preview1>(thumbnail) and <previewpic1>(big)
- for the GET() output : <preview[1-3]>(thumbnails), <previewpic[1-3]>(big),
<previewhtmlpage>(link to the dhtml page with thumbnails on top + 1 big
screenshot at a time in the bottom part)
this could break the API a very little and maybe some clients (so far I know
only khotnewstuff)... I don't know which tags khotnewstuff uses and which it
doesn't, but I doubt the url to html pages from preview[1-3] (LIST and GET
outputs) are used by that tool.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghns