During the sucessful developer and user meeting in Zürich there was the idea to have a second meeting this year at the Albert Ludwig University Medical Center Freiburg http://www.uniklinik-freiburg.de.

Date: Monday, Oktober 29 to Wednesday, Oktober 31 2007

Time: The meeting will start at Monday 10:15 UTC+01:00

Location of the meeting and hotel information.

• Agenda
• Communication: irc.freenode.net#lenya
  

Sorry, no video coverage available. The camera we have here does not play well with Linux, swapping kernels and IEEE1394 libs didn't help. We'll gather the presentation slides on this page, and you can join #lenya at irc.freenode.net if you feel chatty.

Current List of Participants

Sign up here if you can make it to Freiburg:

• MartinGinter
• LambertUtz
• RudolfKorhummel
• JörnNettingsmeier
• AndreasHartmann
• SibylleStromeyer
• MichaelTrindler
• JannForrer (arriving on Monday evening or Tuesday morning).
• JürgenRagaller (Monday and Tuesday)
  
  

This is an early draft. Feel free to add other topics of interests here:

Topic Suggestions

• Problems and solutions
  • Review and clean up the (few) remaining bugzilla issues
  • 2.0-dev concurrency testing as a group, using the zones-server default publication
  • locking - discuss possible improvements
  • Migration of lenya 1.2.x to 2.0
• Publishing the Lenya website with Lenya

Schedule

Talks / Presentations (Tuesday)

• Jürgen Ragaller - Using xi:include to mix user data and external data sources (e.g. a database query) inside the editable area - and make shure the include statement survives the editing process. http://www.null-oder-eins.ch/web-it/lenya_meeting/WebContent/lenya_gt_071029/lenya_code_sources.html slides (s5)
• Rudolf Korhummel - Experiences made with the migration of our website to lenya. (www.uniklinik-freiburg.de) - the slides: freiburgexp.pdf
• Michael Trindler - Presentation of a new WYSIWYG XML-Editor - the slides: mozWriter.pps
  
  

Sketchpad

• Great trick suggested by an UniZh consultant for Lenya deployment and training: first introduce the oneform editor and give your users some insights into xhtml structured markup, and only then show them a WYSIWYG editor :-D Rudolf reports very good acceptance of BXE after users had been sufficiently frightened by oneform.
  
• User requirement: comment feature for reviewers in case of rejection. Could be done with xhtml <ins/> and <del/> tags styled accordingly:

  <h1>Welcome to FOO.com</h1>

  <p><del>Hideho, folks, w</del><ins>W</ins>elcome to the new web site of FOO.com.</p>
  <p>We are <del>like totally kinda wetting our pants with joy now you've come to visit us.</del><ins> happy to see you are taking some of your valuable time to evaluate our offerings.</ins></p>

/* authoring stylesheet: */
 del,ins {color:red;}
 del {text-decoration:line-through;}
 ins {font-style: italic;}
/* live stylesheet */
 del {display:none;}
 ins { };

ATM, documents in review state cannot be edited. We need another usecase "comment" with limited editing capabilities (only add ins, del and plaintext nodes) and necessary transitions...