 tag as a text files
according to MAFileModel.

BTW, why halts in MAFileModel >> renderOn: and MAFileModel >> renderTextOn:
html are not triggered when I open the page with the file or even add it?

Thank you in advance for all answers.

-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From evaklo at gmail.com  Fri Feb 13 15:33:00 2009
From: evaklo at gmail.com (=?ISO-8859-1?Q?Lautaro_Fern=E1ndez?=)
Date: Fri, 13 Feb 2009 12:33:00 -0200
Subject: PRCase and custom pages (template)
Message-ID: <36ce93cf0902130633v1f93d42h3c50222f8261e7e1@mail.gmail.com>

Hello,
I want to know if it possible to create some sort of template, in which if I
create a page it will add other XYZ pages inside of it.
For instance, I want to create a PageProject so that page have 3 other sub
pages:
MyProject
 ->Installation
 ->Wiki
 ->FAQ

I could do something like:
PageProject>>defaultDocument
    ^ super defaultDocument
        add: (PRParagraph new
            add: (PRText content: '*Installation* *Wiki* *FAQ*');
            yourself);
        yourself

But the problem is that those 3 pages aren't created, I have to click on
each link and then accept to make them "alive".

So, here is my question:
Is there any way to create dynamically pages inside a newly page(the one I
just had created)?

Notes:
I'm working with VisualWorks, and therefore the Pier versions are probably
quite old :(
Is somebody working on the port of the latest Pier version into VisualWorks?

Thanks in advance,
Lautaro Fern?ndez
-- 
Luke LAut SkyFernadezWalker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From renggli at gmail.com  Fri Feb 13 15:40:42 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Fri, 13 Feb 2009 15:40:42 +0100
Subject: PRCase and custom pages (template)
In-Reply-To: <36ce93cf0902130633v1f93d42h3c50222f8261e7e1@mail.gmail.com>
References: <36ce93cf0902130633v1f93d42h3c50222f8261e7e1@mail.gmail.com>
Message-ID: <67628d690902130640r6a62e81du9b5c0d1155cbbfbc@mail.gmail.com>

> So, here is my question:
> Is there any way to create dynamically pages inside a newly page(the one I
> just had created)?

I would override PageProject>>#initialize and add the subpages
programmatically. Something like:

PageProject>>initialize
    super initialize.
    self addChild: (PRPage named: 'installation').
    self addChild: (PRPage named: 'wiki').
    self addChild: (PRPage named: 'faq').

You can also change the document contents, title and other properties
from there if you want.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From renggli at gmail.com  Fri Feb 13 15:48:30 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Fri, 13 Feb 2009 15:48:30 +0100
Subject: html from local file
In-Reply-To: <84f77e270902130628l590627a1q15686bf0f4bb66f7@mail.gmail.com>
References: <84f77e270902130628l590627a1q15686bf0f4bb66f7@mail.gmail.com>
Message-ID: <67628d690902130648o3553d89bs6df3c4cb27cab405@mail.gmail.com>

> I want to show a local html file on a pier page. What's the simple way to do
> it?

Copy the part you want to include directly into the wiki document.

> I tried to use File, but it renders it inside  tag as a text files
> according to MAFileModel.

It is problematic to include a html document into another html
document. That's probably why it is not implemented yet. I think it
could only be done through an ugly iframe in a valid way. Is that what
you want?

> BTW, why halts in MAFileModel >> renderOn: and MAFileModel >> renderTextOn:
> html are not triggered when I open the page with the file or even add it?

PRViewRenderer>>#visitFile: does some extra checks at the beginning
and in the case of a text file it skips the Magritte behavior. I
recently cleaned that up a bit, but obviously some more cleanup is
required.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From evaklo at gmail.com  Fri Feb 13 15:53:17 2009
From: evaklo at gmail.com (=?ISO-8859-1?Q?Lautaro_Fern=E1ndez?=)
Date: Fri, 13 Feb 2009 12:53:17 -0200
Subject: PRCase and custom pages (template)
In-Reply-To: <67628d690902130640r6a62e81du9b5c0d1155cbbfbc@mail.gmail.com>
References: <36ce93cf0902130633v1f93d42h3c50222f8261e7e1@mail.gmail.com>
	<67628d690902130640r6a62e81du9b5c0d1155cbbfbc@mail.gmail.com>
Message-ID: <36ce93cf0902130653o221106e5ha1383192cf7b6957@mail.gmail.com>

Thanks for your quickly response!
A friend tried (but it was a bit more ugly code) to do the  "addChild:
(PRPage ...)" in the defaultDocument and it also works.

But initialize seems to be a better place.

Sorry for make the same question again, is somebody making the port of Pier
into VisualWorks?
The latest published version is from 10/2007, and the Pier version is
lr.183-222-81-99 CS12NFR.10

Thanks again,
Lautaro Fern?ndez

2009/2/13 Lukas Renggli 

> > So, here is my question:
> > Is there any way to create dynamically pages inside a newly page(the one
> I
> > just had created)?
>
> I would override PageProject>>#initialize and add the subpages
> programmatically. Something like:
>
> PageProject>>initialize
>    super initialize.
>    self addChild: (PRPage named: 'installation').
>    self addChild: (PRPage named: 'wiki').
>    self addChild: (PRPage named: 'faq').
>
> You can also change the document contents, title and other properties
> from there if you want.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Luke LAut SkyFernadezWalker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From chaetal at gmail.com  Fri Feb 13 15:49:35 2009
From: chaetal at gmail.com (Dennis Schetinin)
Date: Fri, 13 Feb 2009 17:49:35 +0300
Subject: html from local file
In-Reply-To: <84f77e270902130628l590627a1q15686bf0f4bb66f7@mail.gmail.com>
References: <84f77e270902130628l590627a1q15686bf0f4bb66f7@mail.gmail.com>
Message-ID: <84f77e270902130649x3524abb0i20bd7aae1b15a5a2@mail.gmail.com>

I want to show a local html file on a pier page. What's the simple way to do
> it?
>
>
Oh, I found it's possible to use html inside a page... It's partially gives
a solution, but for our project it will be more convinient to have it in an
external file... at least for now... :) So if someone can offer a solution
it will be highly appreciated

-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From chaetal at gmail.com  Fri Feb 13 16:15:22 2009
From: chaetal at gmail.com (Dennis Schetinin)
Date: Fri, 13 Feb 2009 18:15:22 +0300
Subject: html from local file
In-Reply-To: <67628d690902130648o3553d89bs6df3c4cb27cab405@mail.gmail.com>
References: <84f77e270902130628l590627a1q15686bf0f4bb66f7@mail.gmail.com>
	<67628d690902130648o3553d89bs6df3c4cb27cab405@mail.gmail.com>
Message-ID: <84f77e270902130715i61d94fc3mf45607ca45ce0882@mail.gmail.com>

>
> > I tried to use File, but it renders it inside  tag as a text files
> > according to MAFileModel.
>
> It is problematic to include a html document into another html
> document. That's probably why it is not implemented yet. I think it
> could only be done through an ugly iframe in a valid way.

Right, I've got it now

> Is that what you want?

I think no... Pasting works ok for now

-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From chaetal at gmail.com  Fri Feb 13 16:52:54 2009
From: chaetal at gmail.com (Dennis Schetinin)
Date: Fri, 13 Feb 2009 18:52:54 +0300
Subject: Rendering descendant of PRCase
Message-ID: <84f77e270902130752w6fcee90eq1bd684ce62426407@mail.gmail.com>

Is there any "correct'" way to render classes inhereted from PRCase? Here
are the details:

I want to represent an object, say Clinic with fullDescription, address,
etc. attributes. Currently I do such things the way I saw in Pier-Blog. I.e.
I overloaded Person>>viewComponentClass to return PersonView. And there I do
something like:

renderContentOn: html
    super renderContentOn: html.
    self renderFullDescriptionOn: html.
    self renderAddressOn: html.
    self renderDoctorsOn: html

It works ofcourse, but I feel there should be another way to explain Pier
(or Magritte?) how to render Clinics as far as I described them.

And another part is about doctors. They are instances of Doctor which is
surely inhereted from PRCase and properly described. I want to give a list
of doctors in context of the clinic. Items of the list should represent some
short form of doctors, I mean show some of Doctor's attributes. And when one
of the doctors is selected I want all the information to be presented.

Now I do it just the same way:
  -  #renderDoctorsOn: outputs short information about each of them in
context of the clinic
  -  full Doctors information is rendered by DoctorView component.

The question is just the same: I feel there must be another way to do it
using metainformation I give about Doctors (and Clinics). Is there a
"canonized" one?

And one more thing: I saw people mentioned "Tutorial" but I don't know where
to get it. Perhaps it's where all answers are already given? :)

-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From estebanlm at gmail.com  Fri Feb 13 18:18:33 2009
From: estebanlm at gmail.com (Esteban Lorenzano)
Date: Fri, 13 Feb 2009 15:18:33 -0200
Subject: flash movie with MAFileModel and SWFObject
References:  

Message-ID: 

Ok, I s
olve the "problem".
The flash plugin does not read files without the ".swf" file 
extension... yes, it is stupid.
So, I changed MAFIleModel in order to render meaningful urls (bah... 
more or less meaningful), but enough to make it understandable for the 
plugin... and that's all, everithing now works like a charm.

Cheers,
Esteban

On 2009-02-12 09:31:39 -0200, Udo Schneider 
 said:

> Esteban,
> 
>> Or maybe you want the sources?
> I'll drop you a private mail.
> 
> CU,
> 
> Udo
> 
> 
>> 
>> Cheers,
>> Esteban
>> 
>> On 2009-02-10 07:36:01 -0200, Udo Schneider
>>  said:
>> 
>>> That's really change. I still assume I have a bug somewhere in
>>> SWFObject. Is there any way for me to take a look at it?
>>> 
>>> CU,
>>> 
>>> Udo
>>> 
>>> Esteban Lorenzano schrieb:
>>>> Seems to be:
>>>> 
>>>> application/x-

shockwave-flash
>>>> 
>>>> :(
>>>> 
>>>> Cheers,
>>>> Esteban
>>>> 
>>>> 
>>>> On 2009-02-09 14:32:21 -0200, Udo Schneider
>>>>  said:
>>>> 
>>>>>> No, it starts a download  (of mymovie.swf) :(
>>>>> is "mymovie.swf" the name of the file you uploaded? If yes we can at
>>>>> least assume, that the URL does indeed return the uploaded file.
>>>>> 
>>>>> Wild Guess 2: As the browser downloads the file instead of
>>>>> displaying it
>>>>> ... could you check which MIME Type is returned for mymovie.swf in the
>>>>> HTTP Response? (Firebug might help here).
>>>>> 
>>>>> CU,
>>>>> 
>>>>> Udo
>>>>> 
>>>>> 
>>>>> Esteban Lorenzano schrieb:
>>>>>> No, it starts a download  (of mymovie.swf) :(
>>>>>> 
>>>>>> Cheers,
>>>>>> Esteban
>>>>>> 

>>>>>> On 2009-02-09 12:02:44 -0200, Udo Schneider
>>>>>>  said:
>>>>>> 
>>>>>>> Esteban,
>>>>>>> 
>>>>>>>> /seaside/Stroytrast?_s=rigOmvO5PzX_VmOo
>>>>>>> What happens if you type the URL directly in the browser? Does the
>>>>>>> flash
>>>>>>> file play?
>>>>>>> 
>>>>>>> 
>>>>>>> CU,
>>>>>>> 
>>>>>>> Udo
>>>>>>> 
>>>>>>> 
>>>>>>> Esteban Lorenzano schrieb:
>>>>>>>> Hi, Udo,
>>>>>>>> 
>>>>>>>> This is the generated URL, with #urlOn:
>>>>>>>> 
>>>>>>>> /seaside/Stroytrast?_s=rigOmvO5PzX_VmOo
>>>>>>>> 
>>>>>>>> And this is the script generated:
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Seems to be the same :(
>>>>>>>> 
>>>>>>>> Cheers,
>>>>>>>> Esteban
>>>>>>>> 
>>>>>>>> On 2009-02-08 15:37:46 -0200, Udo Schneider
>>>>>>>>  said:
>>>>>>>> 
>>>>>>>>> Esteban,
>>>>>>>>> 
>>>>>>>>> the first thing that comes to my mind is that the JSON encoding
>>>>>>>>> somehow
>>>>>>>>> scrambles the URL.
>>>>>>>>> 
>>>>>>>>> Could you send me the url which /should/ be shown and the one from
>>>>>>>>> the
>>>>>>>>> loadScript at the end of the page source?
>>>>>>>>> 
>>>>>>>>> CU,
>>>>>>>>> 
>>>>>>>>> Udo
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Esteban Lorenzano schrieb:
>>>>>>>>>> Hi,
>>>>>>>>>> I'm trying to render some uploaded files as flash movies... but
>>>>>>>>>> without
>>>>>>>>>> success by now... I thought it was easy, just putting this
>>>>>>>>>> method in
>>>>>>>>>> MAFileModel (and of course, changing #renderOn:)

:
>>>>>>>>>> 
>>>>>>>>>> renderFlashOn: html
>>>>>>>>>> html swfObject
>>>>>>>>>> url: (self urlOn: html);
>>>>>>>>>> with: 'Loading...'.
>>>>>>>>>> 
>>>>>>>>>> But nothing happens (it shows "Movie not loaded...")
>>>>>>>>>> 
>>>>>>>>>> If I put an "example" url, the example movie is loaded ok... :(
>>>>>>>>>> 
>>>>>>>>>> renderFlashOn: html
>>>>>>>>>> html swfObject
>>>>>>>>>> url:  'http://www.mariaclaudiacortes.com/colors/Colors.swf';
>>>>>>>>>> with: 'Loading...'.
>>>>>>>>>> 
>>>>>>>>>> So I think there is something in the URL  generated by #urlOn:
>>>>>>>>>> that is
>>>>>>>>>> not good for swfObject  (writing the html code directly drives to
>>>>>>>>>> the
>>>>>>>>>> same answer)...
>>>>>>>>>> 
>>>>>>>>>> Any idea?
>>>>>>>>>> Thanks,
>>>>>>>>>> Esteban
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> 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
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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
>> 
>> 
>> 
>> 
>> _______________________________________________
>> 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

From renggli at gmail.com  Fri Feb 13 22:02:11 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Fri, 13 Feb 2009 22:02:11 +0100
Subject: Rendering descendant of PRCase
In-Reply-To: <84f77e270902130752w6fcee90eq1bd684ce62426407@mail.gmail.com>
References: <84f77e270902130752w6fcee90eq1bd684ce62426407@mail.gmail.com>
Message-ID: <67628d690902131302x5d36fe24v17cf34c7fb28e356@mail.gmail.com>

On Fri, Feb 13, 2009 at 4:52 PM, Dennis Schetinin  wrote:
>
> Is there any "correct'" way to render classes inhereted from PRCase? Here
> are the details:
>
> I want to represent an object, say Clinic with fullDescription, address,
> etc. attributes. Currently I do such things the way I saw in Pier-Blog. I.e.
> I overloaded Person>>viewComponentClass to return PersonView. And there I do
> something like:
>
> renderContentOn: html
>     super renderContentOn: html.
>     self renderFullDescriptionOn: html.
>     self renderAddressOn: html.
>     self renderDoctorsOn: html
>
> It works ofcourse, but I feel there should be another way to explain Pier
> (or Magritte?) how to render Clinics as far as I described them.

That's basically the right way.

In the custom render method you can use Magritte to generate a
read-only view of the fields, try something along:

html table: [
	aStructure description do: [ :each |
		(each isEditable and: [ each componentClass notNil ]) ifTrue: [
			html tableRow: [
				html tableHeading: each label.
				html tableData: [
					(each componentClass memento: aStructure description: each)
						renderViewerOn: html ] ] ] ] ]

Unfortunately you have to add that yourself, because PRCase overrides
this default view of structures by just displaying the document.

> And one more thing: I saw people mentioned "Tutorial" but I don't know where
> to get it. Perhaps it's where all answers are already given? :)

See here  and keep
asking questions.

Lukas

>
> --
> Dennis Schetinin
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From jborden23 at mac.com  Sat Feb 14 04:37:03 2009
From: jborden23 at mac.com (John Borden)
Date: Fri, 13 Feb 2009 21:37:03 -0600
Subject: Pier - Changing CSS Class
Message-ID: <65F330CB-65CD-4E0E-B100-35CA910DC67D@mac.com>

All,
Lately, I've been attempting to make PRTables have a borders around  
them.  If I create a CSS file for table with class 'hasborden' by  
adding the following to the top of PRTable>>accept:

         (aVisitor isKindOf: PRRenderer) ifTrue: [aVisitor renderer  
table attributes addClass: 'hasborder'].

then PRTables are displayed with the CSS class of 'hasborder' and is  
displayed correctly, and other tables do not have borders (exactly  
what I want!).  Is there a better way to this sort of thing, I have  
several similar changes, and I want to limit the amount of really bad  
smalltalk.

Thanks,
John

From renggli at gmail.com  Sat Feb 14 10:34:45 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 14 Feb 2009 10:34:45 +0100
Subject: Pier - Changing CSS Class
In-Reply-To: <65F330CB-65CD-4E0E-B100-35CA910DC67D@mac.com>
References: <65F330CB-65CD-4E0E-B100-35CA910DC67D@mac.com>
Message-ID: <67628d690902140134t71ccf152ub4114120af914016@mail.gmail.com>

Assuming that all tables of the page contents should have borders, you
just have to make sure that the document is always rendered within a
well known DIV element. Like this you do not need to change the code
and just add a new CSS rule to your style-sheet:

/* all tables within the .contents should have a border */
.contents table { border: 1px solid black; }

Does that help?

Cheers,
Lukas

On Sat, Feb 14, 2009 at 4:37 AM, John Borden  wrote:
> All,
> Lately, I've been attempting to make PRTables have a borders around them.
>  If I create a CSS file for table with class 'hasborden' by adding the
> following to the top of PRTable>>accept:
>
>        (aVisitor isKindOf: PRRenderer) ifTrue: [aVisitor renderer table
> attributes addClass: 'hasborder'].
>
> then PRTables are displayed with the CSS class of 'hasborder' and is
> displayed correctly, and other tables do not have borders (exactly what I
> want!).  Is there a better way to this sort of thing, I have several similar
> changes, and I want to limit the amount of really bad smalltalk.
>
> Thanks,
> John
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From Udo.Schneider at homeaddress.de  Sat Feb 14 13:57:49 2009
From: Udo.Schneider at homeaddress.de (Udo Schneider)
Date: Sat, 14 Feb 2009 13:57:49 +0100
Subject: flash movie with MAFileModel and SWFObject
In-Reply-To: 
References: 

Message-ID: 

Hi Esteban,

 > Ok, I s
olve the "problem".
Great to hear!

BTW: I just stumbled over another "security" feature of the FlashPlayer. 
  Under normal conditions the flash plugin can only load additional 
stuff from the exact same location it was loaded from. I just spent few 
hours debugging because I moved my OpenFlashChartSwf to a CDN and tried 
to deliver it's JSON Data over seaside ... :-(

CU,

Udo

Esteban Lorenzano schrieb:
> Ok, I s
olve the "problem".
> The flash plugin does not read files without the ".swf" file 
> extension... yes, it is stupid.
> So, I changed MAFIleModel in order to render meaningful urls (bah... 
> more or less meaningful), but enough to make it understandable for the 
> plugin... and that's all, everithing now works like a charm.
> 
> Cheers,
> Esteban
> 
> On 2009-02-12 09:31:39 -0200, Udo Schneider 
>  said:
> 
>> Esteban,
>>
>>> Or maybe you want the sources?
>> I'll drop you a private mail.
>>
>> CU,
>>
>> Udo
>>
>>
>>>
>>> Cheers,
>>> Esteban
>>>
>>> On 2009-02-10 07:36:01 -0200, Udo Schneider
>>>  said:
>>>
>>>> That's really change. I still assume I have a bug somewhere in
>>>> SWFObject. Is there any way for me to take a look at it?
>>>>
>>>> CU,
>>>>
>>>> Udo
>>>>
>>>> Esteban Lorenzano schrieb:
>>>>> Seems to be:
>>>>>
>>>>> application/x-

shockwave-flash
>>>>>
>>>>> :(
>>>>>
>>>>> Cheers,
>>>>> Esteban
>>>>>
>>>>>
>>>>> On 2009-02-09 14:32:21 -0200, Udo Schneider
>>>>>  said:
>>>>>
>>>>>>> No, it starts a download  (of mymovie.swf) :(
>>>>>> is "mymovie.swf" the name of the file you uploaded? If yes we can at
>>>>>> least assume, that the URL does indeed return the uploaded file.
>>>>>>
>>>>>> Wild Guess 2: As the browser downloads the file instead of
>>>>>> displaying it
>>>>>> ... could you check which MIME Type is returned for mymovie.swf in 
>>>>>> the
>>>>>> HTTP Response? (Firebug might help here).
>>>>>>
>>>>>> CU,
>>>>>>
>>>>>> Udo
>>>>>>
>>>>>>
>>>>>> Esteban Lorenzano schrieb:
>>>>>>> No, it starts a download  (of mymovie.swf) :(
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Esteban
>>>>>>> 

>>>>>>> On 2009-02-09 12:02:44 -0200, Udo Schneider
>>>>>>>  said:
>>>>>>>
>>>>>>>> Esteban,
>>>>>>>>
>>>>>>>>> /seaside/Stroytrast?_s=rigOmvO5PzX_VmOo
>>>>>>>> What happens if you type the URL directly in the browser? Does the
>>>>>>>> flash
>>>>>>>> file play?
>>>>>>>>
>>>>>>>>
>>>>>>>> CU,
>>>>>>>>
>>>>>>>> Udo
>>>>>>>>
>>>>>>>>
>>>>>>>> Esteban Lorenzano schrieb:
>>>>>>>>> Hi, Udo,
>>>>>>>>>
>>>>>>>>> This is the generated URL, with #urlOn:
>>>>>>>>>
>>>>>>>>> /seaside/Stroytrast?_s=rigOmvO5PzX_VmOo
>>>>>>>>>
>>>>>>>>> And this is the script generated:
>>>>>>>>>
>>>>>>>>> 
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Seems to be the same :(
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Esteban
>>>>>>>>>
>>>>>>>>> On 2009-02-08 15:37:46 -0200, Udo Schneider
>>>>>>>>>  said:
>>>>>>>>>
>>>>>>>>>> Esteban,
>>>>>>>>>>
>>>>>>>>>> the first thing that comes to my mind is that the JSON encoding
>>>>>>>>>> somehow
>>>>>>>>>> scrambles the URL.
>>>>>>>>>>
>>>>>>>>>> Could you send me the url which /should/ be shown and the one 
>>>>>>>>>> from
>>>>>>>>>> the
>>>>>>>>>> loadScript at the end of the page source?
>>>>>>>>>>
>>>>>>>>>> CU,
>>>>>>>>>>
>>>>>>>>>> Udo
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Esteban Lorenzano schrieb:
>>>>>>>>>>> Hi,
>>>>>>>>>>> I'm trying to render some uploaded files as flash movies... but
>>>>>>>>>>> without
>>>>>>>>>>> success by now... I thought it was easy, just putting this
>>>>>>>>>>> method in
>>>>>>>>>>> MAFileModel (and of course, changing #renderOn:)

:
>>>>>>>>>>>
>>>>>>>>>>> renderFlashOn: html
>>>>>>>>>>> html swfObject
>>>>>>>>>>> url: (self urlOn: html);
>>>>>>>>>>> with: 'Loading...'.
>>>>>>>>>>>
>>>>>>>>>>> But nothing happens (it shows "Movie not loaded...")
>>>>>>>>>>>
>>>>>>>>>>> If I put an "example" url, the example movie is loaded ok... :(
>>>>>>>>>>>
>>>>>>>>>>> renderFlashOn: html
>>>>>>>>>>> html swfObject
>>>>>>>>>>> url:  'http://www.mariaclaudiacortes.com/colors/Colors.swf';
>>>>>>>>>>> with: 'Loading...'.
>>>>>>>>>>>
>>>>>>>>>>> So I think there is something in the URL  generated by #urlOn:
>>>>>>>>>>> that is
>>>>>>>>>>> not good for swfObject  (writing the html code directly 
>>>>>>>>>>> drives to
>>>>>>>>>>> the
>>>>>>>>>>> same answer)...
>>>>>>>>>>>
>>>>>>>>>>> Any idea?
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Esteban
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
> 
> 
> 
> 
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> 

From johan.brichau at uclouvain.be  Mon Feb 16 11:25:44 2009
From: johan.brichau at uclouvain.be (Johan Brichau)
Date: Mon, 16 Feb 2009 11:25:44 +0100
Subject: default seaside pass?
Message-ID: <30B7E16B-7872-474B-81D2-07A4894F9909@uclouvain.be>

Hi,

Just giving the latest pier a spin (downloaded from the website)...

Is the default password for the admin of seaside still admin/pier ? It  
does not seem to accept it when I try to enter the /seaside/config area

----------------------------
Johan Brichau
johan.brichau at uclouvain.be

From renggli at gmail.com  Mon Feb 16 11:45:23 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Mon, 16 Feb 2009 11:45:23 +0100
Subject: default seaside pass?
In-Reply-To: <30B7E16B-7872-474B-81D2-07A4894F9909@uclouvain.be>
References: <30B7E16B-7872-474B-81D2-07A4894F9909@uclouvain.be>
Message-ID: <67628d690902160245w6fa8ae26t57b12c13ad0ba211@mail.gmail.com>

Indeed, there is something wrong with the password/username.

http://code.google.com/p/pier/issues/detail?id=75

Doru will upload a fixed version soon. ;-)

Lukas

On Mon, Feb 16, 2009 at 11:25 AM, Johan Brichau
 wrote:
> Hi,
>
> Just giving the latest pier a spin (downloaded from the website)...
>
> Is the default password for the admin of seaside still admin/pier ? It does
> not seem to accept it when I try to enter the /seaside/config area
>
>
> ----------------------------
> Johan Brichau
> johan.brichau at uclouvain.be
>
>
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From girba at iam.unibe.ch  Mon Feb 16 12:25:50 2009
From: girba at iam.unibe.ch (Tudor Girba)
Date: Mon, 16 Feb 2009 12:25:50 +0100
Subject: default seaside pass?
In-Reply-To: <67628d690902160245w6fa8ae26t57b12c13ad0ba211@mail.gmail.com>
References: <30B7E16B-7872-474B-81D2-07A4894F9909@uclouvain.be>
	<67628d690902160245w6fa8ae26t57b12c13ad0ba211@mail.gmail.com>
Message-ID: <0F0C50FB-6B35-49F4-BE29-4586671307B1@iam.unibe.ch>

The seaside password is seaside. An update will indeed happen in the  
following days.

Cheers,
Doru

On 16 Feb 2009, at 11:45, Lukas Renggli wrote:

> Indeed, there is something wrong with the password/username.
>
> http://code.google.com/p/pier/issues/detail?id=75
>
> Doru will upload a fixed version soon. ;-)
>
> Lukas
>
> On Mon, Feb 16, 2009 at 11:25 AM, Johan Brichau
>  wrote:
>> Hi,
>>
>> Just giving the latest pier a spin (downloaded from the website)...
>>
>> Is the default password for the admin of seaside still admin/pier ?  
>> It does
>> not seem to accept it when I try to enter the /seaside/config area
>>
>>
>> ----------------------------
>> Johan Brichau
>> johan.brichau at uclouvain.be
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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

--
www.tudorgirba.com

"Presenting is storytelling."

From johan.brichau at uclouvain.be  Mon Feb 16 14:50:26 2009
From: johan.brichau at uclouvain.be (Johan Brichau)
Date: Mon, 16 Feb 2009 14:50:26 +0100
Subject: default seaside pass?
In-Reply-To: <0F0C50FB-6B35-49F4-BE29-4586671307B1@iam.unibe.ch>
References: <30B7E16B-7872-474B-81D2-07A4894F9909@uclouvain.be>
	<67628d690902160245w6fa8ae26t57b12c13ad0ba211@mail.gmail.com>
	<0F0C50FB-6B35-49F4-BE29-4586671307B1@iam.unibe.ch>
Message-ID: <4A3B4A34-80D5-45A3-B93E-08FD8CD18041@uclouvain.be>

that's fine. Now that I know the pass, I can get on with it ;-)

thanks!

On 16 Feb 2009, at 12:25, Tudor Girba wrote:

> The seaside password is seaside. An update will indeed happen in the  
> following days.
>
> Cheers,
> Doru
>
>
> On 16 Feb 2009, at 11:45, Lukas Renggli wrote:
>
>> Indeed, there is something wrong with the password/username.
>>
>> http://code.google.com/p/pier/issues/detail?id=75
>>
>> Doru will upload a fixed version soon. ;-)
>>
>> Lukas
>>
>> On Mon, Feb 16, 2009 at 11:25 AM, Johan Brichau
>>  wrote:
>>> Hi,
>>>
>>> Just giving the latest pier a spin (downloaded from the website)...
>>>
>>> Is the default password for the admin of seaside still admin/ 
>>> pier ? It does
>>> not seem to accept it when I try to enter the /seaside/config area
>>>
>>>
>>> ----------------------------
>>> Johan Brichau
>>> johan.brichau at uclouvain.be
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>
> --
> www.tudorgirba.com
>
> "Presenting is storytelling."
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

----------------------------
Johan Brichau
johan.brichau at uclouvain.be

From renggli at gmail.com  Mon Feb 16 23:55:46 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Mon, 16 Feb 2009 23:55:46 +0100
Subject: Magritte and many-to-many (possibly)
In-Reply-To: <40CA21C4-F14A-499C-9D5D-F5180701256A@pinesoft.co.uk>
References: <40CA21C4-F14A-499C-9D5D-F5180701256A@pinesoft.co.uk>
Message-ID: <67628d690902161455s759f857fx60658ebbf27f02cb@mail.gmail.com>

> I wondered if you'd be able to give me a bit of a Magritte pointer. At the
> moment I'm thinking I need to support a many-to-many relationship, and I
> can't see anywhere Magritte provides such support. I'm wondering (a) whether
> there's support and (b) whether I even need it.

Have a look at the subclasses of MARelationDescription, depending on
your exact requirements maybe also just MAOptionDescription
subclasses.

> I've got two lists, list A is the set of stuff from which list B could be
> built.  The two lists belong to different objects. There's already support
> for this in MAListCompositonComponent.

This one is used by MAMultipleOptionDescription.

> However, I then need support to go back and put stuff back from list B into
> list A, in the same form as was previously used to populate it, long after
> the original construction was done. MAListCompositonComponent seems to be
> one-way (ie, the model supports the idea of a list of stuff on it, ie one to
> many).

As far as I understand this is possible with
MAMultipleOptionDescription. Have a look at the references to this
class in Pier for sophisticated examples on how to use it.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From victorhcf at gmail.com  Tue Feb 17 04:43:55 2009
From: victorhcf at gmail.com (Victor Hugo)
Date: Tue, 17 Feb 2009 00:43:55 -0300
Subject: download source code
Message-ID: <4a528b150902161943r8a1d397v90f93f91ba9f6e90@mail.gmail.com>

Hi,

I need to download the source code of olders versions of smallwiki, where
can i found then?
I need the version 1.54, 1.90 and 1.304

best regards!

-- 
Victor Hugo de C. Fernandes
Mestrando do Programa de P?s-Gradua??o em Sistemas e Computa??o - UFRN
Analista de Sistemas / Superintendencia de Inform?tica - UFRN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From renggli at gmail.com  Tue Feb 17 08:16:56 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Tue, 17 Feb 2009 08:16:56 +0100
Subject: download source code
In-Reply-To: <4a528b150902161943r8a1d397v90f93f91ba9f6e90@mail.gmail.com>
References: <4a528b150902161943r8a1d397v90f93f91ba9f6e90@mail.gmail.com>
Message-ID: <67628d690902162316y36acf6fy4f552e61e732216d@mail.gmail.com>

> I need to download the source code of olders versions of smallwiki, where
> can i found then?
> I need the version 1.54, 1.90 and 1.304

All the developemnt versions are downloadable here:

     http://smallwiki.unibe.ch/scgstore/

You might also grab idividual release versions from the Cincom Public
Repository.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From victorhcf at gmail.com  Tue Feb 17 12:44:47 2009
From: victorhcf at gmail.com (Victor Hugo)
Date: Tue, 17 Feb 2009 08:44:47 -0300
Subject: download source code
In-Reply-To: <67628d690902162316y36acf6fy4f552e61e732216d@mail.gmail.com>
References: <4a528b150902161943r8a1d397v90f93f91ba9f6e90@mail.gmail.com>
	<67628d690902162316y36acf6fy4f552e61e732216d@mail.gmail.com>
Message-ID: <4a528b150902170344t1fea6097vb2156438087f9757@mail.gmail.com>

Thanks Lukas.
I have another doubt. How can I acess this respository?
I tried with eclipse/cvs using this options (
http://smallwiki.unibe.ch/howtos/howtousecvs/) without success.

thanks

On Tue, Feb 17, 2009 at 4:16 AM, Lukas Renggli  wrote:

> > I need to download the source code of olders versions of smallwiki, where
> > can i found then?
> > I need the version 1.54, 1.90 and 1.304
>
> All the developemnt versions are downloadable here:
>
>     http://smallwiki.unibe.ch/scgstore/
>
> You might also grab idividual release versions from the Cincom Public
> Repository.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Victor Hugo de C. Fernandes
Mestrando do Programa de P?s-Gradua??o em Sistemas e Computa??o - UFRN
Analista de Sistemas / Superintendencia de Inform?tica - UFRN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From damien.cassou at gmail.com  Tue Feb 17 13:02:17 2009
From: damien.cassou at gmail.com (Damien Cassou)
Date: Tue, 17 Feb 2009 13:02:17 +0100
Subject: download source code
In-Reply-To: <4a528b150902170344t1fea6097vb2156438087f9757@mail.gmail.com>
References: <4a528b150902161943r8a1d397v90f93f91ba9f6e90@mail.gmail.com>
	<67628d690902162316y36acf6fy4f552e61e732216d@mail.gmail.com>
	<4a528b150902170344t1fea6097vb2156438087f9757@mail.gmail.com>
Message-ID: <6ac749c10902170402wac2b69ek5bce103bbc717c94@mail.gmail.com>

On Tue, Feb 17, 2009 at 12:44 PM, Victor Hugo  wrote:
> I have another doubt. How can I acess this respository?

I think you will need Visual Works Cincom Smalltalk

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

From victorhcf at gmail.com  Wed Feb 18 01:17:25 2009
From: victorhcf at gmail.com (Victor Hugo)
Date: Tue, 17 Feb 2009 21:17:25 -0300
Subject: download source code
In-Reply-To: <6ac749c10902170402wac2b69ek5bce103bbc717c94@mail.gmail.com>
References: <4a528b150902161943r8a1d397v90f93f91ba9f6e90@mail.gmail.com>
	<67628d690902162316y36acf6fy4f552e61e732216d@mail.gmail.com>
	<4a528b150902170344t1fea6097vb2156438087f9757@mail.gmail.com>
	<6ac749c10902170402wac2b69ek5bce103bbc717c94@mail.gmail.com>
Message-ID: <4a528b150902171617o79e0394i78c615d5fdfd44ae@mail.gmail.com>

Hmmm
I install visual works cincom smalltalk and no i have access to repository
BUT i could not load the releases that i want because the download dont
start.
I click with right button in release e click in load, the program block and
nothing happens.
I think that is problem in connectio! Should I do any configuration like a
proxy to download the releases?

best regards.

On Tue, Feb 17, 2009 at 9:02 AM, Damien Cassou wrote:

> On Tue, Feb 17, 2009 at 12:44 PM, Victor Hugo  wrote:
> > I have another doubt. How can I acess this respository?
>
> I think you will need Visual Works Cincom Smalltalk
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Victor Hugo de C. Fernandes
Mestrando do Programa de P?s-Gradua??o em Sistemas e Computa??o - UFRN
Analista de Sistemas / Superintendencia de Inform?tica - UFRN
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From chaetal at gmail.com  Thu Feb 19 18:43:21 2009
From: chaetal at gmail.com (Dennis Schetinin)
Date: Thu, 19 Feb 2009 20:43:21 +0300
Subject: Rendering descendant of PRCase
In-Reply-To: <67628d690902131302x5d36fe24v17cf34c7fb28e356@mail.gmail.com>
References: <84f77e270902130752w6fcee90eq1bd684ce62426407@mail.gmail.com>
	<67628d690902131302x5d36fe24v17cf34c7fb28e356@mail.gmail.com>
Message-ID: <84f77e270902190943y1573fdd9t19a62ae8c054c0c6@mail.gmail.com>

> keep  asking questions.
>

Ok... :)

In the custom render method you can use Magritte to generate a
> read-only view of the fields, try something along:
>
> html table: [
>        aStructure description do: [ :each |
>                (each isEditable and: [ each componentClass notNil ])
> ifTrue: [
>                        html tableRow: [
>                                html tableHeading: each label.
>                                html tableData: [
>                                        (each componentClass memento:
> aStructure description: each)
>                                                renderViewerOn: html ] ] ] ]
> ]

This way it ignores pier syntax including all the 'special' symbols in
text... I can't understand how to fix it?

-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From chaetal at gmail.com  Thu Feb 19 19:59:57 2009
From: chaetal at gmail.com (Dennis Schetinin)
Date: Thu, 19 Feb 2009 21:59:57 +0300
Subject: Rendering descendant of PRCase
In-Reply-To: <84f77e270902190943y1573fdd9t19a62ae8c054c0c6@mail.gmail.com>
References: <84f77e270902130752w6fcee90eq1bd684ce62426407@mail.gmail.com>
	<67628d690902131302x5d36fe24v17cf34c7fb28e356@mail.gmail.com>
	<84f77e270902190943y1573fdd9t19a62ae8c054c0c6@mail.gmail.com>
Message-ID: <84f77e270902191059q55b02878k302b5b6bf7af833@mail.gmail.com>

>
> In the custom render method you can use Magritte to generate a
>> read-only view of the fields, try something along:
>>
>> html table: [
>>        aStructure description do: [ :each |
>>                (each isEditable and: [ each componentClass notNil ])
>> ifTrue: [
>>                        html tableRow: [
>>                                html tableHeading: each label.
>>                                html tableData: [
>>                                        (each componentClass memento:
>> aStructure description: each)
>>                                                renderViewerOn: html ] ] ]
>> ] ]
>
>
> This way it ignores pier syntax including all the 'special' symbols in
> text... I can't understand how to fix it?
>

I played a little bit more with Pier and understood this question was
somewhat stupid...

My current idea is the following... For my site I have to do again and again
the same thing: render all the 'details' of the current object and then
render 'overview' of it's children. So, considering the 1-st part (details)
I'd like to tag some fields as details of the object. So I implemented
according methods (*#isDetail*, *#isDetail:*, *#beDetail*) in *MADescription
*. Then I want create DetailedCase as a subclass of *PRCase *and override
there *#accept: *

DetailedCase >> accept: aVisitor
  aVisitor visitDetailedCase: self

In *PRViewRenderer >> visitDetailedCase: anObject* I want to visit every
property (is it correct term?) of *anObject *described as detail...
*but I can't understand how i can do it... can I get a property of object by
description (or vice versa)?*

I expect to get all the details about anObject properly presented on the
page this way. Am I right?

-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From chaetal at gmail.com  Thu Feb 19 20:46:37 2009
From: chaetal at gmail.com (Dennis Schetinin)
Date: Thu, 19 Feb 2009 22:46:37 +0300
Subject: Rendering descendant of PRCase
In-Reply-To: <84f77e270902191059q55b02878k302b5b6bf7af833@mail.gmail.com>
References: <84f77e270902130752w6fcee90eq1bd684ce62426407@mail.gmail.com>
	<67628d690902131302x5d36fe24v17cf34c7fb28e356@mail.gmail.com>
	<84f77e270902190943y1573fdd9t19a62ae8c054c0c6@mail.gmail.com>
	<84f77e270902191059q55b02878k302b5b6bf7af833@mail.gmail.com>
Message-ID: <84f77e270902191146t2508b7e2o36c90327191799b6@mail.gmail.com>

:) Seems like I'm the one who likes to talk to himself...

In the custom render method you can use Magritte to generate a
>>> read-only view of the fields, try something along:
>>>
>>> html table: [
>>>        aStructure description do: [ :each |
>>>                (each isEditable and: [ each componentClass notNil ])
>>> ifTrue: [
>>>                        html tableRow: [
>>>                                html tableHeading: each label.
>>>                                html tableData: [
>>>                                        (each componentClass memento:
>>> aStructure description: each)
>>>                                                renderViewerOn: html ] ] ]
>>> ] ]
>>
>>
>> This way it ignores pier syntax including all the 'special' symbols in
>> text... I can't understand how to fix it?
>>
>
> I played a little bit more with Pier and understood this question was
> somewhat stupid...
>
> My current idea is the following... For my site I have to do again and
> again the same thing: render all the 'details' of the current object and
> then render 'overview' of it's children. So, considering the 1-st part
> (details) I'd like to tag some fields as details of the object. So I
> implemented according methods (*#isDetail*, *#isDetail:*, *#beDetail*) in
> *MADescription*. Then I want create DetailedCase as a subclass of *PRCase
> *and override there *#accept: *
>
> DetailedCase >> accept: aVisitor
>   aVisitor visitDetailedCase: self
>
> In *PRViewRenderer >> visitDetailedCase: anObject* I want to visit every
> property (is it correct term?) of *anObject *described as detail...
> *but I can't understand how i can do it... can I get a property of object
> by description (or vice versa)?*
>
> I expect to get all the details about anObject properly presented on the
> page this way. Am I right?
>

I did:

PRViewRenderer >> visitDetailedCase: anObject
    self remember: anObject while: [ super visitDetailedCase: anObject ]

PRDeepRenderer >> visitDetailedCase: anObject
    anObject detailedDescription
        do: [:each | self
                visit: (*each accessor read: anObject*)]

PRVisitor >> visitDetailedCase: anObject
    self visitCase: anObject

It seems to work except the case when I tag *MAStringDescription *with *
#beDetail*. In that case it tries to visit a String which is collection and
so each of its characters should be visited but visiting is not implemented
for most of objects including Chars... and I'm affraid the same error will
be raised for some other types of description...

Hope to hear (or find by myself if only I'll have enough time) how to do it
all the right way tomorrow... :)

-- 
Dennis Schetinin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From rdrvr.biz at gmail.com  Thu Feb 19 21:52:17 2009
From: rdrvr.biz at gmail.com (David Farber)
Date: Thu, 19 Feb 2009 13:52:17 -0700
Subject: PULogin and PRImagePersistency
Message-ID: 

Since PULogin is a PRCommand, if I am using PRImagePersistency, then  
every time someone logs in a snapshot is scheduled.  That isn't the  
behavior I want.  I there a "clean" way to keep logins from triggering  
a snapshot?

Thanks,
David

----
1 Squeak/Seaside/Pier site deployed

From renggli at gmail.com  Fri Feb 20 00:27:18 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Fri, 20 Feb 2009 00:27:18 +0100
Subject: Rendering descendant of PRCase
In-Reply-To: <84f77e270902191146t2508b7e2o36c90327191799b6@mail.gmail.com>
References: <84f77e270902130752w6fcee90eq1bd684ce62426407@mail.gmail.com>
	<67628d690902131302x5d36fe24v17cf34c7fb28e356@mail.gmail.com>
	<84f77e270902190943y1573fdd9t19a62ae8c054c0c6@mail.gmail.com>
	<84f77e270902191059q55b02878k302b5b6bf7af833@mail.gmail.com>
	<84f77e270902191146t2508b7e2o36c90327191799b6@mail.gmail.com>
Message-ID: <67628d690902191527k3205bc5dif82f74316c13ac5d@mail.gmail.com>

> It seems to work except the case when I tag MAStringDescription with
> #beDetail. In that case it tries to visit a String which is collection and
> so each of its characters should be visited but visiting is not implemented
> for most of objects including Chars... and I'm affraid the same error will
> be raised for some other types of description...

Sounds good so far, you just have to stop the visiting at some point.
In your example when you encounter the MAStringDescription you
probably just want to render the described string instead of
continuing visiting the string and its individual characters. Btw, you
can ask descriptions for a renderable string description like so:

     aDescription toString: value

So even if your value is not a string, all descriptions know how to
convert it to one.

Cheers,
Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From renggli at gmail.com  Fri Feb 20 00:33:11 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Fri, 20 Feb 2009 00:33:11 +0100
Subject: PULogin and PRImagePersistency
In-Reply-To: 
References: 
Message-ID: <67628d690902191533g6d063b03o8aadb380a2fd0c61@mail.gmail.com>

Thanks for reporting, this is actually a bug that was recently
introduced. I fixed it in Pier-Squeak-Persistency-lr.19. Just load
that version and it shouldn't schedule a snapshot anymore.

   Name: Pier-Squeak-Persistency-lr.19
   Author: lr
   Time: 20 February 2009, 12:31:55 am
   UUID: 3d57e4a1-a5c9-4018-b948-a7a61d509cb2
   Ancestors: Pier-Squeak-Persistency-lr.18

   - do not start snapshotting if this is a non-logged command

Cheers,
Lukas

On Thu, Feb 19, 2009 at 9:52 PM, David Farber  wrote:
> Since PULogin is a PRCommand, if I am using PRImagePersistency, then every
> time someone logs in a snapshot is scheduled.  That isn't the behavior I
> want.  I there a "clean" way to keep logins from triggering a snapshot?
>
> Thanks,
> David
>
> ----
> 1 Squeak/Seaside/Pier site deployed
>
>
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From rdrvr.biz at gmail.com  Sat Feb 21 06:27:09 2009
From: rdrvr.biz at gmail.com (David Farber)
Date: Fri, 20 Feb 2009 22:27:09 -0700
Subject: piercms.com
Message-ID: 

Lukas - I noticed today that http://piercms.com (i.e. without the www)  
points to SeasideHosting not www.piercms.com.

David
----
1 Squeak/Seaside/Pier site deployed

From rdrvr.biz at gmail.com  Sat Feb 21 06:30:24 2009
From: rdrvr.biz at gmail.com (David Farber)
Date: Fri, 20 Feb 2009 22:30:24 -0700
Subject: New Pier import/export
Message-ID: <4DA1BDC3-F88B-4538-A9DB-952A5A51A7B6@gmail.com>

Lukas - Care to talk a little bit about the new import/export  
functionality?  I haven't had a chance to look at the code yet.  What  
is the overall strategy?  Is there a way to hook my own data into the  
process?

David
----
1 Squeak/Seaside/Pier site deployed

From renggli at gmail.com  Sat Feb 21 11:13:09 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 21 Feb 2009 11:13:09 +0100
Subject: New Pier import/export
In-Reply-To: <4DA1BDC3-F88B-4538-A9DB-952A5A51A7B6@gmail.com>
References: <4DA1BDC3-F88B-4538-A9DB-952A5A51A7B6@gmail.com>
Message-ID: <67628d690902210213n27008a6avf8273389880f124@mail.gmail.com>

I am sure you read this one .

The implementation uses the reference streams, so it is slow and
inefficient but any of your own data that is referenced from the
kernel or any of the structures should automatically come with it.
External files are intentionally left out to avoid the image blowing
up. It is reasonably simple to just move the external files from the
file-system so that the target image can find them.

Cheers,
Lukas

On Sat, Feb 21, 2009 at 6:30 AM, David Farber  wrote:
> Lukas - Care to talk a little bit about the new import/export functionality?
>  I haven't had a chance to look at the code yet.  What is the overall
> strategy?  Is there a way to hook my own data into the process?
>
> David
> ----
> 1 Squeak/Seaside/Pier site deployed
>
>
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From renggli at gmail.com  Sat Feb 21 11:13:39 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Sat, 21 Feb 2009 11:13:39 +0100
Subject: piercms.com
In-Reply-To: 
References: 
Message-ID: <67628d690902210213s2228c4fdof672cc31b48dc311@mail.gmail.com>

I think that's a limitation of seasidehosting.st. We can't do anything
about that.

Lukas

On Sat, Feb 21, 2009 at 6:27 AM, David Farber  wrote:
> Lukas - I noticed today that http://piercms.com (i.e. without the www)
> points to SeasideHosting not www.piercms.com.
>
> David
> ----
> 1 Squeak/Seaside/Pier site deployed
>
>
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From girba at iam.unibe.ch  Sat Feb 21 14:53:49 2009
From: girba at iam.unibe.ch (Tudor Girba)
Date: Sat, 21 Feb 2009 14:53:49 +0100
Subject: piercms.com
In-Reply-To: <67628d690902210213s2228c4fdof672cc31b48dc311@mail.gmail.com>
References: 
	<67628d690902210213s2228c4fdof672cc31b48dc311@mail.gmail.com>
Message-ID: 

Indeed, seasidehosting offers the possibility to map only one address  
to a seaside application.

Cheers,
Doru

On 21 Feb 2009, at 11:13, Lukas Renggli wrote:

> I think that's a limitation of seasidehosting.st. We can't do anything
> about that.
>
> Lukas
>
> On Sat, Feb 21, 2009 at 6:27 AM, David Farber   
> wrote:
>> Lukas - I noticed today that http://piercms.com (i.e. without the  
>> www)
>> points to SeasideHosting not www.piercms.com.
>>
>> David
>> ----
>> 1 Squeak/Seaside/Pier site deployed
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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

--
www.tudorgirba.com

"Every thing has its own flow."

From p3anoman at gmail.com  Sat Feb 21 23:29:03 2009
From: p3anoman at gmail.com (John M)
Date: Sat, 21 Feb 2009 17:29:03 -0500
Subject: SQL
Message-ID: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>

Good day all,
I am looking at the Magritte/Pier "bible" (Reng06a.pdf) Sec 2.3.2 (page 8)
Object Relational Mapping. I decided I would take a stab at implementing:
"In a very similar way, we are able to automatically create SQL statements
to store, load and query objects from a relational database". Any one care
to offer hints? I am very much a novice at all these patterns and things, so
I am guessing a Visitor pattern of sorts (I HAVE been studying the Gang of
Four bible tho ;)....

Here is what I have so far:

MADescription:
 added methods:
>> toSql: anObject    ^self toSql: anObject writer: self sqlWriter.
>>sqlWriter   ^self propertyAt: #sqlWriter ifAbsent: self class
defaultSqlWriter.
class>>defaultSqlWriter  ^SQLWriter

And I have created  MAWriter subclass SQLWriter with one instance variable
'sql'
SQLWriter>>defaultWriteStream
    ^((sql isNil ifTrue: [ sql := String new]) writeStream).
SQLWriter>>write: anObject description: aDescription to: aStream
    anObject isNil ifTrue: [ ^ aDescription undefined ].
    ^ super write: anObject description: aDescription to: aStream  which,
looking at it now, I really shouldn't need to override

Then there are the visiting method which are going to be the reall tricky
part.
SQLWriter>>visitContainer: aDescription
    aDescription memento model isNil  "we have a NEW model object so
INSERT"   will this work????? heh
        ifTrue: [ stream nextPutAll: 'INSERT INTO '; nextPutAll:
aDescription table; nextPutAll: ' VALUES ('; cr ]  where does the table
method come in? hmmm
        ifFalse: [ stream nextPutAll: 'UPDATE '; nextPutAll aDescription
table; cr; nextPutAll: 'SET ' ].

And then I will need to add something like:
     aDescription do: [ :desc | self write: something description: desc
stream: stream ]     What something goes here I am still scratching my head
about...

Any help/suggetions with this last part would be greatly appreciated.

Also, I have started to get used to looking at the unit tests to figure out
what things are supposed to do, then I noticed that there are NO tests for
MAVisitor and subclasses. Why is that? (Or am I missing something?)

Thanks in advance for any advice
John McKeon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From keith_hodges at yahoo.co.uk  Sun Feb 22 00:26:43 2009
From: keith_hodges at yahoo.co.uk (Keith Hodges)
Date: Sat, 21 Feb 2009 23:26:43 +0000
Subject: SQL
In-Reply-To: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
References: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
Message-ID: <49A08DB3.609@yahoo.co.uk>

Have you looked a Magritte-RDB package in magritteaddons repository?

Keith

From p3anoman at gmail.com  Sun Feb 22 00:49:14 2009
From: p3anoman at gmail.com (John M)
Date: Sat, 21 Feb 2009 18:49:14 -0500
Subject: SQL
In-Reply-To: <49A08DB3.609@yahoo.co.uk>
References: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
	<49A08DB3.609@yahoo.co.uk>
Message-ID: <40f637ec0902211549r4de26087l54fd82770e51dc03@mail.gmail.com>

No - are you accusing me of cheating? lol
I will have a look. Thanks Keith

On Sat, Feb 21, 2009 at 6:26 PM, Keith Hodges wrote:

> Have you looked a Magritte-RDB package in magritteaddons repository?
>
> Keith
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From renggli at gmail.com  Sun Feb 22 01:00:56 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Sun, 22 Feb 2009 01:00:56 +0100
Subject: SQL
In-Reply-To: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
References: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
Message-ID: <67628d690902211600x20cfd412mc782becd7a996852@mail.gmail.com>

> Also, I have started to get used to looking at the unit tests to figure out
> what things are supposed to do, then I noticed that there are NO tests for
> MAVisitor and subclasses. Why is that? (Or am I missing something?)

There are tests, but the tests do not directly work with the visitors
but indirectly through the descriptions. For example the tests
MAElementDescriptionTest>>#testToString... and #testFromString... test
MAStringReader and MAStringWriter.

I cannot comment on your approach, because I don't exactly know what
you want to do.

Additionally to what Keith pointed out, there is the package
Magritte-Roe in . It
depends on ROE and the PostgreSQL drivers (both from SqueakSource) and
provides a simple object mapping mechanism that I used in a few
commercial projects. Usually I prefer to directly persist objects
(instead of relations) though.

Cheers,
Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From damien.cassou at gmail.com  Sun Feb 22 11:20:47 2009
From: damien.cassou at gmail.com (Damien Cassou)
Date: Sun, 22 Feb 2009 11:20:47 +0100
Subject: SQL
In-Reply-To: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
References: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
Message-ID: <6ac749c10902220220w334dff0dq74915e959c7bf073@mail.gmail.com>

Hi John,

On Sat, Feb 21, 2009 at 11:29 PM, John M  wrote:
> I am looking at the Magritte/Pier "bible" (Reng06a.pdf) Sec 2.3.2 (page 8)
> Object Relational Mapping. I decided I would take a stab at implementing:
> "In a very similar way, we are able to automatically create SQL statements
> to store, load and query objects from a relational database". Any one care
> to offer hints?

long time ago I had to do a student project and I hacked a link
between Magritte and MySQL: http://www.squeaksource.com/GestionImmo/.

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

From keith_hodges at yahoo.co.uk  Sun Feb 22 18:54:07 2009
From: keith_hodges at yahoo.co.uk (Keith Hodges)
Date: Sun, 22 Feb 2009 17:54:07 +0000
Subject: SQL
In-Reply-To: <6ac749c10902220220w334dff0dq74915e959c7bf073@mail.gmail.com>
References: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
	<6ac749c10902220220w334dff0dq74915e959c7bf073@mail.gmail.com>
Message-ID: <49A1913F.2070704@yahoo.co.uk>

> long time ago I had to do a student project and I hacked a link
> between Magritte and MySQL: http://www.squeaksource.com/GestionImmo/.
>   
Magritte-RDB is a contiuation of the ideas in GestionImmo

Keith

p.s. Roe is something I never understood

From renggli at gmail.com  Sun Feb 22 19:13:47 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Sun, 22 Feb 2009 19:13:47 +0100
Subject: SQL
In-Reply-To: <49A1913F.2070704@yahoo.co.uk>
References: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
	<6ac749c10902220220w334dff0dq74915e959c7bf073@mail.gmail.com>
	<49A1913F.2070704@yahoo.co.uk>
Message-ID: <67628d690902221013l421d94cawba5b427883dd6b5b@mail.gmail.com>

> p.s. Roe is something I never understood

If you know the Smalltalk Collection hierarchy you know ROE.

ROE provides an interface to be able to filter, collect and iterate
over relational tables exactly the same way as Smalltalk collections.
Magritte-ROE mixes this excellent query interface with basic
meta-described object-relational mapping.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From p3anoman at gmail.com  Mon Feb 23 03:59:49 2009
From: p3anoman at gmail.com (John M)
Date: Sun, 22 Feb 2009 21:59:49 -0500
Subject: SQL
In-Reply-To: <67628d690902221013l421d94cawba5b427883dd6b5b@mail.gmail.com>
References: <40f637ec0902211429r63c53486k7146d1df3d7cf2d4@mail.gmail.com>
	<6ac749c10902220220w334dff0dq74915e959c7bf073@mail.gmail.com>
	<49A1913F.2070704@yahoo.co.uk>
	<67628d690902221013l421d94cawba5b427883dd6b5b@mail.gmail.com>
Message-ID: <40f637ec0902221859y1893e0abva6054a7a06047273@mail.gmail.com>

I thank you all for your comments.

My original intent was to create _simple_ insert, update and select
statements from model descriptions. Skipping relation and reference
descriptions, no complex joins etc.

The frameworks suggested are quite robust, and complex, which, being at
quite an early stage of learning just about everything (Smalltalk, Seaside,
Magritteetc), I am trying to avoid - the complexity that is. It has been a
good exercise in delving into the mechanics of Magritte though, so I
continue to learn.

GREAT code btw, just a lot to grok.

Also, it would appear that Magritte-ROE requires that Postgresql be
_running_ when the package is installed as it failed when trying to connect
up a Socket to port 5432.

Thanks again
Warm regards
John

On Sun, Feb 22, 2009 at 1:13 PM, Lukas Renggli  wrote:

> > p.s. Roe is something I never understood
>
> If you know the Smalltalk Collection hierarchy you know ROE.
>
> ROE provides an interface to be able to filter, collect and iterate
> over relational tables exactly the same way as Smalltalk collections.
> Magritte-ROE mixes this excellent query interface with basic
> meta-described object-relational mapping.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From norbert at hartl.name  Wed Feb 25 09:43:01 2009
From: norbert at hartl.name (Norbert Hartl)
Date: Wed, 25 Feb 2009 09:43:01 +0100
Subject: Using Magritte objects  in pier
Message-ID: <1235551381.23539.20.camel@cineflux>

Hi,

last week I did a new start on pier (ok, I do this every
couple of months :) ). I did an application in the late
2006 I'm now trying to ressurect. I developed myself an
external component tree that has a configuration for the
whole site. It has several display modi and makes heavily
use of Announcements to switch/show stuff.

Now I'm thinking that I could benefit by exchanging my
component tree with pier. This way it would be more
flexible and a lot of decorating html stuff could be 
managed by pier.

In the project I also use magritte. I'm not very familiar
with pier so my questions might be very stupid.

- How do I embedded any magritte object on a page? In my
  code I just do anObject asComponent. Is there an easy
  way to just integrate objects on a page. It needs some
  tricks in order not to display all the time the same 
  object. I think yo know what I mean 

- If there is a good solution for the above is there a
  solution for displaying individual slots of an object?
  I mean to have access to an individual component class
  for an instance variable. The most difficult thing 
  (while developing the project) was to layout the
  magritte forms. I would like to see something like 
  +mySuperObject/@title+
  +mySuperObject/@text+
  to display the component classes of the object and
  dealing with the rest of the html the pier way.

There are more questions to come :) 

Norbert

From renggli at gmail.com  Wed Feb 25 10:07:03 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 25 Feb 2009 10:07:03 +0100
Subject: Using Magritte objects in pier
In-Reply-To: <1235551381.23539.20.camel@cineflux>
References: <1235551381.23539.20.camel@cineflux>
Message-ID: <67628d690902250107h312b5649x45b3972ce6d92c44@mail.gmail.com>

> - How do I embedded any magritte object on a page? In my
> ?code I just do anObject asComponent. Is there an easy
> ?way to just integrate objects on a page. It needs some
> ?tricks in order not to display all the time the same
> ?object. I think yo know what I mean

You can embed any Seaside component into Pier. In the case of a
Magritte component you might need to wrap it into a normal Seaside
component that returns true for #canBeRoot and that sets-up the
Magritte component.

Simply create an embedded link in the page like so: +magritte-form+.
Click on the link to add a component and select your component from
the list.

> - If there is a good solution for the above is there a
> ?solution for displaying individual slots of an object?
> ?I mean to have access to an individual component class
> ?for an instance variable. The most difficult thing
> ?(while developing the project) was to layout the
> ?magritte forms. I would like to see something like
> ?+mySuperObject/@title+
> ?+mySuperObject/@text+
> ?to display the component classes of the object and
> ?dealing with the rest of the html the pier way.

Mhh ... links support parameters, but that use-case is currently not
implemented. Maybe you want to give a try and implement that yourself?

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From norbert at hartl.name  Wed Feb 25 11:33:08 2009
From: norbert at hartl.name (Norbert Hartl)
Date: Wed, 25 Feb 2009 11:33:08 +0100
Subject: Using Magritte objects in pier
In-Reply-To: <67628d690902250107h312b5649x45b3972ce6d92c44@mail.gmail.com>
References: <1235551381.23539.20.camel@cineflux>
	<67628d690902250107h312b5649x45b3972ce6d92c44@mail.gmail.com>
Message-ID: <1235557988.23539.26.camel@cineflux>

On Wed, 2009-02-25 at 10:07 +0100, Lukas Renggli wrote:
> > - How do I embedded any magritte object on a page? In my
> >  code I just do anObject asComponent. Is there an easy
> >  way to just integrate objects on a page. It needs some
> >  tricks in order not to display all the time the same
> >  object. I think yo know what I mean
> 
> You can embed any Seaside component into Pier. In the case of a
> Magritte component you might need to wrap it into a normal Seaside
> component that returns true for #canBeRoot and that sets-up the
> Magritte component.
> 
> Simply create an embedded link in the page like so: +magritte-form+.
> Click on the link to add a component and select your component from
> the list.
> 
Ok, thanks, I expected that. It is not big of a problem. With an
additional component I can set up the announcements as well. It just
makes the following approach a little more complicated.

> > - If there is a good solution for the above is there a
> >  solution for displaying individual slots of an object?
> >  I mean to have access to an individual component class
> >  for an instance variable. The most difficult thing
> >  (while developing the project) was to layout the
> >  magritte forms. I would like to see something like
> >  +mySuperObject/@title+
> >  +mySuperObject/@text+
> >  to display the component classes of the object and
> >  dealing with the rest of the html the pier way.
> 
> Mhh ... links support parameters, but that use-case is currently not
> implemented. Maybe you want to give a try and implement that yourself?
> 
Yes, I'll give it a try. I need to know pier anyway if I want to use
it. It is just that I had a very hard time to resolve even simple
things in pier. I can accept the "structure is everything" thingy but
most of this is than "the structure in your brain" and that is hard to
follow. I scan again the papers I collected about magritte and pier over
the years. At the moment it is an infinite learning curve (the structure
seems to be a graph :) ).

thanks so far,

Norbert

From ducasse at iam.unibe.ch  Wed Feb 25 11:51:34 2009
From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=)
Date: Wed, 25 Feb 2009 11:51:34 +0100
Subject: Using Magritte objects in pier
In-Reply-To: <1235557988.23539.26.camel@cineflux>
References: <1235551381.23539.20.camel@cineflux>
	<67628d690902250107h312b5649x45b3972ce6d92c44@mail.gmail.com>
	<1235557988.23539.26.camel@cineflux>
Message-ID: <100FFBDA-A12D-42B0-81B5-392418E62D6F@iam.unibe.ch>

If you can report what you found difficult it would be great.
because pier should improve on that level

Stef
On Feb 25, 2009, at 11:33 AM, Norbert Hartl wrote:

> On Wed, 2009-02-25 at 10:07 +0100, Lukas Renggli wrote:
>>> - How do I embedded any magritte object on a page? In my
>>> code I just do anObject asComponent. Is there an easy
>>> way to just integrate objects on a page. It needs some
>>> tricks in order not to display all the time the same
>>> object. I think yo know what I mean
>>
>> You can embed any Seaside component into Pier. In the case of a
>> Magritte component you might need to wrap it into a normal Seaside
>> component that returns true for #canBeRoot and that sets-up the
>> Magritte component.
>>
>> Simply create an embedded link in the page like so: +magritte-form+.
>> Click on the link to add a component and select your component from
>> the list.
>>
> Ok, thanks, I expected that. It is not big of a problem. With an
> additional component I can set up the announcements as well. It just
> makes the following approach a little more complicated.
>
>>> - If there is a good solution for the above is there a
>>> solution for displaying individual slots of an object?
>>> I mean to have access to an individual component class
>>> for an instance variable. The most difficult thing
>>> (while developing the project) was to layout the
>>> magritte forms. I would like to see something like
>>> +mySuperObject/@title+
>>> +mySuperObject/@text+
>>> to display the component classes of the object and
>>> dealing with the rest of the html the pier way.
>>
>> Mhh ... links support parameters, but that use-case is currently not
>> implemented. Maybe you want to give a try and implement that  
>> yourself?
>>
> Yes, I'll give it a try. I need to know pier anyway if I want to use
> it. It is just that I had a very hard time to resolve even simple
> things in pier. I can accept the "structure is everything" thingy but
> most of this is than "the structure in your brain" and that is hard to
> follow. I scan again the papers I collected about magritte and pier  
> over
> the years. At the moment it is an infinite learning curve (the  
> structure
> seems to be a graph :) ).
>
> thanks so far,
>
> Norbert
>
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

From renggli at gmail.com  Wed Feb 25 19:10:39 2009
From: renggli at gmail.com (Lukas Renggli)
Date: Wed, 25 Feb 2009 19:10:39 +0100
Subject: Using Magritte objects in pier
In-Reply-To: <1235557988.23539.26.camel@cineflux>
References: <1235551381.23539.20.camel@cineflux>
	<67628d690902250107h312b5649x45b3972ce6d92c44@mail.gmail.com>
	<1235557988.23539.26.camel@cineflux>
Message-ID: <67628d690902251010v5e3b2339h227ae8536fb3991a@mail.gmail.com>

> Yes, I'll give it a try. I need to know pier anyway if I want to use
> it. It is just that I had a very hard time to resolve even simple
> things in pier. I can accept the "structure is everything" thingy but
> most of this is than "the structure in your brain" and that is hard to
> follow. I scan again the papers I collected about magritte and pier over
> the years. At the moment it is an infinite learning curve

Personally I wouldn't try to build a complex model as subclasses of
structure, unless they have a clear mapping to a tree. For example the
subpages of a blog are posts and comments, the subpages of an issue
tracker as issues and comments, and the subpages of a shop are
categories and articles. In other cases it is most certainly easier to
embed an independent Seaside application into the website.

> (the structure seems to be a graph :) ).

That's true, but most important the structure and their children form
a tree, much like the directory and files on your harddisc. The graph
like structure comes from the fact that structures can link and embed
into each other, but that's just at the level of the document.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

From norbert at hartl.name  Wed Feb 25 20:54:43 2009
From: norbert at hartl.name (Norbert Hartl)
Date: Wed, 25 Feb 2009 20:54:43 +0100
Subject: Using Magritte objects in pier
In-Reply-To: <67628d690902251010v5e3b2339h227ae8536fb3991a@mail.gmail.com>
References: <1235551381.23539.20.camel@cineflux>
	<67628d690902250107h312b5649x45b3972ce6d92c44@mail.gmail.com>
	<1235557988.23539.26.camel@cineflux>
	<67628d690902251010v5e3b2339h227ae8536fb3991a@mail.gmail.com>
Message-ID: <1235591683.17533.46.camel@cineflux>

On Wed, 2009-02-25 at 19:10 +0100, Lukas Renggli wrote:
> > Yes, I'll give it a try. I need to know pier anyway if I want to use
> > it. It is just that I had a very hard time to resolve even simple
> > things in pier. I can accept the "structure is everything" thingy but
> > most of this is than "the structure in your brain" and that is hard to
> > follow. I scan again the papers I collected about magritte and pier over
> > the years. At the moment it is an infinite learning curve
> 
> Personally I wouldn't try to build a complex model as subclasses of
> structure, unless they have a clear mapping to a tree. For example the
> subpages of a blog are posts and comments, the subpages of an issue
> tracker as issues and comments, and the subpages of a shop are
> categories and articles. In other cases it is most certainly easier to
> embed an independent Seaside application into the website.
> 
That's what I'm trying to to do. I have loads of components to embed.
I just want to try to build the skeleton with pier and embed my 
components into that. Some times (in the case of editors) it is good
to have not only pier _or_ component but to interfere both a little. So
you embed a component but layout the structure of the component with
the tools pier has. 

For me there are at least two views on my site. The one is sitemap
specific where everything has a location. That's the tree pier is 
providing. The other view would be more object/rest centric where
you request an object/content to be displayed and don't care where it
is displayed. I have this already as the description of an object knows
the preferred location where it likes to be displayed. And the location
is configured in a way that it displays the object/content. 

For me the same thing is valid for the roles. The tree and look are
provided by the web designer. I'm just providing the business logic.
My structure lies underneath where only I can see it :)

> > (the structure seems to be a graph :) ).
> 
> That's true, but most important the structure and their children form
> a tree, much like the directory and files on your harddisc. The graph
> like structure comes from the fact that structures can link and embed
> into each other, but that's just at the level of the document.
> 
Yo, was meant as a joke. Just figuring out all the structure-children,
structure-environement stuff.

Norbert

From p3anoman at gmail.com  Wed Feb 25 21:15:09 2009
From: p3anoman at gmail.com (John M)
Date: Wed, 25 Feb 2009 15:15:09 -0500
Subject: Using Magritte objects in pier
In-Reply-To: <67628d690902250107h312b5649x45b3972ce6d92c44@mail.gmail.com>
References: <1235551381.23539.20.camel@cineflux>
	<67628d690902250107h312b5649x45b3972ce6d92c44@mail.gmail.com>
Message-ID: <40f637ec0902251215x76d64819pb536c4ca95125fba@mail.gmail.com>

On Wed, Feb 25, 2009 at 4:07 AM, Lukas Renggli  wrote:

> You can embed any Seaside component into Pier. In the case of a
> Magritte component you might need to wrap it into a normal Seaside
> component that returns true for #canBeRoot and that sets-up the
> Magritte component.
>
> Simply create an embedded link in the page like so: +magritte-form+.
> Click on the link to add a component and select your component from
> the list.
>

That is just amazing.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From norbert at hartl.name  Wed Feb 25 22:58:53 2009
From: norbert at hartl.name (Norbert Hartl)
Date: Wed, 25 Feb 2009 22:58:53 +0100
Subject: Nesting design
Message-ID: <1235599133.17533.64.camel@cineflux>

I'm a little bit further in understanding the structure 
stuff with settings and environment. 

Is there a way to have one environment rendered
inside another one. In bigger sites you have nested
layouts. As an example:

Title
-> navigation bar
   -> sub navigation bar 1
      - component 1
   -> sub navigation bar 2
      - component 2
-> about section without nav bar

To me it appears that in pier I would always have to
provide the whole layout even if only component 1 and
component 2 differ by the sub nav bars. So the environment
for component 1 would include all stuff for

Title, navigation bar and sub navigation 1

and component 2 would include all layout for

Title, navigation bar and sub navigation 2

Or is there a way to nest them properly to have every
single layout only once?

Norbert

From girba at iam.unibe.ch  Wed Feb 25 23:06:12 2009
From: girba at iam.unibe.ch (Tudor Girba)
Date: Wed, 25 Feb 2009 23:06:12 +0100
Subject: Nesting design
In-Reply-To: <1235599133.17533.64.camel@cineflux>
References: <1235599133.17533.64.camel@cineflux>
Message-ID: <4EDB753B-8950-4DA3-8B15-4DBD89B37D4A@iam.unibe.ch>

Hi Norbert,

I did not really understand your example :), but you can always  
extract common parts into separate pages and then embed these pages  
into the environment.

Does that answer the question?

Cheers,
Doru

On 25 Feb 2009, at 22:58, Norbert Hartl wrote:

> I'm a little bit further in understanding the structure
> stuff with settings and environment.
>
> Is there a way to have one environment rendered
> inside another one. In bigger sites you have nested
> layouts. As an example:
>
> Title
> -> navigation bar
>   -> sub navigation bar 1
>      - component 1
>   -> sub navigation bar 2
>      - component 2
> -> about section without nav bar
>
>
> To me it appears that in pier I would always have to
> provide the whole layout even if only component 1 and
> component 2 differ by the sub nav bars. So the environment
> for component 1 would include all stuff for
>
> Title, navigation bar and sub navigation 1
>
> and component 2 would include all layout for
>
> Title, navigation bar and sub navigation 2
>
> Or is there a way to nest them properly to have every
> single layout only once?
>
> Norbert
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

--
www.tudorgirba.com

"What we can governs what we wish."

From norbert at hartl.name  Wed Feb 25 23:19:13 2009
From: norbert at hartl.name (Norbert Hartl)
Date: Wed, 25 Feb 2009 23:19:13 +0100
Subject: Nesting design
In-Reply-To: <4EDB753B-8950-4DA3-8B15-4DBD89B37D4A@iam.unibe.ch>
References: <1235599133.17533.64.camel@cineflux>
	<4EDB753B-8950-4DA3-8B15-4DBD89B37D4A@iam.unibe.ch>
Message-ID: <1235600353.17533.70.camel@cineflux>

On Wed, 2009-02-25 at 23:06 +0100, Tudor Girba wrote:
> Hi Norbert,
> 
> I did not really understand your example :), but you can always  
> extract common parts into separate pages and then embed these pages  
> into the environment.
> 
Hmmm, took some extra time to make a clear example. Seems it
didn't work out.:)

> Does that answer the question?
> 
Sort of. I just recognized that my problem is not that big as
it seemed before. What I tried to explain is:

If you have an environment that contains a header and a menu
component and you want to change that in a child page than you
have to provide an environment that not only contains changed
stuff but also the header and the menu again. 
Clustering stuff like header seems the lessen the problem. You
need to provide all the time the complete page layout but if it
is structured well that is not much.

I hope this is a little bit clearer now.

Norbert

> Cheers,
> Doru
> 
> 
> On 25 Feb 2009, at 22:58, Norbert Hartl wrote:
> 
> > I'm a little bit further in understanding the structure
> > stuff with settings and environment.
> >
> > Is there a way to have one environment rendered
> > inside another one. In bigger sites you have nested
> > layouts. As an example:
> >
> > Title
> > -> navigation bar
> >   -> sub navigation bar 1
> >      - component 1
> >   -> sub navigation bar 2
> >      - component 2
> > -> about section without nav bar
> >
> >
> > To me it appears that in pier I would always have to
> > provide the whole layout even if only component 1 and
> > component 2 differ by the sub nav bars. So the environment
> > for component 1 would include all stuff for
> >
> > Title, navigation bar and sub navigation 1
> >
> > and component 2 would include all layout for
> >
> > Title, navigation bar and sub navigation 2
> >
> > Or is there a way to nest them properly to have every
> > single layout only once?
> >
> > Norbert
> >
> >
> > _______________________________________________
> > SmallWiki, Magritte, Pier and Related Tools ...
> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> 
> --
> www.tudorgirba.com
> 
> "What we can governs what we wish."
> 
> 
> 
> 
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

From girba at iam.unibe.ch  Thu Feb 26 00:04:39 2009
From: girba at iam.unibe.ch (Tudor Girba)
Date: Thu, 26 Feb 2009 00:04:39 +0100
Subject: Nesting design
In-Reply-To: <1235600353.17533.70.camel@cineflux>
References: <1235599133.17533.64.camel@cineflux>
	<4EDB753B-8950-4DA3-8B15-4DBD89B37D4A@iam.unibe.ch>
	<1235600353.17533.70.camel@cineflux>
Message-ID: <03D01CF6-4ACB-4008-A5E3-C641E4F2D593@iam.unibe.ch>

Hi,

>> I did not really understand your example :), but you can always
>> extract common parts into separate pages and then embed these pages
>> into the environment.
>>
> Hmmm, took some extra time to make a clear example. Seems it
> didn't work out.:)
>
>> Does that answer the question?
>>
> Sort of. I just recognized that my problem is not that big as
> it seemed before. What I tried to explain is:
>
> If you have an environment that contains a header and a menu
> component and you want to change that in a child page than you
> have to provide an environment that not only contains changed
> stuff but also the header and the menu again.
> Clustering stuff like header seems the lessen the problem. You
> need to provide all the time the complete page layout but if it
> is structured well that is not much.

Exactly.

However, there are some quite smart components that will make your  
life much easier once you get to know them. One of them is the  
Document. If you embed this one in the environment, you will get an  
extra place that you will be able to edit.

For example, you can use it as a placeholder for the header, and add  
the header in the Document.

Furthermore, Document can inherit from the parent page. Thus, you can  
provide a "default" header in the root page and then override it only  
when you want it to be different in the children.

Hmm, is what I wrote understandable? :)

Cheers,
Doru

> Norbert
>
>> Cheers,
>> Doru
>>
>>
>> On 25 Feb 2009, at 22:58, Norbert Hartl wrote:
>>
>>> I'm a little bit further in understanding the structure
>>> stuff with settings and environment.
>>>
>>> Is there a way to have one environment rendered
>>> inside another one. In bigger sites you have nested
>>> layouts. As an example:
>>>
>>> Title
>>> -> navigation bar
>>>  -> sub navigation bar 1
>>>     - component 1
>>>  -> sub navigation bar 2
>>>     - component 2
>>> -> about section without nav bar
>>>
>>>
>>> To me it appears that in pier I would always have to
>>> provide the whole layout even if only component 1 and
>>> component 2 differ by the sub nav bars. So the environment
>>> for component 1 would include all stuff for
>>>
>>> Title, navigation bar and sub navigation 1
>>>
>>> and component 2 would include all layout for
>>>
>>> Title, navigation bar and sub navigation 2
>>>
>>> Or is there a way to nest them properly to have every
>>> single layout only once?
>>>
>>> Norbert
>>>
>>>
>>> _______________________________________________
>>> SmallWiki, Magritte, Pier and Related Tools ...
>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>> --
>> www.tudorgirba.com
>>
>> "What we can governs what we wish."
>>
>>
>>
>>
>> _______________________________________________
>> 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

--
www.tudorgirba.com

"Presenting is storytelling."

From norbert at hartl.name  Thu Feb 26 10:44:19 2009
From: norbert at hartl.name (Norbert Hartl)
Date: Thu, 26 Feb 2009 10:44:19 +0100
Subject: Nesting design
In-Reply-To: <03D01CF6-4ACB-4008-A5E3-C641E4F2D593@iam.unibe.ch>
References: <1235599133.17533.64.camel@cineflux>
	<4EDB753B-8950-4DA3-8B15-4DBD89B37D4A@iam.unibe.ch>
	<1235600353.17533.70.camel@cineflux>
	<03D01CF6-4ACB-4008-A5E3-C641E4F2D593@iam.unibe.ch>
Message-ID: <1235641459.26814.11.camel@cineflux>

On Thu, 2009-02-26 at 00:04 +0100, Tudor Girba wrote:
> Hi,
> 
> >> I did not really understand your example :), but you can always
> >> extract common parts into separate pages and then embed these pages
> >> into the environment.
> >>
> > Hmmm, took some extra time to make a clear example. Seems it
> > didn't work out.:)
> >
> >> Does that answer the question?
> >>
> > Sort of. I just recognized that my problem is not that big as
> > it seemed before. What I tried to explain is:
> >
> > If you have an environment that contains a header and a menu
> > component and you want to change that in a child page than you
> > have to provide an environment that not only contains changed
> > stuff but also the header and the menu again.
> > Clustering stuff like header seems the lessen the problem. You
> > need to provide all the time the complete page layout but if it
> > is structured well that is not much.
> 
> Exactly.
> 
> However, there are some quite smart components that will make your  
> life much easier once you get to know them. One of them is the  
> Document. If you embed this one in the environment, you will get an  
> extra place that you will be able to edit.
> 
Thanks. That's the kind of tips I need at the moment. 

> For example, you can use it as a placeholder for the header, and add  
> the header in the Document.
> 

> Furthermore, Document can inherit from the parent page. Thus, you can  
> provide a "default" header in the root page and then override it only  
> when you want it to be different in the children.
> 
Hmmmm, sounds good and spooky at the same time. There is even more
hierarchies to build than the ones I discovered.

> Hmm, is what I wrote understandable? :)

It was for sure a good hint that points in the right direction. 

Norbert
> 
> >
> >>
> >> On 25 Feb 2009, at 22:58, Norbert Hartl wrote:
> >>
> >>> I'm a little bit further in understanding the structure
> >>> stuff with settings and environment.
> >>>
> >>> Is there a way to have one environment rendered
> >>> inside another one. In bigger sites you have nested
> >>> layouts. As an example:
> >>>
> >>> Title
> >>> -> navigation bar
> >>>  -> sub navigation bar 1
> >>>     - component 1
> >>>  -> sub navigation bar 2
> >>>     - component 2
> >>> -> about section without nav bar
> >>>
> >>>
> >>> To me it appears that in pier I would always have to
> >>> provide the whole layout even if only component 1 and
> >>> component 2 differ by the sub nav bars. So the environment
> >>> for component 1 would include all stuff for
> >>>
> >>> Title, navigation bar and sub navigation 1
> >>>
> >>> and component 2 would include all layout for
> >>>
> >>> Title, navigation bar and sub navigation 2
> >>>
> >>> Or is there a way to nest them properly to have every
> >>> single layout only once?
> >>>
> >>> Norbert
> >>>
> >>>
> >>> _______________________________________________
> >>> SmallWiki, Magritte, Pier and Related Tools ...
> >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> >>
> >> --
> >> www.tudorgirba.com
> >>
> >> "What we can governs what we wish."
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
> 
> --
> www.tudorgirba.com
> 
> "Presenting is storytelling."
> 
> 
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

From norbert at hartl.name  Sat Feb 28 17:59:36 2009
From: norbert at hartl.name (Norbert Hartl)
Date: Sat, 28 Feb 2009 17:59:36 +0100
Subject: CSS namespaces
Message-ID: <1235840376.15861.7.camel@cineflux>

While testing how hard it will be to bring my site
into pier I discovered some css class clashes. For
people it is quite normal to assign classes like 
header, footer and the like.

In my opinion a cms like pier should try to step
out of the way of any usage conflict. Therefor I
would propose to namespace the css classes. A
pr_header, pr_footer will do I think.

Or do I missunderstand something completely? For me
it was not possible to reconstruct our layout without
haveing to remove all librares for the application. But 
then it is tedious to work with pier as the edit boxes
and stuff are too small.

What is the best approach to bring in the own developed
design and having pier still functioning?

thanks,

Norbert

From rdrvr.biz at gmail.com  Sat Feb 28 20:14:51 2009
From: rdrvr.biz at gmail.com (David Farber)
Date: Sat, 28 Feb 2009 12:14:51 -0700
Subject: CSS namespaces
In-Reply-To: <1235840376.15861.7.camel@cineflux>
References: <1235840376.15861.7.camel@cineflux>
Message-ID: 

I agree that it would be helpful if pier css were more constrained.   
For example, I wanted to apply my own css to a wiki-generated table.   
But doing so messed with all the tables that pier uses (like for edit  
forms).  I went ahead with my css ('cause it was end-user facing) but  
I'd rather that the css didn't clash.

David
----
1 Squeak/Seaside/Pier site deployed

On Feb 28, 2009, at 9:59 AM, Norbert Hartl wrote:

> While testing how hard it will be to bring my site
> into pier I discovered some css class clashes. For
> people it is quite normal to assign classes like
> header, footer and the like.
>
> In my opinion a cms like pier should try to step
> out of the way of any usage conflict. Therefor I
> would propose to namespace the css classes. A
> pr_header, pr_footer will do I think.
>
> Or do I missunderstand something completely? For me
> it was not possible to reconstruct our layout without
> haveing to remove all librares for the application. But
> then it is tedious to work with pier as the edit boxes
> and stuff are too small.
>
> What is the best approach to bring in the own developed
> design and having pier still functioning?
>
> thanks,
>
> Norbert
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

From girba at iam.unibe.ch  Sat Feb 28 20:25:35 2009
From: girba at iam.unibe.ch (Tudor Girba)
Date: Sat, 28 Feb 2009 20:25:35 +0100
Subject: CSS namespaces
In-Reply-To: <1235840376.15861.7.camel@cineflux>
References: <1235840376.15861.7.camel@cineflux>
Message-ID: 

Hi Norbert,

The default look and feel is based on the blueprint css framework.  
This is provided via the PRBlueprintLibrary library. This framework is  
a generic one and it mostly provides css classes for laying out the  
pages into columns. It also provides some default styles for basic  
html tags like textarea or input which is what gets eventually used  
for editing pier. See the project page for more details:
http://code.google.com/p/blueprintcss/

The CSS that is specific to the look and feel of the default webpage  
is available to you via the Edit Design command. This is where .footer  
and .header is defined. So, you have complete control over the look  
and feel without removing the libraries. The provided css features  
some commented to point out where the large parts out. So, all you  
have to replace the Pier css (or part of it) with your css in the  
provided area and to modify the template accordingly.

Is this helpful?

Cheers,
Doru

On 28 Feb 2009, at 17:59, Norbert Hartl wrote:

> While testing how hard it will be to bring my site
> into pier I discovered some css class clashes. For
> people it is quite normal to assign classes like
> header, footer and the like.
>
> In my opinion a cms like pier should try to step
> out of the way of any usage conflict. Therefor I
> would propose to namespace the css classes. A
> pr_header, pr_footer will do I think.
>
> Or do I missunderstand something completely? For me
> it was not possible to reconstruct our layout without
> haveing to remove all librares for the application. But
> then it is tedious to work with pier as the edit boxes
> and stuff are too small.
>
> What is the best approach to bring in the own developed
> design and having pier still functioning?
>
> thanks,
>
> Norbert
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

--
www.tudorgirba.com

"Being happy is a matter of choice."

From girba at iam.unibe.ch  Sat Feb 28 20:29:18 2009
From: girba at iam.unibe.ch (Tudor Girba)
Date: Sat, 28 Feb 2009 20:29:18 +0100
Subject: do you have a pier?
Message-ID: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch>

Hi,

We would like to fill the list of Pier installations from:
http://www.piercms.com/seaside/doc/examples

Thus, we kindly ask you to let us know if you have Pier installation  
somewhere publicly so that we can link to it.

Thanks,
Doru

--
www.tudorgirba.com

"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."

From ducasse at iam.unibe.ch  Sat Feb 28 22:41:27 2009
From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=)
Date: Sat, 28 Feb 2009 22:41:27 +0100
Subject: do you have a pier?
In-Reply-To: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch>
References: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch>
Message-ID: 

rmod.inria.lille.fr

Stef
On Feb 28, 2009, at 8:29 PM, Tudor Girba wrote:

> Hi,
>
> We would like to fill the list of Pier installations from:
> http://www.piercms.com/seaside/doc/examples
>
> Thus, we kindly ask you to let us know if you have Pier installation  
> somewhere publicly so that we can link to it.
>
> Thanks,
> Doru
>
> --
> www.tudorgirba.com
>
> "Problem solving should be concentrated on describing
> the problem in a way that is relevant for the solution."
>
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

From girba at iam.unibe.ch  Sat Feb 28 22:54:20 2009
From: girba at iam.unibe.ch (Tudor Girba)
Date: Sat, 28 Feb 2009 22:54:20 +0100
Subject: do you have a pier?
In-Reply-To: 
References: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch>

Message-ID: <8A74CABA-EB00-4D7A-BA23-8F73BF961394@iam.unibe.ch>

Hmm,

There seems to be an error when accessing it:
Serveur HTTP 1 (d0141-5)

Cheers,
Doru

On 28 Feb 2009, at 22:41, st?phane ducasse wrote:

> rmod.inria.lille.fr
>
> Stef
> On Feb 28, 2009, at 8:29 PM, Tudor Girba wrote:
>
>> Hi,
>>
>> We would like to fill the list of Pier installations from:
>> http://www.piercms.com/seaside/doc/examples
>>
>> Thus, we kindly ask you to let us know if you have Pier  
>> installation somewhere publicly so that we can link to it.
>>
>> Thanks,
>> Doru
>>
>> --
>> www.tudorgirba.com
>>
>> "Problem solving should be concentrated on describing
>> the problem in a way that is relevant for the solution."
>>
>>
>>
>>
>> _______________________________________________
>> 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

--
www.tudorgirba.com

"Value is always contextual."

From ducasse at iam.unibe.ch  Sat Feb 28 23:01:21 2009
From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=)
Date: Sat, 28 Feb 2009 23:01:21 +0100
Subject: do you have a pier?
In-Reply-To: 
References: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch>

Message-ID: <48F79D1A-4596-483E-9736-162DCC9B3F1B@iam.unibe.ch>

rmod.lille.inria.fr
On Feb 28, 2009, at 10:41 PM, st?phane ducasse wrote:

> rmod.inria.lille.fr

From girba at iam.unibe.ch  Sat Feb 28 23:09:02 2009
From: girba at iam.unibe.ch (Tudor Girba)
Date: Sat, 28 Feb 2009 23:09:02 +0100
Subject: do you have a pier?
In-Reply-To: <48F79D1A-4596-483E-9736-162DCC9B3F1B@iam.unibe.ch>
References: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch>

	<48F79D1A-4596-483E-9736-162DCC9B3F1B@iam.unibe.ch>
Message-ID: <7959E291-5F73-4F67-9D70-9E6F613D493D@iam.unibe.ch>

Better :).

Thanks, I added it to our list.

Cheers,
Doru

On 28 Feb 2009, at 23:01, st?phane ducasse wrote:

> rmod.lille.inria.fr
> On Feb 28, 2009, at 10:41 PM, st?phane ducasse wrote:
>
>> rmod.inria.lille.fr
>
>
>
> _______________________________________________
> SmallWiki, Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

--
www.tudorgirba.com

"Presenting is storytelling."