#pyramid

sadly no

goodwill stevepie_ btw, please use git subtree to extract content from repos and then merge in new repos

blaflamme: eh?

blaflamme: what repos?

goodwill stevepie_ because now we loose all people history and that's sad to all contributors

goodwill atm it's pyramid_tutorials -> pyramid_cookbook

ah

goodwill and possibly others... just saw that yesterday

please keep history

blaflamme: interesting

blaflamme: never had to do that before

stevepie_: nice lil overview of git subtree --> https://developer.atlassian.com/blog/2015/05/th...

if you just move files from one repo to another you loose all history

not just a good idea for contributors, but looking back at why a change was made is important

exactly

a year or so ago my workplace moved from svn to git and we said we wouldnt do it if we couldnt keep the history

was intense lol

that one is easy

is it? I wasnt involved in the migration

yeah, there plenty of tools for that

good evening pyramid

blaflamme I read the docs on git-subtree, but do not understand how to do what you want. I don't want the entire pyramid_tutorials project as a subtree of pyramid_cookbook, just the single-file-tasks directory.

…and its contents

you can extract files or directories

you can split the target directory to a separate branch

like git subtree split --prefix=<target-directory> -b <my-splitted-branch>

you'll have to play a bit to find the right workflow

easier to just copy files

yes but you loose all history and in one commit you own all the work o_O

it remains in pyramid_tutorials

until we get rid of or anything else

the history should follow the work

^

i have zero confidence that i will figure this out correctly

or I'll do pyramidwow and copy the source of the actual pyramid repo, I'll do 1 commit of the current repo state and publish it as the new repo =)

and then i'll probably make a bigger mess of things

I think you'll havr to play a bit with two test repos and find the right workflow... then you'll b ok to work on the real one

stevepie_: I built your branch ... it has hello world in it

stevepie_: so I am not sure what you mean

goodwill it's gotta be there somewhere

stevepie_: I am confused ... it has the current hello world in it

oops

hold on

stevepie_: what branch is that?

it was merged into master

I checkout page-media

cause that is what PR30 was based of

stevepiercy wants to merge 7 commits into Pylons:topnav-wip from stevepiercy:page-media

oops, maybe not

sorry, it's been so long since i paid attention to this, that it's fallen out of my memory buffer

there

i guess it needs a PR

so is it master?

master has now the latest approved PR

so merge master back to it to ensure it's up to date

ah, now i remember...

then remove node_modules and do npm install

i created a new branch to discuss the killing of hello world, which is https://github.com/Pylons/tpc/compare/usage-pat...

or this: https://github.com/Pylons/tpc/blob/usage-patter... without the Create Pull Request button

so if you pull down that branch, then you can see it

okie

ugh ... I hate npm

ran it in the wrong folder

which had nothing for npm

it still created node_modules

weak

and omg, why is webpack using libnotify

stevepie_: okie I built it

and I am not understanding it

what is that supposed to achieve

if I got to the site and see

config.add_view(

'mypackage.views.my_view',

route_name='ok',

request_method=('POST')

)

what does that tell me?

if I never seen pyramid

goodwill webpack is not using it, I've added it as a plugin for desktop notifications

blaflamme: weird ;)

gulp do the same

goodwill doesn't the adjacent text to the right explain?

this is it right?

imma jump in and say, Im glad you guys are killing off that 'hello world' thing.

yes

that's my hack at visual design

so how does config.add_view demostrate predicate?

i'm sure there is someone around here who can take that effort and make it work visually ;)

I mean I know there is a predicate in there

but if a person never seen pyramid ... they would not know what

stevepie_ I'll work on that, once you guys has a something concrete

Method__: what's wrong with the hello world

stevepie_: or are those just examples and not the real text?

goodwill: I saw it after working with pyramid a while and thought to myself, "either im doing it all wrong, or whoever builds from this is going to get annoyed with pyramid really quickly"

@view_config should be used, we should show simple and concise first

especially those new to python

blaflamme what would you call that? Decorators?

…as its text heading. i can grab some explanatory text

stevepie_ goodwill Method__ and on the other hand a lot of people are not aware of providing simple example like the hello world snippets when they're trying or sharing stuff/ideas and they provide scaffold based examples o_O

stevepie_ yes it's function decorator in this case

blaflamme: I agree. but I think as a primary example of what pyramid is great for, showing the normal use case first is important, and then showing the "hey you can use this as a microframework too if you wanted" after the fact

the fact that pycharm does all the boilerplate stuff for pyramid when you start a new project, with the three scaffolds make it easier for those that use pycharm. mentioning that on a front page might be helpful too but Im spitballing.

Method__ but someone who never saw pyramid before and looking quickly at the page, what you show him? He wants to know if the style fits his need/mindset

blaflamme but decorators are a Python thing, not just a Pyramid thing. is there some kind of difference between Python and Pyramid in this regard?

Method__ I never use the scaffolds because I don't work that way, why would I promote them

I agree, its hard to figure out what to show people without making too many assumptions

stevepie_ right, so a better way to show people it's python and not an obscure thing only pyramid do

ok. and you've just written the text for the code example ;)

hehe

that's why we do brainstorm

we can change the hello world to a scaffold one

all points are valid against their own goals

but then people will complain about which scaffold

I won't use a scaffold

what about guiding them through an example?

I was thinking maybe a tabbed inteface at the top with words like

Mini-App

RDBS App

like, "select the scaffold (if any) you want" and it explains what each does

sorta carousel like stevepie_ talked about

we have multiple tuts to show them more

blaflamme: why dont you use scaffolds?

I would never build a real app based on them, like a single page app

Method__ ^

stevepie_: I do not mean an actual carosel

those are terrible

nosql ;)

no-carousel

Method__ first I prefer a domain approach than everything splitted by kind: models, views, etc...

blaflamme: Ive only used the alchemy scaffold

only project Ive used without a scaffold has been my 1-pager for my portfolio site.

Method__ the scaffolds holds all views and models in the same files, quickly you'll need to turn them as modules

every other project has needed a db attached and Ive opted for sqlalchemy