I would like to play with resource, but I am stop by
- What Mimetype means?
The mime-type describes the type of a file in a platform independent
manner. The browser needs this information to know how to display the
If you like to know more about the internals of the http-protocol I
suggest to read the standard-documentation. There you will find also
references to documents about the mime-type standard:
Hypertext Transfer Protocol -- HTTP/1.1
If I try to get into an end-user shoes, I think the idea of adding
manually a mime type is not so friendly. Why not to infer it by
regarding the file extension?
Usually you do not need to change this field, as it is automatically
updated by the information the browser is sending when uploading a file.
Unfortunately the additional information you get from the browser is
not standardized in the HTTP protocol: some browser do send mime-type
and filename, some only mime-type, some only the filename, some even
nothing at all.
I do not really like to be obliged to type the string
I want to upload an image.
I agree that this field should not be touched. But I think it is worth
to have it there, if the guess of SmallWiki is wrong and you want to
Something else, why not to hide all the resource
When I add an image from the link *my supper great image*, I am not so
interested by having an entry named 'my supper great image' in the
Why not? You told SmallWiki to add a resource into that folder and it
will appear there. Again, I have to mention that we have to think
slightly different compared to SWiki: I do not attach resources to
pages anymore as I think this is not very intuitive (and made the reuse
impossible), instead I handle them like a simple component.
There are basically two solutions:
1. Don't give users the link to the folder-index, but a link to an
index page where they might navigate your wiki from.
2. Create a new permission called 'List Resource' and add code to check
this permission when listing an component in a folder.