L’Education nationale sous le chochttps://www.liberation.fr/debats/2020/08/26/l-education-nationale-sous-le-choc_1797689
]]>Pew Research Center : https://www.journalism.org/2020/07/30/americans-who-mainly-get-their-news-on-social-media-are-less-engaged-less-knowledgeable
]]>Le gouvernement renonce une fois de plus à sa souveraineté et stocke nos données sur des serveurs accessibles par un gouvernement tiers et à disposition des GAFAM...
]]>Pourtant quand on est enfermé chez soi et que la médiathèque est fermée, quelques livres ça aurait pu être pas mal... Vous pourrez toujours lié des classiques libres de droit sur vous écrans :-/
]]>Here are release highlights:
Tools can now be grouped in the toolbox, and this option is enabled by default.
You can customize groups by creating new ones and dragging tools between them. The changes will take effect immediately. Or you can disable the grouping entirely. You’ll find configuration options on the Interface/Toolbox page of the Preferences dialog.
Please note that the default order of tools in the toolbox is now different. You can customize it as well.
Sliders typically used in GEGL-based filters and tools’ options now have a compact style by default: they take a lot less space vertically and have a vastly improved interaction model.
You can use multiple modifiers with either left-click or mouse wheel scrolling:
Here is the full reference:
The ‘You can drop dockable dialogs here’ message is now gone from the toolbox, and other empty dockable areas. This used to annoy quite a few users who used a single/double-column layout for the left panel.
But since we still need to hint where you can dock dialogs, whenever you drag a dialog, all dockable areas will be highlighted.
Since releasing 2.10 in 2018, we received a lot of feedback that the symbolic icon theme used by default doesn’t have enough contrast. We recently did a quick poll on Twitter showing people a variation of the theme with more foreground/background color contrast, and that certainly clicked with users.
Some of the feedback suggested, however, that a part of the demographic likes the current contrast. So instead of pushing changes for everyone, we introduced a new high-contrast symbolic theme. You can choose it in the Preferences dialog, just like any other icon theme.
The contrast is a compile-time variable that you can change prior to building GIMP from source code. We see this as more of a dirty temporary solution.
With GTK3, it’s going to be a lot easier to make things configurable. In particular, upcoming Inkscape 1.0 is featuring a new icon theme called ‘multicolor’ that makes a great use of CSS in GTK3 and, while staying symbolic, uses some color where it matters. We will be definitely looking closer at that approach.
To complement the new high-contrast variation of the symbolic theme, GIMP now also draws a double black/white border around FG/BG indicator in the toolbox to make that border more legible, especially in dark themes.
A new option called Composited Preview is now available for most transformation tools. It enables the rendering of the transform preview with the right position of the modified layer in the layers stack, as well as with the correct blending mode.
It comes with two sub-options.
Preview linked items enables previewing changes to all linked items like layers rather than just the currently selected item.
Synchronous preview render the preview as you move the mouse/stylus pointer to change the transform instead of waiting for the movement to stop. This provides instant feedback when GIMP can update the display fast enough, which is usually not the case with large layers.
GIMP now also automatically previews the clipping of transformed layers. This allows reducing the amount of trial and error when e.g. rotating.
A new transform tool helps changing the perspective of a layer or panning it in 3D space. You can set a vanishing point, then rotate the layer in X, Y, and Z axes.
Multiple modifiers are available to constrain rotation and panning to just one axis. The Unified interaction checkbox allows shifting the vanishing, as well as panning and rotating without switching between tabs on the on-canvas settings dialog. Finally, the Local frame option allows controlling the transformation in the layer’s local frame of reference, instead of the global one.
The brush outline motion now feels smoother thanks to raising the refresh rate from 20 FPS to a maximum of 120 FPS, as well as disabling the snapping to dabs (new option, off by default). The former became a sensible idea thanks to painting parallelization introduced by Ell several releases ago. The snapping to brush dabs can be re-enabled on the Image Windows page of the Preferences dialog.
Additionally, the paint rate of the Airbrush tool was increased from 15 to a maximum of 60 stamps per second, making paint buildup smoother. Note that, as a result, the relation between the tool’s Rate parameter and the actual paint buildup rate is now different, which may affect existing tool presets.
It’s also worth mentioning that the Warp Transform tool now respects mouse pointer settings defined on the Image Windows page of the Preferences dialog.
Furthermore, in order to improve the quality of downscaled brushes, paint tools now use mipmaps for downscaling bitmap brushes. Instead of resampling downscaled brushes directly from their original size, GIMP now creates a box-filtered mipmap hierarchy for the original brush on demand, and uses the closest mipmap level as the resampling source for downscaled brushes. This significantly reduces aliasing in downscaled brushes, producing smoother results.
The Mandala symmetry painting mode now has a Kaleidoscope option, which combines both rotation and reflection.
When the Kaleidoscope option is enabled, subsequent strokes are mirrored across the symmetry slice edges.
GIMP now spends a lot less time loading Photoshop’s brushes (ABR). So if you use a lot of those, the startup time will become pleasantly smaller, by order of a magnitude.
The technical explanation is that GIMP used to read the stream of ABR data byte by byte, and now it uses scanline reading instead.
PSD files now load faster mostly by eliminating excessive copies between the original file and the project representation inside GIMP. For large PSD files, the loading is now ~1.5 to ~2 times faster.
Moreover, GIMP is now capable of loading CMYK(A) PSD files (only 8-bit per channel for now). It does so by converting pixels to RGB(A) float using sRGB as the profile which, we know, is not good enough for serious work.
However, the plug-in is already using babl formats to specify and communicate CMYK pixel format encodings with GIMP. This is a good first step towards better CMYK support. It can be improved both on its own as well as integrate with the ongoing work enabling general color-space support for babl formats in the development branch.
The Layers dialog finally consolidates the UI for merging layers and attaching floating selections.
The bottom toolbar will now display a button for anchoring a floating selection only when there is one. Otherwise, it will display a button for merging layers.
You can also use several modifiers:
GIMP will now check every time on the start up if the version of GIMP you have is the latest one available. It will do so by pinging GIMP’s server for the version of the latest release, then comparing it to the one installed on your computer.
GIMP will also compare revisions of the installers so that users would be aware of updated installers available. This is typically useful when we update installers to provide fixes in 3rd party components that we use.
Finally, this feature is used when constructing a crash report. If you experience a crash while using an outdated version of the program, GIMP will now tell you so.
You can disable this feature on the System Resources page of the Preferences dialog, and manually use the Check for updates button in the About dialog.
It is also possible to build GIMP without this feature by passing the
--disable-check-update
argument to the configure script.
Work on our continuous integration goes forward. We now implemented
automatic compilation of the main development branch both with the
legacy autotools
build system and the new meson
one. We also produce
an alternative build with the Clang
compiler (additionally to the GNU
compiler gcc
).
Moreover, for cross-platform development, we now produce Windows builds,
both for 32-bit and 64-bit, cross-compiled with the
crossroad
/Mingw-w64
tools.
All these automatic builds allow us to catch early on specific bugs which may affect only certain configurations or platforms.
We hope it could also attract new developers wishing to dabble in contributing. Looking at compilation warnings and trying to fix them may be a very good first step into GIMP code. It would be much less overwhelming than actually trying to dive into our huge code from scratch.
If you are interested, look into our CI
pipelines and look at
the last ones (preferably the master
branch), then into one of the
various compilation jobs. We will be waiting for your
patches!
There have been several improvements in GEGL since the release that accompanied GIMP 2.10.14:
The babl library got build fixes, improved host CPU detection, macOS-specific fixes, and Clang warning squelches.
Code contributors to this release are: Alex Samorukov, Anders Jonsson, band-a-prend, Cyril Richard, Elad Shahar, Ell, Elle Stone, Félix Piédallu, Jehan Pagès, Jernej Simončič, lillolollo, Massimo Valentini, Michael Natterer, Nikc, Øyvind Kolås, Pascal Terjan, woob.
Translators: Alan Mortensen, Alexandre Prokoudine, Anders Jonsson, Asier Sarasua Garmendia, Balázs Meskó, Balázs Úr, Bruce Cowan, Daniel Korostil, Jordi Mas, Julien Hardelin, Marco Ciampa, Piotr Drąg, Rodrigo Lledó Milanca, Ryuta Fujii, Sabri Ünal, sicklylife, Sveinn í Felli, Tim Sabsch, Zander Brown.
As usual, we thank lillolollo, nmat, and Michael Schumacher for triaging bug reports, and Julien Hardelin for keeping the user manual up to date.
Our main objective is still completing the GTK3 port and releasing GIMP 3.0. This will take a while.
One of the ideas we are also exploring is improving the default single-window layout and introducing named workspaces streamlined for common use cases such as general editing, web design, digital photography, painting etc.
If you customized your default GIMP layout, we encourage you to post a screenshot and tell us about your use cases for GIMP that affected this customization. You can do that either on Twitter or in the mailing list for users.
Once we have a representative amount of samples for each common use case, we will analyze the data and see if we can create default workspaces that you can further tweak to your liking.
For the time being, don’t forget you can donate to the project and personally fund several GIMP developers, as a way to give back, and to accelerate the development of GIMP.
]]>Illustration avec cet article du Monde Diplomatique
https://dia.so/4eh . Des faits sont rapportés sur le comportement des forces de l'ordre, certains étayés par des preuves. Le pouvoir démentira formellement, parlera de manipulation, d'images tronquées, sorties de leur contexte. Pour autant, les faits sont là : parmi les force de l'ordre aujourd'hui, certains se lachent totalement, assurés de leur impunité. Jusqu'au moment où le vent tournera et quelques lampistes paieront. Le tout au détriment de la relation citoyens / forces de l'ordre / justice. Dans quelque sens qu'on la prenne. Et à terme (dès maintenant aussi) tout le monde est perdant dans l'affaire...
Pour autant, il est absolument faux dire que tout le monde déteste la police comme cela apparait dans l'article. Sans doute grâce à l'efficacité des écrans de fumée et des dissimulations diverses. Les faits ne sont pas appropriés. Et sondage après sondage, les forces de l'ordre caracolent en tête des institution ayant la plus grande confiance des français : https://www.ifop.com/publication/le-regard-des-francais-sur-la-police/
Du coup, l'article tombe à l'eau. Mais pas poussé par la police. Il s'y jette tout seul...
]]>Les données de 4 milliards de comptes personnels sont stockées sur ce serveur (futura science)
Et elles ont fuité bien sûr. Le plus génial c'est que c'est comme ça. Vous ne pouvez rien y faire. Vous avez sans doute consenti un jour par un click rapide et agacé à des conditions illisibles... Rendez vous sur have I been pwned si vous voulez en savoir le cœur net.
]]>Nucléaire : comment le gouvernement travaille en catimini à la construction de six nouveaux EPR
]]>Le développement personnel, c'est l'idéologie rêvée du néolibéralisme
]]>Thé Economist (en)
]]>Fixing the ‘impeach this’ map with a transition to a cartogram
]]>Diaspora + Signal ?
]]>Chers amis sur framasphere, cherchez votre nouveau pod.
]]>https://www.bloomberg.com/graphics/2019-why-amazon-rainforest-is-on-fire/
]]>#globalwarming #nomorewords #actions
En Islande, Okjökull n’est plus un glacier. Et « tous nos glaciers suivront la même voie »
]]>N'oublions pas que #github est désormais propriété de #Microsoft, grand #colabo avec les services de renseignement US. Avez vous essayé gitlab ou une de ses instances ? Vous devriez...
]]>See the drastic toll climate change is taking on our oceans https://www.nationalgeographic.com/environment/2019/06/see-the-drastic-toll-climate-change-is-taking-on-our-oceans/
]]>Twitter Follow Helper est un script Greasemonkey (ou une extension Chrome) destiné à faciliter la décision de suivre ou non quelqu'un sur Twitter. Sur chaque page de profil, le script ajoute des informations sur l'activité de la personne :
Merci de noter que c'est un bricolage permanent. Il y a sans doute des bugs. N'hésitez pas à m'en faire part et soyez patients : j'ai une famille des amis et un travail qui sont plus importants pour moi que ce bout de code.
Ce script s'installe comme n'importe quel script Greasemonkey. Cliques sur ce lien et accepte l'installation (je jure qu'il n'y pas de code malicieux). Tu peux aussi parcourir le code sur userscript.org... Le script sera sans doute mis à jour de temps en temps. Mais grâce à la magie de GM Script Update Control vous serez toujours informé...
Dans le temps, le script marchait bien avec l'extension TamperMonkey. Mais il était devenu trop lourd de maintenir une version qui soit compatible avec les deux. Du coup, je vous ai mitonné l'extension Twitter Follow Helper qui donne (normalement) le même résultat que le userscript.
Laisses vos commentaires (ça me changera des spams), suggestions, rapports de bugs ci dessous ou sur la page du script. Les compliments et autres sont aussi bienvenus...
Si tu as quelques pièces poussiéreuses au fond d'une poche, n'hésite pas à m'encourager à faire mieux, j'irais boire une bière à ta santé.
En tant qu'être humain utilisant Twitter n'utilisant aucun robot pour lire mes tweets et essayant de rester un peu sociable, j'avais des difficultés pour décider si je devais suivre quelqu'un ou pas. Suivre tout le monde et n'importe qui est le meilleur moyen de crouler bêtement sous les tweets.
Il y a plein d'outils partout sur internet qui donnent des statistiques sur les comptes twitter. Mais c'est un peu lourd de tous les visiter à chaque fois.
Twitter Follow Helper était né.
Twitter Follow Helper is a Greasemonkey userscript / Chrome extension tool designed to help you to decide wether or not you should follow someone on Twitter. On any profile page, the script will add some informations about the activity of the person you're looking at :
Please note this script will always be under "developement". It might be a bit buggy. Feel free to tell me behind and be patient, i have a family, some friends and a job that are more important than this script for me.
You can install this script as any Greasemonkey userscript : click on this script link and agree with install terms. The script is hosted on userscripts which is a huge script repository for Greasemonkey. You can also browse the code there... the script will probably be updated from time to time. But with the magic of GM Script Update Control the script should prompt you about any update.
The script used to work through tampermonkey. However, it has become more and more tricky to maintain dual compatibility with firefox. So you can know access all functionality with Twitter Follow Helper extension
Leave your requests, comments or bugs report on just here down or on the userscripts.org page. You can also post anything else...
If you have some old dusty coins, you can put them in my moneybox. It's a good way to tell me you like this.
As I'm using Twitter like a human being, not using any bot to parse my timeline or follow anybody and trying to keep conversational, it was very difficult for me to decide whether or not i should follow someone : Following anybody is the best way to collapse under timeline stupid overload.
There are lot of tools all over the internet giving you some good stats on any account. But you can't visit them each time you are about following someone.
Twitter Follow Helper was born.
Allez, ne boudons pas notre plaisir, d'autant que je ne poursuis pas la gloire. J'ai quand même droit dans l'annonce à un lien vers la page du script sur le AirCarnet, qui m'a valu près de 400 visiteurs, ainsi qu'à mon nom dans l'extension. Et surtout, le plaisir de savoir que mon travail va être utilisé par beaucoup plus de monde...
]]>http://www.google.com/reader/*
et https://www.google.com/reader/*
./* COPY ALL THIS -> END */and
/* END OF COPY ZONE */
// ==/UserScript==
@version yourScriptVersion
metadata). Please, remember not to put any space in your version number use _ (underscore) instead.var myScriptId=yourScriptIdYou can also set control frequency in order to consume less bandwidth set this with this parameter :
var myScriptVersion="yourScriptVersion";
var GMSUCfreq=9; // frequence of control updates (days)
var GMSUCtime=16; // delay before alert disapears.
var GMSUCPal=cpUserscript; // colorPalette you preferthree are proposed :
cpChrome
, cpUserscript
or cpFlickr
, but you may ad any you want to create by defining a new one using var yourPalette=new colorPalette(background,highlight,foreground,light);
I did test this method on this testing script and it seems to work.
There are some limitation of @require usage in GreaseMonkey : The GM Script Update Control used by your script will be the one available at the date of the FIRST install by your users. If you update your script, GM_scriptVersionControl function WILL NOT upgrade to last version. Users will have to uninstall and reinstall your script to have it updated. It may cause some compatibility problems...
// @require http://userscripts.org/scripts/source/35611.user.js
thisId=yourScriptId;
thisVersion="yourScriptVersion";
GMSUCfreq=9; // control frequency
GMSUCtime=16; // disapearing delay
GMSUCPal=cpUserscript; // color palette
GM_scriptVersionControl();
Definitely not. You may only copy-paste the function from the source script.
But you may find useful to be informed of future updates. If installed, the GmScript will prompt you about this...
the alert message is displayed in French or in English (default) using the navigator.language
property. If you put any translation in comment here or there, i will be pleased to implement it. Use the following models please :
// français
Txt[1]["fr"]="Vous utilisez la version";
Txt[2]["fr"]="du script";
Txt[3]["fr"]="La version officielle est différente";
Txt[4]["fr"]="installer";
Txt[5]["fr"]="voir le code";
Txt[6]["fr"]="propulsé par";
// english
Txt[1]["en"]="You're using";
Txt[2]["en"]="version of";
Txt[3]["en"]="script. Official release version is different";
Txt[4]["en"]="install";
Txt[5]["en"]="view code";
Txt[6]["en"]="powered by";
If you think you're a color genius and defined a pretty nicest of the world colorPalette, post it here or there...
As you can see through Revisions history, i'm very pleased about any comment you can do about this script and its functionalities. And I manage to take care of your idea when i got time for this. Please, don't wait and put anything you brain has in about this script here or there...
as I had no idea about licensing this work, i putted it under the creative-commons by-nc-sa one.
@require
can be installed on my computer and I don't know why,