取决于您的目标市场。就您而言，我的第一个决定是是否将其链接到特定的 RDBMS 实现（可能是 Oracle、SQL Server 或 mySQL），还是尝试使其灵活地在任何主要数据库中使用。后者显然会大大增加复杂性（开发、测试、支持）。
第二个是操作系统平台。特定于 Windows（或者可能是 Windows Vista/7 以上）或可以在 Linux、OSX 等上使用的东西。32 位/64 位也将是这里的一个考虑因素。我需要知道它至少可以在 64 位 Windows 7 上运行。
第三，你用什么来开发你的快速开发工具。Dot Net 几乎只适用于 Windows。 Java 或 Python 提供了更多选择。
第四，您是否将其作为商业产品或开源产品（或两者兼而有之）。坦率地说，如果我考虑购买这样的工具来开发我的 XYZ 产品，我会寻求长期支持。如果该工具没有五年的持续支持，我会非常犹豫，并且只有当它来自 Microsoft/IBM/Oracle/Apple 等在该领域具有悠久历史的公司时才会考虑它。场地。即便如此，我也会持怀疑态度（搜索 Microsoft 的 Oslo/Quadrant/SQL Server Modeling）。
我还会寻找专业的技术文档撰写者。
Depends on the market you are aiming for. In your place, my first decision would be whether to link it to a specific RDBMS implementation (which would be Oracle, SQL Server or mySQL) or to try to make it flexible to use amongst any of the major databases. The latter would obviously add massively to the complexity (development, testing, support).
The second would be the OS platform. Something that is specific to Windows (or perhaps Windows Vista/7 upwards) or can be used on Linux, OSX etc. 32bit/64bit would also be a consideration here. I'd need to know that it can run on 64-bit Windows 7 at least.
Thirdly, what do you develop your Rapid Development Tool in. Dot Net would pretty much be Windows only. Java or Python offer more choice.
Fourthly, are you making this as a commercial product, or as open source (or both). Bluntly, if I was looking at buying such a tool to develop my XYZ product in, I'd be looking at long-term support. If the tool doesn't have a five-year pedigree of ongoing support, I'd be very hesitant and would only consider it if it came from a company of the likes of Microsoft/IBM/Oracle/Apple with some serious history in the field. And even then I would be skeptical (search on Microsoft's Oslo/Quadrant/SQL Server Modeling).
I'd also be looking for professional tech writers for the documentation.
发布评论
评论（3）
取决于您的目标市场。就您而言，我的第一个决定是是否将其链接到特定的 RDBMS 实现（可能是 Oracle、SQL Server 或 mySQL），还是尝试使其灵活地在任何主要数据库中使用。后者显然会大大增加复杂性（开发、测试、支持）。
第二个是操作系统平台。特定于 Windows（或者可能是 Windows Vista/7 以上）或可以在 Linux、OSX 等上使用的东西。32 位/64 位也将是这里的一个考虑因素。我需要知道它至少可以在 64 位 Windows 7 上运行。
第三，你用什么来开发你的快速开发工具。Dot Net 几乎只适用于 Windows。 Java 或 Python 提供了更多选择。
第四，您是否将其作为商业产品或开源产品（或两者兼而有之）。坦率地说，如果我考虑购买这样的工具来开发我的 XYZ 产品，我会寻求长期支持。如果该工具没有五年的持续支持，我会非常犹豫，并且只有当它来自 Microsoft/IBM/Oracle/Apple 等在该领域具有悠久历史的公司时才会考虑它。场地。即便如此，我也会持怀疑态度（搜索 Microsoft 的 Oslo/Quadrant/SQL Server Modeling）。
我还会寻找专业的技术文档撰写者。
Depends on the market you are aiming for. In your place, my first decision would be whether to link it to a specific RDBMS implementation (which would be Oracle, SQL Server or mySQL) or to try to make it flexible to use amongst any of the major databases. The latter would obviously add massively to the complexity (development, testing, support).
The second would be the OS platform. Something that is specific to Windows (or perhaps Windows Vista/7 upwards) or can be used on Linux, OSX etc. 32bit/64bit would also be a consideration here. I'd need to know that it can run on 64-bit Windows 7 at least.
Thirdly, what do you develop your Rapid Development Tool in. Dot Net would pretty much be Windows only. Java or Python offer more choice.
Fourthly, are you making this as a commercial product, or as open source (or both). Bluntly, if I was looking at buying such a tool to develop my XYZ product in, I'd be looking at long-term support. If the tool doesn't have a five-year pedigree of ongoing support, I'd be very hesitant and would only consider it if it came from a company of the likes of Microsoft/IBM/Oracle/Apple with some serious history in the field. And even then I would be skeptical (search on Microsoft's Oslo/Quadrant/SQL Server Modeling).
I'd also be looking for professional tech writers for the documentation.
请参阅 功能列表 http://apex.oracle.com" rel="nofollow noreferrer">Oracle Application Express 了解一些好主意。
See the feature list of Oracle Application Express for some good ideas.
我使用过其中一些工具，我想到的是：
1/自动连接外键
2/保持列与代码中表的顺序相同
3/动态代码生成，没有单独的代码生成阶段
4/ 撤消表更改
5/ 原型功能，以便在开发期间对实际数据进行建模
6/ 隐藏列功能
7/ 针对那些棘手位的 SQL 导入
8/ 对棘手位进行代码锁定
9/ 版本控制
10/ 分段到命名空间
11/用于轻松添加额外代码语言的语言模板
我认为首先进入中间 4gl 会很好，然后第二阶段以所选语言呈现代码会很好。
我希望这对你有用，祝你好运！
I've used a few of these tools and things that come to my mind are:
1/ automatic joining on foreign keys
2/ keeping columns in the same order as the table in the code
3/ dynamic code generation, no separate code generation stage
4/ undo on table changes
5/ prototyping features to enable actual data to be modelled during development
6/ hide column feature
7/ SQL import for those tricky bits
8/ code locking on tricky bits
9/ version control
10/ segmentation into namespaces
11/ Language templates for easy addition of extra code languages
I think going to an intermediate 4gl first would be good and then a second stage to render code in the language of choice would be good.
I hope this is of some use to you, good luck!