Helios moving and a few more changes
Locked
Helios moving and a few more changes
 
|
Hello!
This is mail for those who contribute to amber and thus use the git version from master. tl;dr: Helios will be reorganized. Hold your coding until its done or commit/push/PR your contributions now. I had a talk with Nico, after which I started to integrate changes leading to release 0.13.0. First of these changes is removal of amber.js, introduction of `amber config` mapping builder tool (which builds mapping into config.js file and that file is to be loaded instead of amber.js). `amber config` is already present is cli, and amber repo master is already moved to used config.js built by `amber config`, as you can see in internal/index.html. MORE IMPORTANTLY, second change. With `amber config` configuration builder, it is now easy to decouple Helios into its own repo. It is planned to be done in these days, as soon as it is viable. Those of you who contribute to Helios, either wait for a while until you do changes to the code, or commit, push and PR them now, or find a way how to port them (using patch format, for example). After the move, the helios code will be the same, the namespace will be the same, just files will be part of different repo with independent lifecycle. Extracted Helios, being repo of its own, will be devDependency of amber projects. For development of amber, the plan is to include it as a submodule in external/helios directory (I know submodules are hard to use, there is an alternative of putting another directory, ie my, in .gitignore and letting the developer clone/push any version of Helios he/she currently works on into my/helios, but this needs hand-cloning so it does not work out of the box, submodules OTOH make it hard to use your own fork of Helios; what would you prefer?). 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. |
Re: Helios moving and a few more changes
|
thanks for the info
It sounds like Helios is maturing which is great. So it makes sense if its code starts to feel like an app on top of the core. Said that, I’d prefer to keep things simple with git and clone manually Helios where needed, or any other “module” that might extend core Amber’s powers That would make people feel that Amber is friendly (less hostile) to customize if they want to my 2 cents On Jul 7, 2014, at 7:28 PM, Herby Vojčík <[hidden email]> wrote: > Hello! > > This is mail for those who contribute to amber and thus use the git version from master. > > tl;dr: Helios will be reorganized. Hold your coding until its done or commit/push/PR your contributions now. > > I had a talk with Nico, after which I started to integrate changes leading to release 0.13.0. First of these changes is removal of amber.js, introduction of `amber config` mapping builder tool (which builds mapping into config.js file and that file is to be loaded instead of amber.js). `amber config` is already present is cli, and amber repo master is already moved to used config.js built by `amber config`, as you can see in internal/index.html. > > MORE IMPORTANTLY, second change. With `amber config` configuration builder, it is now easy to decouple Helios into its own repo. It is planned to be done in these days, as soon as it is viable. Those of you who contribute to Helios, either wait for a while until you do changes to the code, or commit, push and PR them now, or find a way how to port them (using patch format, for example). After the move, the helios code will be the same, the namespace will be the same, just files will be part of different repo with independent lifecycle. > > Extracted Helios, being repo of its own, will be devDependency of amber projects. For development of amber, the plan is to include it as a submodule in external/helios directory (I know submodules are hard to use, there is an alternative of putting another directory, ie my, in .gitignore and letting the developer clone/push any version of Helios he/she currently works on into my/helios, but this needs hand-cloning so it does not work out of the box, submodules OTOH make it hard to use your own fork of Helios; what would you prefer?). > > 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. -- 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. |
Re: Helios moving and a few more changes
|
|
I would expect the majority of users not to contribute to Amber itself but rather build apps with it. Maybe I am wrong. Having to clone with a few more flags is not too bad in that case, IMHO. You can detail the necessary steps to contribute in README.md. Jeremy On Jul 7, 2014 7:33 PM, "sebastian" <[hidden email]> wrote:
-- thanks for the info 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. |
Re: Helios moving and a few more changes
|
|
I would not mind hand cloning thus allowing me to have an easier way
of handling a fork of Helios. On 7/7/14, Jeremy Shute <[hidden email]> wrote: > I would expect the majority of users not to contribute to Amber itself but > rather build apps with it. Maybe I am wrong. > > Having to clone with a few more flags is not too bad in that case, IMHO. > > You can detail the necessary steps to contribute in README.md. > > Jeremy > On Jul 7, 2014 7:33 PM, "sebastian" <[hidden email]> wrote: > >> thanks for the info >> >> It sounds like Helios is maturing which is great. >> >> So it makes sense if its code starts to feel like an app on top of the >> core. >> >> Said that, I’d prefer to keep things simple with git and clone manually >> Helios where needed, or any other “module” that might extend core Amber’s >> powers >> >> That would make people feel that Amber is friendly (less hostile) to >> customize if they want to >> >> my 2 cents >> >> >> >> >> On Jul 7, 2014, at 7:28 PM, Herby Vojčík <[hidden email]> wrote: >> >> > Hello! >> > >> > This is mail for those who contribute to amber and thus use the git >> version from master. >> > >> > tl;dr: Helios will be reorganized. Hold your coding until its done or >> commit/push/PR your contributions now. >> > >> > I had a talk with Nico, after which I started to integrate changes >> leading to release 0.13.0. First of these changes is removal of amber.js, >> introduction of `amber config` mapping builder tool (which builds mapping >> into config.js file and that file is to be loaded instead of amber.js). >> `amber config` is already present is cli, and amber repo master is >> already >> moved to used config.js built by `amber config`, as you can see in >> internal/index.html. >> > >> > MORE IMPORTANTLY, second change. With `amber config` configuration >> builder, it is now easy to decouple Helios into its own repo. It is >> planned >> to be done in these days, as soon as it is viable. Those of you who >> contribute to Helios, either wait for a while until you do changes to the >> code, or commit, push and PR them now, or find a way how to port them >> (using patch format, for example). After the move, the helios code will >> be >> the same, the namespace will be the same, just files will be part of >> different repo with independent lifecycle. >> > >> > Extracted Helios, being repo of its own, will be devDependency of amber >> projects. For development of amber, the plan is to include it as a >> submodule in external/helios directory (I know submodules are hard to >> use, >> there is an alternative of putting another directory, ie my, in >> .gitignore >> and letting the developer clone/push any version of Helios he/she >> currently >> works on into my/helios, but this needs hand-cloning so it does not work >> out of the box, submodules OTOH make it hard to use your own fork of >> Helios; what would you prefer?). >> > >> > 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. >> >> -- >> 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. > -- 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. |
Re: Helios moving and a few more changes
|
I love modular code, keep up the great work :) On Tue, Jul 8, 2014 at 10:12 AM, H. Hirzel <[hidden email]> wrote: I would not mind hand cloning thus allowing me to have an easier way 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. |
Re: Helios moving and a few more changes
|
|
In reply to this post by Herby Vojčík
To you who contribute to Amber and Helios:
Helios is now moved to its own repo. Update your amber clone and read CONTRIBUTING.md on how to bring in Helios (your fork if you change Helios or stock one if you just play with Amber). 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. |
Re: Helios moving and a few more changes
|
|
After reading https://github.com/amber-smalltalk/amber/blob/master/CONTRIBUTING.md
I have the question: 'To which directory do I need to copy Helios?' - amber - external - internal - src - support ? On 7/9/14, Herby Vojčík <[hidden email]> wrote: > To you who contribute to Amber and Helios: > > Helios is now moved to its own repo. Update your amber clone and read > CONTRIBUTING.md on how to bring in Helios (your fork if you change > Helios or stock one if you just play with Amber). > > 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. > -- 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. |
Re: Helios moving and a few more changes
|
|
CONTRIBUTING.md directly lists the directory into which to clone, in the clone command itself, in the "obtain your copy of the Helios IDE" step. If it's not understandable, it would be fine if you could propose different wording.
H. Hirzel wrote: > After reading https://github.com/amber-smalltalk/amber/blob/master/CONTRIBUTING.md > > I have the question: > > 'To which directory do I need to copy Helios?' > > - amber > - external > - internal > - src > - support > > ? > > > > > On 7/9/14, Herby Vojčík<[hidden email]> wrote: >> To you who contribute to Amber and Helios: >> >> Helios is now moved to its own repo. Update your amber clone and read >> CONTRIBUTING.md on how to bring in Helios (your fork if you change >> Helios or stock one if you just play with Amber). >> >> 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 >> 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. |
Re: Helios moving and a few more changes
|
|
Herby Vojčík wrote: > CONTRIBUTING.md directly lists the directory into which to clone, in the > clone command itself, in the "obtain your copy of the Helios IDE" step. > If it's not understandable, it would be fine if you could propose > different wording. I changed the wording by including explicit "into my/helios". Hopefully now it is better. > H. Hirzel wrote: >> After reading >> https://github.com/amber-smalltalk/amber/blob/master/CONTRIBUTING.md >> >> I have the question: >> >> 'To which directory do I need to copy Helios?' >> >> - amber >> - external >> - internal >> - src >> - support >> >> ? >> >> >> >> >> On 7/9/14, Herby Vojčík<[hidden email]> wrote: >>> To you who contribute to Amber and Helios: >>> >>> Helios is now moved to its own repo. Update your amber clone and read >>> CONTRIBUTING.md on how to bring in Helios (your fork if you change >>> Helios or stock one if you just play with Amber). >>> >>> 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. >>> >> > -- 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. |
Re: Helios moving and a few more changes
|
|
In reply to this post by Herby Vojčík
Cool, thanks for the heads up.
-- Suggestion for the team, I'd very much like to see progress about deploying a project in the roadmap for 0.13: https://github.com/amber-smalltalk/amber/wiki/Roadmap I'm sending a PR now with a bugfix to cheer you up https://github.com/amber-smalltalk/amber/pull/1046 keep the good work On Monday, July 7, 2014 7:28:41 PM UTC-3, Herby wrote: Hello! 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. |
Re: deployment in 0.13 (was: Helios moving and a few more changes)
|
|
Sebastian Sastre wrote: > Cool, thanks for the heads up. > > Suggestion for the team, I'd /very/ much like to see progress about > deploying a project in the roadmap for 0.13: > https://github.com/amber-smalltalk/amber/wiki/Roadmap Well, I use this, as I think it's, naturally, more up to date: https://github.com/amber-smalltalk/amber/issues?milestone=7&state=open If we're at deploying, config.js produced for any project by `amber config` in 0.13, id directly usable as mainConfigFile field for r.js optimizer. Tried on Amber only (2MB full, 700KB deploy only), but you can use same technique with the right app.build.js file to pack any project that uses amber. > > I'm sending a PR now with a bugfix to cheer you up > https://github.com/amber-smalltalk/amber/pull/1046 > > keep the good work > > > > On Monday, July 7, 2014 7:28:41 PM UTC-3, Herby wrote: > > Hello! > > This is mail for those who contribute to amber and thus use the git > version from master. > > tl;dr: Helios will be reorganized. Hold your coding until its done or > commit/push/PR your contributions now. > > I had a talk with Nico, after which I started to integrate changes > leading to release 0.13.0. First of these changes is removal of > amber.js, introduction of `amber config` mapping builder tool (which > builds mapping into config.js file and that file is to be loaded > instead > of amber.js). `amber config` is already present is cli, and amber repo > master is already moved to used config.js built by `amber config`, as > you can see in internal/index.html. > > MORE IMPORTANTLY, second change. With `amber config` configuration > builder, it is now easy to decouple Helios into its own repo. It is > planned to be done in these days, as soon as it is viable. Those of you > who contribute to Helios, either wait for a while until you do changes > to the code, or commit, push and PR them now, or find a way how to port > them (using patch format, for example). After the move, the helios code > will be the same, the namespace will be the same, just files will be > part of different repo with independent lifecycle. > > Extracted Helios, being repo of its own, will be devDependency of amber > projects. For development of amber, the plan is to include it as a > submodule in external/helios directory (I know submodules are hard to > use, there is an alternative of putting another directory, ie my, in > .gitignore and letting the developer clone/push any version of Helios > he/she currently works on into my/helios, but this needs > hand-cloning so > it does not work out of the box, submodules OTOH make it hard to use > your own fork of Helios; what would you prefer?). > > 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] > <mailto:[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. |
«
Return to Amber Smalltalk
|
1 view|%1 views
| Free forum by Nabble | Edit this page |