Hi guys. As I remember, battery, cell and Wi-Fi icons was blue at top left corner. In 4.4.2 it's white. Any way go back to blue?
Affichage des articles dont le libellé est instead. Afficher tous les articles
Affichage des articles dont le libellé est instead. Afficher tous les articles
mercredi 26 mars 2014
lundi 27 janvier 2014
Re: Highlighting program variables instead of keywords? topic
Skip Montanaro wrote:
> My son sent me a link to an essay about highlighting program data instead
> of keywords:
>
> https://medium.com/p/3a6db2743a1e/
>
> I think this might have value, especially if to could bounce back and
> forth between both schemes. Is anyone aware of tools like this for Python?
AFAIK kdevelop support this.
http://kdevelop.org/sites/kdevelop.o...v_python_1.png
--
By ZeD
> My son sent me a link to an essay about highlighting program data instead
> of keywords:
>
> https://medium.com/p/3a6db2743a1e/
>
> I think this might have value, especially if to could bounce back and
> forth between both schemes. Is anyone aware of tools like this for Python?
AFAIK kdevelop support this.
http://kdevelop.org/sites/kdevelop.o...v_python_1.png
--
By ZeD
Re: Highlighting program variables instead of keywords? topic
On 27/01/2014 01:46, Skip Montanaro wrote:
>> What it is doing is color coding user-supplied identifiers, with different
>> color for each one. I found that confusing to read.
>
> I think it would take some time to get used to, and I don't think it
> would be the only way I'd like to view my program.
>
> I think an interactive pylint (or pyflakes or frosty) type capability
> would be useful, highlighting a subset of the messages it produces,
> like variables which were assigned but never used, or using undefined
> variables. It might be best supported by actually running the checker
> in the background, then using its messages to direct where to
> highlight suspect bits of code.
>
> Skip
>
Pydev uses pylint interactively, must have saved me hours by flagging up
(potential) problems up as I type.
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
>> What it is doing is color coding user-supplied identifiers, with different
>> color for each one. I found that confusing to read.
>
> I think it would take some time to get used to, and I don't think it
> would be the only way I'd like to view my program.
>
> I think an interactive pylint (or pyflakes or frosty) type capability
> would be useful, highlighting a subset of the messages it produces,
> like variables which were assigned but never used, or using undefined
> variables. It might be best supported by actually running the checker
> in the background, then using its messages to direct where to
> highlight suspect bits of code.
>
> Skip
>
Pydev uses pylint interactively, must have saved me hours by flagging up
(potential) problems up as I type.
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
Re: Highlighting program variables instead of keywords? topic
Skip Montanaro <(E-Mail Removed)> writes:
> I think this might have value, especially if to could bounce back and forth
> between both schemes. Is anyone aware of tools like this for Python? Bonus
> points for pointers to an Emacs implementation.
There has been a recent thread on some emacs group about this. Dunno how
far it has gone wrt Python support, but the following mode appeared in
MELPA archives in the last couple of days:
https://github.com/ankurdave/color-identifiers-mode
hth, ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
(E-Mail Removed) | -- Fortunato Depero, 1929.
> I think this might have value, especially if to could bounce back and forth
> between both schemes. Is anyone aware of tools like this for Python? Bonus
> points for pointers to an Emacs implementation.
There has been a recent thread on some emacs group about this. Dunno how
far it has gone wrt Python support, but the following mode appeared in
MELPA archives in the last couple of days:
https://github.com/ankurdave/color-identifiers-mode
hth, ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
(E-Mail Removed) | -- Fortunato Depero, 1929.
dimanche 26 janvier 2014
Re: Highlighting program variables instead of keywords? topic
On 1/26/2014 8:46 PM, Skip Montanaro wrote:
> I think an interactive pylint (or pyflakes or frosty) type capability
> would be useful, highlighting a subset of the messages it produces,
> like variables which were assigned but never used, or using undefined
> variables. It might be best supported by actually running the checker
> in the background, then using its messages to direct where to
> highlight suspect bits of code.
One of my long-term goals for Idle is an extension that would run
user-installed code analyzers over the contents of an edit window, with
the output sent to an OutputWindow. Using the contents of the latter to
mark things in the editor window is an interesting idea. That is already
done for SyntaxErrors and traceback file:line references.
--
Terry Jan Reedy
> I think an interactive pylint (or pyflakes or frosty) type capability
> would be useful, highlighting a subset of the messages it produces,
> like variables which were assigned but never used, or using undefined
> variables. It might be best supported by actually running the checker
> in the background, then using its messages to direct where to
> highlight suspect bits of code.
One of my long-term goals for Idle is an extension that would run
user-installed code analyzers over the contents of an edit window, with
the output sent to an OutputWindow. Using the contents of the latter to
mark things in the editor window is an interesting idea. That is already
done for SyntaxErrors and traceback file:line references.
--
Terry Jan Reedy
Re: Highlighting program variables instead of keywords? topic
> What it is doing is color coding user-supplied identifiers, with different
> color for each one. I found that confusing to read.
I think it would take some time to get used to, and I don't think it
would be the only way I'd like to view my program.
I think an interactive pylint (or pyflakes or frosty) type capability
would be useful, highlighting a subset of the messages it produces,
like variables which were assigned but never used, or using undefined
variables. It might be best supported by actually running the checker
in the background, then using its messages to direct where to
highlight suspect bits of code.
Skip
> color for each one. I found that confusing to read.
I think it would take some time to get used to, and I don't think it
would be the only way I'd like to view my program.
I think an interactive pylint (or pyflakes or frosty) type capability
would be useful, highlighting a subset of the messages it produces,
like variables which were assigned but never used, or using undefined
variables. It might be best supported by actually running the checker
in the background, then using its messages to direct where to
highlight suspect bits of code.
Skip
Highlighting program variables instead of keywords? topic
My son sent me a link to an essay about highlighting program data instead
of keywords:
https://medium.com/p/3a6db2743a1e/
I think this might have value, especially if to could bounce back and forth
between both schemes. Is anyone aware of tools like this for Python? Bonus
points for pointers to an Emacs implementation.
Thanks,
Skip
of keywords:
https://medium.com/p/3a6db2743a1e/
I think this might have value, especially if to could bounce back and forth
between both schemes. Is anyone aware of tools like this for Python? Bonus
points for pointers to an Emacs implementation.
Thanks,
Skip
Re: Highlighting program variables instead of keywords? topic
On 1/26/2014 7:31 PM, Skip Montanaro wrote:
> My son sent me a link to an essay about highlighting program data
> instead of keywords:
>
> https://medium.com/p/3a6db2743a1e/
What it is doing is color coding user-supplied identifiers, with
different color for each one. I found that confusing to read. The only
use I can see for this is to track the usage of a particular name, but
that would be better done by just highlighting one name at a time.
> I think this might have value, especially if to could bounce back and
> forth between both schemes. Is anyone aware of tools like this for
> Python? Bonus points for pointers to an Emacs implementation.
--
Terry Jan Reedy
> My son sent me a link to an essay about highlighting program data
> instead of keywords:
>
> https://medium.com/p/3a6db2743a1e/
What it is doing is color coding user-supplied identifiers, with
different color for each one. I found that confusing to read. The only
use I can see for this is to track the usage of a particular name, but
that would be better done by just highlighting one name at a time.
> I think this might have value, especially if to could bounce back and
> forth between both schemes. Is anyone aware of tools like this for
> Python? Bonus points for pointers to an Emacs implementation.
--
Terry Jan Reedy
Re: Highlighting program variables instead of keywords? topic
On Mon, Jan 27, 2014 at 11:46 AM, Terry Reedy <(E-Mail Removed)> wrote:
> The only use I can see for this is to track the usage of a particular name,
> but that would be better done by just highlighting one name at a time.
In SciTE, I can put the cursor on a word and hit Ctrl-F3 to find other
instances of that word. If that's not enough, following it up with
Ctrl-Home, F3 will find the first instance of it, and if the program
follows the Define-Before-Use principle, that'll be the definition.
That's usually enough.
ChrisA
> The only use I can see for this is to track the usage of a particular name,
> but that would be better done by just highlighting one name at a time.
In SciTE, I can put the cursor on a word and hit Ctrl-F3 to find other
instances of that word. If that's not enough, following it up with
Ctrl-Home, F3 will find the first instance of it, and if the program
follows the Define-Before-Use principle, that'll be the definition.
That's usually enough.
ChrisA
Re: Highlighting program variables instead of keywords? topic
On Mon, Jan 27, 2014 at 11:51 AM, Chris Angelico <(E-Mail Removed)> wrote:
> On Mon, Jan 27, 2014 at 11:46 AM, Terry Reedy <(E-Mail Removed)> wrote:
>> The only use I can see for this is to track the usage of a particular name,
>> but that would be better done by just highlighting one name at a time.
>
> In SciTE, I can put the cursor on a word and hit Ctrl-F3 to find other
> instances of that word. If that's not enough, following it up with
> Ctrl-Home, F3 will find the first instance of it, and if the program
> follows the Define-Before-Use principle, that'll be the definition.
> That's usually enough.
>
> ChrisA
That said, though, I grew up without syntax highlighting of any sort,
and didn't think it particularly important; but now that I have
editors with all those sorts of features, I do find them handy. So
it's possible that a system like this would be of value if once the
programmer gets used to it.
ChrisA
> On Mon, Jan 27, 2014 at 11:46 AM, Terry Reedy <(E-Mail Removed)> wrote:
>> The only use I can see for this is to track the usage of a particular name,
>> but that would be better done by just highlighting one name at a time.
>
> In SciTE, I can put the cursor on a word and hit Ctrl-F3 to find other
> instances of that word. If that's not enough, following it up with
> Ctrl-Home, F3 will find the first instance of it, and if the program
> follows the Define-Before-Use principle, that'll be the definition.
> That's usually enough.
>
> ChrisA
That said, though, I grew up without syntax highlighting of any sort,
and didn't think it particularly important; but now that I have
editors with all those sorts of features, I do find them handy. So
it's possible that a system like this would be of value if once the
programmer gets used to it.
ChrisA
Inscription à :
Articles (Atom)