- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Athens Font Rendering Bug

by J.F. Rick

Thanks. It is working nicely. On Wed, Jul 20, 2016 at 3:32 PM Nicolai Hess <nicolaihess(a)gmail.com> wrote: > 2016-07-20 20:46 GMT+02:00 J.F. Rick <self(a)je77.com>: > >> Cool. What should I use? Is this useful: >> http://www.tudorgirba.com/blog/free-font-collection-for-pharo >> > > Any FreeType font, the builtin (Source Sans Pro/ Source Code Pro) or a > font from your system (after loading all available fonts). > > | font boldFont italicFont | > font := LogicalFont familyName: 'Source Sans Pro' pointSize: 18. > boldFont := (LogicalFont familyName: 'Arial' pointSize: 18) emphasized: > TextEmphasis bold emphasisCode. > italicFont := (LogicalFont familyName: 'Times New Roman' pointSize: 18) > emphasized: TextEmphasis italic emphasisCode. > TextMorph new > contents: (Text initialFont: font stringOrText: 'normal'), (Text > initialFont: boldFont stringOrText: 'bold'), (Text initialFont: italicFont > stringOrText: 'italic'); > openInSceneView > > >> >> On Wed, Jul 20, 2016 at 2:16 PM Nicolai Hess <nicolaihess(a)gmail.com> >> wrote: >> >>> Do not use StrikeFont with athens >>> >>> Am 20.07.2016 7:49 nachm. schrieb "J.F. Rick" <self(a)je77.com>: >>> >>>> It seems that emphasis is also not respected in Athens. If I try the >>>> following, it works in BitBlt, but both are rendered as plain inside Athens. >>>> >>>> | font boldFont | >>>> font := StrikeFont familyName: 'Arial' pointSize: 18. >>>> boldFont := StrikeFont familyName: 'Arial' pointSize: 18 emphasized: >>>> TextEmphasis bold emphasisCode. >>>> TextMorph new >>>> contents: (Text initialFont: font stringOrText: 'test'), (Text >>>> initialFont: boldFont stringOrText: 'this'); >>>> openInHand >>>> >>>>>

July 20, 2016

Re: [Pharo-dev] Athens Font Rendering Bug

by Nicolai Hess

2016-07-20 20:46 GMT+02:00 J.F. Rick <self(a)je77.com>: > Cool. What should I use? Is this useful: > http://www.tudorgirba.com/blog/free-font-collection-for-pharo > Any FreeType font, the builtin (Source Sans Pro/ Source Code Pro) or a font from your system (after loading all available fonts). | font boldFont italicFont | font := LogicalFont familyName: 'Source Sans Pro' pointSize: 18. boldFont := (LogicalFont familyName: 'Arial' pointSize: 18) emphasized: TextEmphasis bold emphasisCode. italicFont := (LogicalFont familyName: 'Times New Roman' pointSize: 18) emphasized: TextEmphasis italic emphasisCode. TextMorph new contents: (Text initialFont: font stringOrText: 'normal'), (Text initialFont: boldFont stringOrText: 'bold'), (Text initialFont: italicFont stringOrText: 'italic'); openInSceneView > > On Wed, Jul 20, 2016 at 2:16 PM Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > >> Do not use StrikeFont with athens >> >> Am 20.07.2016 7:49 nachm. schrieb "J.F. Rick" <self(a)je77.com>: >> >>> It seems that emphasis is also not respected in Athens. If I try the >>> following, it works in BitBlt, but both are rendered as plain inside Athens. >>> >>> | font boldFont | >>> font := StrikeFont familyName: 'Arial' pointSize: 18. >>> boldFont := StrikeFont familyName: 'Arial' pointSize: 18 emphasized: >>> TextEmphasis bold emphasisCode. >>> TextMorph new >>> contents: (Text initialFont: font stringOrText: 'test'), (Text >>> initialFont: boldFont stringOrText: 'this'); >>> openInHand >>> >>>>

July 20, 2016

Re: [Pharo-dev] Athens Font Rendering Bug

by J.F. Rick

Cool. What should I use? Is this useful: http://www.tudorgirba.com/blog/free-font-collection-for-pharo On Wed, Jul 20, 2016 at 2:16 PM Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Do not use StrikeFont with athens > > Am 20.07.2016 7:49 nachm. schrieb "J.F. Rick" <self(a)je77.com>: > >> It seems that emphasis is also not respected in Athens. If I try the >> following, it works in BitBlt, but both are rendered as plain inside Athens. >> >> | font boldFont | >> font := StrikeFont familyName: 'Arial' pointSize: 18. >> boldFont := StrikeFont familyName: 'Arial' pointSize: 18 emphasized: >> TextEmphasis bold emphasisCode. >> TextMorph new >> contents: (Text initialFont: font stringOrText: 'test'), (Text >> initialFont: boldFont stringOrText: 'this'); >> openInHand >> >>>

July 20, 2016

Re: [Pharo-dev] Athens Font Rendering Bug

by Nicolai Hess

Do not use StrikeFont with athens Am 20.07.2016 7:49 nachm. schrieb "J.F. Rick" <self(a)je77.com>: > It seems that emphasis is also not respected in Athens. If I try the > following, it works in BitBlt, but both are rendered as plain inside Athens. > > | font boldFont | > font := StrikeFont familyName: 'Arial' pointSize: 18. > boldFont := StrikeFont familyName: 'Arial' pointSize: 18 emphasized: > TextEmphasis bold emphasisCode. > TextMorph new > contents: (Text initialFont: font stringOrText: 'test'), (Text > initialFont: boldFont stringOrText: 'this'); > openInHand > >>

July 20, 2016

Re: [Pharo-dev] Athens Font Rendering Bug

by J.F. Rick

It seems that emphasis is also not respected in Athens. If I try the following, it works in BitBlt, but both are rendered as plain inside Athens. | font boldFont | font := StrikeFont familyName: 'Arial' pointSize: 18. boldFont := StrikeFont familyName: 'Arial' pointSize: 18 emphasized: TextEmphasis bold emphasisCode. TextMorph new contents: (Text initialFont: font stringOrText: 'test'), (Text initialFont: boldFont stringOrText: 'this'); openInHand >

July 20, 2016

Re: [Pharo-dev] State of Pharo in comparison with the "Pharo vision" document

by Julien Delplanque

Thanks for all your answer I will use the hints you gave me and eventually come back to you if I need more information. :-) Regards, Julien On 20/07/16 01:44, Ben Coman wrote: > On Wed, Jul 20, 2016 at 5:59 AM, Julien Delplanque <julien(a)tamere.eu> wrote: >> Hello everyone, >> >> For a university project I need to write a little about Pharo. >> I found the "Pharo vision" document [1] and I am curious about >> the actual state of Pharo in comparison with it. >> >> I have seen some things on the mailing list but I would like some >> help to gather the state of each goal described in "Pharo vision" >> version 1.0. >> >> I made a list with the goals and wrote some of the (little) knowledge I >> have about some elements (I also joined it to this mail in case it is not >> readable): >> >> Goals -> State >> ------------------- >> 1. Creation of the Pharo Consortium -> Created >> 2. Small kernel & validated packages -> ? >> 3. A Robust and Extensible System Events -> ? >> 4. Rewrite of Filesystem/Streams -> ?/XStream? >> 5. Announcements and Ephemerons -> ? >> 6. UI Canvas for Zoomable Interfaces -> Bloc? >> 7. Bootstrap of the Core -> ? >> 8. Fully parametrized compiler tool chain -> ? >> 9. Packages as real objects -> ? >> 10. Package Meta-Data -> PackageManifest? >> 11. Less Model Clutter and Duplication -> ? >> 12. Building and Reusing UI Logic -> Spec? >> 13. New Network Layer -> ? >> 14. Serializers -> Fuel >> 15. SystemChangeNotifier replacement -> ? >> 16. Cleaning Morphic -> Still valid? (asking because of Bloc existance) >> 17. Everybody should be able to compile VMs -> ? >> 18. VMs identification and regression testing -> ? >> 19. One Unified FFI framework -> Created and still being enhanced >> 20. 64 Bits -> I saw the screenshot on Twitter but what is the state now? >> 21. New Object Formats -> ? >> >> If some of you know the state of one or many of these project and have the >> time to give me some information about it/them, I would be really grateful. >> >> Thanks in advance, >> >> Julien >> >> Links: >> [1]: https://gforge.inria.fr/frs/download.php/30434/PharoVision.pdf > You should be able to get some answers from... > https://github.com/pharo-project/pharo-changelogs > Can you fill in yourself what answers you can extract from that - for > checking, and letting people focus on where there remain gaps in your > questions. > > cheers -ben >

July 20, 2016

Pharo 6 image lockup at startup

by Thierry Goubier

Hi guys, It seems there is a strange interaction between the deprecation rewriter and image startup. If you load a package that has deprecated calls (command line loading: without GUI), then save the image, the image will appear locked on the next interactive start (black background on Linux). Loading the package by hand in an interactive image and saving a new version with the deprecation rewritten solves the problem. Thierry

July 20, 2016

Support for more arrays

by Thibault Raffaillac

Hi, Here is a quick draft for more array sizes as discussed last week. http://smalltalkhub.com/#!/~ThibaultRaffaillac/Collections-Arrays It yields (* => new): SByteArray* and ByteArray ShortArray* and UShortArray* IntegerArray and UIntegerArray* LongArray* and ULongArray* SWordArray* and WordArray FloatArray and DoubleArray* I don't know if this is the right way to make a package (also considering the obvious name), anyway here are the unresolved issues: _ ByteArray and WordArray are unsigned, IntegerArray is signed! The package does not rename any though, I go for conservative :p _ Do we have primitives for 8/16/32/64 sreads/ureads/writes? Doing sign extension by hand is painful. _ Same for 32/64 bit IEEE float reads/writes? Current code implicitly transfers float values through integer registers which is SLOW (worse on ARM). _ A big part of the system is hardcoded with assumption (isBytes or isWords), therefore the inspector does not seem to display values&metadata properly. We should probably fix all occurrences of isBytes. Is there a bug filed already? Cheers, Thibault

July 20, 2016

Re: [Pharo-dev] State of Pharo in comparison with the "Pharo vision" document

by Ben Coman

On Wed, Jul 20, 2016 at 4:59 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > 21. New Object Formats > > In progress > This is Spur? cheers -ben

July 20, 2016

Re: [Pharo-dev] State of Pharo in comparison with the "Pharo vision" document

by Esteban Lorenzano

Hi, this is my following of vision document: > 1. Creation of the Pharo Consortium -> Created DONE > 2. Small kernel & validated packages -> >>In progress (Bootstrap + Cargo) In progress > 3. A Robust and Extensible System Events -> ? DONE. Announcements (but now we have âannouncements plagueâ so we need to iterate/clean a bit here) > 4. Rewrite of Filesystem/Streams -> ?/XStream? -> >>In progress, there was the introduction of File IIRC FileSystem DONE Streams NOT DONE > 5. Announcements and Ephemerons -> >> Will be in Pharo 6 DONE (in Pharo 6) > 6. UI Canvas for Zoomable Interfaces -> Bloc? >>I think yes In progress: Will be Block, yes > 7. Bootstrap of the Core -> >>Should be for Pharo 6. The Bootstrap build pass on Jenkins but still need some love from Christophe, Guillermo and Pavel In progress. > 8. Fully parametrized compiler tool chain -> >>I think I heard that a lot of progress have been made in this area but I don't have any detail and I am not sure. DONE (OpalCompiler, etc.) > 9. Packages as real objects -> >>In progress. now package are objects but there will be improvements with Cargo DONE. Cargo is another thing :) > 10. Package Meta-Data -> >>PackageManifest DONE (but still tools can be built on it) > 11. Less Model Clutter and Duplication -> ? Permanent ongoing process. > 12. Building and Reusing UI Logic -> >>Spec DONE (Spec), but allows enhancements (as everything, I think) > 13. New Network Layer -> >> I think this is Zinc but it still need some work In progress (Zinc is part, but some low-level stuff can be enhanced) > 14. Serializers -> Fuel >> + STON DONE (Fuel, STON) > 15. SystemChangeNotifier replacement -> ? DONE (SystemAnnouncer) > 16. Cleaning Morphic -> Still valid? (asking because of Bloc existance) Permanent ongoing progress (until Bloc arrives, it needs to be done) > 17. Everybody should be able to compile VMs -> ? DONE (CMakeMaker, etc.) > 18. VMs identification and regression testing -> ? DONE > 19. One Unified FFI framework -> Created and still being enhanced DONE (but yes, a v2.0 will be needed) > 20. 64 Bits -> Most of the plugins works on OSX/Unix. Esteban told that it would need around a month to be usable after his holydays. In progress > 21. New Object Formats -> >>STON ? In progress Now, in fact the Pharo Vision document became oldâ¦ we made a lot more stuff than declared there and we are going in more exciting directions now (as shown with the remote debugging). Probably we should work in a "Pharo Vision Updatedâ document, but as always, it takes time, effort, etcâ¦. cheers, Esteban

July 20, 2016