Have you ever had the problem, that you needed to install a package, but you weren't familar wit compiling from source?
Or...have you ever just needed a library real quick, like libcurl?
Or just the bare build environment with GCC, G++ and make?
Oh yeah, I know how you feel. Especially when you then try to install package managers, and they just totally mess up your compiles. That is exactly what a package manager shouldn't do - seriously. As well as their purpose might be - no...just no.
apt installs everything to root (/). So, it installs things into their place. And that is EXACTLY what drag0n will be doing!
drag0n is nearly fully PHP based, packed with additional modules and packages, to make the best out of this powerful scripting language. Basically, I dont like to remember it as a "pre hypertext processor". That is not what it is. It's a real scripting language with some things that make it look more like a real programm - especialyl when you add extensions like I did to enable multithreading. This is so different from what you think, is it? PHP, a multithreading scripting language. And if i could have gotten bcompiler to work, i even would have some binaries made out of PHP completely.
To make Mac OS treat one bundle as two individual apps, we have to swap Info.plist files. It is quite funny that it 1) works and 2) is so dirty but works. But really, I just had no other oslution than to implement InfoSwap, a little class with just two stati methods: toDrag0n and toChromium. These methods swap the Info.plist file to either the one of drag0n or chromium. Sounds easy, is tricky. Consider what happens if our parent process gets terminated somehow? I am building a stack of three processes right here; php 5.3.3 (OS X default) -> php 5.5.3 (drag0n-php) -> Chromium 32. The first and second process will be ran in the background - whilst the first swaps the Info.plist files, so that Chromium launches correctly. drag0n uses LSUIElement=1, and Chromium -=0. As you realize, it is really a lot of hackery.
Drag0n is a big pile of hackery, toat put together, results into a very nice app. If you are searching for some, lurk thru drag0n. ;)
As I now have 3 submodules, you need to clone with all submodules:
git clone --recursive https://github.com/IngwiePhoenix/drag0n.gitThen just double-click drag0n. But if you are a developer, you may want to re-generate my environment. Do this by cloning straight into /Applications, like:
$ cd /Applications
$ git clone --recursive https://github.com/IngwiePhoenix/drag0n.gitThat way you'll get a path like /Applications/drag0n/drag0n.app. That is exactly the way I built my stuff :)
With a copy of drag0n, you get:
I am currently working these out. Check the License folder for current stats. I...am just not very good with long, big, english texts, y'know? :/
Absolutely. This package is not just an installer, it also includes a whole bunch of tools to compile and work with developer stuff. Such as Clang for compiling, with all the neccessary headers, Ninja and Make as build systems, upx to compress executables and ccdv to beautify build process. To use it, just call d0.build from System/bin - like so:
$ source /Applications/drag0n/ddrag0n.app/Contents/System/bin/d0.buildHowever, you can also link to another place. Its just important that the bin folder is within your PATH as you call this script. A nicer solution is on the way. I just need to find a reliable way to re-launch the current shell with a new, overridden one. You can also use d0-config to get all the paths and add them to your .profile folder. And if you realy want to extract all of our goodness of build tools; then cp -r them:
$ sudo cp -rv /Applications/drag0n/drag0n.app/Contents/System/usr /usrAnd the tools are permanent - you can then even erase drag0n.
Oh yes, you totally got this right.
@krakjoe created the pthreads extension, that gives PHP coders three classes:
The first is self-explaining, whilst the second and third are stuck together. A worker is a reusable thread. So what we will be able to do in drag0n is, simultaneous downloads and other things - such as starting another script to fetch updates while we're doing other things...in the short, a lot of things are now possible.
The answer here is appJS - @milani's work.
appJS is a...err... Hm. I would say it's a library. This library allows me to spawn a browser window. But unlike node-webkit or such things, I can actually manipulate the router function - THAT function that serves the files! So in here, I was able to emulate a CGI environment, and plugged a window management into PHP. Because i can operate forth and back. From within the "webview", I can then still use JavaScript to use node.js related functions. So I could trigger another PHP script to execute in the background and log its output into the integrated console - and once done, can tell the webview to change.
As you can see; I am able to do quite a lot of new things. with PHP.
UPDATE: Now we run on @sihorton's Deskshell. It is the evolution of AppJS and defines the new standart in drag0n. I currently had to exclude the shell functionality in the terminal, but it'll return soon :)
Yaaaawn. Lazyness bro! :D
The work that @tekimaki did, is inspiring! And, I am able to patch and hack about as well. So, the native PHP module would parse YAML files into arrays - with my own addition SpycObject I am parsing it into an ArrayObject instead - means I am staying OOP. Why? ...well, I hate typing $variable['key']... o-o
But really, having a PHP module like that is very useful, and tutoring too.
This confusing piece of software really caught my eye. I am about to be implementing it into the drag0n PHP core to save some foreach'es. =)
Exactly. Since my PHP is a custom compile, you will most probably have a problem: You don't meet my dependencies. With this utility however I was able to bundle the dylibs into my package - and using the environment variable DYLD_LIBRARY_PATH, I can just add a path to the linker to look at and for dynamic libraries. So if your libs dont fit, it'll fall back to mine =)
1st: I really dont like using cURL from the command line. wget is just sooo self explaining~! So I included a pre-compile, since I am going to use this for updating the app. Yes, for the update, I will most probably fall back to ordinary shell scripts. These can use CocoaDialog to give you nice output while it updates the internal stuff.
The Apple-class is something I wrote myself, which is especially for making it easier to work in the Mac OS X environment. I will have a Windows and UNIX class, depending on the OS I will distribute this app on/for.
A repository called drag0n-src will be opened up properly soon. It includes the whole lot of dependencies and information to build drag0n. A lot of hand-work will be needed still to get it up and running for your OS. It will compile neatly for MacOS of course, but not for anything else as of now.
Gimme feedback, PR's or whatever you would liek to give me :)
@milani : AppJS is what made this possible. Thank you for this lib, please continue it!
@tekimaki : Thanks to Spyc, I now have a foolproof configuration file format. This is plain amazing!
@krakjoe : pthreads is going to change the way I will be coding PHP in the future, dramatically. Thanks for helping me getting it to work! Keep up the great work!
@mstratman : CocoaDialog makes it possible to keep my users from staring into a terminal when I perform updates to the behind-the-scenes things. Great work there!
@bwoebi : He contributed some patches so far, and is testing drag0n on a MacBook Pro with a Retina display - something I dont have right here :p That way I (or we in that case) can ensure that we'll be retina-ready at some point. :)
@sihorton : Sihorton started the Deskshell project. It now is the new standart behind drag0n. Expect much more to come. In fact, drag0n will end up being the "app-store" for Deskshell apps :)