Re: F11 for XO1 - Fonts
by Yioryos Asprobounitis
--- On Mon, 8/3/09, Tomeu Vizoso <tomeu(a)sugarlabs.org> wrote:
> From: Tomeu Vizoso <tomeu(a)sugarlabs.org>
> Subject: Re: F11 for XO1 - Fonts
> To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> Cc: "Daniel Drake" <dsd(a)laptop.org>, fedora-olpc-list(a)redhat.com
> Date: Monday, August 3, 2009, 8:16 AM
> On Mon, Aug 3, 2009 at 12:46, Yioryos
> Asprobounitis<mavrothal(a)yahoo.com>
> wrote:
> >
> >
> >
> > --- On Mon, 8/3/09, Daniel Drake <dsd(a)laptop.org>
> wrote:
> >
> >> From: Daniel Drake <dsd(a)laptop.org>
> >> Subject: Re: F11 for XO1 - Fonts
> >> To: "Tomeu Vizoso" <tomeu(a)sugarlabs.org>
> >> Cc: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>,
> fedora-olpc-list(a)redhat.com
> >> Date: Monday, August 3, 2009, 6:17 AM
> >> 2009/8/3 Tomeu Vizoso <tomeu(a)sugarlabs.org>:
> >> > It's not really hardcoded in the journal, it
> uses the
> >> default Sugar
> >> > font that happens to be 10.
> >>
> >> On the XO the default is changed to 7, so it seems
> like
> >> there's a bug
> >> somewhere. Yioryos, perhaps you could file that
> ticket?
> >>
> >> Thanks,
> >> Daniel
> >>
> >
> > I did.
> > But I can see a pattern I was afraid of.
> > OLPC devs will say is a Sugar issue and SugarLabs devs
> that is an OLPC_specific-build issue...
>
> Different people working on different software components
> means that
> some effort is needed to work together.
The people?... :-)
>
> > Just someone tell me what the damn relevant files
> might be and I'll see if I can wrestle with them.
>
> With the information I have, it could be in lots of files.
> Will try to
> find time to give it a look soon.
>
> Thanks,
Thank you. Ticket number is #1125
>
> Tomeu
>
> >
> >
> >
>
14 years, 9 months
Re: F11 for XO1 - Fonts
by Daniel Drake
2009/8/3 Tomeu Vizoso <tomeu(a)sugarlabs.org>:
> It's not really hardcoded in the journal, it uses the default Sugar
> font that happens to be 10.
On the XO the default is changed to 7, so it seems like there's a bug
somewhere. Yioryos, perhaps you could file that ticket?
Thanks,
Daniel
14 years, 9 months
Re: F11 for XO1 - Fonts
by Daniel Drake
2009/8/3 Tomeu Vizoso <tomeu(a)sugarlabs.org>:
> You should file a bug if it's like that, but I'm pretty sure that in
> 0.84 these labels use the fixed font size of 10. This "logical" 10 is
> scaled depending on the value of the Xft.dpi property, so I'm not sure
> why you aren't seeing any effect.
Size 10 is too big on the XO screen. Similarly it will be too small on
large displays. Sugar should let you change this. Given that size 10
is your default font size anyway, it would make sense just to use the
sugar default font here, rather than hardcoding it.
Daniel
14 years, 9 months
Re: New F11-for-XO1 build is available and needs testing
by James Cameron
On Mon, Aug 03, 2009 at 10:06:09AM +0200, Tomeu Vizoso wrote:
> Sorry to have confused you. As you say, yum update is not the best
> tool if you want to test a specific image.
>
> I find it convenient to test the latest sugar bits in soas because I
> know which packages need to be updated. Just thought others here that
> cannot download the full image may find it useful even if this method
> cannot fully replace a full download.
Thanks. I agree that in the absence of olpc-update, yum update will
have to do.
--
James Cameron
http://quozl.linux.org.au/
14 years, 9 months
F11 for XO1 - Fonts
by Yioryos Asprobounitis
I have a simple (?) question. If I was to change the default font size in the Journal list view and the list home view which files should I be looking at.
If this is too complicated to explain in a post, where should I start reading?
Thx
14 years, 9 months
Re: New F11-for-XO1 build is available and needs testing
by Mikus Grinbergs
James wrote:
>> Regarding adopting a specific set of package versions -- I am
>> normally concerned only with getting "up-to-date" (i.e., "latest")
>> packages when I do 'yum upgrade <package-name>'. But if I *needed*
>> a specific version, I would use 'yumdownloader <package-version>'
>> and then use 'rpm' (+ appropriate flags) to explicitly install it.
>
> Yes, your needs are unlike the childrens' needs. ;-)
Whoa !! I can understand the usefulness to a _school administrator_
for all the systems he is responsible for to have identical
software. [And a developer may want to perform tests on a system
that has *exactly* the same software as another person's.] But why
ought __children__ all have identical versions (e.g., bash-4.0-7) on
their systems ? Whatever happened to the idea that children ought
to be able to re-program their systems (or to add software from
friends, etc.) -- wouldn't that make their XO *different* from that
of other children, even if it started out with the same image ?
> A new method being proposed is a yum update. This was not used
> previously because it did not produce an identical filesystem to a
> particular image version, and it could not be anchored to a particular
> image version, it could only be updated to the latest version of all
> packages. Therefore it was not a test of an image, but rather a test of
> the latest version of all packages.
>
> So, how can you simply ensure that yum update will adopt a specific set
> of versions that match the build that was done?
As I said in what you quoted: don't rely completely on an automated
'yum upgrade'. Rather, use a manual 'yumdownloader' followed by
'rpm' for where you want a specific version of a package.
[Let me suggest that persons subject to download limits are not the
best candidates to call upon to perform 'test of an image'. I
believe the original idea was that the school would pay for fetching
the image -- then the children would perform updating from local
resources, without themselves incurring internet download costs.]
mikus
14 years, 9 months
Re: New F11-for-XO1 build is available and needs testing
by James Cameron
On Sun, Aug 02, 2009 at 02:39:19PM +0200, Tomeu Vizoso wrote:
> On Sun, Aug 2, 2009 at 14:25, James Cameron<quozl(a)laptop.org> wrote:
> > On Sun, Aug 02, 2009 at 11:26:55AM +0200, Tomeu Vizoso wrote:
> >> What about yum update? Specially as F11 has deltarpm.
> >
> > How can you simply ensure (as a user) that yum update will adopt a
> > specific set of versions that match the build that was done? ?Isn't it
> > simpler to use either olpc-update or the image file?
>
> Sure, it was suggested as an alternative to downloading the image file
> while olpc-update isn't working.
Now you've confused me as well. So I shall respond by writing more.
I've not yet tried os3.img because it is a substantial proportion of my
download limit for the month. I'd like to know how to obtain it based
on what I already have. As we have seen from the RPM package version
comparison, there is very little change. I'd like to obtain that very
little change and apply it.
The method that was used last year and the year before was olpc-update.
This worked by granting rsync access to an unpacked filesystem for each
image version. Once the rsync was complete, the filesystem one had
matched the filesystem of the particular image version. It may well
take more wall-clock time, but it always took far less data. It may
well keep your internet connection active, but always for less data.
A new method being proposed is a yum update. This was not used
previously because it did not produce an identical filesystem to a
particular image version, and it could not be anchored to a particular
image version, it could only be updated to the latest version of all
packages. Therefore it was not a test of an image, but rather a test of
the latest version of all packages.
So, how can you simply ensure that yum update will adopt a specific set
of versions that match the build that was done?
--
James Cameron
http://quozl.linux.org.au/
14 years, 9 months
Re: New F11-for-XO1 build is available and needs testing
by Mikus Grinbergs
James wrote:
>> What about yum update? Specially as F11 has deltarpm.
>
> How can you simply ensure (as a user) that yum update will adopt a
> specific set of versions that match the build that was done? Isn't it
> simpler to use either olpc-update or the image file?
Let me relate my experience with 8.2.x (and earlier) builds. Every
time I tried an "incremental" olpc-update, it found some sort of a
mis-matched file -- and switched over to performing some other kind
of (I presume a "full") update. The end result was that the (wall
clock) time during which my internet connection was "busy" was
longer than if I had asked for a "full" olpc-update to begin with.
[It may have been the fact that I apply additional packages, etc.,
after installing each new build - that may have been the cause of
olpc-update deciding to abandon its "incremental" mode.]
Regarding adopting a specific set of package versions -- I am
normally concerned only with getting "up-to-date" (i.e., "latest")
packages when I do 'yum upgrade <package-name>'. But if I *needed*
a specific version, I would use 'yumdownloader <package-version>'
and then use 'rpm' (+ appropriate flags) to explicitly install it.
mikus
14 years, 9 months
Re: F11 for XO1 - Fonts
by Yioryos Asprobounitis
--- On Sun, 8/2/09, Tomeu Vizoso <tomeu(a)sugarlabs.org> wrote:
> From: Tomeu Vizoso <tomeu(a)sugarlabs.org>
> Subject: Re: F11 for XO1 - Fonts
> To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> Cc: fedora-olpc-list(a)redhat.com
> Date: Sunday, August 2, 2009, 1:01 PM
> On Sun, Aug 2, 2009 at 18:47, Yioryos
> Asprobounitis<mavrothal(a)yahoo.com>
> wrote:
> >
> > I have a simple (?) question. If I was to change the
> default font size in the Journal list view and the list home
> view which files should I be looking at.
> > If this is too complicated to explain in a post, where
> should I start reading?
>
> Create a file named /home/olpc/.Xresources that contains
> this line:
>
> Xft.dpi=150
No. This didn't change a thing.
Does it need a #!/bin/bash #!/bin/sh (tried them both too) or something like it on the top?
>
> You can read more here: https://dev.laptop.org/ticket/9324
Well, I did but is not much help other than we have to take into account the real XO screen resolution and adapt to that.
So the question is how can you define which font and size an activity will use but more specifically the Journal and the list home view?
Or is it one size fits all when it comes to fonts?
>
> HTHs,
>
:(
> Tomeu
>
> > Thx
> >
> >
> >
> >
> > _______________________________________________
> > Fedora-olpc-list mailing list
> > Fedora-olpc-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-olpc-list
> >
>
14 years, 9 months
Re: New F11-for-XO1 build is available and needs testing
by Mikus Grinbergs
Yioryos posted a list of package differences between os2 and os3.
I don't know how "authoritative" this list is -- but if those are
*all* the differences, I myself would not have needed to migrate my
os2 XO-1s to os3 -- by explicitly having applied the individual
package upgrades in that list, I already had my (initially os2)
systems at os3 level. [In fact, except for me being too lazy to
upgrade the kernel, because of regular upgrading my devxo-1 XO-1s
are *also* at the package level listed by Yioryos for os3 !]
mikus
14 years, 9 months