[web2py] Re: short term roadmap
About point 4 of the list it's important, imho, to have an html scaffolding
that fits, through css classes, to our needs. A solution could be to change
the html structure by using javascript.
For example we could obtain the dropdown auth navbar by inserting this code
to the bottom of "layout.html" in bootstrap menu script section:
//-//
var newNavbar = jQuery('');
var newNavbarDropdown = jQuery('');
var dropdownMenu = jQuery('');
var dropdownTitle = ($.trim($('.auth_navbar').text().split('[')[0])).
length?$.trim($('.auth_navbar').text().split('[')[0]):'Welcome'
var icons = ['icon-off', 'icon-user', 'icon-lock'];
var newNavbarElements = jQuery('.auth_navbar').children('a').each(
function(index){
$(this).text(' '+$(this).text()).appendTo(dropdown).prepend('').wrap('');
});
newbardropdown.prepend(''+dropdownTitle+''
);
jQuery('#navbar').replaceWith(newnavbar.append(newbardropdown.append(
dropdown)));
//-//
In other words, in some circumstances, only the css is not enough. My
proposal to avoid backward incompatibility is to build a javascript
function or a js functions library to adequate the html provided from
python code to the chosen css framework (skeleton, bootstrap and so on).
What do you think?
Il giorno domenica 9 settembre 2012 01:37:55 UTC+2, Massimo Di Pierro ha
scritto:
>
> 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] Re: short term roadmap
About point 4 of the list it's important, imho, to have an html scaffolding
that fits, through css classes, to our needs. A solution could be to change
the html structure by using javascript.
For example, we could obtain the dropdown auth navbar by inserting this
code to the bottom of "layout.html" in the section that includes bootstrap
menu script:
//-//
var newNavbar = jQuery('');
var newNavbarDropdown = jQuery('');
var dropdownMenu = jQuery('');
var dropdownTitle =
($.trim($('.auth_navbar').text().split('[')[0])).length?$.trim($('.auth_navbar').text().split('[')[0]):'Welcome'
var icons = ['icon-off', 'icon-user', 'icon-lock'];
var newNavbarElements =
jQuery('.auth_navbar').children('a').each(function(index){
$(this).text('
'+$(this).text()).appendTo(dropdownMenu).prepend('').wrap('');
});
newNavbarDropdown.prepend(''+dropdownTitle+'');
jQuery('#navbar').replaceWith(newNavbar.append(newNavbarDropdown.append(dropdownMenu)));
//-//
In other words, in some circumstances, only the css is not enough. My
proposal to avoid backward incompatibility is to build a javascript
function or a js functions library to adequate the html provided from
python code to the chosen css framework (skeleton, bootstrap and so on).
What do you think?
Il giorno domenica 9 settembre 2012 01:37:55 UTC+2, Massimo Di Pierro ha
scritto:
>
> 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] Re: short term roadmap
I need to see a working example. Can you email a sample new welcome app or
patch to the existing one?
On Sunday, 9 September 2012 18:53:05 UTC-5, Paolo Caruccio wrote:
>
> About point 4 of the list it's important, imho, to have an html
> scaffolding that fits, through css classes, to our needs. A solution could
> be to change the html structure by using javascript.
> For example, we could obtain the dropdown auth navbar by inserting this
> code to the bottom of "layout.html" in the section that includes bootstrap
> menu script:
>
>
> //-//
> var newNavbar = jQuery('');
> var newNavbarDropdown = jQuery('');
> var dropdownMenu = jQuery('');
> var dropdownTitle =
> ($.trim($('.auth_navbar').text().split('[')[0])).length?$.trim($('.auth_navbar').text().split('[')[0]):'Welcome'
> var icons = ['icon-off', 'icon-user', 'icon-lock'];
> var newNavbarElements =
> jQuery('.auth_navbar').children('a').each(function(index){
>$(this).text('
> '+$(this).text()).appendTo(dropdownMenu).prepend(' class="'+icons[index]+'">').wrap('');
> });
> newNavbarDropdown.prepend(' class="dropdown-toggle" href="#">'+dropdownTitle+' class="caret">');
>
> jQuery('#navbar').replaceWith(newNavbar.append(newNavbarDropdown.append(dropdownMenu)));
>
> //-//
>
> In other words, in some circumstances, only the css is not enough. My
> proposal to avoid backward incompatibility is to build a javascript
> function or a js functions library to adequate the html provided from
> python code to the chosen css framework (skeleton, bootstrap and so on).
> What do you think?
>
> Il giorno domenica 9 settembre 2012 01:37:55 UTC+2, Massimo Di Pierro ha
> scritto:
>>
>> 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] Re: short term roadmap
For 1 & 2, if the only remote repository type being considered is Git, then using hg-git is probably ideal since it'll support both hg and git locally and working with remote git repo's. I would like to work on this. Does anyone else have interest / spare cycles to help implement this support? Also, any feedback as to how the interface should be designed for all these actions? Ie, do we keep all remote actions on the site page and then specific local actions within the app edit screens? Andrew On Saturday, September 8, 2012 6:37:55 PM UTC-5, Massimo Di Pierro wrote: > > 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] Re: short term roadmap
+1 On Tuesday, 11 September 2012 11:18:00 UTC-5, Andrew wrote: > > For 1 & 2, if the only remote repository type being considered is Git, > then using hg-git is probably ideal since it'll support both hg and git > locally and working with remote git repo's. > > I would like to work on this. Does anyone else have interest / spare > cycles to help implement this support? > > Also, any feedback as to how the interface should be designed for all > these actions? Ie, do we keep all remote actions on the site page and then > specific local actions within the app edit screens? > > Andrew > > On Saturday, September 8, 2012 6:37:55 PM UTC-5, Massimo Di Pierro wrote: >> >> 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] Re: short term roadmap
I think the first thing to to would be to create a module that implements the features we want. The logic should not be in the admin actions. I think we need a general purpose way to call scripts from apps (in this case admin) that run in background and communicate with them. I am working on this mechanism. On Tuesday, 11 September 2012 11:18:00 UTC-5, Andrew wrote: > > For 1 & 2, if the only remote repository type being considered is Git, > then using hg-git is probably ideal since it'll support both hg and git > locally and working with remote git repo's. > > I would like to work on this. Does anyone else have interest / spare > cycles to help implement this support? > > Also, any feedback as to how the interface should be designed for all > these actions? Ie, do we keep all remote actions on the site page and then > specific local actions within the app edit screens? > > Andrew > > On Saturday, September 8, 2012 6:37:55 PM UTC-5, Massimo Di Pierro wrote: >> >> 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] Re: short term roadmap
> > > On Tue, Sep 11, 2012 at 6:48 PM, Massimo Di Pierro wrote: > I think we need a general purpose way to call scripts from apps (in this > case admin) that run in background and communicate with them. I am working > on this mechanism. > Can't wait to see this + hg/git support! I can help with testing. Marin --
