17 Dec
2003
17 Dec
'03
5:42 p.m.
david
when do you ***really*** plan to deliver the role interface?
Stef
1:46 p.m.
On 18 déc. 03, at 11:58, David Vogel wrote:
sorry stef, I had to deal with some cookie bug from
swazzo...
Did you fix it and publish it on swazoo.This is important to report
this kind of bug to janko.
Jankoi how do we proceed? should david send you the fix?
Stef
Alex, do you have time tomorrow (friday) to install it?
cheers,
dave.
ducasse wrote:
david
when do you ***really*** plan to deliver the role interface?
Stef
2:19 p.m.
sorry stef, I
had to deal with some cookie bug from swazzo...
Did you fix it and publish it on swazoo.This is important to report
this kind of bug to janko. Jankoi how do we proceed? should david send
you the fix? 
2:39 p.m.
Hi guys,
Nice to hear from you after a long time :)
Cookie mgmnt is not a Swazoo duty, it only provides all infrastructure
for it. You set a cookie by properly constructing a HTTPResponse.
Example from Aida:
AIDASite answerTo: aRequest
...
response := Swazoo.HTTPResponse ok.
response entity: <your html response>.
session cookie ifFalse: [response cookie: (self cookieHeaderFor: session)].
^response
AIDASite cookieHeaderFor: aSession
"set a permanent cookie on client (up to year 2010, enough?) "
"for secure sessions different id as for usual ! "
| id |
id := aSession lastRequest isEncrypted
ifTrue: [aSession secureId]
ifFalse: [aSession id].
^(WriteStream on: String new)
nextPutAll: self cookieName;
nextPutAll: '=';
nextPutAll: id printString;
nextPutAll: '; path=/; expires=Friday, 01-Jan-2010 01:00:00 GMT';
contents
In Aida I extended HTTPRequest with a method:
idFromCookie
"return session id from our cookie. nil if not aida field present in
cookie"
| stream part |
stream := self cookie readStream.
[stream atEnd] whileFalse:
[part := stream upTo: $; .
('aida9357*' match: part) ifTrue:
[^part readStream upTo: $=; upToEnd] ].
^nil
.. but event that hadn't been nessesary.
Cheers
Janko
Lukas Renggli wrote:
Already a long time ago, I decided not to support cookies in SmallWiki
anymore. Still there are probably some deprecated messages dealing
with that, but I suggest not to cookies as they are generally not
worth the troubles. Therefor I suspect that the "cookie-bug" isn't a
problem with Swazoo but with SmallWiki ...
Cheers,
Lukas
--
Janko Mivsek
Systems Architect
EraNova d.o.o.
Ljubljana, Slovenia
http://www.eranova.si
sorry stef, I had to deal with some cookie bug from
swazzo...
Did you fix it and publish it on swazoo.This is important to report
this kind of bug to janko. Jankoi how do we proceed? should david
send you the fix?
2:41 p.m.
Guys,
You can freely fix/extend/improve Swazoo and post it as a new version on
Cincom Public Repository. You are actually very encouraged to do that.
My duty is only to maintain some discipline and to make a version to be
put on Cincom Smalltalk CD. So, you are welcome!
Janko
ducasse wrote:
On 18 déc. 03, at 11:58, David Vogel wrote:
--
Janko Mivsek
Systems Architect
EraNova d.o.o.
Ljubljana, Slovenia
http://www.eranova.si
sorry stef, I had to deal with some cookie bug
from swazzo...
Did you fix it and publish it on swazoo.This is important to report
this kind of bug to janko.
Jankoi how do we proceed? should david send you the fix?
Stef
Alex, do you have time tomorrow (friday) to install it?
cheers,
dave.
ducasse wrote:
david
when do you ***really*** plan to deliver the role interface?
Stef
22 Dec
22 Dec
4:10 p.m.
hello,
I put a version of the admin tool 'SmallWiki.Admin' (manage roles and
users) on the cincom store.
remarks:
1) make sure that the versions af the children parents are correct, if
not do something like:
structure root fixVersion
Structure >> fixVersion
"make sure that every child has correct parent"
self childrenDo:
[:aChild |
aChild parent: self.
aChild fixVersion]
2) after loading the admin tool, make sure that the admin link will show
up in the template (thanks lukas):
SmallWiki.TemplateBodyActions allInstances do: [ :each |
each actions add: SmallWiki.AdminAction ]
to scg:
I also loaded the admintool on kilana
I saved a image before and put it into directory:
......./BackupBeforeInstallingRoleManagement
have fun,
david.
merry christmas!
7 Jan
7 Jan
9 a.m.
Hi david
from what I understood the last changes of lukas cut the grass under
your feet.
I know how it is painful to work on something changing, that's why the
strategy is to
cut in small parts the admin tools and push that in the mainstream :)
this way lukas will automatically fixed them when refactoring or
improving Smallwiki.
As soon as the role interface and admin interface are back online, I
will add new wiki
to try the roles. :)
When do you think that your admin tool will be back in life?
Stef
On 22 déc. 03, at 16:10, david vogel wrote:
hello,
I put a version of the admin tool 'SmallWiki.Admin' (manage roles and
users) on the cincom store.
remarks:
1) make sure that the versions af the children parents are correct, if
not do something like:
structure root fixVersion
Structure >> fixVersion
"make sure that every child has correct parent"
self childrenDo:
[:aChild |
aChild parent: self.
aChild fixVersion]
2) after loading the admin tool, make sure that the admin link will
show up in the template (thanks lukas):
SmallWiki.TemplateBodyActions allInstances do: [ :each |
each actions add: SmallWiki.AdminAction ]
to scg:
I also loaded the admintool on kilana
I saved a image before and put it into directory:
......./BackupBeforeInstallingRoleManagement
have fun,
david.
merry christmas!
9:15 a.m.
hi stef,
I'll fix it on friday this week. I'll let you know, when it's set up on
kilana again.
cheers,
david.
ducasse wrote:
Hi david
from what I understood the last changes of lukas cut the grass under
your feet.
I know how it is painful to work on something changing, that's why the
strategy is to
cut in small parts the admin tools and push that in the mainstream :)
this way lukas will automatically fixed them when refactoring or
improving Smallwiki.
As soon as the role interface and admin interface are back online, I
will add new wiki
to try the roles. :)
When do you think that your admin tool will be back in life?
Stef
On 22 déc. 03, at 16:10, david vogel wrote:
hello,
I put a version of the admin tool 'SmallWiki.Admin' (manage roles and
users) on the cincom store.
remarks:
1) make sure that the versions af the children parents are correct,
if not do something like:
structure root fixVersion
Structure >> fixVersion
"make sure that every child has correct parent"
self childrenDo:
[:aChild |
aChild parent: self.
aChild fixVersion]
2) after loading the admin tool, make sure that the admin link will
show up in the template (thanks lukas):
SmallWiki.TemplateBodyActions allInstances do: [ :each |
each actions add: SmallWiki.AdminAction ]
to scg:
I also loaded the admintool on kilana
I saved a image before and put it into directory:
......./BackupBeforeInstallingRoleManagement
have fun,
david.
merry christmas!
10:57 a.m.
excellent and we should talk about your master.... :)
On 7 janv. 04, at 09:15, David Vogel wrote:
hi stef,
I'll fix it on friday this week. I'll let you know, when it's set up
on kilana again.
cheers,
david.
ducasse wrote:
Hi david
from what I understood the last changes of lukas cut the grass under
your feet.
I know how it is painful to work on something changing, that's why
the strategy is to
cut in small parts the admin tools and push that in the mainstream :)
this way lukas will automatically fixed them when refactoring or
improving Smallwiki.
As soon as the role interface and admin interface are back online, I
will add new wiki
to try the roles. :)
When do you think that your admin tool will be back in life?
Stef
On 22 déc. 03, at 16:10, david vogel wrote:
hello,
I put a version of the admin tool 'SmallWiki.Admin' (manage roles
and users) on the cincom store.
remarks:
1) make sure that the versions af the children parents are correct,
if not do something like:
structure root fixVersion
Structure >> fixVersion
"make sure that every child has correct parent"
self childrenDo:
[:aChild |
aChild parent: self.
aChild fixVersion]
2) after loading the admin tool, make sure that the admin link will
show up in the template (thanks lukas):
SmallWiki.TemplateBodyActions allInstances do: [ :each |
each actions add: SmallWiki.AdminAction ]
to scg:
I also loaded the admintool on kilana
I saved a image before and put it into directory:
......./BackupBeforeInstallingRoleManagement
have fun,
david.
merry christmas!
19 Dec
19 Dec
7:08 p.m.
New subject: structures parent child
hi lukas,
I copied the image form kilana to my machine and tested some stuff.
- there might be a problem with the versioning: the version of a
structure is not the same as the version of the structures children parent.
(structure version != structure children first parent version)
...I'm not sure if the version should always be the same.
- another question:
I want the admin link to be visible just like the other ones: view,
edit, contents etc.,
what is the best way to do this? do I have to modify each structure's
template?
cheers,
david.
9:25 p.m.
New subject: structures parent child
- there might be a problem with the versioning: the
version of a
structure is not the same as the version of the structures children
parent.
(structure version != structure children first parent version)
...I'm not sure if the version should always be the same.
No, all structures are versioned independently. There is no need to
create new version for the parent, if a child changes.
- another question:
I want the admin link to be visible just like the other ones: view,
edit, contents etc., what is the best way to do this? do I have to
modify each structure's template?
There are only about 3 templates defined on this wiki: the root, the
SmallWiki folder and the CaroAndBot folder. As you know, these
instances are shared among all their corresponding child structures, so
you have to change only those 3 places.
Weak as I am, I would use the powerful reflection mechanism of
Smalltalk and do something like:
SmallWiki.TemplateBodyActions allInstances do: [ :each |
each actions add: SmallWiki.AdminAction ]
Actually I would like to integrate some other actions into the central
admin menu-item, like the history, the template and the property editor
(something new I wrote yesterday night). We should also think about a
way to show the actions of a page in a tree-like structure, as there
are too many items to show in one line
Admin
History
Properties
Template
Components
Configuration
Stylesheet
Security
User
Roles
Permissions
...
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
20 Dec
20 Dec
9:47 a.m.
New subject: structures parent child
On 19 déc. 03, at 21:25, Lukas Renggli wrote:
I think that for admin this makes sense.
For standard user requiring that is the smell that there is two much
may be in such a case we should have a more... button that show the
optional one.
stef
- there might
be a problem with the versioning: the version of a
structure is not the same as the version of the structures children
parent.
(structure version != structure children first parent version)
...I'm not sure if the version should always be the same.
No, all structures are versioned independently. There is no need to
create new version for the parent, if a child changes.
- another question:
I want the admin link to be visible just like the other ones: view,
edit, contents etc., what is the best way to do this? do I have to
modify each structure's template?
There are only about 3 templates defined on this wiki: the root, the
SmallWiki folder and the CaroAndBot folder. As you know, these
instances are shared among all their corresponding child structures,
so you have to change only those 3 places.
Weak as I am, I would use the powerful reflection mechanism of
Smalltalk and do something like:
SmallWiki.TemplateBodyActions allInstances do: [ :each |
each actions add: SmallWiki.AdminAction ]
Actually I would like to integrate some other actions into the central
admin menu-item, like the history, the template and the property
editor (something new I wrote yesterday night). We should also think
about a way to show the actions of a page in a tree-like structure, as
there are too many items to show in one line
Admin
History
Properties
Template
Components
Configuration
Stylesheet
Security
User
Roles
Permissions
...
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
12:28 p.m.
New subject: structures parent child
Lukas Renggli wrote:
yes, but I wanted to say that a child doesn't reference back to the
right version of the parent.
e.g node01 (version 500) has child node011, but node011 has parent
node01 (version 477)
this is a problem for the admin tool, because I want to be able to
collect all parent roles from e.g node011 in the structure-tree.
otherwise I would have to ask every single node in the tree if it is the
parent of node011 :-(
...to render the admin menu I used some simple mechanism that renders a
menu according to a class and their subclasses:
AdminAction
AdminSecurity
AdminUsers
AdminRoles
AdminStructuresTree
eg. do AdminAction: render the menu of their subclasses (Security
and StructuresTree)
do AdminSecurity: render super, render the menu of their
subclasses (AdminUsers and AdminRoles)
but this system is not very useful and fexible 'cause it uses only the
structure of classes and their subclasses and this should't have
anything to do with a html menu to render...
cheers,
david
- there might
be a problem with the versioning: the version of a
structure is not the same as the version of the structures children
parent.
(structure version != structure children first parent version)
...I'm not sure if the version should always be the same.
No, all structures are versioned independently. There is no need to
create new version for the parent, if a child changes. - another question:
I want the admin link to be visible just like the other ones: view,
edit, contents etc., what is the best way to do this? do I have to
modify each structure's template?
There are only about 3 templates defined on this wiki: the root, the
SmallWiki folder and the CaroAndBot folder. As you know, these
instances are shared among all their corresponding child structures,
so you have to change only those 3 places.
Weak as I am, I would use the powerful reflection mechanism of
Smalltalk and do something like:
SmallWiki.TemplateBodyActions allInstances do: [ :each |
each actions add: SmallWiki.AdminAction ]
Actually I would like to integrate some other actions into the central
admin menu-item, like the history, the template and the property
editor (something new I wrote yesterday night). We should also think
about a way to show the actions of a page in a tree-like structure, as
there are too many items to show in one line
Admin
History
Properties
Template
Components
Configuration
Stylesheet
Security
User
Roles
Permissions
...
Cheers,
Lukas
1:27 p.m.
New subject: structures parent child
- there might be a problem with the versioning: the
version of a
structure is not the same as the version of the structures children
parent.
(structure version != structure children first parent version)
...I'm not sure if the version should always be the same.
No, all structures are versioned independently. There is no need to
create new version for the parent, if a child changes. to render the admin menu I used some simple mechanism
that renders a
menu according to a class and their subclasses:
AdminAction
AdminSecurity
AdminUsers
AdminRoles
AdminStructuresTree
eg. do AdminAction: render the menu of their subclasses (Security
and StructuresTree)
do AdminSecurity: render super, render the menu of their
subclasses (AdminUsers and AdminRoles)
but this system is not very useful and fexible 'cause it uses only the
structure of classes and their subclasses and this should't have
anything to do with a html menu to render...
Yeah, we should look for something more declarative, like having an
explicit action that can hold an arbitrary number of sub-actions. I
think users should be able to specify the actions as flat/nested as
they prefer in the template-editor.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
7414
days inactive
7435
days old
14 comments
5 participants
participants (5)
-
david vogel -
David Vogel
-
ducasse -
Janko Mivsek -
Lukas Renggli