Work on web.py github repo

[Tomas Schertel]

Hi guys.

I'd like to propose a community effort to close all open issues and pull requests from github repo.
By now, we have 96 open issues and 24 pull requests.
Maybe, some of the pull requests are already merged to current code and some issues are already solved. But there are issues from 3 years ago and pull requests from 2 years ago.
I'm not a "master" on git or even on python, but I offer my time to help as I can.
I don't know exactly who are the maintainers beside Anand, but maybe he could trust someone to do this kind of stuff.

I have no intention of attacking someone, but sometimes web.py looks like a hobby project, when I'd really like to see it like a more serious project.
Again, I have no intention of attacking someone. I know Aaron and Anand have done a great, great job.

[Tae Sandoval Murgan]

I was thinking the same thing. I want to make some improvements to the Form class, but first I wanted to communicate with Anand on the open issues because some of them are related to what I want to do. So, I'm willing to help, but my concerns are that I'm new to Python and I have just used frameworks, I have never involved on developing or maintaining one, so some stuff is magic for me. Besides that I'm happy to know that more people wants to continue the Aaron's work.

Cheers from Chile, and please, excuse my English.

[Tomas Schertel]

On Tuesday, 14 May 2013 17:12:51 UTC-3, Tae Sandoval Murgan wrote:

I was thinking the same thing. I want to make some improvements to the Form class, but first I wanted to communicate with Anand on the open issues because some of them are related to what I want to do. So, I'm willing to help, but my concerns are that I'm new to Python and I have just used frameworks, I have never involved on developing or maintaining one, so some stuff is magic for me. Besides that I'm happy to know that more people wants to continue the Aaron's work.

Cheers from Chile, and please, excuse my English.

I was a bit afraid of write this kind of stuff here.
But now I'm glad to see others think just like me.

[Faustino Aguilar Quirós]

I am with you!

I like the way I work with web.py, I tried to get involved with other frameworks and I could not. I know that other frameworks like Flask and Bootle are also good, even thought web.py ever leave, but I am left with web.py.

I've been using python about 3 months and I liked it. It's something I learned on my own. I'm a medical student, but I like programming and I started with php, javascript and now after python in my spare time I practice something and I think I can help.

I think it's important not to let web.py forget and that is in our hands.

I'm from Panama, excuse my English

[Steven Brown]

Love this idea!  Here is a slightly improved dropdown renderer I wrote.  It adds the capability to give classes to select options, so that you can use this jquery plugin: http://www.appelsiini.net/projects/chained
That plugin lets you set up multiple dropdowns so that when you select one, the next one gets populated with certain options depending on which one you picked.

    def render(self):
        attrs = self.attrs.copy()
        attrs['name'] = self.name
        classDefined = False
        selectionMade = False
        x = '<select %s>\n' % attrs

        for arg in self.args:
            if isinstance(arg, (tuple, list)):
                if len(arg) == 3:
                    classDefined = True
                    HTMLclass, value, desc = arg
                if len(arg) == 2:
                    value, desc = arg
            else:
                value, desc = arg, arg
           
            if self.value == str(value) and selectionMade == False:
                select_p = ' selected'
                selectionMade = True
            else: select_p = ''
            if classDefined == True: class_p = ' class="%s"' % net.websafe(HTMLclass)
            else: class_p = ''
            x += '  <option%s value="%s"%s>%s</option>\n' % (class_p, net.websafe(value), select_p, net.websafe(desc))
            classDefined = False

        x += '</select>\n'
        return x

[Tomas Schertel]

I started this thread to tell how I feel and to discuss what can we do to improve web.py.
All code should be put in github as a pull request or issue then quoted here or in a específic thread.
I propouse we start thinking of what can be done to make things better now, like documentation, github, mail list, advocacy, etc.

[Tae Sandoval Murgan]

I think the first step is to close issues. Some of them seems already
solved, but aren't closed so the project seems abandoned. We need
Anand for that, no?

The second step could be to rewrite the documentation. There's is a
lot of repeated information, and also a lot of missing information. I
think we should merge the Cookbook with the Tutorials. What do you
thing about that?

I'll work on improving the Form class this weekend, considering the
Steven's suggestion ;)

[Leandro - ProfessionalIT - Soluções em Tecnologia da Informação.]

Hi Tae,

    I think that is very interessant too, we have a "way", a standard, or conventions to create a project with web.py, a convention to create files, for example, ever init your project with a file called code.py, have a file called forms.py, have a file called render.py, put your templates in a folder called templates and your static files in a folder called static, or be, a example_project, AKA blank_project in another frameworks.

    I don't know but my first impression of web.py was: OK, it's easy, let-me free to choice, but what's the best way to create a project ? how to organize a project with subapps ? and etc.

Atenciosamente,
Leandro Severino - Professional in Information Technology.
MSN: lea...@professionalit.com.br  |  GTalk: lsev...@gmail.com | Skype: leandro-professionalit
Site: http://www.professionalit.com.br |  Blog: http://blog.professionalit.com.br | Twitter: http://twitter.com/professionalit
Mobile: (51) 9390.3511 (Claro) e (51) 8272.5841 (TIM)

 

--
You received this message because you are subscribed to the Google Groups "web.py" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webpy+un...@googlegroups.com.
To post to this group, send email to we...@googlegroups.com.
Visit this group at http://groups.google.com/group/webpy?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Shannon Cruey]

I'd suggest we start a completely new set of documentation on the wiki in github.  It's easy to edit collaboratively, and of course changes are tracked and we can all contribute a topic at a time.

I'm not sure how to turn it on, but a github owner (I'm assuming Anand?) will need to enable the wiki and set up permissions.

Notable changes I'm willing to submit:

• I made the logging of all the HTTP request information to stdout an option - my log file was filling up with low level junk.
• I've overloaded the application class in my app to be able to return many types of HTTP response codes based on different types of exceptions, instead of wrapping everything in the "internal server error" message.  I think this would be a good enhancement to the core.
• I can provide examples on redirecting calls to other modules, common ajax application scenarios, and using a config class to provide a number of extended settings useful in any project.
• Without any mods to the code, I've also got examples around the common "how do I serve another static directory" topic.  I think this would be a good tutorial for the wiki.
  

[michael kapelko]

Closing issues is the way to go.

Rewriting anything - bright idea at first, the worst idea at the second thought. Fixing documentation is a more correct approach, because it won't require hunderds of hours spent just to make it look 'the way you think is the best'. Better start small like closing issues, fixing documentation.

99.9% of contributors get tired at this stage already.

2013/5/15 Leandro - ProfessionalIT - Soluções em Tecnologia da Informação. <lea...@professionalit.com.br>

[Tae Sandoval Murgan]

On Wed, May 15, 2013 at 9:41 AM, Leandro - ProfessionalIT - Soluções
em Tecnologia da Informação. <lea...@professionalit.com.br> wrote:
>
> I don't know but my first impression of web.py was: OK, it's easy, let-me free to choice, but what's the best way to create a project ? how to organize
> a project with subapps ? and etc.

That a good example of something that should go in the
documentation... It's already there, but in a really fragmented way.
I can help taking that and merging it in just one tutorial.

[Tae Sandoval Murgan]

On Wed, May 15, 2013 at 9:51 AM, Shannon Cruey
<shanno...@cloudsidekick.com> wrote:
> I'd suggest we start a completely new set of documentation on the wiki in
> github. It's easy to edit collaboratively, and of course changes are
> tracked and we can all contribute a topic at a time.

I like that idea, I think it could be more easy for me to take all in
the website and put a clean copy (a fixed copy, no new stuff) on the
wiki, but I don't know if Anand is agree with Aaron about that:
https://github.com/webpy/webpy/issues/188 (an example of an issue that
should be closed).

> I'm not sure how to turn it on, but a github owner (I'm assuming Anand?)
> will need to enable the wiki and set up permissions.

That's the way to go.

Hey, I want almost all your improvements merged now! I'm not sure
about a config file... I'm using one right now, but I don't think it
should be a feature. Anyway, that is something that we should discuss
using the issue tracker, studying the code on a pull request ;)

[Tomas Schertel]

I'm waiting Anand to show us a route to go.
I hope he agrees with us and let us help webpy.

[Steven Brown]

I just recently started using web.py and looking at the group; is he pretty active usually?

[Tomas Schertel]

On Wednesday, 15 May 2013 23:56:42 UTC-3, Steven Brown wrote:

I just recently started using web.py and looking at the group; is he pretty active usually?

If you take a look at group info page, you'll see that Anand is the most active user in grup.
But I haven't seen he in a while.

Also you'll see that this group has 1987 members. And just a few are really active or come often to see messages.

[Anand Chitipothu]

Sorry, I've been away on a vacation past few days. Just saw this message today.

Thanks a lot for your enthusiasm. I'll start a new thread with development plans. Please join the discussion.

Anand

--

You received this message because you are subscribed to the Google Groups "web.py" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webpy+un...@googlegroups.com.
To post to this group, send email to we...@googlegroups.com.
Visit this group at http://groups.google.com/group/webpy?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Anand
http://anandology.com/