I suggest that you not use the version labeled "johnson"
because I am still trying to get everything exported
properly. I hope that I will be able to get a version
that works completely very soon.
-Ralph
Begin forwarded message:
> From: James Robertson <jarober(a)comcast.net>
> Date: August 23, 2004 11:12:49 PM CEST
> To: stéphane ducasse <ducasse(a)iam.unibe.ch>
> Subject: Re: Fwd: About running Wiki on VWNC
>
> They would need a commercial license if it was for commercial use.
>
> At 01:06 PM 8/23/2004, you wrote:
>
>
>> Begin forwarded message:
>>
>>> From: "Thomas Bernitt" <thom-ber(a)gmx.net>
>>> Date: August 23, 2004 9:15:25 AM CEST
>>> To: smallwiki(a)iam.unibe.ch
>>> Cc: stéphane ducasse <ducasse(a)iam.unibe.ch>
>>> Subject: Re: About running Wiki on VWNC
>>>
>>> Hi
>>>
>>> I was on vacation the last weeks and now I tried to find a more
>>> concrete
>>> answer and I want to add another yes-no-question:
>>>
>>> -If a company wants to run VW on a server for internal use, and want
>>> to
>>> develope additional smallwiki-functionality, do I need to pay or not?
>>>
>>> We had talks on the cebit this year with cincom to put this question
>>> to them
>>> - and the answer we got was 'yes, you have to pay'. In this case we
>>> has to
>>> pay a developer license at great expense.
>>>
>>> This topic demands a conclusion!
>>>
>>> Thanks
>>>
>>> Thomas
>>>
>>>
>>>> Hi james
>>>>
>>>>> Hmm, isn't that a contradiction:
>>>>>
>>>>> "If a company wants to run VW on a server for internal use, then
>>>>> they
>>>>> would need a license. "
>>>>>
>>>>> and
>>>>>
>>>>> "So, if you put SmallWiki under an Open Source license, you would
>>>>> also
>>>>> be ok on usage."
>>>>>
>>>>> Let's try simple yes/no questions ;-)
>>>>>
>>>>> - If I run Smallwiki on our company server for internal use, do I
>>>>> need
>>>>> to pay or not?
>>>>>
>>>>> - If I run Smallwiki on our company server for internal and
>>>>> external
>>>>> use as the wiki for an OpenSource project, do I need to pay or not?
>>>>>
>>>>> - If I run Smallwiki on our company server for internal and
>>>>> external
>>>>> use as the wiki for a commercial project, do I need to pay or not?
>>>>>
>>>>> I hate these kind of questions too and I appreciate your effort in
>>>>> trying to answer them!
>>>>
>>>> I want to know too because we are developing software which is
>>>> open-source and can be used by companies and I think that the
>>>> position
>>>> of cincom should be clear for all of us.
>>>>
>>>> You wrote: "It really depends. I explicitly open sourced
>>>> BottomFeeder,
>>>> and I'm not making money off it. So, if you put SmallWiki under an
>>>> Open Source license, you would also be ok on usage. It would be
>>>> unsupported by Cincom, but I suspect that's not really an issue
>>>> here."
>>>>
>>>> SmallWiki is open source but I do not understand what is unsupported
>>>> here?
>>>>
>>>> Thanks
>>>
>>>
>
> <Talk Small and Carry a Big Class Library>
> James Robertson, Product Manager, Cincom Smalltalk
> http://www.cincomsmalltalk.com/blog/blogView
> jarober(a)gosmalltalk.com
>
>
Hi
I was on vacation the last weeks and now I tried to find a more concrete
answer and I want to add another yes-no-question:
-If a company wants to run VW on a server for internal use, and want to
develope additional smallwiki-functionality, do I need to pay or not?
We had talks on the cebit this year with cincom to put this question to them
- and the answer we got was 'yes, you have to pay'. In this case we has to
pay a developer license at great expense.
This topic demands a conclusion!
Thanks
Thomas
> Hi james
>
> > Hmm, isn't that a contradiction:
> >
> > "If a company wants to run VW on a server for internal use, then they
> > would need a license. "
> >
> > and
> >
> > "So, if you put SmallWiki under an Open Source license, you would also
> > be ok on usage."
> >
> > Let's try simple yes/no questions ;-)
> >
> > - If I run Smallwiki on our company server for internal use, do I need
> > to pay or not?
> >
> > - If I run Smallwiki on our company server for internal and external
> > use as the wiki for an OpenSource project, do I need to pay or not?
> >
> > - If I run Smallwiki on our company server for internal and external
> > use as the wiki for a commercial project, do I need to pay or not?
> >
> > I hate these kind of questions too and I appreciate your effort in
> > trying to answer them!
>
> I want to know too because we are developing software which is
> open-source and can be used by companies and I think that the position
> of cincom should be clear for all of us.
>
> You wrote: "It really depends. I explicitly open sourced BottomFeeder,
> and I'm not making money off it. So, if you put SmallWiki under an
> Open Source license, you would also be ok on usage. It would be
> unsupported by Cincom, but I suspect that's not really an issue here."
>
> SmallWiki is open source but I do not understand what is unsupported
> here?
>
> Thanks
>
Hi Kris,
I'm very sorry that I didn't answer earlier: I'm currently very busy
and must have missed your post to the mailing-list :(
>> The server where it should run on is (very) infrequently rebooted.
>> Still I would like to make sure the Smallwiki storage is updated when
>> that happens. Can I somehow force this from a shutdown script?
Currently something like this isn't implemented. Try something like
this, it should be easily possible:
===========================================================
Smalltalk.SmallWiki defineClass: #SnapshotWiki
superclass: #{SmallWiki.Action}
indexedType: #none
private: false
instanceVariableNames: ''
classInstanceVariableNames: ''
imports: ''
category: 'SmallWiki Action'
SnapshotWiki>>execute
self server storage snapshot.
===========================================================
#!/bin/bash
wget http://localhost:8080/?aciton=SnapshotWiki
===========================================================
To be save from electrical outage you maybe want to have a look at the
work of Ralph Johnson, he wrote a storage that logs all the changes
instantly. Another possibility would be to increase the frequency of
the SnapshotStorage or to buy USV (uninterruptible power provider) for
you server machines.
>> I get the impression Smallwiki was designed to be run headfull:
>> configuration is done through the image etc. How to deal with this
>> when it is run headless?
Indeed it was designed to be run heedful. We also tried to run it
headless, but there seem to be strange problems with VisualWorks. All
of our servers run with VNC, so we can connect to the images
anytime/where and interact with the system if necessary.
Hope this helps,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
Hi Hans,
nice to hear that you would like to use SmallWiki for your home-page.
> - wie startet man dann automatisch im Image, z.B. mit headless Squeak ?
I don't know a lot about the port of SmallWiki to Squeak, I'm only
responsible for the development of the original version in VisualWorks.
> - Chris Burkert meint, der Squeak Port sei nicht zu empfehlen, wie
> siehst Du das ?
I think for a personal home-page it should be possible to use
VisualWorks, as this there is commercial (you don't earn money) use
then.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
I did the port of SmallWiki to Squeak mainly for myself and to learn
something about it. Unfortunatly I don't have the time to maintain it
further. So if somebody wants to make a try ... write me and I will pass
the maintainership.
Regards
Chris Burkert
--
http://www.chrisburkert.de/
Andreas Gerdes wrote:
> Serge,
> we run Squeak on Debian, it's lightning fast and it runs stable for a
> week now with a SWImageStorage active.
> Me too, I have had some trouble with the snapshot storage (CPU at 100%
> or damaged Snapshots) but IF you get it to run once, it seems to be ok.
>
To me, that seems to be a big *IF*. I've had no luck at all myself-- I
always get damaged Snapshots (except on Windows, where I get CPU at 100%).
The Bountiful Baby forum currently runs under Squeak SmallWiki:
http://www.bountifulbaby.com:8080
Right now I do manual image saves. I've lost data before, but
fortunately the wiki isn't mission critical. I've been tempted to yank
the entire SmallWiki out and replace it with the old Squeak ComWiki (or
PWS Wiki, or whatever it's called). Another option is phpbb (at
http://www.phpbb.com), which is something much more familiar to our
clientele, because so many doll chat groups run under phpbb.
Still undecided on exactly what I'll do, though.
Nevin
--
Nevin Pratt
Bountiful Baby
http://www.bountifulbaby.com
The Most Complete Reborn Supply Store On The Web!
(801) 992-3137
Hi,
please ask you questions directly to the SmallWiki-Mailing list, so
other people can read/answer/... as well!
> Is it possible to check if someone has the right to do something (like
> to view a structure) from anywhere in the wiki ?
Permissions are dynamically calculated for the user currently logged
while looking up the structure. Permissions depend on the context: the
currently browsed structure, the user currently logged in and the roles
that have been assigned to the user.
Currently there is no code to determine the permission for a given user
anywhere in the wiki, because this functionality was not needed.
Actually it could be implemented easily by simulating the call to
#processSecurity: for all the parents of the structure in question.
Cheers,
Lukas
On Aug 12, 2004, at 17:12, f.bulcka(a)alemtid.asso.fr wrote:
> Schl"usse,
>
> Is it possible to check if someone has the right to do something (
> like
> to view a structure) from anywhere in the wiki ?
>
> because something like :
>
> self request user hasPermission: Resource permisionView
>
> where self is an action
>
> is true if the user has the right for ( self structure).
> but if i want to know it for any structure, how can i do that ?
>
> Thanks,
>
> Frederic
>
>
--
Lukas Renggli
http://renggli.freezope.org
I was wondering if anyone has experience with running Smallwiki in a
headless VW image on a linux server. I am interested in replacing a
Squeak Wiki with Smallwiki, but am still wondering about the following
setup problems:
- The server where it should run on is (very) infrequently rebooted.
Still I would like to make sure the Smallwiki storage is updated when
that happens. Can I somehow force this from a shutdown script?
- I get the impression Smallwiki was designed to be run headfull:
configuration is done through the image etc. How to deal with this when
it is run headless?
