- Pharo-dev - lists.pharo.org

Fwd: [Pharo-project] Re: Building VM Freetype
by StÃ©phane Ducasse Sept. 13, 2008

Sept. 13, 2008

Begin forwarded message: > From: John M McIntosh <johnmci(a)smalltalkconsulting.com> > Date: September 13, 2008 11:28:56 AM CEDT > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Cc: Igor Stasenko <siguctua(a)gmail.com>, Michael Rueger <michael(a)impara.de > > > Subject: Re: [Pharo-project] Re: Building VM Freetype > Reply-To: johnmci(a)smalltalkconsulting.com > > Ok, first we statically loaded any *.dll into the freetype plugin > because we found earlier versions of os-x didn't have > the required version of freetype needed to support what we were > doing, also it was a complete mess on the linux side > with regard to what you would find there if you dynamically loaded > the plugin. > > the freetype plugin source code I have was loaded from http://source.impara.de/freetype > > I see the FT2Constants seems to be shared between the freetype base > package and the plugin package, so it appears you > need to load the base in order for the plugin to load. I'm not sure > anyone noticed this since you need to load the base in order > to test the plugin in any case. > > > On Sep 13, 2008, at 8:59 AM, StÃ©phane Ducasse wrote: > >> >> >> Begin forwarded message: >> >>> From: "Igor Stasenko" <siguctua(a)gmail.com> >>> Date: September 13, 2008 8:24:36 AM CEDT >>> To: "An open mailing list to discuss any topics related to an open- >>> source Smalltalk" <pharo-project(a)lists.gforge.inria.fr> >>> Subject: Re: [Pharo-project] Re: Building VM Freetype >>> Reply-To: An open mailing list to discuss any topics related to an >>> open-source Smalltalk <pharo-project(a)lists.gforge.inria.fr> >>> >>> 2008/9/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> I hope other will answer but I thought that we could have a pluggin >>>> and bundle in the deployed packages. >>>> The idea for pharo is to have a similar setup than seaside a one >>>> click app >>>> so the >>>> vm and its plugin would be there (but may be the plugin should >>>> not be in the >>>> image). >>> >>> Plugin is built-in in the VM. But freetype library is coming as >>> separate dynamic library. >>> Is this ok? >>> >>> There can be another option, but it would require to change the >>> plugin >>> code - to not link VM with import lib, but to load freetype.dll on >>> demand. The plugin can simply check if this .dll available and start >>> using it, or if not - fail to initialize, telling the system that >>> plugin functionality is not available. >>> >>>> >>>> Mike or john? On sophie how did you manage that the freetype >>>> bundle could >>>> not be present? >>>> >>> >>> Actually, to build a plugin, you need just headers + freetype.def >>> file >>> which then can be used to >>> create the imports library from it. >>> Building a freetype.dll can be completely separate process. >>> >>> I can remove dependency from freetype.lib, and leave only a >>> freetype.def and create import lib by own, when making VM. >>> But this is not safe, because now you must guarantee that you using >>> correct .dll. (well, you need to guarantee it in either case). >>> >>>> If I remember correctly some people on squeak have been >>>> recompiling it for >>>> 64 bits >>>> >>>>> I done with it. >>>>> The resulting VM will not start without freetype.dll. >>>>> Should i link it statically? But then you should hone their >>>>> license >>>>> stuff... >>>>> >>>>> Also, building freetype on windoze impossible using gnutools which >>>>> used for building VM. >>>>> It's make simply can't understand some things, which i assume >>>>> appear >>>>> in later make versions. >>>>> So, i building freetype using my msys/mingw environment, and then >>>>> simply producing >>>>> - freetype.lib (imports library) >>>>> - freetype.dll >>>>> >>>>> or maybe, i wrong, maybe it can be built using gnutools, but this >>>>> would require too much voodoo dancing. >>>>> it would be cool to make it cleanly build w/o manual work, but >>>>> i'm not >>>>> high expert in makefiles black voodoo. >>>>> >>>>> Okay, who wants the VM? And where i can put the stuff + >>>>> instructions + >>>>> blablabla? >>>> >>>> You can use the code google page for that. >>>> >>>> Stef >>>>> >>>>> >>>>> 2008/9/12 Igor Stasenko <siguctua(a)gmail.com>: >>>>>> >>>>>> 2008/9/12 Igor Stasenko <siguctua(a)gmail.com>: >>>>>>> >>>>>>> As always, things not working out of the box. >>>>>>> >>>>>>> - VM builds from unzipped VM sources OK >>>>>>> - but for building with VMMaker generated sources, had to fix >>>>>>> 'gnuify' >>>>>>> file to make a clean build >>>>>>> >>>>>>> i dreaming to build vm straight from squeak, without horrid >>>>>>> makefiles. >>>>>>> I heard that Keith did a 'Bob' tool which can be used as a >>>>>>> kind of >>>>>>> make utility. >>>>>>> But i think, to fully replace makefiles, it needs an >>>>>>> OSProcessPlugin >>>>>>> to be able to interact with OS/shell. >>>>>>> >>>>>> >>>>>> Next step, tried to load freetype plugin.... >>>>>> http://source.impara.de/freetype/Freetype-Plugin-JMM.53.mcz >>>>>> http://source.impara.de/freetype/Freetype-Plugin-tween.51.mcz >>>>>> >>>>>> and guess what? YES! It can't be loaded! :) >>>>>> >>>>>> MC complains about following: >>>>>> >>>>>> This package depends on the following classes: >>>>>> FT2Constants >>>>>> >>>>>> The FT2Constants is the pool dictionary used by plugin. But not >>>>>> defined within package. >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Igor Stasenko AKA sig. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko AKA sig. >>>>> <fonts.jpg>_______________________________________________ >>>>> 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. >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > >

1 0

[Pharo-project] About fixes for noury and other
by StÃ©phane Ducasse Sept. 12, 2008

Sept. 12, 2008

Hi noury I started to harvest your fixes and I learned something :) when most of your fixes are about extending or changing a package just publish a new version of that package. This way I can use the merge tool and be much more efficient, do not create a specific package with specific class extension for it else I have to modify everything by hand. Stef

2 5

[Pharo-project] Using the new compiler...
by Alexandre Bergel Sept. 12, 2008

Sept. 12, 2008

Dear List, I am now using the new compiler. I found few bugs. Should I post these bugs in the pharo google website ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 12

[Pharo-project] Discussion summary and milestones
by StÃ©phane Ducasse Sept. 12, 2008

Sept. 12, 2008

Hi all we got an extremely positive ESUG. Thanks all of you for your great software: Thanks Gary it was great to see you. Now I would like to summarize some of the discussions we got. For milestone1 ----------------- - we will integrate the Polymorph package of gary. This means we may try to remove some old morphic and integrate really gary's work. Now this task could be continued further in milestone 2. - gary could you send around (not only to adrian) the etoy removal so that we do it? - Marcus plans to integrate the stack interpreter made by eliot so that we will get fullclosures. - We will integrate the freetype plugging (we will need some VM guys probably). - We want to have a one click image! - internally we will work on a core and set of package but publicly we would like to avoid to have a distribution that is not tested/used. For the dev image we would like to only have a set of selected packages, so the idea is that damien will collect the key package that would go in the dev version. (which may be the one click image). We really want to have package without overrides. - We would like to push the idea of a package manifesto. For milestone 2 ------------------- - GTK binding - the newcompiler will replace the old one - marcus is really interested in COG and helping there. I will try to help and learn from mathieu. - popUp plague -> notification mechanism (check the OBNotification hierarchy). We need to push infrastructural work so that everything benefit of it. There are certainly point I forgot to mention but the future is full of new perspectives. Stef

11 20

[Pharo-project] InstallerTest
by Alexandre Bergel Sept. 12, 2008

Sept. 12, 2008

Hi Keith, None of the test in InstallerTest pass. The class ClassClonerTestResource is missing. Any idea how to fix this? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

[Pharo-project] Coding session now...
by Alexandre Bergel Sept. 12, 2008

Sept. 12, 2008

Dear List, Marcus, Stef and I are now doing a Pharo coding. - Stef is cleaning the list of issues in on the pharo website - I am working on making the test server. I am currently deprecating tests that popup windows Feel free to join Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] Hello everyone!
by Igor Stasenko Sept. 12, 2008

Sept. 12, 2008

I just subscribed and want to say hello to this list. :) At ESUG we discussed with Stephane and Markus some things in Squeak (and consequently in Pharo), which really need an overlook and better implementation. Stephane asked me, to think about overlooking Processes and concurrency in its current state. First, i must say that it is very fragile part of system because most things written w/o concurrency in mind. Last year i seen many issues related to concurrency: Semaphore , Delay, Process, Scheduler. Some of them resolved, some of them resolved in an ugly and hackish way - mostly as workarounds of lacking critical VM primitives which should guarantee atomicity for different purposes, and some of them is not resolved at all. Some things, which i noted and which i like/not like, can be found in squeak-dev list. But i will repeat them here, in single place: - Process should assume that it is running in ideal environment (e.g. in parallel to another processes w/o any preemption). Every bit of code, which requires synchronization should be based/take into account this assumption. a process should have three discrete states: - suspended - when initially created. - running - when you invoke resume. - terminated - when process no longer running and can't be resumed. It is wrong to consider a process which waiting on semaphore signal as suspended process. (see http://bugs.squeak.org/view.php?id=6822) Process which waits on semaphore is actually performing an action, while , by definition, a suspended process can't perform any action. Concerning process termination, it is also a can of worms to deal with: - process termination means stop doing anything in requested process, but this going into conflict with exception handling mechanism. The conflict comes from two things like #ensure: and #ifCurtailed: . Such mechanisms used to ensure that some code will have chance to run under any circumstances, regardless of the state of computation. It is interesting, where such code should run? In a process which initiated a terminate request, or in process which needs to be terminated by request. Most valid, of course - to run them in a terminating process. The problem, however, how to achieve that. Someone suggested to throw an exception, like ProcessTerminateException to indicate that the given process is going to be terminated. Such thing is also going into conflict with different points of view: a Process termination is usual functionality, provided for use, so why it should be considered as exceptional? Maybe, to solve the conflicts, and avoid using exceptions in an arguable way, it would be better to add support of process termination notification. So, each time process is going to terminate, it can notify all interesting parties of such event. Then, instead of using #ensure: to free critical system resources, one could use notification. As you can see, there is more questions than answers :) -- Best regards, Igor Stasenko AKA sig.

5 22

[Pharo-project] FileMan
by Alexandre Bergel Sept. 12, 2008

Sept. 12, 2008

Dear List, On SqueakMap there is a package called FileMan. Here is an example: Squeak's file libraries (Directory, DirectoryEntry, FileStream, etc.) are sometimes very confusing to use. FileMan provides a simple, refactored interfaces for manipulating files and directories by wrapping those classes. "Before" subDir := FileDirectory default directoryNamed: 'subDir'. subDir assureExistence. [str := subDir newFileNamed: 'file1'. str nextPutAll: 'Hello!'] ensure: [str close]. "After installation of FileMan" './subDir' asDirectoryEntry at: 'file2' put: 'Hello!' Maybe it worth having a look at it? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 3

[Pharo-project] How to submit changes when SqueakSource is down ?
by Noury Bouraqadi Sept. 11, 2008

Sept. 11, 2008

Hi, SqueakSource is down again :-( Attached a monticello package with a serie of bugfixes and enhancements tested on pharo-dev of sept: *Bug Fixes -Transcript printing and self evaluating -Smalltalk printing and self evaluating -Instance Variable should never start by a capital *Enhancemnts -Monticello Package renaming -Prefix replacement for classes in a Monticello package Regards, Noury ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------

5 8

[Pharo-project] InterfaceDiscoverer
by Alexandre Bergel Sept. 11, 2008

Sept. 11, 2008

Dear List, I built a small extension to OB that display dependencies between class categories. Just load InterfaceDiscoverer from squeaksource, and click on a class category in an OB browser. Shall I add this package to the ScriptLoader>>loadOB? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 11