Re: Next stable release?
On 7 Jun 2008, at 18:30, Adam Fedor wrote: On Jun 7, 2008, at 10:52 AM, Fred Kiefer wrote: Fred Kiefer wrote: At the moment I am updating my second (virtual) Linux system to Ubuntu 8.04, this should include the latest cairo and with that I should be able to reproduce the cairo 1.6.4 issue. This would allow for a GNUstep stable release by the end of next week. Leaving some time to test Richards huge change. The cairo 1.6.0 issue should be solved now. From my side there is no further known issue that would stop us from making the much needed new release. I'm traveling again the last two weeks on June, so we'd have to make the release next week or after July 1. Debian and/or it's derivatives are used by many many people so I'd love to get something out in time for them. When do you want to do the new base release? I think the timeline might be something like this ... monday-wednesday: last chance to deprecate anything we might be wanting to change in the next release cycle thursday: merge trunk into stable branch, adjust version numbers to 1.16.0 (stable) and 1.17.0 (unstable/trunk) friday: update release notes and make release Reasonable? ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: NSTableView editing problem [Was: Next stable release?]
Matt Rice wrote:
On Sun, Jun 8, 2008 at 10:57 AM, Fred Kiefer [EMAIL PROTECTED] wrote:
I was completely wrong here. The problem is at a totally different place.
Look at the code in NSTextFieldsCell that Nicola changed a few months ago:
Ahh, yes changing the below fixes it here i was confused because it is
asked to redraw the edited cell frame, but in the case that it is, the
code is doing what it should by not redrawing.
- (void) drawInteriorWithFrame: (NSRect)cellFrame inView:
(NSView*)controlView
{
/* Do nothing if there is already a text editor doing the drawing;
* otherwise, we draw everything twice. That is bad if there are
* any transparency involved (eg, even an anti-alias font!) because
* if the semi-transparent pixels are drawn over themselves they
* become less transparent (eg, an anti-alias font becomes darker
* and gives the impression of being bold).
*/
if (([controlView respondsToSelector: @selector(currentEditor)] == NO)
|| ([(NSTextField *)controlView currentEditor] == nil))
{
if (_textfieldcell_draws_background)
{
if ([self isEnabled])
{
[_background_color set];
}
else
{
[[NSColor controlBackgroundColor] set];
}
NSRectFill([self drawingRectForBounds: cellFrame]);
}
[super drawInteriorWithFrame: cellFrame inView: controlView];
}
}
This basically means that a text field cell will only draw itself, when
there is no editor for the containing control view. This is nice and fine,
when the text field cell is the only cell of a text field, but in the matrix
and table view case this stops all the cells in the controller from drawing
themselves while there is an editor.
How to get of this trap? We could check if the cell is the selected cell of
its control view and only then not draw it in the editing case. This may
work as a table view has no clear notion of a selected cell and so all cells
will still get drawn, whereas matrix and normal control handle this
correctly.
Another possibility is to move the don't draw check into the control view.
This looks better to me. A cell should always draw itself when asked to do
so, the decision should be put somewhere else.
that seems alright to me, and appears to be what drawRow:clipRect: in
NSTableView is already doing. i've looked at the bug report that code
was added for but didn't have any luck reproducing it with the fix
disabled...
OK, so I submitted this second patch.
Fred
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
WML page refresh
For PFI I'm trying to work around a limitation in the three gateway, it has a 10 second connection timeout ... so if billing takes longer than 10 seconds the handset won't get any response back. I'm adding a holding page ... sent after 5 seconds to say 'please wait', and using cache control headers to stop[ it being cached, and the meta http-equiv=refresh ... tag to get the handset to re-fetch the page. Do you know if this meta tag works reliably for handsets which use wml (I expect that anything which uses xhtml will handle it)? If not, have you any experience with using ontimer= to refresh pages? Can you use 'ontimer=' to refresh the current page, or do you need to put a URL in (eg. 'ontimer=/?Service=XTransaction=Y... where the page has a query string). ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Next stable release?
On Jun 9, 2008, at 1:25 AM, Richard Frith-Macdonald wrote: When do you want to do the new base release? I think the timeline might be something like this ... monday-wednesday: last chance to deprecate anything we might be wanting to change in the next release cycle thursday: merge trunk into stable branch, adjust version numbers to 1.16.0 (stable) and 1.17.0 (unstable/trunk) friday: update release notes and make release Reasonable? That sounds good for me. I'm only afraid of doing something monumentally bad, like releasing something that doesn't compile. I have an extra day or two before I leave to make sure it's tested well. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
