From 4dba1c816d4d4d558729378065f2a46a42862b08 Mon Sep 17 00:00:00 2001 From: Ichthyostega Date: Sat, 23 Aug 2025 04:29:08 +0200 Subject: [PATCH] DOC: FrOSCon meeting -- integrate improvements from Benny --- .../workflow/Verwijlen/FrosconMeeting.txt | 35 ++- wiki/Workflow_Verwijlen.mm | 248 ++++++++++++++++++ 2 files changed, 264 insertions(+), 19 deletions(-) diff --git a/doc/design/workflow/Verwijlen/FrosconMeeting.txt b/doc/design/workflow/Verwijlen/FrosconMeeting.txt index d8af27fb5..7554ae0cd 100644 --- a/doc/design/workflow/Verwijlen/FrosconMeeting.txt +++ b/doc/design/workflow/Verwijlen/FrosconMeeting.txt @@ -117,34 +117,31 @@ the elements step wise while still retaining the ability to edit the contents. Target audience ~~~~~~~~~~~~~~~ -It is important to identify our target audience to be able to obtain a clear -vision of which features are more preferable to include and those features which -might be less suitable to incorporate into Lumiera. This will allow us to -fine-focus into the particular needs of these groups and provide us with a -mechanism to curtail our long feature list. Eventually we might have a list of -features ordered according to priority. Other factors are, of course, -important in determining whether a feature is implemented or not, e.g., effort -required to implement a feature; but we focus solely on identifying our target -audience here. +It is important to identify our target audience to be able to frame a clear +picture of which features are more preferable to include and those features which +might be less suitable to incorporate into Lumiera. +Define such groups will allow us to fine-focus into the particular needs of these groups +and provide us with a mechanism to curtail our long feature list. Eventually we might have +a list of features ordered according to priority. In his link:WorkflowProposals.html[»Lumiera Workflow Proposals«], _Wouter_ -identified six groups which mould most likely be attracted to Lumiera and its goals. +identified six groups which would most likely be attracted to Lumiera and its goals. - The highly specialised editor who works in an environment where different parts of the post-production of a film are handled by different people: assistant editors, colourists, audio engineers, etc. -- The allround contracted editor who handles all aspects of post-production -- The allround artistic filmmaker who also edits -- The allround social media creator who values the use of visual effects, +- The all-round contract editor who handles all aspects of post-production +- The all-round artistic filmmaker who also edits +- The all-round social media creator who appreciates the use of visual effects, motion graphics and sound effects. -- The free-flowing editor who does not have a fixed idea of how the edit should be - and instead wants to play and move things around, and who might not work in a linear - fashion: they might do a bit of colour correction to get a better sense of how a scene feels, - then go back to editing, etc. +- The free-flowing editor without a fixed idea of the edit, who prefers to explore the + footage and move things around, and who might not work in a linear fashion: + they might, for example, do a bit of colour correction to acquire a better feel for a scene + and then go back to coarse-grained editing. - The editor who has the film already cut in their head and have a very strong sense of - what they want to do and work in a very structured way towards accomplishing this vision. + what they want to do and progress through structured and precise steps towards realising their vision. -These groupings are naturally provisional and will mostly likely change -- which +These groupings are naturally provisional and will most likely change -- which is very good -- as we add important features that are deemed essential but fit to no group in our selection. diff --git a/wiki/Workflow_Verwijlen.mm b/wiki/Workflow_Verwijlen.mm index 8437bde0b..c0946a5f0 100644 --- a/wiki/Workflow_Verwijlen.mm +++ b/wiki/Workflow_Verwijlen.mm @@ -143,6 +143,254 @@ + + + + +

+ Mail-Thread "Workflow and Structure" +

+ + + + + + + + + +

+ Mail-Thread "Workflow document update" +

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

+ desen Bilder liegen im Website-Repository +

+ + + + + +

+ {imgg} = /media/img/design.gui +

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

+ Noch vor der ersten wirklichen Veröffentlichung, so daß die Bilder sich nicht im Core-Git niederschlagen. +

+ + + + + + + + +

+ In v1 hatte Wouter Bilder in kleinerer Auflösung eingebaut, die auch noch manuell in Gimp beschnitten werden mußten; jetzt könnte ich diese allesamt durch die besseren Bilder aus v2 substituieren (und damit ein paar 110k Storage sparen) +

+ + + + + + + + +

+ In design/gui/GuiDiscussion/TimelineDiscussion.txt ... der zeigt immer noch auf eine externe Adresse +

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

+ überprüft, das gilt für alle (es sind bisher nur ganz wenige, in den GUI-Proposals); ich hatte mich einfach darum nie gekümmert +

+
    +
  • + design/gui/GuiDiscussion/ConceptProposals/RichardSpindler.txt +
    • +
  • + design/gui/GuiDiscussion/ConceptProposals/Alcarinque.txt +
    • +
  • + design/gui/GuiDiscussion/ConceptProposals/AkhiL.txt +
    • +
  • + design/gui/GuiDiscussion/TimelineDiscussion.txt +
    • +
  • + design/workflow/Verwijlen/WorkflowProposals.txt +
    • +
+ + + + + + + +

+ Zeile 297: +

+

+ +

+

+ /* -------- Image -------- */ +

+

+ span.image img { +

+

+     border-style: none; +

+

+ } +

+

+ +

+

+ div.imageblock img { +

+

+     padding-left: 13%;  +

+

+     border: 0px solid silver; +

+

+ } +

+ + + + + + +

+ commit 694ade36042c420efdeface2c80c0906ea3f5fa6 +

+

+ Author: Ichthyostega <prg@ichthyostega.de> +

+

+ Date:   Mon Feb 21 01:38:15 2011 +0100 +

+

+ +

+

+     small CSS tweaks/fixes +

+

+ +

+

+ +

+

+ commit ed7a397aecb0c5b3b284663bb09e08494adb087d +

+

+ Author: raffa <raffaella.traniello@livecom.it> +

+

+ Date:   Sun May 25 17:51:31 2008 +0200 +

+

+ +

+

+     Added tools for building a web page with asciidoc +

+ + + + + + + +

+ commit 8ee898954a38d9d68ef6fac0a93ceb5ffa587a6e +

+

+ Author: raffa <raffaella.traniello@livecom.it> +

+

+ Date:   Sat Jan 3 18:41:09 2009 +0100 +

+

+ +

+

+     Added 13% padding to images +

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

+ ...denn diese würden eine Angabe direkt im <img...>-Tag übersteuern — und damit gäbe es keine Möglichkeit mehr, direkt aus dem Asciidoc heraus das Layout von Bildern zu steuern +

+ + + + + +