Re: SignAuPif 1.0.2

Le 16 février 2022 à 00:48, Joseph-B d'un élan de joie s'exprima ainsi :

"Benoît L." <benoit@com.invalid> wrote:
>

 

Pour moi c'est comme de demander de faire un
keystroke cmd-alt-esc down
delay 0.2
return

>
Crois ce que tu veux mais tu te trompes et ce n'est pas grave du moment
que ça marche pour toi ;-)
>

Bien sûr si on nomme un bouton quelconque "Quitter" qui n'est pas un
vrai /Cancel button/ dans une boucle repeat, ton ajout sera
indispensable.

C'est ce que j'ai fait.

>
Bien sûr que non puisque tu as nommément désigné le bouton "Quitter"
comme un "vrai" bouton Cancel dans ton code, que je cite :
>
## set {theButtons, minWidth} to create buttons {"Quitter", "Nouveau
tirage", "Copier"} default button "Copier" cancel button "Quitter" ##

C’est le code d’origine de Dialog Toolkit plus. Code que j’ai du mal à
comprendre et pour lequel il va me falloir passer quelques grosses
minutes (heures) à lire le « Read me ».

Mais rien ne t'y oblige ;-)
>
Entre nous, si tu te mets à Swiftt tu vas être très déçu que ces idiots
de développeurs chez Apple promeuvent l'usage du bouton "Cancel" alors
que selon toi ce serait une abomination. (en fait tu cofonds avec la cmd
killall du Shell)

Un escape dans un repeat cela veut dire que plus rien n’est effectué
après. Pas de sauvegarde, pas de trucs ou bidules pour plus tard : rien,
nada, que dalle.

Que tu ne me crois pas, je m'en fous, mais va bien falloir que tu fasses
confiance aux "vrais programmeurs" de Cupertino (ou même Redmond…)

Cela n’est pas/plus en eux que j’ai confiance :)

<https://www.economist.com/business/2022/01/29/what-if-all-workers-wrote-software-not-just-the-geek-elite>

copie ci-dessous

P.S. Je ne sais pas comment tu as géré une variable avec des retours
charriots, quand j'en mets il me dit qu'il y a un problème :
set toto to "Benoît
Leraillez
Téléphone
Adresse"
 
Il y a un problème, d'où mon utilisation des linefeed plutôt que des
return qui ne fonctionnent pas. Avec linefeed je sais que ça marche :)

>
Je ne vois pas de quoi tu parles ???

Si tu tapes
set set AppleScript's text item delimiters (return & return)
ça ne marche pas mais
set AppleScript's text item delimiters to (linefeed & linefeed)
oui. Pourquoi ? No idea.

Dans la récupération du texte de base des citations, pour en créer la
liste j'utilise llinefeed qui s'écrit aussi "\n" comme TID
(je cite)
## set text item delimiters to "\n\n" ##
>
le retour chariot c'est "\r" ou return et il n'y en pas une seule fois
dans le code que j'ai envoyé par cjoint.
Mais là aussi je dois me tromper ?

Je vois des "

"
Dans ton script.

Je ne connaissais le \n ou \r que dans BBEdit. Sinon il faut que je
relise plus calmement tes scripts. Je vois les concepts, mais je rate
beaucoup de détails.

Mon propos n'est pas de polémiquer avec toi, j'ai proposé une piste qui
m'a semblé plus lègère ; tu en prends, tu en laisses, tu accomodes à ta
convenance ou tu rejettes tout en bloc, ça me convient tout pareil,
c'est toi le maître d'œuvre de ton projet.

Certes, mais tu me donnes des idées, des pistes et surtout des leçons.
Tu es d’ailleurs le seul ici.


Article
-------
What if all workers wrote software, not just the geek elite?

Citizen developers are rapidly becoming the vanguard of corporate
digitisation


In 2018 a field technician working for Telstra, an Australian telecoms
firm, built an app that unified 70 messaging systems for reporting
phone-line problems. The technician did this despite having no coding
experience. The interface may look cluttered: the landing page jams in
150 buttons and a local-news ticker—the app equivalent of an airplane
cockpit, quips Charles Lamanna of Microsoft, who oversees the software
titan’s Power Apps platform that made it possible. But it has been a
hit. Some 1,300 other Telstra technicians employ it, saving the firm an
annual $12m.

Professional developers (pro devs) might poke fun at the technician’s
diy app. But the trend it exemplifies is no joke. Since well before
2017, when Chris Wanstrath, co-founder of GitHub, a coding-collaboration
site, declared that “the future of coding is no coding at all”,
so-called low code/no code (lc/nc) tools have burgeoned. They allow
anyone to write software using drag-and-drop visual interfaces alone (no
code) or with a bit of code creeping in (low code). Under the hood, this
is translated into pre-written or automatically generated code, which
then whirs away.

Such tools are in hot demand. Just 25m people around the world are
fluent in standard programming languages, reckons Evans Data
Corporation, a research firm—one for every 125 people in the global
workforce and 1.4m fewer than needed. That shortfall will rise to 4m by
2025, says idc, a research firm. lc/nc products expand the pool of
coders to “line-of-business” employees who seldom speak c++, Java or
Python. And beyond. Cheryl Feldman went from a junior position in a hair
salon to a technical career at Salesforce, a software firm, thanks to
lc/nc. Samit Saini changed jobs after 13 years as a security guard at
Heathrow to become an “ it solution specialist” at the airport after
making software on Microsoft’s Power Apps.

Overcoming language barriers
idc reckons the low/no coders numbered 2.6m globally in 2021. It expects
their ranks to swell by an average of 40% a year until 2025, three times
as fast as the total developer population. The number of organisations
using Power Apps more than doubled in 2021. It now has 10m monthly
users. basf, a chemicals firm, uses it to let 122,000 workers write
software. A study last year by Aite-Novarica Group, a consultancy, found
that over half of American insurers have deployed or plan to deploy
lc/nc. Unqork, a no-code startup valued at over $2bn and backed by
Goldman Sachs, is convincing other financial firms to take the plunge.
Mr Lamanna envisages a global population of a billion low/no coders.

The dream of codelessness is not new. Tony Wasserman of Carnegie Mellon
University’s branch in Silicon Valley dates it back to the concept of
“automatic programming” in the 1960s. Since then successive waves of
simplification and abstraction have made life easier for programmers by
distancing coding languages further from the machine code understood by
computer hardware. In the early 1990s Microsoft tried to simplify things
further by launching Visual Basic, an early stab at lc/nc. In the next
decade firms like Appian, Caspio, Mendix and Salesforce began offering
products aimed expressly at line-of-business types.

Recently lc/nc’s potential has been unlocked by the cloud, which lets
people connect to data easily and collaborate in real time, says Ryan
Ellis, who leads lc/nc products at Salesforce. Last year Amazon Web
Services (aws), the online giant’s cloud-computing arm, introduced
Amazon SageMaker Canvas, a set of tools that lets people deploy
machine-learning models without writing code. It also offers Honeycode,
a no-code app builder, in beta version.

lc/nc used to be chiefly about making pro devs more efficient. Now it is
also about pulling more humans into creating applications, says Adam
Seligman of aws. In terms of impact, he says, the latest wave “will race
higher up the beach”. For one thing, firms in a hurry to digitise
appreciate that when line-of-business people design software, it speeds
things up. “A field worker making something for other field workers is
hugely valuable as the feedback loop is faster,” says Adam Barr, a
former Microsoft pro dev and author of “The Problem with Software: Why
Smart Engineers Write Bad Code”. As digital natives enter the workforce
they are also demanding automation of repetitive or manual data-entry
tasks, often on pain of walking out.

In addition, lc/nc is fast becoming the secret sauce in modern software
development, notably in machine learning, says Arnal Dayaratna of idc.
The mastery of Python or Java required for this type of
artificial-intelligence (ai) software is daunting even for pro devs.
Bratin Saha, who oversees aws’s machine-learning services, wants
SageMaker Canvas to empower regular business analysts—from marketing or
finance, say—to deploy machine learning. That could increase the number
of ai specialists available to businesses by an order of magnitude, he
predicts.

Some scepticism is warranted. Just because non-programmers are able to
build an application with lc/nc tools does not mean it will be any good,
says Mr Wasserman, just as bug-ridden spreadsheets yield faulty results.
They could also become a headache for corporate it departments if
citizen developers collect customer data that are worthless or, worse,
that violate privacy. Especially with no code, businesses can find that
the functionality they need does not yet exist. No-code platforms make
the first 90% of delivering a useful application easy, and the last 5%
often impossible, says Tim Bray, a pro dev formerly of aws. And many pro
devs remain resistant. Although they turn to lc/nc to simplify some
tasks, plenty of pros see it as the programming cousin of pin-it-on
neckties, in the words of one commentator. Some worry that specialising
in lc/nc makes them look like dilettantes, reports Mr Barr.

lc/nc will not displace “full” coding altogether, as its evangelists
insist. Pro devs will continue writing their firms’ core products and
mission-critical enterprise systems. But they will increasingly be
complemented by legions of enterprising line-of-business workers with a
software-development string to their bow. For employers, this means
greater productivity. For employees, it could be life-changing. In 2019
the Telstra technician became senior business specialist for field
digitisation and has since been promoted again. ■

--
Vie : n. f. Maladie mortelle sexuellement transmissible
benoit chez leraillez.com