99% of my practical experience is with Iliad, so my comparison is primarily about how I got to choose Iliad instead of the others.
Seaside. Tried it first, it is the most known and the first you stumble in. I found it hard to understand (as always, no matter what you use, when it gets to real implementation you always run into issues that fit badly with the general theory), there was little documentation around and the community seemed to care little about telling n00bs how to grow up. I eventually dropped it to check Aida. You find them here: http://seaside.st/ and on IRC at #seaside
Aida. I really liked it, as Janko is extremely patient and supportive. It is large, though. I decided to use it, when I was to start implementation for our project and it was only by chance that I ran into Iliad a few days before starting. You find Aida here: http://www.aidaweb.si/ and on IRC at #Aida
Iliad. The main reason I chose it was that I had just dropped Squeak and switched to gnu-smalltalk. gst seemed to have a lot of ongoing activity on Iliad, so I reckoned I was probably going to get a better assistance with it. It is much smaller as a concept (though it does absolutely everything) and I had very little trouble in getting started and in tweaking it to what I needed for. It also proved to be well managed, as I went thru 3 releases without ever being in trouble with what I had already deployed. You get answers to questions usually in 12-24 hours max, which is fine for me. You find Iliad here: http://www.iliadproject.org/index on IRC issues are usually channeled on the #gnu-smalltalk channel
What we are doing is a GUI for a PostgreSQL database used to manage a large multimedia dictionary, that in turn produces content (among others, for KDE-edu). I have no notion of booking apps in general, so I cannot answer to your question properly.
Yet, speaking as an analyst, a booking app is mostly a DB with an online GUI, so I see no reason why you could not make it. Much will depend on how easily your db can translate into objects. You could use a RDBMS, as we did, and design tables to map objects, or use an OODBMS. Both solutions have pluses and minuses, none of them is going to have an impact on your choice of framework, I'd say.
My suggestion is that you take a month or so in making experiments and see what better fits you. I don't think there is a tool that fits everyone, we are all different and what is easy for me may be hell for someone else (and the other way round, obviously). So try your car before buying it ;)
I would not invest too much time in studying the general theory. Using a smalltalk framework is going to turn upside down the way you make a web app anyway, and your first contact is going to be full of "false friends" you inherit from previous mindsets. Your best asset is definitely going to be "how quick can I grasp what they tell me", and this is largely an individual thing, depending on you and on who you bump into. So I'd really suggest you get your hands dirty BEFORE reading too much theoretical stuff.
These frameworks are all quite different and have different goals. It would be interesting to collaboratively create some kind of comparison.
As an author of Seaside I can provide the key properties of Seaside only:
Seaside makes building web applications feel like composing traditional GUIs: components can be freely composed and reused. Sequences of components are defined using a sequence of Smalltalk statements.
Seaside has a layered architecture, providing you with high-level abstractions (components, control flow, callbacks, HTML generation, JavaScript generation, ...) over low-level concepts (HTTP, Request, Response, URLs, HTML, JavaScript). If you need to, Seaside gives you full access to low-level constructs too.
Seaside provides a tight integration into various state of the art web technologies: JavaScript (JQuery and JQueryUI), SVG, RSS, HTML5, Comet (Server-Push)
Seaside runs identically on most today's Smalltalk platforms: Pharo Smalltalk, Squeak, GNU Smalltalk, GemStone Smalltalk, VW Smalltalk, VA Smalltalk, and Dolphin Smalltalk. It is supported by all vendors of Smalltalk platforms.
Seaside provides industry proven open-source components for meta-modeling (Magritte) and content management (Pier).
Let me introduce some strengths of Aida/Web too, because as its author it would be hard to me to compare with other two frameworks. Aida strengths are:
RESTfull URLs
MVC support, every domain object can have its own RESTfull URL, each domain class has its own web presentation class,
Integrated AJAX and Comet support, you don't see any difference between a traditional and Ajax programming anymore,
This is the is a nice example because it was developed it in maybe a week in total, together with a development of GSoC process in parallel and in the same time managing that process as an admin. This site is actually an extended Aida/Scribo CMS, with strong use of so called scriblets, that is, dynamic web "includes" directly into the content of the site. That way I was able to very quickly support the new ideas which come during the evolving GSoC process.
发布评论
评论（4）
我99%的实践经验都是《伊利亚特》，所以我的比较主要是关于我如何选择《伊利亚特》而不是其他的。
海边。先尝试一下，它是最有名的，也是你第一个遇到的。我发现它很难理解（一如既往，无论你使用什么，当它真正实现时，你总是会遇到与一般理论不相符的问题），周围几乎没有任何文档，而且社区似乎不太关心告诉 n00bs 如何成长。我最终把它放下来检查阿伊达。您可以在这里找到它们：http://seaside.st/ 以及#seaside
Seaside 的 IRC
Aida。我真的很喜欢它，因为 Janko 非常耐心和支持。不过它很大。当我要开始实施我们的项目时，我决定使用它，只是在开始前几天偶然遇到了《伊利亚特》。您可以在这里找到 Aida：http://www.aidaweb.si/ 以及 IRC 上的 #Aida
伊利亚特。我选择它的主要原因是我刚刚放弃了 Squeak 并转向了 gnu-smalltalk。 gst 似乎在《伊利亚特》上有很多正在进行的活动，所以我认为我可能会得到更好的帮助。作为一个概念，它要小得多（尽管它绝对可以做所有事情），而且我在开始使用并将其调整为我需要的东西时遇到了很少的麻烦。事实证明它管理得很好，因为我经历了 3 个版本，而我已经部署的内容从未遇到过麻烦。您通常最多 12-24 小时内就能得到问题的答案，这对我来说很好。您可以在这里找到 Iliad：http://www.iliadproject.org/index IRC 问题通常通过#gnu-smalltalk 频道
我们正在做的是 PostgreSQL 数据库的 GUI，用于管理大型多媒体字典，进而生成内容（其中包括用于 KDE-edu 的内容）。我对一般的预订应用程序没有概念，所以我无法正确回答你的问题。
然而，作为一名分析师，预订应用程序主要是一个带有在线 GUI 的数据库，所以我认为你没有理由做不到。很大程度上取决于您的数据库转换为对象的容易程度。您可以像我们一样使用 RDBMS，并设计表来映射对象，或者使用 OODBMS。我想说，这两种解决方案都有优点和缺点，它们都不会影响您选择的框架。
我的建议是你花一个月左右的时间进行实验，看看什么更适合你。我不认为有一种工具适合每个人，我们都是不同的，对我来说容易的事情对其他人来说可能是地狱（显然，反之亦然）。因此，在购买之前先尝试一下您的汽车；）
我不会投入太多时间来研究一般理论。无论如何，使用smalltalk框架将会颠覆你制作网络应用程序的方式，并且你的第一次接触将充满你从以前的思维方式继承的“假朋友”。你最好的资产肯定是“我能多快地掌握他们告诉我的内容”，这在很大程度上是个人的事情，取决于你和你遇到的人。所以我真的建议你在阅读太多理论内容之前先动手。
99% of my practical experience is with Iliad, so my comparison is primarily about how I got to choose Iliad instead of the others.
Seaside. Tried it first, it is the most known and the first you stumble in. I found it hard to understand (as always, no matter what you use, when it gets to real implementation you always run into issues that fit badly with the general theory), there was little documentation around and the community seemed to care little about telling n00bs how to grow up. I eventually dropped it to check Aida. You find them here: http://seaside.st/ and on IRC at #seaside
Aida. I really liked it, as Janko is extremely patient and supportive. It is large, though. I decided to use it, when I was to start implementation for our project and it was only by chance that I ran into Iliad a few days before starting. You find Aida here: http://www.aidaweb.si/ and on IRC at #Aida
Iliad. The main reason I chose it was that I had just dropped Squeak and switched to gnu-smalltalk. gst seemed to have a lot of ongoing activity on Iliad, so I reckoned I was probably going to get a better assistance with it. It is much smaller as a concept (though it does absolutely everything) and I had very little trouble in getting started and in tweaking it to what I needed for. It also proved to be well managed, as I went thru 3 releases without ever being in trouble with what I had already deployed. You get answers to questions usually in 12-24 hours max, which is fine for me. You find Iliad here: http://www.iliadproject.org/index on IRC issues are usually channeled on the #gnu-smalltalk channel
What we are doing is a GUI for a PostgreSQL database used to manage a large multimedia dictionary, that in turn produces content (among others, for KDE-edu). I have no notion of booking apps in general, so I cannot answer to your question properly.
Yet, speaking as an analyst, a booking app is mostly a DB with an online GUI, so I see no reason why you could not make it. Much will depend on how easily your db can translate into objects. You could use a RDBMS, as we did, and design tables to map objects, or use an OODBMS. Both solutions have pluses and minuses, none of them is going to have an impact on your choice of framework, I'd say.
My suggestion is that you take a month or so in making experiments and see what better fits you. I don't think there is a tool that fits everyone, we are all different and what is easy for me may be hell for someone else (and the other way round, obviously). So try your car before buying it ;)
I would not invest too much time in studying the general theory. Using a smalltalk framework is going to turn upside down the way you make a web app anyway, and your first contact is going to be full of "false friends" you inherit from previous mindsets. Your best asset is definitely going to be "how quick can I grasp what they tell me", and this is largely an individual thing, depending on you and on who you bump into. So I'd really suggest you get your hands dirty BEFORE reading too much theoretical stuff.
这些框架都有很大不同，并且有不同的目标。合作进行某种比较会很有趣。
作为 Seaside 的作者，我只能提供 Seaside 的关键属性：
Seaside 使构建 Web 应用程序感觉就像编写传统 GUI：组件可以自由组合和重用。组件序列是使用一系列 Smalltalk 语句来定义的。
Seaside 具有分层架构，为您提供基于低级概念（HTTP、请求）的高级抽象（组件、控制流、回调、HTML 生成、JavaScript 生成等） 、响应、URL、HTML、JavaScript）。如果您需要，Seaside 还可以让您完全访问低级构造。
有两本 Seaside 书籍可以帮助您入门：Seaside 动态 Web 开发< /a> 和 海边教程。
Seaside 在当今大多数 Smalltalk 上运行相同平台：Pharo Smalltalk、Squeak、GNU Smalltalk、GemStone Smalltalk、VW Smalltalk、VA Smalltalk 和 Dolphin Smalltalk。它受到所有 Smalltalk 平台供应商的支持。
Seaside 为元建模提供经过行业验证的开源组件（ Magritte）和内容管理（Pier）。
These frameworks are all quite different and have different goals. It would be interesting to collaboratively create some kind of comparison.
As an author of Seaside I can provide the key properties of Seaside only:
Seaside makes building web applications feel like composing traditional GUIs: components can be freely composed and reused. Sequences of components are defined using a sequence of Smalltalk statements.
Seaside has a layered architecture, providing you with high-level abstractions (components, control flow, callbacks, HTML generation, JavaScript generation, ...) over low-level concepts (HTTP, Request, Response, URLs, HTML, JavaScript). If you need to, Seaside gives you full access to low-level constructs too.
There are two Seaside books to help you get started: Dynamic Web Development with Seaside and Seaside Tutorial.
Seaside provides a tight integration into various state of the art web technologies: JavaScript (JQuery and JQueryUI), SVG, RSS, HTML5, Comet (Server-Push)
Seaside runs identically on most today's Smalltalk platforms: Pharo Smalltalk, Squeak, GNU Smalltalk, GemStone Smalltalk, VW Smalltalk, VA Smalltalk, and Dolphin Smalltalk. It is supported by all vendors of Smalltalk platforms.
Seaside provides industry proven open-source components for meta-modeling (Magritte) and content management (Pier).
让我也介绍一下 Aida/Web 的一些优点，因为作为它的作者，我很难与其他人进行比较两个框架。 Aida 的优势是：
有自己的 RESTfull URL，每个域类都有自己的 Web 表示类，
支持，没看出什么区别
传统和 Ajax 之间
不再编程，
控制流量，无需
继续
由组件/元素组成
（不基于模板）
控制和用户/组管理
Squeak/Pharo、VisualWorks、宝石
GLASS、Dolphin、Smalltalk/X
Prime 和 Aida 最新的工作示例是今年 Smalltalk Google Summer of
代码站点。
这是一个很好的例子，因为它是在一周内开发出来的
总计，以及并行和并行开发的 GSoC 流程
同时以管理员身份管理该流程。这个网站实际上是
扩展的 Aida/Scribo CMS，大量使用所谓的 scriblet，
也就是说，动态网络直接“包含”到网站的内容中。
这样我就能很快支持新的想法
在不断发展的 GSoC 过程中。
Let me introduce some strengths of Aida/Web too, because as its author it would be hard to me to compare with other two frameworks. Aida strengths are:
have its own RESTfull URL, each domain class has its own web presentation class,
support, you don't see any difference
between a traditional and Ajax
programming anymore,
control flows, without need for
continuations
composing from components/elements
(no template based)
control and users/groups management
Squeak/Pharo, VisualWorks, Gemstone
GLASS, Dolphin, Smalltalk/X
Prime and most fresh example of Aida at work is this year Smalltalk Google Summer of
Code site.
This is the is a nice example because it was developed it in maybe a week in
total, together with a development of GSoC process in parallel and in
the same time managing that process as an admin. This site is actually
an extended Aida/Scribo CMS, with strong use of so called scriblets,
that is, dynamic web "includes" directly into the content of the site.
That way I was able to very quickly support the new ideas which come
during the evolving GSoC process.
嗯，Suixo 使用 Seaside。查看我们定义的GSoC 项目。它更像是 ERP，而不是簿记，目前专注于医疗保健。
Well, Suixo uses Seaside. Take a look at the GSoC projects we defined. Its more ERP than bookkeeping, and currently focused on healthcare.