Bluetooth connector?
A request was made for a Bluetooth connector - EDGENT-71 [1] I updated the jira with the results of an initial brief investigation I made into the topic. Does anyone in the community have insights to offer? [1] https://issues.apache.org/jira/browse/EDGENT-71 — Dale
[jira] [Created] (EDGENT-364) Update instructions on how to use the binary/source release bundles
Queenie Ma created EDGENT-364: - Summary: Update instructions on how to use the binary/source release bundles Key: EDGENT-364 URL: https://issues.apache.org/jira/browse/EDGENT-364 Project: Edgent Issue Type: Improvement Components: Documentation, Web Site Reporter: Queenie Ma Assignee: Queenie Ma Priority: Minor I figure this information can be updated in the [Downloading Apache Edgent|http://edgent.incubator.apache.org/docs/edgent-getting-started.html#downloading-apache-edgent] section of the _Getting started_ page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EDGENT-71) Add bluetooth support
[ https://issues.apache.org/jira/browse/EDGENT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-71: -- Description: Moved from https://github.com/quarks-edge/quarks/issues/85 . [dlaboss] I did a bit of investigation of the use of Bluecove (http://www.bluecove.org/) as suggested in that original issue: - BlueCove implements JSR-82 "javax.bluetooth" but development seems to have stopped in 2008 - "doesn't implement BLE" [1] - challenges making it work on a Raspberry Pi [4], making it work on a Pi [5] - some of it is GPL (unacceptible) but some (the part of interest?) is AL-2.0 Intel TinyB [2] - what platforms? "everything worked" [1] Android BLE API [3] Looks like Java ME SDK 3.0 include Bluetooth from in the "Wireless Toolkit" [6] (present in "SE embedded" or "ME embedded" ?) For some applications there was a suggestion to just the standard linux Bluetooth stack "BlueZ" utils e.g., "sudo hcitool lescan" and process the command output. I've also seen an approach using python to access the bluez stack APIs to perform a "device scan" and emit the desired info to stdout. Edgent's Command connector (CommandStreams) provides a convenient way to integrate with external commands should use of external commands be an acceptable solution. [1] http://stackoverflow.com/questions/28855288/java-j2se-bluetooth-low-energy-ble [2] intel TinyB https://software.intel.com/en-us/java-for-bluetooth-le-apps [3] android BLE API https://developer.android.com/guide/topics/connectivity/bluetooth-le.html [4] Pi/Bluecove nightmare https://www.raspberrypi.org/forums/viewtopic.php?f=81=120317 [5] 2015 Pi/Bluecove success? http://lukealderton.com/blog/posts/2015/january/raspberry-pi-bluetooth-using-bluecove-on-raspbian.aspx [6] http://www.oracle.com/technetwork/java/download-135801.html was:Moved from https://github.com/quarks-edge/quarks/issues/85 . > Add bluetooth support > - > > Key: EDGENT-71 > URL: https://issues.apache.org/jira/browse/EDGENT-71 > Project: Edgent > Issue Type: Improvement >Reporter: Victor Dogaru > > Moved from https://github.com/quarks-edge/quarks/issues/85 . > [dlaboss] > I did a bit of investigation of the use of Bluecove > (http://www.bluecove.org/) as suggested in that original issue: > - BlueCove implements JSR-82 "javax.bluetooth" but development seems to have > stopped in 2008 > - "doesn't implement BLE" [1] > - challenges making it work on a Raspberry Pi [4], making it work on a Pi [5] > - some of it is GPL (unacceptible) but some (the part of interest?) is AL-2.0 > Intel TinyB [2] - what platforms? "everything worked" [1] > Android BLE API [3] > Looks like Java ME SDK 3.0 include Bluetooth from in the "Wireless Toolkit" > [6] >(present in "SE embedded" or "ME embedded" ?) > For some applications there was a suggestion to just the standard linux > Bluetooth stack "BlueZ" utils > e.g., "sudo hcitool lescan" and process the command output. > I've also seen an approach using python to access the bluez stack APIs to > perform a "device scan" and emit the > desired info to stdout. > Edgent's Command connector (CommandStreams) provides a convenient way to > integrate with external commands should use of external commands be an > acceptable solution. > [1] > http://stackoverflow.com/questions/28855288/java-j2se-bluetooth-low-energy-ble > [2] intel TinyB https://software.intel.com/en-us/java-for-bluetooth-le-apps > [3] android BLE API > https://developer.android.com/guide/topics/connectivity/bluetooth-le.html > [4] Pi/Bluecove nightmare > https://www.raspberrypi.org/forums/viewtopic.php?f=81=120317 > [5] 2015 Pi/Bluecove success? > http://lukealderton.com/blog/posts/2015/january/raspberry-pi-bluetooth-using-bluecove-on-raspbian.aspx > [6] http://www.oracle.com/technetwork/java/download-135801.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EDGENT-363) clarify / disallow null topology names
[ https://issues.apache.org/jira/browse/EDGENT-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere resolved EDGENT-363. Resolution: Fixed resolved via https://github.com/apache/incubator-edgent/pull/271 > clarify / disallow null topology names > -- > > Key: EDGENT-363 > URL: https://issues.apache.org/jira/browse/EDGENT-363 > Project: Edgent > Issue Type: Bug > Components: API >Reporter: Dale LaBossiere >Assignee: Dale LaBossiere > > TopologyProvider.newTopology(String name) doesn't state that null/empty names > are disallowed. DirectProvider allows them. But other places in the code > will be unhappy or non-sensical if they are - e.g., Etaio's synthesis of a > job-name. > ApplicationService.registerTopology() and IotProvider.registerTopology() are > other places. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-360) Change Javadoc Dropdown's lastest word to latest under the web site
[ https://issues.apache.org/jira/browse/EDGENT-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815413#comment-15815413 ] Queenie Ma commented on EDGENT-360: --- Fixed in the changes associated with EDGENT-327. > Change Javadoc Dropdown's lastest word to latest under the web site > --- > > Key: EDGENT-360 > URL: https://issues.apache.org/jira/browse/EDGENT-360 > Project: Edgent > Issue Type: Bug > Components: Web Site >Affects Versions: Apache Edgent 1.0.0 >Reporter: Cazen Lee >Priority: Trivial > Labels: newbie > Fix For: Apache Edgent 1.1.0 > > > Latest is not grammatically correct, so change to latest (typo) > You can find it in the javadoc dropdown of topnav at > http://edgent.incubator.apache.org/docs/home -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (EDGENT-360) Change Javadoc Dropdown's lastest word to latest under the web site
[ https://issues.apache.org/jira/browse/EDGENT-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma resolved EDGENT-360. --- Resolution: Fixed Assignee: Queenie Ma > Change Javadoc Dropdown's lastest word to latest under the web site > --- > > Key: EDGENT-360 > URL: https://issues.apache.org/jira/browse/EDGENT-360 > Project: Edgent > Issue Type: Bug > Components: Web Site >Affects Versions: Apache Edgent 1.0.0 >Reporter: Cazen Lee >Assignee: Queenie Ma >Priority: Trivial > Labels: newbie > Fix For: Apache Edgent 1.1.0 > > > Latest is not grammatically correct, so change to latest (typo) > You can find it in the javadoc dropdown of topnav at > http://edgent.incubator.apache.org/docs/home -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing
[ https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815404#comment-15815404 ] Dale LaBossiere commented on EDGENT-327: [~queeniema] As your contribs also addressed https://issues.apache.org/jira/browse/EDGENT-360 please take ownership of it - and credit for resolving it! :-) > some http urls in the website prevent full local testing > > > Key: EDGENT-327 > URL: https://issues.apache.org/jira/browse/EDGENT-327 > Project: Edgent > Issue Type: Task > Components: Web Site >Reporter: Dale LaBossiere >Assignee: Queenie Ma >Priority: Trivial > > If you create a local / test instance of the website (e.g., "jekyll server") > all of the javadoc related links go to the live website. > site/_config.yml defines docurl which is used in many places. See the note > there about issues encountered when I tried changing it from a http url to a > / url... though overall it seemed to work. > Also the javadoc "latest", 1.0.0, ... links in > site/_data/mydoc/mydoc_topnav.yml are http links. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing
[ https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815388#comment-15815388 ] ASF GitHub Bot commented on EDGENT-327: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent-website/pull/89 > some http urls in the website prevent full local testing > > > Key: EDGENT-327 > URL: https://issues.apache.org/jira/browse/EDGENT-327 > Project: Edgent > Issue Type: Task > Components: Web Site >Reporter: Dale LaBossiere >Assignee: Queenie Ma >Priority: Trivial > > If you create a local / test instance of the website (e.g., "jekyll server") > all of the javadoc related links go to the live website. > site/_config.yml defines docurl which is used in many places. See the note > there about issues encountered when I tried changing it from a http url to a > / url... though overall it seemed to work. > Also the javadoc "latest", 1.0.0, ... links in > site/_data/mydoc/mydoc_topnav.yml are http links. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-edgent-website pull request #89: [EDGENT-327] Use local Javadoc UR...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent-website/pull/89 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (EDGENT-327) some http urls in the website prevent full local testing
[ https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814869#comment-15814869 ] ASF GitHub Bot commented on EDGENT-327: --- Github user dlaboss commented on the issue: https://github.com/apache/incubator-edgent-website/pull/89 +1 thanks for straightening this out! > some http urls in the website prevent full local testing > > > Key: EDGENT-327 > URL: https://issues.apache.org/jira/browse/EDGENT-327 > Project: Edgent > Issue Type: Task > Components: Web Site >Reporter: Dale LaBossiere >Assignee: Queenie Ma >Priority: Trivial > > If you create a local / test instance of the website (e.g., "jekyll server") > all of the javadoc related links go to the live website. > site/_config.yml defines docurl which is used in many places. See the note > there about issues encountered when I tried changing it from a http url to a > / url... though overall it seemed to work. > Also the javadoc "latest", 1.0.0, ... links in > site/_data/mydoc/mydoc_topnav.yml are http links. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
