removing examples

[Massimo DiPierro]

I am reconsidering Simone’s proposal of removing examples from web2py. I dismissed it because it would break my deployment process but but it would not break it too badly. I can fix it easily.

Does anybody oppose to removing examples?
Can you think of any place were we link/linked the local examples app and the link would break?



Massimo

[Michele Comitini]

if nobody is willing and has time to maintain then removal is the only option

Massimo

--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details    : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official    : http://www.web2py.com/
---
You received this message because you are subscribed to the Google Groups "web2py-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py-develop...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Massimo DiPierro]

I do not think that is the main rationale. I think the issue is, does it belong there?

Massimo

[Michele Comitini]

I think it should go in a separate repo.

[Niphlod]

just because I'm the original "requestor"....

<kidding>
a great time ago, when the world was full of wonders, the examples app was showing the latest and badasses features to "lure" smart developers in the magical world of web2py.
It was readily available on web2py.com AND was a reference implementation for nearly all the bullets web2py had.
Then, a big group of witches came by and harassed the online app so bad that was a problem to maintain, and so everything that was database related was stripped out.
Several years passed, and the needs of the online app changed to a more pleasing landing page, that was never decoupled from the one shipped with web2py.
In all this time, no recipes were added and no updates were made. Then pythonanywhere came to the rescue with "demo1", "demo2" and "demo3"....
</kidding>

the examples app could be a great deal if it included "modern" patterns (i.e. keep up with the new features) and actually unit-tested, while being decoupled from the "online landing page pattern" that the current one has.
I even proposed such an app but it never started being followed by "the general population".
As it is, it's a - not even complete - dump of the online landing page, and the examples are not so readily available --> it's not really of much use.

[Leonel Câmara]

How about every time we make release people have a week or so to submit examples, if people don't re-submit they are removed.

[Michele Comitini]

It would be nice to have a new slice site with live examples instead.

2015-03-20 22:37 GMT+01:00 Leonel Câmara <leonel...@gmail.com>:

How about every time we make release people have a week or so to submit examples, if people don't re-submit they are removed.

--

[Massimo DiPierro]

"I even proposed such an app but it never started being followed by "the general population”.

link?

[Niphlod]

was the idea behind https://github.com/niphlod/welcome_augmented . Two birds with one stone... showing how to test an app and live-test it on travis-ci guaranteeing that all the moving parts actually work.

[Massimo DiPierro]

Now I remember it. I like this a lot but not for welcome. It bloats it too much.

I am not even sure this belongs to examples.

Could’d we have a repo of scaffodling applications and we link them?

This could be one of them.

massimo

[Niphlod]

this isn't a scaffolding. it was an attempt to bootstrap (not the css framework, pun intended) interest on live testing an app.
 
Was born with the idea/hope that everybody in need of a "core feature" in his app, would:
- know how to test it in his app
- "contribute" back that "feature", including tests, to that app

Doing so, he'd be sure the "feature" doesn't brake further in the development timeline, and developers would be happy to hack in web2py's code, knowing that if tests pass, nobody will be hurted.

Of course creating such an "examples" - that carried also unittesting - would have been quite an added value.
We have moving parts in python, html, css and js: to my recall, mdipierro, niphlod, paolo and maybe one or two more have been "brave enough" to hack web2py "outside the realm of python"... and for me those were scary times (remember when we stripped javascript out of gluon? I do...) .... live testing is the only option to cover a great part of currently untested gluon code... and we should test js too, but that's another - closely related - story.