Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add group by "Neighborhood and City" #22

Open
ramiroruda opened this issue Aug 1, 2018 · 7 comments
Open

Add group by "Neighborhood and City" #22

ramiroruda opened this issue Aug 1, 2018 · 7 comments

Comments

@ramiroruda
Copy link

Members in Argentina are used to search meetings by neighbourhood so it would be very helpful to have the possibility to have the search results listed like that instead of week days

@dgershman
Copy link
Collaborator

do you want to see city on top where day is and then subdivided by neighborhood?

@ramiroruda
Copy link
Author

Hey guys! thanks for the assistance!
This is how we are currently showing the meetings in our print version: https://share.icloud.com/photos/0WSFn2WF_fiw5bglTtNpB2P6Q#Buenos_Aires_-_Palermo

@ramiroruda
Copy link
Author

Is it posible to export it like that?

@dgershman dgershman self-assigned this Oct 2, 2018
@dgershman dgershman changed the title Add group by "Neighborhood and City", Add group by "Neighborhood and City" Oct 27, 2018
@dgershman dgershman removed their assignment Oct 27, 2018
@pjaudiomv pjaudiomv self-assigned this Oct 27, 2018
@dgershman
Copy link
Collaborator

released in bread 1.7.0

@dgershman
Copy link
Collaborator

@otrok7 will your changes be able to incorporate such a layout?

@otrok7
Copy link
Collaborator

otrok7 commented Jun 27, 2019

You're asking about the actual layout in the pdf, not the grouping, right?

If it was only a question of getting the table rows right, with the format code under the days, yes. But the real problem here, at least at first glance, is the grouping of the meetings inside of a larger table, with headings on every page. That's not the way bread works. The heading is a table by itself. Each meeting is a table by itself (or the css equivalent). If we opened up the concept of heading, put all the meetings in a group in the same table, we could maybe use here, but that moves in exactly the opposite direction of trying to avoid table for performance reasons.

Let me think for a while on this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants