Hi lukas
I restarted to read SmallWiki code because I lost the changes of my
previous image.
Anyway, if I understand correctly there are permissions and users.
Permission are grants to perform action.
A role contains a list of permissions.
A user play certain roles.
Before performing an action, sw checks whether the user has the right
permissions obtained
by playing a certain role.
Now the structure itself is not involved, this means that if I want to
have a special page that only a certain person can edit but everybody
else cannot I have to create a special role for that. Am I correct? Or
is it possible to grant permission at the instance level like a page?
For example how do I say that a folder can only be edited by admin or
User X, or a person playing the role editFolderX?
Stef
Hello,
I am a trainee working on a small project with Smallwiki. I am mainly
interested in all the security issues. Formally, my project was about
the IP filtering. This approach seems to be not really relevant because
of the dynamic IP distribution by internet providers. Just by logging
out and logging in a new IP can be obtained, and could potentially
upload again, whereas an innocent user can be banned because her/his ISP
just could have given a banned IP.
So, let's take an another approach. Do you think it would be useful to
only grant the upload of some Mimes-types and only allocate a clear
space disk to users and groups of users like 50MB/day/user or
100MB/user, or define a clear file size allowed to avoid the flood.
I could maybe do it if you think it is useful.
Let me know.
Thanks
Cheers
Eric Luisi
Hi all,
I loaded the 'latest' version of SmallWiki in my experiments to
assemble a working version for which I do not have to touch the code. I
tested my assembly by running the unit tests (all run green) and by
then starting a server and adding some pages here and there.
Below I describe from which repository I took what version to make it
work (half from the scgStore, half from the Cincom public store). I
then started to reconcile things to find the corresponding versions in
the store repositories, in the hope that this helps in getting
everything syned again.
My assembly was the following:
Swazoo, scgStore, 1.5 ?can'find same version on Cincom store (see
below)
SIXX, scgStore, 3.5 (= 0.1g on cincom public store)
SmaCC, cincom public store, 1.3 (was on scg store - I put it as
1.3Cincom)
SmallWiki, cincom public store, 0.9.20 (=0.301 on scg store)
(note: the same configuration using SmaCC 2.0 from the scgStore did not
work).
So what I did: I published SmaCC 1.3 from the Cincom store in the scg
store. That way you can load everything from the scgStore and use it.
This is also what I will use for my students' repository.
To be done: Sync everything properly, especially Swazoo... it is the
really different between the scgStore and the Cincom store, and I can't
make any sense from it. I tried to sync the scg version with 6 versions
on the Cincom public store, but it never worked. So I guess that these
should be properly merged or, if that is not possible, the delta should
be put in its own package.
--
Roel Wuyts
DeComp
roel.wuyts(a)ulb.ac.be Université Libre de
Bruxelles
http://homepages.ulb.ac.be/~rowuyts/
Belgique
Board Member of the European Smalltalk User Group: www.esug.org
Hello guys,
next monday all the students here will start working on SmallWiki. I
put a version in a dedicated Store repository they can load from,
thinking that the latest version worked, but this is not the case (I
guess it is the same problem that Alex mentioned). Since yesterday Alex
told us that the version at the Cincom Store also gives problems I am
really wondering what to do (and it is quite urgent - my assistents
need to be able to load it before the course next monday).
So what version/combination of versions is known to work?
I am trying to make some time to test as much as I can myself, and will
let you know my findings.
--
Roel Wuyts
DeComp
roel.wuyts(a)ulb.ac.be Université Libre de
Bruxelles
http://homepages.ulb.ac.be/~rowuyts/
Belgique
Board Member of the European Smalltalk User Group: www.esug.org
Hello
We started this morning to work on Smallwiki, but unfortunately we encountered several issues:
- From store@SCG we cannot run smallwiki without getting an exception. So forth we are using store@Cincom, for which it is okay
- We cannot create a new page! What is the meaning of editing and viewing the content of a folder?
- Why do we have this smalltalk sequence when editing a folder?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[ "If you are not logged-in as administrator, please remove everything between the square-brackets before saving the page!"
structure children isEmpty ifFalse: [
html unorderedList: [
structure children do: [ :each |
html listItem: [ html anchorWithUrl: each url do: each title ] ] ] ].
nil]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
> Ich nehme an, ich hab beim Portieren von SmallWiki auf Squeak einen
> Bug gefunden. Es existiert keine Message 'notFound' in VW7.1. Ich
> vermute du meinst 'notFoundSignal'.
>
> Folder>>remove: aStructure
> aStructure parent: nil.
> ^(children includes: aStructure)
> ifTrue: [ children remove: aStructure ]
> ifFalse: [ self class notFound signal ]
jup, this is obviously wrong. I hope that the following code is working
without additional changes in Squeak:
Folder>>remove: aStructure
aStructure parent: nil.
^(children includes: aStructure)
ifTrue: [ children remove: aStructure ]
ifFalse: [ self class notFoundSignal signal ]
Even-tough I tried to make my code as portable as possible, there were
quite a lot of VW specific message-calls that John Brant pointed out.
If you find some more, please report them so that porting of new
versions of SmallWiki will be only a matter of a few clicks ...
What about some SmallLint rules to detect unportable non-ansi code?
> Mal sehen, ob ich in den nächsten Tagen noch weitere Sachen finde :)
Great, I am looking forward hearing from you.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
Hi lukas
- Here I cannot be connected all the time, so it would be good to have
one way to have the css locally by for example having a method
generating it.
- as I cannot be connected all the time I downloaded the style.css file
and put just near the image,
then I edited the stylesheet and put @import
"file:///Volumes/Data/Users/ducasse/Workspace/FirstCircle/Coding/
style.css";
and it worked :) cooooool
- I spent more than half and hour to upgrade to get the new version and
at the end SmallWiki could not work because
Smacc was not updated (idiot store). I think that we should pay
attention to have the right number of the right components.
I do not know what is the solution but we should try to find one.
- for the templates it would be nice to have a title above the pane so
that we know which list represent the possible choices and which one is
the current one.
- we should remove the code from the first page and put it in a page
called how to access your children programmatically
because we can scare a lot of people that way.
- removed the validator by login and modify the templates and it works.
- I started small and wanted to add a button inspect
Smalltalk.SmallWiki defineClass: #Inspect
superclass: #{SmallWiki.Action}
indexedType: #none
private: false
instanceVariableNames: ''
classInstanceVariableNames: ''
imports: ''
category: 'SmallWiki Moka'
renderContent
html submitButtonWithAction: #inspect text: 'inspect'
class>>title
^'Inspect'
I can see it in the action list, I can remove predefined actions from
the list but when I add 'inspect' nothing changes.
When I typed http://localhost:8080/?action=Inspect I can see the button
rendered but there is no inspector that
show up in VW
two questions:
1- What should I do to get the actions showing up in the actions list
once I modify the template?
2- When I redefined renderContent as
renderContent
self inspect
The inspector pops up in VW but not with html submitButtonWithAction:
#inspect text: 'inspect'
I looked at the permission but you mentioned that the default for
permission is that everybody can see the action.
I think that we should start a FAQ :)
Stef
Hi,
I would like to talk about cleaning an initialize issue.
I had the problem that Squeak Changesets don't sort the
initialize messages of some classes in the right order and it
happend that after init the subclasses of Structure, the later
init of Structure itself destroyed the inits before. So I propose
to change it to lazy init like:
SWStructure>>initialize
self initializeActions.
self initializePermissions.
SWStructure>>initializeActions
self actions
add: SWLogin;
add: SWLogout;
add: SWSearch;
add: SWTemplateEdit;
add: SWRecentChanges;
add: SWPreviousStructure;
add: SWParentStructure;
add: SWNextStructure.
SWStructure>>permissions
^permissions ifNil: [permissions := Set new]
SWStructure>>actions
^actions ifNil: [actions := Set new]
Also we should change every direct reference to 'actions' or
'permissions' to 'self actions' and 'self permissions' in this
example.
This lazy init would affect Structure, HtmlWriteStream and
Template (AFAIK).
regards
Chris Burkert
--
http://www.chrisburkert.de/
Hi all,
i vould like to propose a my students a project about building a search engine
for Smallwiki. What do you think about the idea ?
You could look at the current description of the project here :
http://www.iutc3.unicaen.fr/serge/SergeStinckwich/ProjetsMaitriseInformatiq…
Sorry, it's in french. You could add some comments on my personal Wiki page.
--
Serge Stinckwich -< )
Université de Caen>CNRS UMR 6072>GREYC>MAD /~\
http://www.iutc3.unicaen.fr/serge/ (/ |
Smalltalkers do: [:it | All with: Class, (And love: it)] _|_/
Hi,
I have done more work on porting SmallWiki AND IT IS STILL FULL
OF BUGS, but I hope that won't last a long time.
There is one yellow test in ParserTests and three in
DocumentTests. This is a problem with the Compiler. Unfortunatly
I couldn't fix it yet. But you will only need this, if you want
to embed code. Everything else runs green.
Besides this I could set up the comanche server and got the right
Response in my Mozilla (that was exciting :).
Most Links won't work. I'll fix this next week.
If you want to try it, get a fresh image (I use 3.6 #5424) and
load the following Packages from SqueakMap:
- SUnit (3.1)
- SmaCC Runtime (1.0)
- SIXX (0.1f)
- Refactoring Browser (0.94)
- KomHttpServer (6.2)
Then fileIn the attached changeset. A Workspace should open and
tell you more. If not, look at SWServer class>>defaultWorkspace.
It would be a great if one of you (familiar with the
Squeak-Compiler) could help me and figure out the problem with
the code (Maybe the new ClosureCompiler would do it?!?). Try
something with SWCode>>evaluateWith: and take a look at
SWDocumentTests>>testCode*.
I think I could publish a .sar at SqueakMap in some weeks ...
after cleaning those issues above.
Regards
Chris Burkert
--
http://www.chrisburkert.de/