Smalltalk › Amber Smalltalk

amber init, working

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

34 messages Options

Herby Vojčík

Re: amber init, working

[hidden email] wrote:
> On Sun, Apr 13, 2014 at 10:55 PM, Herby Vojčík <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>
>
> [hidden email] <mailto:[hidden email]> wrote:
>
> Well, Windows with Mingw/Msys isn't behaving as nicely.

I myself use Windows, but with native programs (node as well as npm are
native, git for windows which is compiled using mingw installed).

node and npm, thus grunt, bower and all those things work nicely in
windows natively.

With this setup, npm nicely gets amber from git and the rest works, too.

I don't know what is your setup different in, that it fails...

Herby

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Herby Vojčík

Re: amber init, working

Ok, the news:

There is 'amber-cli' in npm now.

So, if you want to use amber init, and officially be amongst the first
who will use amber cli tool from its own repo, as it should be soon
blessed, in repo, you should do only these steps.

1. Uninstall old global amber:

(sudo) npm -g uninstall amber

2. Install the amber-cli:

(sudo) npm -g install amber-cli

3. Initialize your project:

mkdir myproj
cd myproj
amber init

4. Go on:

amber serve
browse http://localhost:4000/

Herby

P.S.: Let me know if something gone wrong... it shouldn't ;-) for me it
works on Windows.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

philippeback

Re: amber init, working

Worked nicely until trying to open Helios. See screenshot

User@Techlab ~

$ npm -g uninstall amber

unbuild amber@0.12.3

User@Techlab ~

$ npm -g install amber-cli

npm http GET https://registry.npmjs.org/amber-cli

npm http 200 https://registry.npmjs.org/amber-cli

npm http GET https://registry.npmjs.org/amber-cli/-/amber-cli-0.0.3.tgz

npm http 200 https://registry.npmjs.org/amber-cli/-/amber-cli-0.0.3.tgz

npm http GET https://registry.npmjs.org/amdefine/0.0.8

npm http GET https://registry.npmjs.org/es6-promise

npm http GET https://registry.npmjs.org/amber

npm http GET https://registry.npmjs.org/grunt-init

npm http GET https://registry.npmjs.org/bower

npm http 304 https://registry.npmjs.org/grunt-init

npm http 200 https://registry.npmjs.org/es6-promise

npm http 200 https://registry.npmjs.org/amdefine/0.0.8

npm http GET https://registry.npmjs.org/amdefine/-/amdefine-0.0.8.tgz

npm http 200 https://registry.npmjs.org/amber

npm http GET https://registry.npmjs.org/amber/-/amber-0.12.4.tgz

npm http 200 https://registry.npmjs.org/bower

npm http 200 https://registry.npmjs.org/amdefine/-/amdefine-0.0.8.tgz

npm http 200 https://registry.npmjs.org/amber/-/amber-0.12.4.tgz

npm http GET https://registry.npmjs.org/prompt

npm http GET https://registry.npmjs.org/colors

npm http GET https://registry.npmjs.org/lodash

npm http GET https://registry.npmjs.org/hooker

npm http GET https://registry.npmjs.org/grunt

npm http GET https://registry.npmjs.org/semver

npm http GET https://registry.npmjs.org/async

npm http 304 https://registry.npmjs.org/colors

npm http 304 https://registry.npmjs.org/grunt

npm http 304 https://registry.npmjs.org/lodash

npm http 304 https://registry.npmjs.org/async

npm http 304 https://registry.npmjs.org/prompt

npm http GET https://registry.npmjs.org/abbrev

npm http GET https://registry.npmjs.org/bower-endpoint-parser

npm http GET https://registry.npmjs.org/bower-config

npm http GET https://registry.npmjs.org/bower-json

npm http GET https://registry.npmjs.org/archy/0.0.2

npm http GET https://registry.npmjs.org/chalk

npm http GET https://registry.npmjs.org/bower-logger

npm http GET https://registry.npmjs.org/bower-registry-client

npm http GET https://registry.npmjs.org/fstream-ignore

npm http GET https://registry.npmjs.org/cardinal

npm http GET https://registry.npmjs.org/decompress-zip

npm http GET https://registry.npmjs.org/chmodr

npm http GET https://registry.npmjs.org/glob

npm http GET https://registry.npmjs.org/fstream

npm http GET https://registry.npmjs.org/graceful-fs

npm http GET https://registry.npmjs.org/handlebars

npm http GET https://registry.npmjs.org/inquirer

npm http GET https://registry.npmjs.org/junk

npm http GET https://registry.npmjs.org/mkdirp

npm http GET https://registry.npmjs.org/open

npm http GET https://registry.npmjs.org/promptly

npm http GET https://registry.npmjs.org/osenv

npm http GET https://registry.npmjs.org/nopt

npm http GET https://registry.npmjs.org/lru-cache

npm http GET https://registry.npmjs.org/q

npm http GET https://registry.npmjs.org/mout

npm http GET https://registry.npmjs.org/retry

npm http GET https://registry.npmjs.org/request

npm http GET https://registry.npmjs.org/request-progress

npm http GET https://registry.npmjs.org/stringify-object

npm http GET https://registry.npmjs.org/rimraf

npm http GET https://registry.npmjs.org/semver

npm http GET https://registry.npmjs.org/tar

npm http GET https://registry.npmjs.org/tmp

npm http GET https://registry.npmjs.org/update-notifier

npm http GET https://registry.npmjs.org/which

npm http GET https://registry.npmjs.org/p-throttler

npm http GET https://registry.npmjs.org/insight

npm http GET https://registry.npmjs.org/is-root

npm http GET https://registry.npmjs.org/shell-quote

npm http GET https://registry.npmjs.org/lockfile

npm http 304 https://registry.npmjs.org/abbrev

npm http 304 https://registry.npmjs.org/bower-config

npm http 304 https://registry.npmjs.org/hooker

npm http 304 https://registry.npmjs.org/semver

npm http 304 https://registry.npmjs.org/bower-endpoint-parser

npm http 304 https://registry.npmjs.org/chalk

npm http 304 https://registry.npmjs.org/bower-json

npm http 304 https://registry.npmjs.org/archy/0.0.2

npm http 304 https://registry.npmjs.org/bower-logger

npm http 304 https://registry.npmjs.org/bower-registry-client

npm http 304 https://registry.npmjs.org/fstream-ignore

npm http 304 https://registry.npmjs.org/cardinal

npm http 304 https://registry.npmjs.org/glob

npm http 304 https://registry.npmjs.org/decompress-zip

npm http 304 https://registry.npmjs.org/handlebars

npm http 304 https://registry.npmjs.org/graceful-fs

npm http 304 https://registry.npmjs.org/chmodr

npm http 304 https://registry.npmjs.org/fstream

npm http GET https://registry.npmjs.org/coffee-script

npm http GET https://registry.npmjs.org/winston

npm http GET https://registry.npmjs.org/pkginfo

npm http GET https://registry.npmjs.org/minimatch

npm http GET https://registry.npmjs.org/eventemitter2

npm http GET https://registry.npmjs.org/iconv-lite

npm http GET https://registry.npmjs.org/rimraf

npm http GET https://registry.npmjs.org/nopt

npm http GET https://registry.npmjs.org/findup-sync

npm http GET https://registry.npmjs.org/underscore.string

npm http GET https://registry.npmjs.org/dateformat/1.0.2-1.2.3

npm http GET https://registry.npmjs.org/exit

npm http GET https://registry.npmjs.org/js-yaml

npm http 304 https://registry.npmjs.org/inquirer

npm http 304 https://registry.npmjs.org/mkdirp

npm http 304 https://registry.npmjs.org/junk

npm http GET https://registry.npmjs.org/getobject

npm http GET https://registry.npmjs.org/grunt-legacy-util

npm http 304 https://registry.npmjs.org/nopt

npm http 304 https://registry.npmjs.org/lru-cache

npm http 304 https://registry.npmjs.org/open

npm http 304 https://registry.npmjs.org/promptly

npm http 304 https://registry.npmjs.org/request

npm http 304 https://registry.npmjs.org/osenv

npm http 304 https://registry.npmjs.org/q

npm http 304 https://registry.npmjs.org/retry

npm http 304 https://registry.npmjs.org/rimraf

npm http 200 https://registry.npmjs.org/mout

npm http 304 https://registry.npmjs.org/semver

npm http 304 https://registry.npmjs.org/stringify-object

npm http 304 https://registry.npmjs.org/tar

npm http 304 https://registry.npmjs.org/request-progress

npm http 304 https://registry.npmjs.org/tmp

npm http 304 https://registry.npmjs.org/update-notifier

npm http 304 https://registry.npmjs.org/which

npm http 304 https://registry.npmjs.org/p-throttler

npm http 304 https://registry.npmjs.org/insight

npm http 304 https://registry.npmjs.org/is-root

npm http 304 https://registry.npmjs.org/shell-quote

npm http 304 https://registry.npmjs.org/lockfile

npm http 304 https://registry.npmjs.org/coffee-script

npm http 304 https://registry.npmjs.org/iconv-lite

npm http 304 https://registry.npmjs.org/eventemitter2

npm http 304 https://registry.npmjs.org/pkginfo

npm http 200 https://registry.npmjs.org/minimatch

npm http 200 https://registry.npmjs.org/winston

npm http 200 https://registry.npmjs.org/rimraf

npm http 304 https://registry.npmjs.org/nopt

npm http 304 https://registry.npmjs.org/findup-sync

npm http 304 https://registry.npmjs.org/dateformat/1.0.2-1.2.3

npm http 304 https://registry.npmjs.org/grunt-legacy-util

npm http 304 https://registry.npmjs.org/exit

npm http 304 https://registry.npmjs.org/underscore.string

npm http 304 https://registry.npmjs.org/js-yaml

npm http GET https://registry.npmjs.org/has-color

npm http GET https://registry.npmjs.org/ansi-styles

npm http GET https://registry.npmjs.org/strip-ansi

npm http 304 https://registry.npmjs.org/getobject

npm http GET https://registry.npmjs.org/configstore

npm http GET https://registry.npmjs.org/object-assign

npm http GET https://registry.npmjs.org/lodash.debounce

npm http GET https://registry.npmjs.org/configstore

npm http GET https://registry.npmjs.org/throttleit

npm http 304 https://registry.npmjs.org/ansi-styles

npm http 304 https://registry.npmjs.org/has-color

npm http GET https://registry.npmjs.org/read

npm http 304 https://registry.npmjs.org/strip-ansi

npm http 304 https://registry.npmjs.org/configstore

npm http GET https://registry.npmjs.org/optimist

npm http 304 https://registry.npmjs.org/object-assign

npm http 304 https://registry.npmjs.org/throttleit

npm http GET https://registry.npmjs.org/inherits

npm http 304 https://registry.npmjs.org/read

npm http 304 https://registry.npmjs.org/lodash.debounce

npm http GET https://registry.npmjs.org/jsonify

npm http GET https://registry.npmjs.org/array-filter

npm http GET https://registry.npmjs.org/array-map

npm http GET https://registry.npmjs.org/array-reduce

npm http 304 https://registry.npmjs.org/optimist

npm http GET https://registry.npmjs.org/deep-extend

npm http GET https://registry.npmjs.org/intersect

npm http GET https://registry.npmjs.org/mkpath

npm http GET https://registry.npmjs.org/binary

npm http GET https://registry.npmjs.org/touch/0.0.2

npm http GET https://registry.npmjs.org/readable-stream

npm http 304 https://registry.npmjs.org/array-map

npm http 304 https://registry.npmjs.org/inherits

npm http GET https://registry.npmjs.org/uuid

npm http GET https://registry.npmjs.org/qs

npm http GET https://registry.npmjs.org/json-stringify-safe

npm http GET https://registry.npmjs.org/node-uuid

npm http GET https://registry.npmjs.org/forever-agent

npm http GET https://registry.npmjs.org/form-data

npm http GET https://registry.npmjs.org/tunnel-agent

npm http GET https://registry.npmjs.org/http-signature

npm http GET https://registry.npmjs.org/oauth-sign

npm http GET https://registry.npmjs.org/mime

npm http GET https://registry.npmjs.org/tough-cookie

npm http GET https://registry.npmjs.org/hawk

npm http GET https://registry.npmjs.org/aws-sign2

npm http 304 https://registry.npmjs.org/array-reduce

npm http 304 https://registry.npmjs.org/array-filter

npm http GET https://registry.npmjs.org/lodash.isfunction

npm http GET https://registry.npmjs.org/lodash.isobject

npm http GET https://registry.npmjs.org/lodash.now

npm http GET https://registry.npmjs.org/cli-color

npm http GET https://registry.npmjs.org/readline2

npm http GET https://registry.npmjs.org/mute-stream/0.0.4

npm http GET https://registry.npmjs.org/through

npm http 304 https://registry.npmjs.org/binary

npm http 304 https://registry.npmjs.org/intersect

npm http 304 https://registry.npmjs.org/readable-stream

npm http 304 https://registry.npmjs.org/deep-extend

npm http 304 https://registry.npmjs.org/touch/0.0.2

npm http 304 https://registry.npmjs.org/jsonify

npm http GET https://registry.npmjs.org/sigmund

npm http 304 https://registry.npmjs.org/json-stringify-safe

npm http GET https://registry.npmjs.org/mute-stream

npm http 304 https://registry.npmjs.org/qs

npm http 304 https://registry.npmjs.org/mkpath

npm http 304 https://registry.npmjs.org/uuid

npm http 304 https://registry.npmjs.org/http-signature

npm http 304 https://registry.npmjs.org/forever-agent

npm http 304 https://registry.npmjs.org/oauth-sign

npm http 304 https://registry.npmjs.org/mime

npm http 304 https://registry.npmjs.org/tough-cookie

npm http 304 https://registry.npmjs.org/tunnel-agent

npm http 304 https://registry.npmjs.org/aws-sign2

npm http GET https://registry.npmjs.org/request-replay

npm http 304 https://registry.npmjs.org/hawk

npm http 304 https://registry.npmjs.org/lodash.isfunction

npm http 304 https://registry.npmjs.org/form-data

npm http 304 https://registry.npmjs.org/node-uuid

npm http 304 https://registry.npmjs.org/lodash.now

npm http 304 https://registry.npmjs.org/lodash.isobject

npm http 304 https://registry.npmjs.org/cli-color

npm http 304 https://registry.npmjs.org/sigmund

npm http GET https://registry.npmjs.org/redeyed

npm http GET https://registry.npmjs.org/ansicolors

npm http 304 https://registry.npmjs.org/readline2

npm http 304 https://registry.npmjs.org/mute-stream/0.0.4

npm http 304 https://registry.npmjs.org/through

npm http GET https://registry.npmjs.org/block-stream

npm http 304 https://registry.npmjs.org/request-replay

npm http 304 https://registry.npmjs.org/redeyed

npm http 304 https://registry.npmjs.org/ansicolors

npm http 304 https://registry.npmjs.org/mute-stream

npm http 304 https://registry.npmjs.org/block-stream

npm http GET https://registry.npmjs.org/lodash._isnative

npm http GET https://registry.npmjs.org/lodash._objecttypes

npm http GET https://registry.npmjs.org/combined-stream

npm http GET https://registry.npmjs.org/wordwrap

npm http GET https://registry.npmjs.org/minimist

npm http 304 https://registry.npmjs.org/lodash._isnative

npm http 304 https://registry.npmjs.org/combined-stream

npm http 304 https://registry.npmjs.org/wordwrap

npm http 304 https://registry.npmjs.org/minimist

npm http 304 https://registry.npmjs.org/lodash._objecttypes

npm http GET https://registry.npmjs.org/argparse

npm http GET https://registry.npmjs.org/esprima

npm http GET https://registry.npmjs.org/asn1/0.1.11

npm http GET https://registry.npmjs.org/assert-plus/0.1.2

npm http GET https://registry.npmjs.org/ctype/0.5.2

npm http GET https://registry.npmjs.org/core-util-is

npm http GET https://registry.npmjs.org/string_decoder

npm http GET https://registry.npmjs.org/isarray/0.0.1

npm http 304 https://registry.npmjs.org/asn1/0.1.11

npm http 304 https://registry.npmjs.org/assert-plus/0.1.2

npm http 304 https://registry.npmjs.org/core-util-is

npm http 304 https://registry.npmjs.org/ctype/0.5.2

npm http 304 https://registry.npmjs.org/isarray/0.0.1

npm http 304 https://registry.npmjs.org/argparse

npm http 304 https://registry.npmjs.org/string_decoder

npm http 304 https://registry.npmjs.org/esprima

npm http GET https://registry.npmjs.org/es5-ext

npm http GET https://registry.npmjs.org/memoizee

npm http GET https://registry.npmjs.org/chainsaw

npm http GET https://registry.npmjs.org/buffers

npm http 304 https://registry.npmjs.org/chainsaw

npm http 304 https://registry.npmjs.org/memoizee

npm http 304 https://registry.npmjs.org/buffers

npm http GET https://registry.npmjs.org/delayed-stream/0.0.5

npm http 200 https://registry.npmjs.org/es5-ext

npm http 304 https://registry.npmjs.org/delayed-stream/0.0.5

npm http GET https://registry.npmjs.org/aws-sign

npm http GET https://registry.npmjs.org/cookie-jar

npm http GET https://registry.npmjs.org/traverse

npm http GET https://registry.npmjs.org/punycode

npm http 304 https://registry.npmjs.org/aws-sign

npm http 304 https://registry.npmjs.org/cookie-jar

npm http GET https://registry.npmjs.org/hoek

npm http GET https://registry.npmjs.org/boom

npm http GET https://registry.npmjs.org/cryptiles

npm http GET https://registry.npmjs.org/sntp

npm http 304 https://registry.npmjs.org/traverse

npm http 304 https://registry.npmjs.org/punycode

npm http 304 https://registry.npmjs.org/cryptiles

npm http 304 https://registry.npmjs.org/hoek

npm http 304 https://registry.npmjs.org/sntp

npm http 304 https://registry.npmjs.org/boom

npm http GET https://registry.npmjs.org/eyes

npm http GET https://registry.npmjs.org/loggly

npm http GET https://registry.npmjs.org/stack-trace

npm http GET https://registry.npmjs.org/underscore

npm http 304 https://registry.npmjs.org/stack-trace

npm http 304 https://registry.npmjs.org/loggly

npm http 304 https://registry.npmjs.org/underscore

npm http GET https://registry.npmjs.org/event-emitter

npm http GET https://registry.npmjs.org/next-tick

npm http 304 https://registry.npmjs.org/eyes

npm http GET https://registry.npmjs.org/uglify-js

npm http 304 https://registry.npmjs.org/event-emitter

npm http 304 https://registry.npmjs.org/next-tick

npm http 304 https://registry.npmjs.org/uglify-js

npm http GET https://registry.npmjs.org/timespan

npm http 304 https://registry.npmjs.org/timespan

npm http GET https://registry.npmjs.org/source-map

npm http 304 https://registry.npmjs.org/source-map

C:\Users\User\AppData\Roaming\npm\amberc -> C:\Users\User\AppData\Roaming\npm\node_modules\amber-cli\cli\support\amberc-cli.js

C:\Users\User\AppData\Roaming\npm\amber -> C:\Users\User\AppData\Roaming\npm\node_modules\amber-cli\cli\support\amber-cli.js

amber-cli@0.0.3 C:\Users\User\AppData\Roaming\npm\node_modules\amber-cli

├── amdefine@0.0.8

├── grunt-init-amber@0.0.1

├── es6-promise@0.1.1

├── amber@0.12.4

├── grunt-init@0.3.1 (semver@1.0.14, colors@0.6.2, async@0.2.10, hooker@0.2.3, lodash@2.4.1, grunt@0.4.4, prompt@0.1.12)

└── bower@1.3.2 (is-root@0.1.0, junk@0.2.2, stringify-object@0.2.0, abbrev@1.0.4, chmodr@0.1.0, which@1.0.5, osenv@0.0.3, archy@0.0.2, graceful-fs@2.0.3, lockfile@0.4.2, open@0.0.5, rimraf@2.2.6, bower-endpoint-parser@0.2.1, bower-logger@0.2.2, lru-cache@2.5.0, nopt@2.1.2, retry@0.6.0, tmp@0.0.23, mkdirp@0.3.5, chalk@0.4.0, q@1.0.1, request-progress@0.3.1, semver@2.2.1, p-throttler@0.0.1, bower-json@0.4.0, shell-quote@1.4.1, fstream@0.1.25, promptly@0.2.0, fstream-ignore@0.0.7, tar@0.1.19, glob@3.2.9, decompress-zip@0.0.6, request@2.33.0, handlebars@1.3.0, inquirer@0.4.1, cardinal@0.4.4, insight@0.3.1, bower-config@0.5.0, update-notifier@0.1.8, mout@0.9.1, bower-registry-client@0.1.6)

User@Techlab ~

$ cd Amber/

User@Techlab ~/Amber

$ mkdir 20140414_1558

User@Techlab ~/Amber

$ cd *1558

User@Techlab ~/Amber/20140414_1558

$ ls

User@Techlab ~/Amber/20140414_1558

$ amber init

Welcome to Amber version 0.13.0-pre (NodeJS 0.10.26).

Running "init:c\:\\Users\\User\\AppData\\Roaming\\npm\\node_modules\\amber-cli\\node_modules\\grunt-init-amber" (init) task

This task will create one or more files in the current directory, based on the

environment and the answers to a few questions. Note that answering "?" to any

question will show question-specific help and answering "none" to most questions

will leave its value blank.

"grunt-init-amber" template notes:

Project title should be a human-readable title.

Please answer the following:

[?] Project name (AmberApplication)

[?] Project title (Amberapplication)

[?] Description (Amber Application.)

[?] The namespace used to store your Amber Packages.

[?] The version of Amber to use. Must be >= 0.12.4 (>= 0.12.4)

[?] Version (0.1.0)

[?] Project git repository (git://github.com/User/20140414_1558.git)

[?] Project homepage (https://github.com/User/20140414_1558)

[?] Project issues tracker (https://github.com/User/20140414_1558/issues)

[?] Licenses (MIT)

[?] Author name (Philippe Back)

[?] Author email ([hidden email])

[?] Author url (none)

[?] Do you need to make any changes to the above before continuing? (y/N)

Writing .npmignore...OK

Writing Gruntfile.js...OK

Writing README.md...OK

Writing index.html...OK

Writing src/AmberApplication.js...OK

Writing src/AmberApplication.st...OK

Writing LICENSE-MIT...OK

Initialized from template "grunt-init-amber".

You should now install project dependencies with bower install. Afterwards,

start the development server with ./bower_components/amber/bin/amber serve.

Your application is then accessible via http://localhost:4000/

Done, without errors.

bower amber#~>= 0.12.4 cached git://github.com/amber-smalltalk/amber.git#0.12.4

bower amber#~>= 0.12.4 validate 0.12.4 against git://github.com/amber-smalltalk/amber.git#~>= 0.12.4

bower bootstrap#* cached http://getbootstrap.com/2.3.2/assets/bootstrap.zip

bower bootstrap#* validate http://getbootstrap.com/2.3.2/assets/bootstrap.zip#*

bower jquery-tabby#* cached git://github.com/alanhogan/Tabby.git#925c5a416a

bower jquery-tabby#* validate 925c5a416a against git://github.com/alanhogan/Tabby.git#*

bower jquery#~1.10.2 cached git://github.com/jquery/jquery.git#1.10.2

bower jquery#~1.10.2 validate 1.10.2 against git://github.com/jquery/jquery.git#~1.10.2

bower codemirror#~3.20.0 cached git://github.com/marijnh/CodeMirror.git#3.20.0

bower codemirror#~3.20.0 validate 3.20.0 against git://github.com/marijnh/CodeMirror.git#~3.20.0

bower es5-shim#~2.1.0 cached git://github.com/es-shims/es5-shim.git#2.1.0

bower es5-shim#~2.1.0 validate 2.1.0 against git://github.com/es-shims/es5-shim.git#~2.1.0

bower showdown#~0.3.1 cached git://github.com/coreyti/showdown.git#0.3.1

bower showdown#~0.3.1 validate 0.3.1 against git://github.com/coreyti/showdown.git#~0.3.1

bower require-css#~0.0.8 cached git://github.com/guybedford/require-css.git#0.0.8

bower require-css#~0.0.8 validate 0.0.8 against git://github.com/guybedford/require-css.git#~0.0.8

bower jquery-ui#~1.10.3 cached git://github.com/components/jqueryui.git#1.10.4

bower jquery-ui#~1.10.3 validate 1.10.4 against git://github.com/components/jqueryui.git#~1.10.3

bower jquery#>=1.6 cached git://github.com/jquery/jquery.git#2.1.0

bower jquery#>=1.6 validate 2.1.0 against git://github.com/jquery/jquery.git#>=1.6

bower bootstrap#* new version for http://getbootstrap.com/2.3.2/assets/bootstrap.zip#*

bower bootstrap#* resolve http://getbootstrap.com/2.3.2/assets/bootstrap.zip#*

bower bootstrap#* download http://getbootstrap.com/2.3.2/assets/bootstrap.zip

bower bootstrap#* extract bootstrap.zip

bower bootstrap#* resolved http://getbootstrap.com/2.3.2/assets/bootstrap.zip

bower amber#~>= 0.12.4 install amber#0.12.4

bower jquery-tabby#* install jquery-tabby#925c5a416a

bower require-css#~0.0.8 install require-css#0.0.8

bower jquery-ui#~1.10.3 install jquery-ui#1.10.4

bower es5-shim#~2.1.0 install es5-shim#2.1.0

bower showdown#~0.3.1 install showdown#0.3.1

bower codemirror#~3.20.0 install codemirror#3.20.0

bower jquery#~1.10.2 install jquery#1.10.2

bower bootstrap#* install bootstrap

amber#0.12.4 bower_components\amber

├── bootstrap

├── codemirror#3.20.0

├── es5-shim#2.1.0

├── jquery#1.10.2

├── jquery-tabby#925c5a416a

├── jquery-ui#1.10.4

├── require-css#0.0.8

└── showdown#0.3.1

jquery-tabby#925c5a416a bower_components\jquery-tabby

require-css#0.0.8 bower_components\require-css

jquery-ui#1.10.4 bower_components\jquery-ui

└── jquery#1.10.2

es5-shim#2.1.0 bower_components\es5-shim

showdown#0.3.1 bower_components\showdown

codemirror#3.20.0 bower_components\codemirror

jquery#1.10.2 bower_components\jquery

bootstrap bower_components\bootstrap

User@Techlab ~/Amber/20140414_1558

$ ls

Gruntfile.js README.md bower_components src

LICENSE-MIT bower.json index.html

User@Techlab ~/Amber/20140414_1558

$ amber serve

Welcome to Amber version 0.13.0-pre (NodeJS 0.10.26).

Starting file server on http://127.0.0.1:4000

On Mon, Apr 14, 2014 at 3:36 PM, Herby Vojčík <[hidden email]> wrote:

Ok, the news:

There is 'amber-cli' in npm now.

So, if you want to use amber init, and officially be amongst the first who will use amber cli tool from its own repo, as it should be soon blessed, in repo, you should do only these steps.

1. Uninstall old global amber:

(sudo) npm -g uninstall amber

2. Install the amber-cli:

(sudo) npm -g install amber-cli

3. Initialize your project:

mkdir myproj
cd myproj
amber init

4. Go on:

amber serve
browse http://localhost:4000/

Herby

P.S.: Let me know if something gone wrong... it shouldn't ;-) for me it works on Windows.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

ambercli-14-04-14 16-00-22.png (508K) Download Attachment

Hannes Hirzel

Re: amber init, working

In reply to this post by Herby Vojčík

On 4/14/14, Herby Vojčík <[hidden email]> wrote:

> Ok, the news:
>
> There is 'amber-cli' in npm now.
>
> So, if you want to use amber init, and officially be amongst the first
> who will use amber cli tool from its own repo, as it should be soon
> blessed, in repo, you should do only these steps.
>
> 1. Uninstall old global amber:
>
> (sudo) npm -g uninstall amber
>
> 2. Install the amber-cli:
>
> (sudo) npm -g install amber-cli
>
> 3. Initialize your project:
>
> mkdir myproj
> cd myproj
> amber init
>
> 4. Go on:
>
> amber serve
> browse http://localhost:4000/
>
> Herby
>
> P.S.: Let me know if something gone wrong... it shouldn't ;-) for me it
> works on Windows.
>

Herby Vojčík

Re: amber init, working

Interesting... I had report on other problems in unix regardng crlf (I first published from Windows), so I publish new version from a UNIX.

You may try if it does not end up better.

Thanks for report, Herby

H. Hirzel wrote:

> On 4/14/14, Herby Vojčík<[hidden email]> wrote:
>> Ok, the news:
>>
>> There is 'amber-cli' in npm now.
>>
>> So, if you want to use amber init, and officially be amongst the first
>> who will use amber cli tool from its own repo, as it should be soon
>> blessed, in repo, you should do only these steps.
>>
>> 1. Uninstall old global amber:
>>
>> (sudo) npm -g uninstall amber
>>
>> 2. Install the amber-cli:
>>
>> (sudo) npm -g install amber-cli
>>
>> 3. Initialize your project:
>>
>> mkdir myproj
>> cd myproj
>> amber init
>>
>> 4. Go on:
>>
>> amber serve
>> browse http://localhost:4000/
>>
>> Herby
>>
>> P.S.: Let me know if something gone wrong... it shouldn't ;-) for me it
>> works on Windows.
>>
>
> H

erby,

>
> I do not get amber-cli properly on Linux Mint (Ubuntu 12.04LTS). After
> installing (see log below).
>
> I get the following answers
>
> user@user-Latitude ~ $ amber-cli
> amber-cli: command not found
> user@user-Latitude ~ $ amber
> : No such file or directory
> user@user-Latitude ~ $ amber help
> : No such file or directory
> user@user-Latitude ~ $
>
> ...................................................................................
> amber-cli installation log
> ....................................................................................
>
>
>
> user@user-Latitude ~ $ sudo npm -g uninstall amber
> [sudo] password for user:
> unbuild amber@0.13.0-pre
>
>
> user@user-Latitude ~ $ sudo npm -g install amber-cli
> npm http GET https://registry.npmjs.org/amber-cli
> npm http 200 https://registry.npmjs.org/amber-cli
> npm http GET https://registry.npmjs.org/amber-cli/-/amber-cli-0.0.3.tgz
> npm http 200 https://registry.npmjs.org/amber-cli/-/amber-cli-0.0.3.tg

semver

registry.npmjs.org/junk

p GET https://registry.npmjs.org/is-root

//registry.npmjs.org/rimraf

nore

.org/promptly

mjs.org/object-assign

registry.npmjs.org/readable-stream

http GET https://registry.npmjs.org/inherits

rits

pmjs.org/wordwrap

s.org/http-signature

ttp GET https://registry.npmjs.org/assert-plus/0.1.2

https://registry.npmjs.org/uglify-js

GET https://registry.npmjs.org/lodash._isnative

delayed-stream/0.0.5

cli/support/amber-cli.js

> /usr/local/bin/amberc ->
> /usr/local/lib/node_modules/amber-cli/cli/support/amberc-cli.js
> amber-cli@0.0.3 /usr/local/lib/node_modules/amber-cli
> ├── grunt-init-amber@0.0.1
> ├── amdefine@0.0.8
> ├── es6-promise@0.1.1
> ├── amber@0.12.4
> ├── grunt-init@0.3.1 (semver@1.0.14, colors@0.6.2, hooker@0.2.3,
> async@0.2.10, lodash@2.4.1, prompt@0.1.12, grunt@0.4.4)
> └── bower@1.3.2 (is-root@0.1.0, junk@0.2.2, stringify-object@0.2.0,
> abbrev@1.0.4, which@1.0.5, chmodr@0.1.0, osenv@0.0.3, archy@0.0.2,
> graceful-fs@2.0.3, lockfile@0.4.2, rimraf@2.2.6, open@0.0.5,
> lru-cache@2.5.0, bower-logger@0.2.2, bower-endpoint-parser@0.2.1,
> nopt@2.1.2, retry@0.6.0, mkdirp@0.3.5, tmp@0.0.23, q@1.0.1,
> semver@2.2.1, p-throttler@0.0.1, chalk@0.4.0, request-progress@0.3.1,
> mout@0.9.1, bower-json@0.4.0, shell-quote@1.4.1, fstream@0.1.25,
> tar@0.1.19, glob@3.2.9, fstream-ignore@0.0.7, promptly@0.2.0,
> bower-config@0.5.0, decom

press-zip@0.0.6, request@2.33.0,
> handlebars@1.3.0, cardinal@0.4.4, bower-registry-client@0.1.6,
> insight@0.3.1, inquirer@0.4.1, update-notifier@0.1.8)
>
>
> user@user ~ $ amber help
> : No such file or directory
> user@user-Latitude ~ $
>

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Herby Vojčík

Re: amber init, working

In reply to this post by philippeback

[hidden email] wrote:
> Worked nicely until trying to open Helios. See screenshot

This is strange, as the error seems to be pretty inside amber, and
amber-cli just repackaged cli tooling and got rid of amber itself,
bringing it with itself as the dependency...

I tried the whole procedure in Windows, and it worked.

I also got some reports as to problem with cr-lf in Unixes (I published
from Windows), so I published new version from Unix environment (there
it should only have lfs)... you may try if this wasn't the reason...

I don't have graphical Unix, I may try to vnc to some of the friend's
Macs to try it out there...

Thanks for reporting, Herby

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Nicolas Petton

Re: amber init, working

Trying on Ubuntu :)

Nico

Herby Vojčík writes:

> [hidden email] wrote:
>> Worked nicely until trying to open Helios. See screenshot
>
> This is strange, as the error seems to be pretty inside amber, and
> amber-cli just repackaged cli tooling and got rid of amber itself,
> bringing it with itself as the dependency...
>
> I tried the whole procedure in Windows, and it worked.
>
> I also got some reports as to problem with cr-lf in Unixes (I published
> from Windows), so I published new version from Unix environment (there
> it should only have lfs)... you may try if this wasn't the reason...
>
> I don't have graphical Unix, I may try to vnc to some of the friend's
> Macs to try it out there...
>
> Thanks for reporting, Herby

--
Nicolas Petton
http://nicolas-petton.fr

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

philippeback

Re: amber init, working

In reply to this post by Herby Vojčík

I searched some more.

I replaced the index.html with the one of the kickstart and things worked with the components and amber server.

So the issue was elsewhere.

I did a diff between the two things and I ended up getting the Helios UI showing by commenting out the AmberApplication bit.

There must be something wrong in the code or in the way src does the mapping.

With the st and js mappings and the older MyPackage, the thing loaded.

<!DOCTYPE html>

<html>

<head>

<title>Amberapplication</title>

</head>

<body>

require.config({ paths: {

'': 'src'

}});

require([

'amber/devel',

// '/AmberApplication'

], function (smalltalk) {

//used for all new packages in IDE

smalltalk.initialize({

'transport.defaultAmdNamespace': ""

});

</script>

<button onclick="require('amber/helpers').globals.Browser._open()">legacy IDE</button>

<button onclick="require('amber/helpers').popupHelios()">Helios IDE</button>

</body>

</html>

On Mon, Apr 14, 2014 at 5:02 PM, Herby Vojčík <[hidden email]> wrote:

[hidden email] wrote:

Worked nicely until trying to open Helios. See screenshot

This is strange, as the error seems to be pretty inside amber, and amber-cli just repackaged cli tooling and got rid of amber itself, bringing it with itself as the dependency...

I tried the whole procedure in Windows, and it worked.

I also got some reports as to problem with cr-lf in Unixes (I published from Windows), so I published new version from Unix environment (there it should only have lfs)... you may try if this wasn't the reason...

I don't have graphical Unix, I may try to vnc to some of the friend's Macs to try it out there...

Thanks for reporting, Herby

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Herby Vojčík

Re: amber init, working

[hidden email] wrote:

> I searched some more.
>
> I replaced the index.html with the one of the kickstart and things
> worked with the components and amber server.
> So the issue was elsewhere.
>
> I did a diff between the two things and I ended up getting the Helios
> UI showing by commenting out the AmberApplication bit.
> There must be something wrong in the code or in the way src does the
> mapping.
>
> With the st and js mappings and the older MyPackage, the thing loaded.
>
>
> <!DOCTYPE html>
> <html>
>
> <head>
> <title>Amberapplication</title>
> <meta http-equiv="content-type" content="text/html; />
> <meta name="author" content="Philippe Back" />
> <script type='text/javascript'
> src='bower_components/amber/support/requirejs/require.min.js'></script>
> <script type='text/javascript'
> src='bower_components/amber/support/amber.js'></script>
> </head>
>
> <body>
> <script type='text/javascript'>
> require.config({ paths: {
> '': 'src'

Oh, here's the
culprit!

You probably just pressed Enter all the way down to set up with defaults.
But you need to add some non-empty namespace!
(this should be an issue in grunt-init-amber, to enforce valid namespace)

> }});
> require([
> 'amber/devel',
> // '/AmberApplication'
> ], function (smalltalk) {
> //used for all new packages in IDE
> smalltalk.initialize({
> 'transport.defaultAmdNamespace': ""
> });
> });
> </script>
> <button
> onclick="require('amber/helpers').globals.Browser._open()">legacy
> IDE</button>
> <button onclick="require('amber/helpers').popupHelios()">Helios
> IDE</button>
> </body>
>
> </html>

philippeback

Re: amber init, working

Le 14 avr. 2014 17:54, "Herby Vojčík" <[hidden email]> a écrit :
>
>
>
> [hidden email] wrote:
>>
>> I searched some more.
>>
>> I replaced the index.html with the one of the kickstart and things worked with the components and amber server.
>> So the issue was elsewhere.
>>
>> I did a diff between the two things and I ended up getting the Helios UI showing by commenting out the AmberApplication bit.
>> There must be something wrong in the code or in the way src does the mapping.
>>
>> With the st and js mappings and the older MyPackage, the thing loaded.
>>
>>
>> <!DOCTYPE html>
>> <html>
>>
>> <head>
>> <title>Amberapplication</title>
>> <meta http-equiv="content-type" content="text/html; />
>>
>> <meta name="author" content="Philippe Back" />
>> <script type='text/javascript' src='bower_components/amber/support/requirejs/require.min.js'></script>
>> <script type='text/javascript' src='bower_components/amber/support/amber.js'></script>
>> </head>
>>
>> <body>
>> <script type='text/javascript'>
>> require.config({ paths: {
>> '': 'src'
>
>
> Oh, here's the culprit!
>
> You probably just pressed Enter all the way down to set up with defaults.
> But you need to add some non-empty namespace!
> (this should be an issue in grunt-init-amber, to enforce valid namespace)
>

I'll try with that and report back.
Cool to see that it is nothing complicated.
Obviously one starting will hit return a couple times in the huge list of questions.

>
>> }});
>> require([
>> 'amber/devel',
>> // '/AmberApplication'
>> ], function (smalltalk) {
>> //used for all new packages in IDE
>> smalltalk.initialize({
>> 'transport.defaultAmdNamespace': ""
>> });
>> });
>> </script>
>> <button onclick="require('amber/helpers').globals.Browser._open()">legacy IDE</button>
>> <button onclick="require('amber/helpers').popupHelios()">Helios IDE</button>
>> </body>
>>
>> </html>
>
>
> --
> You received this message because you are subscribed to the Google Groups "amber-lang" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> For more options, visit https://groups.google.com/d/optout.

Herby Vojčík

Re: amber init, working

In reply to this post by Herby Vojčík

Herby Vojčík wrote:
>
>
> [hidden email] wrote:
>> Worked nicely until trying to open Helios. See screenshot
>
> I don't have graphical Unix, I may try to vnc to some of the friend's
> Macs to try it out there...

I tested on two Macs, works fine.

Now only some Linux... ;-)

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

Bernat Romagosa

Re: amber init, working

Tested on an Ubuntu 13.10 box. Worked flawlessly!

Congratulations and thank you SO MUCH! You have no idea how much easier this makes my life!

I'll try on my Debian Wheezy box and let you know too!

2014-04-14 18:20 GMT+02:00 Herby Vojčík <[hidden email]>:

Herby Vojčík wrote:

[hidden email] wrote:

Worked nicely until trying to open Helios. See screenshot

I don't have graphical Unix, I may try to vnc to some of the friend's Macs to try it out there...

I tested on two Macs, works fine.

Now only some Linux... ;-)

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
Bernat Romagosa.

Hannes Hirzel

Re: amber init, working

In reply to this post by Herby Vojčík

Retest done. Now this time amber-cli works OK on Linux Mint (Ubuntu 12.04LTS)

sudo npm -g uninstall amber-cli
sudo npm -g install amber-cli
mkdir myAmberProj
cd myAmberProj
amber init
// answer questions and in particular non-empty Namespace
amber serve

--Hannes

On 4/14/14, Herby Vojčík <[hidden email]> wrote:

Tim Mackinnon

Re: amber init, working

In reply to this post by Herby Vojčík

Yes - it works on my mac as well (this wasn't a clean install - it was the bower uninstall followed by the reinstall)

Tim

On 14 Apr 2014, at 17:20, Herby Vojčík <[hidden email]> wrote:

>
>
>
> Herby Vojčík wrote:
>>
>>
>> [hidden email] wrote:
>>> Worked nicely until trying to open Helios. See screenshot
>>
>> I don't have graphical Unix, I may try to vnc to some of the friend's Macs to try it out there...
>
> I tested on two Macs, works fine.
>
> Now only some Linux... ;-)
>
> --
> You received this message because you are subscribed to the Google Groups "amber-lang" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> For more options, visit https://groups.google.com/d/optout.