>> Is Mime supported in the VW-SmallWiki?
Yes, this is working in VW: The mime-type is automatically read from
the HTTP header when uploading a file.
>> As I understand, the mimetype is set when you create a new Resource,
>> but not, when you upload the data (or a new version). The default
>> value is ''.
You can get the mime-type of the data with any callback-block you
define. I suspect that in Squeak SmallWiki this is not properly passed
from the server to the callback-block:
[ :action :value :mimetype | ... ]
I know, I should add a test to catch that kind of problem.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
Hello
I created a SWResource item in the 'contents' list of a folder.
I am asked to supply the title and the indicate from where to upload the
resource. I pointed to a *.wav file.
The file was uploaded in is served inline if another pages refers to
this resource. However the mime type is not set.
Where and how do I update the list of known mime types?
Is this a candidate for the FAQ?
Thank you for the answer in advance.
Hannes
Hi,
today morning I updated kilana to use the latest code. It is slightly
faster, as the folders are optimized to have a faster look-up of their
children.
Unfortunately there were some problems in the ESE part of the wiki. At
two places there were structures differing only in case, but as ids are
now case in-sensitive I had to rename them. Michele, probably you
should tell that to your students, nothing is gone or lost, it just has
a slightly different name.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
There are two failing tests in the latest version on the public repository.
Both failures are related to 'mailto:' being translated into
'mailto:'.
Also, could the action and permissions be changed to lazily initialize.
Currently, the initialization is in the post load block. This is VW specific
so when I port it, I must convert it to #Smalltalk code manually. I think
this would work:
actions
actions isNil
ifTrue: [ self initializeActions ].
^actions
initializeActions
actions := Set new.
actions
add: ...
John Brant
Hi Maurice,
> I would appreciate any pointers for installing it on server of our
> 1and1.com webhosted account. If not, I see that several SmallWikis
> are hosted at http://kilana.unibe.ch:9090. Would it be possible to
> host mine there as well?
kilana.unibe.ch is a server run by the University of Bern, I am not
sure about their policies but I think it should not be used for non
university related wikis.
When studying the features of 1and1.com I read that the owner gets SSH
access to the server, so it should be no big deal to install and run
either VisualWorks or Squeak there. We usually also run a VNC server on
our hosts to allow remote access easily.
The company I am working for (netstyle.ch, www.netstyle.ch) is offering
Smalltalk hosting. The advantage for you would be that we could provide
you with a running configuration and if necessary integrate it into
your corporate design. Let us know, if you are interested.
Regards,
Lukas
On Dec 6, 2003, at 03:19, Maurice Rabb wrote:
> Dear Lukas,
>
> I have been looking at your SmallWiki with great interest. We would
> like to use it instead of the CoWeb for our wiki.
>
> I would appreciate any pointers for installing it on server of our
> 1and1.com webhosted account. If not, I see that several SmallWikis
> are hosted at http://kilana.unibe.ch:9090. Would it be possible to
> host mine there as well?
>
> Thank for your time.
>
> Sincerely,
>
> Maurice
>
>
> Maurice Rabb
> 312-735-0580
--
Lukas Renggli
http://renggli.freezope.org
Here are some more bugs/comments:
*) If you have a page title with quotes in it, they don't appear when you
reedit the page. For example, if you have (This is a "test"), the page title
on reediting will be (This is a ).
*) If you enter < in a page for the < character, it appears as a < when
you reedit the page. For example, edit the syntax page. After you save the
page, the <b> is changed to <b>.
*) The scanner should reinitialize the keyword map when it loads
(WikiScanner initializeKeywordMap).
*) If you rename the Syntax page, it stops appearing on the edit pages.
*) Page names should be case-insensitive. Most likely ordinary users are
used to non-case-sensitive items (e.g., the Windows file system, domain
names -- WWW.GOOGLE.COM = www.google.com).
John Brant
Hi,
I wanted to set up a script that starts SmallWiki (if it crashes)
with the old documentroot. So I wrote a file config.st with the
following lines:
sw := SWKom startOn: 8080 host: 'localhost' ip: '127.0.0.1'.
sw storage: (SWSIXXStorage new delay: 60 * 60).
sw start.
and started everything with
squeak squeak.image config.st
But when I restart the SmallWiki, the saved documentroot becomes
overridden.
So can I reload a root.xml in a fresh SmallWiki-Image? I didn't
find the semantics in the Methods. I think of something like:
sw := SWKom startOn: 8080 host: 'localhost' ip: '127.0.0.1'.
sw storage: (SWSIXXStorage new delay: 60 * 60).
sw storage restoreFromDefaultXmlFile.
sw start.
thanks
Chris Burkert
--
http://www.chrisburkert.de/
Hello
I wonder if I'm really the first person who uses Smallwiki (Squeak
implementation) for writing French.
I type for example
Yaoundé
(the last letter is a lower case e with acute accent)
and I get at the Webpage Smallwiki serves
YaoundÈ
(the last letter is an E with acute accent).
Any suggestion how I can fix this?
Regards
Hannes
Hi Nevin,
> 1. The "contents" of a SmallWiki is a combination of pages, folders,
> and resources.
correct.
> 2. A "page" and a "resource" are components, and a "folder" is a
> composite of those two components.
^^^^^^^^^^^^^^
yes, it is a composite-pattern, but there are not just those two
components that might be put into a folder:
- First of all it is possible to nest folders, to allow putting
together related content. Furthermore folders are a kind of a
namespace, so you might have pages with the same title in different
folders.
- There are other components available to be used with SmallWiki as
extension. As an example some time ago I have written a component
displaying a keyword-index of your wiki. A lot of other components
(have been|are|will be) written during software design courses at the
University of Bern and Brussels. Just to name a few examples: link
collection, photo gallery, forum, address-book, calendar pages, rss
viewer, ...
> 3. A "resource" is some uploaded file resource, such as a sound, a
> video clip, or a picture.
Exactly, usually this is for things like you mention: jpg, gif, mp3,
mpg, zip, pdf, doc, ... Actually it is also possible to upload a
html-file to serve static pages/style-sheets ...
> OK, what if I don't care to allow anybody to upload file resources?
> That would leave a "page" as the only interesting component left.
For further information about the design, see the diagrams in the
documentation:
Smallwiki - Collaborative Content Management
http://www.iam.unibe.ch/~scg/smallwiki/smallwiki.pdf
> And why bother having a composite (a "folder") of only one component?
Wikis have always been flat (WikiWorks has one level: Book -> Page,
SWiki has two levels: Shelf -> Book -> Page) and in my opinion this has
a lot of drawbacks. Therefor I decided to implement a real composite
and this gives a lot of power to the users to organize their things. Of
course it also adds some complexity, but I think today everybody is
used to work with folders and files in their filesystem.
After all, it is possible to use SmallWiki without creating any folder:
just put everything into the root, but there will be a mess very soon
;)
> In other words, if I don't care to allow people to upload files to my
> SmallWiki, why would I be interested in anything other than pages (eg,
> children of type SWPage)?
See the examples above.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
_______________________________________________
Seaside mailing list
Seaside(a)lists.squeakfoundation.org
http://lists.squeakfoundation.org/listinfo/seaside