If your question is a tool-shopping question, then it's off-topic. However, I'm reading it as more of a methodology question, and so the salient question becomes "What are you trying to communicate with your project artifacts?"
According to Wikipedia:
A Gantt chart...illustrates a project schedule. Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project. Terminal elements and summary elements comprise the work breakdown structure of the project. Some Gantt charts also show the dependency (i.e. precedence network) relationships between activities. Gantt charts can be used to show current schedule status using percent-complete shadings and a vertical "TODAY" line[.]
So, while I don't think Gantt charts are the best way to radiate information about project status, they certainly can be used that way. If it's the right artifact for your project, but your chart is really big, you always have the option of using a plotter or large-format printer. Even if the whole chart won't fit on a single continuous page, I've worked on a number of large government projects where the Gantt charts were printed on the largest available paper size and pasted together on one or more walls in an office. Maybe that will work for you, too.
Revisit Your Status-Communication Needs
Depending on your organization and your project, the goal of the status report or management dashboard may vary in its specifics. This isn't really a tool-specific issue; it's more a question of what information management needs or wants in order to facilitate strategic decision-making.
For example, in Scrum the most common artifact is the Sprint or project burn-down chart, scaling the chart based on the Sprint Backlog or Product Backlog as needed. Other methodologies like Critical Path use network or activity-on-node diagrams, and you could certainly use a couple of colored push-pins to identify "You Are Here" in your diagrams if you want to do so.
The bottom line is that you should start by re-examining:
- What it is that you are actually expected to communicate about your project's status.
- What you are comparing, contrasting, or tracking with your visualization techniques.
- What methodologies and tools work best for your specific project within whatever organizational limitations you have.
In other words, don't start from the assumption that you must use a specific artifact or tool. Instead, start from your known communications requirements, then work backwards to identify the optimal processes and procedures to deliver that communication effectively.