[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bean: current problems

From: Fred Kiefer
Subject: Re: Bean: current problems
Date: Sat, 18 Feb 2012 18:02:12 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1

On 16.02.2012 10:38, Riccardo Mottola wrote:

with Bean I notice several problems. I don't imply that they are
regressions, perhaps they have been this way since ages, I didn't try
Bean lately, so I don't remember.

Screenshot attached.

1) the color encoding problem Fred mentions. The temporary workaround is
just to remove the values. I don't know if the file is GNUstep or Cocoa
generated, I suppose the latter, but Greg needs to confirm this, since
he imported Bean originally.

Sorry my description here was incorrect. Bean doesn't use keyed coding here, it uses normal coding, but as this file comes from Apple it is in Apple format. And we don't support the typed stream Apple used for its coding. If we ever implemented this format it would mean that we have to re-implement (non-keyed) coding for all Foundation and AppKit classes in a way that breaks backward compatibility. This is not very likely. Best to remove these values from the defaults file or replace them with GNUstep encoded values.

2) the text typed is very strange. I'm using the cairo backend and the
default Font draws as in the screenshot, with positioning errors. It
looks as if a bitmapped font is placed with another positioning or
something like that. I tried to open a RTF file generated by Ink, it has
a different font setting and it looks perfect.

I cannot reproduce this behaviour here. But I remember that you have this in other applications as well. I think Bean uses Helvetica as its default font, maybe this is a bitmap font on your system and the font metrics are incorrect?

3) the toolbar items look strange. I don't think they need to have
"toolbar label:" in the description

Not visible on my machine. See screen shot.

4) 2012-02-16 10:22:56.129 Bean[9174]
NSNumberFormatter-getObjectValue:forString:... not fully implemented

Yes, but this message has been around for a very long time now. And we only report this for NSNumberFormatterBehavior10_0 (otherwise we use ICU). Maybe we could just remove this message and live with the incomplete result?

Attachment: Bean_screenshot.png
Description: PNG image

reply via email to

[Prev in Thread] Current Thread [Next in Thread]