are the input file schema/structure of piecrust1 (php) and piecrust2(python) - the same/compatible?

[zaxebo1]

if i have written my markup input in "piecrust2" ,which is in python ; then are the input file structure of "piecrust2" and "piecrust1"(in PHP) are compatible enough that i get the similar result from pirecrust1 and piecrust2 with same markup?

ie, I mean to say that in case of cheap PHP webhosts, can i deploy my piecrust2 input files to piecrust1 on PHP webhost, and get it dynamically rendered as a CMS, not as a static website generator.

Thanks in advance

[zaxebo1]

are there any hiccups in this thinking?

[zaxebo1]

if this piecrust1(PHP) and piecrust2(python) input compatibility does not work out, THEN probably i will have to port piecrust2 to haxe language (http://haxe.org). If we write a program in haxe, then i can get that program compiled to PHP, python3, java,C#, nodejs, C++ - all from single source code. Then i will get ultimate deployment . CMS running on any type of language webhost and static website generator too . Just thinking!
http://haxe.org/documentation/introduction/compiler-targets.html
https://en.wikipedia.org/wiki/HaXe

[ludovicchabant]

The input structures are not totally compatible, no. See the second part of this documentation page, but basically the biggest difference is that PieCrust1 mixes up all your assets with the rest of the special folders. That made it cumbersome to manage assets when asset pipelines like Grunt and Bower started getting popular, so in PieCrust2 all that stuff is in an assets folder.

I don't know how well Haxe works so it would be fun to try that, but most cheap webhosts started supporting Python a few years ago, so you could just run PieCrust2 as a CMS directly, no? Or are you tied to PHP one way or another? Granted, most cheap webhosts only support Python 2.7 so I would have to look at backwards compatibility, though.