28 Mar
2007
28 Mar
'07
2:03 p.m.
Just found http://www.wikimatrix.org. I'm wondering why Pier is not
listed there. Is there some other reason apart from "no one registered
it yet"?
Cheers, Elfi
28 Mar
28 Mar
2:25 p.m.
Just found http://www.wikimatrix.org. I'm
wondering why Pier is not
listed there. Is there some other reason apart from "no one registered
it yet"?
Because it is more than a Wiki, more like a CMS with full
pluggability for Seaside applications ;-)
Well, I think it could make sense to add. Do you volunteer?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
3:02 p.m.
Because it is more than a Wiki, more like a CMS with
full
pluggability for Seaside applications ;-)
I knew that, of course :-)
Well, I think it could make sense to add. Do you
volunteer?
I'd say yes, but I'm not sure I really know all features. I am able to
answer questions like: "What programming language is it implemented
in?", so if you you want me to, I could try to at least enter the basic
information there.
Elfi
3:57 p.m.
Well, I think
it could make sense to add. Do you volunteer?
I'd say yes, but I'm not sure I really know all features. I am able to
answer questions like: "What programming language is it implemented
in?", so if you you want me to, I could try to at least enter the
basic
information there.
29 Mar
29 Mar
3:09 p.m.
Ok, enter the basic information and copy the rest into
the mailing
list so that we can collect all the remaining information together.
Pier is now visible on http://www.wikimatrix.org/show/Pier. I've entered
some information I gleaned from SqueakMap browser (version/license
information), the project page (overview text), the seaside mailing list
(webservers) and other sources.
If something is wrong, it would be good to tell me ASAP, so I can
correct it. Please tell me also about all the missing information.
Cheers, Elfi
30 Mar
30 Mar
6:38 p.m.
2007/3/29, Elfi Heck <yjgalla(a)gmx.net>et>:
License Cost/ Fee: free
Webserver: (has webserver included, but can be run behind
Apache/lighty/whatever)
ACL: yes, with Windows Security
Host Blocking: yes, with Windows Security
Commercial Support: I'm pretty sure netstyle.ch will provide
commercial support if asked
Issue Tracker: http://bugs.squeak.org/ (I think)
Unicode Support: yes
Interface Languages: english only
InterWiki: yes (I think)
Other (data storage): xml, oodb, smalltalk image
Themes & Skins: yes (I think)
Embedded Video: yes (I think, probably needs testing)
Images (syntax): +image+
Ok, enter the basic information and copy the rest
into the mailing
list so that we can collect all the remaining information together.
Pier is now visible on http://www.wikimatrix.org/show/Pier. I've entered
some information I gleaned from SqueakMap browser (version/license
information), the project page (overview text), the seaside mailing list
(webservers) and other sources.
If something is wrong, it would be good to tell me ASAP, so I can
correct it. Please tell me also about all the missing information. Cheers, Elfi
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
6:58 p.m.
2007/3/29, Elfi Heck <yjgalla(a)gmx.net>et>:
I just found out that no is an answer too, so
Operating System: Windows, MacOS, Linux (maybe Solaris, *BSD and
RiscOS, but I don't know about the VM status on these machines)
License Cost/ Fee: free
Webserver: none needed
Datastorage:
Text Files: no
MySQL: no
PostgreSQL: theoricially, probably no is better
Oracle: no
SQLite: no
BerkeleyDB: no
RCS: no
Other: XML, Magman, Smalltalk image, ReferenceStream,
SmartRefernceStream (ImageSegment)
ACL: yes, with Windows Security
Authentication Backends: no (if I understood correctly)
Preconfigured Hosting: no
Support Forum: no
IRC Channel: no
Preview: no
Right-to-Left Support: Optional (if I understood correctly)
Email notification: no
Comments: no
Page Redirection: no
Conflict Handling: no
Namespaces: yes (I think)
Math formulas: no
Tables: yes (!)
CREOLE support: no
Markdown Support: no
Textile Support: no
BBCode Support: no
Emoticon Images: no (was in old versions)
Syntax Highlighting: no
Footnotes: no
Section Editing: no
Double-Click Edit: no
Toolbar: no
WYSIWYG Editing: no
Access Keys: yes (I think)
Auto Signature: no (I think)
Raw Export: yes (!)
Ok, enter the basic information and copy the rest
into the mailing
list so that we can collect all the remaining information together.
Pier is now visible on http://www.wikimatrix.org/show/Pier. I've entered
some information I gleaned from SqueakMap browser (version/license
information), the project page (overview text), the seaside mailing list
(webservers) and other sources.
If something is wrong, it would be good to tell me ASAP, so I can
correct it. Please tell me also about all the missing information. Cheers, Elfi
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
7:31 p.m.
Some more comments and a few additions:
Page Redirection: no
Yes, you can do this by adding something like into the body of your
page:
<script>window.location.href="http://www.target.com/to"</script>
Conflict Handling: no
Yes, Magritte does this.
Namespaces: yes (I think)
Yes, definitely.
Section Editing: no
Double-Click Edit: no
That was also possible some time ago. Should be easy to add if
somebody wants this.
Access Keys: yes (I think)
Yes.
CREOLE support: no
I think it would be cool if somebody implemented that. It is sort of
a standard nowadays.
Issue Tracker: http://bugs.squeak.org/ (I think)
Yes.
InterWiki: yes (I think)
I don't think so.
Themes & Skins: yes (I think)
Yes, but unfortunately there are no other choices available. It would
be cool if different skins could be included with the distribution. I
would also like to have to ugly header table to be removed (I don't
use it in my personal website) ;-)
Embedded Video: yes (I think, probably needs testing)
Yes, it works.
Images (syntax): +image+
Monospace Format:
= Monospace Text 1
= Monospace Text 2
or via html <code>
Strikethrough Format: via html <del>
Superscript Format: via html <sup>
Subscript Format: via html <sub>
Aligning Text: via html <div>
Text Indentation: via html <blockquote>
Definition Lists: via html <dl>
--
Lukas Renggli
http://www.lukas-renggli.ch
7:50 p.m.
OK, I've entered your information with the following changes:
I just found out that no is an answer too, so
The possible answers for many of the fields are No, Yes, Optional,
Plugin, Patch
Operating System: Windows, MacOS, Linux (maybe
Solaris, *BSD and
RiscOS, but I don't know about the VM status on these machines)
I put "anything Squeak runs on" in because the comparison views will
look awful when the text is too long
Webserver: none needed
I've kept my entry, because that's what "standalone" means,
and you have
yet to convince me that it doesn't run with the other two :-)
PostgreSQL: theoricially, probably no is better
I put in "no"
ACL: yes, with Windows Security
There's only Yes, No, Unknown available, so I chose "Yes"
Authentication Backends: no (if I understood
correctly)
...
Support Forum: no
IRC Channel: no
These are free text fields so I'm simply leaving them empty
Conflict Handling: no
I've kept Unknown for now because Lukas says "Yes", but the
available
options are None, Conflict Detection, Page Locking, Conflict Resolution
Namespaces: yes (I think)
"Yes", it is then
Tables: yes (!)
The choices are simple, complex, simple + complex. I put simple because
I don't know what their meaning of complex is .
Double-Click Edit: no
After reading Lukas' mail I put in "Patch"
The information icons to the right of each field point to a wiki page
where it's possible to give some details. I'll try to add additional
information given here to these pages.
I hope I didn't miss anything,
Elfi
8 p.m.
Yes, you can do this by adding something like into the
body of your
page:
<script>window.location.href="http://www.target.com/to"</script>
I thought this would be something to add to the information page, so
there it is now.
Conflict
Handling: no
Yes, Magritte does this.
CREOLE
support: no
I think it would be cool if somebody implemented that. It is sort of
a standard nowadays.
8:35 p.m.
2007/3/30, Elfi Heck <yjgalla(a)gmx.net>et>:
Yes simple is probably right. For example it is not where DocuWiki ist.
OK, I've entered your information with the
following changes:
Conflict Detection, unless I missed something
I just found out that no is an answer too, so
The possible answers for many of the fields are No, Yes, Optional,
Plugin, Patch
Operating System: Windows, MacOS, Linux (maybe
Solaris, *BSD and
RiscOS, but I don't know about the VM status on these machines)
I put "anything Squeak runs on" in because the comparison views will
look awful when the text is too long
Webserver: none needed
I've kept my entry, because that's what "standalone" means, and
you have
yet to convince me that it doesn't run with the other two :-)
PostgreSQL: theoricially, probably no is better
I put in "no"
ACL: yes, with Windows Security
There's only Yes, No, Unknown available, so I chose "Yes"
Authentication Backends: no (if I understood
correctly)
...
Support Forum: no
IRC Channel: no
These are free text fields so I'm simply leaving them empty
Conflict Handling: no
I've kept Unknown for now because Lukas says "Yes", but the
available
options are None, Conflict Detection, Page Locking, Conflict Resolution Namespaces:
yes (I think)
"Yes", it is then
Tables: yes (!)
The choices are simple, complex, simple + complex. I put simple because
I don't know what their meaning of complex is . Double-Click
Edit: no
After reading Lukas' mail I put in "Patch"
The information icons to the right of each field point to a wiki page
where it's possible to give some details. I'll try to add additional
information given here to these pages.
I hope I didn't miss anything,
Elfi
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
8:38 p.m.
2007/3/30, Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
Some more comments and a few additions:
Don't they mean something like in Wikipedia where some pages are just synonyms.
For example:
http://en.wikipedia.org/wiki/Gemstone_Systems
Page Redirection: no
Yes, you can do this by adding something like into the body of your
page:
<script>window.location.href="http://www.target.com/to"</script>
Conflict
Handling: no
Yes, Magritte does this.
Namespaces: yes (I think)
Yes, definitely.
Section Editing: no
Double-Click Edit: no
That was also possible some time ago. Should be easy to add if
somebody wants this.
Access Keys: yes (I think)
Yes.
CREOLE support: no
I think it would be cool if somebody implemented that. It is sort of
a standard nowadays.
Issue Tracker: http://bugs.squeak.org/ (I think)
Yes.
InterWiki: yes (I think)
I don't think so.
Themes & Skins: yes (I think)
Yes, but unfortunately there are no other choices available. It would
be cool if different skins could be included with the distribution. I
would also like to have to ugly header table to be removed (I don't
use it in my personal website) ;-)
Embedded Video: yes (I think, probably needs
testing)
Yes, it works.
Images (syntax): +image+
Monospace Format:
= Monospace Text 1
= Monospace Text 2
or via html <code>
Strikethrough Format: via html <del>
Superscript Format: via html <sup>
Subscript Format: via html <sub>
Aligning Text: via html <div>
Text Indentation: via html <blockquote>
Definition Lists: via html <dl>
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
9:36 p.m.
Conflict Handling: no
Yes, Magritte does this.
31 Mar
31 Mar
1:50 a.m.
Elfi Heck wrote:
Dear Elfi,
*whatever* is for linking, +whatever+ is for embedding, if 'whatever'
exists and is an image it will display in the page.
best regards
Keith
Images
(syntax): +image+
Oh, and I didn't understand this. Putting +whatever+ in a page gives me
a regular link to "whatever" I think they meant an image shown directly
on the page.
Elfi
2 Apr
2 Apr
11:10 a.m.
New subject: Image embedding (was: Re: wikimatrix.org)
Images (syntax): +image+
Oh, and I didn't understand this. Putting +whatever+ in a page gives me
a regular link to "whatever" I think they meant an image shown directly
on the page.
Elfi
1:25 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
How is "and is an image" being detected? I
tried +...+ (with an
external reference, in 1.0.9, on Linux) and actually *got* a link
and not an embedded image. Are there restrictions on the type of
reference or on the image type?
Embedding currently does not work with external links. It seems to be
possible to add quite easy, I am tempted to implement it ;-)
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
2 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
How is
"and is an image" being detected? I tried +...+ (with an
external reference, in 1.0.9, on Linux) and actually *got* a link
and not an embedded image. Are there restrictions on the type of
reference or on the image type?
Embedding currently does not work with external links. It seems to be
possible to add quite easy, I am tempted to implement it ;-)
2:50 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
2007/4/2, Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
Name: Pier-All-lr.180
Author: lr
Time: 2 April 2007, 1:59:20 pm
UUID: 418e9cd7-7a65-4664-96a0-ffdcfc064280
Ancestors: Pier-All-lr.179
Dependencies: Pier-Model-lr.135, Pier-Tests-lr.63, Pier-Seaside-lr.
150, Pier-OmniBrowser-lr.23, Pier-Security-lr.75, Pier-Blog-lr.49
Tries to embed external links marked with + as well, if the url
contains .gif, .jpg, .jpeg, .png an IMG tag will be generated,
otherwise an IFRAME (ugly, but this is what the user requested).
Other cases shoud be added, but that's it for now.
I guess IFRAME is for PDFs
Why not do a HEAD request and using the same code (and semantic) for
embedding internal and external links (MAFileModel).
Philippe
How is "and is an image" being detected? I
tried +...+ (with an
external reference, in 1.0.9, on Linux) and actually *got* a link
and not an embedded image. Are there restrictions on the type of
reference or on the image type?
Embedding currently does not work with external links. It seems to be
possible to add quite easy, I am tempted to implement it ;-) Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
6:11 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
On 02/04/07, Philippe Marschall <philippe.marschall(a)gmail.com> wrote:
I guess IFRAME is for PDFs
No, AFAIK it is like the old <frameset> and <frame>... to compose a
full web page inside another one.
--
Damien Pollet
type less, do more [ | ] http://typo.cdlm.fasmz.org
3 Apr
3 Apr
11:21 a.m.
New subject: Image embedding (was: Re: wikimatrix.org)
2007/4/2, Damien Pollet <damien.pollet(a)gmail.com>om>:
On 02/04/07, Philippe Marschall
<philippe.marschall(a)gmail.com> wrote:
That's not what I meant. To "embed" images you use <img>, to
"embed"
audio, video, flash, java you use <object>. The only way to "embed"
PDF I see is <iframe>
Philippe
I guess IFRAME is for PDFs
No, AFAIK it is like the old <frameset> and <frame>... to compose a
full web page inside another one. --
Damien Pollet
type less, do more [ | ] http://typo.cdlm.fasmz.org
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
12:19 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
No, AFAIK it
is like the old <frameset> and <frame>... to compose a
full web page inside another one.
That's not what I meant. To "embed" images you use <img>, to
"embed"
audio, video, flash, java you use <object>. The only way to "embed"
PDF I see is <iframe>
1:14 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
No, AFAIK it is like the old <frameset> and
<frame>... to compose a
full web page inside another one.
That's not what I meant. To "embed" images you use <img>, to
"embed"
audio, video, flash, java you use <object>. The only way to "embed"
PDF I see is <iframe>
1:23 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
2007/4/3, Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
<object> is naughty.
Ya, lets hope for <audio> and <video>
No, AFAIK it is like the old <frameset> and
<frame>... to compose a
full web page inside another one.
That's not what I meant. To "embed" images you use <img>, to
"embed"
audio, video, flash, java you use <object>. The only way to "embed"
PDF I see is <iframe> Unfortunately Pier cannot know the size of the
contents (audio, video, flash, java applet, whatever) and <object>
always takes a default size independent of the actual content. Does
anybody know a hack/fix for that?
When talking about "size", we mean dimension, not filesize or playlenght,
right?
All I'm really asking for is embedding internal and external video's,
flash, whatever, ... the same way (and with the same code). Right now
internal uses <object>, external uses <iframe>. That is very
inconsistent IMHO.
I have two proposals:
1. extend the link syntax:
+http://tinyurl/video.mpeg:witdth:640:height:480+
2. Extend PRFile to include more meta information depending on the
type (eg. a video would have width and height, a Java Applet would
have parameters, ...
Then we make a PRExternalFile that instead of file upload has an external url.
Philippe
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
1:47 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
When talking about "size", we mean
dimension, not filesize or
playlenght, right?
Exactly, see my second mail.
All I'm really asking for is embedding internal
and external video's,
flash, whatever, ... the same way (and with the same code). Right now
internal uses <object>, external uses <iframe>. That is very
inconsistent IMHO.
Indeed, this was just a quick hack. Quite ugly all in all, especially
the guessing of the file-type depending on the extension. A head
request that is cached would be much cooler.
I have two proposals:
1. extend the link syntax:
+http://tinyurl/video.mpeg:witdth:640:height:480+
I tried to avoid that, most other wikis do that. Probably there is no
other way around this.
2. Extend PRFile to include more meta information
depending on the
type (eg. a video would have width and height, a Java Applet would
have parameters, ...
And where do you get this information from?
Then we make a PRExternalFile that instead of file
upload has an
external url.
I am lost, could you rephrase proposition 2?
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
7:25 p.m.
New subject: Image embedding (was: Re: wikimatrix.org)
2007/4/3, Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
Make a description, let the user provide it there is no where esle we
can get it from.
Right now we have PRFile which has only a MAFileDescription which more
or less a MAFileModel that only stores the binary contents and the
filename (and computes the mime-type). Now for video files we
additionally store the width and height. Either in MAFileModel
(probably not possible because it's orthogonal to internal <->
external), PRFile or somewhere else.
When you upload a video file you can additionally provide the width
and height of the video.
Same for flash, java, ...
Now for url we make a new kind of structure (PRExternalResource or
whatever) that is very much like PRFile but does not have a
MAFileDescription but a MAResourceDescription (or whatever) that is
just the url. It has the same metainformation for videos like a
PRFile.
The cool thing about that is that it's very uniform. It's just a
structure that you embed.
Philippe
When talking
about "size", we mean dimension, not filesize or
playlenght, right?
Exactly, see my second mail.
All I'm really asking for is embedding
internal and external video's,
flash, whatever, ... the same way (and with the same code). Right now
internal uses <object>, external uses <iframe>. That is very
inconsistent IMHO.
Indeed, this was just a quick hack. Quite ugly all in all, especially
the guessing of the file-type depending on the extension. A head
request that is cached would be much cooler.
I have two proposals:
1. extend the link syntax:
+http://tinyurl/video.mpeg:witdth:640:height:480+
I tried to avoid that, most other wikis do that. Probably there is no
other way around this.
2. Extend PRFile to include more meta information
depending on the
type (eg. a video would have width and height, a Java Applet would
have parameters, ...
And where do you get this information from? Then we make a
PRExternalFile that instead of file upload has an
external url.
I am lost, could you rephrase proposition 2? Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
4 Apr
4 Apr
3:17 a.m.
New subject: Image embedding (was: Re: wikimatrix.org)
2007/4/3, Philippe Marschall <philippe.marschall(a)gmail.com>om>:
2007/4/3, Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
<object> is naughty.
Ya, lets hope for <audio> and <video>
http://video.google.com/videoplay?docid=5545573096553082541
No, AFAIK it is like the old <frameset> and
<frame>... to compose a
full web page inside another one.
That's not what I meant. To "embed" images you use <img>, to
"embed"
audio, video, flash, java you use <object>. The only way to "embed"
PDF I see is <iframe> Unfortunately
Pier cannot know the size of the
contents (audio, video, flash, java applet, whatever) and <object>
always takes a default size independent of the actual content. Does
anybody know a hack/fix for that?
When talking about "size", we mean dimension, not filesize or playlenght,
right?
All I'm really asking for is embedding internal and external video's,
flash, whatever, ... the same way (and with the same code). Right now
internal uses <object>, external uses <iframe>. That is very
inconsistent IMHO.
I have two proposals:
1. extend the link syntax:
+http://tinyurl/video.mpeg:witdth:640:height:480+
2. Extend PRFile to include more meta information depending on the
type (eg. a video would have width and height, a Java Applet would
have parameters, ...
Then we make a PRExternalFile that instead of file upload has an external url.
Philippe
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
6235
days inactive
6242
days old
26 comments
5 participants
participants (5)
-
Damien Pollet -
Elfi Heck -
Keith Hodges -
Lukas Renggli -
Philippe Marschall