From 74b801ba08dc0fe464eec568bebc36d43173e540 Mon Sep 17 00:00:00 2001
From: Maximilian Hils <git@maximilianhils.com>
Date: Thu, 7 Aug 2014 00:55:42 +0200
Subject: docs: suggest to use inline scripts rather than libmproxy

---
 doc-src/scripting/libmproxy.html | 10 ++++++++++
 1 file changed, 10 insertions(+)

(limited to 'doc-src/scripting')

diff --git a/doc-src/scripting/libmproxy.html b/doc-src/scripting/libmproxy.html
index e2d2ff6a..db58f7e0 100644
--- a/doc-src/scripting/libmproxy.html
+++ b/doc-src/scripting/libmproxy.html
@@ -1,3 +1,13 @@
+<div class="well">
+    <strong>Heads up!</strong> We strongly encourage you to use <a href="@!urlTo("scripting/inlinescripts.html")!@">inline scripts</a> rather than libmproxy
+    directly.<br><br>
+    <ul>
+        <li>Inline Scripts are equally powerful and provide an easier syntax.</li>
+        <li>Most examples are written as inline scripts.</li>
+        <li>Multiple inline scripts can be combined and used together.</li>
+        <li>Inline Scripts can either be executed headless with mitmdump or within the mitmproxy UI.</li>
+    </ul>
+</div>
 
 All of mitmproxy's basic functionality is exposed through the __libmproxy__
 library. The example below shows a simple implementation of the "sticky cookie"
-- 
cgit v1.2.3