Ado

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

      $ENV{TEST_AUTHOR} is 1.
    - Ado::Plugin::config_dir now defaults to etc/plugins
      relative to the plugin base directory.
    - Implemented Ado::Plugin::home_dir, pointing to the plugin
      base directory, no matter where the plugin is installed.
    - Moved 'app' accessor up to Ado::Command::generate so it can be reused
      by other generators.
    - Implemented Ado::Command::generate::crud->routes and used it in
      Ado::Command::generate::adoplugin.
    - In Ado::Command::generate::crud:
      - renamed argument 'lib_root' to 'lib';
      - added argument home_dir, so files can be dumped to arbitrary directory,
        and at the same time keeping the file structure.
      - Removed 'TODO' marker in crud.t
    - Upgraded to Mojolicious 5.29.
    - Updtaed the default index page.

0.57 2014-08-14
    - Cleanups and clarifications in "Changes" file - no code changes.

0.56 2014-08-14

public/vendor/pagedown/Markdown.Editor.js  view on Meta::CPAN

            innerWidth = doc.body.clientWidth;
            innerHeight = doc.body.clientHeight;
        }

        var maxWidth = Math.max(scrollWidth, innerWidth);
        var maxHeight = Math.max(scrollHeight, innerHeight);
        return [maxWidth, maxHeight, innerWidth, innerHeight];
    };

    // Handles pushing and popping TextareaStates for undo/redo commands.
    // I should rename the stack variables to list.
    function UndoManager(callback, panels) {

        var undoObj = this;
        var undoStack = []; // A stack of undo states
        var stackPtr = 0; // The index of the current state
        var mode = "none";
        var lastState; // The last state
        var timer; // The setTimeout handle for cancelling the timer
        var inputStateObj;

t/ado-build.t  view on Meta::CPAN

#test Ado::Build it self
isa_ok(
    my $build = Ado::Build->new(
        module_name        => 'Ado',
        configure_requires => {'Module::Build' => '0.42'}
    ),
    'Module::Build'
);

subtest 'missing build element' => sub {
    ok(rename('log', 'log_'), 'no "log" dir');
    stdout_like(
        sub { $build->create_build_script(); },
        qr/Creating\snew\s'Build'\sscript/,
        'create_build_script()(no "log" dir) output ok'
    );
    my $elems = join('', qw(etc public templates));
    like(join('', @{$build->build_elements()}), qr/$elems$/, " build_elements($elems) present");

    ok(rename('log_', 'log'), 'yes "log" dir');
    done_testing();
};

stdout_like(
    sub { $build->create_build_script(); },
    qr/Creating\snew\s'Build'\sscript/,
    'create_build_script() output ok'
);

my $build_elements = [qw(etc public log templates)];

templates/default/index_text.html.ep  view on Meta::CPAN

    The current url is <code>"<%=url_for('/')->base%>"</code>.
    On the right side above you see a picture explaining one of 
    the meanings of the word "ado". 
  </p>
  <h2>What's next?</h2>
  <ol>
    <li>Copy <code>etc/ado.conf</code> to 
    <code>etc/ado.development.conf</code>. 
    This will be your configuration file during development.
    Logging is more verbose within this environment.
    You can rename the default <code>etc/ado.conf</code> to something known to you only 
    and keep it for restoring the configuration to its initial state.
    Alternatively you can keep it but modify only <code>etc/ado.development.conf</code>. 
    Both files will be read but the environment specific configuration will override the
    settings from the default file.
    <blockquote> 
      Later, when you are ready to go officially in <i>production</i> mode,
      copy <code>etc/ado.development.conf</code> to <code>etc/ado.production.conf</code>,
      modify the settings (paths, secrets etc) in it accordingly and do not forget to set <code>MOJO_MODE='production'</code> in your  ~/.bashrc
      or copy <code>bin/ado</code> to <code>bin/ado.production.pl</code>, modify it and use it to start Ado.
    </blockquote>