From 651cf144a5474ce54b52f072c31150ba6c7fbc6b Mon Sep 17 00:00:00 2001 From: Ichthyostega Date: Fri, 28 Nov 2025 21:21:13 +0100 Subject: [PATCH] Release: general washdown - comb through the Website, starting at the frontpage - add a **news** entry to confirm this major upgrade step (C++23) - improve the wording in various overview pages - adapt the ''release checklist'' to align it with **git-flow** - reorganise the image folder(s) on the website - the animated beating heart is back ;-) --- admin/build_lumiera-build-dependencies.sh | 61 --- admin/deb.lumiera.org.PUB.gpg | Bin 6927 -> 17715 bytes admin/docker_open-lumiera-buildenv.sh | 44 -- admin/gnu-indent.sh | 5 - .../GuiDiscussion/ConceptProposals/AkhiL.txt | 2 +- .../ConceptProposals/Alcarinque.txt | 2 +- .../GuiDiscussion/ConceptProposals/Barnes.txt | 8 +- .../ConceptProposals/RichardSpindler.txt | 2 +- .../GuiBrainstormingReviewed.txt | 5 +- .../archive/rawGuiBrainstorming.moinmoin | 55 ++- doc/devel/meeting_summary/2008-10-10.txt | 2 +- doc/devel/meeting_summary/index.txt | 11 + doc/technical/build/BuildDroneDraft.txt | 200 -------- doc/technical/code/CodingGuidelines.txt | 12 +- doc/technical/code/c++11.txt | 6 + doc/technical/code/index.txt | 51 ++- doc/technical/infra/Release.txt | 134 ++++-- doc/technical/infra/index.txt | 41 +- doc/user/intro/intro.txt | 1 + doc/user/tutorials/building.txt | 3 +- doc/user/tutorials/contributing.txt | 45 +- wiki/thinkPad.ichthyo.mm | 430 ++++++++++++++++-- 22 files changed, 632 insertions(+), 488 deletions(-) delete mode 100755 admin/build_lumiera-build-dependencies.sh delete mode 100755 admin/docker_open-lumiera-buildenv.sh delete mode 100644 admin/gnu-indent.sh delete mode 100644 doc/technical/build/BuildDroneDraft.txt diff --git a/admin/build_lumiera-build-dependencies.sh b/admin/build_lumiera-build-dependencies.sh deleted file mode 100755 index 96fbf8a76..000000000 --- a/admin/build_lumiera-build-dependencies.sh +++ /dev/null @@ -1,61 +0,0 @@ -#!/bin/sh -# -# build_lumiera-build-dependencies.sh - prepare/build on a pristine Debian/Ubuntu system (Docker) -# -# -#------------------------------------------------------Setup -# The Debian DEB Depot to retrieve the source packages -DEBIAN_REPO="http://lumiera.org/debian/" -SRC_DISTRO="stretch" -REPO_SECTION="experimental" -# -# GPG pubkey to trust for signed packages -TRUSTED_GPG=$(dirname $0)/deb.lumiera.org.PUB.gpg -# -# Directory for building DEB packages -PACK_DIR=./pack -# -#------------------------------------------------------Setup(End) -# -fail() { - echo "\nFAIL: $1\n\n" - exit 1 -} - -# Sanity-Checks -[ -f $TRUSTED_GPG ] || fail "GPG Key not found: $TRUSTED_GPG" -mkdir -p $PACK_DIR -[ -w $PACK_DIR ] || fail "Unable to build. Can not write to $PACK_DIR" - - -# prepare the host system with Lumiera package sources -cp $TRUSTED_GPG /etc/apt/trusted.gpg.d/ -chmod a+r-x /etc/apt/trusted.gpg.d/$(basename $TRUSTED_GPG) -echo "deb-src $DEBIAN_REPO $SRC_DISTRO $REPO_SECTION" > /etc/apt/sources.list.d/55-lumiera.list - -apt update -apt install -y build-essential ca-certificates -apt update - -# build some special build dependencies from source -WORKDIR=$(pwd -P) -cd $PACK_DIR - -echo "\n\n======= building NoBug =======\n" -apt-get -y build-dep nobug -apt-get source --compile nobug -dpkg -i nobug-dev*deb libnobug*deb || fail "installing NoBug" -echo "\n\n======= building GDLmm =======\n" -apt-get -y build-dep libgdlmm-3-dev -apt-get source --compile libgdlmm-3-dev || fail "installing GDLmm" -dpkg -i libgdlmm-3*deb - -# install the build dependencies of Lumiera from DEB -echo "\n\nInstalling Lumiera build dependencies...\n" -apt-get -y build-dep lumiera - -# return to the working directory -cd $WORKDIR - -echo "Build-Dependencies of Lumiera successfully installed.\n\n" - diff --git a/admin/deb.lumiera.org.PUB.gpg b/admin/deb.lumiera.org.PUB.gpg index 6403dc3b65d41cd281de173ec2ec5717839012c1..f049db8f8893f3e4c42cca22d6228dd205fd4633 100644 GIT binary patch literal 17715 zcmeIZWn5g#wl6wy5AN<3AUMGx5FCON+})iZ9SDTr?ivX0?vg-o3GVLhE`2*|?S1w- z=bn4+-ur!c@58J9)vVE@Mpf6S{?9RM))Ek~_#IPI+q_L;NDYisaSa7` zPbg|6`Q3Q+Om9cw;jRlKIgCE?QJy4bG=uhyJN!j|CzR%F?q`86r66W#RWq)+7yL?LCg*O`y+f8iRX71{X_TRXYUd*5v_zBt~XgK z>`W8qQGK@GM#nlogu&qAJOu_dIC}K#hNs&;$=JiUN%j-(zE=A>T8ioFwkgv>#s}oY zVw2G8YCfrKD0x=6sBqPukT;Wg##Zv(h3Ovl_&dYP$79%b9`^JS4T-dCpHRO|{y{0q zkV+}QQP!)_8F>~MP_b1=jYiY>-FZUc-eGO=nVC0U`9mu5nEw(ZEXT2iR|1vOMOF0d z9Qpg8X=xE!g?6)}U6o%dz#~A;N{C(5PkBF_!=kqnrN`q1Ye*7CpT)*%SKk&IQ#FW> z@KTCwmYut2gBCaExic^&Mm1=y5W_D&zu%_oqunB(kNA}2`xptv4ppjoOm{3=MK!Ja zu0r!`_?V`QX?d)Aue}~rFvG{|dvz^;smhy-6`Cdh6AFN;rIInRbhY$yaB(%WFrpCr z>o-vkGh7zPdrYX}B_LqS4BfQH9KMnXh^hQ))1fr2K3g2w-d zM+uAhbTz&((=u~8H`o30Ts791k5&^7+W0PM51J4PKt{s&J5w?b1L%ngMPO5GKzG$h zZ-w5^-rU7ItDbi(oK-xQWApy`X_Lz!eY4JPhE`&xSGd}Nq1c^N$n#_paBR-|elKN6 zINI`p=hQ|~Ks4LDx!Q!I$~duxVSKZfo^ZisuaS_&Fn;>SlNv|A$MBdbnMxypM1PT_ zM6CHZx`%kK=qddV>hC1WEjsNVHKGDFnX{bevMg43JH)qkZbe;X2%~=`zTu&DS2x6s zrPgz}2%TZK?{zD`%XwLL_Vo277kTJF+Rvqt?${UcUJ~z@T(SD;_{BbZU)V-c@b&~| z+ej7}7o;vG4p^?4xc1#u(BLkh2Ty&5ifC_SJ^1EEg01xcJxHjWM!y9cP_w;=*qeH5 z{jF{{0)*Kx41UTh%ORZ|d}Ny8Us_mqh;)&@`x#wK6uy>ANU)Z-Iq-ATXndL0B)la{ z)bzX!I>TF{pzC0dUiAfjifmT(PjDIn%ZGgJs_2guORoofR&FIjaE0(*h|>;9t-v&? z2|CKrCCmD;#R1cl(4Sr>-|?Y3P=36!d2=~{B zBE0)*o>%NR^6J%_jY>E>MPH;e7M(OVqii8ln~tf;uNH$ zWj3FZmH$3&R&RswbveHJH*OM#Vc_6Ae*@?5TsapYOI`VwmL{pP!*&K@-mF(AKnENR z0NLrKPBT67Kl*Y}#nUfiG~*8X?e}VF{|0Fa2G!pXXQU8xbhZ$+`U~p+#JJiY7#IE@ zAe_>TWfBDtFnmn)Tabti@C%@F*J)0@tt;Tu{>OP zy)8nY+O%Nhx;s9nUv`-4j9PW9AXBA%JbLBGZyt#DQOxY7;1@ZR>dWGkVr~>uVXiAO zB`G6(Ggef}wWKh~o9haqWkStUna_zHn5!?l=Lw1X5Q(6&5@M;HqxfDsYHIFr-s;xu z`Z>%p3l}BDEh|&Y}ZH}NRD%A?+L7RG~?fn zT-Yjvz>LV&!)aV-FrOfNKlPLyO%sKxaOd^!bL?&9q+t0Jm>?&hnult0_i<6$OP9Vo zq7xQZn@f6!NGP~*)`eX6^}g7LDY;Z-Jm%^hk9Z7+Du$qiJo#i}r1|LEy2(|x0dK}7 zweNi2$zXs**-zt*7jIU=He76)xJaW*f*EKo->riX2GPG>RfOG3%UrWG9ZgbLbZm4~ zj4d&(j-nO|kUCi%ybDpo4_GQm9+0fT@TVb6j_R(RELnB)5{ z_fakFJl|dObj+YB;HsH35n_SqVct7Y&vCbNmZ{sm3cD25X)bm-oEB8FmGFFW*o}h{ z(_ai;C0;?!HTow2o`m~f0Zx?*Wa&m5yrVi}#IHPWxjNgf#OMAXo(E+4CTDiv;0KKa z2*kYZPRMtYQQ0-ArE#@1lQwgeU-};*>Ry;*`jVZ z3)t+xQR3|S;azOBFhXikvyMirE)c3OR*SuHp%y(-DfnKbVy3y?q(SfHoQYO-@Z;D3 ze!Am{9IXMq2b3>Uh7pf{&^C-t&2~u)H2lK%V)+lXT=7g6GNtOZ(?dVP^q9lh>(uFb zIbC`6P8O;^#vJqKQq2~o&6GNlJihTrB)wB4dXWgqC6@DqWsgO+Mmdmh<9*qB*hq-} zdW?`@*U@A5em7$!c;a5z+Vx}NIHQkeHzLTE_~hQ%D|3O^kgOXCga6vsI=o>>UtWom zuafL=;n`giz3m%uM<%Y;iI-Z{i#91=k6C?|>W?Zb)xBDre?lveOg$Ty?DlNtDD@Qw3d@%`isWM8CWwYNhb zI&D?mNMp^NK=WZQ#RJ(rRZgVj>n~PVh(#;~u98$zrM0kYi4CM>Gz=inwsQZsV4WcR zFTt9F6a(n%txM9b)qvSb2tKWW{>*s6Iu$cc(T)4nYGzb`FNkNgsNM^9W~wSg#N((f zaesXT>^{OX!N4MGu7md?%Y29yle4XawNF*L4r&X|{Xwmj55YqnfkAF>eB}K5cdLiT zu5Z0D*n!TXg56Ih$-5j!^-PX7rztV3Ps(zO<(pQUfsR@JFC$1^Hr7>pA_j16GrwaO z>8KSSIsEl{G>ix~Atl3VD15~ujs9y3miVm>pESpM`7fDHL`Ld{XLdN(JMQ#k4*9*t z5!_QvZM#KxWfmCY&TT~gFKJAT_@6vzhwYHd!7T^9QxA?OtBK$_A6oq69<0ISSjMHk z8zcHaRI2Py=ql8k1Hb*og#I6d7cdBLn zk9CQJq&UkvBNH1V3p2>-#MI3A--3Cf(Z2+91x*Yfl02j)a{sOp-RJ>*=+2DlP9*ul zQkpw~RO9O~UmAIK=kuJNA<|L?0h{M9=dsHUOroAnf=F*kv-NExZ2dxHE`!2jDWVeB z$908zyg1s}B-~;l-`ABix~*UJLX()KLY3y|F*LbCrakrZ6(;R0tD1T@1MTB|Qm{$2 z<*r$sD^|jqmCuL0(8F;GWD-?F`*)G}kiG1-wnM-uI@;$AOKQBlAN{ z*``StravnvoxTFE5q!S;QE!4*Gl&YF?FlGn#=g|%VA^)69Sx}J{QUj$Qq~ zAt6T!AFj)FFBL8ewrlyRxDG|vf>`sXEe*WJ*a=wPc^bxQP=~!^NuhvRDL@r2pX7gH zW|(0>W%g*%mY@GkbW*;$sJqM3d<*x7L?ot;B=dgg1VM&Z;_Q#>Zuf1_5A&r$ zH=!|^-CP>fY-bpUxM{3qe}2kz?e@EXNqCFnL>SM5#E8=t7CXfYZ8YSdFl)_l%r$D) zSx>*Sn@X8=(b{a1Ukd@$<-b0)S6bVX8HK=BRpo;=Oy_I6nS_bCO_n3`-tfx1qKCgh zm}g1vO$wBoy!wO!GAH`bDZ-#mMtQufZP^y$^eN5;KAJ2;)FyKGK{UiR@qQf;%k!cX zcx0j1{8bsJjA3%${Xv!eOHMJU;>vHfx$ED8`R5iOdvvr$nBT{^Dx{}6`_;}5G5wAy zJs>;F4jaM$m-1kyS05UR60OB9gFCbS41qBQI(HwGt`U?#W1p~l9BwQgG215Uqf&ZQV zLgW68{w)Uu{bxTPAT;#fXmT>h7f3?<f{c9mU4nbBC*8kNJv7Enf8< zS7q#!hSS(N00|inpMa2vmX4l*k%^0&hnMd){~HO(w^GtFvZ`w88k$<~wM|UT%q=Xf ztX*8)+&w(KK70xc`W*ZvBs4ZIJ|QtFIVCkG_gh|mL19sGbxmzueM4hY^N+6XpFO>O z{R86@lT*_(vvc!n>l>R}+dI2^`)B7Dmsi&}w|Doy_4=*n-_xI({TID3A$mc>!ot8J z{MHK!+T*w4n6Pk^?C@A($_PeI*i;<;h&bXgU#q?&QFE%C;u<@TA>+|-tY^L$QD8H4mV|KtcXI7)(F}7|jV~9uyMI31tBO|NQ^T96+;k*^PC`8n6q2 zWQVlszGgJ*eFp;#9wodQ_oW(6{V%cvhPv&QXe0S{{7+=h+R81CFl~mE491g&l(Yv@ zxOWX@h@~6f&2E*YzevDZvi3rrmM4E`S2ZtDTrJjJfW?d%PplT6E9xcF9x9I9ro*Md zZ-`~}@t+}~%$Y~e(4ELBk)mC|Y+ec$S>zU`F}V7oIYAMcmeUly&qQAPw!=@tKt5e1 zEE)Z=KI-`ar`K7VF-Jm(RO#3FXN0dfK&`SQfb&mek9z5djv>1?_7NfL?3R!Ea>S!p z#j#MV2p@J?x!7usz<|tBi^%t=1Krcpg87pIFrYA(XbuL{Gr@rN-Lt0Yj0(eKuE)>~ zj~hYhv1^!N160(&tR}*(f)mJy!?UDsfqriEu@>ej{AzEy<@S+fYwkyf?Z}jJ7W2Y^ zLfnrmv+#WpyQPNb_jg)gz@psxba0+gDorhoBSI2kppI|wh+{ZYPD!ZY>>Po(g)BLL z&eIB!OnZrUv1Umff`JM>hrm{mYdcvPzo`~iSd+nC zx0~{&jXXsjUpV!*NG+KTg4)B$JMtN7q}gpPQ5WO6a!=xdgm&&G<-4=SZ5zs`4%b0B z=nZ#XhG1adW%lf*?I8G!JixCXt^fJgN`u2=RgX*5bxCoA*NB2F&-k`$g-GDq`V@^h zRJS2n8>pv@cAvbB#w1I-3L&s{+u-uhLgai9GA_l|)2O+!t+=Cw`nNh{8l3*mS8D8B zrboVhW|QHoeL<55-_AfQ##uX(U_eOq`5rfn^z&@00q3#lhJ&t}u@4CSKo6OBc62_k zsht%4t-(l=^L^Av)AzDF(D_L^(1q-<9^DDb{SzX{9)R?DsPMhM_Cl^zsY3Zi*G$V5}p$xJI+V#J<@$k zZb3U)U_ie)mjDbTW{c#%byCmPyHQ~>G!YqT6wWCY8^M@z<(u;QIlui1CC}sG`&JY>9gVhD?zXV)%)|LWuIGPoZN*Fum2%3Gr7d*`IXXIBtux zT74>plIV`dwtiXq`PEkY=Gq@Ga6XD?*DjOJtw(Tx>MRBm=@z!Gx^|}9aBUCOeSX&X z>r`PfaI31;h3fI|cHvmLY&M4KW#ibAU`SCTWHM`hQd5bGJ+`_EksZ*(4QIpEyCeGc z?r^CcbHpjU205;adHbm(-NfRmLTK8DeZ5Tlj84zirz&W0NiOr-z4wg5>4Wq%m%$PF zk+Kik4wsci)9tRoz}4iq&b;2d)#(WQ89j|=wgpeC9M?5-;jQjn$Yu+3A()}3?J(#{SajqAdRUT@I) z^TO%TH=Wij0TAC(xPY$^b753hCi%tk+h3RCIy70;QgNf>RaYX|yO}txi6WIUBpS1K zEJmX6tNf^uM~??yszI8BMYQg5dNT&C$K4uT!`cZv87=8sV4$m_)-zV>d1|4B#5YT% zQ)Ir7^%>uxB?45>-UyXd;|&Hn^z?$GxD*tnkBzIF$;=(~X+{ajm#@n}^hZUKOfs=J6`pydBq<;w;j}*pah)!Fte@b^7HNTQ}^;z-Gb5$tjBs za@!>8@n;=h-Bch{Pj=MvKJWCOS3T;~q(7j`-qWjccz%AShKVsApiEshIq&1}fX<}| zc=7r`{1!!y{OsVH)hjUIZC73H%g>^LO|JCfTQ2AsC^TTlrw3&u!&+~ zdT}xCFZUZ>JAcS~7T=Z~^d`yZ2;$6}@4a4WA#&LQ)m)Xb*sPUrW~n|;_bxrH%(aKj zcwAO!{cNUy#zp1>7}iS$ovfIN-+p{0^oD}@K(DswrC?Kmy1=tJOZ_Om0rFGkEGYkY z0Sw4jtsE#tbqSQ2Ha%F}XDhC-mBWA7Zd1~XlO3;Zs$hLdZJE2!q=HMc_38^~6ZE)53)#?#W7FJkgkEg$4eQg(rW#2Cn=q2^ z#UydwK|wOYSg1M}2rekh(;CyN&I$Ms&CF7lMr`ZVK5IS?<>L*}uOiQQQ9_d-z55xx(Y_ebBDh>^@W^tiYb5+}`n;SdD_z%l| zQqEGr)P0;*xCtH*aGJ=hlTx2{Z6nsMn~3O*bK-j&DHOgC#;!bqND`&JkyTlusLngJ z8<9I~ufDHSGe#FlMgOYBe#BXc{7Z?!+!6i~W;v*(_p-FVu4rT0jzzKuOG8xCaEB$b zvE&{MeBoL`IRpdqy!uiZEf&XfHQ^T7!Z}T^PaD&*bt4$&T$P-C_XhfE3bTdvSJCx5 zf_OaXY@`F7;r13I*|jp+rfF&)$mi(iTKrC;NjB{HqsnYbXRvm8IC|z1HX@Q&T@tp# z)f^YE(iHcY?~baFId7Xewucj|EQl+is5@|f+W6r#HBawM74TH=9W}h_lfw=|8HkB& zy(%v&NH`k9t)b{y^WPhmB_p(b9(8u^Jz*1WB4uWn>6$8BG>zRFKk_lyxlJOJWmXvB z2LnHbeb-*I)OsGhtRN>-8)(-bl1AEk`&N`XN_%^Vzc$0FrfK%Mv6?gw_=X>jAv>9$W&~jUSh9jO*ihFg>5Fg*D z?qzA^3ydO$h8B-2FhE^!!0j7VrBUPaQ{=OU@y!qX8C8dbjpk^CxNV~^zfP5=n=?dI z-)!4opeuGnwRwVp?-e9gc+JF?+V!~&@7gCr-=IhDc)CU4*sFIAnmS8y(+hrB#JNLYphMuv3w#-kYVf}CPrb_1(lfVwK+R!r79*BzP}B)KHuLn zt55Rl>kj|vyc&tvE2gUsc_3phfD-5SGFc8vqSV^QZL^!sV3*&ys+rH1rAYS^i24%G z*SVzXZ^q|M&p&nRB(3wCH%D?_Fk_~>;&eILuJDDSJsst85A#N}axDsf9R)4+&ph81 zmHFtb4Th-jop{)fAS6&c$1mBc#VX=mg$PE@6Z4XrH~W9hgiGYLCcXO2Tewg&Dv%XNTdbE)O{v6M5aOnVlZG^cTM|3S*?eMOA&wwzw%n{G1r zhN&xQ2bR*>Nz9&-hrW-tpXtLHuZqLglE!PA?4;7bfM9Sz1y4PNd zgQC-8N&EXqsy4py_*&`soQy+B7ZWq@hLPF;y_DV*0$Ym-5!v$<%v%IaxstF(`_hg2 z#I11U(n#bY8vl=t1Y`*Z#I*XK?o@Pj-nby=joXWg^+@lWKH89QTh}tx)){!-=v$0> zo7FeQF26?+l*q-9f&CQ8)a?un>~QZ1)17jEn{IaxD=Jg67>;bL;Fvrr zzqHfV(WyO`*IH~s3ooRO$x_xIMn0_|{`uIP_9Itus7g{ZbXDdvT7vKtA4Mdy>Q{lV z-&V@S+slb=ltX@lZ&h8ablB9R_5uI+QziM{kuvuo*2YjKZLd-~^3b$dJx|D%V&t-6 z-wSjT{g+R3G*_Hq8nW}G68b!ep3^8oZ(RG}x6Va7Nythf8;fWBm}bWGHrhG~zMtoU z0pyKKg{pmy7M@@4&J_`q_44Yo3Jk3F$CuVtUaQA=lNZ$4sY`aa%^|a5PUUJ0{qxTGw#ah&@j0YI7{ON%{ceZsW*C5cm<0!I(dtfxl&{H5(I>%Vp z;d&`TWb?{;#pwA*{^0 zeecGe4~EYeL6ILyYu>}(wTxq#*{!h!vkN0cTS_+?fDvKSXU-iTpYHx?gS!8nGhzhA zC2rwBUzm!^3{ka!nALlEenJ0R6P;XAWZ};!kwroay0FvK_^8%9Ii}K1h}oQZY`H{(pH+m z07XmHYCGSpU7@Ez_w|RFAlIxKt5jDcFRm3U&GXHOxs>|8pOLs~tI#j_HEsgh>8(>c z7CLIVqj(3-uR*y?8v-?B2-y{CXJ+vqf`i?3%-J3e2y=e8y?#sLePO`8vez6H;L~xK zhLZ9;lf`+2QDZk3ZemHkEMzlP@I3d{DQ=oa?irDO;ArtikHgoRoOi_5f?!SPiCOXa zL3FazxNhp(1*$10>l{1@G&=K@@Ko1cJ6Fo%$`O2ZeGiX4Ew9_C#!kbIdYo26TYIw5 zaHaTre@&7L$byg5aDS|(ph@E?uCNBHEs2@+J7b zW`|tS@50vxI0*YD(STRI(02%Jv_MVjjk%}8uM}>cL20Eu3^A5SWF1GUp5YS4@e6g2 z-wT?Vm#m&&*0#8f=ggNxv2B0Zpw4RbtIKi}W=4rW7nxjj00U75`X4UFTM)S~6SuU6 zZ9eTTuW0{L(B?H1+~tW2c!PdcpoDF@QWJJ1uGF;SyzC>>&>CVMXN`q|s*}k%Dmzc<^ixTjAt)!HGTCAMWj zrZ?n!HbZf*;WsBc;HYe{q@7^X=8pf2=MXq^vJVE7F0DYfp+V2go)nK2WzOi-hc%!x z+#rY*S@_QByX5B*b-err40KQXuKehL=|KSl4ojvDuUms5OOEnB)$awR1s+fCxG76} zD;R<-MY6`#laIYf9po1AKCK@r8jH2Bh5uJaIo*x7=4$jM9Vt|<%CmSD*g?u}J?eU(Q-qtgaIvnp)ijZ;TV zDm=9%$9G-4VY%2lAp{~C74uh>bEECTbIfkgMgF3htH{bUyto@+sm+j6%SBqXQp`&h zP}t-VldImZ;t7+QsONBa3kIZ?TAo@#vK0>A^;oKRxw{f>Gc3Qqja=zrHf)!y{7`k8v7S6>67ykI(3$cCnxS;z;q&kfz}&q zx~y;a2=!)*zUfQPXvTN7kL;ZXm*pK@_3Q-D$A0F$%Dc?OQlE~R(r)}N2z#LH zvw}RDHG`jj;6E|@(X2dIkYzqk^=$ChT-&_K)U9u#xffI@(3MPS_ndVKKNn8u&%nJL zy}b!tdmL?Ra|!oFXmg*B%)7>CztcHSt7#!?U!DpUZrZT}18;joAnW}DO`Weqn48wy zns!S#G)=J=gz9&oW+5AeE8N(b?>4UxG0nrPt{{{4J=s^1c0`q-!%Bfjii z1hgmg(l*T78pio8?UsdG5aQYlJ+NkMnYb@M2~28!?Q1f*!No}v;GQ;SN1IrPx`iyy zi2`;E&Z#^C;hS)uj)R zznlRBq>y=>#gV}&GsaP!mNRhimZ z(7yPxwszH~e}FUSqB;+; z@byyGkNR-S4>?&s;s&Cgy$YVr8TO1;^ibb6tUPM%2r-0`Qz_FO%^rnotR#>>UMM|m zDsTRTEbJzp?{IV#44f6kBp63{!(d(qt4-RXCYbe%6zLyw;v-u$ozpT$?0gRg(ZB4VAuLp zq`Jj0jgj4p&pRp)Z&#M=7P8hyFH3s`Of8; zs44eZr(fGkC+14t{ zvM}d5tr)T+d)Lu)!Mkx=6>hPxoZ(b*clXq@Snu}?%6s=f(y?qXG$B09K>t#NQ*wfw zHe=8La_i)SZm;0M0L+u-vyj>lmc@K7Z~+Eh zcAP=9pxP&A|67m6@Vw+d?7G}(taTLmB{q)_(4_(Nv8SQ9T2dl{MYj$OnSwjKtHwGckC_r54q>L z15poQcdCWi@LtMbV3Z3Cv`dnyfi8wcPGXdD{87)1M|{4GKIBBvvE6NF-SicViDKSi zf<|fn5R@?ZLr_Iowu}0l3Jhe*fB~OSgMY|={1+p);eyD}nA+Jx`iIu~lQ#WL`~0TuY~3JZ`y>6<5Y^0HT@_N&Kr#s+1;_vjz&n5f zFb3QJE5H`w%4dO;_7IK>paQ8E|39=R`lJ0jNGoGVD=WYR(n11o0PFyxKiUJo{{x5& zB>iJz$&1riAGe}^ypo{7IDIEWV?9sw2+ z5(B{XN9Y11asd_z?$6r4g)UISV_~yXiNzq`8u{Z;bBHUes5-^salWZqgS3L2Hh`Q< z_M&Ui|8SY@MAY#dxMC;uw&fAZ0X<}qr)-{vuj zBCEs$kOHT8Ml@;e=eOvQHiU*(ubAnzZL7;RH7Qy$nNn91dqd>*Fd3YQ%$jp~X)jYAQt;X0zG~gJ!pH4UygvMAxv+ zqAZvcn2T7Pkv*-|%uy54Q!;XDhd4RcW{k3`G`_e`R$XS>`?}n%eJ|h% zYS5}3p%$#aO!9?&KDyH4j?kV9kI`kxE4!gec)5wn?8O!_85dQ#V9)tId+Lgzj^H?Y zNn(F7Z}KyxVCU#a^Q}Hv-D;RHMJ!+DmhP)e2bA2CH35=i>0-{aZ|l|SKCBS0!DDhF zr`;!&anD#3Z*M(CF@Cs2iJJ6_ugIJvL5`Y7?tCJReP#MHI*k*apD$#m?80ve(WOmBy@HC^Cve%a~7}p0IyN(~PnENM``q~qG8S`ZQ znPz)`1z*P9h8B#iKH)r5Rge28zH}-Y$SJx-ZjaAK2hW8-|KHC#bdLN>(S+R37(js6 z`jy98Y zmSgTPF0AV`kfa{#l*X%4nKfStg|xfzkAd2W-aQbgDv4XSF}g=Iq64<(G4GN%;Bm zqWOs9bS8b0?$QQa_vM?hp}pJa*llWo`()Hm}PSk=aRcdldj0 z(Y$>9E-4{v(DZ0Lry*^PL{=u>Iw+=aw!X4+bN9`6t$TK@{VH3(;C?eta3b5a zsM&$Yn4fIte)1tsPF>-D= zb+E!Q=Rb8wPU9d6Y*TU_mT=(Ki~dr^OG~gkQ*-qwYcep_Dm!vY>T`6?LYIjC(xC=< zc6f7(1B`fxM~P9@c&vM~yg4f9cI0bx>r5Nuq@g@L#RLB8u7Q5Ov{NsQ8iZ^}vqB@O zeI;3Q-C<*#>Gpl-((C5izSDtGL77}+Oo5_fGA>fbJTn>(06uG-!F(+;rG7q_ME8#`3G=?S)#}M zp~bM_OS=}HZfU6-u8c+VIjSgwK2^{&;$uI~wK4JX&(MLcx9fE@{>tY$1ZNCJl1qgz zP*^Jp9@vyF&0G%Ne&5S2)$-xHJu*@DcV$r{Y@58bIl3|r(?5C)9Nog6Q=u^Qal-zm z;A1)0Lk5S0&>eO0SNO=!Lyib?&TsqMYYjeHRCQ;FdHbg4H^4$2nF|J){u-za%amGc zL0hO7347k6y-ltBMu^!l7xO)!_)B^nchu;YuT8$V7FpxACKr#J-F6>{M)3?Rb};f8 z5T;MQp!za?p?@h+MwjRFqR3@<5yqPmzZBmiTsYTz_>~8#O~T;BF;x0>)U9f*WeXyr z6>P7wRwi!TzA&25q@Wxud6wEy8`~W|5j~|zS{o1M&B2vNIdCFZpBY`nb!DR{=FO{J`E>Z2 z&SO4P%_3?`b((Xz(4_eRX0(w(_j_sySS)DeRo!I_ux!1=i@uNP2~`-QExLv#9}K{W zED2xdZ}BoL+ahtE+vtkLtDzBk!xs!UkID7o;hWF-dn>YmjdMjjsZ6C5F^vzerh(T! zA2C$|QPU@66d#!NOMB;QwGH;DCe~sI2EJU{CqTDI?t7wL*Vn`AW=-FX@pQw1CaS4) zu-c-}|_)2Z)P;Ury&EHKH)&FF&ihi4{_eX%gI|VEu9wI;r5uQpP>3Z1U`PLmI^agUa z@}_#x66*I!+pjghq4{@?*f11OgzZG<+MvxsseI|C85dtm_c~S#oxEyDqkZ}zSsauC z1>_{5jWVF`O9%{yc7%|<%&J#u>>Q>P~xNc zBaQS0w~X_WUNlcH$iY6_mr-U^1;L4w(dNRr;qdKNr%PbXkKl9yb(l9fm6>FM+cfem zHOEZ^zeI?2l0)j{rr%UMjiJn)#mn|q9?v2q9`eGvrg%k{37Xn$qA73t;kIxKK6L-| z-;o&@i`iKx9cBZ)Q)%CO+ zC69`|kUO4vL{$gwK=#+d)+c#}kPfmy^#u$t zJdcOkz4X|z{Fyv4eL$vkM?q5{lv6UldjAS9>DPhF2G1vurk1O+#jUt#mkTixF{5;B z-Uup6Xej;B{s1zWb$yr?x*LJnlF89;Z}zO&B}ujF!q!|!T- zi0|Moq%v8rV`&Hl-z&NIG*CcIfCKTx!k#FMUWuFwk)`C$%XPm~NpIUCbAPetw4@Q= zRT2f_E4#Ljs5TE|A{#5^!R|gtQM@eo9p3+vw-BtZ*7I0!l9u*@awJpO>$RV>j~31r zwGid}1;7`1?zc)2Med;8C+GfMBaiS$B)TbzD_`2(bHZq^guS(NZ5jCsGTj`jT*O`e z)|cP-&kEk!#GV%n1t7LOuJX#r>FuGn(97oE5|GB+z3Bg^Pz$k?tiLT~gx&uKP&@Mx z1IRW*5_j8tah>12H;5ovP-9Q4IVDL%+;tN^ggkTQq*Q7o0gdpQtsk}2*3a{e_Q}56 z?6G19aT^Lj5G@uDKJKAl6d(}zw)~NORy9hxrKgf&T(cYn@%8y8;BTJpLF7_(2H0~qubDYv7V!#PVJJ#-J=9mlmouo2yl4GGZi>C1`5~h*y8bi;*@9ZVK6WI_fq!nYC%SV@_A~4Gi4!oVIh2?bF<#c4%kdm6$q|iE}L!V%Wla(lreQB-9k-+0oXPx# literal 6927 zcmb`Mbx<7J_NZqD26rdHEqJitB)9|#F2QAR7?=RT37SEJ6M_xyK6r4~-~@*t!8O4N zFX#O3edoM-uTI^1b^EXG{$uy9y}xg*wO6MCb5O-EktKwvfU~wMmYo3LfW_#hlLApF zJlM6vT;F?3-q!y(73wE7=zCz;oKKtjqH3|Wf z!*M`VP;3-cCdin{x3#Uz#Mp8sbtW#;#$UsI&n0*%l4zx z*Pol+`*t^p!WXT*Rsy~=Qblee(#x8Lj%_CzCS0G;dq@jhD%NkaJkU39U9FOyBQTZn z8Yaz7mbues?-GNuY$uFHgKb4l=YwGALQvy4iX`-?%|+%<07c{v`Pp zV!>?%c@CFHB_;#`(7+&RB4Qc<7ACkBLE_vBA#|o+6w-O)1f?TjA|;U zjmi^{DJYg9kq!JV49!;W93`tYdaJQ|3b#ik_&p8-h!O~*0fNZifkCf#@qVFUV`8AA zfWV|!m>Ae#G87;P03bq#D5xs{fIv(FNWBAk_DW)nfG{A-y6EMh#1Y9*z&;NO36eVi znJ{z?Kx};&+;?`3c&S5RqU86=n=yT^b~+qHg-Y;yq~DW%Wo#z*$E4L+eeVNupkLU- z@gIx|Om#K*uzneZ5~e6iqL3f!Z^~_V@B)lD@)}WJS)V7%CDhmD%X`w6RQT8!U3QxL z2;dNAV(t#-gsJyDf)kOS(DI?+u~1&SZ3hERU7$ek`X{dHLSl>e7pu&LvIX_=X{iyO7iH^$^Ykvzcbs-3!|N5sE>amX8TAGb*KhiqT%J+M!t+$8%wi#( zdJlb8jkYr_!*SeKBv(qYy|~qs8FFZ7<6SST{6zXFZLmBD2U2`;=LPsJ54i|cPb_Ak z+HYgpwPikd^TX%7yz&flh3WudRepgwfi~|6)Pj!q#nf`Ab*kbOJoWKsPo!Q0 z32eVl&Ukmg>Wy*37jj0&>wSnLOoj=0NkO9{$03p&PF-PHwdHaOY({Y-5tn&#NG3O1 zh#~~$WbW)tCvN*cH zy)WE$ow>)rO^|py0Aj|J^D;3}K;g^w%f4nK&6LvnFW`RwwTy@W&{*OeXWO-8WZg07 zQo%@#Z4tkhf71&fxn|!0Ht?Y}qlgqzDx< zXic-TbyeOShkAYUNErgx#rrfEBHwBAk8w&htGBf+;Fo^CInYLVM-(5r2=@VYrdk`A{{&(%oZ z7xak8v2jZU;T84SN5n!HOWtt5#9T)|Hg-nOnr06hqVQOb+g|8eQNc4HTJ$!yK@q9)@H@znymgFH4+UuG;N{h-6K=12!CM> z&O1jp(H}oB1}yLrPwBC=v%zr{PL3}|5@gU@U0lW|fVTGmxYdaj0JKUL9B(rB;~FoU z(Yp{Rj&QAWTc+y_`Pt2n?1m$xl~v6rL?{$k;)nW(Mdn+*iOy7=UukU^vf%vtBg!Mt z)QekcRPwcmXYIxB#jPJD7b+~Cv8`n9QceuqzoOG1F?+^FoBP(;Rd<89X|lomWef7@ zPqf#>dVR1oO%bxl^0&UInrl1?suNsB_+HjLU5v2JYdqwu1{|512@S%`` zP*BJ~{|cmkgtvd=mv08hWX63Lg=$V-6r?H2L%>&`$qZ9C24tC^s*QZ>IN#{ZydkqY zL)7yqkqGrMh&Go`qQ>}~Yei8QqE(f8&i zL|YyDW9_4tMQ7&Wg!GcPa@K(=S@xW)%k(Ox;@Hz`b3`ly zi70UrC$-->?`yR*n%HXwPLvpMiNR!{!h(wRgK1%$X?M+*Ad9vY$6xk5LKHRUm~I~R zt9i?_$J0j{kM2^&jtBAWoPwPdo4+jEJ`lz*oypK6G!P1Tig-CY*qn?)JZ*wLaz&A4l^1X#W(T@dizshp5ARQ?)n6u%6swe;ujzG=5mwCaV!Csup7nRNk3qh! zIa`GXfaAa6I1rYT4%$$ES3=H-#ebt*3oAeZd%6b)&>TW&aP?u+=!Y_3Q|K8*%`f_I z4TYITubD3p`Oz@qI-|Aob*)vA6Rpn%iM^OdGim{gT)f%~oS))t#Vo0+uSF&)`FS15 zqDuf!S={Gbi$2k%sz7U0MMu-(me6x%cTY%1LEi%r-~ z{7}SK@TDpXA#WwQSNew2TqEy&MSvWVvWW)`;4zrE4pF1uHu;ersdcGyDfDC0uIY*Bc9!wujpjeA6GggtEGO_zbI;B=Q^0p zck%ViVlIvXVcFG~<+nHEW|@gNeh%&6T#1&AaDG-~ZEF)Qs04iBCDd(SG%sYxJJ<_1 zTg_!C#ESP1o-8sg9&!IBMqkwM?N!KBQP7PL_7&k(-{z@`0==wjcHT&fkR*g!jXkFbKsZ4Jb%WeFnUiqU7PsJ+Pb|)ppmFl@}WoQSXjSc%9lvOUgzvK@Lxr8S~hLCyUbXk2C5J0m0 zWySwEKqqbmvG^|~h+lSqG%)s_s*x<_GM>;1g5MLpwC*%`=6Bv2|H)t1R9jqYO@bQY z18Yu{184t(3V|{NfYj-3=&VK**}JUHDh;m^_IZ_*gt@|B){eX|iDoWNO$qYwL08FA zwgUQ6WIZhCdS1aUsyz09(la*!T?6`sa*#4}I(;S4DLU0Yq5y}2C;uv6SAxTe(Xspx z@Ke5xVfP24K%(_1UVaH%bL_GQANu(blkDCT%g~`mRb= zc6+CfY~RYy7&pkPSShnMJ*Ydi2eWq^Zshw$#S!B^I2p#&SroK+EXlwsWmjXRjY25z z36YeP?~+o*Kg1F;MRBO?(jb$cTs)&#Kr}@vq94aU;>pw^1do^^#4)g*)EdT5+eg0G z2$#K&d|Zv_6%#s4uOaY1NPQcoPqlXRLzJSQ^wD*yToyxyu*s_u6Ey)7w_mD0$&K5L z7F^DY0_;Bi-juL3u0cgfizeFH51s5bY3{tbMPs~o@>o*Y5D(g|OqARxa&hOI zH|?V>mFJWNiQFcvm%GoHQH#zo%^sQ))&ky$Zi&`zpJdLKr>za`7L|y)_dvI@uRE)( zkG8}|Y-eb<&xWs=KMZ_(5C2xM%jZ{u`9@+%bxrfhnA6v}H&c&o2&=Pkb)la~_ZrUW zdTB5ck9XB}4)e!iotF zQ4T&^;um>709`TUc6m2bxy87-n${aI8R7S2zBl|ik^HkL0BSqg=dcuAvuxZjuj>8R zmRg^0Ko4A(RWX#pBu+1J`?S#Mz69FOh=yWmAD$O$OCqT>)B->E?cign_K;O|lHY~2 zDInf#GfK%ZB4U-A3Gd|-m%P|%f>$Onky^46>%=EEXzQU{SZJrNeXPufBm9C5>8}}w zV+;mAdejD3dpCY``_b(kjh`yu=Amvatt6B!KVS= za&*N}*cj{yj(bxzaqz7S4pdB8x2&CnG_c}R`i-B5S1q8yXImCj0(p+;BG>h9Rid6Z zwds?p^V*54bt_OOdqUFJuKkc@3aRJg5d?8}LCV=S^QOMWo;E$BQ=y~vN+{eURWYp` zX{+05N?j?H-n5NamY#R&7EtVo=g}lhO9jgLo(k)8xZ2a~Yoz-4>l(0*fC80%bJRQU z<4qj=oFb+q#(IP3M)F>e>#qsF3Nk z8v5w6y*S%Fe~xOY4fCW@lQ;nq3V>xn@ob~6azv#6A??rcRsFwfv10$9X)&7*$Yc{w zdJ~ipLHK?|6^MM`G18v=>gmR0lCw*GK%7vYjvD?imCV|lNPr2dx#bmA^BoBvX3 z2r33-vOd&fcF3bV^DX9sRMoz8e`o6WQX&5j4h*E? z-%}mdeR)XIFf3_L=;@QIxf1ESZ(*iM1Fc=J(n^#>f4$u$IViI{6OyO&mt2tkSa*l# zvC11HB6d%lU#{@u0hNTJWjnB<*9&f4=08j zmkiw{QvsVF(jT<&VV@PyKgEI^4Uoi*VHyR7jXf?G@k)@pmceUCww_HG84+I*g151+3Y zjegvm`ugT57~4tO|0{puD$rM9!<AHdc;><*%B} z_Ve%hSomF8w>K|)F5wy2Tb&?fy{u|hKC((r6TtZ{h7k*c@6Y!bPl{;bE0ea?^=h+^ zY0PVJ%M$OLhGZH2Nm5N}sqOYV(M8rJK7AVW@2vhPFL<{(%buEK(m%_VXGOBqoI<zAvwdZ&%SHdK``F+?F335X);yd#-}@;Km|Np1c|`2^Q`0zFm1kYU zX_6S(#e$1;stc4p<;G)n+FlJ5qRlU#!8zZxwbH^s{XsJA?-XUDouDCH8~oi8S+v1K9=Ya|B()FEVMCbFzFyZvgugh%2O++2=-IiTwE ziTyuwU{MQzSc?Wn5q~IPI^feA`YHIbv_y2P9e~Jw@~%%XmJqe95)?XeVzANnwPU&o zg!^ZUn*alFA+6Vd5r9Ds%W0l1mOcmXTx$`EysAHSZc-MeTL2d7=927wkkmOJNADY! zDNZcERIv(Ey21%=h3t|~XHThL{WLIL^3Z%GArZYemb$JNZ!mh_SmE}n_s-*UaIXT7 z`IzsZ^#kd3%YB?lKd@xVFf$sF4-=h!bkZ&l(C66t0l(K*Q(7FQLuPEop$j_jI|}2< zQRDlpWwrtaRVjaAgKcmgdqNlWv_| zK5Q`n2!#G%3A8TBy(nkru^s*u?$RLZj) zV&!2uIP@bjB7CFq8YESUl^nJ7x*p}|Jxf{VqAx;6uIFa=EJ5!qDM>CZx$f?>~v zOe9E0MTvJ1dLB9-X_m#Uc`gxThuQhGLRs1Dr^yFFXN!y=RLX$p6o1;0#+c>zNm?{H zKNc-gPw?*bd%imfSFhaCTTg`0Lg!E^#V)%rzg{ z=+BDxf!m?7{_b$IfkCQ1`Q8lFC@`qIo1HU+&eGQ0*#<%fwWfnOTf)3t-0YyvbPf=& zzgHy`J%DsfRe8Zdjw^lad{b+0B<~<~f2S@WlaCh*-}vbGq02imAe-KmIUp>i5U!0% z@%vLaV9+1`Sip~Q0KYGyzuG|mZlL!;0Ekay65sFrOU5*ViRnt_!-Tx>EVlrNg`C?g zHXZM;>p0R_(5G{|Xda#zO+Z{!Ri8XJAO@hf2-cAow>rfLd3v)j&k{opE}gC*_?}TI z89bX3i}I7|;F^V}APA*gcQ{?pCxDbuGKegx5S?j%JBPDP0B&y<)FHSxY_SZ9u1O7%+Lc+iL`*LV=NR5PNV>_WGb z17|&i>xDU0-YV_La3{99m%2AcIH)G_GnSDkMrsarU>S(EA_4lePc(J6sgvuV36fE4 z?-nYwJS@<++k>W0JgfujJ#ojNO#!dTa!Q)Hj@`}?#gaP?k^A~vGZyLeC^46Gl*YkP zi@IZUn?gekt5R1c(^~!Z@cTeXp)3F)5CDWL{kh7Re{5*p@9Glg?;B=#2|%|n|#HjfRYVkU=rRJZGOln|6i>s{WAan diff --git a/admin/docker_open-lumiera-buildenv.sh b/admin/docker_open-lumiera-buildenv.sh deleted file mode 100755 index 2c245c209..000000000 --- a/admin/docker_open-lumiera-buildenv.sh +++ /dev/null @@ -1,44 +0,0 @@ -#!/bin/sh -# -# docker_open-lumiera-buildenv.sh - launch Docker container with interactive build shell -# -# -#------------------------------------------------------Setup -# -# Working directory path on the host -WORKDIR_HOST="/home/$USER/devel/lumi" -# -# bind-mount of the working dir in the container -WORKDIR_GUEST="/lumi" -# -# Docker image-ID to launch -DOCKER_IMAGE="ubuntu:bionic" -# -# Script code to inject into interactive shell -COMMANDS=$(cat) <# his reservation. Prior to this meeting some people joined a brainstorming session and came up with _another design_([purple]#broken-URL `combo.png`#) compiled of several proposals, which could meet the acceptance of the core devs. At the same time, Raffa made an argument for conducting a public contest, similar to the one which gave us the name of Lumiera. The situation for Lumiera is somewhat special. Usually, the community builds when the product is already minimally usable; we can't have users for now, but we have a lot of prospective users. +This summer, one of the proposals by link:{imgg}/LumieraLogoLeonardoRiberio.2008.jpg[Leandro Ribeiro] gained some popularity and especially was embraced by two of the core devs, while the GUI core dev wasn't convinced and explained [purple]## his reservation. Prior to this meeting some people joined a brainstorming session and came up with _another design_([purple]#broken-URL `combo.png`#) compiled of several proposals, which could meet the acceptance of the core devs. At the same time, Raffa made an argument for conducting a public contest, similar to the one which gave us the name of Lumiera. The situation for Lumiera is somewhat special. Usually, the community builds when the product is already minimally usable; we can't have users for now, but we have a lot of prospective users. Thus, while basically it would be possible for the core devs to shorten the process by just picking a design which is acceptable for all, maybe after augmenting it a little, several of the arguments articulated this far are in favour of a more formal decision by a contest: diff --git a/doc/devel/meeting_summary/index.txt b/doc/devel/meeting_summary/index.txt index e237f1526..75b137845 100644 --- a/doc/devel/meeting_summary/index.txt +++ b/doc/devel/meeting_summary/index.txt @@ -11,6 +11,17 @@ spending time on the task of writing a summary. Anyone interested in Lumiera development is also encouraged to read mailing list archives and other documentation. +2024-2025 +--------- +All meetings were informal in style; usually _Ichthyo_ gave a summary +of recent achievements and explained some of the problems he was facing. +Usually this leads into a rather detailed and technical discussion. + +Since Spring 2005, _Wouter Verwijlen_ has regularly participated in +renewed discussions for a +of a renewed link:{ldoc}/design/workflow/Verwijlen/[Workflow Concept]. + + 8 May / 12 June 2024 -------------------- Discussion regarding the approach taken towards the next core topic, which diff --git a/doc/technical/build/BuildDroneDraft.txt b/doc/technical/build/BuildDroneDraft.txt deleted file mode 100644 index 84cb38fb0..000000000 --- a/doc/technical/build/BuildDroneDraft.txt +++ /dev/null @@ -1,200 +0,0 @@ -A Build Drone for Lumiera -========================= -:Author: Christian Thäter -:Date: 2008 - - -This is a brainstorming page for what a build system on the server would need. -First of all, it should be simple and extensible, preferably by simple shell -scripts (note that *anything* else is a subset of a shell script!). We should -use existing good ol' unix utilities when applicable (batch, mail,...). -In my opinion this all can be a lot shell code glued together. Things should be -isolated to single tasks and well refactored to make it maintainable. - -Lets go: - - -Whats needed? -------------- - - * A description/configuration what needs to be done, these may be recursive. - * a batch/scheduling system (batch) - * triggers/events which are passed along (initiate a build by a git commit, ...) - * actions to perform - * handlers for success and failure cases which act on the outcome of a action - (scp, mail, rsync, filters to produce asciidoc output...) - * maybe some dependency handing (only build lumiera after installing the recent nobug version successfully) - - -Top Down scratch ----------------- - -Lets say the configs are shell scripts. - -first a verbose one: - ------------------------------------------------------------- -cd project_dir -if git pull; then - # call handlers for success case - sendmail foo@bar.com <>,build_drone_report -} - -function GitPull() -{ - local dir="$1" - local repo="${2:-origin}" - local branch="${3:-master}" - ACTION="GitPull $*" - RESULT=FAILURE - cd "$dir" 2>&1 | AddToReport , return 1 - git pull "$repo" "$branch" 2>&1 | AddToReport , return 1 - RESULT=SUCCESS - return 0 -} - -function SendMail -{ - cat ,build_drone_mail <>,build_drone_mail - - for i in "$@"; do - sendmail "$i" <,build_drone_mail - done -} ------------------------------------------------------------- - - -now we can do following: (looks much nicer or?) - ------------------------------------------------------------- -if GitPull project_dir; then - SendMail foo@bar.com other@blah.net -else - SendMail boss@bar.com -fi ------------------------------------------------------------- - -the above snippet can be a file in some config dir and will be processed by sourcing it with proper setup -lets place it in /build_drone/project/10GitPull - ------------------------------------------------------------- -for i in "/build_drone/project/*"; do - ( - source "$i" - ) - CallTrigger -done ------------------------------------------------------------- - -... ok enough for now, whats needed is the CallTrigger implementation, -stopping processes waiting (either reading on a pipe or wait for signal (-CONT -for success, -TERM for failure)) - -setup of the function scriptlets: - for i in link:/usr/local/lib/BuildDrone/[]*; do source $i; done ... -and so on -.. - - -Conventions ------------ - -. one drone runs always in a well defined directory, if commands have to go into subdirs, use subshells (good idea anyways) -. all jobs need to run in serial order, nothing parallel. What the job then does itself (make -j3 ..) can be parallelized. -. we need a well defined environment and some file where it is registered ,bd_env or so -. all jobs append write their output to some well defined logfile (logfiles ..) -. the status must be recorded in a file too - -Example: - - ------------------------------------------------------------- -function BatchJob() -{ - batch <&log -echo $? >,bd_exitcode - -kill -CONT $$ -EOF - - # wait for signal - suspend - return $(<,bd_exitcode) -} ------------------------------------------------------------- - -This of course needs some more work, trap handlers for signals etc. I am not -sure if the idea with signals is good, maybe better use a pipe, lets see. - - - - -Actions and Handlers Brainstorming ----------------------------------- - -Ideas, not in order - -SendMail:: - send report as email -GitPull:: - updates a git checkout + - Split this in - * GitFetch - fetch from remote - * GitHasChanges - are there changes between HEAD and remote? - * GitCheckout - reset to the remote head and checkout -Bootstrap:: - autoreconf and configure -Make:: - runs 'make' -Check:: - runs 'make check' -Distcheck:: - runs 'make distcheck' -Doxygen:: - runs doxygen -StyleCheck:: - checks if files violate the style rules, something like: - 'astyle --style=gnu <$FILE.c | diff -u FILE.c - ...' -ToDos:: - greps for TODO (with some -A context) and produces a report - * beautify (asciidoc) reports - * publish reports, packages etc to the webserver (scp, rsync) - diff --git a/doc/technical/code/CodingGuidelines.txt b/doc/technical/code/CodingGuidelines.txt index ae82c5e85..c399c91ab 100644 --- a/doc/technical/code/CodingGuidelines.txt +++ b/doc/technical/code/CodingGuidelines.txt @@ -52,9 +52,11 @@ The Lumiera project uses GNU indentation style with slight adaptations. beyond just a short list of names -- especially when including initialisers -- they are preferably written on a separate line, directly above the argument list in parenthesis * the opening brace of namespaces is placed on the same line. Optionally, the namespace - body may be indented, as long as this helps underpinning the nesting structure. But - there is no need to use 3 indents on a 3 level nested namespace. One level is enough - to highlight the presence of a nesting. + body may be indented (by one half-indent), as long as this helps underpinning the + nesting structure. But there is no need to use three indents on a 3-level deep + nested namespace. One step is enough to highlight the presence of a nesting. + Effectively this implies that the majority of code is set apart from the + left border by two spaces. - the shorthand type names `uint`, `ulong`, `uchar`, `short`, `ushort`, `llong`, `ullong` are preferred, as it is clearer to write the fundamental type in a single word. Index @@ -71,12 +73,12 @@ The Lumiera project uses GNU indentation style with slight adaptations. to define a type alias for the _function signature_ first. - in a similar vein, we distinguish between an ```const object`'' which _is really in-itself_ unmodifiable, as opposed to _taking a const-reference,_ which is always spelled out - post-fix as `object const&`, or a constant-pointer spelled as `const*`. + post-fix as `SomeType const&`, or a constant-pointer spelled as `SomeType const*`. - we use the textual form of the boolean operators `and`, `or` and `not`, because this allows to make the code resemble complete meaningful sentences in human language. We _do use_ the »line noise« variant however for all low-level bit manipulation, `&`,`|`, `^`, sometimes also for `!` -- using those is taken as an indication of - entering the ``danger zone''... + having entered the ``danger zone''... Spelling diff --git a/doc/technical/code/c++11.txt b/doc/technical/code/c++11.txt index 50755c1ae..d6f59a47b 100644 --- a/doc/technical/code/c++11.txt +++ b/doc/technical/code/c++11.txt @@ -225,6 +225,11 @@ February 2020:: * still running into problems with perfect forwarding in combination with overload resolution; not clear if this is a shortcoming of current compilers, or the current shape of the language +May 2025:: + We did the big leap and are now on C\+\+23, with Debian/Trixie as the »reference system«. + The new language features, notably the **Concepts** will be adopted gradually and we + will certainly have to face some new challenges... + @@ -321,3 +326,4 @@ impose some challenging effort to retrofit existing structures. much cleaner and high-level than most ``mainstream'' usage of other common build systems out there.footnote:[ ``hello CMake'', ``hello Autotools'', anyone else? Meson, Ninja? Maven? should maybe consider a switch to WAF?] +NOTE: in May 2025, we achieved that switch and require now C\+\+23 and at least GCC-14. diff --git a/doc/technical/code/index.txt b/doc/technical/code/index.txt index 6e94c6321..30161021e 100644 --- a/doc/technical/code/index.txt +++ b/doc/technical/code/index.txt @@ -7,46 +7,53 @@ Code Base Organisation //Menu: put child GitBranching after LinkingStructure -This section of Lumiera's technical documentation deals with the code base as such, -not so much with the internals of the Lumiera application. It is targeted towards -people participating in Lumiera development. +This section of the Lumiera technical documentation deals with the code base itself, +and is less concerned with the internals of the Lumiera application. It is primarily +aimed at people who want to participate in Lumiera development. -The Lumiera source base is huge and expected to grow for some time to come. Just -judging by the _lines of code_, Lumiera can be considered as a *medium sized system*, -which gives us some hints towards the adequate practices, conventions and the -degree of formalism to apply. +The Lumiera source base is huge already, and expected to grow for some time to come. +Judging based on the _lines of code_ metric, Lumiera can be considered a +*medium sized system* -- which gives us some hints towards the adequate practices, +conventions and the degree of formalism to apply. Generally speaking, a *small system* doesn't exceed the mental capacity of a single -knowledgeable human. A single person can know everything and understand everything -in such a code base. Thus, any formalism and organisational overhead is detrimental; -we're best off doing away with ``Methods'' and just rely on taste and craftsmanship. +knowledgeable human person. A single developer can reasonably know everything and +understand everything in such a code base. Thus, any further formalism and organisational +overhead is detrimental; we're best off doing away with any kind of ``Method'' and just +rely on our taste and craftsmanship. -But there is a hard limit for this approach, kind of a _sonic wall_ -- usually somewhere -around a size of 60000 LoC. At that point, the adequate value system flips around as a -whole. Since beyond that point, no single person can understand and know everything about -such a system, _communication and understanding become the primary concerns_ of the -development process. Suddenly, we _do need_ some organisation, some rituals and -a methodical approach. Yet still we don't need a high degree of formalism, since -at least we can easily _know and recall everyone involved_. +Yet this approach reaches a hard limit, a kind of sonic barrier -- usually somewhere +at a size of about 60000 LoC. From this point on, the appropriate value system is +completely reversed: since no single person can _understand and know everything_ about +such a system, _communication and understanding become the primary concerns_ +of the development process. Suddenly, we _do need_ some organisation, some rituals +and a methodical approach. Yet still we don't need a high degree of formalism -- +as long as we can at least easily _know and recall everyone involved_. -To give a delineation to the other side, a constantly growing project might eventually +To create a distinction from the other side, a constantly growing project might eventually reach the point where the actual coding of new functionality makes up less than 25% -of the overall work required. More people might be involved than anyone can recall or -overlook reasonably. A code size of 1 Million LoC seems to exceed any kind of sufficiently +of the overall work required. More people might be involved than anyone can reasonably +recall or survey. A code size of 1 Million LoC seems to exceed any kind of sufficiently precise imagination. From that point on, a rigorously formalised organisation is vital to keep such a *large scale project* from floundering. -//// Conventions ----------- -_to be written_ +- link:/project/legal/legal.html[Lumiera is **Free Software**] (GPL-2+) +- link:CodingGuidelines.html[Lumiera code uses]: *GNU style*, 4-space indent, CamelCase and British spelling +- link:GitBranching.html[Branches and Releases] are organised according to *Git-flow* +//// Guidelines ---------- //// '''' +[TIP] +-- + * link:{ldoc}/devel/meeting_summary/index.html[Developers Meetings] and protocols * also see the link:/x/DesignProcess.html[Design Process] for ongoing discussions * see the link:/devs-vault/[Developers Vault] for frequently used developer's resources +-- diff --git a/doc/technical/infra/Release.txt b/doc/technical/infra/Release.txt index 2b884fe8c..1abf38dd2 100644 --- a/doc/technical/infra/Release.txt +++ b/doc/technical/infra/Release.txt @@ -1,17 +1,53 @@ Release preparation =================== :Author: Ichthyo -:Date: Nov 2015 +:Date: Nov 2025 -we have nothing to show and don't provide public releases yet -- +We have nothing to show and don't provide public releases yet -- but we ought to rehearse and practice the release process. This document contains some hints and a checklist of steps to perform for a proper release. +IMPORTANT: Lumiera uses link:{ldoc}/technical/code/GitBranching.html[Git-flow] + for the organisation of release branches and tags. Releases are still + considered ``experimental'' and happen infrequently, so that a full + automation of these steps was not yet considered. So please be + sure to adhere to the established conventions. + + Steps to perform for a release ------------------------------ - . release prep: clean-up obsolete information + . Pre-Release _»convergence phase«_ + + - care for code stability and refrain from breaking changes + - verify that the _current version number_ is already set to + the version number expected for the upcoming release, yet + decorated with the `~dev` suffix -- if it turns out that + the upcoming release shall make a _major version bump,_ + then the expected version must be set *now*. Once + the release branch has been forked, the version + must not be changed any more. + + . Release cut + + - create the _Release Branch_ with name `rel/#.#.#` + - after that fork, immediately perform the *version bump* + on branch `integration` ++ +-- +** use the Script: `admin/buildVersion --bump=maj|min|rev --suffix=dev` +** typical usage +---- +admin/setVersion `admin/buildVersion.py --bump -s dev` +---- +-- ++ +[IMPORTANT] +what you set here *must* be the next version _after the release_ + + + . Release preparation: clean-up obsolete information - Debian package descriptions - Build-Tutorial @@ -21,55 +57,81 @@ Steps to perform for a release * contributing - technical/build/Dependencies + - check and update *Release-Notes* - . release prep: bump version number + * check that 'README' is up-to-date + * add a new summary entry into 'NEWS' + * check the 'AUTHORS' info - - `admin/scons/Setup.py` - - `data/config/setup.ini` - - `doc/devel/Doxyfile` - - `doc/devel/Doxyfile.browse` + ** ensure that the copyright time span + mentioned for each relevant contributor + is correct and possibly spans the current year + ** it is _crucial_ (legally relevant) that at least + the person preparing the release and thus acting as + publisher is mentioned here with the _current year_ + ** ensure that a correct summary is presented in the "About" + dialog of the GTK-UI. The necessary config is currently (2025) + maintained in the file 'setup.ini' (the info displayed here + should be the list of all _significant contributors_ and + cover the whole time span from 2007 until _NOW_) - . perform a back-merge from the release branch. + - It is relevant not to loose any bugfixes. Especially verify + * check that the 'LICENSE' file mentions the core authors, + again with the correct copyright time span - - that all ongoing fixes from DEBs and other build activities - are properly represented as patches and committed to the release branch - - that adjustments to platform dependencies are picked up adequately + . Test phase - . perform the *Release-commit*: - it should mention the kind of the release and the version number. - Typically, with this commit, you'll update some top level stuff in the - source tree, like + - even while we have automated tests, be sure at least to do + some ``smoke test''. Ideally have _someone else_ use the new + version on a real-world project. + - depending on the circumstances, possibly set a _release candidate_ version, + + using a `--suffix=rc.#` - - `README` - - `AUTHORS` - - * also in the ``about'' box in the GTK-UI - * see `setup.ini` + . Publish the Release - - check the `LICENSE` file and add new license - declarations and notes, clean obsolete info here. + - merge the release branch into `master` + - set the version again, this time without any `--suffix` + - amend the merge commit to _include that final version_ + - set the *Release Tag* in accordance with the + link:{ldoc}/devel/rfc/VersionNumberScheme.html[Version-Number scheme]. + - fast forward also the _release branch_ to sit at that tag + - *publish* by pushing into git://git/lumiera/org/LUMIERA - . update the *release branch*: ``upgrade current release to ##.##'' + - Make sure the release branch now really reflects current master, maybe - with the omission of some stuff to be kept out of the packages. - Set the *release tag* + ** the latest state of `master` + ** the release tag - . packaging... + . Back-Merge: + + **never loose any release work** - - merge release -> deb + - `git checkout integration` + - `git merge rel/#.#.#` + - work through possible merge conflicts and resolve them + - conflicts on the version number *must* be resolved in favour + of the _next version number_ -- you can perform that as an + extra step, _after the merge_ is otherwise complete: + `admin/buildVersion --bump ... --suffix=dev` (and then + amend the merge!) + - *delete* the release-branch + - push this delete to the public repos, incl the main repo! + + . Packaging... + + - merge release-tag -> branch `deb` - verify the package description - - have a look at manpages and similar packaging documents - - update `debian/control` to reflect current version dependencies - - have a look into `debian/rules` (e.g. build flags and similar) + - have a look at manpages and similar packaging documents; + + notably look into 'debian/README.Debian', since we deliver + that instead of 'README' for the Debian users, since they + do not need instructions how to build the software... + - update 'debian/control' to reflect current version dependencies + - have a look into 'debian/rules' (e.g. build flags and similar) + - update 'debian/copyright' to reflect authors and copyright! - . delivery + . Delivery - use whatever infrastructure is available to build packages. - - verify packages can be installed on a pristine VM + - verify packages can be installed on a pristine VM / Container - upload packages to debian depot or commit them to PPAs - clean-up and discard obsoleted old distributions and packages - . close the **release ticket** + . Close the **Release Ticket** diff --git a/doc/technical/infra/index.txt b/doc/technical/infra/index.txt index a47abbf95..1dc7c3670 100644 --- a/doc/technical/infra/index.txt +++ b/doc/technical/infra/index.txt @@ -1,12 +1,18 @@ Infrastructure ============== +// Menu : prepend child Release +// Menu : prepend child MenuGen +// Menu : prepend child Webserver +// Menu : prepend child TestSupport +// Menu : prepend child debianDepot + Various details, documentation and other pieces of information regarding the infrastructure of the Lumiera project. This includes the infrastructure used for building and maintaining documentation and website. - * see link:../build/index.html[separate page for the Buildsystem] + * see link:{ldoc}/technical/build/index.html[separate page for the Buildsystem] * generating the link:MenuGen.html[navigation menu] for the website * how to use the link:rfcsh.html[rfc.sh] script for maintaining RFC's @@ -18,14 +24,27 @@ Other tools in the ./admin folder There are various other small tools and scripts in the admin folder which are not yet fully documented (Read the Source!). -.headercheck -This is a small tool which checks that all headers are sufficiently standalone -and include anything they need. In future we might extend this to find out -bogus includes by predefining (-D) headerguards they include, effectively -disableing this include for a test. -.render_icon.py -used by the buildsystem to translate svg icons to bitmaps (png) +.buildVersion.py +Uses some Git magic to figure out the current version number +based on the HEAD revision. In addition, it allows to bump select +components of this version number, and to append a decoration suffix. +We use the link:{ldoc}/technical/code/GitBranching.html[Git-flow] +branching structure, and thus this script is typically used to +generate an input for the setVersion script, +immediately after forking off a _Release branch_. + +.setVersion +This shell script uses `sed` to update the current Lumiera version number. +It contains hard coded knowledge of all relevant locations in the code base +where this version number is embedded and must be updated. + +.rfc.sh +This shell script (written by Cehteh) was used in the early days of Lumiera +to create, update and manage the link:{ldoc}/devel/design_process.html[»RfC« entries] +for the _Lumiera Design Process_. While this formal documentation of design decisions +is still considered relevant, this formalised process is suspended, as long as _Ichthyo_ +is working basically alone on the project. .treeinfo.sh Generates a report about the projects directory structure by parsing the @@ -39,9 +58,6 @@ more details. A directory containing example git hooks for signing and pushing on commit. Only use them when you know what you are doing. -.lumiera_c_skeleton -A script which instantiates a new pair of .c/.h files. - .vg-run.sh convenience wrapper script to run an executable with valgrind using "typical options"; output goes to a logfile, which is @@ -51,9 +67,6 @@ A valgrind suppression file is generated automatically, in case there is an executable "vgsuppression" located in the same directory as the target executable. -.gnu-indent -call the "indent" tool with parameters suitable for our (GNU derrived) coding style - .testrunner Script driving make and running a test, possibly under valgrind. Works only for autotools build. diff --git a/doc/user/intro/intro.txt b/doc/user/intro/intro.txt index b193a8f7c..5c1e5bdc2 100755 --- a/doc/user/intro/intro.txt +++ b/doc/user/intro/intro.txt @@ -2,6 +2,7 @@ Lumiera (as seen) from Outer Space ================================== :Author: Lumiera_Core_Developers :Date: 2012 / 2025 +:webidx: :toc: ****************************************************************************** diff --git a/doc/user/tutorials/building.txt b/doc/user/tutorials/building.txt index 5323570eb..3638e73b1 100644 --- a/doc/user/tutorials/building.txt +++ b/doc/user/tutorials/building.txt @@ -220,7 +220,8 @@ scons -j# The build process will take some time, so sit back and relax. You can use for `#` (at least) the number of cores available on your system to speed up the build -- but it will take several minutes even for a debug -build and significantly more for an optimised release build (-> see `scons -h`) +build and significantly more for an optimised release build + +(-> see `scons -h` for build options you can change) And if you feel like waiting even more, you might build and run the test suite by issuing `scons -j# check`... diff --git a/doc/user/tutorials/contributing.txt b/doc/user/tutorials/contributing.txt index 440733825..aa53825db 100644 --- a/doc/user/tutorials/contributing.txt +++ b/doc/user/tutorials/contributing.txt @@ -25,7 +25,7 @@ require considerable experience, some sections require less experience whereas certain aspects might be ideal to new programmers. Thus we attempt here to describe a number of areas in the project to assist you in selecting an area in which you might like to make a contribution. -Of course, you are more than welcome--and even encouraged--to select other areas +Of course, you are more than welcome -- and even encouraged -- to select other areas in Lumiera towards which you would like to contribute. @@ -34,9 +34,10 @@ How to contribute to Lumiera Git: Essentials for Lumiera ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -All files in the Lumiera project are managed by *Git*, the distributed sourcecode -management software. Although Git was primarily brought to life to manage source -code, it plays a fundamental role in the Lumiera project. It is central to +image:{img}/git.png[title="Git"] All files in the Lumiera project are managed by +https://git-scm.com/[Git], the distributed sourcecode management software. +Although Git was primarily brought to life to manage source code, +it plays a fundamental role in the Lumiera project. It is central to communication and contribution in the project. If you'd like to contribute to Lumiera, you will have to acquire some understanding of Git at some stage or other. Please note, this is not the only way to contribute to Lumiera, you can @@ -260,20 +261,20 @@ fact, many user interfaces should be possible. - the stylesheet has been roughly ported to GTK-3, but needs a lot more polishing - we urgently need conceptual (non-coding) contributions - * work out a coherent UI handling concept, in accordance with model and core - * we need a concept for key bindings and focus - * we need a concept for integration with control surfaces - * we need a concept for pen based handling + * work out a + http://localhost:8888/documentation/design/workflow/Verwijlen/index.html[coherent UI handling concept] + + ** we need a concept for key bindings and focus + ** we need a concept for integration with control surfaces + ** we need a concept for pen based handling Steam Layer:: - external connection systems - * investigate good ways to output video, both in-window and full screen. - Especially, the integration is what counts: it should be a well maintained - library, and play well with our intended framework and memory management. * expand on the work done for ALSA and Jack audio. - * expand on the work done for LADSPA / L2. Make Lumiera a host for these plugin systems + * expand on the work done for LADSPA / LV2; + + make Lumiera a host for these plugin systems... * investigate how to discover sound card properties. Develop a concept how to describe these in a generic fashion, independent of the concrete library used for output. The purpose is to allow binding with the structure of the session model @@ -283,12 +284,6 @@ Steam Layer:: * expand on the work done for a pooling small objects allocator. * develop a backend for our various allocation schemes to use this allocator. -- Command system at the GUI interface - - * expand on the work done for generic commands - * implement a command dispatcher to allow blocking and queuing of commands - * develop a scheme how to code the GUI commands in practice - - provide the foundation for symbolic rules and script bindings * expand on the work done for symbolic and hash references @@ -314,10 +309,20 @@ Website and infrastructure:: - help with our continuous integration setup +Current goals of development:: +- achive a link:{ldoc}/design/governance/integration.html[first integration] of the application... +- https://issues.lumiera.org/report/17[»Focus Topics«] for further development. + '''' -'''' +.... +​ +​ +​ +.... -Do you have any further ideas? Please speak up on the mailing list or on IRC. +Do you have any further ideas? + +Please speak up on the mailing list or on IRC. + Such are always welcome. diff --git a/wiki/thinkPad.ichthyo.mm b/wiki/thinkPad.ichthyo.mm index d5fa1f364..60265eb76 100644 --- a/wiki/thinkPad.ichthyo.mm +++ b/wiki/thinkPad.ichthyo.mm @@ -159529,10 +159529,58 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo + + + + + + + + + + + + + + + + + + + + + + +

+ {date} : eine lokale Konvention nur für Lumiera +

+ + + + + +

+ ...einfach weil wir dieses Attribut explizit in unserer page.conf verwenden — und wenn es nicht definiert ist, fällt die ganze Zeile mit dem umschließenden <span>-Element weg! +

+ + + + + + + + + + + + + + + - + @@ -159678,7 +159726,7 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - + @@ -160094,10 +160142,10 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - + - + @@ -160381,7 +160429,7 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - + @@ -160528,7 +160576,8 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - + + @@ -161877,7 +161926,7 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - + @@ -162039,7 +162088,7 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - + @@ -162342,7 +162391,7 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - + @@ -162683,7 +162732,7 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - + @@ -162695,8 +162744,8 @@ unsigned int ThreadIdAsInt = *static_cast<unsigned int*>(static_cast<vo - - + + @@ -165574,8 +165623,9 @@ on some aspects of file handling media loading. - + + @@ -165612,7 +165662,8 @@ on some aspects of file handling media loading. - + + @@ -166050,8 +166101,42 @@ that situation will improve in forseeable future. + + + + +

+ Die Umstände sind nicht ganz klar — seinem Nachbarn (Fritz) geht es schlecht, und die Heizung ist (jetzt wohl endgültig) kaputt, und was sonst noch so durch den Wind is... +

+ + + + - + + + + + + + + + + +

+ ...denn ich habe sie ganz bewußt in eine größere Aufräum-Aktion mit eingebunden; die Texte müssen also in der Git-Historie in diesem Kontext stehen, weil dadurch auch meine Entscheidungen in den RfCs mit in den Kontext gestellt sind. Außerdem habe ich den sehr gewichtigen Essay zur Komplexität geschrieben, der die adäqate Antwort auf den Streit zur Plugin-Architektur darstellt. Und all das zusammen ist jetzt »dezent versteckt« in einem riesigen Schall an genereller Aufräum-Arbeit, die ich nunmehr gut zuende gebracht habe. +

+ + + + + + + + + + + @@ -166167,7 +166252,7 @@ that situation will improve in forseeable future. - + @@ -166276,7 +166361,7 @@ that situation will improve in forseeable future. - + @@ -166315,7 +166400,7 @@ that situation will improve in forseeable future.

- + @@ -166408,7 +166493,7 @@ that situation will improve in forseeable future. - + @@ -166543,7 +166628,7 @@ that situation will improve in forseeable future. - + @@ -166701,6 +166786,78 @@ that situation will improve in forseeable future. + + + + + + + + + + + + + + + + +

+ ...was ich super finde! +

+

+ Denn dadruch wird eine Seite auch neu gerendert, wenn sich ein Include geändert hat, oder das page-Template +

+ + + + + + + +

+ wodurch diese neuer wird als das zugehörige HTML — und damit von der eigentlichen Render-Schleife in build_website.sh aufgegriffen... +

+ + + + + + + + + + + +

+ auf jeder Seite steht im Footer das Datum der letzten Änderung gemöß Git +

+ + + + + + + + + + + + + + + + + + + + + + + + + + @@ -166718,7 +166875,7 @@ that situation will improve in forseeable future. - + @@ -168377,13 +168534,159 @@ that situation will improve in forseeable future. - - + + - - + + + + + + + + + + + + + + +

+ Ha! ich fand diese Seite bisher immer schon lustlos im Design — so gut der Text auch ist (Benny's Hilfe sei Dank!) +

+

+ Dieses Logo ist eine banal-einfache Idee mit erheblicher Wirkung: nun stehen die zwei Blöcke oben prominent da, und die drei Textblöcke darunter setzen sich klarer ab... +

+

+ +

+

+ Die Breite der Grafik läßt sich leider nur +

+ + + + + + + + +

+ Diese Geschichte ist nun doch endlos lange her, und eigentlich etwas peinlich (wie meine erneute Unterschung der Anfänge gezeigt hat). Aus heutiger Sicht könnte dieser Text schon knapper sein ... und die beiden Abschnitte schließen nun direkt aneinander an, und sind auch insgesamt Abstrakter. Diesen ganzen Schlenker mit dem Namen "Cinelerra-3" brauchts wirklich nicht mehr! +

+ + + + + + + + + + + + + + +

+ auch wenn wir die Storage nicht mehr loswerden können, immerhin kann man es mal unter den Teppich kehren +

+ + + + + + + + + + + + + + + + +

+ als »Müll« gelten Grafiken, hinter denen keine wirkliche Idee steht und auf die niemals aufgebaut wurde; ein Beispiel sind Screenshots aus der Prototypen-Zeit — da genügt es, einen einzigen aufzuheben +

+ + + + + + + + + + + + + + + +

+ ich teile definitiv nicht den Glauben an spontane Selbstheilungskräfte +

+ + + + + + + + + + +

+ Das läuft bloß darauf hinaus, daß wieder mal ein neues »Design« erfunden wird und dann die Umsetzung anderen überlassen bleibt. Oder mir jemand erzählt, wie man heute im Internet kommuniziert (obwohl ich das sehr gut selber weiß) +

+ + + + + + + +

+ sowas funktioniert möglicherweise bei einem gut eingespielten, professionellen Team. +

+ + + + + + + +

+ Es ist mir völlig klar, daß »Jedermann« vor allem erschlagen und befremdet ist nach Lektüre der Design-Seiten. Und was ich gleich schon gar nicht mehr haben kann, wäre ein weiteres »GUI brainstorming« +

+ + + + + + + + + + + + + + + + + + + + + + + + @@ -168944,16 +169247,44 @@ that situation will improve in forseeable future. - + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + - + @@ -168970,14 +169301,16 @@ that situation will improve in forseeable future. - + - + + + @@ -169086,7 +169419,7 @@ that situation will improve in forseeable future. - + @@ -169113,7 +169446,7 @@ that situation will improve in forseeable future. - + @@ -170080,14 +170413,15 @@ that situation will improve in forseeable future. - - - + + + + - - + + - + @@ -180159,14 +180493,14 @@ env.Command('out.bin', 'in.bin', my_action) - + - + @@ -180187,7 +180521,7 @@ env.Command('out.bin', 'in.bin', my_action) - + @@ -180656,7 +180990,11 @@ env.Command('out.bin', 'in.bin', my_action) - + + + + + @@ -180690,7 +181028,7 @@ env.Command('out.bin', 'in.bin', my_action) - + @@ -180839,8 +181177,9 @@ env.Command('out.bin', 'in.bin', my_action) - + + @@ -180970,6 +181309,9 @@ env.Command('out.bin', 'in.bin', my_action) + + +