Re: [web2py] short term roadmap

[Andrew W]

Great idea, allowing a core set of options, and add your own as well.
I've been meaning to have a look at Martin's bootstrap app, it would fit 
into this approach -  Having more than one valid option/approach.

On Friday, September 14, 2012 8:43:27 AM UTC+12, rochacbruno wrote:
>
> also it will need on admin BUTTON('update scaffold list') and in command 
> line web2py.py -S updatescaffold 

-- 

Re: [web2py] short term roadmap

[Bruno Rocha]

also it will need on admin BUTTON('update scaffold list') and in command
line web2py.py -S updatescaffold

-- 

Re: [web2py] short term roadmap

[Bruno Rocha]

I would like to have a repo of scaffold apps and a command line tool +
/admin tool to checkout

ADMIN -> create new app -> SELECT(*['simple', 'bootstrap', 'foundation',
'ecommerce', 'tuned',..long list])

and on command line

>>>python web2py.py -S newappname*|*foundation
>>> downloading 'foundation' scaffold app from
github.com/web2py/foundation..
>>> unpacking.
>>> done! WELCOME TO WEB2PY shell
>>>

-- 

Re: [web2py] short term roadmap

[Michele Comitini]

I think that welcome app should be changed to a very simple hello
world type example.
Then welcome app become a project on its own, with latest stable
version always included in web2py distribution.
Welcome app would have its roadmap and milestones in parallel to
web2py but without strict synchronization.

Advantages would be:
 - a feature rich and easy cloneable welcome app, useful to start new
projects based on it by anyone and lighten the release of new web2py
framework versions;
- a better backward compatibility test, since welcome app is developed
at its own pace;
- separation of issues that would be addressed by the welcome app
project and by web2py;

The issues with presentation (css, html, js) are complex and distinct
from the core of the framework as it is now they add more issues to be
solved when a major release is on arrival.

Indeed in the long run, the welcome app could become more important
and popular than web2py framework.

What do you think?

mic


2012/9/9 Massimo DiPierro :
> I have been speaking with some friends and heavy web2py users and we agree
> that the following issue need to be addressed:
>
> 1) Improve Mercurial and Git support. Currently Git+web2py allows "clone"
> and "push" whirl Hg+web2py allows "commit", "status" and "revert". I think
> we need an abstraction layer that allows "clone", "push", "commit",
> "status", "revert", and "pull" with both the version control system (with a
> preference for Git). I think we need an abstraction layer on top of both VCS
> even if for now we may support only one of them.
>
> 2) Handle gthub callback so that a push to github triggers a local web2py
> pull (for testing)
>
> 3) make it easier to run tests and manage databases (rename, backup, etc) at
> the click of a button.
>
> 4) Bootstrap looks great but it is not consistent throughout the welcome
> app. The idea is that this should be edited in web2py.css instead of any
> python code to allow backwards compatibility. Also we should avoid changing
> bootstrap.css so that we can just drop-in new versions of bootstrap, and or
> bootswatches. So we need someone with good CSS skills. It shouldn't be too
> much extra work to make it look great out of the box.
>
> 5) Port admin on top of bootstrap (while preserving the artwork).
>
>
> If you want to work on any of these topics, there may be funding available.
> I think 1) should be a priority for web2py 2.1 or 2.2.
>
>
>
> P.S. Friends have suggested looking to the following links:
>
> Here are some issues and examples of what is possible from
> wrapbootstrap.com templates:
> 1. Web2py forms: they are using no styling webkit (see
> registration/login/password reset). (Example:
> http://wbpreview.com/previews/WB00U99JJ/login.html
> 2. Navbar has "login/logout/password" which seems to be styled
> differently that the other menu items. (Nice dropdown example:
> http://wbpreview.com/previews/WB0087188/account.html)
> 3. Form Validation: would be nice to use bootstrap form validation
> perhaps with popovers overriding of the the redflash for incomplete
> forms.  (Example:
> http://wbpreview.com/previews/WB0F35928/form-validation.html )
> 4. Notifications: Use Bootstrap notifications for flash, overriding
> the web2py growl notifications. (Lot's of options here:
> http://wbpreview.com/previews/WB0881879/noty.html)
>
>
>
> --
>
>
>

-- 

Re: [web2py] short term roadmap

[Ezugworie Ikechukwu]

Hello, I don't av the capacity to implement this on web2py yet but I think
this would be a cool
(optional) feature for tables if doesn't already exist.
 I picked it up from a thread by smogzer  :Stream
Updates with Server-Sent Events.posted On Sun, Sep 9, 2012 at 11:00 AM
http://www.html5rocks.com/en/tutorials/eventsource/basics/

Thanks
Ikechukwu
On Sun, Sep 9, 2012 at 8:12 PM, Andrew  wrote:

> Massimo,
>
> As web2py picks up higher adoption and enhancement requests and bug
> reports increase do you have any thoughts / desires for agile or
> distributed development management?
>
> Would you consider something like 
> Jiraif Web2py can get 
> qualified as an approved open-source project with free
> hosting? It's got issue tracking, agile project management for sprints /
> releases as well as plugins to report bugs straight from the browser with
> screenshot support.
>
> In any case, some system regardless of whether or not it's Jira might be
> useful to assist with release management / feature prioritization etc.
>
> Regards,
> Andrew
>
>
> On Saturday, September 8, 2012 7:29:19 PM UTC-5, Massimo Di Pierro wrote:
>>
>> While this is a possibility, it may be easier if people publicly sponsor
>> features they want and pay directly the developer who gets it done.
>>
>> Massimo
>>
>> On Saturday, 8 September 2012 18:59:28 UTC-5, Ovidio Marinho wrote:
>>>
>>> I think we need to come together and make donations of at least U.S.
>>> 10:00 U.S. dollars to fund the changes. The community web2py will be
>>> happier, harder and making the job easier.
>>>
>>>
>>>
>>>Ovidio Marinho Falcao Neto
>>> Web Developer
>>>  ovid...@gmail.com
>>>   ovidio...@itjp.net.br
>>>  ITJP - itjp.net.br
>>>83   8826 9088 - Oi
>>>83   9334 0266 - Claro
>>> Brasil
>>>
>>>
>>>
>>>
>>> 2012/9/8 Massimo DiPierro 
>>>
 I have been speaking with some friends and heavy web2py users and we
 agree that the following issue need to be addressed:

 1) Improve Mercurial and Git support. Currently Git+web2py allows
 "clone" and "push" whirl Hg+web2py allows "commit", "status" and "revert".
 I think we need an abstraction layer that allows "clone", "push", "commit",
 "status", "revert", and "pull" with both the version control system (with a
 preference for Git). I think we need an abstraction layer on top of both
 VCS even if for now we may support only one of them.

 2) Handle gthub callback so that a push to github triggers a local
 web2py pull (for testing)

 3) make it easier to run tests and manage databases (rename, backup,
 etc) at the click of a button.

 4) Bootstrap looks great but it is not consistent throughout the
 welcome app. The idea is that this should be edited in web2py.css instead
 of any python code to allow backwards compatibility. Also we should
 avoid changing bootstrap.css so that we can just drop-in new versions
 of bootstrap, and or bootswatches. So we need someone with good CSS skills.
 It shouldn't be too much extra work to make it look great out of the box.

 5) Port admin on top of bootstrap (while preserving the artwork).


 If you want to work on any of these topics, there may be funding
 available. I think 1) should be a priority for web2py 2.1 or 2.2.



 P.S. Friends have suggested looking to the following links:

 Here are some issues and examples of what is possible from
 wrapbootstrap.com templates:
 1. Web2py forms: they are using no styling webkit (see
 registration/login/password reset). (Example:
 http://wbpreview.com/previews/**WB00U99JJ/login.html
 2. Navbar has "login/logout/password" which seems to be styled
 differently that the other menu items. (Nice dropdown example:
 http://wbpreview.com/previews/**WB0087188/account.html
 )
 3. Form Validation: would be nice to use bootstrap form validation
 perhaps with popovers overriding of the the redflash for incomplete
 forms.  (Example:
 http://wbpreview.com/previews/**WB0F35928/form-validation.html
 ** )
 4. Notifications: Use Bootstrap notifications for flash, overriding
 the web2py growl notifications. (Lot's of options here:
 http://wbpreview.com/previews/**WB0881879/noty.html
 )



  --




>>>
>>>  --
>
>
>
>

-- 

Re: [web2py] short term roadmap

[Andrew]

Massimo,

As web2py picks up higher adoption and enhancement requests and bug reports 
increase do you have any thoughts / desires for agile or distributed 
development management?

Would you consider something like 
Jiraif Web2py can get 
qualified as an approved open-source project with free 
hosting? It's got issue tracking, agile project management for sprints / 
releases as well as plugins to report bugs straight from the browser with 
screenshot support. 

In any case, some system regardless of whether or not it's Jira might be 
useful to assist with release management / feature prioritization etc.

Regards,
Andrew

On Saturday, September 8, 2012 7:29:19 PM UTC-5, Massimo Di Pierro wrote:
>
> While this is a possibility, it may be easier if people publicly sponsor 
> features they want and pay directly the developer who gets it done.
>
> Massimo
>
> On Saturday, 8 September 2012 18:59:28 UTC-5, Ovidio Marinho wrote:
>>
>> I think we need to come together and make donations of at least U.S. 
>> 10:00 U.S. dollars to fund the changes. The community web2py will be 
>> happier, harder and making the job easier.
>>   
>>
>>
>>Ovidio Marinho Falcao Neto
>> Web Developer
>>  ovid...@gmail.com 
>>   ovidio...@itjp.net.br
>>  ITJP - itjp.net.br
>>83   8826 9088 - Oi
>>83   9334 0266 - Claro
>> Brasil
>>   
>>
>>
>>
>> 2012/9/8 Massimo DiPierro 
>>
>>> I have been speaking with some friends and heavy web2py users and we 
>>> agree that the following issue need to be addressed:
>>>
>>> 1) Improve Mercurial and Git support. Currently Git+web2py allows 
>>> "clone" and "push" whirl Hg+web2py allows "commit", "status" and "revert". 
>>> I think we need an abstraction layer that allows "clone", "push", "commit", 
>>> "status", "revert", and "pull" with both the version control system (with a 
>>> preference for Git). I think we need an abstraction layer on top of both 
>>> VCS even if for now we may support only one of them.
>>>
>>> 2) Handle gthub callback so that a push to github triggers a local 
>>> web2py pull (for testing)
>>>
>>> 3) make it easier to run tests and manage databases (rename, backup, 
>>> etc) at the click of a button.
>>>
>>> 4) Bootstrap looks great but it is not consistent throughout the 
>>> welcome app. The idea is that this should be edited in web2py.css instead 
>>> of any python code to allow backwards compatibility. Also we should 
>>> avoid changing bootstrap.css so that we can just drop-in new versions 
>>> of bootstrap, and or bootswatches. So we need someone with good CSS skills. 
>>> It shouldn't be too much extra work to make it look great out of the box.
>>>
>>> 5) Port admin on top of bootstrap (while preserving the artwork).
>>>
>>>
>>> If you want to work on any of these topics, there may be funding 
>>> available. I think 1) should be a priority for web2py 2.1 or 2.2.
>>>
>>>
>>>
>>> P.S. Friends have suggested looking to the following links:
>>>
>>> Here are some issues and examples of what is possible from
>>> wrapbootstrap.com templates:
>>> 1. Web2py forms: they are using no styling webkit (see
>>> registration/login/password reset). (Example:
>>> http://wbpreview.com/previews/WB00U99JJ/login.html
>>> 2. Navbar has "login/logout/password" which seems to be styled
>>> differently that the other menu items. (Nice dropdown example:
>>> http://wbpreview.com/previews/WB0087188/account.html)
>>> 3. Form Validation: would be nice to use bootstrap form validation
>>> perhaps with popovers overriding of the the redflash for incomplete
>>> forms.  (Example:
>>> http://wbpreview.com/previews/WB0F35928/form-validation.html )
>>> 4. Notifications: Use Bootstrap notifications for flash, overriding
>>> the web2py growl notifications. (Lot's of options here:
>>> http://wbpreview.com/previews/WB0881879/noty.html)
>>>
>>>
>>>
>>>  -- 
>>>  
>>>  
>>>  
>>>
>>
>>

-- 

Re: [web2py] short term roadmap

[Don_X]

The feature mentionned here :


4. Notifications: Use Bootstrap notifications for flash, overriding
the web2py growl notifications. (Lot's of options here:
http://wbpreview.com/previews/WB0881879/noty.html)

would be awesome ! .. I have a serious need for various notification types 
in different scenarios in my app ! ... how do I go about getting it 
implemented 

I will be willing to sponsor that feature if affordable ! ... please advise

Don_X

-- 

Re: [web2py] short term roadmap

[Massimo Di Pierro]

While this is a possibility, it may be easier if people publicly sponsor 
features they want and pay directly the developer who gets it done.

Massimo

On Saturday, 8 September 2012 18:59:28 UTC-5, Ovidio Marinho wrote:
>
> I think we need to come together and make donations of at least U.S. 10:00 
> U.S. dollars to fund the changes. The community web2py will be happier, 
> harder and making the job easier.
>   
>
>
>Ovidio Marinho Falcao Neto
> Web Developer
>  ovid...@gmail.com  
>   ovidio...@itjp.net.br 
>  ITJP - itjp.net.br
>83   8826 9088 - Oi
>83   9334 0266 - Claro
> Brasil
>   
>
>
>
> 2012/9/8 Massimo DiPierro >
>
>> I have been speaking with some friends and heavy web2py users and we 
>> agree that the following issue need to be addressed:
>>
>> 1) Improve Mercurial and Git support. Currently Git+web2py allows "clone" 
>> and "push" whirl Hg+web2py allows "commit", "status" and "revert". I think 
>> we need an abstraction layer that allows "clone", "push", "commit", 
>> "status", "revert", and "pull" with both the version control system (with a 
>> preference for Git). I think we need an abstraction layer on top of both 
>> VCS even if for now we may support only one of them.
>>
>> 2) Handle gthub callback so that a push to github triggers a local web2py 
>> pull (for testing)
>>
>> 3) make it easier to run tests and manage databases (rename, backup, etc) 
>> at the click of a button.
>>
>> 4) Bootstrap looks great but it is not consistent throughout the 
>> welcome app. The idea is that this should be edited in web2py.css instead 
>> of any python code to allow backwards compatibility. Also we should 
>> avoid changing bootstrap.css so that we can just drop-in new versions 
>> of bootstrap, and or bootswatches. So we need someone with good CSS skills. 
>> It shouldn't be too much extra work to make it look great out of the box.
>>
>> 5) Port admin on top of bootstrap (while preserving the artwork).
>>
>>
>> If you want to work on any of these topics, there may be funding 
>> available. I think 1) should be a priority for web2py 2.1 or 2.2.
>>
>>
>>
>> P.S. Friends have suggested looking to the following links:
>>
>> Here are some issues and examples of what is possible from
>> wrapbootstrap.com templates:
>> 1. Web2py forms: they are using no styling webkit (see
>> registration/login/password reset). (Example:
>> http://wbpreview.com/previews/WB00U99JJ/login.html
>> 2. Navbar has "login/logout/password" which seems to be styled
>> differently that the other menu items. (Nice dropdown example:
>> http://wbpreview.com/previews/WB0087188/account.html)
>> 3. Form Validation: would be nice to use bootstrap form validation
>> perhaps with popovers overriding of the the redflash for incomplete
>> forms.  (Example:
>> http://wbpreview.com/previews/WB0F35928/form-validation.html )
>> 4. Notifications: Use Bootstrap notifications for flash, overriding
>> the web2py growl notifications. (Lot's of options here:
>> http://wbpreview.com/previews/WB0881879/noty.html)
>>
>>
>>
>>  -- 
>>  
>>  
>>  
>>
>
>

-- 

Re: [web2py] short term roadmap

[Ovidio Marinho]

I think we need to come together and make donations of at least U.S. 10:00
U.S. dollars to fund the changes. The community web2py will be happier,
harder and making the job easier.



   Ovidio Marinho Falcao Neto
Web Developer
 ovidio...@gmail.com
  ovidiomari...@itjp.net.br
 ITJP - itjp.net.br
   83   8826 9088 - Oi
   83   9334 0266 - Claro
Brasil




2012/9/8 Massimo DiPierro 

> I have been speaking with some friends and heavy web2py users and we agree
> that the following issue need to be addressed:
>
> 1) Improve Mercurial and Git support. Currently Git+web2py allows "clone"
> and "push" whirl Hg+web2py allows "commit", "status" and "revert". I think
> we need an abstraction layer that allows "clone", "push", "commit",
> "status", "revert", and "pull" with both the version control system (with a
> preference for Git). I think we need an abstraction layer on top of both
> VCS even if for now we may support only one of them.
>
> 2) Handle gthub callback so that a push to github triggers a local web2py
> pull (for testing)
>
> 3) make it easier to run tests and manage databases (rename, backup, etc)
> at the click of a button.
>
> 4) Bootstrap looks great but it is not consistent throughout the
> welcome app. The idea is that this should be edited in web2py.css instead
> of any python code to allow backwards compatibility. Also we should
> avoid changing bootstrap.css so that we can just drop-in new versions
> of bootstrap, and or bootswatches. So we need someone with good CSS skills.
> It shouldn't be too much extra work to make it look great out of the box.
>
> 5) Port admin on top of bootstrap (while preserving the artwork).
>
>
> If you want to work on any of these topics, there may be funding
> available. I think 1) should be a priority for web2py 2.1 or 2.2.
>
>
>
> P.S. Friends have suggested looking to the following links:
>
> Here are some issues and examples of what is possible from
> wrapbootstrap.com templates:
> 1. Web2py forms: they are using no styling webkit (see
> registration/login/password reset). (Example:
> http://wbpreview.com/previews/WB00U99JJ/login.html
> 2. Navbar has "login/logout/password" which seems to be styled
> differently that the other menu items. (Nice dropdown example:
> http://wbpreview.com/previews/WB0087188/account.html)
> 3. Form Validation: would be nice to use bootstrap form validation
> perhaps with popovers overriding of the the redflash for incomplete
> forms.  (Example:
> http://wbpreview.com/previews/WB0F35928/form-validation.html )
> 4. Notifications: Use Bootstrap notifications for flash, overriding
> the web2py growl notifications. (Lot's of options here:
> http://wbpreview.com/previews/WB0881879/noty.html)
>
>
>
>  --
>
>
>
>

-- 

[web2py] short term roadmap

[Massimo DiPierro]

I have been speaking with some friends and heavy web2py users and we agree that 
the following issue need to be addressed:

1) Improve Mercurial and Git support. Currently Git+web2py allows "clone" and 
"push" whirl Hg+web2py allows "commit", "status" and "revert". I think we need 
an abstraction layer that allows "clone", "push", "commit", "status", "revert", 
and "pull" with both the version control system (with a preference for Git). I 
think we need an abstraction layer on top of both VCS even if for now we may 
support only one of them.

2) Handle gthub callback so that a push to github triggers a local web2py pull 
(for testing)

3) make it easier to run tests and manage databases (rename, backup, etc) at 
the click of a button.

4) Bootstrap looks great but it is not consistent throughout the welcome app. 
The idea is that this should be edited in web2py.css instead of any python code 
to allow backwards compatibility. Also we should avoid changing bootstrap.css 
so that we can just drop-in new versions of bootstrap, and or bootswatches. So 
we need someone with good CSS skills. It shouldn't be too much extra work to 
make it look great out of the box.

5) Port admin on top of bootstrap (while preserving the artwork).


If you want to work on any of these topics, there may be funding available. I 
think 1) should be a priority for web2py 2.1 or 2.2.



P.S. Friends have suggested looking to the following links:

Here are some issues and examples of what is possible from
wrapbootstrap.com templates:
1. Web2py forms: they are using no styling webkit (see
registration/login/password reset). (Example:
http://wbpreview.com/previews/WB00U99JJ/login.html
2. Navbar has "login/logout/password" which seems to be styled
differently that the other menu items. (Nice dropdown example:
http://wbpreview.com/previews/WB0087188/account.html)
3. Form Validation: would be nice to use bootstrap form validation
perhaps with popovers overriding of the the redflash for incomplete
forms.  (Example:
http://wbpreview.com/previews/WB0F35928/form-validation.html )
4. Notifications: Use Bootstrap notifications for flash, overriding
the web2py growl notifications. (Lot's of options here:
http://wbpreview.com/previews/WB0881879/noty.html)



--