- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PetitParser in 3.0?

by Sean P. DeNigris

Stephan Eggermont wrote > And there is a image build at > https://ci.inria.fr/pharo-contribution/job/PetitParser/ Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems) ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Stephan Eggermont

On smalltalkhub, Moose/PetitParser And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/ Stephan

July 17, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Sean P. DeNigris

Martin McClure-2 wrote > Anyone using PetitParser in Pharo 3.0? Yes! 1. Open the Config Browser from the World menu 2. Right click in the list pane and switch to the ss3 meta repo 3. Load the PP config 4. ConfigurationOfPetitParser project stableVersion load: 'Core' HTH ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768405.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2014

Re: [Pharo-dev] SmalltalkHub and public write access

by Sean P. DeNigris

Nicolas Petton wrote > It should be working fine now. Thanks! That's important for contributions :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/SmalltalkHub-and-public-write-access-tp4768266p476840… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2014

Re: [Pharo-dev] Logic we will have to clean

by Sean P. DeNigris

Why? Looks perfectly understandable to me ;-P ----- Cheers, Sean -- View this message in context: http://forum.world.st/Logic-we-will-have-to-clean-tp4768190p4768403.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2014

PetitParser in 3.0?

by Martin McClure

Anyone using PetitParser in Pharo 3.0? What's the best repository to find PP for 3.0 in? Thanks, -Martin

July 17, 2014

Re: [Pharo-dev] [squeak-dev] Re: How to get started with Git and Pharo?

by Chris Muller

> > On Thu, Jun 26, 2014 at 3:16 PM, Dale Henrichs < > dale.henrichs(a)gemtalksystems.com> wrote: > >> My favorite feature by far is the ability to look at the git history of >> the methods themselves ... just the other day I had a bug that I was >> tracking down, and by looking at the git history I discovered that a >> critical change had been made to that method 1 year 12 days ago ... from >> that I was able to look at all of the changes to all of the packages that >> had been made in the same commit (the critical code had not only been moved >> to a different class but the critical method had been moved to a separate >> package ... and from that I was able to see that a bug had been introduced >> when not all of the critical method was moved ... bug fixed ... >> > > Chris Muller has recently done some superb work in Squeak with his Magma > database that provides exactly this within the existing Monticello > framework. In current Squeak 4.5 images if you add the repository > Hey, glad it could be useful! Just for clarity, one thing MC doesn't do is track single commits that include changes across multiple packages. In Dale's story, the "critical code had not only been moved to a different class but the critical method had been moved to a separate package" -- MC doesn't have anything to track "multipackage commits"; (I don't think it needs it, even though it proved useful in Dale's example, because when we have a set of packages we care to work together, MC can instantiate a MCConfiguration to define it). The reason you were able to see the history of WeakRegistry today even though it had been moved from Collections to System is that the MCDefinitions instances are indexed simply by their #description, which is package agnostic. It didn't care that it moved packages. > MCHttpRepository > location: 'http://box4.squeak.org:8888/trunk' > user: 'squeak' > password: 'squeak' > > to the Monticello Browser and then add it to the packages one is > interested in (a script to add it to all is trivial), then a "Browse mc > history" menu item becomes available on the class and method lists in the > browser and voila, one can browse the entire class and/or method history. > > This feature has been missing for a long time. I really needed it this > morning and wasn't quite aware that it was available already. I expect > this will become a standard feature of new Squeak releases. The server can > easily be duplicated on one's own machine for working detached from the > internet (e.g. via http://localhost:8888/mchistory) and updates itself at > regular intervals. > It was released with Squeak 4.5. The box4 server supporting it has been running for 7-8 months. > Besides method versions, you can look at the git history for a class, >> package or metacello project .... these are thing that would take a bit of >> work to accomplish using just Monticello ... and if you were to attempt to >> do it, the simplest thing to do would be to copy all of the packages into a >> git repository and just use git:) Frank Shearar wrote some code that did >> something along these lines a couple of years ago ... >> > > But the work's mostly been done. Chris's work provides class & method. > Package history is there already, with "search history" providing free > text search through a specific package's history, and Chris will be > providing keyword search across all packages soon. > TMK, Pharo did not adopt the MCRepository changes we did, so there would be issues in Pharo. The box4 tool is intended only as a tool to help Monticello users.. Every kind of MC backend will have its own pluses and minuses, it's an area worth exploring in multiple directions..

July 17, 2014

Re: [Pharo-dev] [ANN] Ephestos - Using and Coding Blender from inside Pharo

by kilon alios

Does it work with Pharo ? I downloaded the documentation and is really well written. But I have no clue how to test with Pharo. Communication of languages and apps through sockets is nothing original or rare. I was actually considering expanding Atlas to not only talk to python but also talk to Pharo as well. My goal is to make pharo take advantage of multi core cpus. Each new instance of Pharo takes on core because this is how OS works with processes and Atlas could act as a net of communication between different instances of Pharo. Possible its an idea I wont work on but its something I consider in the back of my head. But if its easy enough I may do it. On Thu, Jul 17, 2014 at 9:06 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > The goal of Atlas, is to create a two way communication socket >> bridge between cpython (most popular python implementation) and >> pharo. Very similar to Ephestos but you will no longer need Blender. >> That means that pharo coders will be able to use python libraries >> from inside pharo and even mix python with pharo code. So you could >> make part of your application in python and part in pharo and still >> function as a single application. >> >> >> I am interested in Atlas. Do you have a link? >> >> > This has been done some three years ago for OpenQwak :-) > > http://squeakingalong.wordpress.com/2011/05/04/ > openqwaq-python-integration/ > > Best, Jan > > > >

July 17, 2014

Re: [Pharo-dev] [ANN] Ephestos - Using and Coding Blender from inside Pharo

by kilon alios

I do have some great news I solved the problem with blender operators that means I now have full access to the whole API of blender. Everything in Blender API is basically operators and properties.There are still limitations to be solved of course. First that I will tackle is how to communicate data from Blender back to Pharo. Also I have added example code for people to look at. Just pull from my repo here http://www.smalltalkhub.com/#!/~kilon/Ephestos/ Ephestos is not something I am making for others to use, its primarily for my needs. Because I am very interested in interacting and integrating other Blender addons in my workflow I want to keep the Pharo API as close to BPY as possible. This will make it easy for me to port BPY code to pharo and talk to existing Blender addons. Blender addons are extremely important they implement tons of new functionality for Blender. A cube is not a separate object in BPY , a cube is basically a mesh object. So BPYMesh would make more sense. But in BPY its really a BPYObject. Additional I can be lazy and avoid documenting stuff since translating python calls to pharo is dead easy. Python has a very simple syntax, not as simple as Pharo but quite close. So its easy to go to Blender wiki BPY API and find all the information you want instead of me going through the pain of rewriting this huge documentation. There are also a lot of tutorials about making blender addons with python online, there is no way I can compete with that . So in the end if you really want to take advantage of Blender learning python and the blender api is mandatory. Pretty much every major 3d app uses Python and Python is a very popular language so there is nothing to lose by learning it. I would not put too much faith to me mapping alone the huge BPY API, the operators alone are 1500 or so I have been told, properties must be at least double that amount. Translating all that to Pharo objects is just an insane amount of work unless I find a cleaver way around it with some pharo parsing but still too much work for little gain. But I will map some basic stuff to decrease the need of writing python code. About Atlas here is the repo that I am going to post the code https://github.com/kilon/pyAtlas For now I work on Ephestos and when I am happy with the progress I made with it I will port it to Atlas and make an announcement here. Its basically the same code minus the Blender stuff. PS: It may also make some of you happy that I plan to expand Ephestos to include besides BPY also BGE. BGE stand for Blender Game Engine , its a game engine offered by Blender that excels at any kind of interacting graphics, that means that you will have access to a very powerful game engine and a general engine for 3d interactive applications. BGE is a lower priority , but it should be easy to implement once the big limitations of Ephestos have been solved. More info about BGE can be found here http://wiki.blender.org/index.php/Doc:2.6/Manual you can find finished games made with BGE here http://blenderartists.org/forum/forumdisplay.php?39-Finished-Games A very good example is this http://deadcyborg.com/ On Thu, Jul 17, 2014 at 8:31 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > > 2014-07-16 12:31 GMT-03:00 kilon alios <kilon.alios(a)gmail.com>: > > yes the one I am considering as strong candidate is >> >> (BPYObjects at: 'Cube' ) location : #( 0 0 0 ) >> >> > Why not BPYCube? > > > >> I would try to simplify bpy ( Blender Python API) and make it a lot more >> pharo friendly. >> >> However plain python string will be kept as well, so you can copy paste >> existing python code. >> >> One thing to note here is that Blender python addons are a huge deal. >> Python addons are actually full blown python apps. Blender python is >> basically a regular cpython 3 which is by far the most popular python >> implementation , meaning not only that you can use blender api object but >> any python library you can find. As a pharo developer you also can tap into >> this power via Ephestos. >> >> something that I forgot to mention in the video, in the github repo there >> is a rawcode.py. This is a strip down version of the Blender code that will >> separate to its own project that I am naming "Atlas". >> >> The goal of Atlas, is to create a two way communication socket bridge >> between cpython (most popular python implementation) and pharo. Very >> similar to Ephestos but you will no longer need Blender. That means that >> pharo coders will be able to use python libraries from inside pharo and >> even mix python with pharo code. So you could make part of your application >> in python and part in pharo and still function as a single application. >> >> > I am interested in Atlas. Do you have a link? > > > >> If I find the time I would like to expand Atlas to other languages too, >> so that pharo can take advantage of any library written in any language >> without the trouble of FFIs. But most likely I will stick to python and let >> others do the work. >> >> But even with just python as you imagine python is extremely popular and >> quite friendly with the pharo way of thinking. Meaning that in python its >> all about live objects too. Pharo will be able to tap into thousands of >> powerful python libraries. ï»¿ >> >> I reserve some doubts to the amount of problems I will have to face to >> accomplish this and I am no way claiming it wont be a long process but so >> far through these very first steps the idea seems to go well in practice. >> >> >> On Wed, Jul 16, 2014 at 5:55 PM, Damien Cassou <damien.cassou(a)gmail.com> >> wrote: >> >>> On Tue, Jul 15, 2014 at 11:09 PM, kilon alios <kilon.alios(a)gmail.com> >>> wrote: >>> > >>> > The goal is to expose Blender coders to the power of Pharo and Pharo >>> to the >>> > power of Blender. As you can imagine the potential is huge but I >>> rather talk >>> > what Ephestos can do already. >>> >>> That's great kilon! I can't wait to see how far you could go with >>> that. I hope you plan to use Pharo syntax instead of plain string for >>> the messages. A message like this: >>> >>> "bpy.data.objects["Cube"].location = (0.0, 0.0, 0.0)" >>> >>> could be written like that: >>> >>> (EphestosMessage bpy data objects: 'Cube') location: (EphestosLocation >>> x: 0 y: 0 z: 0) >>> >>> or something similar >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." >>> Winston Churchill >>> >>> >> >

July 17, 2014

Fun With Pharo on ci

by Stephan Eggermont

Thanks to some help by Damien, we now have FunWithPharo on ci. It generates the whole book and separate chapters. Stephan

July 17, 2014