11 http://groups.google.com/group/google-appengine/browse_frm/thread/f48cf6099973aef5/c28cd6934dd72457 |
11 http://groups.google.com/group/google-appengine/browse_frm/thread/f48cf6099973aef5/c28cd6934dd72457 |
12 ] |
12 ] |
13 |
13 |
14 * Why does not CubicWeb have a template language ? |
14 * Why does not CubicWeb have a template language ? |
15 |
15 |
16 It does. Actually, you can use your preferred template language if you |
16 There are enough template languages out there. You can use your |
17 want. [explain how to use a template language] |
17 preferred template language if you want. [explain how to use a |
|
18 template language] |
18 |
19 |
19 `CubicWeb` does not define its own templating language as this was |
20 `CubicWeb` does not define its own templating language as this was |
20 not our goal and emphasize. Based on our experience, we realized that |
21 not our goal. Based on our experience, we realized that |
21 we could gain productivity by letting designers use design tools |
22 we could gain productivity by letting designers use design tools |
22 and developpers develop without the use of the templating language |
23 and developpers develop without the use of the templating language |
23 as an intermediary that could not be anyway efficient for both parties. |
24 as an intermediary that could not be anyway efficient for both parties. |
24 Python is the templating language that we use in `CubicWeb`, but again, |
25 Python is the templating language that we use in `CubicWeb`, but again, |
25 it does not prevent you from using a templating language. |
26 it does not prevent you from using a templating language. |
26 |
27 |
27 The reason template languages are not used in this book is that |
28 The reason template languages are not used in this book is that |
28 experience has proved us that using pure python was more efficient. |
29 experience has proved us that using pure python was less cumbersome. |
29 |
30 |
30 * Why do you think using pure python is better than using a template language ? |
31 * Why do you think using pure python is better than using a template language ? |
31 |
32 |
32 Python is an Object Oriented Programming language and as such it |
33 Python is an Object Oriented Programming language and as such it |
33 already provides a consistent and strong architecture and syntax |
34 already provides a consistent and strong architecture and syntax |
34 a templating language would not reach. |
35 a templating language would not reach. |
35 |
36 |
36 When doing development, you need a real language and template |
37 When doing development, you need a real language and template |
37 languages are not real language. |
38 languages are not real languages. |
38 |
39 |
39 Using Python enables developing applications for which code is |
40 Using Python enables developing applications for which code is |
40 easier to maintain with real functions/classes |
41 easier to maintain with real functions/classes |
41 without the need of learning a new dialect. By using Python, |
42 without the need of learning a new dialect. By using Python, |
42 we use standard OOP techniques and this is a key factor in a |
43 we use standard OOP techniques and this is a key factor in a |
70 |
71 |
71 That RQL language is what is going to make a difference with django- |
72 That RQL language is what is going to make a difference with django- |
72 like frameworks for several reasons. |
73 like frameworks for several reasons. |
73 |
74 |
74 1. accessing data is *much* easier with it. One can write complex |
75 1. accessing data is *much* easier with it. One can write complex |
75 queries with RQL that would just be impossible to define or unreadable |
76 queries with RQL that would be tedious to define and hard to maintain |
76 using an object/filter suite of method calls. |
77 using an object/filter suite of method calls. |
77 |
78 |
78 2. it offers an abstraction layers that allows to have a single |
79 2. it offers an abstraction layer allowing your applications to run |
79 framework that runs on multiple back-ends. We have not published the |
80 on multiple back-ends. That means not only various SQL backends |
80 SQL backend yet (still working on separating it clearly from other |
81 (postgresql, sqlite, mysql), but also multiple databases at the |
81 backends), but we already have components (pieces of schema and views) |
82 same time, and also non-SQL data stores like LDAP directories and |
82 that run both on SQL and AppEngine. |
83 subversion/mercurial repositories (see the `vcsfile` |
|
84 component). Google App Engine is yet another supported target for |
|
85 RQL. |
83 |
86 |
84 [copy answer from forum, explain why similar to sparql and why better |
87 [copy answer from forum, explain why similar to sparql and why better |
85 than django and SQL] |
88 than django and SQL] |
86 |
89 |
87 * which ajax library |
90 * which ajax library |