Michael Feingold wrote:
>
> Thank you for the pointers. You have some pretty interesting test
> cases in your project.
Thanks. Actually most of the credit goes to the django developers, because
most of my tests are just ported versions of the django tests.
> We also have quiet a few test
Thank you for the pointers. You have some pretty interesting test
cases in your project. We also have quiet a few test cases in our unit
tests have a peek if you are interested. As to the ticket - this is an
interesting one. The scenario it refers to seems pretty clear to me I
agree with Karen's
Michael Feingold wrote:
> On Sep 23, 2:54 am, Pablo Escobar
> wrote:
>> 1. Django is Open Source. It is not a problem to find the parsing
>> algorithm
>>
> Of course it is And we did go through the code. But reverse
> engineering can show you what happens, not what the
On Sep 23, 2:54 am, Pablo Escobar wrote:
> 1. Django is Open Source. It is not a problem to find the parsing
> algorithm
>
Of course it is And we did go through the code. But reverse
engineering can show you what happens, not what the intention was
1. Django is Open Source. It is not a problem to find the parsing
algorithm
PS Anyway. I don't see any advantages of django's templates comparing
with ASP.NET MVC Views
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Tue, Sep 22, 2009 at 2:20 PM, Michael Feingold wrote:
>
> That's what we started with. It did not work out. While IronPython (as
> well as some other implementations of Python) are available in .Net,
> integrating an app written in Python with anything else written in any
That's what we started with. It did not work out. While IronPython (as
well as some other implementations of Python) are available in .Net,
integrating an app written in Python with anything else written in any
other .Net language proved to be a big challenge. You can run a Python
app on .Net
I dont know all that much about .Net but isnt the point of it that all
the .Net languages can be used together? eg using C#.Net components in
a VB.Net app and such.
So why not just use the django template language as is via IronPython
instead of trying to port it to another language?
Well, we liked the language, and it is too late anyway - it is
implemented
On Sep 22, 12:18 pm, Anton Bessonov wrote:
> Hello,
>
> if you need template engine only, then make more sence to port pure
> template engine such as jinja2. IMHO.
>
> Michael Feingold schrieb:
>
>
Hello,
if you need template engine only, then make more sence to port pure
template engine such as jinja2. IMHO.
Michael Feingold schrieb:
> I am working on NDjango project. NDjango is a port of Django template
> language to .Net. It is an open source project. If you are curious you
> can get
I am working on NDjango project. NDjango is a port of Django template
language to .Net. It is an open source project. If you are curious you
can get all information about it here: www.ndjango.org.
The reason I am posting here is that while one of our design goals is
to keep ndjango templates
11 matches
Mail list logo