On Tue, Jul 29, 2014 at 4:29 PM, Emanuele <emanuel...@gmail.com> wrote:

> Alexandro Colorado wrote:
> > Mdtext is not a logical structure but a presentation structure which
> > basically restrict the development of mantainable websites because it
> > doesnt allow the modification through CSS or JS.
>
> hmm...
> Probably we are looking at the "problem" from two very different
> perspectives.
> Markdown allows to define styles and ids in the markup.
> It allows to use HTML (provided you don't put markdown inside html
> blocks, that's query a limitations at times, but it can be worked
> around) so you can add additional styles.
> Yes, it doesn't allow to add classes or ids to certain elements (e.g. ul
> and tables are the two I know for sure). This could be worked around
> using the CMS.
>
> > The structure there should have been something like a JSON string
> > carrying the values for country, link, state, localization, Javascript
> > could then parse that data, and put it on some table structure and
> > loop through it.
> > Something like this:
> ​​
> http://blog.andremakram.com/?p=7
> >
> Sorry, I probably missed a piece of discussion, so I hope you don't mind
> a question: why do you want use a JSON strings to build a table that is
> already built in HTML or markdown? (Genuine question.)
>

​JSON or XML is a datatype source, that has no presentation defined. For me
Markdown is same as HTML, it's formated data that can't be moified that
easily (change an HTML table into a list for example). XML, JSON are
datatypes that are builted to be consumed and presented into a different
presentations (take ODF for example, or SVG). ​


> I mean: I used in the download page example a json-like block, because
> the resulting table was an expansion of the block (multiplied by the
> number of languages IIRC), but in that case the json string and the
> table would be a "1:1" match (i.e. any cell of the table would require a
> corresponding entry in the json array), so I can't see exactly the
> advantage of one against the other.
>

​Basically take the presentation out of the equation, also making it more
easy to maintain. I gave you an example of how it can play here.​
http://andremakram.com/blog/sourcecode/html_table_js_json/

If you ever worked with bash scripts (sed, awk, variable expansions, etc),
having serialized data is much simpler to process like this than with an
HTML file which could be a pain to get the right transformation.



>
> Emanuele
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Reply via email to