- Pharo-dev - lists.pharo.org

[Pharo-project] Small tool to edit bloc code

by Hilaire Fernandes

>From DrGeo I would like the user to edit Smalltalk code in the form of block of code. The user interface I need is maninly to let the user write and compile code. When compiled, DrGeo should get a notification to fetch the code for internal use. What is the best candidate to do that ? Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

Nov. 1, 2011

[Pharo-project] UbiquiTalk

by Chris Cunnington

Hi Sean, I've been looking at this post: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-td2400767.html and I see you have UbiquiTalk running on Squeak 4.1. I've got the shorter loading script here (from after you got update access to the rST and UbiquiTalk repos). You made a change ( UbiquiTalk-Platform.pharo ) to load into Pharo. What do I need to change in this to make it load in Squeak? Thanks, Chris Gofer new squeaksource: 'KomHttpServer'; package: 'DynamicBindings'; package: 'KomServices'; load. Gofer new squeaksource: 'rST'; package: 'rST'; load. Gofer new squeaksource: 'OSProcess'; package: 'OSProcess'; load. Gofer new squeaksource: 'UbiquiTalk'; package: 'UbiquiTalk-Platform.pharo'; package: 'UbiquiTalk-Utilities'; "depends on Platform" package: 'UbiquiTalk-Kernel'; "depends on Utilities" package: 'UbiquiTalk-Cache'; "depends on Kernel" package: 'UbiquiTalk-GUI'; "depends on Kernel" package: 'UbiquiTalk-Plugins'; "depends on Kernel" package: 'UbiquiTalk-PDA'; package: 'UbiquiTalk-Property Editors'; package: 'UbiquiTalk-Tests'; package: 'UTAllServices'; load.

Nov. 1, 2011

[Pharo-project] curl?

by Sebastian Sastre

hi guys, how can I use curl from the image? where is the code I should install? sebastian o/

Nov. 1, 2011

Re: [Pharo-project] Comment Syntax

by Eliot Miranda

On Mon, Oct 31, 2011 at 2:22 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > The problem is that both #/* and #/* are valid binary operators, so > they don't work well for comments. > > I don't really remember what I proposed a few years ago, although I > remember that exactly the same proposal was made. What would work is > to use something like "* and *" (or any other double thing that starts > with a double quote). Like this the comments could contain double > quotes. > Gilad Bracha chose (* & *) for Newspeak. These are not valid binary selectors and * can't follow ( in valid code. A good choice. > > As a short term solution you can also put your comments into single > quotes. Unused string literals are removed by the compiler. > > Lukas > > On 31 October 2011 22:00, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > Me too. > > > > Sean lukas proposed a syntax for that in the mailing-list a year ago. > > If you find it please resent it. > > > > Stef > > > > On Oct 31, 2011, at 9:12 PM, Sean P. DeNigris wrote: > > > >> Would it be difficult/valuable to create an alternate comment syntax? I > often > >> find myself wanting to comment a large block itself containing > comments. It > >> would be nice to have something like C++'s /* */. I feel like this may > have > >> been brought up before, but couldn't find it searching the lists. > >> > >> Sean > >> > >> -- > >> View this message in context: > http://forum.world.st/Comment-Syntax-tp3961451p3961451.html > >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >> > > > > > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > -- best, Eliot

Nov. 1, 2011

Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Ben Coman

Nov. 1, 2011

Re: [Pharo-project] Goods Test Runner Pharo 1.3 Issues

by Carlo

Hi On 01 Nov 2011, at 1:41 PM, mail list wrote: >>>> self deny: (set includes: 1@1). -->fails >>>> >>>> set = (2@2,1@1) >>>> so it seems to think that x and 1@1 are the same. Which to me seems correct but I may be misunderstanding the testcase. KKIdentitySet should not think x and 1@1 are the same as they are 2 different instances. I would think that the implementation of Set has changed (@see scanFor: method, specifically the SetElement wrapper around nil). My guess would be that Set storage has changed slightly. Maybe try changing KKIdentitySet to be: KKIdentitySet>>scanFor: anObject "Scan the key array for the first slot containing either a nil (indicating an empty slot) or an element that matches anObject. Answer the index of that slot or raise an error if no slot is found. This method will be overridden in various subclasses that have different interpretations for matching elements." | index start | index := start := anObject hash \\ array size + 1. [ | element | ((element := array at: index) == nil or: [ element enclosedSetElement == anObject ]) ifTrue: [ ^index ]. (index := index \\ array size + 1) = start ] whileFalse. self errorNoFreeSpace Cheers Carlo

Nov. 1, 2011

Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Ben Coman

StÃ©phane Ducasse wrote: > Hi guys > > we have a roadmap for Esteban and we would like to share it with you. We have extra items that we would like to see fixed and we are welcoming your > feedback/suggestions. Note this is typically the way we want to work with the consortium in the future: > Build an initial roadmap and refine it based on the input of the community. > > - A website for the consortium registration (esteban is expert on that). > - This is important for INRIA and for the visibility of the consortium. We should get new members :) > - Integration with SmalltalkHub > > - Working on fixing bugs! > - Debugger fixes > - Continuous bug fixing. > > - Improving release process: faster, more people involved, simpler. > - Working on metacello repositories for each distributions (everything is there but missing last bits) > - Metacello tools > - Automatic release validations > - Automatic validation of fixes > > Now the free items with probably igor involvement > - Multiwindowing support > - Fully working multithreaded FFI with ***Documentation*** > - Filesystem fix and integration > - Integration of OPAL > - RPackage integration > > Igor related > - Ephemerons > - Object format > - VM branding > - Use of new canvas > - Event cleaning > > So we are waiting for your suggestions. > > > Stef Just a very general view... that in paid positions, you don't always get to work on the sexy stuff. One of the downsides of open-source is the chance that developers might focus on the fun 80% of their ideas before moving on to the next-big-thing(c). It is easy to develop something to be used by oneself. It is much harder to develop something to be used by others - particularly in providing a sense of how to use the system by way of well documented examples. There is a lot of drudge work to make a system successful and stable. Knowing there is a paid position that might deal with part of that work definitely increases confidence in the system. One new idea. I really like the way Wordpress manages their thousands of Plugins with the "Compatability" sidebox where you choose a Wordpress version and a Plugin version and it indicates how compatible they are based on user votes. However rather than (or as well as) user voting I think that TestRunner results from applications could be used - and also presented in a tabulated form rather than just pull-down choices showing a single sample point. A continuous integration and testing system would take combinatorial approach to testing registered Metacello configurations - which might take a lot of processing power and leads to... A second idea for a distributed continuous integration test system. I would personally be happy to contribute cpu cycles to running a Pharo test system on top of a virtual machine, which from a central server obtains a random set of Metacello configurations to install, runs tests and reports results to the central server. Apart from gaining the processing power to possibly test all permutations of configurations, it also provides a way for new community members to feel like they are contributing, which preceeds them getting more involved. As an example in line with my first comment, perhaps the initial proof of concept would be done as a research project, and then the paid professional would polish off the stability and usability of it. cheers, Ben

Nov. 1, 2011

Re: [Pharo-project] Someone bought Smalltalk?

by Tudor Girba

Oh, my God! I will have to delete every piece of Smalltalk evidence! Ah, but I guess it will be a while until they get to Switzerland. I just hope they do not catch me in Argentina. Doru On 1 Nov 2011, at 11:12, Damien Cassou wrote: > I just received this email: > > > ---------- Forwarded message ---------- > > I heard some rumors about Smalltalk. Apparently, an american > enterprise bought Smalltalk and is trying to make money by sueing > users. Therefore, they changed the licence agreements (and maybe other > stuff). In my company we have a strict interdiction to use Smalltalk. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > -- www.tudorgirba.com "Some battles are better lost than fought."

Nov. 1, 2011

[Pharo-project] Custom-Global Exception handlers

by Guillermo Polito

Hi! Am I wrong If I say that there is no way to set a custom event handler per * application* in pharo? Let's say I want a different error handling approach for OmniBrowser, the TestRunner and Pharo in general. More over, there is no application idea (or I didn't find it). I think it is healthy to have such handlers to have a single point of error handling... Ideas? Guille

Nov. 1, 2011

Re: [Pharo-project] Comment Syntax

by Schwab,Wilhelm K

Actually, I think the second point is arguable, for reasons I gave and that you snipped. But they *would* indeed say "just delete it." ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Sean P. DeNigris [sean(a)clipperadams.com] Sent: Monday, October 31, 2011 8:57 PM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Comment Syntax Schwab,Wilhelm K wrote: > > ...It would be nice if it were portable to other Smalltalks, but it would > be useful. > ... > XP advocates would tell us that we don't need the code and to just delete > it. > The second point is valid, but only applies to a subset of comments. For example, in my case the thing that needs to be commented is Applescript code that provides context for the method. It is part of the documentation, and must contain double quotes to be valid Applescript. -- View this message in context: http://forum.world.st/Comment-Syntax-tp3961451p3962192.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 1, 2011