I added a ticket: http://code.google.com/p/pharo/issues/detail?id=2908
Cheers, Adrian On Sep 3, 2010, at 17:20 , Miguel Enrique Cobá Martínez wrote: > El vie, 03-09-2010 a las 15:24 +0200, Adrian Lienhard escribió: >> On Sep 3, 2010, at 15:03 , Pavel Krivanek wrote: >> >>> 2010/9/3 Denis Kudriashov <dionisi...@gmail.com>: >>>> Could you explain why Text is not part of ui system? And why it should be >>>> in >>>> kernel? >>> >>> In fact some time ago I had a headless image without Text but it >>> needed a lot of modifications. Pharo can use text formatting for the >>> source codes. That is the main reason why Text should be in the >>> kernel. >> >> oh, shouldn't we better remove the text formatting in source code feature? >> >> I assume almost nobody uses it and it is more annoying than helpful (e.g., >> if I copy code from a mail, I never want to style my code). > > +1 > > It can be added as an external packege for development images later. > >> >> Adrian >> >> >>> >>> -- Pavel >>> >>>> 2010/9/3 Pavel Krivanek <pavel.kriva...@gmail.com> >>>>> >>>>> On Fri, Sep 3, 2010 at 2:11 PM, George Herolyants >>>>> <george.herolya...@gmail.com> wrote: >>>>>> 2010/9/3 Pavel Krivanek <pavel.kriva...@gmail.com>: >>>>>>> It is headless image. You have to use start-up scripts. See the file >>>>>>> "build_image.sh". >>>>>> >>>>>> So, why do you need this one: >>>>>> >>>>>>> - Fonts need some refactorings. Some sort of AbstractFont only with >>>>>>> capabilities required only by Text class should be part of the kernel. >>>>>> >>>>> >>>>> Because we need Text in the kernel and this class has ugly >>>>> dependencies on fonts. But this class does need only basic information >>>>> about used fonts like name, size etc. It is not the only problematic >>>>> part of the Text class. For example it is dependent on URLs. >>>>> >>>>> -- Pavel >>>>> >>>>>> ? >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project@lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project@lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project@lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project@lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project@lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel Cobá > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
