I'm done at this point. There is some polish work that anyone can do if there comes a need for it.
----- Original Message ---- > From: Dave Fisher <[email protected]> > To: [email protected] > Sent: Mon, July 4, 2011 4:51:36 PM > Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ >content/openofficeorg/people.html > > > On Jul 4, 2011, at 12:42 PM, Joe Schaefer wrote: > > > I implemented it so that you put the v or ^ marker > > in the line which separates the header from the entries. > > Enjoy. > > I see from the commits log that you are still working on it. I'll delay any >comment other than - it looks cool so far. Thanks! > > Regards, > Dave > > > > > > > > > ----- Original Message ---- > >> From: Alexandro Colorado <[email protected]> > >> To: [email protected] > >> Sent: Mon, July 4, 2011 2:44:56 PM > >> Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: >./ > > >> content/openofficeorg/people.html > >> > >> On Mon, Jul 4, 2011 at 1:20 PM, Joe Schaefer <[email protected]> >wrote: > >> > >>> > >>> > >>> > >>> > >>> ----- Original Message ---- > >>>> From: Alexandro Colorado <[email protected]> > >>>> To: [email protected] > >>>> Cc: [email protected] > >>>> Sent: Mon, July 4, 2011 2:04:30 PM > >>>> Subject: Re: svn commit: r792168 - in >/websites/production/openofficeorg: > >>> ./ > >>>> content/openofficeorg/people.html > >>>> > >>>> On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <[email protected] > >>>> 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, >it > >>>> 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 > >>> >to > >>> 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 > > server. > >>> And > >>> besides that aspect, the markdown daemon is the python implementation >which > >>> 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( <DATA> ) { > >> chomp; > >> $count++; > >> # skip header > >> next unless $count; > >> my $row; > >> @$row = split( /|/, $_ ); > >> push @$sheet, $row; > >> } > >> > >> foreach my $row ( sort { $a->[1] <=> $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 | [email protected] | > >> | 1 | John | [email protected] | > >> | 2 | Dan | [email protected] | > >> > >> || ID v || Name || Email || > >> | 3 | Mark | [email protected] | > >> | 2 | Dan | [email protected] | > >> | 1 | John | [email protected] | > >> > >> > >> > >>> > >>> 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 <[email protected]> > >>>>>> To: [email protected] > >>>>>> Cc: [email protected] > >>>>>> 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 <[email protected] > >>>> > >>>>> 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 <style type="text/css"> block in the markdown just > >>>>>>>> before the table. > >>>>>>> > >>>>>>> That will be a PITA - each column needs a different minimum width > >>> and > >>>>> there > >>>>>>> is no way to differentiate. > >>>>>>> > >>>>>>> Maybe someone should enhance markdown extras. > >>>>>>> > >>>>>>> http://michelf.com/projects/php-markdown/extra/#table > >>>>>>> > >>>>>>> All it can do is control the alignment. Width control ought to be > >>>>> allowed, > >>>>>>> either that or an id / class tag to actually tie it in with > >>> specific > >>>>> css. > >>>>>>> > >>>>>>> | Item | Value | > >>>>>>> | ------200 | --:100| > >>>>>>> | Computer | $1600 | > >>>>>>> | Phone | $12 | > >>>>>>> | Pipe | $1 | > >>>>>>> > >>>>>>> Thoughts? > >>>>>>> > >>>>>>> Otherwise I really don't see why it's wrong to have the html > >>> table > >>>>> here. > >>>>>>> > >>>>>> > >>>>>> Now we just need to find out if there is something like ^ or v to > >>> sort > >>>>> the > >>>>>> table by names. If it was pure php then we could do some sort() > >>>>> function. > >>>>>> > >>>>>> > >>>>>> > >>>>>>> > >>>>>>> Regards, > >>>>>>> Dave > >>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> ----- Original Message ---- > >>>>>>>>> From: Dave Fisher <[email protected]> > >>>>>>>>> To: [email protected] > >>>>>>>>> Cc: [email protected] > >>>>>>>>> Sent: Mon, July 4, 2011 11:50:06 AM > >>>>>>>>> Subject: Re: svn commit: r792168 - in > >>>>>>> /websites/production/openofficeorg: ./ > >>>>>>>>> content/openofficeorg/people.html > >>>>>>>>> > >>>>>>>>> Hi Joe, > >>>>>>>>> > >>>>>>>>> Thanks for switching the people.mdtext to wiki formatting. > >>>>>>>>> > >>>>>>>>> There was one change lost in your conversion. I had set the > >>> width > >>>>> of > >>>>>>> the first > >>>>>>>>> three columns. By doing that the table was much easier to > >>> read. > >>>>>>>>> > >>>>>>>>> How do we set column width in markdown? > >>>>>>>>> > >>>>>>>>> Regards, > >>>>>>>>> Dave > >>>>>>>>> > >>>>>>>>> On Jul 4, 2011, at 8:22 AM, [email protected] wrote: > >>>>>>>>> > >>>>>>>>>> Author: joes > >>>>>>>>>> Date: Mon Jul 4 15:22:24 2011 > >>>>>>>>>> New Revision: 792168 > >>>>>>>>>> > >>>>>>>>>> Log: > >>>>>>>>>> Publishing merge to openofficeorg site by joes > >>>>>>>>>> > >>>>>>>>>> Modified: > >>>>>>>>>> websites/production/openofficeorg/ (props changed) > >>>>>>>>>> > >>>>> websites/production/openofficeorg/content/openofficeorg/people.html > >>>>>>>>>> > >>>>>>>>>> Propchange: websites/production/openofficeorg/ > >>>>>>>>>> > >>>>>>>>> > >>>>>>> > >>>>> > >>>>> > >>> > >>> > >>>> >------------------------------------------------------------------------------ > >>>>>>>>>> --- svn:mergeinfo (original) > >>>>>>>>>> +++ svn:mergeinfo Mon Jul 4 15:22:24 2011 > >>>>>>>>>> @@ -1 +1 @@ > >>>>>>>>>> -/websites/staging/openofficeorg/trunk:791146-792165 > >>>>>>>>>> +/websites/staging/openofficeorg/trunk:791146-792167 > >>>>>>>>>> ; > >>>>>>>>>> Modified: > >>>>>>>>> > >>> websites/production/openofficeorg/content/openofficeorg/people.html > >>>>>>>>>> > >>>>>>>>> > >>>>>>> > >>>>> > >>>>> > >>> > >>> > >>>> >============================================================================== > >>>>>>>>>> --- > >>>>> websites/production/openofficeorg/content/openofficeorg/people.html > >>>>>>>>> (original) > >>>>>>>>>> +++ > >>>>>>> > >>> websites/production/openofficeorg/content/openofficeorg/people.html > >>>>> Mon > >>>>>>>>> Jul 4 15:22:24 2011 > >>>>>>>>>> @@ -192,7 +192,7 @@ to look at all contributors to our > >>> issue > >>>>>>>>>> </tr> > >>>>>>>>>> <tr> > >>>>>>>>>> <td>homembit</td> > >>>>>>>>>> -<td><a href="http://www.homembit.com"";>Jomar Silva</a></td> > >>>>>>>>>> +<td><a href="http://www.homembit.com";>Jomar > >>> Silva</a></td> > >>>>>>>>>> <td>Sao Paulo, Brazil</td> > >>>>>>>>>> <td>C/C++, Python, XML, ODF, Architecture, Marketing, > >>>>> Localization, > >>>>>>>>> Documentation, Community Management</td> > >>>>>>>>>> </tr> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> *Alexandro Colorado* > >>>>>> *OpenOffice.org* Español > >>>>>> http://es.openoffice.org > >>>>>> > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> *Alexandro Colorado* > >>>> *OpenOffice.org* Español > >>>> http://es.openoffice.org > >>>> > >>> > >> > >> > >> > >> -- > >> *Alexandro Colorado* > >> *OpenOffice.org* Español > >> http://es.openoffice.org > >> > >
