This is probably a closable question, but really I think * is the best source where a practical answer can be found.
这可能是一个可回答的问题,但我认为*是最好的来源,可以找到实用的答案。
I'm working on a web page showing a pivot table. My solution is based on pure jQuery+html. Works pretty nice till now although some css work is still needed. Anyway my project leader is asking me to try to host the excel pivot table connecting to analisys services as an object into the browser. I don't like too much that solution, but I need to have some more points than just saying is an out of date architecture. The first point that come to me is that it only works in IE, but unfortunately the end customer is not just happy with that but also requiring IE. Another interesting point is that the protocol who that funny beast would probably use to communicate with the server is something not really HTTP, just to make firewall happy. End customer ( yes, the one who says IE is a requirement ) would eventually want to see the app working on IPad too, even if the project seems to stand sometime in developement, I doubt this time would be enough to Apple to properly port the ActiveX object in Safari.
我正在开发一个显示数据透视表的网页。我的解决方案基于纯jQuery+html。虽然还需要一些css工作,但是到目前为止效果还不错。无论如何,我的项目负责人要求我尝试将连接到analisys服务的excel数据透视表作为对象保存到浏览器中。我不太喜欢这个解决方案,但我需要有更多的观点,而不仅仅是说它是过时的架构。我想到的第一点是,它只在IE中工作,但不幸的是,最终客户不仅对此感到满意,而且还需要IE。另一个有趣的地方是,那个滑稽的家伙可能会用来与服务器通信的协议不是真正的HTTP,只是为了让防火墙高兴。最终客户(是的,谁说即是要求)最终希望看到IPad应用程序工作,即使这个项目似乎站在发展,我怀疑这一次足以苹果Safari中正确端口ActiveX对象。
What about? Are moi reason pointless, any more reason you see?
关于什么?莫伊是毫无意义的理性,还有什么理由让你看到?
1 个解决方案
#1
9
Enterprise decisions are driven by data and infrastructure, not code.
-
If all your customer's data is stored in Analysis services, then all your JQuery+CSS wizardry doesn't matter if they're not able to pivot the data that they want
如果客户的所有数据都存储在分析服务中,那么所有JQuery+CSS的魔法都不重要,因为它们无法对所需的数据进行数据透视
-
The custom protocol of Analysis Services is designed to pivot billions of records, your JQuery/CSS may not be that scalable yet
分析服务的自定义协议被设计成透视数十亿条记录,您的JQuery/CSS可能还没有那么可伸缩
-
Most enterprises have only IE6/7 infrastructure, they don't even have Firefox, let alone Chrome. They want you to support IE rather than upgrading every desktop
大多数企业只有IE6/7基础架构,甚至没有Firefox,更不用说Chrome了。他们希望你支持IE而不是升级每个桌面。
-
Customers who stress for IE compatibility hardly get around to supporting iPads in their infrastructure. Think Agile. Worry about things when they come, and don't waste effort on skeptical/fictional things. My favorite quote here as a programmer is:
强调IE兼容性的客户很难在基础设施中支持ipad。认为敏捷。当事情来的时候要担心,不要把精力浪费在怀疑或虚构的事情上。作为程序员,我最喜欢的一句话是:
We design architecture and frameworks which support a thousand future possibilities. The customer somehow manages to come up with the thousand-and-oneth thing that we never designed for. Surely, they must be cleverer than us?
我们设计架构和框架,支持一千个未来的可能性。不知何故,客户设法想出了上千件我们从未设计过的东西。他们肯定比我们聪明吗?
So you need to have an open mind on what you've been asked to do.
所以你需要对你被要求做的事情保持开放的心态。
I'm sorry if this post doesn't directly answer your question. But I want to leave it this way.
如果这篇文章没有直接回答你的问题,我很抱歉。但我想这样做。
#1
9
Enterprise decisions are driven by data and infrastructure, not code.
-
If all your customer's data is stored in Analysis services, then all your JQuery+CSS wizardry doesn't matter if they're not able to pivot the data that they want
如果客户的所有数据都存储在分析服务中,那么所有JQuery+CSS的魔法都不重要,因为它们无法对所需的数据进行数据透视
-
The custom protocol of Analysis Services is designed to pivot billions of records, your JQuery/CSS may not be that scalable yet
分析服务的自定义协议被设计成透视数十亿条记录,您的JQuery/CSS可能还没有那么可伸缩
-
Most enterprises have only IE6/7 infrastructure, they don't even have Firefox, let alone Chrome. They want you to support IE rather than upgrading every desktop
大多数企业只有IE6/7基础架构,甚至没有Firefox,更不用说Chrome了。他们希望你支持IE而不是升级每个桌面。
-
Customers who stress for IE compatibility hardly get around to supporting iPads in their infrastructure. Think Agile. Worry about things when they come, and don't waste effort on skeptical/fictional things. My favorite quote here as a programmer is:
强调IE兼容性的客户很难在基础设施中支持ipad。认为敏捷。当事情来的时候要担心,不要把精力浪费在怀疑或虚构的事情上。作为程序员,我最喜欢的一句话是:
We design architecture and frameworks which support a thousand future possibilities. The customer somehow manages to come up with the thousand-and-oneth thing that we never designed for. Surely, they must be cleverer than us?
我们设计架构和框架,支持一千个未来的可能性。不知何故,客户设法想出了上千件我们从未设计过的东西。他们肯定比我们聪明吗?
So you need to have an open mind on what you've been asked to do.
所以你需要对你被要求做的事情保持开放的心态。
I'm sorry if this post doesn't directly answer your question. But I want to leave it this way.
如果这篇文章没有直接回答你的问题,我很抱歉。但我想这样做。