Re: [Developers] Boards Maqnager - external sources

[Mikal Hart]

W

-------- Original message --------

From: Todd Treece <to...@uniontownlabs.org>

Date:04/03/2015 8:07 PM (GMT-06:00)

To: devel...@arduino.cc

Cc:

Subject: Re: [Developers] Boards Manager - external sources

Roger,

Thanks for the tip. I'll have to see if OS X stores that file somewhere else. I wrote that simple proxy server because I couldn't find any mention of that with the OS X install when searching with ack. This returns no results in 1.6.3:

todd:And q11rduino.app todd$ ack PACKAGE_INDEX_URL

On Friday, April 3, 2015 at 5:54:35 PM UTC-4, Roger Clark wrote:

If you are on windows, you can simply add a line to the arduino.l4j.ini file in the install root

-DPACKAGE_INDEX_URL=http://www.yoururl.com/package_index.json

Of course this could be done with a simple local web server rather than a real server out on the web.

Then it will load a file of your choice

(PS. There is probably an equivalent on Linux and OSX)

On Fri, Apr 3, 2015 at 10:04 AM, Todd Treece <to...@uniontownlabs.org> wrote:

I was looking for a way to test out board packages, and wrote a simple proxy server yesterday to add custom packages to the Board Manager. Not sure if this is a worthwhile stop gap until custom boards can be added through official methods, but I thought I'd post it helre in case it could help: https://github.com/adafruit/adafruit-arduino-proxy

It hasn't been tested heavily, but it seems to work ok.

On Thursday, April 2, 2015 at 3:04:54 PM UTC-4, Brian Cook wrote:

Federico,

Thank you for the feedback.

Do not make it a bounty on my behalf.  I can be patient and I do not
have to means to do it myself.

Thanks,
Brian

> Brian, I really like it! Easy and low risk!
>
> I'll put it in the todo list. I'm not sure how fast I'll be at coding
> it (list is already pretty full) but even if I come
> up too late with an implementation, it will be done this way
>
> Could this be a good candidate for a bounty on bountysource?
>
> Anyway, thank you!
>
> Federico
>
>
>
> Brian Cook ha scrito il 01/04/2015 alle 22:27:
>> Hi Federico,
>>
>>> We would also like to include additional contributed cores to the
>>> list. This is both a strategic move and a support issue (will people
>>> mail us for support on core XYZ?)
>>> So, we would love to populate that list but we still have to make up
>>> our minds about how to properly do that.
>>> For now, your users will have to install the SAM core from the boards
>>> manager
>>
>> In the short term I suggest one change.  The package list is in a file
>> named package_index.json.  I suggest loading / merging all files named
>> package*.json from the directory containing package_index.json.
>>
>> This provides a method for adding cores that is about the same effort as
>> exists now.  Currently, adding a core means: closing the IDE,
>> downloading an archive (e.g. 7-Zip file), expanding the archive to the
>> correct location, starting the IDE.  The new steps would roughly be:
>> close the IDE, download a json file to the correct location, start the
>> IDE, use the Board Manager to install the new core.
>>
>> The change allows all affected parties to start testing the new Board
>> Manager without having to wait for a more complete solution.
>>
>> The change is low risk.  Instead of loading a single file the code would
>> load an arbitrary set of files then merge.  If something goes terribly
>> wrong, the code can easily be reverted to what it is now.
>>
>> I also suggest publishing a simple guideline for naming the package
>> file: package_OrganizationOrDeveloperName_PackageName.json seems like a
>> good pattern.
>>
>> - Brian
>>
>>
>

--
You received this message because you are subscribed to the Google Groups "Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@arduino.cc.

--
You received this message because you are subscribed to the Google Groups "Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@arduino.cc.