Best practices!

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Best practices!

NorbertHartl
Hi guys,

didn’t have time to do amber stuff the last couple of months. Now I’m trying getting up to speed with a new project. But I struggle to find the right information how to do things. Most stuff I find is still for 0.10 or 0.12 and the world didn’t stop turning. I know most of the topics come up every now and then so excuse my lazy inquiry.

I want to know what you would consider current best practices when starting an amber project:

- Is there an up-to-date skeleton to use? Are there any hints about directory setup that works for any of you?
- What is the status about require and shims. Last time I had problems to get jquery, google maps and modules for them integrated in the require process. Any examples out there? Is it now possible to use r.js or similar to produce a compact version for deployment?
- What are you using for backend communication? Plain requests, backbone.js, knockout.js, ….?
- Any advize what to use for widgets and UI components. Last time I was pretty satisfied with plain smalltalk for UI components.

Norbert

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

Nicolas Petton
Hi Norbert!

Norbert Hartl writes:

> Hi guys,
>
> didn’t have time to do amber stuff the last couple of months. Now I’m trying getting up to speed with a new project. But I struggle to find the right information how to do things. Most stuff I find is still for 0.10 or 0.12 and the world didn’t stop turning. I know most of the topics come up every now and then so excuse my lazy inquiry.
>
> I want to know what you would consider current best practices when starting an amber project:
>
> - Is there an up-to-date skeleton to use? Are there any hints about
> directory setup that works for any of you?

The best way to go is using amber as a bower library. You can do as
explained on the readme:

# Install the CLI tool `amber`
npm install -g amber

# Load amber via bower in your project
bower init
bower install amber --save

The first line will install the CLI tools, and the second will install
amber in the bower_components/ directory of your project.

You first need to install npm and bower.

Then to structure your project, I would suggest to take a look at
https://github.com/amber-smalltalk/amber/wiki/Writing-my-first-app, it
should help.

> - What is the status about require and shims. Last time I had problems
> to get jquery, google maps and modules for them integrated in the
> require process. Any examples out there? Is it now possible to use
> r.js or similar to produce a compact version for deployment?

That's 2 questions :)

- You can load our libraries with require without any trouble, and if
you do have troubles, please tell us! I'm writing a documentation for
Amber, and if anything isn't obvious, I want to write it there :)

- Yes, it is possible to use r.js (there was a thread about that on
here, I'll try to find it)

> - What are you using for backend communication? Plain requests,
> backbone.js, knockout.js, ….?

I'm using a custom-made amber lib (that I plan to share in the future)
to communicate with a Zinc server. But that's just me. Anything will do ;)

> - Any advize what to use for widgets and UI components. Last time I
> was pretty satisfied with plain smalltalk for UI components.

I really like bootstrap as the backbone of my css. For the widget logic,
I usually stick with Amber widgets/components. But you could use
jQueryUI, etc. if you like that.

Hope this helps!
Nico

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

laci
Bower fails on installing bootstrap 2.3.2:

C:\Users\Laci>bower install amber
bower amber#*                   cached git://github.com/amber-smalltalk/amber.git#0.12.2
bower amber#*                 validate 0.12.2 against git://github.com/amber-smalltalk/amber.git#*
bower bootstrap#*           not-cached 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 jquery-tabby#*            cached git://github.com/alanhogan/Tabby.git#925c5a416a
bower jquery-tabby#*          validate 925c5a416a against git://github.com/alanhogan/Tabby.git#*
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 codemirror#~3.13.0        cached git://github.com/marijnh/CodeMirror.git#3.13.0
bower codemirror#~3.13.0      validate 3.13.0 against git://github.com/marijnh/CodeMirror.git#~3.13.0
bower jquery#~1.8.3             cached git://github.com/components/jquery.git#1.8.3
bower jquery#~1.8.3           validate 1.8.3 against git://github.com/components/jquery.git#~1.8.3
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 es5-shim#~2.1.0           cached git://github.com/kriskowal/es5-shim.git#2.1.0
bower es5-shim#~2.1.0         validate 2.1.0 against git://github.com/kriskowal/es5-shim.git#~2.1.0
bower bootstrap#*              extract bootstrap.zip
bower bootstrap#*                EPERM EPERM, rename 'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'

Stack trace:
Error: EPERM, rename 'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'

Console trace:
Trace
    at StandardRenderer.error (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
    at Logger.updateNotifier.packageName (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
    at Logger.EventEmitter.emit (events.js:95:17)
    at Logger.emit (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
    at C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
    at _rejected (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
    at C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:30
    at Promise.when (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:1079:31)
    at Promise.promise.promiseDispatch (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
    at C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44

System info:
Bower version: 1.2.8
Node version: 0.10.24
OS: Windows_NT 6.0.6002 ia32

The only way I could resolve that setting up amber from ZIP and fetching each dependencies one by one.
Would be great if bower could install amber.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

Herby Vojčík
Try again.

People had these EPERM errors, but it always somehow settled.

(and it's better to install it with --save, to save the dependency)

laci wrote:

> Bower fails on installing bootstrap 2.3.2:
>
> C:\Users\Laci>bower install amber
> bower amber#*                   cached
> git://github.com/amber-smalltalk/amber.git#0.12.2
> bower amber#*                 validate 0.12.2 against
> git://github.com/amber-smalltalk/amber.git#*
> bower bootstrap#*           not-cached
> 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 jquery-tabby#*            cached
> git://github.com/alanhogan/Tabby.git#925c5a416a
> bower jquery-tabby#*          validate 925c5a416a against
> git://github.com/alanhogan/Tabby.git#*
> 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 codemirror#~3.13.0        cached
> git://github.com/marijnh/CodeMirror.git#3.13.0
> bower codemirror#~3.13.0      validate 3.13.0 against
> git://github.com/marijnh/CodeMirror.git#~3.13.0
> bower jquery#~1.8.3             cached
> git://github.com/components/jquery.git#1.8.3
> bower jquery#~1.8.3           validate 1.8.3 against
> git://github.com/components/jquery.git#~1.8.3
> 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 es5-shim#~2.1.0           cached
> git://github.com/kriskowal/es5-shim.git#2.1.0
> bower es5-shim#~2.1.0         validate 2.1.0 against
> git://github.com/kriskowal/es5-shim.git#~2.1.0
> bower bootstrap#*              extract bootstrap.zip
> bower bootstrap#*                EPERM E
PERM, rename

> 'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
> Stack trace:
> Error: EPERM, rename
> 'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
> Console trace:
> Trace
>      at StandardRenderer.error
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
>      at Logger.updateNotifier.packageName
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
>      at Logger.EventEmitter.emit (events.js:95:17)
>      at Logger.emit
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
>      at
> C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
>      at _rejected
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
>      at
> C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:
30

>      at Promise.when
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:1079:31)
>      at Promise.promise.promiseDispatch
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
>      at
> C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44
>
> System info:
> Bower version: 1.2.8
> Node version: 0.10.24
> OS: Windows_NT 6.0.6002 ia32
>
> The only way I could resolve that setting up amber from ZIP and fetching
> each dependencies one by one.
> Would be great if bower could install amber.
>
>
>
> --
> View this message in context: http://forum.world.st/Best-practices-tp4736458p4737693.html
> Sent from the Amber Smalltalk mailing list archive at Nabble.com.
>

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Re: Best practices!

laci
No luck. Running on Windows.
Falls over on bootstrap.
----Original Message----
From : [hidden email]
Date : 18/01/2014 13:17
To : [hidden email]
Subject : Re: Best practices!

Try again.

People had these EPERM errors, but it always somehow settled.

(and it's better to install it with --save, to save the dependency)

laci wrote:

> Bower fails on installing bootstrap 2.3.2:
>
> C:\Users\Laci>bower install amber
> bower amber#*                   cached
> git://github.com/amber-smalltalk/amber.git#0.12.2
> bower amber#*                 validate 0.12.2 against
> git://github.com/amber-smalltalk/amber.git#*
> bower bootstrap#*           not-cached
> 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 jquery-tabby#*            cached
> git://github.com/alanhogan/Tabby.git#925c5a416a
> bower jquery-tabby#*          validate 925c5a416a against
> git://github.com/alanhogan/Tabby.git#*
> 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 codemirror#~3.13.0        cached
> git://github.com/marijnh/CodeMirror.git#3.13.0
> bower codemirror#~3.13.0      validate 3.13.0 against
> git://github.com/marijnh/CodeMirror.git#~3.13.0
> bower jquery#~1.8.3             cached
> git://github.com/components/jquery.git#1.8.3
> bower jquery#~1.8.3           validate 1.8.3 against
> git://github.com/components/jquery.git#~1.8.3
> 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 es5-shim#~2.1.0           cached
> git://github.com/kriskowal/es5-shim.git#2.1.0
> bower es5-shim#~2.1.0         validate 2.1.0 against
> git://github.com/kriskowal/es5-shim.git#~2.1.0
> bower bootstrap#*              extract bootstrap.zip
> bower bootstrap#*                EPERM E
PERM, rename

> 'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
> Stack trace:
> Error: EPERM, rename
> 'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
> Console trace:
> Trace
>      at StandardRenderer.error
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
>      at Logger.updateNotifier.packageName
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
>      at Logger.EventEmitter.emit (events.js:95:17)
>      at Logger.emit
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
>      at
> C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
>      at _rejected
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
>      at
> C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:
30

>      at Promise.when
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:1079:31)
>      at Promise.promise.promiseDispatch
> (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
>      at
> C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44
>
> System info:
> Bower version: 1.2.8
> Node version: 0.10.24
> OS: Windows_NT 6.0.6002 ia32
>
> The only way I could resolve that setting up amber from ZIP and fetching
> each dependencies one by one.
> Would be great if bower could install amber.
>
>
>
> --
> View this message in context: http://forum.world.st/Best-practices-tp4736458p4737693.html
> Sent from the Amber Smalltalk mailing list archive at Nabble.com.
>
--
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/groups/opt_out.



If you reply to this email, your message will be added to the discussion below:
http://forum.world.st/Best-practices-tp4736458p4737695.html
To start a new topic under Amber Smalltalk, email [hidden email]
To unsubscribe from Amber Smalltalk, click here.
NAML


Reply | Threaded
Open this post in threaded view
|

Re: Re: Best practices!

Herby Vojčík
Bad luck. I also work on Windows, and everything's fine.

The only difference which strikes me (as it fails on rename) is that I work on D:, C: is left for SW.

If that happens to be the case, you should fill an issue to bower (fail unzipping into same drive on Windows). Maybe the issue already is there...

Herby

laci wrote:

> No luck. Running on Windows.
> Falls over on bootstrap.
>
>     ----Original Message----
>     From : [hidden email] </user/SendEmail.jtp?type=node&node=4737712&i=0>
>     Date : 18/01/2014 13:17
>     To : [hidden email] </user/SendEmail.jtp?type=node&node=4737712&i=1>
>     Subject : Re: Best practices!
>
>     Try again.
>
>     People had these EPERM errors, but it always somehow settled.
>
>     (and it's better to install it with --save, to save the dependency)
>
>     laci wrote:
>
>     > Bower fails on installing bootstrap 2.3.2:
>     >
>     > C:\Users\Laci>bower install amber
>     > bower amber#* cached
>     > git://github.com/amber-small
talk/amber.git#0.12.2

>     > bower amber#* validate 0.12.2 against
>     > git://github.com/amber-smalltalk/amber.git#*
>     > bower bootstrap#* not-cached
>     > 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 jquery-tabby#* cached
>     > git://github.com/alanhogan/Tabby.git#925c5a416a
>     > bower jquery-tabby#* validate 925c5a416a against
>     > git://github.com/alanhogan/Tabby.git#*
>     > 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 codemirror#~3.13.0 cached
>     > git://github.com/marijnh/CodeMirror.git#3.13.0
>     > bower codemirror#~3.13.0 validate 3.13.0 against
>     > git://github.com/marij
nh/CodeMirror.git#~3.13.0

>     > bower jquery#~1.8.3 cached
>     > git://github.com/components/jquery.git#1.8.3
>     > bower jquery#~1.8.3 validate 1.8.3 against
>     > git://github.com/components/jquery.git#~1.8.3
>     > 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 es5-shim#~2.1.0 cached
>     > git://github.com/kriskowal/es5-shim.git#2.1.0
>     > bower es5-shim#~2.1.0 validate 2.1.0 against
>     > git://github.com/kriskowal/es5-shim.git#~2.1.0
>     > bower bootstrap#* extract bootstrap.zip
>     > bower bootstrap#* EPERM E
>     PERM, rename
>
>     >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
>     >
>     > Stack trace:
>     > Error: EPERM, rename
>     >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb
0848f2894a69\_wildcard'

>
>     >
>     > Console trace:
>     > Trace
>     > at StandardRenderer.error
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
>
>     > at Logger.updateNotifier.packageName
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
>
>     > at Logger.EventEmitter.emit (events.js:95:17)
>     > at Logger.emit
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
>
>     > at
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
>
>     > at _rejected
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
>
>     > at
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:
>
>     30
>
>     > at Promise.when
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modul
es\q\q.js:1079:31)

>
>     > at Promise.promise.promiseDispatch
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
>
>     > at
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44
>
>     >
>     > System info:
>     > Bower version: 1.2.8
>     > Node version: 0.10.24
>     > OS: Windows_NT 6.0.6002 ia32
>     >
>     > The only way I could resolve that setting up amber from ZIP and
>     fetching
>     > each dependencies one by one.
>     > Would be great if bower could install amber.
>     >
>     >
>     >
>     > --
>     > View this message in context:
>     http://forum.world.st/Best-practices-tp4736458p4737693.html
>     > Sent from the Amber Smalltalk mailing list archive at Nabble.com.
>     >
>     --
>     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]

>     </user/SendEmail.jtp?type=node&node=4737695&i=0>.
>     For more options, visit https://groups.google.com/groups/opt_out.
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://forum.world.st/Best-practices-tp4736458p4737695.html
>     To start a new topic under Amber Smalltalk, email [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737712&i=2>
>     To unsubscribe from Amber Smalltalk, click here.
>     NAML
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> ----------------
--------------------------------------------------------

> View this message in context: Re: Re: Best practices!
> <http://forum.world.st/Best-practices-tp4736458p4737712.html>
> Sent from the Amber Smalltalk mailing list archive
> <http://forum.world.st/Amber-Smalltalk-f3824463.html> at Nabble.com.
>
> --
> 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/groups/opt_out.

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Best practices!

laci
Thanks Herby.
This is where the problem lies.
----Original Message----
From : [hidden email]
Date : 18/01/2014 14:59
To : [hidden email]
Subject : Re: Re: Best practices!

Bad luck. I also work on Windows, and everything's fine.

The only difference which strikes me (as it fails on rename) is that I work on D:, C: is left for SW.

If that happens to be the case, you should fill an issue to bower (fail unzipping into same drive on Windows). Maybe the issue already is there...

Herby

laci wrote:

> No luck. Running on Windows.
> Falls over on bootstrap.
>
>     ----Original Message----
>     From : [hidden email] </user/SendEmail.jtp?type=node&node=4737712&i=0>
>     Date : 18/01/2014 13:17
>     To : [hidden email] </user/SendEmail.jtp?type=node&node=4737712&i=1>
>     Subject : Re: Best practices!
>
>     Try again.
>
>     People had these EPERM errors, but it always somehow settled.
>
>     (and it's better to install it with --save, to save the dependency)
>
>     laci wrote:
>
>     > Bower fails on installing bootstrap 2.3.2:
>     >
>     > C:\Users\Laci>bower install amber
>     > bower amber#* cached
>     > git://github.com/amber-small
talk/amber.git#0.12.2

>     > bower amber#* validate 0.12.2 against
>     > git://github.com/amber-smalltalk/amber.git#*
>     > bower bootstrap#* not-cached
>     > 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 jquery-tabby#* cached
>     > git://github.com/alanhogan/Tabby.git#925c5a416a
>     > bower jquery-tabby#* validate 925c5a416a against
>     > git://github.com/alanhogan/Tabby.git#*
>     > 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 codemirror#~3.13.0 cached
>     > git://github.com/marijnh/CodeMirror.git#3.13.0
>     > bower codemirror#~3.13.0 validate 3.13.0 against
>     > git://github.com/marij
nh/CodeMirror.git#~3.13.0

>     > bower jquery#~1.8.3 cached
>     > git://github.com/components/jquery.git#1.8.3
>     > bower jquery#~1.8.3 validate 1.8.3 against
>     > git://github.com/components/jquery.git#~1.8.3
>     > 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 es5-shim#~2.1.0 cached
>     > git://github.com/kriskowal/es5-shim.git#2.1.0
>     > bower es5-shim#~2.1.0 validate 2.1.0 against
>     > git://github.com/kriskowal/es5-shim.git#~2.1.0
>     > bower bootstrap#* extract bootstrap.zip
>     > bower bootstrap#* EPERM E
>     PERM, rename
>
>     >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
>     >
>     > Stack trace:
>     > Error: EPERM, rename
>     >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb
0848f2894a69\_wildcard'

>
>     >
>     > Console trace:
>     > Trace
>     > at StandardRenderer.error
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
>
>     > at Logger.updateNotifier.packageName
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
>
>     > at Logger.EventEmitter.emit (events.js:95:17)
>     > at Logger.emit
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
>
>     > at
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
>
>     > at _rejected
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
>
>     > at
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:
>
>     30
>
>     > at Promise.when
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modul
es\q\q.js:1079:31)

>
>     > at Promise.promise.promiseDispatch
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
>
>     > at
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44
>
>     >
>     > System info:
>     > Bower version: 1.2.8
>     > Node version: 0.10.24
>     > OS: Windows_NT 6.0.6002 ia32
>     >
>     > The only way I could resolve that setting up amber from ZIP and
>     fetching
>     > each dependencies one by one.
>     > Would be great if bower could install amber.
>     >
>     >
>     >
>     > --
>     > View this message in context:
>     http://forum.world.st/Best-practices-tp4736458p4737693.html
>     > Sent from the Amber Smalltalk mailing list archive at Nabble.com.
>     >
>     --
>     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]

>     </user/SendEmail.jtp?type=node&node=4737695&i=0>.
>     For more options, visit https://groups.google.com/groups/opt_out.
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://forum.world.st/Best-practices-tp4736458p4737695.html
>     To start a new topic under Amber Smalltalk, email [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737712&i=2>
>     To unsubscribe from Amber Smalltalk, click here.
>     NAML
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> ----------------
--------------------------------------------------------

> View this message in context: Re: Re: Best practices!
> <http://forum.world.st/Best-practices-tp4736458p4737712.html>
> Sent from the Amber Smalltalk mailing list archive
> <http://forum.world.st/Amber-Smalltalk-f3824463.html> at Nabble.com.
>
> --
> 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/groups/opt_out.
--
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/groups/opt_out.



If you reply to this email, your message will be added to the discussion below:
http://forum.world.st/Best-practices-tp4736458p4737720.html
To start a new topic under Amber Smalltalk, email [hidden email]
To unsubscribe from Amber Smalltalk, click here.
NAML


Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Best practices!

Herby Vojčík
Could you add a page / section about it somewhere in Amber wiki? With
link to the bower issue if it exists (or if not, create one)?

It happened a few times, it's fine to have it explained in some faq.

Herby

laci wrote:

> Thanks Herby.
> This is where the problem lies.
>
>     ----Original Message----
>      From : [hidden email] </user/SendEmail.jtp?type=node&node=4737723&i=0>
>     Date : 18/01/2014 14:59
>     To : [hidden email] </user/SendEmail.jtp?type=node&node=4737723&i=1>
>     Subject : Re: Re: Best practices!
>
>     Bad luck. I also work on Windows, and everything's fine.
>
>     The only difference which strikes me (as it fails on rename) is that
>     I work on D:, C: is left for SW.
>
>     If that happens to be the case, you should fill an issue to bower
>     (fail unzipping into same drive on Windows). Maybe the issue already
>     is there...
>
>     Herby
>
>     laci wrote:
>
>      > No luck. Running on Windows.
>      > Falls over on bootstrap.
>      >
>      > ----Original Message----
>      > From : [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737712&i=0>
>      > Date : 18/01/2014 13:17
>      > To : [hidden email] </user/SendEmail.jtp?type=node&node=4737712&i=1>
>      > Subject : Re: Best practices!
>      >
>      > Try again.
>      >
>      > People had these EPERM errors, but it always somehow settled.
>      >
>      > (and it's better to install it with --save, to save the dependency)
>      >
>      > laci wrote:
>      >
>      > > Bower fails on installing bootstrap 2.3.2:
>      > >
>      > > C:\Users\Laci>bower install amber
>      > > bower amber#* cached
>      > > git://github.com/amber-small
>     talk/amber.git#0.12.2
>
>      > > bower amber#* validate 0.12.2 against
>      > > git://github.com/amber-smalltalk/amber.git#*
>      > > bower bootstrap#* not-cached
>      > > 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 jquery-tabby#* cached
>      > > git://github.com/alanhogan/Tabby.git#925c5a416a
>      > > bower jquery-tabby#* validate 925c5a416a against
>      > > git://github.com/alanhogan/Tabby.git#*
>      > > 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 codemirror#~3.13.0 cached
>      > > git://github.com/marijnh/CodeMirror.git#3.13.0
>      > > bower codemirror#~3.13.0 validate 3.13.0 against
>      > > git://github.com/marij
>     nh/CodeMirror.git#~3.13.0
>
>      > > bower jquery#~1.8.3 cached
>      > > git://github.com/components/jquery.git#1.8.3
>      > > bower jquery#~1.8.3 validate 1.8.3 against
>      > > git://github.com/components/jquery.git#~1.8.3
>      > > 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 es5-shim#~2.1.0 cached
>      > > git://github.com/kriskowal/es5-shim.git#2.1.0
>      > > bower es5-shim#~2.1.0 validate 2.1.0 against
>      > > git://github.com/kriskowal/es5-shim.git#~2.1.0
>      > > bower bootstrap#* extract bootstrap.zip
>      > > bower bootstrap#* EPERM E
>      > PERM, rename
>      >
>      > >
>      >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
>      >
>      > >
>      > > Stack trace:
>      > > Error: EPERM, rename
>      > >
>      >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb
>
>     0848f2894a69\_wildcard'
>
>      >
>      > >
>      > > Console trace:
>      > > Trace
>      > > at StandardRenderer.error
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
>
>      >
>      > > at Logger.updateNotifier.packageName
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
>      >
>      > > at Logger.EventEmitter.emit (events.js:95:17)
>      > > at Logger.emit
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
>
>      >
>      > > at
>      > >
>      >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
>
>      >
>      > > at _rejected
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
>
>      >
>      > > at
>      > >
>      >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:
>
>      >
>      > 30
>      >
>      > > at Promise.when
>      > >
>      > (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modul
>     es\q\q.js:1079:31)
>
>      >
>      > > at Promise.promise.promiseDispatch
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
>
>      >
>      > > at
>      > >
>      >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44
>
>      >
>      > >
>      > > System info:
>      > > Bower version: 1.2.8
>      > > Node version: 0.10.24
>      > > OS: Windows_NT 6.0.6002 ia32
>      > >
>      > > The only way I could resolve that setting up amber from ZIP and
>      > fetching
>      > > each dependencies one by one.
>      > > Would be great if bower could install amber.
>      > >
>      > >
>      > >
>      > > --
>      > > View this message in context:
>      > http://forum.world.st/Best-practices-tp4736458p4737693.html
>      > > Sent from the Amber Smalltalk mailing list archive at Nabble.com.
>      > >
>      > --
>      > 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]
>
>      > </user/SendEmail.jtp?type=node&node=4737695&i=0>.
>      > For more options, visit https://groups.google.com/groups/opt_out.
>      >
>      >
>      >
>     ------------------------------------------------------------------------
>
>      > If you reply to this email, your message will be added to the
>      > discussion below:
>      > http://forum.world.st/Best-practices-tp4736458p4737695.html
>      > To start a new topic under Amber Smalltalk, email [hidden email]
>      > </user/SendEmail.jtp?type=node&node=4737712&i=2>
>      > To unsubscribe from Amber Smalltalk, click here.
>      > NAML
>      >
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>>
>
>      >
>      >
>      >
>      >
>      > ----------------
>     --------------------------------------------------------
>
>      > View this message in context: Re: Re: Best practices!
>      > <http://forum.world.st/Best-practices-tp4736458p4737712.html>
>      > Sent from the Amber Smalltalk mailing list archive
>      > <http://forum.world.st/Amber-Smalltalk-f3824463.html> at Nabble.com.
>      >
>      > --
>      > 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]
>     </user/SendEmail.jtp?type=node&node=4737720&i=0>.
>      > For more options, visit https://groups.google.com/groups/opt_out.
>     --
>     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]
>     </user/SendEmail.jtp?type=node&node=4737720&i=1>.
>     For more options, visit https://groups.google.com/groups/opt_out.
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://forum.world.st/Best-practices-tp4736458p4737720.html
>     To start a new topic under Amber Smalltalk, email [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737723&i=2>
>     To unsubscribe from Amber Smalltalk, click here.
>     NAML
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> ------------------------------------------------------------------------
> View this message in context: Re: Re: Re: Best practices!
> <http://forum.world.st/Best-practices-tp4736458p4737723.html>
> Sent from the Amber Smalltalk mailing list archive
> <http://forum.world.st/Amber-Smalltalk-f3824463.html> at Nabble.com.
>
> --
> 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/groups/opt_out.

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Re: Best practices!

laci
Haven't found the solution yet.
For now I have configured the bower_components manually.
There must be a solution for that in bower.
I'll check it somewhat later.

----Original Message----
From : [hidden email]
Date : 18/01/2014 15:41
To : [hidden email]
Subject : Re: Re: Re: Best practices!

Could you add a page / section about it somewhere in Amber wiki? With
link to the bower issue if it exists (or if not, create one)?

It happened a few times, it's fine to have it explained in some faq.

Herby

laci wrote:

> Thanks Herby.
> This is where the problem lies.
>
>     ----Original Message----
>      From : [hidden email] </user/SendEmail.jtp?type=node&node=4737723&i=0>
>     Date : 18/01/2014 14:59
>     To : [hidden email] </user/SendEmail.jtp?type=node&node=4737723&i=1>
>     Subject : Re: Re: Best practices!
>
>     Bad luck. I also work on Windows, and everything's fine.
>
>     The only difference which strikes me (as it fails on rename) is that
>     I work on D:, C: is left for SW.
>
>     If that happens to be the case, you should fill an issue to bower
>     (fail unzipping into same drive on Windows). Maybe the issue already
>     is there...
>
>     Herby
>
>     laci wrote:
>
>      > No luck. Running on Windows.
>      > Falls over on bootstrap.
>      >
>      > ----Original Message----
>      > From : [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737712&i=0>
>      > Date : 18/01/2014 13:17
>      > To : [hidden email] </user/SendEmail.jtp?type=node&node=4737712&i=1>
>      > Subject : Re: Best practices!
>      >
>      > Try again.
>      >
>      > People had these EPERM errors, but it always somehow settled.
>      >
>      > (and it's better to install it with --save, to save the dependency)
>      >
>      > laci wrote:
>      >
>      > > Bower fails on installing bootstrap 2.3.2:
>      > >
>      > > C:\Users\Laci>bower install amber
>      > > bower amber#* cached
>      > > git://github.com/amber-small
>     talk/amber.git#0.12.2
>
>      > > bower amber#* validate 0.12.2 against
>      > > git://github.com/amber-smalltalk/amber.git#*
>      > > bower bootstrap#* not-cached
>      > > 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 jquery-tabby#* cached
>      > > git://github.com/alanhogan/Tabby.git#925c5a416a
>      > > bower jquery-tabby#* validate 925c5a416a against
>      > > git://github.com/alanhogan/Tabby.git#*
>      > > 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 codemirror#~3.13.0 cached
>      > > git://github.com/marijnh/CodeMirror.git#3.13.0
>      > > bower codemirror#~3.13.0 validate 3.13.0 against
>      > > git://github.com/marij
>     nh/CodeMirror.git#~3.13.0
>
>      > > bower jquery#~1.8.3 cached
>      > > git://github.com/components/jquery.git#1.8.3
>      > > bower jquery#~1.8.3 validate 1.8.3 against
>      > > git://github.com/components/jquery.git#~1.8.3
>      > > 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 es5-shim#~2.1.0 cached
>      > > git://github.com/kriskowal/es5-shim.git#2.1.0
>      > > bower es5-shim#~2.1.0 validate 2.1.0 against
>      > > git://github.com/kriskowal/es5-shim.git#~2.1.0
>      > > bower bootstrap#* extract bootstrap.zip
>      > > bower bootstrap#* EPERM E
>      > PERM, rename
>      >
>      > >
>      >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
>      >
>      > >
>      > > Stack trace:
>      > > Error: EPERM, rename
>      > >
>      >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb
>
>     0848f2894a69\_wildcard'
>
>      >
>      > >
>      > > Console trace:
>      > > Trace
>      > > at StandardRenderer.error
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
>
>      >
>      > > at Logger.updateNotifier.packageName
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
>      >
>      > > at Logger.EventEmitter.emit (events.js:95:17)
>      > > at Logger.emit
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
>
>      >
>      > > at
>      > >
>      >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
>
>      >
>      > > at _rejected
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
>
>      >
>      > > at
>      > >
>      >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:
>
>      >
>      > 30
>      >
>      > > at Promise.when
>      > >
>      > (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modul
>     es\q\q.js:1079:31)
>
>      >
>      > > at Promise.promise.promiseDispatch
>      > >
>      >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
>
>      >
>      > > at
>      > >
>      >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44
>
>      >
>      > >
>      > > System info:
>      > > Bower version: 1.2.8
>      > > Node version: 0.10.24
>      > > OS: Windows_NT 6.0.6002 ia32
>      > >
>      > > The only way I could resolve that setting up amber from ZIP and
>      > fetching
>      > > each dependencies one by one.
>      > > Would be great if bower could install amber.
>      > >
>      > >
>      > >
>      > > --
>      > > View this message in context:
>      > http://forum.world.st/Best-practices-tp4736458p4737693.html
>      > > Sent from the Amber Smalltalk mailing list archive at Nabble.com.
>      > >
>      > --
>      > 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]
>
>      > </user/SendEmail.jtp?type=node&node=4737695&i=0>.
>      > For more options, visit https://groups.google.com/groups/opt_out.
>      >
>      >
>      >
>     ------------------------------------------------------------------------
>
>      > If you reply to this email, your message will be added to the
>      > discussion below:
>      > http://forum.world.st/Best-practices-tp4736458p4737695.html
>      > To start a new topic under Amber Smalltalk, email [hidden email]
>      > </user/SendEmail.jtp?type=node&node=4737712&i=2>
>      > To unsubscribe from Amber Smalltalk, click here.
>      > NAML
>      >
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>>
>
>      >
>      >
>      >
>      >
>      > ----------------
>     --------------------------------------------------------
>
>      > View this message in context: Re: Re: Best practices!
>      > <http://forum.world.st/Best-practices-tp4736458p4737712.html>
>      > Sent from the Amber Smalltalk mailing list archive
>      > <http://forum.world.st/Amber-Smalltalk-f3824463.html> at Nabble.com.
>      >
>      > --
>      > 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]
>     </user/SendEmail.jtp?type=node&node=4737720&i=0>.
>      > For more options, visit https://groups.google.com/groups/opt_out.
>     --
>     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]
>     </user/SendEmail.jtp?type=node&node=4737720&i=1>.
>     For more options, visit https://groups.google.com/groups/opt_out.
>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://forum.world.st/Best-practices-tp4736458p4737720.html
>     To start a new topic under Amber Smalltalk, email [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737723&i=2>
>     To unsubscribe from Amber Smalltalk, click here.
>     NAML
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> ------------------------------------------------------------------------
> View this message in context: Re: Re: Re: Best practices!
> <http://forum.world.st/Best-practices-tp4736458p4737723.html>
> Sent from the Amber Smalltalk mailing list archive
> <http://forum.world.st/Amber-Smalltalk-f3824463.html> at Nabble.com.
>
> --
> 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/groups/opt_out.
--
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/groups/opt_out.



If you reply to this email, your message will be added to the discussion below:
http://forum.world.st/Best-practices-tp4736458p4737733.html
To start a new topic under Amber Smalltalk, email [hidden email]
To unsubscribe from Amber Smalltalk, click here.
NAML


Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Re: Best practices!

Herby Vojčík
It's a bug, of course; which should be reported. You won't find a solution.

laci wrote:

> Haven't found the solution yet.
> For now I have configured the bower_components manually.
> There must be a solution for that in bower.
> I'll check it somewhat later.
>
> ----Original Message----
>
>     From : [hidden email] </user/SendEmail.jtp?type=node&node=4737748&i=0>
>     Date : 18/01/2014 15:41
>     To : [hidden email] </user/SendEmail.jtp?type=node&node=4737748&i=1>
>     Subject : Re: Re: Re: Best practices!
>
>     Could you add a page / section about it somewhere in Amber wiki? With
>     link to the bower issue if it exists (or if not, create one)?
>
>     It happened a few times, it's fine to have it explained in some faq.
>
>     Herby
>
>     laci wrote:
>
>     > Thanks Herby.
>     > This is where the problem lies.
>     >
>     > ----Original Message----
>     > From : [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737723&i=0>
>     > Date : 18/01/2014
14:59

>     > To : [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737723&i=1>
>     > Subject : Re: Re: Best practices!
>     >
>     > Bad luck. I also work on Windows, and everything's fine.
>     >
>     > The only difference which strikes me (as it fails on rename) is
>     that
>     > I work on D:, C: is left for SW.
>     >
>     > If that happens to be the case, you should fill an issue to bower
>     > (fail unzipping into same drive on Windows). Maybe the issue
>     already
>     > is there...
>     >
>     > Herby
>     >
>     > laci wrote:
>     >
>     > > No luck. Running on Windows.
>     > > Falls over on bootstrap.
>     > >
>     > > ----Original Message----
>     > > From : [hidden email]
>     > </user/SendEmail.jtp?type=node&node=4737712&i=0>
>     > > Date : 18/01/2014 13:17
>     > > To : [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737712&i=1>
>     > > Subject : Re: Best practices!
>     > >
>     > > Try again.
>     > >
>  
   > > People had these EPERM errors, but it always somehow settled.

>     > >
>     > > (and it's better to install it with --save, to save the
>     dependency)
>     > >
>     > > laci wrote:
>     > >
>     > > > Bower fails on installing bootstrap 2.3.2:
>     > > >
>     > > > C:\Users\Laci>bower install amber
>     > > > bower amber#* cached
>     > > > git://github.com/amber-small
>     > talk/amber.git#0.12.2
>     >
>     > > > bower amber#* validate 0.12.2 against
>     > > > git://github.com/amber-smalltalk/amber.git#*
>     > > > bower bootstrap#* not-cached
>     > > > 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 jquery-tabby#* cached
>     > > > git://github.com/alanhogan/Tabby.git#925c5a416a
>     > > > bower jquery-tabby#* validate
925c5a416a against

>     > > > git://github.com/alanhogan/Tabby.git#*
>     > > > 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 codemirror#~3.13.0 cached
>     > > > git://github.com/marijnh/CodeMirror.git#3.13.0
>     > > > bower codemirror#~3.13.0 validate 3.13.0 against
>     > > > git://github.com/marij
>     > nh/CodeMirror.git#~3.13.0
>     >
>     > > > bower jquery#~1.8.3 cached
>     > > > git://github.com/components/jquery.git#1.8.3
>     > > > bower jquery#~1.8.3 validate 1.8.3 against
>     > > > git://github.com/components/jquery.git#~1.8.3
>     > > > 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 es5-shim#~2.1.0 cached

>     > > > git://github.com/kriskowal/es5-shim.git#2.1.0
>     > > > bower es5-shim#~2.1.0 validate 2.1.0 against
>     > > > git://github.com/kriskowal/es5-shim.git#~2.1.0
>     > > > bower bootstrap#* extract bootstrap.zip
>     > > > bower bootstrap#* EPERM E
>     > > PERM, rename
>     > >
>     > > >
>     > >
>     >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb0848f2894a69\_wildcard'
>
>     >
>     > >
>     > > >
>     > > > Stack trace:
>     > > > Error: EPERM, rename
>     > > >
>     > >
>     >
>     'C:\Users\Laci\AppData\Roaming\bower\cache\packages\44a378c78a1e035a4bcb
>
>     >
>     > 0848f2894a69\_wildcard'
>     >
>     > >
>     > > >
>     > > > Console trace:
>     > > > Trace
>     > > > at StandardRenderer.error
>     > > >
>     > >
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\renderers\StandardRenderer.js:74:17)
>
>     >
>     > >
>     > > > at Logger.up
dateNotifier.packageName

>     > > >
>     > >
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\bin\bower:109:18)
>
>     > >
>     > > > at Logger.EventEmitter.emit (events.js:95:17)
>     > > > at Logger.emit
>     > > >
>     > >
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\bower-logger\lib\Logger.js:29:39)
>
>     >
>     > >
>     > > > at
>     > > >
>     > >
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\lib\commands\install.js:27:16
>
>     >
>     > >
>     > > > at _rejected
>     > > >
>     > >
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:808:24)
>
>     >
>     > >
>     > > > at
>     > > >
>     > >
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:834:
>
>     >
>     > >
>     > > 30
>     > >
>     > > > at Promise.when
>     > > >
>     > > (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modul

>     > es\q\q.js:1079:31)
>     >
>     > >
>     > > > at Promise.promise.promiseDispatch
>     > > >
>     > >
>     >
>     (C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:752:41)
>
>     >
>     > >
>     > > > at
>     > > >
>     > >
>     >
>     C:\Users\Laci\AppData\Roaming\npm\node_modules\bower\node_modules\q\q.js:574:44
>
>     >
>     > >
>     > > >
>     > > > System info:
>     > > > Bower version: 1.2.8
>     > > > Node version: 0.10.24
>     > > > OS: Windows_NT 6.0.6002 ia32
>     > > >
>     > > > The only way I could resolve that setting up amber from ZIP and
>     > > fetching
>     > > > each dependencies one by one.
>     > > > Would be great if bower could install amber.
>     > > >
>     > > >
>     > > >
>     > > > --
>     > > > View this message in context:
>     > > http://forum.world.st/Best-practices-tp4736458p4737693.html
>     > > > Sent from the Amber Smalltalk mailing list archive at
>     Nabble.com.
>     > >
>
>     > > --
>     > > 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]
>     >
>     > > </user/SendEmail.jtp?type=node&node=4737695&i=0>.
>     > > For more options, visit https://groups.google.com/groups/opt_out.
>     > >
>     > >
>     > >
>     >
>     ------------------------------------------------------------------------
>
>     >
>     > > If you reply to this email, your message will be added to the
>     > > discussion below:
>     > > http://forum.world.st/Best-practices-tp4736458p4737695.html
>     > > To start a new topic under Amber Smalltalk, email [hidden email]
>     > > </user/SendEmail.jtp?type=node&node=4737712&i=2>
>     > > To unsubscribe from Amber Smalltalk, click here.
>     > > NAML
>     > >
>     >
>     <http://forum.world.st/template/NamlServlet.jtp?macro=ma
cro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>     >
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3A
email.naml-send_instant_email%21nabble%3Aemail.naml

>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>>>
>
>     >
>     > >
>     > >
>     > >
>     > >
>     > > ----------------
>     > --------------------------------------------------------
>     >
>     > > View this message in context: Re: Re: Best practices!
>     > > <http://forum.world.st/Best-practices-tp4736458p4737712.html>
>     > > Sent from the Amber Smalltalk mailing list archive
>     > > <http://forum.world.st/Amber-Smalltalk-f3824463.html> at
>     Nabble.com.
>     > >
>     > > --
>     > > You received this message because you are subscribed to the
>     Google
>     > > Groups "amber-lang" gr
oup.

>     > > To unsubscribe from this group and stop receiving emails from it,
>     > send
>     > > an email to [hidden email]
>     > </user/SendEmail.jtp?type=node&node=4737720&i=0>.
>     > > For more options, visit https://groups.google.com/groups/opt_out.
>     > --
>     > 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]
>     > </user/SendEmail.jtp?type=node&node=4737720&i=1>.
>     > For more options, visit https://groups.google.com/groups/opt_out.
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>
>     > If you reply to this email, your message will be added to the
>     > discussion below:
>     > http://forum.world.st/Best-practices-tp4736458p4737720.html
>     > To start a new topic under Amber Smalltalk, email [hidden email]
>     > </user/S
endEmail.jtp?type=node&node=4737723&i=2> s message in context: Re: Re: Re: Best practices!

>     > <http://forum.world.st/Best-practices-tp4736458p4737723.html>
>     > Sent from the Amber Smalltalk mailing list archive
>     > <http://forum.world.st/Amber-Smalltalk-f3824463.html> at
>     Nabble.com.
>     >
>     > --
>     > 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]
>     </user/SendEmail.jtp?type=node&node=4737733&i=0>.
>     > For more options, visit https://groups.google.com/groups/opt_out.
>     --
>     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]
>     </user/SendEmail.jtp?type=node&node=4737733&i=1>.
>     For more options, visit https://groups.google.com/groups/opt_
out.

>
>
>     ------------------------------------------------------------------------
>     If you reply to this email, your message will be added to the
>     discussion below:
>     http://forum.world.st/Best-practices-tp4736458p4737733.html
>     To start a new topic under Amber Smalltalk, email [hidden email]
>     </user/SendEmail.jtp?type=node&node=4737748&i=2>
>     To unsubscribe from Amber Smalltalk, click here.
>     NAML
>     <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
>
>
> ------------------------------------------------------------------------
> View this message in context: Re: Re: Re: Re: Best practices!
> <http://forum.world.st/Best-practice
s-tp4736458p4737748.html>
> Sent from the Amber Smalltalk mailing list archive
> <http://forum.world.st/Amber-Smalltalk-f3824463.html> at Nabble.com.
>
> --
> 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/groups/opt_out.

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Re: Best practices!

laci
The problem is related to anti-virus software.
See issues:
Fix EPERM error on Windows with A/V software: https://github.com/Obvious/phantomjs/pull/28
Error thrown at bower install: https://github.com/bower/bower/issues/798
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

NorbertHartl
In reply to this post by Nicolas Petton
thanks Nico, I have my first project setup. Still a few things unclear. Comments inline!


Am 14.01.2014 um 11:35 schrieb Nicolas Petton <[hidden email]>:

> Hi Norbert!
>
> Norbert Hartl writes:
>
>> Hi guys,
>>
>> didn’t have time to do amber stuff the last couple of months. Now I’m trying getting up to speed with a new project. But I struggle to find the right information how to do things. Most stuff I find is still for 0.10 or 0.12 and the world didn’t stop turning. I know most of the topics come up every now and then so excuse my lazy inquiry.
>>
>> I want to know what you would consider current best practices when starting an amber project:
>>
>> - Is there an up-to-date skeleton to use? Are there any hints about
>> directory setup that works for any of you?
>
> The best way to go is using amber as a bower library. You can do as
> explained on the readme:
>
> # Install the CLI tool `amber`
> npm install -g amber
>
> # Load amber via bower in your project
> bower init
> bower install amber --save
>
> The first line will install the CLI tools, and the second will install
> amber in the bower_components/ directory of your project.
>
> You first need to install npm and bower.
>
> Then to structure your project, I would suggest to take a look at
> https://github.com/amber-smalltalk/amber/wiki/Writing-my-first-app, it
> should help.
>
This is irritating because bower installs everything in bower_components and the tutorial advizes to clone git in a custom directory. I did the latter and I’m very happy with it. To be honest I quite don’t understand what bower is useful for. Ok, it’s a package manager which seems that there is a repository of packages somewhere on the net including dependencies. But where to go after you have a directory bower_components that you surely do not want to have when you layout your directory structure for your web project.
I’m asking myself if bower is useful to manage my own project. If it insists to have everything in bower_components the answer is easy.

Another question that is related to this is the deployment scenario. Let’s assume we have the directory structure from the „writing my first app“ tutorial

vendor/amber/
js/
st/

and of course another 100 directories/files because this is a web app, right? How do you arrange something that you deploy online? Using grunt to copy everything into its place or is there something more intelligent I can do?

thanks,

Norbert

>> - What is the status about require and shims. Last time I had problems
>> to get jquery, google maps and modules for them integrated in the
>> require process. Any examples out there? Is it now possible to use
>> r.js or similar to produce a compact version for deployment?
>
> That's 2 questions :)
>
> - You can load our libraries with require without any trouble, and if
> you do have troubles, please tell us! I'm writing a documentation for
> Amber, and if anything isn't obvious, I want to write it there :)
>
> - Yes, it is possible to use r.js (there was a thread about that on
> here, I'll try to find it)
>
>> - What are you using for backend communication? Plain requests,
>> backbone.js, knockout.js, ….?
>
> I'm using a custom-made amber lib (that I plan to share in the future)
> to communicate with a Zinc server. But that's just me. Anything will do ;)
>
>> - Any advize what to use for widgets and UI components. Last time I
>> was pretty satisfied with plain smalltalk for UI components.
>
> I really like bootstrap as the backbone of my css. For the widget logic,
> I usually stick with Amber widgets/components. But you could use
> jQueryUI, etc. if you like that.
>
> Hope this helps!
> Nico
>
> --
> 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/groups/opt_out.

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

Nicolas Petton

Norbert Hartl writes:

> This is irritating because bower installs everything in
> bower_components and the tutorial advizes to clone git in a custom
> directory. I did the latter and I’m very happy with it. To be honest I
> quite don’t understand what bower is useful for. Ok, it’s a package
> manager which seems that there is a repository of packages somewhere
> on the net including dependencies. But where to go after you have a
> directory bower_components that you surely do not want to have when
> you layout your directory structure for your web project.  I’m asking
> myself if bower is useful to manage my own project. If it insists to
> have everything in bower_components the answer is easy.
>

Yes, it will insist having a flat directory for all components. Now we
use bower internally for Amber, and you can very well do `bower install`
from the Amber directory, and not care about bower for your project itself.

> Another question that is related to this is the deployment
> scenario. Let’s assume we have the directory structure from the
> „writing my first app“ tutorial
>
> vendor/amber/
> js/
> st/
>
> and of course another 100 directories/files because this is a web app,
> right? How do you arrange something that you deploy online? Using
> grunt to copy everything into its place or is there something more
> intelligent I can do?

What do you mean? You want to deploy files by copying them to the
deployment server automatically? I usually use git for that, and push to
a 'deploy' branch. Does it answer your question?

Cheers,
Nico

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

Herby Vojčík
In reply to this post by NorbertHartl


Norbert Hartl wrote:

> thanks Nico, I have my first project setup. Still a few things unclear. Comments inline!
>
>
> Am 14.01.2014 um 11:35 schrieb Nicolas Petton<[hidden email]>:
>
>> Hi Norbert!
>>
>> Norbert Hartl writes:
>>
>>> Hi guys,
>>>
>>> didn’t have time to do amber stuff the last couple of months. Now I’m trying getting up to speed with a new project. But I struggle to find the right information how to do things. Most stuff I find is still for 0.10 or 0.12 and the world didn’t stop turning. I know most of the topics come up every now and then so excuse my lazy inquiry.
>>>
>>> I want to know what you would consider current best practices when starting an amber project:
>>>
>>> - Is there an up-to-date skeleton to use? Are there any hints about
>>> directory setup that works for any of you?
>> The best way to go is using amber as a bower library. You can do as
>> explained on the readme:
>>
>> # Install the CLI tool `amber`
>> npm install -g amber
>>
>> # Load amber via bower in your project
>> bower init
>> bower install amber --save
>>
>> The first line will install the CLI tools, and the second will install
>> amber in the bower_components/ directory of your project.
>>
>> You first need to install npm and bower.
>>
>> Then to structure your project, I would suggest to take a look at
>> https://github.com/amber-smalltalk/amber/wiki/Writing-my-first-app, it
>> should help.
>>
> This is irritating because bower installs everything in bower_components and the tutorial advizes to clone git in a custom directory. I did the latter and I’m very happy with it. To be honest I quite don’t understand what bower is useful for. Ok, it’s a package manager which seems that there is a repository of packages somewhere on the net including dependencies. But where to go after you have a directory bower_components that you surely do not want to have when you layout your directory structure for your web project.
> I’m asking myself if bower is useful to manage my own project. If it insists to have everything in bower_components the answer is easy.
>
> Another question that is related to this is the deployment scenario. Let’s assume we have the directory structure from the „writing my first app“ tutorial
>
> vendor/amber/
> js/
> st/
>
> and of course another 100 directories/files because this is a web
> app, right? How do you arrange something that you deploy online?
> Using grunt to copy everything into its place or is there something
> more  intelligent I can do?

This is what bower is good for. Set up your project with bower, add
amber as dependency and all other libs as dependency as well. Then just
deploy your skeleton from git or .zip or however and run bower install.

You are not restricted to use only libs that bower has in its repository
- you can manage your own modules as dependencies as well, just use
bower install with your own component name and specify git path to it or
url to tarball. It is saved in bower.json and during deploy, lone 'bower
install' loads bower-repo libraries as well as your own modules with all
their dependencies.

Of course, you run into trouble when there is a version clash, but that
comes with the flat hierarchy.

Herby

> thanks,
>
> Norbert
>
>>> - What is the status about require and shims. Last time I had problems
>>> to get jquery, google maps and modules for them integrated in the
>>> require process. Any examples out there? Is it now possible to use
>>> r.js or similar to produce a compact version for deployment?
>> That's 2 questions :)
>>
>> - You can load our libraries with require without any trouble, and if
>> you do have troubles, please tell us! I'm writing a documentation for
>> Amber, and if anything isn't obvious, I want to write it there :)
>>
>> - Yes, it is possible to use r.js (there was a thread about that on
>> here, I'll try to find it)
>>
>>> - What are you using for backend communication? Plain requests,
>>> backbone.js, knockout.js, ….?
>> I'm using a custom-made amber lib (that I plan to share in the future)
>> to communicate with a Zinc server. But that's just me. Anything will do ;)
>>
>>> - Any advize what to use for widgets and UI components. Last time I
>>> was pretty satisfied with plain smalltalk for UI components.
>> I really like bootstrap as the backbone of my css. For the widget logic,
>> I usually stick with Amber widgets/components. But you could use
>> jQueryUI, etc. if you like that.
>>
>> Hope this helps!
>> Nico
>>
>> --
>> 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/groups/opt_out.
>

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

NorbertHartl
In reply to this post by Nicolas Petton

Am 30.01.2014 um 11:07 schrieb Nicolas Petton <[hidden email]>:

>
> Norbert Hartl writes:
>
>> This is irritating because bower installs everything in
>> bower_components and the tutorial advizes to clone git in a custom
>> directory. I did the latter and I'm very happy with it. To be honest I
>> quite don't understand what bower is useful for. Ok, it's a package
>> manager which seems that there is a repository of packages somewhere
>> on the net including dependencies. But where to go after you have a
>> directory bower_components that you surely do not want to have when
>> you layout your directory structure for your web project.  I'm asking
>> myself if bower is useful to manage my own project. If it insists to
>> have everything in bower_components the answer is easy.
>>
>
> Yes, it will insist having a flat directory for all components. Now we
> use bower internally for Amber, and you can very well do `bower install`
> from the Amber directory, and not care about bower for your project itself.
>
>> Another question that is related to this is the deployment
>> scenario. Let's assume we have the directory structure from the
>> "writing my first app" tutorial
>>
>> vendor/amber/
>> js/
>> st/
>>
>> and of course another 100 directories/files because this is a web app,
>> right? How do you arrange something that you deploy online? Using
>> grunt to copy everything into its place or is there something more
>> intelligent I can do?
>
> What do you mean? You want to deploy files by copying them to the
> deployment server automatically? I usually use git for that, and push to
> a 'deploy' branch. Does it answer your question?

I mean first you set up everything for development. It is having all .js and .st files laying around. Then you have maybe that bower_components directory there. Do you have the same directory layout with all the files on the web server when the application gets deployed. Or do you rearrange directories and stuff to have something "more clean" ?

Norbert

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

Nicolas Petton

Norbert Hartl writes:

> I mean first you set up everything for development. It is having all
> .js and .st files laying around. Then you have maybe that
> bower_components directory there. Do you have the same directory
> layout with all the files on the web server when the application gets
> deployed. Or do you rearrange directories and stuff to have something
> "more clean" ?

Since Amber packages are AMD modules, I'd use r.js[1] for deployment. It
combines all files together, which is better for deployment and will
also uglify them.

Note though that as of today, there's no convenient way to remove the
source from the JS files. That's on the todo list though :)

[1] http://requirejs.org/docs/optimization.html

Cheers,
Nico


>
> Norbert


--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

Herby Vojčík
Nicolas Petton wrote:

> Norbert Hartl writes:
>
>> I mean first you set up everything for development. It is having all
>> .js and .st files laying around. Then you have maybe that
>> bower_components directory there. Do you have the same directory
>> layout with all the files on the web server when the application gets
>> deployed. Or do you rearrange directories and stuff to have something
>> "more clean" ?
>
> Since Amber packages are AMD modules, I'd use r.js[1] for deployment. It
> combines all files together, which is better for deployment and will
> also uglify them.
>
> Note though that as of today, there's no convenient way to remove the
> source from the JS files. That's on the todo list though :)

Srikumar used grep for this successfully, didn't it?

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

Nicolas Petton

Herby Vojčík writes:

>> Note though that as of today, there's no convenient way to remove the
>> source from the JS files. That's on the todo list though :)
>
> Srikumar used grep for this successfully, didn't it?

Yes, but I'd like to provide an option in the exporter to export without
the source. Then a bit of r.js and deployment becomes a breeze :)

Nico

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

NorbertHartl
In reply to this post by Nicolas Petton

Am 30.01.2014 um 21:09 schrieb Nicolas Petton <[hidden email]>:

>
> Norbert Hartl writes:
>
>> I mean first you set up everything for development. It is having all
>> .js and .st files laying around. Then you have maybe that
>> bower_components directory there. Do you have the same directory
>> layout with all the files on the web server when the application gets
>> deployed. Or do you rearrange directories and stuff to have something
>> "more clean" ?
>
> Since Amber packages are AMD modules, I'd use r.js[1] for deployment. It
> combines all files together, which is better for deployment and will
> also uglify them.
>
> Note though that as of today, there's no convenient way to remove the
> source from the JS files. That's on the todo list though :)
>
Agreed. I think this is the most viable option. And how do you go from development to deployment? In development you have css, images and stuff laying around plus the bower_components and whatever resources. So I think the only option is to copy the resources (css, images,...) and a combined (r.js) source file into a similar structure for deployment. Maybe I missing an important piece so I don't get the obvious :)

Norbert

> [1] http://requirejs.org/docs/optimization.html
>
> Cheers,
> Nico
>
>
>>
>> Norbert
>
>
> --
> 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/groups/opt_out.

--
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/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Best practices!

Nicolas Petton
For deployment I usually have a 'deployment' branch. When I push to it, there are wither post-commit hooks that perform extra actions. The deployment branch would then have static files + the combined js file.

Another way is to have a CI job that runs deployment scripts each time you push to 'deployment'.

Does it help? I have the feeling that I'm missing your point :/

Nico

--
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/groups/opt_out.
12