- Pharo-users - lists.pharo.org

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

by Mircea S.

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.

Jan. 31, 2015

Standalone GUI

by falzonidavide＠libero.it

Hi guys, How can I make a standalone pharo installation that starts on a GUI? About the gui: my first idea was to use Morphic, but then user has access to all the source code, am I right? Thanks Francis

Jan. 31, 2015

Pharo Shop

by Torsten Bergmann

What happened to the Pharo shop ... http://old.pharo-project.org/community/shop it's online but seems not be linked from the new webpage.

Jan. 31, 2015

Re: [Pharo-users] Rule engine

by stepharo

> I would be curious to hear more about the various projects mentioned in this > thread. SOUL was a prolog with an extra term that unified method AST. Check Roel Wuyts, Andy Kellens, Johan Brichau At the VUB in the Soft (prog lab) previously the group was doing logic meta programming. Kris Gybels from the same group was working on Rete or may be this is Koen deRover. NeoPus was (not working anymore) a rule-based system that could use object for fact and change. I have the doc around if you want. Herve Verjus http://smalltalkhub.com/#!/~HerveVerjus/SmallAI is a little project to support backward and forward chainer. > I am working on a constraint logic system that has been used as a > backend for a variety of inference systems in other languages. Can you explain a bit more? > > > Thanks, > Evan > > > > -- > View this message in context: http://forum.world.st/Rule-engine-tp4801671p4802961.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Jan. 31, 2015

Re: [Pharo-users] Seaside - How do I install Scriptaculous on a clean Seaside install (via Configuration Browser) on Pharo?

by Mircea S.

For those looking to install jQuery into Seaside can use these: Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/Seaside31/main'; package: 'Javascript-Core'; load. Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/Seaside31/main'; package: 'JQuery-Core'; load. Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/Seaside31/main'; package: 'JQuery-UI'; load. "notice that there is no -Core on this last one, I don't know why" Pe 31 ian. 2015, la 16:23, Johan Brichau <johan(a)inceptive.be> a scris: > Hi Mircea, > > Pharoâs Configuration browser loads the default group of the Metacello configuration, which unfortunately was set to âCoreâ for Seaside 3.1. > So, you will need to load additional groups programmatically: > > (ConfigurationOfSeaside3 project version: #stable) load: #(âScriptaculousâ âJSONâ) > > If you want to get the list of possible groups to load, inspect: > > (ConfigurationOfSeaside3 project version: #stable) groups > > This is something we fixed for Seaside 3.2, where the default will load everything to help newcomers. > We prefer not to change the existing 3.1 configuration versions to not break existing uses, but itâs fixed in the upcoming version. > > Btw, Scriptaculous is really outdated. You will prefer to use jQuery and jQuery-UI (or any other JS frameworkâ¦) > > cheers > Johan > >> On 31 Jan 2015, at 15:01, Mircea S. <mircea(a)unom.ro> wrote: >> >> I used the method described here to install Seaside3 on Pharo. All is well, but Scriptaculous doesn't come preinstalled. How do I get it? >> >> Seaside3 : >> >> 1: Go to the configuration manager >> >> 2: Select the Seaside 3 configuration. Click on Install. >> >> 3: Wait while it loads. Takes a couple of minutes on an i7 and a decent network link. >> >> 4: Open a Workspace and start a ZincServerAdaptor on the port you like (here 8080): ZnZincServerAdaptor startOn: 8080. (then CMD+d for Do It) >> >> 7: Access Seaside from your browser. >> >> 8: Install Scriptaculous, but how? > >

Jan. 31, 2015

Re: [Pharo-users] Rule engine

by Evan Donahue

I would be curious to hear more about the various projects mentioned in this thread. I am working on a constraint logic system that has been used as a backend for a variety of inference systems in other languages. Thanks, Evan -- View this message in context: http://forum.world.st/Rule-engine-tp4801671p4802961.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 31, 2015

Re: [Pharo-users] Seaside - How do I install Scriptaculous on a clean Seaside install (via Configuration Browser) on Pharo?

by Mircea S.

Well, I undertook a hands-on approach and finally figured it out. Mainly because I was following the Seaside book and the chapter on Scriptaculous. The packages needed for Scriptaculous to work are listed in the book here: http://book.seaside.st/book/web-20/scriptaculous/frameworks/installation Then you need to find a repository to get them from, after a little poking around here: http://www.smalltalkhub.com/mc/Seaside/ I chose the Seaside31 repository, which is what I apparently managed to install a few hours ago. http://www.smalltalkhub.com/mc/Seaside/Seaside31/main Then I had to Do-It a couple of times on (maybe there is a faster way to do this): Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/Seaside31/main'; package: 'Javascript-Core'; load. Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/Seaside31/main'; package: 'Prototype-Core'; load. Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/Seaside31/main'; package: 'Scriptaculous-Core'; load. Gofer new url:'http://www.smalltalkhub.com/mc/Seaside/Seaside31/main'; package: 'Scriptaculous-Components'; load. Pe 31 ian. 2015, la 16:23, Johan Brichau <johan(a)inceptive.be> a scris: > Hi Mircea, > > Pharoâs Configuration browser loads the default group of the Metacello configuration, which unfortunately was set to âCoreâ for Seaside 3.1. > So, you will need to load additional groups programmatically: > > (ConfigurationOfSeaside3 project version: #stable) load: #(âScriptaculousâ âJSONâ) > > If you want to get the list of possible groups to load, inspect: > > (ConfigurationOfSeaside3 project version: #stable) groups > > This is something we fixed for Seaside 3.2, where the default will load everything to help newcomers. > We prefer not to change the existing 3.1 configuration versions to not break existing uses, but itâs fixed in the upcoming version. > > Btw, Scriptaculous is really outdated. You will prefer to use jQuery and jQuery-UI (or any other JS frameworkâ¦) > > cheers > Johan > >> On 31 Jan 2015, at 15:01, Mircea S. <mircea(a)unom.ro> wrote: >> >> I used the method described here to install Seaside3 on Pharo. All is well, but Scriptaculous doesn't come preinstalled. How do I get it? >> >> Seaside3 : >> >> 1: Go to the configuration manager >> >> 2: Select the Seaside 3 configuration. Click on Install. >> >> 3: Wait while it loads. Takes a couple of minutes on an i7 and a decent network link. >> >> 4: Open a Workspace and start a ZincServerAdaptor on the port you like (here 8080): ZnZincServerAdaptor startOn: 8080. (then CMD+d for Do It) >> >> 7: Access Seaside from your browser. >> >> 8: Install Scriptaculous, but how? > >

Jan. 31, 2015

Re: [Pharo-users] NumericalMethods and SciSmalltalk

by stepharo

Le 27/1/15 00:29, Werner Kassens a Ã©crit : > let me rephrase it <g> just that there are no misunderstandings, > NumericalMethods is independent of SciSmalltalk and does work in Pharo4 By SciTalk will include its own copy of NumericalMethods. Stef > werner > > > On 01/26/2015 10:22 PM, Ignacio Sniechowski wrote: >> That was my question. If in Pharo 4 the NumericalMethods package will be >> deprecated and instead SciSmalltalk will be de defacto package for >> stats. > >

Jan. 31, 2015

Re: [Pharo-users] Updated Pharo Days Schedule

by Ben Coman

Le 27/1/15 23:18, Ben Coman a Ã©crit : On Wed, Jan 28, 2015 at 2:09 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Ben, > > I totally understand your question, but I known from experience that > things are always very hectic and connecting with off-site people is > usually quite hard. > cool. just giving it a bump ;). > > The main thing around your Delay work is to find someone knowledgeable > enough ;-) Or someone who wants to be knowledgable :). On Sat, Jan 31, 2015 at 5:30 PM, stepharo <stepharo(a)free.fr> wrote: > I will read it. > I have to fix one chapter of updated pharo > finish the mustache chapter and I will take time to at least have a > look precisely > > I appreciate that Stef. I know you have a heavy load. Actually (and I should have been more explicit) I was thinking this Delay stuff might be interesting knowledge to any robotics guys that might one day want to do soft-realtime control with Pharo (nudge-nudge). cheers -ben

Jan. 31, 2015

Re: [Pharo-users] how to debug zinc server errors from tests

by Ben Coman

On Sat, Jan 31, 2015 at 4:48 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 30 Jan 2015, at 12:18, Ben Coman <btc(a)openInWorld.com> wrote: > > > > If there is a particular test you want to run outside of the test > framework, essentially you reproduce TestCase>>runCase in the Workspace. > > For example... > > MyClassTest new setUp testMyTest > > Actually the proper usage is > > MyTestCase run: #testSelector > > or > > MyTestCase debug: #testSelector > > Ahhh... Usually I do this when a test fails intermittently such that clicking on TestRunner's list of failed tests doesn't bring up a debugger. So my hack was to avoid the "on: self class failure , self class skip, self class warning, self class error do: [ ... ]" exception handling in #runCase:. #debug: is much better than my hack - thanks. cheers -ben

Jan. 31, 2015