Native DSDT/AML IDE & Compiler: MaciASL Open Beta

[SJ_UnderWater]

Ok, I'm ready to release the DSDT editor I've been working on, MaciASL, to open release.

Like other projects, this is available in source and binary form at http://maciasl.sourceforge.net. Three screenshots.

So how does MaciASL improve on the already-crowded OS X AML IDE space?

1. First, no need for Java.
2. Second, code-coloring, indenting, and patching are all available in the same app.
3. Third, useful preferences, like light and dark coloring themes, compiler output, and so on.
4. Fourth, adding many features like online patch repositories, AppleScript automation, Previous Versions and OS X Document Model support (imagine rolling back your /Extra/DSDT.aml natively!), a tree navigator with filtering, updatable iASL binary, easy extraction of _all_ loaded ACPI tables, SSDT generation using revoGirl's script, full compiler logging, app-wide font selection, and QuickLook support using exported UTIs.

/* Source Provider Definition
 Source = {name:<user-defined name>, url:<url without trailing slash>}
 URLs are automatically composed <url>/.maciasl, where .maciasl is the manifest
 A manifest file is a simple list of patch metadata, one patch per line
 Lines are composed like <name>\t<type>\t<url> and separated by newlines (\n)
 The only illegal field characters are tab (\t) and newline (\n)
 Type is one of DSDT or SSDT, but if absent defaults to DSDT for compatibility
 New fields may be added in the future, but <url> will _always_ be last
 Patch URLs will automatically be composed like <source URL>/<patch URL>
 It is recommended that patches start with a comment of the form:
 #Maintained by: <name> for: <site>
*/

 

[toleda]

Ok, I'm ready to release the DSDT editor I've been working on, MaciASL, to an open beta. Beta #1 will last until January 11th.

Outstanding work. MaciASL replaced DSDTSE (won't open files when Users and Applications are on different discs) and DSDT Editor (crashes on save .aml to /Extra) on all my systems. Thanks.

 

[philip_petev]

Reeeeealy fast and works like it should. Nice work!

 

[RehabMan]

Build 210 on ML 10.8.2

Bug report: There seems to be a bug in validation of SSDT generator params.

To repro:
- Run MaciASL
- Choose Tools -> MaciASL
- on my Core i7-2600, it is filled by default with 65 (gray), 2900 (gray), 8, and 3392.
- I change TDP to 95, and MaxTurbo to 3800 (using keyboard, tab between fields)
- Hit Enter or click OK

Bug: get error "Incorrect Range"... "CPU Frequency must be less than Max Turbo Frequency"
(Tax Turbo is 3800, CPU freq is 3392)

Workaround:
- If you fiddle with it enough, use the up/down arrows on various fields, eventually it will take.

 

[SJ_UnderWater]

set Continuously Updates Value for SSDT text fields (build #211)

 

[mmesh]

Hi!

Can this App be used to try and patch DSDT from my new HP 6570b ProBook?

 

[RehabMan]

Hi!

Can this App be used to try and patch DSDT from my new HP 6570b ProBook?

Yes. It is working fine with the probook patches. There is a thread in the probook forum already for your laptop, you should probably look at it.

 

[RehabMan]

set Continuously Updates Value for SSDT text fields (build #211)

Verified fix in build 211.

 

[xsmile]

Thanks for the app.

PS: You might want to change/remove the second download link in your first post as it leads to the old build 210.

 

[SJ_UnderWater]

I have been asked to create a few derivative products, including a Foundation (command line) binary for automated patching, and while I think these may have uses, my main goal is getting out a native open-source IDE to exist as a standard/model implementation. Of course anyone is free to take the source and create these branches, but I don't think I will be building them myself.
Particular to Xcode, I know that the APIs aren't public, and some have difficulty producing plugins. There is no claim of stability from Apple, so I'm not interested in chasing their changes, if/when they are made. As it is, the workflow for Xcode projects is at odds with the general DSDT-editing workflow, which for most users is only to extract their vanilla DSDT, add any patch repos if necessary, apply patches, compile, fix errors, and save. I have added automation abilities and patch "isolation" (select a single patch in the viewer to see only those results) for pros and DSDT providers, but 90%+ will not be reusing MaciASL.
If you have any suggestions for usability enhancements, please let me know.