- Here I cannot be connected all the time, so it would be good to
one way to have the css locally by for example having a method
- 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
style.css"; and it worked :) cooooool
You could even put the style.css and the image as resource into your
wiki and serve it from the wiki itself, so you don't need to give a
- 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
That are the timeframes I get at home too, when loading the whole code
into a fresh image. Even-tough Monticello is considered to be slow, I
would rather consider StORE to be terribly slow using remote
connections ... ;)
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.
I updated the SmaCC on the SCG-StORE with the one of Cincom StORE, so
it should be the latest. What if you try to load SmallWiki from Cincom
StORE, I think it should work with the latest version from there.
- for the templates it would be nice to have a title above the pane
that we know which list represent the possible choices and which one
is the current one.
Ok, this is an easy thing to change ...
- 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.
I am not sure: that code is put into every folder to simulate the look
of the old folders that were no subclasses of Page. Like this you have
an dynamically created list of children by default on all the folders.
But probably we should extract that code into an external method, so it
would only look like this for the end-user:
[ self renderChildrenOn: html ]
- removed the validator by login and modify the templates and it
Pages containing code can only be saved (reparsed) when being logged in
as administrator. We should probably generate more specific
error-messages, to help the user in that case.
I can see it in the action list, I can remove predefined actions from
the list but when I add 'inspect' nothing changes.
An action has to register to the structures it is able to handle, so to
make it show up on pages and folders, but not on resources, you have to
add the following code to the class-side of your action:
Page registerAction: self.
Folder registerAction: self.
When I typed http://localhost:8080/?action=Inspect
I can see the
button rendered but there is no inspector that show up in VW
HTML requires a form-tag around any form-element (buttons, combo-boxes,
list-boxes, text-input, text-areas, etc) inside a page. Your code
should look somehow like this and your browser will understand:
html form: [
html submitButtonWithAction: #inspect text: 'inspect' ]
1- What should I do to get the actions showing up in the actions list
once I modify the template?
See above :)
2- When I redefined renderContent as
The inspector pops up in VW but not with html submitButtonWithAction:
#inspect text: 'inspect'
See above :)
Probably it is easier to start with a link, as links do no require
additional HTML-tags around:
html anchorWithAction: #inspect text: 'inspect'
Hope that helps!
I have to go to university now,