is there anywhere where you can get a quick summary of the different
add ons?
a few are detailed on squeaksource but not all of them. loading in
from monticello
and checking them out is always an option, but i wanted to see if
there was a quicker
route.
Shout Pier =>
Syntax highlights Smalltalk expressions and methods. The color scheme
can be con gured using a CSS style-sheet.
congured should be configured .
I'm using the blog on my site for everything I like to add
there. But then I would like to subscribe my blog in
planet smalltalk. For such meta blogs the mixture of things
is not wanted. So how would you solve this?
I could have a blog per topic or at least one for things
being smalltalk. Then I only need to tweak post ticker
component to include more than one blog.
I would rather use the opposite approach. I like to put
everything in one blog but have the ability to filter
the posts by tag or anything else. This might make the
subscription Url more ugly.
What do you think?
Norbert
SSean,
Use SIXX. During SIXX testing I was able to move a Pier kernel from Squeak to GemStone.
If you run into issues, I will be very interested to fix them, since at the moment I think SIXX is the best alternative.
Dale
----- "Sean Allen" <sean(a)monkeysnatchbanana.com> wrote:
| i want to start playing around with putting together a site in pharo
|
| on my laptop and then when i have it mostly completed, moving it over
|
| to a GLASS installation.
| i've scanned back through the list since i first signed up last year
|
| ( and found numerous interesting tidbits i had missed ), but i can't
|
| find anything on this:
|
| if i want to move an existing pier site out of a pharo/squeak image
| and into glass, how do i do that? i assume it would be using
| monticello. i'm not sure though, how much i need to move. i'm sure
| there is a simple answer to this, but i still haven't really used
| monticello much as i have been able to get by without using it yet.
|
|
| _______________________________________________
| Magritte, Pier and Related Tools ...
| https://www.iam.unibe.ch/mailman/listinfo/smallwiki
i want to start playing around with putting together a site in pharo
on my laptop and then when i have it mostly completed, moving it over
to a GLASS installation.
i've scanned back through the list since i first signed up last year
( and found numerous interesting tidbits i had missed ), but i can't
find anything on this:
if i want to move an existing pier site out of a pharo/squeak image
and into glass, how do i do that? i assume it would be using
monticello. i'm not sure though, how much i need to move. i'm sure
there is a simple answer to this, but i still haven't really used
monticello much as i have been able to get by without using it yet.
I have added google analytics to my site. I configured
it to strip _s, _n and _k from the url. On every page
there is the canonical url embedded.
In my statistics there is sometimes still the link counter
of an url included so there appears
/blog?15=
/blog?13=
and so on.
Does anybody know how to get this right?
thanks,
Norbert
Hi,
I was totally confused about my blog today. I always
expected that people can comment on blog posts. Having
a look today first showed that there was no entry form
for entering a comment.
I started to fiddle around with the permissions on the
blog page but this was kinda strange. As soon as I added
the "Add commment" permission to others a link "add"
was added at the bottom beside login and view. Clicking
on the link opened the normal add command that would
let me add post, component,...
Removing the permission again removed the link again. I
know this sounds strange and I'm also sure that it is
probably not what really happened.
Now it is so that only the first post has the comment
add form and no other post. Well, it is the only one
in this month so it could also be that. Aren't all blog
post supposed to be commentable?
thanks,
Norbert
Hello to all,
I'm involved in a project which uses the Pier wiki. We hope that this
project will have mass appeal and involve many users. Unfortunately,
we've seen a problem with the edit box. If one pastes something from a
non-UTF-8 compatible world processor, it is rejected with an error
message reading, "Input is Invalid." Unfortunately, this is not a very
helpful error message, and it will make using the Pier wiki impossible
for those of us who aren't at least mid-level geeks. Would it be
possible to make some changes which would allow a more user-friendly
error message?
I see two possible ways to handle this.
1.) Replace the current message with a message that reads, "Your input
cannot be read because it is not UTF-8 compatible. Please set your
word-processor to produce UTF-8 compatible text and try pasting your
input again." Such an error message could even connect to Pier's help
system which could explain how to set various word-processors for UTF-8.
I'm not a Squeak programmer, but I'd be happy to write help text for the
word processing programs I own.
2.) The second is to devise a more forgiving edit window. Instead of
giving an error message and rejecting the input, it could accept the
input and replace characters it can't read with a question mark, or one
of those square boxes, then output an error message, something like:
"There was a problem reading your input because your word processor is
not set to UTF-8. Characters which could not be read have been replaced
with a "?". Please click here to continue." I think this is the better
of the two alternatives, though obviously it involves more programming time.
A more sophisticated version of the second solution could present users
with a small, pop-up edit box containing the text that is causing
problems. The users could then use their keyboards to make the
appropriate changes.
As things stand now, the edit box is very "user-unfriendly." I don't, of
course, insist that my solutions be used - it's entirely possible that a
better way exists than I imagine above - but the present situation will
make things very difficult for users who don't have serious computing
skills.
Thanks in advance for any help you can offer.
Alex
> GemStone can't migrate an object that is on the stack (as a receiver), this means that the normal Magritte mechanism for creating variables doesn't work in GemStone...callers of readUsing: ... the solution for GemStone is to flip the logic:
I don't understand the problem. As far as I understand this only
appears when the MAAutoSelectorAccessor is used. Magritte itself (with
the exception of the respective test case) and Pier does not make use
of this functionality.
Personally I never use MAAutoSelectorAccessor, I rather use the
refactoring tools. If nobody opposes I would propose to remove it?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
