#frontier

I’m not saying apps these days need to be Frontier-like in any details. But it seems absolutely bizarre to me that we — we who write Mac and iOS apps — still have to build and run the app, make changes, build and run the app, and so on, all day long. In the year 2025.

"Yes, of course -- it's running in Frontier, which was GPL'd in 2004. It's got the full environment, the object database, scripting, verb set, TCP support, web server, CMS, etc."

"The lib should be libpaigefat.a" Getting an error when trying to build with libpaigemacho.a - maybe this is the resolution?

"Frontier for OS X is a bridge between the Macintosh and UNIX worlds."

"I thought maybe I could improve the XML-RPC server to have it branch to different places based on the HOST header of the HTTP request."

"So XML is central to the implementation, but is hidden from the script writer."

"This contextual menu plugin for OS X gives you a Frontier Scripts submenu."

"The OPML Editor is an open source application, developed in C, released under the GPL."

"Frontier does perform a little more automatic HTML for you, which you can prevent if you don't want it."

"Here are two new OPML Editor apps, one for Mac, one for Windows."

"How to install your own server"

"tcp.im is an instant messaging client and server framework for Frontier and Radio UserLand."

"In this HowTo we build a script that allows you to import an entire folder full of images at once."

"It took a fair amount of wrangling to strip extraneous markup and nest the stories in appropriately classed divs and spans."

""

"In which outlines magically become bulleted lists, tables, and (best of all) nothing."

"However, it's going to take more than a half-hearted apology (immediately followed by a justfication) to really get me involved again." Wow, seems like that answers my questions about what ever happened to the Frontier Open Source release.