Comments (7)
I know that other groups do exactly that, but I'm not sure if there are some issues with this approach.
from paper-template.
I am definitely in favour of putting the content of the paper into a different file from all the boilerplate. Personally I prefer to keep all sections in one file though, mostly because I'm used to it and I can jump to section as easily as jumping to file in my editor. Also sometimes I want to make a nice transition from one section to another which is slightly easier when viewing both in the same file. But I suppose it's easy enough to decide this per-project!
from paper-template.
I would agree that it might make sense to put the boilerplate into a separate file. With respect to factoring out subsections into separate files, that is a subjective choice. I personally like to keep everything in a single file, as I typically navigate by searching to the term that I am interested in. That works best for me if everything is in a single file. I know that @goens likes to have multiple files and other groups indeed split papers up. I guess you do not use use search to navigate to a section or have an editor that supports folding?
from paper-template.
I am happy to arrange a brainstorming how we can improve this template given that the deadline is now over.
from paper-template.
I moved some of the builerplate into separate .tex files. See #33. Does that seem like a step into the right direction?
from paper-template.
To me, this makes a lot of sense!
I prefer having the boilerplate extracted from the main file, rather than having a single file for each section.
Having a single file for each section makes it harder to quickly move in the code!
from paper-template.
That's certainly a step in the right direction. As the consensus seems to be that most people prefer one file for the entire text, I guess we can leave this as is after merging #33. I agree that adding files for each section can be done on a per-project basis, if anyone prefers that.
from paper-template.
Related Issues (8)
- Add TODO list for paper submission to the repository
- Investigate the use of self-hosted builders
- Remove input/abstract.tex and write the abstract in paper.tex
- The IEEE template introduces a lot of if/def noise. HOT 1
- How to compile for ACM camera ready? HOT 1
- Comment in comment leads to infinite loop in build HOT 1
- `\circled` circles are uneven in size
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from paper-template.