Comments for Julien Lecomte's Blog http://www.julienlecomte.net/blog Web Development, Operating System Programming and Amateur Astronomy Sat, 10 Jul 2010 05:57:06 +0000 http://wordpress.org/?v=2.9.1 hourly 1 Comment on OR: Lake San Antonio, 5/11/2010, and Herschel 400 by David Majors http://www.julienlecomte.net/blog/2010/05/515/comment-page-1/#comment-4239 David Majors Sat, 10 Jul 2010 05:57:06 +0000 http://www.julienlecomte.net/blog/?p=515#comment-4239 Julian: YESSS!!!! Congrats on finishing your Herschel 400. You did it a lot quicker than I managed it. It took me about 5 years to go through the list- finishing up the last of the fall objects in Oct of 2008. I accomplished most of it with my old C-8 and a 28mm Plossl with a 56 minute TFOV. There were about 40 objects which I could not confirm seeing with this one. I got those 40 when I went to a 12" Orion Intelliscope and the Orion Q70 eyepiece with a 1.49 deg TFOV. Dave M. CCAS Julian:

YESSS!!!!

Congrats on finishing your Herschel 400.

You did it a lot quicker than I managed it. It took me about 5 years to go through the list- finishing up the last of the fall objects in Oct of 2008.

I accomplished most of it with my old C-8 and a 28mm Plossl with a 56 minute TFOV. There were about 40 objects which I could not confirm seeing with this one. I got those 40 when I went to a 12″ Orion Intelliscope and the Orion Q70 eyepiece with a 1.49 deg TFOV.

Dave M.
CCAS

]]> Comment on YUI Compressor and Java Class Loader by Andrey http://www.julienlecomte.net/blog/2008/10/80/comment-page-1/#comment-4150 Andrey Wed, 03 Mar 2010 12:07:01 +0000 http://www.julienlecomte.net/blog/?p=80#comment-4150 Dean, I've fixed the issue with jquery.blockUI.js If no charset paramis specified for YUICompressor then it use system default encoding (which is ISO-8859-1 for me) but original jquery.blockUI.js have UTF-8 encoding. So you should converte this file to the system default encoding (e.g. ISO-8859-1) or explicitly setting YUICompressor charset param to the UTF-8 for this file. Dean, I’ve fixed the issue with jquery.blockUI.js If no charset paramis specified for YUICompressor then it use system default encoding (which is ISO-8859-1 for me) but original jquery.blockUI.js have UTF-8 encoding. So you should converte this file to the system default encoding (e.g. ISO-8859-1) or explicitly setting YUICompressor charset param to the UTF-8 for this file.

]]> Comment on O’Reilly Book “High Performance JavaScript” Now Available For Preorder by Simone Chiaretta http://www.julienlecomte.net/blog/2010/02/404/comment-page-1/#comment-4125 Simone Chiaretta Wed, 03 Feb 2010 17:21:56 +0000 http://www.julienlecomte.net/blog/?p=404#comment-4125 Is the book available as rough cut or on safari as ebook? I'm starting to hate paper book lately :) Is the book available as rough cut or on safari as ebook? I’m starting to hate paper book lately :)

]]> Comment on From Dream To Reality by Antoine LECOMTE http://www.julienlecomte.net/blog/2009/11/386/comment-page-1/#comment-4085 Antoine LECOMTE Sun, 20 Dec 2009 05:19:06 +0000 http://www.julienlecomte.net/blog/?p=386#comment-4085 Not bad for a nerd.... If you need some mechanical help, just ask me! Antoine Not bad for a nerd….
If you need some mechanical help, just ask me!

Antoine

]]> Comment on From Dream To Reality by George Feliz http://www.julienlecomte.net/blog/2009/11/386/comment-page-1/#comment-3850 George Feliz Mon, 23 Nov 2009 00:32:07 +0000 http://www.julienlecomte.net/blog/?p=386#comment-3850 Looking good, Julien. Now a few days of sanding and 6-8 coats of Polyrurethane, and it will really look great! Just kidding, I know it will be painted black, but I prefer the natural look. Clear Skies, George Looking good, Julien. Now a few days of sanding and 6-8 coats of Polyrurethane, and it will really look great!

Just kidding, I know it will be painted black, but I prefer the natural look.

Clear Skies,
George

]]> Comment on A Better Implementation Of The Input Prompt Pattern by devsmt http://www.julienlecomte.net/blog/2009/09/314/comment-page-1/#comment-3756 devsmt Tue, 15 Sep 2009 15:29:43 +0000 http://www.julienlecomte.net/blog/?p=314#comment-3756 extremely nice this creative use of markup. tnx for sharing the good idea extremely nice this creative use of markup. tnx for sharing the good idea

]]> Comment on A Better Implementation Of The Input Prompt Pattern by Rik http://www.julienlecomte.net/blog/2009/09/314/comment-page-1/#comment-3754 Rik Tue, 15 Sep 2009 12:42:27 +0000 http://www.julienlecomte.net/blog/?p=314#comment-3754 Nice implementation for present use. Hopefully, HTML5 will ease this behavior through the placeholder attribute (currently implemented in WebKit browsers). Nice implementation for present use.

Hopefully, HTML5 will ease this behavior through the placeholder attribute (currently implemented in WebKit browsers).

]]> Comment on A Better Implementation Of The Input Prompt Pattern by Dominykas http://www.julienlecomte.net/blog/2009/09/314/comment-page-1/#comment-3750 Dominykas Tue, 15 Sep 2009 10:09:33 +0000 http://www.julienlecomte.net/blog/?p=314#comment-3750 As Luke says, the real problem is the autofilled values, which make things look very very very ugly. Especially if one of the fields is a password field... So, you do need to init the default values with timeout. The label approach also has problems with positioning, since every browser has different margins/paddings for the input elements. But that can be solved with enough determination :) Another problem is that some browsers keep the focus upon page reload/back/forward - which means that you also need to double check the hasFocus upon init to avoid changing the value of the field when the user is already about to start typing. http://code.dominykas.com/js/hasFocus.html - focus on the input, F5 in IE. (The actual code, I think, has a bug for activeElement - can't remember if I fixed it) As Luke says, the real problem is the autofilled values, which make things look very very very ugly. Especially if one of the fields is a password field… So, you do need to init the default values with timeout.

The label approach also has problems with positioning, since every browser has different margins/paddings for the input elements. But that can be solved with enough determination :)

Another problem is that some browsers keep the focus upon page reload/back/forward – which means that you also need to double check the hasFocus upon init to avoid changing the value of the field when the user is already about to start typing.

http://code.dominykas.com/js/hasFocus.html – focus on the input, F5 in IE. (The actual code, I think, has a bug for activeElement – can’t remember if I fixed it)

]]> Comment on A Better Implementation Of The Input Prompt Pattern by Thomas Broyer http://www.julienlecomte.net/blog/2009/09/314/comment-page-1/#comment-3749 Thomas Broyer Tue, 15 Sep 2009 09:02:38 +0000 http://www.julienlecomte.net/blog/?p=314#comment-3749 The best implementation, of course, is to rely on the browser's own implementation: [input placeholder="Search"] (well, in the case of a search field, you'd rather even use [input type=search placeholder="Search"]) placeholder="" is implemented in WebKit for a long time (which means Safari and Chrome); for others you'd then rely on JavaScript to create a [label] and use your CSS positioning trick (which I concur is the best solution, compared to changing the value="" attribute's value). To style the placeholder, you can use the ::-webkit-input-placeholder pseudo-element (input::-webkit-input-placeholder). ...and to detect whether placeholder="" is implemented, see http://diveintohtml5.org/detect.html#input-placeholder The only "issue" with placeholder="" is that it isn't meant to replace [label], which you seem do be doing here: http://www.w3.org/TR/html5/forms.html#the-placeholder-attribute Also, just wondering, couldn't you position the [label] *below* the [input] and dynamically changing the [input]'s background (from transparent to white) instead of moving the [label] around? the only drawback that I can see is that as soon as you style the background you no longer have the "platform" styling (thin blue border on Windows for instance) and you have to style the border too. The best implementation, of course, is to rely on the browser’s own implementation: [input placeholder="Search"] (well, in the case of a search field, you’d rather even use [input type=search placeholder="Search"])

placeholder=”" is implemented in WebKit for a long time (which means Safari and Chrome); for others you’d then rely on JavaScript to create a [label] and use your CSS positioning trick (which I concur is the best solution, compared to changing the value=”" attribute’s value). To style the placeholder, you can use the ::-webkit-input-placeholder pseudo-element (input::-webkit-input-placeholder).

…and to detect whether placeholder=”" is implemented, see http://diveintohtml5.org/detect.html#input-placeholder

The only “issue” with placeholder=”" is that it isn’t meant to replace [label], which you seem do be doing here: http://www.w3.org/TR/html5/forms.html#the-placeholder-attribute

Also, just wondering, couldn’t you position the [label] *below* the [input] and dynamically changing the [input]’s background (from transparent to white) instead of moving the [label] around? the only drawback that I can see is that as soon as you style the background you no longer have the “platform” styling (thin blue border on Windows for instance) and you have to style the border too.

]]> Comment on A Better Implementation Of The Input Prompt Pattern by Julien Lecomte http://www.julienlecomte.net/blog/2009/09/314/comment-page-1/#comment-3745 Julien Lecomte Tue, 15 Sep 2009 04:26:45 +0000 http://www.julienlecomte.net/blog/?p=314#comment-3745 Thanks Luke, this is very useful research! Thanks Luke, this is very useful research!

]]>