[jira] [Reopened] (EDGENT-248) [console] no hover popup for source oplet

[Dale LaBossiere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale LaBossiere reopened EDGENT-248:


Maybe that was it!  I just tried with a full-width window and everything worked 
- the source oplet is about 1/2 across the page, under the "Topology Graph" 
title (chrome fwiw).  

Then narrowing the window so the oplet is about 1/4 of the way across, under 
the "View by" tag, and the popup doesn't show up. The window is still >3/4 the 
width of my screen. Incrementally widening the window then makes it so the 
popup shows up.

Reopening.  The console needs to be smart enough to place the hover where it 
can be displayed / is visible.  The user has no clue what's going on and the 
window size is more than reasonable when the problem happens.

Hmm... I also just noticed that if one continues to narrow the window, 
eventually the graph slides off the LHS of the screen, whereas the rest of the 
widgets stay on the left and the right gets clipped, and the slider bar doesn't 
help make the graph visible again.

> [console] no hover popup for source oplet
> -
>
> Key: EDGENT-248
> URL: https://issues.apache.org/jira/browse/EDGENT-248
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
> Attachments: HoverPopupWorking.png
>
>
> This used to work... if you hover on a source oplet (of any type?) no popup 
> is generated.  Hovering on other oplets works fine.  (can demo with sample 
> file connector - see scripts/connectors/file/README) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EDGENT-312) update website's "where to get edgent" info

[Dale LaBossiere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale LaBossiere resolved EDGENT-312.

Resolution: Fixed

resolved via https://github.com/apache/incubator-edgent-website/pull/80

> update website's "where to get edgent" info
> ---
>
> Key: EDGENT-312
> URL: https://issues.apache.org/jira/browse/EDGENT-312
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> http://edgent.incubator.apache.org/docs/faq.html#where-can-i-download-apache-edgent-to-try-it-out
> Seems like the "is migrating" info should be removed.  
> Also the reference to the non-apache binary info is probably best removed.  
> It can be replaced by https://www.apache.org/dist/release/incubator/edgent  
> -- which will be empty until we get the first release out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EDGENT-322) Source function recipe missing submit()

[Dale LaBossiere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale LaBossiere resolved EDGENT-322.

Resolution: Fixed

resolved via https://github.com/apache/incubator-edgent-website/pull/84

> Source function recipe missing submit()
> ---
>
> Key: EDGENT-322
> URL: https://issues.apache.org/jira/browse/EDGENT-322
> Project: Edgent
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>Priority: Minor
>
> Recipe http://edgent.incubator.apache.org/recipes/recipe_source_function.html 
> can lead to confusion with newbies because the main() part way down the page 
> lacks the "dp.submit(top)" necessary for it to generate the output shown. 
> (note, it's present in the periodic section's main)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EDGENT-326) More website cleanup for faq, downloads

[Dale LaBossiere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale LaBossiere resolved EDGENT-326.

Resolution: Fixed

resolved via https://github.com/apache/incubator-edgent-website/pull/84

> More website cleanup for faq, downloads
> ---
>
> Key: EDGENT-326
> URL: https://issues.apache.org/jira/browse/EDGENT-326
> Project: Edgent
>  Issue Type: Task
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>
> - a few places should be Download instead of just Download Source
> - the downloads page needs separate signature/checksum file links for source 
> vs binary bundles.  the page can also be simplified a bit (my bad)
> - rename some of the url links to make managing the website pages clearer
> - clean up a couple of items in the FAQ
> - fix a problem in the source-function-recipe (EDGENT-322)
> - add a recipe for creating a connector
> - fix reference to quarks-edge github url
> - fix reference to apache-edgent stackoverflow tag
> - no link back to edgent.apache.org from the Documentation home



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-322) Source function recipe missing submit()

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15771252#comment-15771252
 ] 

ASF GitHub Bot commented on EDGENT-322:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/84


> Source function recipe missing submit()
> ---
>
> Key: EDGENT-322
> URL: https://issues.apache.org/jira/browse/EDGENT-322
> Project: Edgent
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>Priority: Minor
>
> Recipe http://edgent.incubator.apache.org/recipes/recipe_source_function.html 
> can lead to confusion with newbies because the main() part way down the page 
> lacks the "dp.submit(top)" necessary for it to generate the output shown. 
> (note, it's present in the periodic section's main)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-edgent-website pull request #84: [Edgent-326] website faqs, downlo...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-edgent-website/pull/84


---
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-322) Source function recipe missing submit()

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15771169#comment-15771169
 ] 

ASF GitHub Bot commented on EDGENT-322:
---

GitHub user dlaboss opened a pull request:

https://github.com/apache/incubator-edgent-website/pull/84

[Edgent-326] website faqs, downloads cleanup

- clarify 1.0.0-incubating on sidebar of doc
- change quarks github reference to edgent
- fix stackoverflow apache-edgent tag reference
- define separate src and bin download urls for signatures, ...
- add way to navigate back to edgent home from documentation page (Edgent 
References -> ...)
- change Download Source to Downloads
- refactor the downloads page to simplify and for separate src vs bin 
signatures, etc
- tweak doap_Edgent.rdf
- simplify and correct stuff in faq
- fix source-function recipe (EDGENT-322)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dlaboss/incubator-edgent-website 
tweakDownloads

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-edgent-website/pull/84.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #84


commit 13c657adc448da0cbed81e241527a99cf5f2828b
Author: Dale LaBossiere 
Date:   2016-12-22T21:26:15Z

[Edgent-326] more website cleanup

commit 951f4413c06f6c7fa135c5a47ab3db8cecbee241
Author: Dale LaBossiere 
Date:   2016-12-22T21:41:04Z

fix new External References -> edgent.apache.org link




> Source function recipe missing submit()
> ---
>
> Key: EDGENT-322
> URL: https://issues.apache.org/jira/browse/EDGENT-322
> Project: Edgent
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>Priority: Minor
>
> Recipe http://edgent.incubator.apache.org/recipes/recipe_source_function.html 
> can lead to confusion with newbies because the main() part way down the page 
> lacks the "dp.submit(top)" necessary for it to generate the output shown. 
> (note, it's present in the periodic section's main)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EDGENT-248) [console] no hover popup for source oplet

[Queenie Ma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Queenie Ma closed EDGENT-248.
-
Resolution: Not A Bug
  Assignee: Queenie Ma

> [console] no hover popup for source oplet
> -
>
> Key: EDGENT-248
> URL: https://issues.apache.org/jira/browse/EDGENT-248
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
> Attachments: HoverPopupWorking.png
>
>
> This used to work... if you hover on a source oplet (of any type?) no popup 
> is generated.  Hovering on other oplets works fine.  (can demo with sample 
> file connector - see scripts/connectors/file/README) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EDGENT-248) [console] no hover popup for source oplet

[Queenie Ma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Queenie Ma updated EDGENT-248:
--
Attachment: HoverPopupWorking.png

> [console] no hover popup for source oplet
> -
>
> Key: EDGENT-248
> URL: https://issues.apache.org/jira/browse/EDGENT-248
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
> Attachments: HoverPopupWorking.png
>
>
> This used to work... if you hover on a source oplet (of any type?) no popup 
> is generated.  Hovering on other oplets works fine.  (can demo with sample 
> file connector - see scripts/connectors/file/README) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-248) [console] no hover popup for source oplet

[Queenie Ma (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15771017#comment-15771017
 ] 

Queenie Ma commented on EDGENT-248:
---

I believe that the issue may be that your browser window was too small. The 
hover popup appears to the left of the oplet but it will not be visible if the 
window is not big enough. I've attached a screenshot of the popup working with 
file connector sample.

> [console] no hover popup for source oplet
> -
>
> Key: EDGENT-248
> URL: https://issues.apache.org/jira/browse/EDGENT-248
> Project: Edgent
>  Issue Type: Bug
>  Components: Console
>Reporter: Dale LaBossiere
> Attachments: HoverPopupWorking.png
>
>
> This used to work... if you hover on a source oplet (of any type?) no popup 
> is generated.  Hovering on other oplets works fine.  (can demo with sample 
> file connector - see scripts/connectors/file/README) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15770985#comment-15770985
 ] 

ASF GitHub Bot commented on EDGENT-200:
---

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent/pull/258

[EDGENT-200] Console: Add missing tuple counts



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/queeniema/incubator-edgent EDGENT-200

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-edgent/pull/258.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #258


commit 8b34651a3ba489dc6adad58048fe5deb0ffa0285
Author: Queenie Ma 
Date:   2016-12-22T20:09:43Z

[EDGENT-200] Console: Add missing tuple counts




> Console: stream hovers in oplet kind layout lack tuple counts
> -
>
> Key: EDGENT-200
> URL: https://issues.apache.org/jira/browse/EDGENT-200
> Project: Edgent
>  Issue Type: Improvement
>  Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
>  Labels: newbie
> Attachments: in_equals_out_tuple_count.png, 
> in_not_equal_to_out_tuple_count.png, stream_hover_current.png, 
> tuple_count_static_layer.png
>
>
> stream hovers lack tuple count.  oplet hovers have them.
> related, wish the stream/oplet hovers in the static layout had tuple cnt info 
> too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-edgent pull request #258: [EDGENT-200] Console: Add missing tuple ...

[queeniema]

GitHub user queeniema opened a pull request:

https://github.com/apache/incubator-edgent/pull/258

[EDGENT-200] Console: Add missing tuple counts



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/queeniema/incubator-edgent EDGENT-200

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-edgent/pull/258.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #258


commit 8b34651a3ba489dc6adad58048fe5deb0ffa0285
Author: Queenie Ma 
Date:   2016-12-22T20:09:43Z

[EDGENT-200] Console: Add missing tuple counts




---
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] [Closed] (EDGENT-315) The d3 images on the streaming-concepts.html page are not appearing

[Queenie Ma (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Queenie Ma closed EDGENT-315.
-
Resolution: Works for Me

> The d3 images on the streaming-concepts.html page are not appearing
> ---
>
> Key: EDGENT-315
> URL: https://issues.apache.org/jira/browse/EDGENT-315
> Project: Edgent
>  Issue Type: Bug
>  Components: Web Site
>Reporter: Susan L. Cline
>Priority: Minor
>
> When I was reading this page it was referring to colors and streams and I 
> could not see any images.  It turns out that this error is being thrown when 
> browsing to the page and looking at a javascript console:
> Mixed Content: The page at 
> 'https://edgent.apache.org/docs/streaming-concepts.html' was loaded over 
> HTTPS, but requested an insecure script 'http://d3js.org/d3.v3.min.js'. This 
> request has been blocked; the content must be served over HTTPS.
> This seems to be due to attempting to fetch the d3 library at a non-https 
> url.  There is this post about this:
> https://github.com/jsbin/jsbin/issues/2549
> Also, I tried changing the url from 'http://d3js.org/d3.v3.min.js' in my 
> local incubator-edgent-website 'streaming-concepts.html' to 
> 'https://d3js.org/d3.v3.min.js' and it seems to work fine.  I.e, the images 
> appear.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EDGENT-326) More website cleanup for faq, downloads

[Dale LaBossiere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale LaBossiere updated EDGENT-326:
---
Description: 
- a few places should be Download instead of just Download Source
- the downloads page needs separate signature/checksum file links for source vs 
binary bundles.  the page can also be simplified a bit (my bad)
- rename some of the url links to make managing the website pages clearer
- clean up a couple of items in the FAQ
- fix a problem in the source-function-recipe (EDGENT-322)
- add a recipe for creating a connector
- fix reference to quarks-edge github url
- fix reference to apache-edgent stackoverflow tag
- no link back to edgent.apache.org from the Documentation home

  was:
- a few places should be Download instead of just Download Source
- the downloads page needs separate signature/checksum file links for source vs 
binary bundles.  the page can also be simplified a bit (my bad)
- rename some of the url links to make managing the website pages clearer
- clean up a couple of items in the FAQ
- fix a problem in the source-function-recipe (EDGENT-322)
- add a recipe for creating a connector


> More website cleanup for faq, downloads
> ---
>
> Key: EDGENT-326
> URL: https://issues.apache.org/jira/browse/EDGENT-326
> Project: Edgent
>  Issue Type: Task
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>
> - a few places should be Download instead of just Download Source
> - the downloads page needs separate signature/checksum file links for source 
> vs binary bundles.  the page can also be simplified a bit (my bad)
> - rename some of the url links to make managing the website pages clearer
> - clean up a couple of items in the FAQ
> - fix a problem in the source-function-recipe (EDGENT-322)
> - add a recipe for creating a connector
> - fix reference to quarks-edge github url
> - fix reference to apache-edgent stackoverflow tag
> - no link back to edgent.apache.org from the Documentation home



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EDGENT-326) More website cleanup for faq, downloads

[Dale LaBossiere (JIRA)]

Dale LaBossiere created EDGENT-326:
--

 Summary: More website cleanup for faq, downloads
 Key: EDGENT-326
 URL: https://issues.apache.org/jira/browse/EDGENT-326
 Project: Edgent
  Issue Type: Task
Reporter: Dale LaBossiere
Assignee: Dale LaBossiere


- a few places should be Download instead of just Download Source
- the downloads page needs separate signature/checksum file links for source vs 
binary bundles.  the page can also be simplified a bit (my bad)
- rename some of the url links to make managing the website pages clearer
- clean up a couple of items in the FAQ
- fix a problem in the source-function-recipe (EDGENT-322)
- add a recipe for creating a connector



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EDGENT-323) edgent.apache.org needs refactoring for "downloads" info

[Dale LaBossiere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale LaBossiere resolved EDGENT-323.

Resolution: Fixed

resolved via https://github.com/apache/incubator-edgent-website/pull/82

> edgent.apache.org needs refactoring for "downloads" info
> 
>
> Key: EDGENT-323
> URL: https://issues.apache.org/jira/browse/EDGENT-323
> Project: Edgent
>  Issue Type: Bug
>Reporter: Dale LaBossiere
>Assignee: Cazen Lee
>
> A precursor to making a release announcement is that the project's website is 
> updated for the release.
> There are several places in the current edgent.apache.org dealing with 
> downloads.  Downloads are a bit more complicated in the ASF world -- with the 
> official www.apache.org/dist site (and mirrors, and dynamic resolver) for 
> releases (with src and convenience binary bundles) as well as the Edgent ASF 
> git repo and mirror at github.
> We need a edgent.apache.org/downloads.html page that all other references / 
> buttons point to.  That page can clarify these different locations and their 
> uses, provide a list of releases, and release specific links (dynamic-mirror 
> links for bundles, backup-mirror links for the md5/sha/asc files, 
> release-specific-github link).
> Fwiw, it seems common for ASF release announcements to refer people to 
> /downloads.html as opposed just to the project's main page.
> Various locations related to downloads in edgent.apache.org:
> - Download Source button - links to github
> - Community tab -> Source Code - links to github
> - Getting Started tab -> Download Source - links to github
> - docs/community - "Source code" - no mention of ASF release, ...
> - docs/faq 
>   - "Where can I download..."  github and quarks-edge - see EDGENT-312 / 
> https://github.com/apache/incubator-edgent-website/pull/80
>   - "Where can I get the code?" - links to github
> - docs/edgent-getting-started
>   - upper left says Edgent Version 0.3.0
>   - "Downloading Apache Edgent" - has link to DEVELOPMENT.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EDGENT-298) Announce new release

[Dale LaBossiere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EDGENT-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale LaBossiere resolved EDGENT-298.

Resolution: Fixed

> Announce new release
> 
>
> Key: EDGENT-298
> URL: https://issues.apache.org/jira/browse/EDGENT-298
> Project: Edgent
>  Issue Type: Sub-task
>Reporter: Dale LaBossiere
>Assignee: Dale LaBossiere
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)