headers
Offray Vladimir Luna Cárdenas | 10 Feb 12:19

Enabling Dynatree on Pier/Seaside

Hi all,

Hi. I'm trying to load a dynatree support[0][1] in Seaside following the 
instructions at [2]. It says that I need to load the last version of 
ConfigurationOfJQueryWidgetBox and then  JQWidgetBox-Dynatree-Dev-tbn.3 
JQWidgetBox-Dynatree-Core-tbn.3, but it doesn't say how, so following 
the instructions at [3] I thought that:

  ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) loadLatestVersion) load:
    	#('JQWidgetBox-Dynatree-Core-tbn.4'
	   'JQWidgetBox-Dynatree-Dev-tbn.4').

would do the trick, but the first object doesn't understand the "load:" 
message. So there is something I'm not understanding properly. Any help 
would be appreciated.

Cheers,

Offray

[0] http://wwwendt.de/tech/dynatree/
[1] http://wwwendt.de/tech/dynatree/doc/samples.html
[2] 
http://forum.world.st/ANN-Dynatree-as-part-of-jquery-widget-box-td3748281.html
[3] http://forum.world.st/ANN-JQueryWidgetbox-and-Metacello-td1013881.html
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
(Continue reading)

Permalink | Reply | 8 comments |
headers
sergio_101 | 8 Feb 01:27

value:children+ -> rendering relative to containing component

hi all..

say i have a component.. call "stories"

this has many children:

"story 1"
"story 2"
"story 3"

so, all i want to do is list all the stories in the component..

so, stories would have:

+value:children+

everything works just fine..

so.. now, i'd like to embed this component in another page..

i end up with a page with this:

some text.. blah blah .. here is my list of stories:
+stories+

the problem is, it wants to rembed value:children with respect to the
current structure (which, according to the docs, is what it should
do)..

but i would rather have the the children render relative to the
(Continue reading)

Permalink | Reply | 1 comment |
headers
sergio_101 | 7 Feb 03:53

new pier site launched

okay, fellas..

i volunteered to help my sister in law out.. she is totally
technically non savvy.. but she did write a novel. which is more than
i could ever do..

so i helped her out by putting her site together..

keep in mind.. i am the crappiest designer ever.. but i do love me some pier..

as this project moves forward, we'll get a real designer on deck..

but it was pretty cool for us to be able to put this together quickly
with such a great product (pier)..

thanks, all..

oh! the url is:

http://www.toaplacebehindthesun.com/

--

-- 
----
peace,
sergio
photographer, journalist, visionary

http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
(Continue reading)

Permalink | Reply | 0 comments |
headers
sergio_101 | 7 Feb 03:40

value:structure|level - what does it mean?

ran across these on the blog title page

<h1 class="heading">}}}*>value:structure|level=2*{{{</h1>
<h1>}}}*>value:structure|level=0|lower=3*{{{</h1>

can someone explain what level and lower are?

thanks!

--

-- 
----
peace,
sergio
photographer, journalist, visionary

http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Permalink | Reply | 1 comment |
headers
sergio_101 | 6 Feb 07:16

component - display most recent blog post

on the front page of my pier site, i would like to automatically
display an abbreviated (say, 1000 characters) of the latest blog
story..

anyone have any idea on how i would do this? say, grab the newest
child of the blog component..

thanks!

--

-- 
----
peace,
sergio
photographer, journalist, visionary

http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Permalink | Reply | 3 comments |
headers
sergio_101 | 5 Feb 23:13

what to do when you break your site..

here's one i could never figure out how to do..

okay..

so, if you edit a component.. say, header.. and you accidentally put
in some broken html.. say, you forget to close out a tag..

when you do this, the whole site is rendered incorrectly..

this then means that the whole site is breaks, and you can't edit it,
or go back to a different revision...

how would you go back and fix this?

thanks!

--

-- 
----
peace,
sergio
photographer, journalist, visionary

http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
(Continue reading)

Permalink | Reply | 4 comments |
headers
sergio_101 | 5 Feb 07:49

inserting a single line break..

how would l go about making some text render like so:

this is a few lines
that i want to have break
in specified places rather
than have a space between
them

to insert a line break, i have to add two.. and i end up with this..

this is a few lines

that i want to have break

in specified places rather

than have a space between

them

any ideas?

thanks!

--

-- 
----
peace,
sergio
photographer, journalist, visionary
(Continue reading)

Permalink | Reply | 4 comments |
headers
sergio_101 | 4 Feb 21:50

Pier-Seaside-NickAger.526 - new error report

i have updated to Pier-Seaside-NickAger.526, and when i go to
/system/components/contents/, i can't save.. i get the following
error..

Seaside Walkback

MessageNotUnderstood: PRViewCommand>>fields
Debug Proceed

Possible Causes
you sent a message this type of object doesn't understand
Stack Trace
thisContext
PRViewCommand(Object)>>doesNotUnderstand: #fields
self
a PRViewCommand[246939648]
thisContext
PRDocumentWidget>>text:
self
a PRDocumentWidget
thisContext
[:value | self text: value] in PRDocumentWidget>>renderEditOn:
self
a PRDocumentWidget
thisContext
BlockClosure>>valueWithPossibleArguments:
self
[:value | self text: value]
thisContext
WAValueCallback>>evaluateWithArgument:
(Continue reading)

Permalink | Reply | 2 comments |
headers
sergio_101 | 4 Feb 14:29

Pier-Seaside-NickAger.526 fixes cookie issue

not sure if i commented on this yet, but this indeed fixes the issue
that i had with chrome and cookies..

thanks, nick!

--

-- 
----
peace,
sergio
photographer, journalist, visionary

http://www.CodingForHire.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Permalink | Reply | 4 comments |
headers
Nick Ager | 3 Feb 15:14
Picon
Gravatar

MAComponent>>#magritteDescription and Object>>#magritteDescription

Hi,


When I translated #description to #magritteDescription I noticed that both MAComponent and Object implement #description and now in Magritte 3 both implement #magritteDescription.

It seems that MAComponent>>#description/#magritteDescription is a redundant redefinition of Object>>#description/#magritteDescription. Any reason for it's existence? 

Nick










_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Permalink | Reply | 3 comments |
headers
Nick Ager | 3 Feb 13:20
Picon
Gravatar

loading refactoring support legacy (deprecated) code

Hi,


I forgot to mention in my previous mail how to load refactoring support (currently refactoring tool support doesn't load by default):

Gofer it
  squeaksource: 'MetacelloRepository';
  package: 'ConfigurationOfMagritte3';
  load.

ConfigurationOfMagritte3 project stableVersion load: 'Magritte-Pharo-Tools'

This will load refactoring support to move Magritte 1 or 2 described objects to instance-side pragma descriptions.
It also loads deprecated code such as #description with redirects to #magritteDescription with a deprecation warning.


-----

So that everything is the same place here are the porting guidelines I posted previously:

1) search for all senders and implementors of #description in your code, if they are magritte descriptions rename the selector from #description to #magritteDescription 
2) remove #magritteDynamic and remove the block around the method.
3) Use the refactoring support to move class-side descriptions to instance side descriptions with pragmas - making sure that any accessors to class side methods are either prefixed with ‘class’ or moved to the instance side. If you move description help methods to instance side be careful if they contain: 'context := PRCurrentContext value' as context will shadow an instance variable of the same name so either replace context with 'self context' and remove 'context := PRCurrentContext value' or rename context say theContext and replace 'context := PRCurrentContext value' with 'theContext := self context'.
4) Remove any empty categories on the class side.
5) PRWidget derived classes should either by modified to be derived from PRWidgetPropertyBase or keep derived from PRWidget but modify the accessors to store state in instance variable rather than the property dictionary in PRWidgetPropertyBase. See PRViewsWidget and PRSearchWidget for examples of both types of port.
6) Modify structure initialisation with PRComponent to use prototype instance rather than classes. So

       (PRComponent named: 'contents')
componentClass: PRContentsWidget;
write: '%c' using: PRContentsWidget descriptionHeading;
yourself

becomes:

       (PRComponent named: 'contents')
prototypeInstance: (PRContentsWidget new
heading: '%c';
yourself);
yourself

 add setters to allow initial settings to be set on the prototype instances again see  PRViewsWidget and PRSearchWidget for examples.
7) Put a break point in Object>>description and Object class>>description to trap any cases you’ve missed (the break-point should not be hit) and check the add-on. Note Object>>#description and Object class>>#description are only present if you load 'Magritte-Deprecated'
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Permalink | Reply | 0 comments |

Gmane