Re: [racket-dev] the new `racket/gui' --- now with bug reports
On Sun, Sep 12, 2010 at 11:40 AM, Matthew Flatt mfl...@cs.utah.edu wrote: The code is still hosted here: http://github.com/mflatt/gr2 This should be http://github.com/mflatt/gr2.git I believe. Robby _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] the new `racket/gui' --- now with bug reports
The other URL is fine, it gives you all the github information about the repo (commit log, browser, etc), whereas the .git is the thing that you give to the git command line. Jay On Tue, Sep 14, 2010 at 5:03 AM, Robby Findler ro...@eecs.northwestern.edu wrote: On Sun, Sep 12, 2010 at 11:40 AM, Matthew Flatt mfl...@cs.utah.edu wrote: The code is still hosted here: http://github.com/mflatt/gr2 This should be http://github.com/mflatt/gr2.git I believe. Robby _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev -- Jay McCarthy j...@cs.byu.edu Assistant Professor / Brigham Young University http://teammccarthy.org/jay The glory of God is Intelligence - DC 93 _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] [plt] Push #21078: master branch updated
Right -- this is why I suggested a simple extension: allow tools to change the default values. Without that, the current situation is creating more implicit dependencies such as this commit. Not too related: the reason that I need to actually change the preferences is that students already had the (lacking) default in their preferences. One way to solve that would be to record in the preference only the divergence from the default -- what you added and what you removed -- so changing the default will propagate as needed. But this is a UI problem (if you click OK -- does that mean that you want the current set and nothing else?), and a better solution would be a restore defaults button. On Sep 13, Robby Findler wrote: But this is editing the user's preferences, not setting the defaults. Robby On Mon, Sep 13, 2010 at 3:52 PM, Eli Barzilay e...@barzilay.org wrote: On Sep 13, Robby Findler wrote: DrRacket doesn't yet have good tool support for such things, but it should at least look at the #lang line for indentation and probably will do that at some point (in which case the dialog will change to be letting you add things to what the #lang line specifies instead of just specifying everything). But not today, I'm sorry to say. Here's the code from my class tool: (define (add-form-specs) (define (sethash! t key val) (unless (hash-ref t key #f) (hash-set! t key val))) (define (setalist l key val) (if (assoc key l) l (cons (list key val) l))) (let ([t (car (preferences:get 'framework:tabify))]) (for ([s '(define: define-type)]) (sethash! t s 'define)) (for ([s '(lambda: cases)]) (sethash! t s 'lambda))) (let* ([l1 (preferences:get 'framework:square-bracket:cond/offset)] [l2 (setalist l1 define-type 1)] [l2 (setalist l2 cases 1)] [l2 (setalist l2 match 1)]) (unless (equal? l1 l2) (preferences:set 'framework:square-bracket:cond/offset l2 (A minor extension to the preferences could probably even do that without writing the file.) -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] [plt] Push #21078: master branch updated
On Tue, Sep 14, 2010 at 9:13 AM, Eli Barzilay e...@barzilay.org wrote: Right -- this is why I suggested a simple extension: allow tools to change the default values. Without that, the current situation is creating more implicit dependencies such as this commit. Do you think that this is needed if my suggestion (made earlier, namely to have #lang line-specific settings that can be augmented by user's preferences) is done? Not too related: the reason that I need to actually change the preferences is that students already had the (lacking) default in their preferences. One way to solve that would be to record in the preference only the divergence from the default -- what you added and what you removed -- so changing the default will propagate as needed. But this is a UI problem (if you click OK -- does that mean that you want the current set and nothing else?), and a better solution would be a restore defaults button. There is a restore defaults button, but it is global. Robby _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] [plt] Push #21078: master branch updated
On Sep 14, Robby Findler wrote: On Tue, Sep 14, 2010 at 9:13 AM, Eli Barzilay e...@barzilay.org wrote: Right -- this is why I suggested a simple extension: allow tools to change the default values. Without that, the current situation is creating more implicit dependencies such as this commit. Do you think that this is needed if my suggestion (made earlier, namely to have #lang line-specific settings that can be augmented by user's preferences) is done? Of course not -- it would also mean that there's no need to leak stuff along the wrong side of the dependency. Not too related: the reason that I need to actually change the preferences is that students already had the (lacking) default in their preferences. One way to solve that would be to record in the preference only the divergence from the default -- what you added and what you removed -- so changing the default will propagate as needed. But this is a UI problem (if you click OK -- does that mean that you want the current set and nothing else?), and a better solution would be a restore defaults button. There is a restore defaults button, but it is global. Yeah, that's the problem -- a global restore is almost the same as nuking your preferences... Could actually be implemented that way. Because I like some of my preferences, I'd never use it, to avoid losing everything. -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
[racket-dev] [PATCH] Use png_set_expand_gray_1_2_4_to_8 when compiling with libpng-1.4
According to [1] png_set_gray_1_2_4_to_8 was renamed to png_set_expand_gray_1_2_4_to_8 in libpng-1.4.0 [1] http://libpng.sourceforge.net/ANNOUNCE-1.4.0.txt Signed-off-by: Mariusz Ceier mce...@gmail.com --- src/wxcommon/wxJPEG.cxx |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/src/wxcommon/wxJPEG.cxx b/src/wxcommon/wxJPEG.cxx index 053a3ee..a13d760 100644 --- a/src/wxcommon/wxJPEG.cxx +++ b/src/wxcommon/wxJPEG.cxx @@ -726,7 +726,11 @@ int wx_read_png(char *file_name, wxBitmap *bm, int w_mask, wxColour *bg) png_set_strip_16(png_ptr); /* Expand grayscale images to the full 8 bits from 1, 2, or 4 bits/pixel */ +#if PNG_LIBPNG_VER = 10400 + png_set_expand_gray_1_2_4_to_8(png_ptr); +#else png_set_gray_1_2_4_to_8(png_ptr); +#endif } /* Set the background color to draw transparent and alpha images over. -- 1.7.2.2 _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
