I am just starting to learn web2py and I want to better understand the
issue. Is the issue simply that Bootstrap 3 is not backward compatible
with v2.x and therefore we cannot use Bootstrap3 with the templates in
web2py that have been created with Bootstrap 2 ? The issue seems to be
bigger th
The use case is that you design a template application that will be
installed and edited by some businesses that use a work flow from
development to testing to staging and finally to production. Most of the
configuration values are shared in these different stages. These shared
configuration v
The use case that I have in mind is that I create a wrapper web2py
application over another web2py application that will be updated regularly
by a third party. I do not want to have to update the wrapper at each
update. The specific use case that I have in mind is that the wrapper
application
this is turning into a maintenance nightmare. This is
> against the original spirit. This is why I believe we need a new approach
> to this problem and a new library for form generation.
>
>
> Massimo
>
>
> On Saturday, 18 June 2016 07:47:42 UTC-5, Dominic Mayers wrote:
>>
t; include a special model file in the app that sets up the configuration on
> each request -- you just have to ensure that the update mechanism doesn't
> allow that file to be overwritten or deleted.
>
> Anthony
>
> On Saturday, June 18, 2016 at 11:11:25 AM UTC-4, Domin
complexity of layouts + styles, which prevent the creation of an
abstraction layer over templates similar to what we have in the case of
database structures.
On Saturday, 18 June 2016 13:29:54 UTC-4, Anthony wrote:
>
> On Saturday, June 18, 2016 at 8:47:42 AM UTC-4, Dominic Mayers wrote:
&
reply. As I am new with web2py, your help is very much appreciated. I am
still looking at the WSGI middleware option. Thank you for your guidance.
On Saturday, 18 June 2016 20:16:03 UTC-4, Anthony wrote:
>
> On Saturday, June 18, 2016 at 1:35:40 PM UTC-4, Dominic Mayers wrote:
>>
>>
es.py:
>
> from gluon.settings import global_settings
> global_settings.mysetting = 'some value'
>
> Then you can import and access the global settings from within the
> application.
>
> Anthony
>
> On Saturday, June 18, 2016 at 9:05:01 PM UTC-4, Dominic Mayers wrote:
I reply within.
On Sunday, 19 June 2016 14:35:37 UTC-4, Anthony wrote:
>
> I suppose you could put web2py in one directory, and then symlink to an
> application folder in some other directory. But it seems odd that you
> somehow don't have control over how the application code gets updated.
> T
I reply in the message.
On Sunday, 19 June 2016 20:06:30 UTC-4, Anthony wrote:
>
> On Sunday, 19 June 2016 14:35:37 UTC-4, Anthony wrote:
>>>
>>> I suppose you could put web2py in one directory, and then symlink to an
>>> application folder in some other directory. But it seems odd that you
>>>
Anthony, I am going to reply to one specific part of your last post, the
one with "I don't think the concept of wrapper application is well
defined.":
I don't think the concept of "wrapper application" is well defined. In any
case, we should probably drop that idea, as your ultimate goal is no
The problem space is in terms of wrapper applications. The original
question is can we have a wrapper [without an http request] as we can in
PHP?
I get the impression is that you plan on writing one application for use by
many customers, and that this application will be installed in many
e
On Monday, 20 June 2016 18:59:58 UTC-4, Anthony wrote:
>
> On Monday, June 20, 2016 at 3:24:46 PM UTC-4, Dominic Mayers wrote:
>>
>> Anthony, I am going to reply to one specific part of your last post, the
>> one with "I don't think the concept of wrapp
On Monday, 20 June 2016 18:59:58 UTC-4, Anthony wrote:
>
>
>>
>> I think the concept is easy to generalize to an application, to a script,
>> etc.
>>
>
> The *concept* is easy to generalize, but the *implementation* may become
> more complex as you move from a simple single-page PHP script to
On Monday, 20 June 2016 21:29:11 UTC-4, Dave S wrote:
>
>
> Perhaps my imagination is too small, but I'm failing to see a value in a
> general concept of a wrapper.
>
I am sure you have plenty of imagination. I might have said the opposite at
some point, but I said "we", meaning "me".
>
Anthony, I will be more careful with the words I use, because there can be
a discrepancy between what you receive and what I intend to say. You can
assume that I do not have any issue with you and what you say, except,
possibly at a technical or conceptual level in the area of concern. Now,
it
On Monday, 20 June 2016 23:21:45 UTC-4, Anthony wrote:
>
>
> On Monday, 20 June 2016 18:59:58 UTC-4, Anthony wrote:
>>>
>>>
I think the concept is easy to generalize to an application, to a
script, etc.
>>>
>>> The *concept* is easy to generalize, but the *implementation* m
On Tuesday, 21 June 2016 00:20:07 UTC-4, Anthony wrote:
>
> However, for a programmer, the application is what is created when we
>> create a new folder in the applications folder. A wrapper application has
>> to be an application separated, in terms of its declaration, from the
>> wrapped app
On Tuesday, 21 June 2016 01:27:05 UTC-4, Anthony wrote:
>
> You make claims about how a "wrapper application" *must* look without
>>> demonstrating *why* it must look like that.
>>>
>>
>> Yes and they are not based on any use case. They are based on what seems
>> natural. Some times, we have de
On Tuesday, 21 June 2016 00:20:07 UTC-4, Anthony wrote:
>
> I'm not saying web2py can easily handle all possible cases, and its
> execution model probably does introduce some limitations, but it would be
> easier to explore the limitations and possible workarounds with some
> concrete example
Perhaps, you already provided the answer:
wsgihandler.py is *where* you would call the entry point to your wrapper
application (and by the way, it doesn't have to be there -- you could put
it anywhere, as long as you tell your web server where it is), but the
wrapper application code itself can
On Tuesday, 21 June 2016 00:20:07 UTC-4, Anthony wrote:
>
> However, for a programmer, the application is what is created when we
>> create a new folder in the applications folder. A wrapper application has
>> to be an application separated, in terms of its declaration, from the
>> wrapped app
Can you expand on your proposal? It's not a big deal if, in the process of
being wrapped, the application becomes a plug-in. Indeed, some thing along
the line of Yii2 modules would be fine, as long as the entire application,
except the part that parses the request, but at the least every thing
I am restating the use case and the concept of wrapper application.
On Wednesday, 22 June 2016 09:00:12 UTC-4, Anthony wrote:
>
>1. I don't think this approach completely satisfies Dominic's
>requirements, as he wants the wrapper to be external to the application
>folder of the wra
I have the impression that you are saying the same thing as me, but with an
emphasis on the "unimportant". I already mentioned that it can be seen as
unimportant in a scenario where we design web2py. I prefer though to
mention that it is useful to consider the use case where we do not really
d
Is the wrapper code inside the wrapped application here?
On Thursday, 23 June 2016 00:14:36 UTC-4, Anthony wrote:
>
> The installer creates the /applications/myapp folder and puts a single
> __wrapper.py file inside the /models folder. The content of this wrapper
> file would be sufficient to
On Wednesday, 22 June 2016 23:58:47 UTC-4, Anthony wrote:
>
>
> The current idea of Anthony is to directly use wsgihandler as the wrapper
>>
>
> No, the "wrapper" would be a callable object, and it can be defined
> anywhere. wsgihandler.py is just the entry point -- you could import the
> wrapp
On Thursday, 23 June 2016 00:14:36 UTC-4, Anthony wrote:
>
>
> Regarding the comment that the flexibility to have a separate wrapper is
>> not important,
>>
>
> Unimportant for the wrapper code to be outside the application folder
> because there is a simple approach that should work fine. The
On Thursday, 23 June 2016 09:56:19 UTC-4, Anthony wrote:
>
>
> No, the "wrapper" would be a callable object, and it can be defined
>>> anywhere. wsgihandler.py is just the entry point -- you could import the
>>> wrapper in wsgihandler.py and then expose it to the web server (as in the
>>> buil
It is also important that the installer does not have to use the
application folder.
On Thursday, 23 June 2016 10:23:45 UTC-4, Anthony wrote:
The installer creates the /applications/myapp folder and puts a single
> __wrapper.py file inside the /models folder ...
> The simple fact that the
On Thursday, 23 June 2016 15:41:35 UTC-4, Anthony wrote:
>
> On Thursday, June 23, 2016 at 1:26:38 PM UTC-4, Dominic Mayers wrote:
>>
>> It is also important that the installer does not have to use the
>> application folder.
>>
>
> Unless you can identify c
You should write a self-contained document to explain your concept of
wrapper application. In this post, you try to explain the concept of
application wrapper (at the application level) in opposition to the concept
of a wrapper at the framework level. You say that I do not understand this
conce
You should write a self-contained document to explain your concept of
wrapper application. In this post, you try to explain the concept of
application wrapper (at the application level) in opposition to the concept
of a wrapper at the framework level. You say that I do not understand this
conce
You should write a self-contained document to explain your concept of
wrapper application. In this post, you try to explain the concept of
application wrapper (at the application level) in opposition to the concept
of a wrapper at the framework level. You say that I do not understand this
conce
This discussion is challenging and it shows that you are right that use
cases are useful, if only to help frame a discussion. I think that your use
case is not to pass the configuration information, but the need for a
wrapper (for pre-processing and post-processing) and it does not have the
ext
You will not agree with my comments below. Apparently, we cannot even agree
on what happened in the discussion. However, my concepts became clearer,
at the least for me, in this discussion and you pointed out ways to do
things that can be useful. So, I am thankful for all the time that you
spe
36 matches
Mail list logo
