Something like this was already implemented 4 years ago when we write a
compatibility layer between Django and web2py:
http://web2py.com/AlterEgo/default/download/document.file.08621820-64d8-4db5-a85c-569a647a4437.py
Perhaps you can take some of that code and re-adapt it.
On Monday, 2
Hello,
About webpy example, I think this is readilly possible in web2py, I mean it
just maybe a better way to structure your model declaration/defintion...
Did you try it with web2py?
Richard
On Mon, Nov 2, 2015 at 9:51 AM, Carlos Cesar Caballero Díaz <
desarro...@spicm.cfg.sld.cu> wrote:
>
Antony, thanks for your answer, there were some things I did not know
you could do, but there is just a problem with:
|
db.define_table('review',
Field('author'),
Field('valuea','int'),
Field('valueb','int'),
Field('valuec','int'),
Field('place','reference place'))
defget_review_average(row):
On Monday, November 2, 2015 at 12:21:53 PM UTC-5, Carlos Cesar Caballero
wrote:
>
> Antony, thanks for your answer, there were some things I did not know you
> could do, but there is just a problem with:
>
> db.define_table('review',
>Field('author'),
>Field('valuea', 'int'),
>
On Monday, November 2, 2015 at 9:50:34 AM UTC-5, Carlos Cesar Caballero
wrote:
>
> ok, now is not so clean, the "functions" are before the "variables"
> declarations,
>
In weppy, you have this (note the need for the @virtualfield decorator):
class Review:
author = Field()
value =
I am building a plugin for use the weppy code in web2py, It seems to
work, but need more coding and testing, I will upload it to github in a
couple of minutes.
Greetings.
El 02/11/15 a las 10:02, Richard Vézina escribió:
Hello,
About webpy example, I think this is readilly possible in
The dal is a very good piece of software, and it can done practically
everything that any orm can do, but in my opinion, the problem is not
what we can do, but how we do it, for example, we have places, and the
places have reviews, it will be something like this:
db.define_table('review',
On Saturday, October 31, 2015 at 8:23:50 PM UTC-4, Vinicius Assef wrote:
>
> The best scenario I see is defining methods to model classes.
>
> For example, centralising queries and business actions like:
> create_customer(), get_active_employees(), register_student() and so on.
>
If those are
The best scenario I see is defining methods to model classes.
For example, centralising queries and business actions like:
create_customer(), get_active_employees(), register_student() and so on.
--
Vinicius Assef
On 30 October 2015 at 12:49, Anthony wrote:
>
> Well,
> Well, the only thing that I really want right now, is a layer for object
> oriented use, something like the weppy pyDAL layer should be enough, it
> will be a impressive improvement to pydal (will convince to many users to
> use pydal and web2py)
>
What are some examples of things you
We could use object oriented modeling, we could save our objects
directly to the database, we could declare non persistent variables in
objects, we could have a better code structure in our apps, we could
maintain large models easily, we could reuse or extend model classes
easily, we don't
On Friday, October 30, 2015 at 3:10:29 PM UTC-4, Carlos Cesar Caballero
wrote:
>
> We could use object oriented modeling,
>
Yes, but the question is, what exactly does that mean to you, and how would
it improve things over the current DAL? Can you share a specific example,
possibly including
Hi Ramos,
What's your project ?
Because if you do some console, desktop or Python notebook doc.
standalone pydal is there.
But if you're looking at developing a web app or rest api
Web2py Is quite good at it and quite well integrated with pydal ;)
Or what inconvenience do you see with web2py
my inconvenients:
1 - Bootstrap, i need layout.html but dont want bootstrap. How do i get rid
of bootstrap or change it to semantic ?
Bootstrap should not be a constraint but just an add-on.
2 - web2py custom forms and tables. Are nice tools but if they dont do what
you want you will have a
Hey!
Bootstrap was never a constraint, I am removing it from every single
project and adding foundation/semantic/custom - I can't stand it.
I am also manually writing forms (everything in between of
form.custom.begin and form.custom.end) while using the power of SQLFORMs on
backend.
What do you
On Wednesday, October 28, 2015 at 11:07:42 AM UTC-4, Ramos wrote:
>
> my inconvenients:
>
> 1 - Bootstrap, i need layout.html but dont want bootstrap. How do i get
> rid of bootstrap or change it to semantic ?
> Bootstrap should not be a constraint but just an add-on.
>
How would you do it
pyDAL is the choice.
But if i use it outside web2py i need an alternative http server/rest
endpoint and something to auth clients.
What do you suggest to add to pyDAL ?
Regards
António
2015-10-22 14:56 GMT+01:00 António Ramos :
> I agree with you except for the "kept
I agree with you except for the "kept secret" because it keeps away people
that could help make it even better.
and yes, i meant pyDAL
2015-10-22 14:53 GMT+01:00 Richard Vézina :
> Do you mean pyDAL?
>
> If so, you have to consider that it is very young and may still
Do you mean pyDAL?
If so, you have to consider that it is very young and may still seems to be
web2py related which may make poeple think that they can't use it without
web2py...
I use to refer many StackOverflow asker to pyDAL as a way to solve their
issue, I guess word of mouth is not in use
19 matches
Mail list logo