Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?

basilmir

Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?

Ex1:

html scriptaculous sortable onUpdate: (html scriptaculous... etc).

html jQuery new sortable onStop: (html jQuery... etc).

Ex2:

html scriptaculous effect id: helpId; toggleAppear. 
 (html jQuery id: helpId) slideToggle: 1 seconds.

The way jQuery and Scriptaculous were integrated 'seems' similar. Can anyone explain what design change took place between the two and it's effect on syntax?

PS. Especially in the last example.


Reply | Threaded
Open this post in threaded view
|

Re: Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?

philippeback


Le 31 janv. 2015 22:37, "Mircea S." <[hidden email]> a écrit :
>
>
> Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?
>
> Ex1:
>
> html scriptaculous sortable onUpdate: (html scriptaculous... etc).
>
> html jQuery new sortable onStop: (html jQuery... etc).
>
> Ex2:
>
> html scriptaculous effect id: helpId; toggleAppear. 
>
>  (html jQuery id: helpId) slideToggle: 1 seconds.
>
> The way jQuery and Scriptaculous were integrated 'seems' similar. Can anyone explain what design change took place between the two and it's effect on syntax?
>
> PS. Especially in the last example.

Mostly because that is how jQuery works.

This is mapping the jQuery API.

A good trick is to halt around those calls and inspect what the expression between parentheses gives.

This helped me tremendously in understanding how jQuery worked with Seaside. Docs are quite shallow in that area but the system works very well.

Check the tests and JQWidgetbox for a ton of samples.

HTH
Phil

>
>

Reply | Threaded
Open this post in threaded view
|

Re: Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?

basilmir
Are there any Guides of any kind?

The seaside book seems to have some jQuery parts but they are sketchy and commenting is disabled so I can't correct them. 



Pe 1 feb. 2015, la 00:10, "[hidden email]" <[hidden email]> a scris:


Le 31 janv. 2015 22:37, "Mircea S." <[hidden email]> a écrit :
>
>
> Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?
>
> Ex1:
>
> html scriptaculous sortable onUpdate: (html scriptaculous... etc).
>
> html jQuery new sortable onStop: (html jQuery... etc).
>
> Ex2:
>
> html scriptaculous effect id: helpId; toggleAppear. 
>
>  (html jQuery id: helpId) slideToggle: 1 seconds.
>
> The way jQuery and Scriptaculous were integrated 'seems' similar. Can anyone explain what design change took place between the two and it's effect on syntax?
>
> PS. Especially in the last example.

Mostly because that is how jQuery works.

This is mapping the jQuery API.

A good trick is to halt around those calls and inspect what the expression between parentheses gives.

This helped me tremendously in understanding how jQuery worked with Seaside. Docs are quite shallow in that area but the system works very well.

Check the tests and JQWidgetbox for a ton of samples.

HTH
Phil

>
>

Reply | Threaded
Open this post in threaded view
|

Re: Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?

jtuchel
As Phil stated already, there is not much documentation on Seaside/JQuery. There are a few slide decks by Lukas, Johan and Adrian that you can find on slideshare, but you are pretty much on your own to find our about it. Sad but true.


Am 01.02.15 um 00:09 schrieb Mircea S.:
Are there any Guides of any kind?

The seaside book seems to have some jQuery parts but they are sketchy and commenting is disabled so I can't correct them. 



Pe 1 feb. 2015, la 00:10, "[hidden email]" <[hidden email]> a scris:


Le 31 janv. 2015 22:37, "Mircea S." <[hidden email]> a écrit :
>
>
> Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?
>
> Ex1:
>
> html scriptaculous sortable onUpdate: (html scriptaculous... etc).
>
> html jQuery new sortable onStop: (html jQuery... etc).
>
> Ex2:
>
> html scriptaculous effect id: helpId; toggleAppear. 
>
>  (html jQuery id: helpId) slideToggle: 1 seconds.
>
> The way jQuery and Scriptaculous were integrated 'seems' similar. Can anyone explain what design change took place between the two and it's effect on syntax?
>
> PS. Especially in the last example.

Mostly because that is how jQuery works.

This is mapping the jQuery API.

A good trick is to halt around those calls and inspect what the expression between parentheses gives.

This helped me tremendously in understanding how jQuery worked with Seaside. Docs are quite shallow in that area but the system works very well.

Check the tests and JQWidgetbox for a ton of samples.

HTH
Phil

>
>



-- 
-----------------------------------------------------------------------
Objektfabrik Joachim Tuchel          [hidden email]
Fliederweg 1                         http://www.objektfabrik.de
D-71640 Ludwigsburg                  http://joachimtuchel.wordpress.com
Telefon: +49 7141 56 10 86 0         Fax: +49 7141 56 10 86 1

Reply | Threaded
Open this post in threaded view
|

Re: Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?

Sven Van Caekenberghe-2
http://esug.org/data/ESUG2014/4%20thursday/1400-1530%20Seaside/

> On 01 Feb 2015, at 05:57, [hidden email] wrote:
>
> As Phil stated already, there is not much documentation on Seaside/JQuery. There are a few slide decks by Lukas, Johan and Adrian that you can find on slideshare, but you are pretty much on your own to find our about it. Sad but true.
>
>
> Am 01.02.15 um 00:09 schrieb Mircea S.:
>> Are there any Guides of any kind?
>>
>> The seaside book seems to have some jQuery parts but they are sketchy and commenting is disabled so I can't correct them.
>>
>>
>>
>> Pe 1 feb. 2015, la 00:10, "[hidden email]" <[hidden email]> a scris:
>>
>>>
>>> Le 31 janv. 2015 22:37, "Mircea S." <[hidden email]> a écrit :
>>> >
>>> >
>>> > Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?
>>> >
>>> > Ex1:
>>> >
>>> > html scriptaculous sortable onUpdate: (html scriptaculous... etc).
>>> >
>>> > html jQuery new sortable onStop: (html jQuery... etc).
>>> >
>>> > Ex2:
>>> >
>>> > html scriptaculous effect id: helpId; toggleAppear.
>>> >
>>> >  (html jQuery id: helpId) slideToggle: 1 seconds.
>>> >
>>> > The way jQuery and Scriptaculous were integrated 'seems' similar. Can anyone explain what design change took place between the two and it's effect on syntax?
>>> >
>>> > PS. Especially in the last example.
>>>
>>> Mostly because that is how jQuery works.
>>>
>>> This is mapping the jQuery API.
>>>
>>> A good trick is to halt around those calls and inspect what the expression between parentheses gives.
>>>
>>> This helped me tremendously in understanding how jQuery worked with Seaside. Docs are quite shallow in that area but the system works very well.
>>>
>>> Check the tests and JQWidgetbox for a ton of samples.
>>>
>>> HTH
>>> Phil
>>>
>>> >
>>> >
>
>
> --
> -----------------------------------------------------------------------
> Objektfabrik Joachim Tuchel          
> mailto:[hidden email]
>
> Fliederweg 1                        
> http://www.objektfabrik.de
>
> D-71640 Ludwigsburg                  
> http://joachimtuchel.wordpress.com
>
> Telefon: +49 7141 56 10 86 0         Fax: +49 7141 56 10 86 1
>
>


Reply | Threaded
Open this post in threaded view
|

Re: Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?

NorbertHartl
This thread should be moved to the seaside list.

[hidden email]

There you might get more answers.

Norbert



> Am 01.02.2015 um 10:06 schrieb Sven Van Caekenberghe <[hidden email]>:
>
> http://esug.org/data/ESUG2014/4%20thursday/1400-1530%20Seaside/
>
>> On 01 Feb 2015, at 05:57, [hidden email] wrote:
>>
>> As Phil stated already, there is not much documentation on Seaside/JQuery. There are a few slide decks by Lukas, Johan and Adrian that you can find on slideshare, but you are pretty much on your own to find our about it. Sad but true.
>>
>>
>>> Am 01.02.15 um 00:09 schrieb Mircea S.:
>>> Are there any Guides of any kind?
>>>
>>> The seaside book seems to have some jQuery parts but they are sketchy and commenting is disabled so I can't correct them.
>>>
>>>
>>>
>>> Pe 1 feb. 2015, la 00:10, "[hidden email]" <[hidden email]> a scris:
>>>
>>>>
>>>> Le 31 janv. 2015 22:37, "Mircea S." <[hidden email]> a écrit :
>>>>>
>>>>>
>>>>> Seaside on Pharo - Why the weird jQuery integration syntax compared to Scriptaculous?
>>>>>
>>>>> Ex1:
>>>>>
>>>>> html scriptaculous sortable onUpdate: (html scriptaculous... etc).
>>>>>
>>>>> html jQuery new sortable onStop: (html jQuery... etc).
>>>>>
>>>>> Ex2:
>>>>>
>>>>> html scriptaculous effect id: helpId; toggleAppear.
>>>>>
>>>>> (html jQuery id: helpId) slideToggle: 1 seconds.
>>>>>
>>>>> The way jQuery and Scriptaculous were integrated 'seems' similar. Can anyone explain what design change took place between the two and it's effect on syntax?
>>>>>
>>>>> PS. Especially in the last example.
>>>>
>>>> Mostly because that is how jQuery works.
>>>>
>>>> This is mapping the jQuery API.
>>>>
>>>> A good trick is to halt around those calls and inspect what the expression between parentheses gives.
>>>>
>>>> This helped me tremendously in understanding how jQuery worked with Seaside. Docs are quite shallow in that area but the system works very well.
>>>>
>>>> Check the tests and JQWidgetbox for a ton of samples.
>>>>
>>>> HTH
>>>> Phil
>>>>
>>
>>
>> --
>> -----------------------------------------------------------------------
>> Objektfabrik Joachim Tuchel          
>> mailto:[hidden email]
>>
>> Fliederweg 1                        
>> http://www.objektfabrik.de
>>
>> D-71640 Ludwigsburg                  
>> http://joachimtuchel.wordpress.com
>>
>> Telefon: +49 7141 56 10 86 0         Fax: +49 7141 56 10 86 1
>
>