Restructure things so that the application is now just another module.

Kohana makes this type of transition fairly straightforward in that
all controllers/helpers/etc are still located in the cascading
filesystem without any extra effort, except that I've temporarily
added a hack to force modules/gallery into the module path.

Rename what's left of "core" to be "application" so that it conforms
more closely to the Kohana standard (basically, just
application/config/config.php which is the minimal thing that you need
in the application directory)

There's still considerable work left to be done here.

1 files changed, 28 insertions, 0 deletions

diff --git a/modules/gallery/views/admin_graphics.html.php b/modules/gallery/views/admin_graphics.html.php
new file mode 100644
index 00000000..08374471
--- /dev/null
+++ b/modules/gallery/views/admin_graphics.html.php
@@ -0,0 +1,28 @@
+<?php defined("SYSPATH") or die("No direct script access.") ?>
+<script type="text/javascript">
+  $(document).ready(function() {
+    select_toolkit = function(el) {
+      if (!$(this).hasClass("gUnavailable")) {
+        window.location = '<?= url::site("admin/graphics/choose/__TK__?csrf=$csrf") ?>'
+          .replace("__TK__", $(this).attr("id"));
+      }
+    };
+    $("#gAdminGraphics div.gAvailable .gBlock").click(select_toolkit);
+  });
+
+</script>
+<div id="gAdminGraphics">
+  <h1> <?= t("Graphics Settings") ?> </h1>
+  <p>
+    <?= t("Gallery needs a graphics toolkit in order to manipulate your photos.  Please choose one from the list below.") ?>
+  </p>
+
+  <h2> <?= t("Active Toolkit") ?> </h2>
+  <?= $active ?>
+
+  <div class="gAvailable">
+    <h2> <?= t("Available Toolkits") ?> </h2>
+    <?= $available ?>
+  </div>
+</div>
+