Hi Frank,
> With some easy things in css I was able to realize what I want in
> HTML. But what do you think about syntax extension of pier to do
> such things like
> :indented_text.
> I found this behavior in another wiki and it helps for readability
> of the text.
> Sure I can use HTML but writing of such things written above is
> much easier.
I tried to keep the syntax as simple as possible. However there were
several requests lately for that kind of things. I don't really know,
how we could implement that the simplest without bloating the wiki-
syntax and while keeping the visitors small that transform the AST
into different output-formats (HTML, Text, Latex, etc).
The best idea I cam up so far is to add some sort of XML-Tags that
can be parsed in a generic fashion, so that extensions can register
their own tags. Something along ...
<pier:indented>
The time is now: <pier:smalltalk>Time now</pier:smalltalk>
</pier:indented>
Would that help? Is something like that of generic interest?
> I've been searching in the code for the place of translation from
> *..* and others to HTML and coming down to PRDocumentScanner
> scanForToken and see the scannerDefinitionComment on class-side.
> The next step to define a new element would be very interesting.
The scanner and parser is automatically generated from the respective
definitions using SmaCC, so you probably don't want to change these
methods manually ;-)
If you only want to do some simple string transformations when
generating HTML you could simply patch the methods from the protocol
#visiting-document in the class PRViewRenderer.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
Hi, Lukas!
I can understand that a simple syntax keep it easy writing some content.
My intention was keeping fingertips writing my ideas in the wiki. On the other
side the idea using some sort of XML-tags bring us the possibility write
some extensions like a building set.
I'm not so familiar with XML but in my understanding of this we could bring
the translation to other formats into the tags. With an open repository of
these buildingblocks everybody can decide what he want.
The loosers in this kind of solution are my fingers ;-).
> > Sure I can use HTML but writing of such things written above is
> > much easier.
>
> I tried to keep the syntax as simple as possible. However there were
> several requests lately for that kind of things. I don't really know,
> how we could implement that the simplest without bloating the wiki-
> syntax and while keeping the visitors small that transform the AST
> into different output-formats (HTML, Text, Latex, etc).
>
> The best idea I cam up so far is to add some sort of XML-Tags that
> can be parsed in a generic fashion, so that extensions can register
> their own tags. Something along ...
>
> <pier:indented>
> The time is now: <pier:smalltalk>Time now</pier:smalltalk>
> </pier:indented>
>
> Would that help? Is something like that of generic interest?
>
> > I've been searching in the code for the place of translation from
> > *..* and others to HTML and coming down to PRDocumentScanner
> > scanForToken and see the scannerDefinitionComment on class-side.
> > The next step to define a new element would be very interesting.
>
> The scanner and parser is automatically generated from the respective
> definitions using SmaCC, so you probably don't want to change these
> methods manually ;-)
My mistake. Is it possible to add a comment "Do not touch, it's generated"?
Cheers,
Frank
> If you only want to do some simple string transformations when
> generating HTML you could simply patch the methods from the protocol
> #visiting-document in the class PRViewRenderer.
>
> Cheers,
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>
>
>
Hi all,
I want to indent some parts of text in pier. But I didn't see in the syntax-introduction these things. Can anybody advise me for this.
Thanks in advance.
Cheers,
Frank
Hi,
I'm new to smalltalk, seaside and pier. I want to use pier to host a small
site, and if possible, I'd like to change the way internal links to other
pages are rendered, so that the wiki text:
*Introduction>introduction*
produces the link:
http://localhost:9090/seaside/pier/information/introduction
instead of:
http://localhost:9090/seaside/pier/information/introduction?view=PRDefaultV…
Both links return the same URL when typed into the browser, so clearly
view is the default command. I've tried searching around for information
about this but I couldn't find anything obvious to me. While browsing the
source code, I came across WAUrl adaptToContext: and WAAnchorTag goto:,
which look potentially relevant, but I'm honestly not sure if I'm on the
right track. I'd appreciate it if someone could point me in the right
direction. Also, if this is a really bad idea for some reason, that would
also be good to know.
I'm using Sqeak-3.8, Seaside 2.63a3-lr.51 and Pier-all-lr.81
Thanks,
Brian
Hi
StellDichEin is a Pier addon that allows you to create VCards and ICal
events and todos in Pier like you would create structures (eg pages).
Later these can be downloaded and imported (iCalendar, Outlook, ....).
It not tested very roughly and very likely has several bugs.
It can be found at http://mc.lukas-renggli.ch/pieraddons/ and depends
on the following packages:
- NetworkAddress (http://mc.lukas-renggli.ch/magritteaddons/)
- ICal (http://squeaksource.com/ical/)
- ICalMagritte (http://squeaksource.com/ical/)
There is also a configuration map that should load all these automatically.
There is also a very simple poll in the same repository.
Cheers
Philippe
Hi lukas
I wanted to know this was possible to specify how an field should be
saved and reloaded.
For example I wanted to save a date and reload it.
I added
MADateDescription>>parseString: aString
^ self parseString: aString protected: [ aString asDate ].
to MADateDescription :)
but I have the impression that been able to specify at the
description level
the way the values are saved and filed in would make sense.
I checked on my old version of MA, but I could not find how the
MADescription
itself was describing the condition because it would be the same process
may be been able to specify a block or a selector for each of the
action would be cool.
Lukas?
Stef
Hi all,
I have an instance of pier running in an image which seems to be hosed. The problem is that while Pier will still display pages, it will not allow them to be edited. This started sometime after I put in a back ground process to periodically save the image.
So, I need to know how to migrate the contents of this wiki to another image. Any tips on this? BTW, I can still edit methods in the System browser, and execute workspace code.
Thanks,
Brett Taylor
Hi all,
I'm searching the right way for saving my work in pier every 5 minutes automaticly. I've tryed to connect with the http://smallwiki.unibe.ch/smallwiki but no answer.
Thanks in advance
Cheers,
Frank
Please could someone tell me the proper way to change the
administrator's password in Pier?
Last week, I could do it by using the Pier Browser, exploring the root,
and sending a password: message to the adminUser instance.
I've now created a new image, with the latest Pier packages from Squeak
Map. Even though the password appears to change in the instance, the
old passwords (user=admin, password=pier) remain in use.
I realise I'm probably doing something stupid :-)
Thanks for any help,
Duncan.
P.S. With the latest Squeak Map Pier package the Pier Browser doesn't
appear to be added to the Tools flap like last time.