I've finally gotten back to this and just pushed something that uses
tooltips for these messages now.
Thanks,
Robby
On Tue, Nov 6, 2012 at 9:56 PM, Stephen Bloch wrote:
> I find confusing the caption at the bottom of the dialog that explains what
> the currently-selected language means. I thin
I find confusing the caption at the bottom of the dialog that explains what the
currently-selected language means. I think we could provide the same
information more intuitively with mouseover tooltips, and lose the caption
entirely. I'm not worried about showing a caption for the language the
Ah, no I see what you mean. Let's keep this one for a while.
On Nov 6, 2012, at 9:27 PM, Robby Findler wrote:
> Just to check: did you click on #lang racket when you had #lang racket
> in the buffer already? I need to improve that case a little bit.
>
> On Tue, Nov 6, 2012 at 7:40 PM, Matthi
No, I just played with the language dialog itself.
On Nov 6, 2012, at 9:27 PM, Robby Findler wrote:
> Just to check: did you click on #lang racket when you had #lang racket
> in the buffer already? I need to improve that case a little bit.
>
> On Tue, Nov 6, 2012 at 7:40 PM, Matthias Felleise
Just to check: did you click on #lang racket when you had #lang racket
in the buffer already? I need to improve that case a little bit.
On Tue, Nov 6, 2012 at 7:40 PM, Matthias Felleisen wrote:
>
> Ouch. It satisfies the "gui design laws" so it passes this test.
> For an 'old timer' it doesn't tr
Ouch. It satisfies the "gui design laws" so it passes this test.
For an 'old timer' it doesn't truly work. Let's wait and see.
-- Matthias
On Nov 6, 2012, at 8:17 PM, Robby Findler wrote:
> Okay, I've push something to try to deal with this.
>
> Robby
>
> On Tue, Nov 6, 2012 at 3:35 PM,
Okay, I've push something to try to deal with this.
Robby
On Tue, Nov 6, 2012 at 3:35 PM, Robby Findler
wrote:
> OH! I now get the confusion. Clicking on the teaching languages is the
> way one interacts with that part of the dialog but the #lang lines are
> just text and users of this thing wil
OH! I now get the confusion. Clicking on the teaching languages is the
way one interacts with that part of the dialog but the #lang lines are
just text and users of this thing will be completely confused by
non-parallelism.
Duh!
Hm.
Robby
On Tue, Nov 6, 2012 at 2:24 PM, Matthias Felleisen wrot
+1
Thank you for the experiment. I am coming to two conclusions:
-- I think we're closer to getting it right
-- I am beginning to think we dont' ever wish to abolish it.
On Nov 6, 2012, at 3:09 PM, Asumu Takikawa wrote:
> On 2012-11-06 14:03:50 -0600, Robby Findler wrote:
>> The "docs"
On 2012-11-06 14:03:50 -0600, Robby Findler wrote:
> The "docs" links are meant to all be clickable (and I can certainly
> underline them). What were you expecting, exactly?
>
> I prefer not to make clicking on the "#lang .." part edit the
> definitions window; I think copy and paste is probably cl
The "docs" links are meant to all be clickable (and I can certainly
underline them). What were you expecting, exactly?
I prefer not to make clicking on the "#lang .." part edit the
definitions window; I think copy and paste is probably clearer to the
user.
Robby
On Tue, Nov 6, 2012 at 1:33 PM, A
On 2012-11-06 14:27:42 -0500, Asumu Takikawa wrote:
> The latest dialog with this change looks really nice! FWIW, one thing
> that confused me was that the language selector in the bottom left still
> says "Determine language from source" when you click on "The Racket
> Language" in the dialog.
An
On Tue, Nov 6, 2012 at 10:48 AM, Robby Findler
wrote:
> Okay, thanks for the feedback.
>
> I've pushed a change that mostly takes the suggestions, except no blue
> and instead of the parentheticals, I've linked to the docs. (I don't
> like how the links don't line up vertically so I'll fix that un
On 2012-11-05 22:14:57 -0500, Matthias Felleisen wrote:
> -- I would use "The Racket Language" for the first line of the first item
The latest dialog with this change looks really nice! FWIW, one thing
that confused me was that the language selector in the bottom left still
says "Determine languag
A few minutes ago, Robby Findler wrote:
> Well, I can't say that I'm excited about the prospect of going back
> to that dialog. My goal is to move towards no language dialog at all
> eventually and that change would not be a step in that direction.
(Yes, I know that the goal is to get rid of it --
Well, I can't say that I'm excited about the prospect of going back to
that dialog. My goal is to move towards no language dialog at all
eventually and that change would not be a step in that direction.
While we wait for others' opinions, I've pushed something that makes
the ellipsis clickable, at
Yesterday, Matthias Felleisen wrote:
>
> I second Sam's suggestions.
>
> -- I would use "The Racket Language" for the first line of the first
+117
(I see it in the new dialog, but looks like the language still has the
long name elsewhere.)
> I agree with Robby that *SLs probably have to reje
Okay, thanks for the feedback.
I've pushed a change that mostly takes the suggestions, except no blue
and instead of the parentheticals, I've linked to the docs. (I don't
like how the links don't line up vertically so I'll fix that unless
the whole thing is dumped, depending on what people say her
Matthias Felleisen wrote at 11/05/2012 10:14 PM:
* racket/base (for scripting)
* racket (for programming)
After thinking about it, I think I see what you mean with the
distinction between ``for scripting'' and ``for programming''. But I
think this might be confusing.
(Expl
The DrRacket-based languages have access to the port. So they can get
the actual characters from it.
Not "The Racket (meta-)Language" ;)
I think I'll not color things blue, as that would look strange in this
context; indentation seems to serve the same role and I think I can do
something like wha
I second Sam's suggestions.
-- I would use "The Racket Language" for the first line of the first item
then I would have in blue "Use #lang to Specify the Desired Dialect"
then I would list some candidates, possible as radio buttons
* racket/base (for scripting)
I think it makes sense to put that error message directly into the
teaching languages.
Robby
On Mon, Nov 5, 2012 at 5:16 PM, Sam Tobin-Hochstadt wrote:
> On Mon, Nov 5, 2012 at 6:11 PM, Robby Findler
> wrote:
>> Thanks for taking a look.
>>
>> On Monday, November 5, 2012, Sam Tobin-Hochstadt wr
On Mon, Nov 5, 2012 at 6:11 PM, Robby Findler
wrote:
> Thanks for taking a look.
>
> On Monday, November 5, 2012, Sam Tobin-Hochstadt wrote:
>>
>> - Allow the presence of a #lang line to override the language dialog,
>> or at least give an error that's more helpful than currently.
>>
>
> What did
Thanks for taking a look.
On Monday, November 5, 2012, Sam Tobin-Hochstadt wrote:
> - Allow the presence of a #lang line to override the language dialog,
> or at least give an error that's more helpful than currently.
>
>
What did you have in mind here? The error you get in the teaching languages
On Sat, Nov 3, 2012 at 2:57 PM, Robby Findler
wrote:
> There was a discussion a while back on revising the language dialog
> (I've lost track of the thread since I started hacking on the dialog;
> apologies).
The thread starts here:
http://bugs.racket-lang.org/query/?cmd=view&pr=12642 and continu
25 matches
Mail list logo
