适用于小规模会计应用的最佳GUI？ [英] Best GUI for small-scale accounting app?

问题描述

我很快就会开始开发专门的小应用程序，需要

才能选择GUI。


我已经缩小了选择wxPython / PythonCard和QT / PyQT

（购买商业许可证不是一个大问题，公司

会支付它）。 />

这种应用哪种更好？我的意思是，从纯粹的技术和长期发展方面看待


并忽略许可问题：


- QT似乎是工业强度，但是......它可能更加复杂/难以使用。


- wxPython / PythonCard可能很简单易用，但是......

一旦应用程序开始增长（他们都这样做），开发工作会不会出现一些陷阱

？


必须显示发票，分包商和任务的长清单（可能是数百或数千美元） - 哪种工具包

对你的体验更好？


我很感激任何人在开发此类软件

或类似软件时与

相关工具包分享经验。



-

这是一个人在Python编程协会的生活。

解决方案

Bulba！ < BU *** @ bulba.com>写道：

我很快就会开始开发一个专门的小应用程序，需要
为它选择GUI。

我已经缩小了对wxPython /的选择范围PythonCard和QT / PyQT

应用程序需要做什么？我会尝试以网络为基础，除非

有充分的理由不这样做。即使它只是在

用户的桌面上运行，也是如此;在本地主机上运行http监听器，让

用户通过浏览器连接到它。


然而，在你提到的那两个之间，wxPython似乎更容易使用

并在更多平台上运行。另一方面，它可能不如QT维持b $ b。例如，它当前的安装脚本

似乎假设安装了旧版本的GTK，并且使用较新的GTK版本它会失败

。

>我已经缩小了选择wxPython / PythonCard和QT / PyQT

（购买商业许可证不是一个大问题，公司将为此付费）。
哪种更适合这种应用？我的意思是，从纯粹的技术和长期发展方面看待
并忽略许可问题：

- QT似乎是工业强国，但是......它是可能更复杂/更难使用。

- wxPython / PythonCard可能很简单，但是......
没有一些陷阱会让开发失败
一旦应用程序开始增长（他们都这样做）？

如果你可以花钱，我肯定会去qt。我刚用它创建了一个

中型gui应用程序，它只是摇滚。设计师非常酷，

并且整个框架经过精心设计和工作（到目前为止）完美无瑕

对我而言。此外，信号插槽机制使MVC

模式的实现变得非常简单。


但我不得不承认我没有更大的expierience与WX。尝试用这个新闻组浏览这个新闻组，有很多讨论。


你可以在linux上免费试用qt，你可以尝试两个，看看是什么适合你的

最需要。


-

问候，


Diez B. Roggisch

Paul Rubin写道：

Bulba！ < BU *** @ bulba.com>写道：

我很快就会开始开发一个专门的小应用程序，需要
为它选择GUI。

我缩小了选择wxPython / PythonCard和QT / PyQT

应用程序需要做什么？我会尝试以网络为基础，除非
有充分的理由不这样做。即使它只是在用户桌面上运行，也就是这样;在本地主机上运行http监听器，让
用户通过浏览器连接到它。

我不确定我是否同意这个建议。比以前更容易将一个好看的网络界面放在一起，但是比使用wxPython或PyQT还要困难得多b $ b。对于某些类型的互动，网络仍然是笨拙的，因为您必须在服务器往返或紧密协调后完全重新显示


客户端代码，用于保持客户端本地的一些交互。这是很难妥协的，需要很多经验。

然而，在你提到的那两个之间，wxPython似乎更容易使用
并在更多平台上运行。另一方面，它可能不如QT保持良好。例如，它当前的安装脚本似乎假设安装了较旧版本的GTK，并且使用较新的GTK版本它会失败。

这两个软件包都是由那些知道自己在做什么的人维护的。

wxPython多年来一直存在问题，但其中很多都（我相信b $ b）是由于底层wxWindows（没有

wxWidgets）包的不稳定性，而这通常是由于介绍了很多新功能的b $ b。


就个人而言，我认为选择可能取决于哪个API最接近Bulba过去使用的
。


这两个套件都能很好地处理一个严肃的程序员

想要做的事情。我个人认为wxPython最接近窗口平台的原始外观，但这可能仅仅是我说话的有限经验。


问候

Steve

-

Steve Holden http://www.holdenweb.com/

Python网页编程 http://pydish.holdenweb.com/

Holden Web LLC [phone] [phone]

I''ll soon start development of a specialized small app and need
to choose GUI for it.

I have narrowed the choice to wxPython/PythonCard and QT/PyQT
(buying commercial licenses is not a big problem, the company
would pay for it).

Which is better for this kind of application? I mean, looking
from purely technological and long-term development aspects
and ignoring licensing issues:

- QT seems to be industrial-strength, but.. it''s probably
more complex/difficult to use.

- wxPython/PythonCard is probably simple to use, but..
are there not some pitfalls that development will fall
into once the app starts growing (they all do)?

The long lists of invoices, subcontractors and tasks (possibly
hundreds or thousands) will have to be displayed - which toolkit
is better for that in your experience?

I would appreciate anybody sharing their experiences with
relevant toolkits in development of this type of software
or similar.


--
It''s a man''s life in a Python Programming Association.

解决方案

Bulba! <bu***@bulba.com> writes:

I''ll soon start development of a specialized small app and need
to choose GUI for it.

I have narrowed the choice to wxPython/PythonCard and QT/PyQT

What does the app need to do? I''d try to make it web based unless
there''s a good reason not to. That''s even if it just runs on the
user''s desktop; run the http listener on the localhost and let the
user connect to it with a browser.

However, between those two you mention, wxPython seems easier to use
and runs on more platforms. On the other hand, it may be less well
maintained than QT. For example, its current installation script
seems to assume an older version of GTK is installed, and it fails
with newer GTK versions.

> I have narrowed the choice to wxPython/PythonCard and QT/PyQT

(buying commercial licenses is not a big problem, the company
would pay for it).

Which is better for this kind of application? I mean, looking
from purely technological and long-term development aspects
and ignoring licensing issues:

- QT seems to be industrial-strength, but.. it''s probably
more complex/difficult to use.

- wxPython/PythonCard is probably simple to use, but..
are there not some pitfalls that development will fall
into once the app starts growing (they all do)?

If you can spend the money, I''d certainly go for qt. I just created a
mid-size gui app with it, and it simply rocks. The designer is really cool,
and the whole framework is thouroughly designed and works (so far) flawless
for me. Also the signal-slot mechanism makes implementation of a MVC
pattern pretty easy.

But I have to admit that I don''t have larger expierience with wx. Try
googling this newsgroup, there have been plenty of discussions on this.

As you can qt for free on linux, you could try both and see what suits your
needs best.

--
Regards,

Diez B. Roggisch

Paul Rubin wrote:

Bulba! <bu***@bulba.com> writes:

I''ll soon start development of a specialized small app and need
to choose GUI for it.

I have narrowed the choice to wxPython/PythonCard and QT/PyQT

What does the app need to do? I''d try to make it web based unless
there''s a good reason not to. That''s even if it just runs on the
user''s desktop; run the http listener on the localhost and let the
user connect to it with a browser.

I''m not sure I''d agree with this advice. It''s easier than it used to be
to put a good-looking web interface together, but considerably more
difficult still than using either wxPython or PyQT. The web is still
clunky for certain types of interaction, as you either have to
completely redisplay after a server round-trip or closely co-ordinate
client-side code to keep some interactions local to the client. This is
a difficult compromise, and requires a lot of experience.
However, between those two you mention, wxPython seems easier to use
and runs on more platforms. On the other hand, it may be less well
maintained than QT. For example, its current installation script
seems to assume an older version of GTK is installed, and it fails
with newer GTK versions.

Both packages are maintained be people who know what they are doing.
wxPython has had its issues over the years, but many of those have (I
believe) been due to the instability of the underlying wxWindows (no
wxWidgets) package, which in turn has often been due to the introduction
of serious chunks of new functionality.

Personally I think that the choice may well come down to which API is
closest to what Bulba has used in the past.

Both kits are well capable of handling everything a serious programmer
would want to do. I personally think that wxPython gets closest to the
native look-and-feel of the windowing platform, but that may just be my
limited experience speaking.

regards
Steve
--
Steve Holden http://www.holdenweb.com/
Python Web Programming http://pydish.holdenweb.com/
Holden Web LLC [phone] [phone]

这篇关于适用于小规模会计应用的最佳GUI？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！