Code organization

> François Stephany wrote:
>> Hi,
> Hi,
>
>> It's probably a stupid question but how do you guys organize your code
>> in Amber?
>>
>> I've started the ./bin/server and created a package with a bunch of
>> classes. My code is saved but is in the middle of all the existing
>> classes. Is there a way to separate my code from the core classes ? If
>> not, how do you upgrade amber ?
>
> The loader now allows to load packages (and save them, partially) to
> different place then is the amber itself.
>
> Portion of the page I am working on:
>
> <script src="//assets.foo.biz/amber/js/amber.js"></script>
> <script>
> // ...
> loadAmber({
> // ...
> packages: [
> "//assets.foo.biz/trapped/Trapped-Backend",
> "//assets.foo.biz/trapped/Trapped-Frontend",
> "//assets.foo.biz/foo/foo-Lib",
> "Foo-Model",
> "Foo-Client"
> ],
> packageHome: "code/",
> // ...
> });
>
> Here, I have some dependencies in assets.foo.biz (amber, trapped and foo
> folders), first two included simply as git submodules.

>
>
> Herby Vojčík wrote:
>>
>> François Stephany wrote:
>>>
>>> Hi,
>>
>> Hi,
>>
>>> It's probably a stupid question but how do you guys organize your code
>>> in Amber?
>>>
>>> I've started the ./bin/server and created a package with a bunch of
>>> classes. My code is saved but is in the middle of all the existing
>>> classes. Is there a way to separate my code from the core classes ? If
>>> not, how do you upgrade amber ?
>>
>>
>> The loader now allows to load packages (and save them, partially) to
>> different place then is the amber itself.
>>
>> Portion of the page I am working on:
>>
>> <script src="//assets.foo.biz/amber/js/amber.js"></script>
>> <script>
>> // ...
>> loadAmber({
>> // ...
>> packages: [
>> "//assets.foo.biz/trapped/Trapped-Backend",
>> "//assets.foo.biz/trapped/Trapped-Frontend",
>> "//assets.foo.biz/foo/foo-Lib",
>> "Foo-Model",
>> "Foo-Client"
>> ],
>> packageHome: "code/",
>> // ...
>> });
>>
>> Here, I have some dependencies in assets.foo.biz (amber, trapped and foo
>> folders), first two included simply as git submodules.
>
> Not true here, I select only some subfolders, during jenkins deploy job.
> Sorry for misinformation.
>
>>
>> The packages I work on are Foo-Model and Foo-Client. They are loaded
>> (and saved) into folder code (relative to the starting folder of server).
>>
>> Bottom line is, use packageHome to say where to load packages without
>> path (the ones you work on), and load anything other with including path
>> (either local absolute or relative (to packageHome), or in the form of
>> URL as shown above (//machine/path is also url, just reusing protocol so
>> is is always http or https the same as the main page is)).
>
> Do not include 'js' in paths, it is included automatically as last part of
> path.
>
>
>> Packages that you <del>save</del>commit go always to packageHome.
>>
>>> Cheers,
>>> Francois
>>
>>
>> Hope this helped,
>> 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/groups/opt_out.
>
>

> Hi,
>
> It's probably a stupid question but how do you guys organize your code in Amber?
>
> I've started the ./bin/server and created a package with a bunch of
> classes. My code is saved but is in the middle of all the existing
> classes. Is there a way to separate my code from the core classes ? If
> not, how do you upgrade amber ?
>
> Cheers,
> Francois
>
> --
> 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.
>
>