[jira] [Resolved] (EDGENT-371) Not seeing animations with chrome
[ https://issues.apache.org/jira/browse/EDGENT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma resolved EDGENT-371. --- Resolution: Fixed > Not seeing animations with chrome > - > > Key: EDGENT-371 > URL: https://issues.apache.org/jira/browse/EDGENT-371 > Project: Edgent > Issue Type: Bug > Components: Web Site >Reporter: Dale LaBossiere >Assignee: Queenie Ma > Attachments: Screen Shot 2017-01-24 at 10.54.30 AM.png > > > Using chrome (v55.0 on OSX) I navigated to > https://edgent.apache.org/docs/streaming-concepts. I didn't see the > animations. I noticed the protections shield shown in the screenshot > attachment. Can anything be done on the site to make this all "just work"? > Using firefox the animations on > https://edgent.apache.org/docs/streaming-concepts show up fine (though it > shows the connection as insecure and apparently I may have allowed that in > the past). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (EDGENT-371) Not seeing animations with chrome
[ https://issues.apache.org/jira/browse/EDGENT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma reassigned EDGENT-371: - Assignee: Queenie Ma > Not seeing animations with chrome > - > > Key: EDGENT-371 > URL: https://issues.apache.org/jira/browse/EDGENT-371 > Project: Edgent > Issue Type: Bug > Components: Web Site >Reporter: Dale LaBossiere >Assignee: Queenie Ma > Attachments: Screen Shot 2017-01-24 at 10.54.30 AM.png > > > Using chrome (v55.0 on OSX) I navigated to > https://edgent.apache.org/docs/streaming-concepts. I didn't see the > animations. I noticed the protections shield shown in the screenshot > attachment. Can anything be done on the site to make this all "just work"? > Using firefox the animations on > https://edgent.apache.org/docs/streaming-concepts show up fine (though it > shows the connection as insecure and apparently I may have allowed that in > the past). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EDGENT-37) Visual aids to help understand streaming
[ https://issues.apache.org/jira/browse/EDGENT-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma closed EDGENT-37. > Visual aids to help understand streaming > > > Key: EDGENT-37 > URL: https://issues.apache.org/jira/browse/EDGENT-37 > Project: Edgent > Issue Type: Task > Components: Web Site >Reporter: Daniel John Debrunner >Assignee: Queenie Ma >Priority: Minor > Attachments: continuousAggregate.html, filter.html, > last5secondswindow.html > > > For a while I wanted to create web-pages that visually demonstrated > streaming, and I found the time to figure out the Javascript to do it. > I created three pages demonstrating filter, windows and continuous > aggregation. > Once the web-site is up I was thinking they could be added (along with an > intro page) somewhere in the site. Assuming that is folks think they are > useful. > I'd welcome involvement from others in adding new pages (e.g. split, batch, > union etc.) and/or improving the look and feel of the pages. The initial > pages can be seen as a seed of a teaching aid for streaming. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (EDGENT-183) Replace from all the URLs that hardcoded to using properties
[ https://issues.apache.org/jira/browse/EDGENT-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma closed EDGENT-183. - Resolution: Fixed > Replace from all the URLs that hardcoded to using properties > > > Key: EDGENT-183 > URL: https://issues.apache.org/jira/browse/EDGENT-183 > Project: Edgent > Issue Type: Improvement > Components: Web Site >Reporter: Cazen Lee >Assignee: Queenie Ma > Labels: newbie > > Replace from all the URLs that hardcoded to using properties > All major URLs will be managed by properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EDGENT-168) Console Splitter properties hover output tags wrong
[
https://issues.apache.org/jira/browse/EDGENT-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Queenie Ma updated EDGENT-168:
--
Attachment: multiple_target_stream_tags.png
multiple_source_stream_tags.png
Attached are images of what the new tags look like. There is a {{Split}} oplet,
resulting in two streams. One is tagged with the tags {{even1}} and {{even2}},
and the other stream is tagged with {{odd1}} and {{odd2}}. When hovering over
the {{Split}} oplet (see _multiple_target_streams_tag.png_), all 4 tags appear
in 'Target Stream Tags'.
The {{Union}} oplet has similar behavior. Both source streams contain multiple
tags (4 total), and all 4 appear in 'Source Stream Tags' (see
_multiple_source_streams_tag.png_).
> Console Splitter properties hover output tags wrong
> ---
>
> Key: EDGENT-168
> URL: https://issues.apache.org/jira/browse/EDGENT-168
> Project: Edgent
> Issue Type: Bug
> Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
> Labels: newbie
> Attachments: Screen Shot 2016-05-04 at 12.41.30 PM.png,
> multiple_source_stream_tags.png, multiple_target_stream_tags.png
>
>
> The hover on a TStream.split() generated Splitter oplet incorrectly reports
> only that last splitter channel's tag for Target Stream Tags.
> Minimally it seems like it should list the first channel's tag (or the first
> channel with a tag) and then ", ..." to indicate there are more.
> See the attached image.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (EDGENT-168) Console Splitter properties hover output tags wrong
[ https://issues.apache.org/jira/browse/EDGENT-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma updated EDGENT-168: -- Comment: was deleted (was: Yes, the column widens automatically to accommodate all tags (see _column_width_tags.png_).) > Console Splitter properties hover output tags wrong > --- > > Key: EDGENT-168 > URL: https://issues.apache.org/jira/browse/EDGENT-168 > Project: Edgent > Issue Type: Bug > Components: Console >Reporter: Dale LaBossiere >Assignee: Queenie Ma >Priority: Minor > Labels: newbie > Attachments: Screen Shot 2016-05-04 at 12.41.30 PM.png, > column_width_tags.png, multiple_source_stream_tags.png, > multiple_target_stream_tags.png > > > The hover on a TStream.split() generated Splitter oplet incorrectly reports > only that last splitter channel's tag for Target Stream Tags. > Minimally it seems like it should list the first channel's tag (or the first > channel with a tag) and then ", ..." to indicate there are more. > See the attached image. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-178) console: stream hover should report "alias" in addition to tags; maybe oplet hover too
[
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524184#comment-15524184
]
Queenie Ma commented on EDGENT-178:
---
[~dlaboss], would you mind giving me an idea of what you think should be
displayed for oplet hovers? Perhaps what is mentioned in the previous comment?
Thanks!
> console: stream hover should report "alias" in addition to tags; maybe oplet
> hover too
> --
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
> Issue Type: Improvement
> Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
> Labels: newbie
> Attachments: alias_stream_hover.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to
> tags. I'm pretty sure the graph json captures the alias already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close"
[ https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15524187#comment-15524187 ] Queenie Ma commented on EDGENT-179: --- I think that's a good idea, and I'll work on implementing it. Thank you for your input! > console: oplet coloring gradients "too close" > - > > Key: EDGENT-179 > URL: https://issues.apache.org/jira/browse/EDGENT-179 > Project: Edgent > Issue Type: Bug > Components: Console >Reporter: Dale LaBossiere >Assignee: Queenie Ma >Priority: Minor > Attachments: EDGENT-179_oplet_colors.png, Screen Shot 2016-09-19 at > 2.22.00 PM.png > > > The oplet color generator ends up yielding two light purple-ish colors for > two different kinds of (adjacent) oplets and one can't tell them apart. One > is a Sink the other is a subtype of Peek - a StreamScope. > I was seeing this in a ParallelBalancedRecipe app of mine. I can provide it > if really necessary to repro/improve this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts
[ https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma updated EDGENT-200: -- Attachment: stream_hover_current.png > 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: stream_hover_current.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)
[jira] [Commented] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts
[ https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15533242#comment-15533242 ] Queenie Ma commented on EDGENT-200: --- I see that stream hovers already have tuple count information. See attached: stream_hover_current.png. So, this issue may not be relevant anymore. But, I like the idea of adding tuple counts to hover popups in the _Static flow_ layer. Regarding the previous comment, I think it would be safe to remove the _Tuple count_ field column from oplet hovers since this information is now available in the _Source streams_ and _Target streams_ columns as part of [EDGENT-178|https://issues.apache.org/jira/browse/EDGENT-178]. Each source/target stream now lists the number of tuples flowing through it, as well as alias and tag information. With this, we can see the number of tuples flowing in/out of an oplet. > 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: stream_hover_current.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)
[jira] [Resolved] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts
[ https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma resolved EDGENT-200. --- Resolution: Resolved > 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)
[jira] [Updated] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts
[ https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma updated EDGENT-200: -- Attachment: in_not_equal_to_out_tuple_count.png in_equals_out_tuple_count.png > 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 > > > 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)
[jira] [Updated] (EDGENT-200) Console: stream hovers in oplet kind layout lack tuple counts
[ https://issues.apache.org/jira/browse/EDGENT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma updated EDGENT-200: -- Attachment: tuple_count_static_layer.png > 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)
[jira] [Commented] (EDGENT-248) [console] no hover popup for source oplet
[ https://issues.apache.org/jira/browse/EDGENT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497454#comment-15497454 ] Queenie Ma commented on EDGENT-248: --- I followed those steps (but had to modify the CLASSPATH variable in runfilesample.sh to get the script to run), but still couldn't reproduce it. I'm on Mac as well and tested on the same three browsers. I tried using both my cloned Git repo and the downloaded master zip file from GitHub. I think we may need someone else to try this out... But yes, I have seen what you mentioned before (both the leftmost source oplet and its output stream didn't bring up anything on hover). That fact that I can't reproduce it anymore is odd. > [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 > > 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] [Closed] (EDGENT-245) replace the favicon.png for the console with a new one that uses E instead of Q
[ https://issues.apache.org/jira/browse/EDGENT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma closed EDGENT-245. - Resolution: Resolved > replace the favicon.png for the console with a new one that uses E instead of > Q > --- > > Key: EDGENT-245 > URL: https://issues.apache.org/jira/browse/EDGENT-245 > Project: Edgent > Issue Type: Task > Components: Console >Reporter: Susan L. Cline >Assignee: Queenie Ma >Priority: Minor > Labels: newbie > > The old favicon.png has a 'Q' in the middle of it. It needs to have the 'E' > in the middle of it now that the project has changed from 'Quarks' to > 'Edgent'. This would be a great newbie item. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close"
[
https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504099#comment-15504099
]
Queenie Ma commented on EDGENT-179:
---
It looks like this may have been fixed in [PR
#116|https://github.com/apache/incubator-edgent/pull/116/commits/18c2480560544aa56cb904e0e5f351fbf956fcb7]
as the colors are not too similar anymore. StreamScope oplets are
{color:#c7c7c7}#c7c7c7{color} (light grey), and Sink oplets are
{color:#c5b0d5}#c5b0d5{color} (light purple). See screenshot.
[~dlaboss], is this okay to close?
> console: oplet coloring gradients "too close"
> -
>
> Key: EDGENT-179
> URL: https://issues.apache.org/jira/browse/EDGENT-179
> Project: Edgent
> Issue Type: Bug
> Components: Console
>Reporter: Dale LaBossiere
>Priority: Minor
> Attachments: EDGENT-179_oplet_colors.png
>
>
> The oplet color generator ends up yielding two light purple-ish colors for
> two different kinds of (adjacent) oplets and one can't tell them apart. One
> is a Sink the other is a subtype of Peek - a StreamScope.
> I was seeing this in a ParallelBalancedRecipe app of mine. I can provide it
> if really necessary to repro/improve this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EDGENT-179) console: oplet coloring gradients "too close"
[ https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma updated EDGENT-179: -- Attachment: EDGENT-179_oplet_colors.png > console: oplet coloring gradients "too close" > - > > Key: EDGENT-179 > URL: https://issues.apache.org/jira/browse/EDGENT-179 > Project: Edgent > Issue Type: Bug > Components: Console >Reporter: Dale LaBossiere >Priority: Minor > Attachments: EDGENT-179_oplet_colors.png > > > The oplet color generator ends up yielding two light purple-ish colors for > two different kinds of (adjacent) oplets and one can't tell them apart. One > is a Sink the other is a subtype of Peek - a StreamScope. > I was seeing this in a ParallelBalancedRecipe app of mine. I can provide it > if really necessary to repro/improve this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close"
[
https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507280#comment-15507280
]
Queenie Ma commented on EDGENT-179:
---
Currently, the oplet colors are hard-coded by oplet kind ({{invocation.kind}})
in {{graph.js}}. The issue wih the "ParallelBalancedRecipe" sample is that the
Peek oplet's kind ({{org.apache.edgent.oplet.functional.Peek}}) was not defined
in {{graph.js}}, so its color was generated randomly and was chosen to be the
same color as the Union oplet. To fix this bug, we need to assign a new color
to this Peek oplet.
However, I suspect that other oplet kinds may have been missed when hard-coding
these colors. Is there a way to get a list of all possible kinds without
manually looking at each of the classes?
In the future, if an oplet kind has not been assigned a color (e.g., because it
was missed or because it is new), I think it would be a good idea to perhaps
hard-code a set of unused colors and pick one of them to assign to the oplet
kind. This way, there will be no overlap.
> console: oplet coloring gradients "too close"
> -
>
> Key: EDGENT-179
> URL: https://issues.apache.org/jira/browse/EDGENT-179
> Project: Edgent
> Issue Type: Bug
> Components: Console
>Reporter: Dale LaBossiere
>Priority: Minor
> Attachments: EDGENT-179_oplet_colors.png, Screen Shot 2016-09-19 at
> 2.22.00 PM.png
>
>
> The oplet color generator ends up yielding two light purple-ish colors for
> two different kinds of (adjacent) oplets and one can't tell them apart. One
> is a Sink the other is a subtype of Peek - a StreamScope.
> I was seeing this in a ParallelBalancedRecipe app of mine. I can provide it
> if really necessary to repro/improve this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EDGENT-178) console: stream hover should report "alias" in addition to tags; maybe oplet hover too
[
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Queenie Ma updated EDGENT-178:
--
Attachment: oplet_hover.png
> console: stream hover should report "alias" in addition to tags; maybe oplet
> hover too
> --
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
> Issue Type: Improvement
> Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
> Labels: newbie
> Attachments: alias_stream_hover.png, oplet_hover.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to
> tags. I'm pretty sure the graph json captures the alias already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EDGENT-178) console: stream hover should report "alias" in addition to tags; maybe oplet hover too
[
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530803#comment-15530803
]
Queenie Ma commented on EDGENT-178:
---
I added an attachment for the new hover popup. Please take a look.
> console: stream hover should report "alias" in addition to tags; maybe oplet
> hover too
> --
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
> Issue Type: Improvement
> Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
> Labels: newbie
> Attachments: alias_stream_hover.png, oplet_hover.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to
> tags. I'm pretty sure the graph json captures the alias already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EDGENT-178) console: stream hover should report "alias" in addition to tags; maybe oplet hover too
[
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531230#comment-15531230
]
Queenie Ma commented on EDGENT-178:
---
Thanks for your feedback. I agree that the popup should be as narrow as
possible... I attached new images of the oplet hover popup and the oplet
properties window.
> console: stream hover should report "alias" in addition to tags; maybe oplet
> hover too
> --
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
> Issue Type: Improvement
> Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
> Labels: newbie
> Attachments: alias_stream_hover.png, oplet_hover.png,
> oplet_hover2.png, oplet_properties.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to
> tags. I'm pretty sure the graph json captures the alias already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EDGENT-178) console: stream hover should report "alias" in addition to tags; maybe oplet hover too
[
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Queenie Ma resolved EDGENT-178.
---
Resolution: Resolved
> console: stream hover should report "alias" in addition to tags; maybe oplet
> hover too
> --
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
> Issue Type: Improvement
> Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
> Labels: newbie
> Attachments: alias_stream_hover.png, oplet_hover.png,
> oplet_hover2.png, oplet_properties.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to
> tags. I'm pretty sure the graph json captures the alias already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EDGENT-178) console: stream hover should report "alias" in addition to tags; maybe oplet hover too
[
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Queenie Ma updated EDGENT-178:
--
Attachment: oplet_properties.png
oplet_hover2.png
> console: stream hover should report "alias" in addition to tags; maybe oplet
> hover too
> --
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
> Issue Type: Improvement
> Components: Console
>Reporter: Dale LaBossiere
>Assignee: Queenie Ma
>Priority: Minor
> Labels: newbie
> Attachments: alias_stream_hover.png, oplet_hover.png,
> oplet_hover2.png, oplet_properties.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to
> tags. I'm pretty sure the graph json captures the alias already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (EDGENT-289) Verify an Eclipse runtime development environment can be setup
[ https://issues.apache.org/jira/browse/EDGENT-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma resolved EDGENT-289. --- Resolution: Resolved > Verify an Eclipse runtime development environment can be setup > -- > > Key: EDGENT-289 > URL: https://issues.apache.org/jira/browse/EDGENT-289 > Project: Edgent > Issue Type: Sub-task >Reporter: Dale LaBossiere >Assignee: Queenie Ma > -- 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] [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] [Assigned] (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:all-tabpanel ] Queenie Ma reassigned EDGENT-327: - Assignee: Queenie Ma > 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-234) Console: broken doc links
[ https://issues.apache.org/jira/browse/EDGENT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802242#comment-15802242 ] Queenie Ma commented on EDGENT-234: --- Will remove these broken links. > Console: broken doc links > - > > Key: EDGENT-234 > URL: https://issues.apache.org/jira/browse/EDGENT-234 > Project: Edgent > Issue Type: Bug > Components: Console >Reporter: Dale LaBossiere >Assignee: Queenie Ma >Priority: Minor > > In doing the Edgent rename, noticed two broken doc links in the console > samples. In both cases they refer to console/package-summary > (package-info.java) info that doesn't exist. > See the samples.console's "Web Console Application" link on this page > incubator-quarks/target/docs/javadoc/overview-summary.html > and a similar link in the Description text on this page > incubator-quarks/target/docs/javadoc/org/apache/edgent/samples/console/package-summary.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (EDGENT-234) Console: broken doc links
[ https://issues.apache.org/jira/browse/EDGENT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma reassigned EDGENT-234: - Assignee: Queenie Ma > Console: broken doc links > - > > Key: EDGENT-234 > URL: https://issues.apache.org/jira/browse/EDGENT-234 > Project: Edgent > Issue Type: Bug > Components: Console >Reporter: Dale LaBossiere >Assignee: Queenie Ma >Priority: Minor > > In doing the Edgent rename, noticed two broken doc links in the console > samples. In both cases they refer to console/package-summary > (package-info.java) info that doesn't exist. > See the samples.console's "Web Console Application" link on this page > incubator-quarks/target/docs/javadoc/overview-summary.html > and a similar link in the Description text on this page > incubator-quarks/target/docs/javadoc/org/apache/edgent/samples/console/package-summary.html -- 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=15802747#comment-15802747
]
Queenie Ma commented on EDGENT-327:
---
I looked into the {{ERROR `/javadoc/latest/resources/fonts/dejavu.css' not
found}} messages. It seems to be a bug in the Javadoc tool due to a dangling
reference to dejavu.css in stylesheet.css. Note the {{@import}} statement
below.
{code:title=stylesheet.css|borderStyle=solid}
@import url('resources/fonts/dejavu.css');
body {
background-color:#ff;
color:#353833;
font-family:'DejaVu Sans', Arial, Helvetica, sans-serif;
font-size:14px;
margin:0;
}
...
{code}
Found this related issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=470739.
A person who commented on that issue submitted a Java bug, but it seems that
the bug hasn't been fixed.
Workarounds are:
# Manually add the dejavu.css font file to the generated Javadoc (not sure
where to get that file)
# Remove the {{@import}} statement and use a different default font
Thoughts?
> 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=15805357#comment-15805357
]
Queenie Ma commented on EDGENT-327:
---
I'm not sure why that favicon.ico message appears. I don't see any references
to it in the javadoc folder, which is odd...
If the external URL is used, then an error is displayed in the browser console
when you navigate to the
[page|https://edgent.incubator.apache.org/javadoc/latest/index.html], rather
than in the Jekyll output.
{quote}
Failed to load resource: the server responded with a status of 404 (Not Found)
https://edgent.incubator.apache.org/javadoc/latest/resources/fonts/dejavu.css
{quote}
> 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=15812317#comment-15812317
]
Queenie Ma commented on EDGENT-327:
---
I just committed some changes that removes the DejaVu references in
{{stylesheet.css}} in {{build.sh}}. Since these replacements do not occur until
the site is built, running {{jekyll serve}} will still show the {{ERROR
`/javadoc/latest/resources/fonts/dejavu.css' not found}} message. For the other
error message regarding {{favicon.ico}}, it seems that Jekyll automatically
looks for that file so I just added it to the root of the site.
> 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] [Closed] (EDGENT-315) The d3 images on the streaming-concepts.html page are not appearing
[ 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] [Commented] (EDGENT-248) [console] no hover popup for source oplet
[ 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] [Updated] (EDGENT-248) [console] no hover popup for source oplet
[ 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] [Closed] (EDGENT-248) [console] no hover popup for source oplet
[ 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] [Closed] (EDGENT-410) Update the Apache Incubator logo to the new logo
[ https://issues.apache.org/jira/browse/EDGENT-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Queenie Ma closed EDGENT-410. - Resolution: Resolved > Update the Apache Incubator logo to the new logo > > > Key: EDGENT-410 > URL: https://issues.apache.org/jira/browse/EDGENT-410 > Project: Edgent > Issue Type: Task > Components: Web Site >Reporter: Queenie Ma >Assignee: Queenie Ma > > The Incubator has recently selected a new logo. We need to update the logo on > our website to use the new logo (the first image in Press Kit for Podlings > page at http://incubator.apache.org/guides/press-kit.html). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (EDGENT-410) Update the Apache Incubator logo to the new logo
Queenie Ma created EDGENT-410: - Summary: Update the Apache Incubator logo to the new logo Key: EDGENT-410 URL: https://issues.apache.org/jira/browse/EDGENT-410 Project: Edgent Issue Type: Task Components: Web Site Reporter: Queenie Ma Assignee: Queenie Ma The Incubator has recently selected a new logo. We need to update the logo on our website to use the new logo (the first image in Press Kit for Podlings page at http://incubator.apache.org/guides/press-kit.html). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
