Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E68CA61FA for ; Mon, 4 Jul 2011 18:45:24 +0000 (UTC) Received: (qmail 21629 invoked by uid 500); 4 Jul 2011 18:45:24 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 21567 invoked by uid 500); 4 Jul 2011 18:45:24 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 21559 invoked by uid 99); 4 Jul 2011 18:45:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2011 18:45:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of acolorado@gmail.com designates 74.125.82.175 as permitted sender) Received: from [74.125.82.175] (HELO mail-wy0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2011 18:45:16 +0000 Received: by wyg30 with SMTP id 30so4020080wyg.6 for ; Mon, 04 Jul 2011 11:44:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=LlRA591IWwBRwt0XlpByLfjkiThANkI8ox/FnPLsg1A=; b=ts3DVG7npR1OPRRk0nnkro4eD6+WaW5q8G9cbd1A/b6bKUIpaKZRI4XUIrZveh2zM1 bnJEFm4iEi9mt0H6ffe0650ePXV8RKi1FcrrZ9l4qBEV7ypISBalBvC7Lm7OM6Otd2jD E0g+kn1oktKBCWh/nIfbzgE3ATjhVUGz2JsW8= MIME-Version: 1.0 Received: by 10.216.237.8 with SMTP id x8mr3911983weq.37.1309805096249; Mon, 04 Jul 2011 11:44:56 -0700 (PDT) Sender: acolorado@gmail.com Received: by 10.216.136.134 with HTTP; Mon, 4 Jul 2011 11:44:56 -0700 (PDT) In-Reply-To: <731743.91661.qm@web161425.mail.bf1.yahoo.com> References: <20110704152224.7ECFE2388994@eris.apache.org> <5589495C-C188-43B3-812A-36C509A032E9@comcast.net> <325204.78804.qm@web161423.mail.bf1.yahoo.com> <0F49D7AD-21D8-44A2-8886-C6882496587B@comcast.net> <896479.41828.qm@web161427.mail.bf1.yahoo.com> <731743.91661.qm@web161425.mail.bf1.yahoo.com> Date: Mon, 4 Jul 2011 13:44:56 -0500 X-Google-Sender-Auth: h7AsI8_LmKcRDc3_PwbXButB6fE Message-ID: Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html From: Alexandro Colorado To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=000e0cd2c60a7ca96a04a742c334 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd2c60a7ca96a04a742c334 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Jul 4, 2011 at 1:20 PM, Joe Schaefer wrote= : > > > > > ----- Original Message ---- > > From: Alexandro Colorado > > To: ooo-dev@incubator.apache.org > > Cc: ooo-commits@incubator.apache.org > > Sent: Mon, July 4, 2011 2:04:30 PM > > Subject: Re: svn commit: r792168 - in /websites/production/openofficeor= g: > ./ > >content/openofficeorg/people.html > > > > On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer >wrote: > > > > > That's not useful criticism. Either learn some perl > > > and code it up for the project to use, or learn some > > > python and submit your change upstream. Either way > > > discussing php is kinda pointless for this. > > > > > > > Well it could be whatever u want, as long as is some dynamic script, i= t > > could be Javascript for all I know. Is the implementation that I have = no > > idea how to integrate to the CMS. So the problem is not the script. > Python > > and Perl also have some sort()-like function as well. > > As I explained to Dave, the best way to understand how the CMS works is t= o > think of it as django done (mostly) in perl, but with an agressive > filesystem > cache. (Pretend the markdown files are "from the database", and read up = on > how django dispatches urls to view code via urls.py- that will give you > clues as > to how the path.pm @patterns array works). > > The code you write in view.pm to process a (markdown) file can be > arbitrary, > even > to call out to php if you can convince me to install php on the cms serve= r. > And > besides that aspect, the markdown daemon is the python implementation whi= ch > is > designed to be extensible, and we already run a custom asf-only extension > here. > Adding more of those if they're well done is certainly ok with me. > ok so here would be the type of code -- in perl -- that would aim to do the job. while( ) { chomp; $count++; # skip header next unless $count; my $row; @$row =3D split( /|/, $_ ); push @$sheet, $row; } foreach my $row ( sort { $a->[1] <=3D> $b->[1] } @$sheet ) { print join( '|', @$row ), "\n"; } This process should be triggeered by some sort of markup. (i.e. ^ v on header) so aditional code would need to be there to inspect these triggers. example: || ID || Name || Email || | 3 | Mark | mark@apache.org | | 1 | John | john@apache.org | | 2 | Dan | dan@apache.org | || ID v || Name || Email || | 3 | Mark | mark@apache.org | | 2 | Dan | dan@apache.org | | 1 | John | john@apache.org | > > Yes it takes time to familiarize oneself with the CMS, as it is not a > typical > CMS. It is designed to be both powerful and easy to use, and based on > generating > read-only cacheable content from a variety of sources (not all of which > need to > be on disk). Look over the documentation for the www.apache.org site and > checkout > how a few of the more complex sample pages like http://www.apache.org/dev= /and > http://www.apache.org/licenses/exports/ to see some of the capabilities. > > If you have any questions along the lines of "How do I do so and so" that > are > not answered at http://www.apache.org/dev/cmsref.html , ask here and I'll > be > glad to both update that page and give you suggestions. If it's > interesting > enough I may even help you write it ;-). > > > > > > > > > > > > > > > > > > > ----- Original Message ---- > > > > From: Alexandro Colorado > > > > To: ooo-dev@incubator.apache.org > > > > Cc: ooo-commits@incubator.apache.org > > > > Sent: Mon, July 4, 2011 1:25:33 PM > > > > Subject: Re: svn commit: r792168 - in > /websites/production/openofficeorg: > > > ./ > > > >content/openofficeorg/people.html > > > > > > > > On Mon, Jul 4, 2011 at 11:09 AM, Dave Fisher > > > > wrote: > > > > > > > > > > > > > > On Jul 4, 2011, at 8:54 AM, Joe Schaefer wrote: > > > > > > > > > > > At 23' full-screen it renders just fine ;-). I'd say try > > > > > > playing with the min-width css attribute for th or td. > > > > > > > > > > > > > > > > > > You have a choice here of using ooo.css or embedding > > > > > > a