Open atownley opened 13 years ago
Two things:
Hi Eric,
Sure. Will enter a separate issue about the fonts thing.
Re item 2, if I can get the environment running on my MacBook, and we end up using it for the project, I'll be happy to do what I can to help you sort the issue with the macports environment. I've never used homebrew, so I've no idea what the brew calls are actually doing in the rakefile. "Back" to OSX from using Linux as primary platform since Apple bought NeXT and originally dropped Intel support for Rhapsody (years ago), so haven't really paid much attention to macports other than getting the tools I needed on the machine so I had a sane command line environment. Might take a bit of investigation before I can a) understand exactly what the issue is and b) contribute something useful to the project.
Right now, I'm just under pressure to find something simple that allows me to leverage Ruby to present a simple, non-Web UI on both Windows and OSX. :)
Cheers,
ast
Sounds good. I think getting you a working binary will be faster than sorting out macports :)
I'm trying to build Shoes (today's clone) on 10.6 since the latest available binary displays boxes instead of characters for para entries. However, I'm using macports for many other things on my machine and the changes required to build for macports on the install in https://github.com/shoes/shoes/wiki/Building-Shoes-on-Mac-OS-X-10.6-and-10.7 don't seem to actually work.
Is there a way to make the rakefile work with either macports or homebrew by default? Seems like the changes required for the pango modules have been invalidated by the changes to the way the modules are determined in the current Rakefile. Poking around, there also seems to be a large number of brew-related stuff in the Rakefile that would need to be altered.
Any ideas on the best way to proceed here? Trying to evaluate whether Shoes is the right solution for a simple cross-platfom UI tool, but can't work if I can't display the standard para fonts! ;)
Thanks in advance,
ast