You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Dave Fisher <da...@comcast.net> on 2011/07/04 17:50:06 UTC
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, joes@apache.org 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>
>
>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
Those are all available on the cms server as well
(which is not the same as people.apache.org). The
cms server is responsible for building the staging
site and committing those changes back via buildbot,
so it's important for your code in view.pm to be
supported by that (FreeBSD) installation.
----- Original Message ----
> From: Dave Fisher <da...@comcast.net>
> To: ooo-dev@incubator.apache.org
> Cc: ooo-commits@incubator.apache.org
> Sent: Mon, July 4, 2011 2:07:54 PM
> Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./
>content/openofficeorg/people.html
>
> Hi Joe,
>
> On Jul 4, 2011, at 10:45 AM, 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.
>
> Perl may be important, but it is not the only text manipulation script that
>will be useful.
>
> I personally prefer to use nawk, find, grep and sed. These are available on
>people.a.o.
>
> I'll gladly hack a perl script, if badly.
>
> Regards,
> Dave
>
> >
> >
> >
> > ----- Original Message ----
> >> From: Alexandro Colorado <jz...@openoffice.org>
> >> 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 <da...@comcast.net>
>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 <da...@comcast.net>
> >>>>> To: ooo-dev@incubator.apache.org
> >>>>> Cc: ooo-commits@incubator.apache.org
> >>>>> 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, joes@apache.org 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
> >>
>
>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Dave Fisher <da...@comcast.net>.
Hi Joe,
On Jul 4, 2011, at 10:45 AM, 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.
Perl may be important, but it is not the only text manipulation script that will be useful.
I personally prefer to use nawk, find, grep and sed. These are available on people.a.o.
I'll gladly hack a perl script, if badly.
Regards,
Dave
>
>
>
> ----- Original Message ----
>> From: Alexandro Colorado <jz...@openoffice.org>
>> 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 <da...@comcast.net> 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 <da...@comcast.net>
>>>>> To: ooo-dev@incubator.apache.org
>>>>> Cc: ooo-commits@incubator.apache.org
>>>>> 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, joes@apache.org 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
>>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Dave Fisher <da...@comcast.net>.
On Jul 4, 2011, at 11:04 AM, Alexandro Colorado wrote:
> On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <jo...@yahoo.com>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.
We can get this effect, but it will need to be in the generation of static pages.
We can then get effects like language changes and different sorts.
Here are some things you can start.
(1) A spanish version of sidenav.mdtext to use figure out how to have foreign language versions of the site.
(2) Compare es.openiffice.org with www.openoffice.org. How similar is the structure? Name some pages that will be challenges due to current use of javascript and other dynamic page mechanisms.
Step by baby step, but soon we'll be able to script.
Regards,
Dave
>
>
>
>>
>>
>>
>> ----- Original Message ----
>>> From: Alexandro Colorado <jz...@openoffice.org>
>>> 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 <da...@comcast.net>
>> 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 <da...@comcast.net>
>>>>>> To: ooo-dev@incubator.apache.org
>>>>>> Cc: ooo-commits@incubator.apache.org
>>>>>> 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, joes@apache.org 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
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
----- Original Message ----
> From: Dave Fisher <da...@comcast.net>
> To: ooo-dev@incubator.apache.org
> Cc: ooo-commits@incubator.apache.org
> Sent: Mon, July 4, 2011 2:47:50 PM
> Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./
>content/openofficeorg/people.html
>
> OK - I have a sense how atachments work from
>http://www.apache.org/dev/index.html and then invoking the bookmarklet
>
> I see that attachments are important for multiple content markups.
>
> <div class="section-content">
> {{ links.content|markdown }}
> </div>
>
> In the other example:
>
> {% block content %}
> <div id="content" class="grid_16">
> <div class="section-content">{{ main.content|markdown }}
> {{ table|safe }}
> </div>
> </div>
> {% endblock %}
>
> It is not clear how table|safe corresponds with the attached eccnmatrix.xml
>and eccnmatrix.xsl. Is that hidden in the view.pm?
Yes, you need to look at the code in view.pm which handles that url to see how
it works.
>
> Maybe I don't understand attachments in the Apache CMS.
>
> I am thinking of sidenav.mdtext. Is it possible to attach this to every
>English language page and maintain it a single space?
Well that's not how I'd do it. I'd create per-language base templates
each of which pull-in a different per-lang version of sidenav.mdtext.
You can give them all the same basic look and feel using template inheritance
and css.
>
> Also for the xml example, this looks like a path to a sort filter.
I just tried my hand at implementing one.
>
> Regards,
> Dave
>
>
> On Jul 4, 2011, at 11:20 AM, Joe Schaefer wrote:
>
> >
> >
> >
> >
> > ----- Original Message ----
> >> From: Alexandro Colorado <jz...@openoffice.org>
> >> 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/openofficeorg:
>./
>
> >> content/openofficeorg/people.html
> >>
> >> On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer
><jo...@yahoo.com>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.
> >
> > 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 <jz...@openoffice.org>
> >>>> 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 <da...@comcast.net>
> >>> 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 <da...@comcast.net>
> >>>>>>> To: ooo-dev@incubator.apache.org
> >>>>>>> Cc: ooo-commits@incubator.apache.org
> >>>>>>> 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, joes@apache.org 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
> >>
>
>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Dave Fisher <da...@comcast.net>.
OK - I have a sense how atachments work from http://www.apache.org/dev/index.html and then invoking the bookmarklet
I see that attachments are important for multiple content markups.
<div class="section-content">
{{ links.content|markdown }}
</div>
In the other example:
{% block content %}
<div id="content" class="grid_16">
<div class="section-content">{{ main.content|markdown }}
{{ table|safe }}
</div>
</div>
{% endblock %}
It is not clear how table|safe corresponds with the attached eccnmatrix.xml and eccnmatrix.xsl. Is that hidden in the view.pm?
Maybe I don't understand attachments in the Apache CMS.
I am thinking of sidenav.mdtext. Is it possible to attach this to every English language page and maintain it a single space?
Also for the xml example, this looks like a path to a sort filter.
Regards,
Dave
On Jul 4, 2011, at 11:20 AM, Joe Schaefer wrote:
>
>
>
>
> ----- Original Message ----
>> From: Alexandro Colorado <jz...@openoffice.org>
>> 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/openofficeorg: ./
>> content/openofficeorg/people.html
>>
>> On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <jo...@yahoo.com>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.
>
> 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 <jz...@openoffice.org>
>>>> 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 <da...@comcast.net>
>>> 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 <da...@comcast.net>
>>>>>>> To: ooo-dev@incubator.apache.org
>>>>>>> Cc: ooo-commits@incubator.apache.org
>>>>>>> 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, joes@apache.org 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
>>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
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 <da...@comcast.net>
> To: ooo-dev@incubator.apache.org
> 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 <jz...@openoffice.org>
> >> To: ooo-dev@incubator.apache.org
> >> 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 <jo...@yahoo.com>
>wrote:
> >>
> >>>
> >>>
> >>>
> >>>
> >>> ----- Original Message ----
> >>>> From: Alexandro Colorado <jz...@openoffice.org>
> >>>> 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/openofficeorg:
> >>> ./
> >>>> content/openofficeorg/people.html
> >>>>
> >>>> On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <joe_schaefer@yahoo.com
> >>>> 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 | 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 <jz...@openoffice.org>
> >>>>>> 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 <dave2wave@comcast.net
> >>>>
> >>>>> 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 <da...@comcast.net>
> >>>>>>>>> To: ooo-dev@incubator.apache.org
> >>>>>>>>> Cc: ooo-commits@incubator.apache.org
> >>>>>>>>> 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, joes@apache.org 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
> >>
>
>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Dave Fisher <da...@comcast.net>.
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 <jz...@openoffice.org>
>> To: ooo-dev@incubator.apache.org
>> 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 <jo...@yahoo.com> wrote:
>>
>>>
>>>
>>>
>>>
>>> ----- Original Message ----
>>>> From: Alexandro Colorado <jz...@openoffice.org>
>>>> 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/openofficeorg:
>>> ./
>>>> content/openofficeorg/people.html
>>>>
>>>> On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <joe_schaefer@yahoo.com
>>>> 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 | 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 <jz...@openoffice.org>
>>>>>> 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 <dave2wave@comcast.net
>>>>
>>>>> 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 <da...@comcast.net>
>>>>>>>>> To: ooo-dev@incubator.apache.org
>>>>>>>>> Cc: ooo-commits@incubator.apache.org
>>>>>>>>> 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, joes@apache.org 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
>>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
I implemented it so that you put the v or ^ marker
in the line which separates the header from the entries.
Enjoy.
----- Original Message ----
> From: Alexandro Colorado <jz...@openoffice.org>
> To: ooo-dev@incubator.apache.org
> 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 <jo...@yahoo.com> wrote:
>
> >
> >
> >
> >
> > ----- Original Message ----
> > > From: Alexandro Colorado <jz...@openoffice.org>
> > > 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/openofficeorg:
> > ./
> > >content/openofficeorg/people.html
> > >
> > > On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <joe_schaefer@yahoo.com
> > >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 | 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 <jz...@openoffice.org>
> > > > > 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 <dave2wave@comcast.net
> > >
> > > > 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 <da...@comcast.net>
> > > > > > >> To: ooo-dev@incubator.apache.org
> > > > > > >> Cc: ooo-commits@incubator.apache.org
> > > > > > >> 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, joes@apache.org 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
>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Alexandro Colorado <jz...@openoffice.org>.
On Mon, Jul 4, 2011 at 1:20 PM, Joe Schaefer <jo...@yahoo.com> wrote:
>
>
>
>
> ----- Original Message ----
> > From: Alexandro Colorado <jz...@openoffice.org>
> > 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/openofficeorg:
> ./
> >content/openofficeorg/people.html
> >
> > On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <joe_schaefer@yahoo.com
> >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 | 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 <jz...@openoffice.org>
> > > > 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 <dave2wave@comcast.net
> >
> > > 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 <da...@comcast.net>
> > > > > >> To: ooo-dev@incubator.apache.org
> > > > > >> Cc: ooo-commits@incubator.apache.org
> > > > > >> 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, joes@apache.org 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
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
----- Original Message ----
> From: Alexandro Colorado <jz...@openoffice.org>
> 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/openofficeorg: ./
>content/openofficeorg/people.html
>
> On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <jo...@yahoo.com>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.
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 <jz...@openoffice.org>
> > > 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 <da...@comcast.net>
> > 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 <da...@comcast.net>
> > > > >> To: ooo-dev@incubator.apache.org
> > > > >> Cc: ooo-commits@incubator.apache.org
> > > > >> 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, joes@apache.org 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
>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Alexandro Colorado <jz...@openoffice.org>.
On Mon, Jul 4, 2011 at 12:45 PM, Joe Schaefer <jo...@yahoo.com>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.
>
>
>
> ----- Original Message ----
> > From: Alexandro Colorado <jz...@openoffice.org>
> > 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 <da...@comcast.net>
> 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 <da...@comcast.net>
> > > >> To: ooo-dev@incubator.apache.org
> > > >> Cc: ooo-commits@incubator.apache.org
> > > >> 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, joes@apache.org 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
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
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.
----- Original Message ----
> From: Alexandro Colorado <jz...@openoffice.org>
> 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 <da...@comcast.net> 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 <da...@comcast.net>
> > >> To: ooo-dev@incubator.apache.org
> > >> Cc: ooo-commits@incubator.apache.org
> > >> 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, joes@apache.org 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
>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Alexandro Colorado <jz...@openoffice.org>.
On Mon, Jul 4, 2011 at 11:09 AM, Dave Fisher <da...@comcast.net> 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 <da...@comcast.net>
> >> To: ooo-dev@incubator.apache.org
> >> Cc: ooo-commits@incubator.apache.org
> >> 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, joes@apache.org 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
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
The existing conversion utils are at
https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/
All committers have commit to this section of the infra repos.
The anakia2markdown.xslt file in there has entries for table conversion.
Gluck.
----- Original Message ----
> From: Dave Fisher <da...@comcast.net>
> To: ooo-dev@incubator.apache.org
> Cc: ooo-commits@incubator.apache.org
> Sent: Mon, July 4, 2011 1:59:56 PM
> Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./
>content/openofficeorg/people.html
>
>
> On Jul 4, 2011, at 9:39 AM, Joe Schaefer wrote:
>
> <snip>
>
> >>> Perhaps you can describe "why" you need to do this?
> >>
> >> Yes. not everyone has a big screen like you. A lot of people have learned
>that
>
> >> eye fatigue is aggravated by reading long lines.
> >
> > That isn't useful feedback. Useful feedback would be something like:
> > the table columns break the text into two rows on whitespace-separated
text.
> > Or is it the reverse, that you *want* them to break into two rows (
> > in which case you have a bug because that's not what happens on my
> > screen)?
>
> OK. I could have stated my issue more carefully. There are two different
>points here. One is overall and the other is specific to this case.
>
> (1) Overall we should all agree that we design our web content to look in a
>narrow window like a laptop. Ten years ago this would be about 600px. Now I
>think we should work towards 800px. Then pages work on Tablets, Laptops, etc.
>
> (2) The intent is for the shorter data in the first three columns to not wrap
>- while the last column is very free-form. When not given widths I find that
>html layout gives too much space to this content.
>
> I now have it controlled by adding to the longest text in columns two
>and three. The fourth column only wraps for three people on my 13" laptop and
>the table looks like it was done by a professional.
>
> >
> >>> Would simply using between the text words resolve this?
> >>
> >> Perhaps, so. I'll be experimenting with the headers. But for me knowing
>pixels
>
> >> is a little easier than counting
> >
> > No that's not what I meant for you to do. What I meant was, look at the
> > longest entry in each column and replace the separating whitespace in
> > that one entry with . If your problem is columns breaking
prematurely
> > this will resolve it.
>
> Yes, this is what I did on my second try. Admittedly this moves the problem. A
>real solution would modify markdown. This is something to think about.
>
> >>>> 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?
> >>>
> >>> You do realize that the CMS allows you to do arbitrary things with the
> >> markdown,
> >>> including preprocessing it before sending it off to the templating
>system.
>
> >> Also
> >>> the python markdown parser is extensible, so if you prefer going that way
>
> >> and
> >>> contributing code to infra we can add a custom extension for everyone to
> >> use.
> >>
> >> Yes, I do. I am currently thinking about the OOo webcontent and conversion
>of
>
> >> the html.
> >
> > We have an xslt file somewhere in the conversion-utilities directory
> > that converts tables to markdown-style tables, if you decide to go that way
> > (and I strongly recommend you do). It's currently embedded in the
> > anakia stuff but can easily be extracted.
>
> Yes. A pointer to existing scripts is great. If you would give me the full
>repos path I'll take a look this week.
>
> You may have noticed that we've started with a webcontent fetch in
>ooo/trunk/tools/dev/.
>
> >> There will be thousand of pages, but hopefully not too many patterns.
> >>
> >>
> >>
> >>>
> >>>>
> >>>> Otherwise I really don't see why it's wrong to have the html table
>here.
> >>>
> >>> If you had examined the content of the table you might have noticed how
> >> bloody
> >>
> >>> awful
> >>> the html was (filled with unmatched tags). What you have now is far more
>
> >>> maintainable
> >>> in a collaborative context- humans make terrible html parsers.
> >>
> >> Agreed. Not everyone has written lexers and parsers.
> >>
> >> I'm just frustrated by the movement of the controls.
> >
> > Change happens. ;-)
>
> And when two committers are in the same place discussion happens for all to
>see!
>
> Regards,
> Dave
>
>
>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Dave Fisher <da...@comcast.net>.
On Jul 4, 2011, at 9:39 AM, Joe Schaefer wrote:
<snip>
>>> Perhaps you can describe "why" you need to do this?
>>
>> Yes. not everyone has a big screen like you. A lot of people have learned that
>> eye fatigue is aggravated by reading long lines.
>
> That isn't useful feedback. Useful feedback would be something like:
> the table columns break the text into two rows on whitespace-separated text.
> Or is it the reverse, that you *want* them to break into two rows (
> in which case you have a bug because that's not what happens on my
> screen)?
OK. I could have stated my issue more carefully. There are two different points here. One is overall and the other is specific to this case.
(1) Overall we should all agree that we design our web content to look in a narrow window like a laptop. Ten years ago this would be about 600px. Now I think we should work towards 800px. Then pages work on Tablets, Laptops, etc.
(2) The intent is for the shorter data in the first three columns to not wrap - while the last column is very free-form. When not given widths I find that html layout gives too much space to this content.
I now have it controlled by adding to the longest text in columns two and three. The fourth column only wraps for three people on my 13" laptop and the table looks like it was done by a professional.
>
>>> Would simply using between the text words resolve this?
>>
>> Perhaps, so. I'll be experimenting with the headers. But for me knowing pixels
>> is a little easier than counting
>
> No that's not what I meant for you to do. What I meant was, look at the
> longest entry in each column and replace the separating whitespace in
> that one entry with . If your problem is columns breaking prematurely
> this will resolve it.
Yes, this is what I did on my second try. Admittedly this moves the problem. A real solution would modify markdown. This is something to think about.
>>>> 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?
>>>
>>> You do realize that the CMS allows you to do arbitrary things with the
>> markdown,
>>> including preprocessing it before sending it off to the templating system.
>> Also
>>> the python markdown parser is extensible, so if you prefer going that way
>> and
>>> contributing code to infra we can add a custom extension for everyone to
>> use.
>>
>> Yes, I do. I am currently thinking about the OOo webcontent and conversion of
>> the html.
>
> We have an xslt file somewhere in the conversion-utilities directory
> that converts tables to markdown-style tables, if you decide to go that way
> (and I strongly recommend you do). It's currently embedded in the
> anakia stuff but can easily be extracted.
Yes. A pointer to existing scripts is great. If you would give me the full repos path I'll take a look this week.
You may have noticed that we've started with a webcontent fetch in ooo/trunk/tools/dev/.
>> There will be thousand of pages, but hopefully not too many patterns.
>>
>>
>>
>>>
>>>>
>>>> Otherwise I really don't see why it's wrong to have the html table here.
>>>
>>> If you had examined the content of the table you might have noticed how
>> bloody
>>
>>> awful
>>> the html was (filled with unmatched tags). What you have now is far more
>>> maintainable
>>> in a collaborative context- humans make terrible html parsers.
>>
>> Agreed. Not everyone has written lexers and parsers.
>>
>> I'm just frustrated by the movement of the controls.
>
> Change happens. ;-)
And when two committers are in the same place discussion happens for all to see!
Regards,
Dave
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
----- Original Message ----
> From: Dave Fisher <da...@comcast.net>
> To: ooo-dev@incubator.apache.org
> Cc: ooo-commits@incubator.apache.org
> Sent: Mon, July 4, 2011 12:30:39 PM
> Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./
>content/openofficeorg/people.html
>
>
> On Jul 4, 2011, at 9:17 AM, Joe Schaefer wrote:
>
> > ----- Original Message ----
> >
> >> From: Dave Fisher <da...@comcast.net>
> >> To: ooo-dev@incubator.apache.org
> >> Cc: ooo-commits@incubator.apache.org
> >> Sent: Mon, July 4, 2011 12:09:53 PM
> >> Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg:
>./
>
> >> content/openofficeorg/people.html
> >>
> >>
> >> 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.
> >
> > Perhaps you can describe "why" you need to do this?
>
> Yes. not everyone has a big screen like you. A lot of people have learned that
>eye fatigue is aggravated by reading long lines.
That isn't useful feedback. Useful feedback would be something like:
the table columns break the text into two rows on whitespace-separated text.
Or is it the reverse, that you *want* them to break into two rows (
in which case you have a bug because that's not what happens on my
screen)?
> > Would simply using between the text words resolve this?
>
> Perhaps, so. I'll be experimenting with the headers. But for me knowing pixels
>is a little easier than counting
No that's not what I meant for you to do. What I meant was, look at the
longest entry in each column and replace the separating whitespace in
that one entry with . If your problem is columns breaking prematurely
this will resolve it.
>
> >> 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?
> >
> > You do realize that the CMS allows you to do arbitrary things with the
>markdown,
> > including preprocessing it before sending it off to the templating system.
>Also
> > the python markdown parser is extensible, so if you prefer going that way
>and
> > contributing code to infra we can add a custom extension for everyone to
>use.
>
> Yes, I do. I am currently thinking about the OOo webcontent and conversion of
>the html.
We have an xslt file somewhere in the conversion-utilities directory
that converts tables to markdown-style tables, if you decide to go that way
(and I strongly recommend you do). It's currently embedded in the
anakia stuff but can easily be extracted.
>
> There will be thousand of pages, but hopefully not too many patterns.
>
>
>
> >
> >>
> >> Otherwise I really don't see why it's wrong to have the html table here.
> >
> > If you had examined the content of the table you might have noticed how
>bloody
>
> > awful
> > the html was (filled with unmatched tags). What you have now is far more
> > maintainable
> > in a collaborative context- humans make terrible html parsers.
>
> Agreed. Not everyone has written lexers and parsers.
>
> I'm just frustrated by the movement of the controls.
Change happens. ;-)
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Dave Fisher <da...@comcast.net>.
On Jul 4, 2011, at 9:17 AM, Joe Schaefer wrote:
> ----- Original Message ----
>
>> From: Dave Fisher <da...@comcast.net>
>> To: ooo-dev@incubator.apache.org
>> Cc: ooo-commits@incubator.apache.org
>> Sent: Mon, July 4, 2011 12:09:53 PM
>> Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./
>> content/openofficeorg/people.html
>>
>>
>> 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.
>
> Perhaps you can describe "why" you need to do this?
Yes. not everyone has a big screen like you. A lot of people have learned that eye fatigue is aggravated by reading long lines.
> Would simply using between the text words resolve this?
Perhaps, so. I'll be experimenting with the headers. But for me knowing pixels is a little easier than counting
>> 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?
>
> You do realize that the CMS allows you to do arbitrary things with the markdown,
> including preprocessing it before sending it off to the templating system. Also
> the python markdown parser is extensible, so if you prefer going that way and
> contributing code to infra we can add a custom extension for everyone to use.
Yes, I do. I am currently thinking about the OOo webcontent and conversion of the html.
There will be thousand of pages, but hopefully not too many patterns.
>
>>
>> Otherwise I really don't see why it's wrong to have the html table here.
>
> If you had examined the content of the table you might have noticed how bloody
> awful
> the html was (filled with unmatched tags). What you have now is far more
> maintainable
> in a collaborative context- humans make terrible html parsers.
Agreed. Not everyone has written lexers and parsers.
I'm just frustrated by the movement of the controls.
Regards,
Dave
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
----- Original Message ----
> From: Dave Fisher <da...@comcast.net>
> To: ooo-dev@incubator.apache.org
> Cc: ooo-commits@incubator.apache.org
> Sent: Mon, July 4, 2011 12:09:53 PM
> Subject: Re: svn commit: r792168 - in /websites/production/openofficeorg: ./
>content/openofficeorg/people.html
>
>
> 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.
Perhaps you can describe "why" you need to do this?
Would simply using between the text words resolve this?
>
> 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?
You do realize that the CMS allows you to do arbitrary things with the markdown,
including preprocessing it before sending it off to the templating system. Also
the python markdown parser is extensible, so if you prefer going that way and
contributing code to infra we can add a custom extension for everyone to use.
>
> Otherwise I really don't see why it's wrong to have the html table here.
If you had examined the content of the table you might have noticed how bloody
awful
the html was (filled with unmatched tags). What you have now is far more
maintainable
in a collaborative context- humans make terrible html parsers.
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Dave Fisher <da...@comcast.net>.
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.
Regards,
Dave
>
>
> ----- Original Message ----
>> From: Dave Fisher <da...@comcast.net>
>> To: ooo-dev@incubator.apache.org
>> Cc: ooo-commits@incubator.apache.org
>> 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, joes@apache.org 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>
>>>
>>>
>>
>>
Re: svn commit: r792168 - in /websites/production/openofficeorg: ./ content/openofficeorg/people.html
Posted by Joe Schaefer <jo...@yahoo.com>.
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.
----- Original Message ----
> From: Dave Fisher <da...@comcast.net>
> To: ooo-dev@incubator.apache.org
> Cc: ooo-commits@incubator.apache.org
> 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, joes@apache.org 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>
> >
> >
>
>