From dev-return-77861-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Thu Sep 08 05:07:52 2005 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 11194 invoked from network); 8 Sep 2005 05:07:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Sep 2005 05:07:51 -0000 Received: (qmail 37948 invoked by uid 500); 8 Sep 2005 05:07:41 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 37773 invoked by uid 500); 8 Sep 2005 05:07:40 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 37747 invoked by uid 99); 8 Sep 2005 05:07:39 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Sep 2005 22:07:39 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [213.133.33.30] (HELO mailrelay.is.nl) (213.133.33.30) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Sep 2005 22:07:52 -0700 Received: from [213.133.51.241] (HELO hai01.hippo.local) by mailrelay.is.nl (CommuniGate Pro SMTP 4.3.5) with ESMTP id 5254966; Thu, 08 Sep 2005 07:08:38 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: [GT2005] Cocoon GT Talks! Date: Thu, 8 Sep 2005 07:07:36 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [GT2005] Cocoon GT Talks! Thread-Index: AcW0M3FBXCKpsMOdQDagq/y0+mvr8g== From: "Arje Cahn" To: , X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi everyone, This is the list of proposed talks for the upcoming CocoonGT, ordered by = date received. 14 in total, and there's only place for 8! I'd like to = put the=20 program online by friday afternoon, to make sure people have enough=20 time to sign up for the event. Could everyone who feels the need to do so please state his opinion!? I don't know what would be the smartest way of doing this...=20 But any feedback would be very well appreciated! Also see my notes below.. Thanks and hope to see you all in october,=20 Arj=E9 ------------ PROPOSALS -------------- 01 - Torsten Schlabach:=20 "All about URIs or: Find your sources=20 (protocols from file:// to jcr:// and beyond)" Any Cocoon pipeline starts with a generator that is getting stuff from=20 somehere that will be augmented and eventually rendered further down = the=20 road. The underlying Avalon framework in Cocoon allows the use of a=20 number of pseudo-protocols to define from where a Geneator (or also a=20 transformer) should read its byte input stream. In the first place, proper use of these protocols can make sitemaps = much=20 more readable and provides abstraction from specific installation=20 deteails such as file system paths. But there are also protocols that=20 allow Cocoon to directly access content from basically anwhere and not=20 just the filesystem. 02 - Carsten Ziegeler "Past, Present and Future of the Cocoon Portal" This talk gives an overview of the Cocoon portal solution. The portal = is based on Apache Cocoon to benefit from the advantages of Cocoon when it comes to integrating different data sources and providing the information to different devices in different formats. This session introduces the basic concepts behind the portal and how to build a portal application. Learn how the portal changed through time and what the future might bring. 03 - Torsten Curdt "Rapid application development with cocoon - javaflow and the=20 compiling class loader" =09 The session would be probably be more for a slightly advanced=20 audience. I could talk about how to use the auto-reloading and javaflow with its current limitations. 04 - Andrew Savory "Simplifying Cocoon" New frameworks such as Ruby on Rails are teaching the old dogs some =20 new tricks. With the maxims of "write less code", "don't repeat =20 yourself" and "convention over configuration", programming has become =20 fun again. What can the Cocoon framework learn from this? Consider the lilies: most Java/XML developers fight with =20 configuration and project building tools, and while they do XML =20 situps, our Rails colleagues utter nice Zen-like 'umms' as their =20 framework gently guesses at their thoughts. This session will point out the ways in which we can learn from our =20 competitors and make life easier for our users. It will also =20 introduce Racoon: all the fun of Rails, on Cocoon. 05 - Daniel Fagerstr=F6m "Cocoon Blocks" =09 The Cocoon community is working hard on the next generation of Cocoon.=20 The most important improvement is that most of the functionality will = be=20 packaged in so called blocks. The blocks architecture is built on the=20 application framework OSGi, which also is used as the basis for the=20 plugin architecture in Eclipse 3. A block can contain libraries and=20 resources. At a higher level, blocks can contain reusable components. = It=20 will be possible to choose what component framework to use for each=20 block, so that one block can contain e.g. Spring managed components and = another Pico managed ones, that can cooperate seamlessly. What is maybe = most exciting is that a block can contain a whole extensible web=20 application. This will lead to a new level of application reuse. An=20 application can be built by extending an application block and by just=20 overriding the resources that needs to be modified. This is analogous = to=20 extension in object oriented languages. The blocks based Cocoon will = put=20 an end of todays huge download, you just download a small Cocoon core=20 and use a deployment tool to download, configure and install the blocks = that your application happens to need. In the talk the new architecture = will be described and examples will be given on how applications can be = devloped with the new tools. 06 - Sylvain Wallez "Something about AJAX" =09 ([AC] Sylvain hasn't completed his proposal, yet. But here are some=20 promising quotes:) "I may help by talking about some of my favorite subjects. One that = comes=20 to mind is Ajax in Cocoon."=20 "Actually, this may force me to actually implement some things I have = in=20 mind, the main one being replacing the current client-side JS I wrote = to=20 handle Ajax request by Prototype and Scriptaculous, the JS library=20 used in Ruby on Rails. Even more fun!" 07 - Bertrand Delacretaz "Cocoon Bricks: best practices by example" =09 The "Cocoon Bricks" example application demonstrates all the essential=20 aspects of a typical Cocoon-based web application: java components=20 management at the application level, database access using=20 object-relational mappings, and of course the Power Trio: Pipelines,=20 Flowscript and Cocoon Forms, all tied together in a consistent whole. =09 The application, which will be available online in source form,=20 contains a minimal amount of code, structured and written to be easy to = understand. External libraries include Hivemind for component=20 management, OJB for database access and Derby as the database, all=20 easily replaceable with equivalents if desired. =09 We will study code snippets of all the important parts, from the build=20 system to the component interactions and final application stages. =09 This talk is open to Cocoon beginners, although a basic understanding=20 of the main Cocoon concepts (sitemaps, flowscript, pipelines, as=20 presented in the Supersonic Tour) will help in getting the most from=20 it. =09 08 - Alfred Nathaniel "XSP Tips and Traps" Although XSP is no longer considered a core technology by the Cocoon=20 avantgarde, it is still a powerful tool for generating dynamic = webpages. =20 Its stability, robustness, and similarity to the well-known ASP/JSP=20 concepts makes it a good fit for moving an established team from=20 another framework to Cocoon. The talk draws from three years of XSP experience and wants to warn of=20 common pitfalls and point to less known details of XSP and logicsheet=20 processing. Knowledge of Java, XSLT, and Cocoon pipelines are assumed. 09 - Andrew Savory / Massimo Sonego "What we get up to with Cocoon" I've been talking with Massimo at Otego about a talk we were =20 considering doing together, but we're wondering if it might fit a =20 "lightning talks" session rather than a full-size session. Are there =20 any plans to do shorter talks? We were thinking it might be fun to do some quick "what we get up to =20 with Cocoon" examples, more from a newbie/business user perspective =20 than a techie perspective, and I'm sure a few others would be able to =20 join in, too. 10 - Michael Wechner "What Daisy, Hippo and Lenya can learn from each other!" Instead of doing a shootout, let's discuss and focuse on where the various Cocoon based CMS can learn from each other and maybe even collaborate ... PROPOSED SPEAKERS: Steven Noels (haven't asked him yet ;-) Arje Cahn (haven't asked him yet ;-) Michael Wechner (he won't be on vacation this year ;-) 11 - Max Pfingsthorn "CForms libraries: How Cocoon forms libraries make your life easier" ([AC] Max hasn't finished his proposal yet, since he's buried himself=20 in GSOC code, but he'd like to do a short talk on what he did, possibly combined with Sylvain's AJAX talk) 12 - Lars Huttar "Sitemap Browser: Using Cocoon to Explore Cocoon Sitemaps" A simple Cocoon sitemap can be clean and elegant. But=20 as pipelines aggregate calls to other pipelines, and the number of=20 pipelines increases, a sitemap can become difficult to follow. Sitemap=20 Browser (SB) addresses this problem by visualizing a sitemap as an HTML = document, displaying each pipeline next to the pipeline(s) it calls, = and=20 by hyperlinking related pipelines to each other for easy navigation. SB = works to some degree on unmodified sitemaps but works better if you add = sb:* markup to help handle the harder cases. SB can also be a = convenient=20 aid in unit testing, as a framework for linking to a sample invocation=20 of each pipeline. 13 - Jack Ivers / Joh Berry / Scott Roth / Vadim Gritsenko "Performance / XSLT processors running with Cocoon" The folks here at Agile (Jack Ivers, Joh Berry, Scott Roth,=20 Vadim Gritsenko) did a fairly in-depth analysis of XSLT processors = running=20 with Cocoon, looking at performance and memory consumption. Not=20 completely scientific but we generated more information than we have = been=20 able to find elsewhere. We specifically looked at Xalan and Saxon, had = Gregor but never completed testing with it. Anyway, if there was strong = interest in this getting presented, we are willing to polish up our = work=20 and also try to get a Gregor test in. 14 - Nico Verwer "Performance / A case with very big XML documents (100's of megs)" ------------ /PROPOSALS -------------- I was thinking of combining Sylvain's Ajax talk (30 mins) with Max' = CForms libraries talk (15 mins). This would then be a kind of a "what's = new in CForms" presentation (that's what Sylvain and I discussed). Also, I was hoping to combine talk 13 (XSLT performance) and 14 (big = documents) combined with possibly a third performance talk from Pier = into a "Performance track: hints, tips and guidelines!" I'm a little bit in a hurry because I want to give people the = opportunity to see what the program will be when they start signing up = for the event. However, he list above should make clear that whatever 8 = options we choose, it will be worth travelling to Amsterdam anyway! ;-P ---- Thanks Arj=E9 Cahn Hippo =20 Oosteinde 11 1017WT Amsterdam The Netherlands Tel +31 (0)20 5224466 ------------------------------------------------------------- a.cahn@hippo.nl / www.hippo.nl --------------------------------------------------------------