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.

Signed-off-by: Gallery Role Account <gallery@menalto.com>

1 files changed, 15 insertions, 0 deletions

diff --git a/modules/gallery/views/admin_languages.html.php b/modules/gallery/views/admin_languages.html.php
new file mode 100644
index 00000000..2b43f1b4
--- /dev/null
+++ b/modules/gallery/views/admin_languages.html.php
@@ -0,0 +1,15 @@
+<?php defined("SYSPATH") or die("No direct script access.") ?>
+<div id="gLanguages">
+  <h2> <?= t("Languages") ?> </h2>
+
+  <?= $settings_form ?>
+
+  <h2> <?= t("Download translations") ?> </h2>
+  <a href="<?= url::site("admin/maintenance/start/core_task::update_l10n?csrf=$csrf") ?>"
+     class="gDialogLink">
+    <?= t("Get updates") ?>
+  </a>
+
+  <h2> <?= t("Your Own Translations") ?> </h2>
+  <?= $share_translations_form ?>
+</div>