8:58 a.m.
Looking through the various Pier documentation, I see that code has
changed and thus there are several different explanations of how to
change stylesheets. I want to use a different css stylesheets but I
can't find out where to change it/them. Isn't there one place to point
Pier to one stylesheet?
BTW: for some reason, I have no style sheet at all for Pier. I don't
know what I did, but I didn't edit any code... I must have loaded a new
version of some package. Anyway, unless it stomped on something else, if
I can learn where to change the stylesheet pointer, It'd give me a start.
thanks,
brad
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
1:16 p.m.
On Fri, 2007-02-16 at 23:58 -0800, Brad Fuller wrote:
Looking through the various Pier documentation, I see that code has
changed and thus there are several different explanations of how to
change stylesheets. I want to use a different css stylesheets but I
can't find out where to change it/them. Isn't there one place to point
Pier to one stylesheet?
BTW: for some reason, I have no style sheet at all for Pier. I don't
know what I did, but I didn't edit any code... I must have loaded a new
version of some package. Anyway, unless it stomped on something else, if
I can learn where to change the stylesheet pointer, It'd give me a start.
It is in PRPierLibrary>>style and it is pointing to lukas style sheet
on www.lukas-renggli.ch.
Norbert
5:48 p.m.
Norbert Hartl wrote:
On Fri, 2007-02-16 at 23:58 -0800, Brad Fuller wrote:
> Looking through the various Pier documentation, I see that code has
> changed and thus there are several different explanations of how to
> change stylesheets. I want to use a different css stylesheets but I
> can't find out where to change it/them. Isn't there one place to point
> Pier to one stylesheet?
>
> BTW: for some reason, I have no style sheet at all for Pier. I don't
> know what I did, but I didn't edit any code... I must have loaded a new
> version of some package. Anyway, unless it stomped on something else, if
> I can learn where to change the stylesheet pointer, It'd give me a start.
>
It is in PRPierLibrary>>style and it is pointing to lukas style sheet
on www.lukas-renggli.ch.
I've seen that in docs/msgs, but I actually don't have
PRPierLibrary>>style, it's styleCss. And it not a file pointer but
appears to be the content of a css file - with a comment about cc Lukas
and import statements like his file:
@import url(basic.css)
etc..
maybe I need to upgrade? I have Pier-Model-lr.105, Pier-Seaside-lr.108,
etc...
9:24 p.m.
Brad Fuller wrote:
Norbert Hartl wrote:
> On Fri, 2007-02-16 at 23:58 -0800, Brad Fuller wrote:
>> Looking through the various Pier documentation, I see that code has
>> changed and thus there are several different explanations of how to
>> change stylesheets. I want to use a different css stylesheets but I
>> can't find out where to change it/them. Isn't there one place to point
>> Pier to one stylesheet?
>>
>> BTW: for some reason, I have no style sheet at all for Pier. I don't
>> know what I did, but I didn't edit any code... I must have loaded a new
>> version of some package. Anyway, unless it stomped on something else, if
>> I can learn where to change the stylesheet pointer, It'd give me a start.
>>
> It is in PRPierLibrary>>style and it is pointing to lukas style sheet
> on www.lukas-renggli.ch.
I've seen that in docs/msgs, but I actually don't have
PRPierLibrary>>style, it's styleCss. And it not a file pointer but
appears to be the content of a css file - with a comment about cc Lukas
and import statements like his file:
@import url(basic.css)
etc..
maybe I need to upgrade? I have Pier-Model-lr.105, Pier-Seaside-lr.108,
etc...
I did upgrade, and it's still the same.
So, changed styleCss to:
^ '@import "file://styles/style.css";'.
as the styles directory is a subdir of where the image is located. But,
no go.
(wow, seaside configuration page is a lot different. The dispacher
browser selection goes no where - should it?)
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
12:07 a.m.
New subject: Pier Stylesheets - Help!
Brad Fuller wrote:
Brad Fuller wrote:
> Norbert Hartl wrote:
>> On Fri, 2007-02-16 at 23:58 -0800, Brad Fuller wrote:
>>> Looking through the various Pier documentation, I see that code has
>>> changed and thus there are several different explanations of how to
>>> change stylesheets. I want to use a different css stylesheets but I
>>> can't find out where to change it/them. Isn't there one place to
point
>>> Pier to one stylesheet?
>>>
>>> BTW: for some reason, I have no style sheet at all for Pier. I don't
>>> know what I did, but I didn't edit any code... I must have loaded a new
>>> version of some package. Anyway, unless it stomped on something else, if
>>> I can learn where to change the stylesheet pointer, It'd give me a
start.
>>>
>> It is in PRPierLibrary>>style and it is pointing to lukas style sheet
>> on www.lukas-renggli.ch.
> I've seen that in docs/msgs, but I actually don't have
> PRPierLibrary>>style, it's styleCss. And it not a file pointer but
> appears to be the content of a css file - with a comment about cc Lukas
> and import statements like his file:
>
> @import url(basic.css)
> etc..
>
> maybe I need to upgrade? I have Pier-Model-lr.105, Pier-Seaside-lr.108,
> etc...
I did upgrade, and it's still the same.
So, changed styleCss to:
^ '@import "file://styles/style.css";'.
as the styles directory is a subdir of where the image is located. But,
no go.
How come nobody has PRPierLibrary>>styleCss method?
This class seems to have all of the default css styles of Pier. Why I
get absolutely no stylesheet at all, I don't know.
In any case, I've added the style sheet by hand from the "Toggle Halos"
in Pier. This works fine, except it doesn't seem to find the png files.
I've seen from searching msgs and found that "/seaside" is thought to
be the root for pier. So, I changed them to point to the direct path. As
example:
background: url(/seaside/styles/box-contents.png)
but this does not work.
I have also tried:
background: url(styles/box-contents.png)
Any hints you can give me for more searching?
This might be a clue: Going to /seaside/config brought up a css with the
beautiful seaside logo, etc. Now there is NO css associated, just this:
Seaside
Seaside2.7a1-lr.185.mcz 16 February 2007 3:36:17 pm
/seaside
browse Dispatcher Browser
examples Directory
mmiki Pier
tools Directory
12:17 a.m.
New subject: Pier Stylesheets - Help!
Hi Brad,
How come nobody has PRPierLibrary>>styleCss method?
This class seems to have all of the default css styles of Pier. Why I
get absolutely no stylesheet at all, I don't know.
sorry, I am on a trip and I couldn't replay earlier. I don't exactly
understand why the thing with the style are not working.
There are I few things that might be the problem:
1. The 2.7 branch of Seaside made some big changes in that area (and
there are a few more to expect), they do work fine in my image but
they are mostly untested.
2. Pier and Magritte require the latest version of Seaside (I think
you use those).
Maybe you want to use the version of Pier from SqueakMap, as it
builds you an image with the right version of Seaside, Magritte and
Pier that is knows to work well together. It is not bleeding edge,
but it is fresh and should be fairly easy to update later on.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
12:34 a.m.
New subject: Pier Stylesheets - Help!
Lukas Renggli wrote:
Hi Brad,
> How come nobody has PRPierLibrary>>styleCss method?
> This class seems to have all of the default css styles of Pier. Why I
> get absolutely no stylesheet at all, I don't know.
sorry, I am on a trip and I couldn't replay earlier. I don't exactly
understand why the thing with the style are not working.
There are I few things that might be the problem:
1. The 2.7 branch of Seaside made some big changes in that area (and
there are a few more to expect), they do work fine in my image but
they are mostly untested.
2. Pier and Magritte require the latest version of Seaside (I think
you use those).
Maybe you want to use the version of Pier from SqueakMap, as it
builds you an image with the right version of Seaside, Magritte and
Pier that is knows to work well together. It is not bleeding edge,
but it is fresh and should be fairly easy to update later on.
Hey, thanks for the reply, Lukas.
Well. that's where I started ;-) Even at that point, if I remember
correctly, I had "styleCss" method and not "style" method that pointed
to an actual file (your file, I believe on the Internet.)
I really wanted the newest blog plugin and a better way to handle images
- which I thought FileLibrary was to do.
It would be good if there was a proper way to update. I certainly don't
know if that's the problem. That's what Keith seems to be headed for.
Well.. I'm almost there... so maybe I can druge along with the member's
help and see if I can get this puppy running like it should be!
I think I need to find out how FileLibrary works. Or at least, find out
how I can serve png files for the css.
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
12:57 a.m.
New subject: Pier Stylesheets - Help!
Lukas Renggli wrote:
Hi Brad,
1. The 2.7 branch of Seaside made some big changes in that area (and
there are a few more to expect), they do work fine in my image but
they are mostly untested.
Ok, let me ask you how you change css?
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
1:52 a.m.
New subject: Pier Stylesheets - Help!
Brad Fuller wrote:
Lukas Renggli wrote:
> Hi Brad,
>
> 1. The 2.7 branch of Seaside made some big changes in that area (and
> there are a few more to expect), they do work fine in my image but
> they are mostly untested.
>
Ok, let me ask you how you change css?
I have an implementation which uses pier itself to edit the style sheet,
since a hierarchical collection of pier pages can be rendered into one
css file. Pictures are uploaded to pier, and rendered into the css as a
url. Any portion of the stylesheet can be pulled out into a page in the
tree, for example each reference to a color can be a reference to one
page, edit that page and the color changes everywhere that it is referenced.
If you would like to take a look at it, though I think it probably needs
some work once more, I put the image containing the latest code in
http://squeak.warwick.st/pier
An earlier version is actually running at www.warwick.st , and you are
welcome to have a play with that, but when I last looked there seemed to
be a gateway error.
best regards
Keith
___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of
use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html
2:12 a.m.
New subject: Pier Stylesheets - Help!
Keith Hodges wrote:
Brad Fuller wrote:
> Lukas Renggli wrote:
>
>> Hi Brad,
>>
>> 1. The 2.7 branch of Seaside made some big changes in that area (and
>> there are a few more to expect), they do work fine in my image but
>> they are mostly untested.
>>
> Ok, let me ask you how you change css?
>
>
>
I have an implementation which uses pier itself to edit the style sheet,
since a hierarchical collection of pier pages can be rendered into one
css file. Pictures are uploaded to pier, and rendered into the css as a
url. Any portion of the stylesheet can be pulled out into a page in the
tree, for example each reference to a color can be a reference to one
page, edit that page and the color changes everywhere that it is referenced.
That would be a bit more convenient than using the Toggle Halos and
editing the CSS there. However, I can see the advantage of having it
available for css editors that are remote. All they have to do is go to
the area in question and edit the css. However, I don't like having the
links available on the bottom - users could click and mess things up.
If you would like to take a look at it, though I think it probably
needs
some work once more, I put the image containing the latest code in
http://squeak.warwick.st/pier
I'm still trying to construct a good seaside-pier-magma image. It's
tough! It shouldn't be this tough, should it?
An earlier version is actually running at www.warwick.st , and you
are
welcome to have a play with that, but when I last looked there seemed to
be a gateway error.
yeah... still there.
Thanks
3:36 a.m.
New subject: Pier Stylesheets - Help!
I am not sure what is going on at seaside hosting, but I had a look at
another site on there and guess what, it has no style!
So it looks like the default pier configuration may be unable to get to
the style sheet served by lukas' machine at the moment. This might
explain your problem.
I'm still trying to construct a good seaside-pier-magma image. It's
tough! It shouldn't be this tough, should it?
No it shouldn't, but I recall my initial time with Pier; it took me at
least two weeks to get the hang of the packages so that they installed
correctly. I had never used MC before, so it took me a while to get used
to its quirks.
At the moment with pier-magma integration we are in a period of limbo,
where things are not actually expected to work out of the box. You see I
made some changes to both pier and magma in making the
seaside-pier-magma image work. I was waiting for Lukas and Chris to
update the mainstream of pier and magma to incorporate my changes. They
have both done this now, so it remains for me to review their changes
(not all were accepted) and update the pier-magma package.
Now that the necessary infrastructure changes (apart from one; I suspect
PRKernel realizeKernel may still have to be added) are in both pier and
magma, the process should be much smoother. In theory, pier-magma will
not have to touch pier or magma to work.
The plan is to pull my contribution to Pier-Seaside, including the item
that uses the elusive WADispatcherEditorPlugin into a separate package
for "persistency management". This is the code and UI that enables
switching between persistency schemes on the fly.
With this in mind, I will point out that Magma supports pier in an
entirely transparent manner. Pier really does nothing special to support
Magma. Therefore I can encourage you to get going with Pier, safe in the
knowledge that enabling magma persistency requires nothing more than a
drop down menu selection.
best regards
Keith
___________________________________________________________
Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail.
http://uk.docs.yahoo.com/nowyoucan.html
3:42 a.m.
New subject: Pier Stylesheets - Help!
Keith Hodges wrote:
I am not sure what is going on at seaside hosting, but I had a look
at
another site on there and guess what, it has no style!
So it looks like the default pier configuration may be unable to get to
the style sheet served by lukas' machine at the moment. This might
explain your problem.
> I'm still trying to construct a good seaside-pier-magma image. It's
> tough! It shouldn't be this tough, should it?
>
No it shouldn't, but I recall my initial time with Pier; it took me at
least two weeks to get the hang of the packages so that they installed
correctly. I had never used MC before, so it took me a while to get used
to its quirks.
At the moment with pier-magma integration we are in a period of limbo,
where things are not actually expected to work out of the box. You see I
made some changes to both pier and magma in making the
seaside-pier-magma image work. I was waiting for Lukas and Chris to
update the mainstream of pier and magma to incorporate my changes. They
have both done this now, so it remains for me to review their changes
(not all were accepted) and update the pier-magma package.
Now that the necessary infrastructure changes (apart from one; I suspect
PRKernel realizeKernel may still have to be added) are in both pier and
magma, the process should be much smoother. In theory, pier-magma will
not have to touch pier or magma to work.
The plan is to pull my contribution to Pier-Seaside, including the item
that uses the elusive WADispatcherEditorPlugin into a separate package
for "persistency management". This is the code and UI that enables
switching between persistency schemes on the fly.
With this in mind, I will point out that Magma supports pier in an
entirely transparent manner. Pier really does nothing special to support
Magma. Therefore I can encourage you to get going with Pier, safe in the
knowledge that enabling magma persistency requires nothing more than a
drop down menu selection.
Now, THAT I Like!
Thanks for the update and explanation. I've got the "basic" SqueakMap"
Pier running so I'm going to start with that. I sure would like to get
the new packages merged because from what I've seen, there are some
handy features that will make my life easier.
thanks again,
brad
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
10:04 a.m.
New subject: Pier enhancement idea
Joomla has a feature that lets you see and install Joomla components right
from the web page.
How would it sound to have something like this for Pier? Instead of having
to open up the image, download a MC and/or Squeak map thing, you can just go
to the "Add" button, and one extra option there would be to add a new
component. We could have some special button added on Squeak source to say
if a package is a Pier or Seaside component.
So what do people think of this idea?
Thanks,
Jason
_________________________________________________________________
Refi Now: Rates near 39yr lows! $430,000 Mortgage for $1,399/mo - Calculate
new payment
http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-17727&moi...
10:51 a.m.
New subject: Pier enhancement idea
2007/2/18, J J <azreal1977(a)hotmail.com>:
Joomla has a feature that lets you see and install Joomla components
right
from the web page.
How would it sound to have something like this for Pier? Instead of having
to open up the image, download a MC and/or Squeak map thing, you can just go
to the "Add" button, and one extra option there would be to add a new
component. We could have some special button added on Squeak source to say
if a package is a Pier or Seaside component.
So what do people think of this idea?
If Squeak supports sending an url (or loading code) from a webpage to
the currently open image ....
Philippe
Thanks,
Jason
_________________________________________________________________
Refi Now: Rates near 39yr lows! $430,000 Mortgage for $1,399/mo - Calculate
new payment
http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-17727&moi...
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
11:04 a.m.
New subject: Pier enhancement idea
From: "Philippe Marschall"
<philippe.marschall(a)gmail.com>
Reply-To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
Subject: Re: Pier enhancement idea
Date: Sun, 18 Feb 2007 10:51:30 +0100
If Squeak supports sending an url (or loading code) from a webpage to
the currently open image ....
Sorry, I'm confused. Are you pointing out a security issue, or a suggested
implementation?
I think security is no problem because the "Add" button only looks where we
tell it, and if you somehow did download something bad just don't save it.
As far as implementation, I'm sure that wont be too hard (and for sure it
will be much more clean, elegant and easy to maintain then what Joomla is
doing), and I planned on doing it myself once I get through some other
tasks. I just thought I would see what others think about it, and see if
maybe someone already was working on something similar.
Thanks,
Jason
_________________________________________________________________
The average US Credit Score is 675. The cost to see yours: $0 by Experian.
http://www.freecreditreport.com/pm/default.aspx?sc=660600&bcd=EMAILFO...
11:21 a.m.
New subject: Pier enhancement idea
2007/2/18, J J <azreal1977(a)hotmail.com>:
>From: "Philippe Marschall"
<philippe.marschall(a)gmail.com>
>Reply-To: "Magritte, Pier and Related Tools ..."
<smallwiki(a)iam.unibe.ch>
>To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
>Subject: Re: Pier enhancement idea
>Date: Sun, 18 Feb 2007 10:51:30 +0100
>
>If Squeak supports sending an url (or loading code) from a webpage to
>the currently open image ....
Sorry, I'm confused. Are you pointing out a security issue, or a suggested
implementation?
I think security is no problem because the "Add" button only looks where we
tell it, and if you somehow did download something bad just don't save it.
There are a lot of security issues with that since in Smalltalk
loading code means executing code (with the access rights of the
image). Not saving the image might not help that much if you home
directory has just been deleted. But that's not really the issue here.
As far as implementation, I'm sure that wont be too hard
Then please show us a prototype.
(and for sure it
will be much more clean, elegant and easy to maintain then what Joomla is
doing), and I planned on doing it myself once I get through some other
tasks. I just thought I would see what others think about it, and see if
maybe someone already was working on something similar.
Thanks,
Jason
_________________________________________________________________
The average US Credit Score is 675. The cost to see yours: $0 by Experian.
http://www.freecreditreport.com/pm/default.aspx?sc=660600&bcd=EMAILFO...
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
11:54 a.m.
New subject: Pier enhancement idea
From: "Philippe Marschall"
<philippe.marschall(a)gmail.com>
Reply-To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
Subject: Re: Pier enhancement idea
Date: Sun, 18 Feb 2007 11:21:23 +0100
There are a lot of security issues with that since in Smalltalk
loading code means executing code (with the access rights of the
image). Not saving the image might not help that much if you home
directory has just been deleted. But that's not really the issue here.
Ok, yes that is true. If you download a smalltalk package that is evil it
could delete data from your machine. But that is the case with MC,
SqueakMap and any other thing. It isn't unique to what I am talking about.
> As far as implementation, I'm sure that wont be too hard
Then please show us a prototype.
You mean of how it should work? Look at Joomla, you go to a component page,
say "add a new component" and it gives you a huge list of components people
have made. You select one and it gets added to the system. Now it can be
place inside pages just other components.
Or do you mean how it would be implemented in Squeak? For that it would be
much like SqueakMap.
Or maybe you are asking me to do the work. If no one else has done it by
the time I get to it, then I will. :) I'm just not the fastest implementer
since work takes up 14 hours of my day and I have a wife and a new baby. :)
_________________________________________________________________
Find a local pizza place, movie theater, and more
.then map the best route!
http://maps.live.com/?icid=hmtag1&FORM=MGAC01
11:23 a.m.
New subject: Pier enhancement idea
How would it sound to have something like this for Pier? Instead
of having
to open up the image, download a MC and/or Squeak map thing, you
can just go to the "Add" button, and one extra option there would
be to add a new
component. We could have some special button added on Squeak
source to say
if a package is a Pier or Seaside component.
So what do people think of this idea?
Well, you can do this already for quite some time:
http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov
Or do you have something else in mind?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
11:27 a.m.
New subject: Pier enhancement idea
No, I meant downloading something that wasn't previously in the image. Like
your new blog component for example. Right now I have to find out where it
is hosted, go there in MC and load it, then go into Pier to use it.
In a Joomla system this can all be done from inside the web site, and I
don't see why Pier would have to be any different.
From: Lukas Renggli <renggli(a)iam.unibe.ch>
Reply-To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
Subject: Re: Pier enhancement idea
Date: Sun, 18 Feb 2007 11:23:04 +0100
> How would it sound to have something like this for Pier? Instead
> of having
> to open up the image, download a MC and/or Squeak map thing, you
> can just go to the "Add" button, and one extra option there would
> be to add a new
> component. We could have some special button added on Squeak
> source to say
> if a package is a Pier or Seaside component.
>
> So what do people think of this idea?
Well, you can do this already for quite some time:
http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov
Or do you have something else in mind?
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
Find what you need at prices youll love. Compare products and save at MSN®
Shopping.
http://shopping.msn.com/default/shp/?ptnrid=37,ptnrdata=24102&tcode=T...
11:31 a.m.
New subject: Pier enhancement idea
In a Joomla system this can all be done from inside the web site,
and I don't see why Pier would have to be any different.
Ok sure, that should be easily possible. Then we need sort of a
database of package URLs that can be automatically loaded into Pier.
Or maybe something together with SqueakMap? If we could introduce a
Pier-Package tag then a UI could automatically build a list of those
packages and offer to install/uninstall them into the running image.
Cheers,
Lukas
> From: Lukas Renggli <renggli(a)iam.unibe.ch>
> Reply-To: "Magritte, Pier and Related Tools ..."
> <smallwiki(a)iam.unibe.ch>
> To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
> Subject: Re: Pier enhancement idea
> Date: Sun, 18 Feb 2007 11:23:04 +0100
>
> > How would it sound to have something like this for Pier? Instead
> > of having
> > to open up the image, download a MC and/or Squeak map thing, you
> > can just go to the "Add" button, and one extra option there would
> > be to add a new
> > component. We could have some special button added on Squeak
> > source to say
> > if a package is a Pier or Seaside component.
> >
> > So what do people think of this idea?
>
> Well, you can do this already for quite some time:
>
> http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov
>
> Or do you have something else in mind?
>
> Cheers,
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
Find what you need at prices you’ll love. Compare products and save
at MSN® Shopping. http://shopping.msn.com/default/shp/?
ptnrid=37,ptnrdata=24102&tcode=T001MSN20A0701
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
http://www.lukas-renggli.ch
11:57 a.m.
New subject: Pier enhancement idea
Yes, exactly what I was thinking. We would also want Seaside components as
well, since they clearly work.
We might want to flag the Pier components with some special flag (e.g. a
"Pier integrated" symbol) since the Pier components can take special
advantage of the Pier system, while the Seaside components can't.
From: Lukas Renggli <renggli(a)iam.unibe.ch>
Reply-To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
Subject: Re: Pier enhancement idea
Date: Sun, 18 Feb 2007 11:31:29 +0100
> In a Joomla system this can all be done from inside the web site,
> and I don't see why Pier would have to be any different.
Ok sure, that should be easily possible. Then we need sort of a
database of package URLs that can be automatically loaded into Pier.
Or maybe something together with SqueakMap? If we could introduce a
Pier-Package tag then a UI could automatically build a list of those
packages and offer to install/uninstall them into the running image.
Cheers,
Lukas
>
>> From: Lukas Renggli <renggli(a)iam.unibe.ch>
>> Reply-To: "Magritte, Pier and Related Tools ..."
>> <smallwiki(a)iam.unibe.ch>
>> To: "Magritte, Pier and Related Tools ..."
<smallwiki(a)iam.unibe.ch>
>> Subject: Re: Pier enhancement idea
>> Date: Sun, 18 Feb 2007 11:23:04 +0100
>>
>> > How would it sound to have something like this for Pier? Instead
>> > of having
>> > to open up the image, download a MC and/or Squeak map thing, you
>> > can just go to the "Add" button, and one extra option there
would
>> > be to add a new
>> > component. We could have some special button added on Squeak
>> > source to say
>> > if a package is a Pier or Seaside component.
>> >
>> > So what do people think of this idea?
>>
>> Well, you can do this already for quite some time:
>>
>> http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov
>>
>> Or do you have something else in mind?
>>
>> Cheers,
>> Lukas
>>
>> --
>> Lukas Renggli
>> http://www.lukas-renggli.ch
>>
>>
>>
>> _______________________________________________
>> SmallWiki, Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
> _________________________________________________________________
> Find what you need at prices youll love. Compare products and save
> at MSN® Shopping. http://shopping.msn.com/default/shp/?
> ptnrid=37,ptnrdata=24102&tcode=T001MSN20A0701
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
Play Flexicon: the crossword game that feeds your brain. PLAY now for FREE.
http://zone.msn.com/en/flexicon/default.htm?icid=flexicon_hmtagline
10:07 p.m.
New subject: Pier enhancement idea
Yes, exactly what I was thinking. We would also want Seaside
components as well, since they clearly work.
We might want to flag the Pier components with some special flag
(e.g. a "Pier integrated" symbol) since the Pier components can
take special advantage of the Pier system, while the Seaside
components can't.
Exactly, maybe we should ask to Goran (I think he is the maintainer
of SqueakMap) if we could get those two tags (Seaside, Pier, maybe
also Magritte) so that we can query and filter the SqueakMap database
from a standard Seaside/Pier component to allow loading extension
through the existing SqueakMap interface and reuse all its
functionality from there.
Cheers,
Lukas
> From: Lukas Renggli <renggli(a)iam.unibe.ch>
> Reply-To: "Magritte, Pier and Related Tools ..."
> <smallwiki(a)iam.unibe.ch>
> To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
> Subject: Re: Pier enhancement idea
> Date: Sun, 18 Feb 2007 11:31:29 +0100
>
> > In a Joomla system this can all be done from inside the web site,
> > and I don't see why Pier would have to be any different.
>
> Ok sure, that should be easily possible. Then we need sort of a
> database of package URLs that can be automatically loaded into Pier.
>
> Or maybe something together with SqueakMap? If we could introduce a
> Pier-Package tag then a UI could automatically build a list of those
> packages and offer to install/uninstall them into the running image.
>
> Cheers,
> Lukas
>
> >
> >> From: Lukas Renggli <renggli(a)iam.unibe.ch>
> >> Reply-To: "Magritte, Pier and Related Tools ..."
> >> <smallwiki(a)iam.unibe.ch>
> >> To: "Magritte, Pier and Related Tools ..."
> <smallwiki(a)iam.unibe.ch>
> >> Subject: Re: Pier enhancement idea
> >> Date: Sun, 18 Feb 2007 11:23:04 +0100
> >>
> >> > How would it sound to have something like this for Pier?
> Instead
> >> > of having
> >> > to open up the image, download a MC and/or Squeak map thing, you
> >> > can just go to the "Add" button, and one extra option there
> would
> >> > be to add a new
> >> > component. We could have some special button added on Squeak
> >> > source to say
> >> > if a package is a Pier or Seaside component.
> >> >
> >> > So what do people think of this idea?
> >>
> >> Well, you can do this already for quite some time:
> >>
> >> http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov
> >>
> >> Or do you have something else in mind?
> >>
> >> Cheers,
> >> Lukas
> >>
> >> --
> >> Lukas Renggli
> >> http://www.lukas-renggli.ch
> >>
> >>
> >>
> >> _______________________________________________
> >> SmallWiki, Magritte, Pier and Related Tools ...
> >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> >
> > _________________________________________________________________
> > Find what you need at prices you’ll love. Compare products and save
> > at MSN® Shopping. http://shopping.msn.com/default/shp/?
> > ptnrid=37,ptnrdata=24102&tcode=T001MSN20A0701
> >
> >
> > _______________________________________________
> > SmallWiki, Magritte, Pier and Related Tools ...
> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
Play Flexicon: the crossword game that feeds your brain. PLAY now
for FREE. http://zone.msn.com/en/flexicon/default.htm?
icid=flexicon_hmtagline
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
http://www.lukas-renggli.ch
10:07 a.m.
New subject: Pier Magritte question
Hi,
Related to my previous email, I was wondering what happens if I have a
seaside component that uses Magritte to display itself (Ramon does this a
lot on his blog), and I try to use it in Pier. Will the Pier settings
button show the same thing that the main render does? Or does Pier somehow
know which are Pier components and which are seaside components?
Thanks,
Jason
_________________________________________________________________
Dont miss your chance to WIN 10 hours of private jet travel from Microsoft®
Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/
10:55 a.m.
New subject: Pier Magritte question
2007/2/18, J J <azreal1977(a)hotmail.com>:
Hi,
Related to my previous email, I was wondering what happens if I have a
seaside component that uses Magritte to display itself (Ramon does this a
lot on his blog), and I try to use it in Pier. Will the Pier settings
button show the same thing that the main render does? Or does Pier somehow
know which are Pier components and which are seaside components?
Can you be a bit more precise? What do you do, add a new metadescribed
structure kind to Pier or embed a Seaside application (that uses
Magritte somewhere) in Pier? What do you mean with 'Will the Pier
settings button show the same thing that the main render does'?
Whether it will work on your component class like on other components?
Philippe
Thanks,
Jason
_________________________________________________________________
Don't miss your chance to WIN 10 hours of private jet travel from Microsoft(r)
Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
11:09 a.m.
New subject: Pier Magritte question
Sorry. What I mean is, Ramon has a screencase that shows how to make things
in Seaside like, e.g. a Blog. He builds the domain classes and then uses
Magritte-Seaside to display it in a web page.
I can see a lot of components I would want working this way, but I was
wondering if this would cause some strange behavior if these components were
used in a Pier page since Pier already uses Magritte to configure
components.
http://onsmalltalk.com/programming/smalltalk/screencast-how-to-build-a-bl...
is the screencase I am talking about.
From: "Philippe Marschall"
<philippe.marschall(a)gmail.com>
Reply-To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
Subject: Re: Pier Magritte question
Date: Sun, 18 Feb 2007 10:55:33 +0100
2007/2/18, J J <azreal1977(a)hotmail.com>:
> Hi,
>
> Related to my previous email, I was wondering what happens if I have a
> seaside component that uses Magritte to display itself (Ramon does this
a
> lot on his blog), and I try to use it in Pier. Will the Pier settings
> button show the same thing that the main render does? Or does Pier
somehow
> know which are Pier components and which are seaside components?
Can you be a bit more precise? What do you do, add a new metadescribed
structure kind to Pier or embed a Seaside application (that uses
Magritte somewhere) in Pier? What do you mean with 'Will the Pier
settings button show the same thing that the main render does'?
Whether it will work on your component class like on other components?
Philippe
> Thanks,
> Jason
>
> _________________________________________________________________
> Don't miss your chance to WIN 10 hours of private jet travel from
Microsoft(r)
> Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
With tax season right around the corner, make sure to follow these few
simple tips.
http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationTip...
11:15 a.m.
New subject: Pier Magritte question
2007/2/18, J J <azreal1977(a)hotmail.com>:
Sorry. What I mean is, Ramon has a screencase that shows how to make
things
in Seaside like, e.g. a Blog. He builds the domain classes and then uses
Magritte-Seaside to display it in a web page.
I can see a lot of components I would want working this way, but I was
wondering if this would cause some strange behavior if these components were
used in a Pier page since Pier already uses Magritte to configure
components.
No, if it does it is a bug. The only thing to be aware of is that the
same style will be applied to Magritte forms whether they come from
Pier or your application. The settings command should work on the root
component class of your application.
Philippe.
http://onsmalltalk.com/programming/smalltalk/screencast-how-to-build-a-bl...
is the screencase I am talking about.
>From: "Philippe Marschall" <philippe.marschall(a)gmail.com>
>Reply-To: "Magritte, Pier and Related Tools ..."
<smallwiki(a)iam.unibe.ch>
>To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
>Subject: Re: Pier Magritte question
>Date: Sun, 18 Feb 2007 10:55:33 +0100
>
>2007/2/18, J J <azreal1977(a)hotmail.com>:
> > Hi,
> >
> > Related to my previous email, I was wondering what happens if I have a
> > seaside component that uses Magritte to display itself (Ramon does this
>a
> > lot on his blog), and I try to use it in Pier. Will the Pier settings
> > button show the same thing that the main render does? Or does Pier
>somehow
> > know which are Pier components and which are seaside components?
>
>Can you be a bit more precise? What do you do, add a new metadescribed
>structure kind to Pier or embed a Seaside application (that uses
>Magritte somewhere) in Pier? What do you mean with 'Will the Pier
>settings button show the same thing that the main render does'?
>Whether it will work on your component class like on other components?
>
>Philippe
>
> > Thanks,
> > Jason
> >
> > _________________________________________________________________
> > Don't miss your chance to WIN 10 hours of private jet travel from
>Microsoft(r)
> > Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/
> >
> >
> >
> > _______________________________________________
> > SmallWiki, Magritte, Pier and Related Tools ...
> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> >
>
>_______________________________________________
>SmallWiki, Magritte, Pier and Related Tools ...
>https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
With tax season right around the corner, make sure to follow these few
simple tips.
http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationTip...
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
1:51 p.m.
New subject: Pier Magritte question
Related to my previous email, I was wondering what happens if I
have a seaside component that uses Magritte to display itself
(Ramon does this a lot on his blog), and I try to use it in Pier.
Will the Pier settings button show the same thing that the main
render does? Or does Pier somehow know which are Pier components
and which are seaside components?
Basically Pier doesn't care if it is a Seaside component or a special
Pier component. You can add and configure any Seaside component that
answers true for #canBeRoot.
Now for quite some time Seaside started to use #description to return
a descriptive text of the component, what sort of conflicts with
Magritte.
Cheers,
Lukas
Thanks,
Jason
_________________________________________________________________
Don’t miss your chance to WIN 10 hours of private jet travel from
Microsoft® Office Live http://clk.atdmt.com/MRT/go/
mcrssaub0540002499mrt/direct/01/
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
http://www.lukas-renggli.ch
10:44 a.m.
2007/2/17, Brad Fuller <brad(a)sonaural.com>:
Looking through the various Pier documentation, I see that code has
changed and thus there are several different explanations of how to
change stylesheets. I want to use a different css stylesheets but I
can't find out where to change it/them. Isn't there one place to point
Pier to one stylesheet?
BTW: for some reason, I have no style sheet at all for Pier. I don't
know what I did, but I didn't edit any code... I must have loaded a new
version of some package. Anyway, unless it stomped on something else, if
I can learn where to change the stylesheet pointer, It'd give me a start.
Thanks to Christoph Wysseier Pier now supports easy custom styles with
FileLibraries. All you need to do is provide your own FileLibrary that
implements #styleCss which returns a string that is the main CSS file.
You can put all your CSS there, or in other selectors (as PierLibrary
does) or in other locations by importing the CSS files you need.
For example if #styleCss makes
@import url(basic.css);
this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary
one of the classes that actually have a comment that describes what it
does.
In the configuration of your pier application under 'Pier' you can
select it in 'File Library'.
Cheers
Philippe
thanks,
brad
--
brad fuller
http://www.Sonaural.com/
+1 (408) 799-6124
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
5:19 p.m.
Philippe Marschall wrote:
2007/2/17, Brad Fuller <brad(a)sonaural.com>:
> Looking through the various Pier documentation, I see that code has
> changed and thus there are several different explanations of how to
> change stylesheets. I want to use a different css stylesheets but I
> can't find out where to change it/them. Isn't there one place to point
> Pier to one stylesheet?
>
> BTW: for some reason, I have no style sheet at all for Pier. I don't
> know what I did, but I didn't edit any code... I must have loaded a new
> version of some package. Anyway, unless it stomped on something else, if
> I can learn where to change the stylesheet pointer, It'd give me a start.
Thanks to Christoph Wysseier Pier now supports easy custom styles with
FileLibraries. All you need to do is provide your own FileLibrary that
implements #styleCss which returns a string that is the main CSS file.
You can put all your CSS there, or in other selectors (as PierLibrary
does) or in other locations by importing the CSS files you need.
For example if #styleCss makes
@import url(basic.css);
this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary
one of the classes that actually have a comment that describes what it
does.
In the configuration of your pier application under 'Pier' you can
select it in 'File Library'.
Thanks Philippe. Now that I'm back running to a basic, and slightly
older implementation, I'll check it out.
4:49 p.m.
Brad Fuller schrieb:
Looking through the various Pier documentation, I see that code has
changed and thus there are several different explanations of how to
change stylesheets. I want to use a different css stylesheets but I
can't find out where to change it/them. Isn't there one place to point
Pier to one stylesheet?
Here again my mail (26.12.2006) pointing out how to change the
stylesheet for different look'n'feel of Pier:
Pier is using Seaside File Libraries (PRPierLibrary) to store CSS and
images for the look'n'feel. Using a small extension that I just
committed it is now very easy to change the look'n'feel by just changing
the file library to another one.
Name: Pier-Seaside-cw.107
Author: cw
Time: 26 December 2006, 12:56:04 pm
After loading this patch a variable will be available in the seaside
config that allows you to change the default File Library to any other
you need to provide before (any subclass of WAFileLibrary is available).
This way the look'n'feel may be changed on-the-fly and you may store
your own File Library with your CSS and image files in a repository of
your choice.
Cheers, Chris
5825
days inactive
5827
days old
29 comments
7 participants
participants (7)
-
Brad Fuller -
Christoph Wysseier -
J J -
Keith Hodges -
Lukas Renggli -
Norbert Hartl -
Philippe Marschall