- Pharo-dev - lists.pharo.org

Re: [Pharo-project] FFI examples?

by StÃ©phane Ducasse

> StÃ©phane Ducasse wrote: >> >> Does anybody with experience have a bit of time to get some text for the >> website >> > > You read my mind... stop that! In another life we did telepathy magicianwith alex and it was fun > > I've been working on this for a few days. I almost have a summary for > more-knowledgeable folks to critique. excellent I'm eager to read that. > > Sean > -- > View this message in context: http://forum.world.st/FFI-examples-tp2219674p2219873.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 17, 2010

Re: [Pharo-project] FFI examples?

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > > Does anybody with experience have a bit of time to get some text for the > website > You read my mind... stop that! I've been working on this for a few days. I almost have a summary for more-knowledgeable folks to critique. Sean -- View this message in context: http://forum.world.st/FFI-examples-tp2219674p2219873.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 17, 2010

Re: [Pharo-project] TextEditor and NewTextMorph merges and fixes

by Fernando olivero

De nada ! Actually i just published another version of the CodeMorph. I found no need for subclassing CodeMorph, since the accepting behavior is on the announcements now, having specific ClassDescriptionMorph and MethodMorph wouldn't be beneficial. Also removed the dependency with the Shout ( and the styler). Name: Morphic-FernandoOlivero.589 Rethought the CodeMorph class hierarchy, removed the subclasses and added CodeMorph class methods for creating "MethodMorph" and "ClassDefinitionMorph" Fernando On May 17, 2010, at 3:35 PM, StÃ©phane Ducasse wrote: > Tx!!!! > Gaucho man > > On May 17, 2010, at 3:32 PM, Fernando olivero wrote: > >> Issue: 2375 >> >> Name: System-Text-FernandoOlivero.8 >> Author: FernandoOlivero >> Time: 17 May 2010, 3:22:14 pm >> >> >> >> ###################################### >> Issue: -- >> >> Name: Morphic-FernandoOlivero.588 >> Author: FernandoOlivero >> Time: 17 May 2010, 1:42:04 pm >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 17, 2010

Re: [Pharo-project] Decoupling Shout and Styler

by Lukas Renggli

Yes, that makes sende. Another possibility would be to use the RB or PetitParser (this is what I do in Helvetia) parser instead. Lukas On Monday, May 17, 2010, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > can be a good idea. > > Stef > > On May 17, 2010, at 5:21 PM, Fernando olivero wrote: > >> I would like to decouple the Styler Object ( For example SHTextStyler) from the Shout packages. >> >> Since Shout purpose it to add: Â 'Syntax Highlighting that updates after each key stroke so that the highlighting remains correct during the editing of a method'. >> >> I think it would be beneficial to Â style any piece of text, independently from the editing of a method. >> >> For example, when working on the NewTextMorph Â i do not need any functionality of the TextMorphForShout or TextMorphForShoutEditor classes, but only the Styler related classes. And in its current state, these two are coupled in the same package. >> >> I propose Shout could be spitted into 2 packages, that better reflect the classes intentions. >> >> 1. Code Styler: which would include Shout-Parsing, and Shout-Styling. >> >> 2. TextMorphShout: Shout-TextSupport, Shout-Windows. >> >> What do you think? >> >> Fernando >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

May 17, 2010

Re: [Pharo-project] FFI examples?

by Igor Stasenko

On 17 May 2010 18:35, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Jake > > can you check in the archive of this list because there were a lot of mail on this topic. > We should consolidate that into a couple of page and documentation > Does anybody with experience have a bit of time to get some text for the website > Stef > I cannot help, because a Jake's question is too generic. I have no idea what kind of explanations he may require. Is FFI-Examples not enough to grasp the idea? Because for me, its so naturally trivial, that i can't understand what kind of help is needed there. > > On May 17, 2010, at 3:53 PM, Jake Bartlett wrote: > >> I'm trying to use SVMLight (http://svmlight.joachims.org/) from Pharo. Â SVMLight has some *.h files I need to load and some *.so libraries. Â I need to be able to call functions from them and manage the results. Â How do I create a FFI in Pharo? >> >> [jake] >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

May 17, 2010

Re: [Pharo-project] Decoupling Shout and Styler

by StÃ©phane Ducasse

can be a good idea. Stef On May 17, 2010, at 5:21 PM, Fernando olivero wrote: > I would like to decouple the Styler Object ( For example SHTextStyler) from the Shout packages. > > Since Shout purpose it to add: 'Syntax Highlighting that updates after each key stroke so that the highlighting remains correct during the editing of a method'. > > I think it would be beneficial to style any piece of text, independently from the editing of a method. > > For example, when working on the NewTextMorph i do not need any functionality of the TextMorphForShout or TextMorphForShoutEditor classes, but only the Styler related classes. And in its current state, these two are coupled in the same package. > > I propose Shout could be spitted into 2 packages, that better reflect the classes intentions. > > 1. Code Styler: which would include Shout-Parsing, and Shout-Styling. > > 2. TextMorphShout: Shout-TextSupport, Shout-Windows. > > What do you think? > > Fernando > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 17, 2010

Re: [Pharo-project] Community Supported Packages

by StÃ©phane Ducasse

I like the friendly tone of this email. Stef On May 17, 2010, at 4:45 PM, Torsten Bergmann wrote: > Hi Chris, > >> I don't know if you watched all that carefully, but in the last 48 hours >> we've made our decision >> You seem to think we're having a discussion about it. > > That's what I would call a very quick decision after the proposal > from Saturday leaving out people who didnt follow over the weekend. > But since the people who showed up agreed with Andreas > I'm fine with the decision. > > However using Monticello in one or the other way will have an > impact on future development and how people can contribute. > >> I think at bottom you are more of a Pharo guy. > > Yes, maybe I'm biased since I now usually use Pharo images since > they satisfy more needs I personally know from other Smalltalk and > non-Smalltalk environments. > > On the other side I'm with Squeak from the beginning, still contribute > and try to keep up compatibility for packages as much as possible. > There are many things that make up Squeak different and unique. > > I've contributed code, fixes, packages, discussions, installer code, > help system to both: Squeak and Pharo and still try to keep them > as compatible as possible. > > So what did you do to prevent reinventing the wheel within > the broader community? > >> Added to which, you say that Pharo has packages to manage? > > Yes, look at ConfigurationOfPharo and you will find the packages > forming the Pharo release from a pharo core. Also look at > squeaksource/MetacelloRepository - for other configurations > (sadly only a few of them work for Squeak yet) > > You seem to think that Pharo is solely there to satisfy Seaside > users which is a very naive view. > >> I repeat, you are one step behind the times, Torsten > > Looks like I'm old and behind the times since I was not able to > read and respond over the weekend B) > >> We have chosen. Colin has just created the first test case. > > Which will make my "Squeak/Pharo dissociative identity disorder" > a little bit harder since I have another difference. > Nonetheless I continue with both even when I'm still behind the times ;) > > Bye > T. > > > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 17, 2010

Re: [Pharo-project] [Vm-dev] CMake for Windows?

by Mariano Martinez Peck

On Sun, May 16, 2010 at 11:15 PM, Geoffroy Couprie <geo.couprie(a)gmail.com>wrote: > > Hello, > > Here is the latest set of files for CMake: > http://eleves.ec-lille.fr/~couprieg/divers/changes-16-05-10.tar.gz<http://eleves.ec-lille.fr/%7Ecouprieg/divers/changes-16-05-10.tar.gz> > (you have to remove platforms/win32/vm/config.h to make it build) > > I tried to remove the dependency on the Squeak-win2-tools package. The > Direct3D code still uses a lot of DirectX 7 structures, and the recent > MinGW toolchain provides DirectX 8, so the B3DAccelerator plugin > doesn't build right now. If it's ok, I'll send other patches to make > it work with the new version. Otherwise, it's possible to modify > config.cmake for B3DAccelerator to use DirectX 7. > > Could these patches be included now? The Unix VM builds without any > problem, so it can become the main way to build it (just replace > platforms/unix/cmake/configure by platforms/cmake/configure in the > tutorials). There may still be some problems with the Windows build, > but I'll send more patches once these are pushed in the svn :) > > Hi Geoffroy. This is cool work. I cannot help you in the details of how to commit that in SVN as I have no idea. Listen to David. Now...I have a couple of ideas: 1) regardless that, it would be really really cool if you can document all this in the pharo collaborative book. As you can see there is already a chapter for VM http://book.pharo-project.org/book/Virtual-Machine/ and the windows part is empty: http://book.pharo-project.org/book/Virtual-Machine/Building/BuildVMOnWindow… So...we can write the two possibilities to compile in Windows: the standard one and this new one using CMake. You can start writing the one of CMake :) If you want, please just let us know and we create a user for you. 2) In addition, I think it would be a good idea to have a Git for scripts for the VM. If Squeak VM developers like them, they can also include it in the svn. Laurent Laffont already has a git repository with scripts like easy_squeakvm or something like that. So, you may want to commit your code there too. 3) What about integrating like easy_squeakvm with this ? or do a easy_squeakvm version of CMake for winwows ? I would love to do for example: ./easy_squeakvm.sh --os=Windows or ./easy_squeakvm.sh --os=Unix 4) Would be really great to have a Screencast about how to compile windows with CMake :) Cheers and continue pushing. Mariano > Best regards, > > Geoffroy >

May 17, 2010

Re: [Pharo-project] FFI examples?

by StÃ©phane Ducasse

Jake can you check in the archive of this list because there were a lot of mail on this topic. We should consolidate that into a couple of page and documentation Does anybody with experience have a bit of time to get some text for the website Stef On May 17, 2010, at 3:53 PM, Jake Bartlett wrote: > I'm trying to use SVMLight (http://svmlight.joachims.org/) from Pharo. SVMLight has some *.h files I need to load and some *.so libraries. I need to be able to call functions from them and manage the results. How do I create a FFI in Pharo? > > [jake] > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 17, 2010

[Pharo-project] Decoupling Shout and Styler

by Fernando olivero

I would like to decouple the Styler Object ( For example SHTextStyler) from the Shout packages. Since Shout purpose it to add: 'Syntax Highlighting that updates after each key stroke so that the highlighting remains correct during the editing of a method'. I think it would be beneficial to style any piece of text, independently from the editing of a method. For example, when working on the NewTextMorph i do not need any functionality of the TextMorphForShout or TextMorphForShoutEditor classes, but only the Styler related classes. And in its current state, these two are coupled in the same package. I propose Shout could be spitted into 2 packages, that better reflect the classes intentions. 1. Code Styler: which would include Shout-Parsing, and Shout-Styling. 2. TextMorphShout: Shout-TextSupport, Shout-Windows. What do you think? Fernando

May 17, 2010