dskinner / damsel-python Goto Github PK

View Code? Open in Web Editor NEW

43.0 43.0 3.0 557 KB

Markup Language featuring html outlining via css-selectors, embedded python, and extensibility.

License: MIT License

Vim Script 3.38% Python 96.62%

damsel-python's People

Contributors

Stargazers

Watchers

Forkers

andreif micheltem dsjiang

damsel-python's Issues

newline variables bomb

a variable on a line by itself doesn't work

Nested For loops with complex mixed content fail

Explicit for loops with complex mixed content fails though there are various workarounds depending on complexity, such as using list comprehensions

Please add support for Python 3.x

Great templating language! I just miss it in Py3k.

tag followed by inline func fails

when all else is missing (text, string formatters), reference py_formatter.daml in tests

ending colon always invokes python

Should check line directive before invoking python on this bit.

builtin filter for html comment blocks

Should be able to prepend to any line to create an html comment.
Should be able to prepend to any root node and the resulting children will be part of the block comment, just as filters are intended to work
Should be able to use inline to comment out a specific portion of a line

Tag Hash Order

since attributes follow the css attribute selector style, all attributes must follow id and class hashes, which i find to be more readable but could be setup for mixed ordering.

nested function calls in mixed content fail

The following will fail

%p :str(len([1,2,3]))

as py_parse doesn't keep track of how many parenthesis were opened.

provide relative include

allow include path to be relative to file, so maybe like include("./this.dmsl")

:include with conditionals fails

:include that does basic conditional and in main template is followed by a block, fails. This might not be an issue in trunk.

elipses starting text disappear

Multiline Text missing at end of document

When document has multiline plain text at end of document, it will get dropped. This is avoidable currently just by sticking a blank element below the multiline text

formatter and dict conflicts

curly braces get recognized as a formatter before a dict in statements such as for. This should never happen, ever, total goof

Feature Request: HAML Style Comments

Make the first non-whitespace character '/' at the beginning of a line indicate that the line is a comment.

Inline content too restrictive

Considering the rendering code dmsl.Template('index.dmsl').render(hello="World")

The following crashes in a template: %p Hello, { hello }

Where %p Hello, {hello} does not.

The whitespace here shouldn't matter to the parser. Also, the PEP-8 states that variables enclosed in dictionaries and tuples should have a space on both ends.

PEP-8 approves: a = { 'foo' : 'bar' } and discourages a = {'foo':'bar'} making this restriction feel unnatural.

if statements with mixed content, screwy order

if i have an unordered list and the first two items are conditional, they will end up at end of list, content thats at the top will end up at the bottom, etc

Better Error Reporting

daml on a whole could use much better error reporting with template problems, warnings, etc

Fails to build

$ python setup.py build_ext -i
running build_ext
cythoning dmsl/cdoc.pyx to dmsl/cdoc.c
building 'dmsl.cdoc' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/dmsl
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c dmsl/cdoc.c -o build/temp.linux-x86_64-2.7/dmsl/cdoc.o
dmsl/cdoc.c:8:22: error fatal: pyconfig.h: No existe el fichero o el directorio
compilación terminada.
error: command 'gcc' failed with exit status 1

Feature Request: Pretty Source Formatting

Dmsl generates some nastily formatted HTML output. Sensible newlines would be nice.

From the template:

%html
    %head
        %title Headshots Backend API Manager
    %body
        %h2 Overview
        %p This is the webservice to manage images stored within S3.
        %h2 Submit a New Thumbnail Request
        %form[action="/create"][method="post"]
            %label[for="create_form_url"] Url 
            %input[id="create_form_url"][type="text"][name="url"]
            %input[id="create_form_submit"][type="submit"][name="submit"]

DMSL generates:

<!DOCTYPE html><html><head><title>Headshots Backend API Manager</title></head><body><h2>Overview</h2><p>This is the webserive to manage images stored within S3.</p><h2>Submit a New Thumbnail Request</h2><form action="/create" method="post"><label for="create_form_url">Url</label><input id="create_form_url" type="text" name="url"></input><input id="create_form_submit" type="submit" name="submit"></input></form></body></html>

I would like for it to generate:

<!DOCTYPE html>
<html>
    <head>
        <title>Headshots Backend API Manager</title>
    </head>
    <body>
        <h2>Overview</h2>
        <p>This is the webserive to manage images stored within S3.</p>
        <h2>Submit a New Thumbnail Request</h2>
        <form action="/create" method="post">
            <label for="create_form_url">Url</label>
            <input id="create_form_url" type="text" name="url"></input>
            <input id="create_form_submit" type="submit" name="submit"></input>
        </form>
    </body>
</html>

Filters and Embedded Funcs Compete after TagHash

having a filter after a taghash competes with current functionality in _pre for embedded functions following a taghash

Tabs dont work

Im pretty sure anyways, and mixed tabs/spaces definitely dont. This should be easily rectifiable since python has string.expandtabs

includes cant be embedded in python statements

includes are currently handled in _pre.py and not in the sandbox environment, preventing dynamic use in templates

pass arg to include for limiting selection

it might be helpful to be able to pass an arg to builtin include that specifies which top-level blocks to include, ignoring the rest.

This stems from noticing a need to abstract out certain reusable blocks into seperate files for reuse in many places, but the creation of so many files with little bits of information creates confusion. Typically, it seems there is a particular page that outlines the majority of these blocks for use there, and reuse elsewhere. Workflow might be simplified with this addition as well as keeping the original work contained in its more intended usage, and removing the file cruft.

Colon Crashes Label Tag

Awesome job with this.

If you include the character ':' after some text in a label tag dmsl crashes.

%label[for="someid"] Url

is okay but

%label[for="someid"] Url:

causes dmsl to throw the error => IndexError('list index out of range',)

simple file with raise call fails

for example

cherrypy.lib.sessions.expire()
raise cherrypy.HTTPRedirect('/')

content

nested concat'd tags dont work

reference py_mixed_content.daml in tests