原始文献 / 论坛帖 / Re: A few suggestions
Re: A few suggestions
Bitcointalk · 2009-12-12 18:17:10 UTC
引用自：madhatter2，2009 年 12 月 12 日 06:34:21 AM（https://bitcointalk.org/index.php?topic=12.msg51#msg51）
svn 0.2 在 Mac OS X 10.4.11/Intel 上快编译通过了（我这还有台 PPC970 的机器，也可以编 PPC 版）。窗口是 wxwidgets 的原生 carbon！飞快！我新建了个 makefile（makefile.osx，当然是基于 makefile.unix 的……考虑过用 autoconf 吗？），还在 header.h 里加了几个 ifdef。我有补丁。继续折腾。下一步可能试 FreeBSD。
能支持 Mac 就好了。wxWidgets 的跨平台真是没白选。
别试 PPC 了。PPC 是大端序，比特币是小端序，无穷无尽的大小端 bug 会让我更难调试网络——万一有个到处字节交换的节点在外面。PPC 反正也快被淘汰了。
考虑过 autoconf。autoconf 是那种 makefile 一团糟的大项目才需要的，我觉得我们还小，不用它更划算。makefile 能简单就尽量简单。
引用：
我觉得把比特币拆成两个应用最理想。一个 wxwidgets 前端（反正基本都有了），一个绑控制 TCP 套接字的后端。我读了下源码，感觉拆起来应该不难。当然得先开发 API。
光想想我就头疼。把 UI 后端全 funnel 到一条 TCP 连接上，所有事都难一倍。因为 listview 控件的工作方式，UI 和内部数据结构之间带宽需求太大，要不停地更新 listview。
我更想要命令行控制，那样远程管理和批量自动化都有了。
英文原文
Quote from: madhatter2 on December 12, 2009, 06:34:21 AM（https://bitcointalk.org/index.php?topic=12.msg51#msg51）I almost have the svn 0.2 compiling on Mac OS X 10.4.11/Intel (I also have a PPC970 machine here as well so a PPC build would be possible as well). The windowing is native carbon too via wxwidgets! It is FAST! I had to create a new makefile (makefile.osx; based on makefile.unix of course.. given any thought to using autoconf?) and put some ifdef's into header.h. I have patches. I will keep toying around. I might try it on FreeBSD next.
Mac support would be nice. wxWidgets really pays off for cross platform.
Please don't try PPC. PPC is big-endian and Bitcoin is little-endian, there would be endless endian bugs making it harder for me to debug the network if there's a potentially byte-swapping node out there. PPC is on its way out anyway.
Considered autoconf. Autoconf is a necessity for large projects with a quagmire makefile, but I think we're small enough that it's more optimal without it. I'd rather keep the makefile simple as long as possible.
QuoteI think that breaking bitcoin into two apps is ideal. A wxwidgets front end (since it is mostly all there) and a backend that binds to a control TCP socket. I have been reading over the source to see how hard it would be to break it apart and I think it should be fairly simple. Of course an API would have to be developed.
My head hurts just thinking about that. Funnelling all the UI backend through a TCP connection would make everything twice as hard. There's too much bandwidth between the UI and the internal data structures in order to keep the listview control updated, because of the way the listview control works.
I'd rather have command line control, that would get us remote admin and batch automation.