那么 360Works SuperContainer 有什么大不了的呢？
六个月前，在我开始从事目前的工作之前，我从未接触过 FileMaker。从那时起，我对它就比较熟悉了。
我们的容器对象删除对文件的引用一直遇到一些问题，我一直在研究自己的解决方案。嗯，有人告诉我的老板 360Works SuperContainer，他让我去看看。
在我看来，SuperContainer只是一个用于组织图像的虚拟服务器。我们的图像数据库的设置方式是，只需创建一个根据项目编号返回图像路径的字段，然后将其传递给 Web 查看器，这根本就不是麻烦 - 这基本上就是 SuperContainer 所做的全部工作。鉴于我可以向其他一些员工解释如何将图像正确放入数据库中，因此没有人需要再次通过 FileMaker 手动添加图像。我们对 FileMaker 即时网络发布功能也不是很感兴趣，所以就是这样。
现在，我很难证明花费公司 200 美元的资金来购买额外的软件是合理的，而这些软件可以完成我已经在处理的事情。 SuperContainer 是否有任何我没有注意到的颠覆性、改变游戏规则的功能？ （请记住，我可以使用 XnView 免费将图像批量处理为缩略图大小，或者，如果情况紧急，我可以轻松构建一个 Web 应用程序来制作程序内的图片幻灯片。）
你们怎么看？思考？
I had never had to deal with FileMaker before I started at my current job, six months ago. Since then, I've become relatively familiar with it.
We've been having some issues with our Container objects dropping references to files, and I have been working on a solution of my own. Well, someone told my boss about 360Works SuperContainer, and he told me to check it out.
It seems to me that SuperContainer is just a virtual server for organizing images. The way that our image database is set up, it would be no hassle at all to just create a field that returns an image's path based on the item number, then pas that to a Web Viewer - which is basically all that SuperContainer does, anyway. Given that I could explain to some of the other employees how to put images in the database correctly, nobody would ever have to manually add an image through FileMaker again. We're not really very interested in the FileMaker Instant Web Publishing features, either, so there's that.
Right now, I'm having a pretty hard time justifying spending $200 of my company's money to pay for additional software that does something that I'm already taking care of. Are there any ground-shaking, game-changing features of SuperContainer that I'm just not picking up on? (Keep in mind that I can batch-process images down to thumbnail size for free with XnView, or that, if push came to shove, I could easily build a webapp to make an in-program slideshow of pictures.)
What do you guys think?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
你说得对。当通过引用将文件存储在 FileMaker 中而不是将整个文件存储在数据库中时，SuperContainer 可以帮助处理删除的引用。就个人而言，考虑到 FileMaker 文件有多大，在处理文档时，我倾向于将它们简单地存储在数据库中并编写检索脚本。但是 SuperContainer 不会做任何您自己通过脚本和 Web 服务器无法完成的事情。通过使用 SuperContainer，您可能会节省一些编码时间，这可能值得购买，但它不会添加任何您无法自己编码的功能。
You're right. SuperContainer could help to deal with the dropped references when storing files in FileMaker by reference instead of storing the entire file within the database. Personally, given how large FileMaker files can be, when working with documents, I tend to simply store them within the database and script their retrieval. But SuperContainer isn't doing anything that you couldn't do yourself with scripting and a web server. By using SuperContainer you might save yourself some coding time, which might make it worth the purchase, but it won't add any capabilities that you couldn't code yourself.