just some sparse thoughts.. naming is hard but we can agree on the fact that in the name, moving from left to right we go from general to particular.

If your module brings to PDL the ability to open websockets then PDL::WebSocket should be correct, but there is also the possibility that you module enhances Mojo::WebSocket with the ability to create live ndarray, so i'd dont exclude something like Mojo::WebSocket::PDL or Mojo::WebSocket::PDLarray

In my opinion this depends on the point of view of the developper and how the module is created: if more stress is put on generalising the Mojo::WebSocket part or the PDL one.

Just my humble opinion

L*

Interesting so far! If I had a solid answer, I wouldn't need to ask for help. Also, to state the obvious: if anyone wants to beat me to it and prototype this (maybe posted on here?), that would be amazing!

use strict; use warnings;
use Mojo::UserAgent;
use Mojo::JSON qw(decode_json);
use Encode qw(encode);
my $ua = Mojo::UserAgent->new;
$ua->websocket("wss://ws1.blitzortung.org/" => sub { my ($ua, $tx) = @
+_;
  print "WebSocket handshake failed!\n" and return unless $tx->is_webs
+ocket;
  $tx->on(message => sub { my ($tx, $chars) = @_;
    $chars = blitz_decode($chars);
    my $bytes = encode('UTF-8', $chars, Encode::FB_CROAK);
    my $hash = decode_json $bytes;
    use Data::Dumper; print "message ", Dumper $hash;
  });
  $tx->send({json=>{a=>111}});
});
Mojo::IOLoop->start unless Mojo::IOLoop->is_running;

# code from https://github.com/mrk-its/homeassistant-blitzortung/issue
+s/74
sub blitz_decode {
  my ($data) = @_;
  my %e;
  my @d = split //, $data;
  my @g = my $f = my $c = $d[0];
  my $o = 256;
  for my $ind (1..$#d) {
    my $ord = ord($d[$ind]);
    my $str = $ord < 256 ? $d[$ind] : exists $e{$ord} ? $e{$ord} : $f 
+. $c;
    push @g, $str;
    $c = substr $str, 0, 1;
    $e{$o++} = $f . $c;
    $f = $str;
  }
  join('', @g);
}
[download]

using PDL's new plugin-based demo system). What would such a module be called? PDL::WebSocket?

What are the existing demos named?

PDL::WebSocket is definitely wrong as is Mojo::WebSocket::PDL... Its like naming your car Batter::Wheels because it uses a battery and wheels.

https://metacpan.org/search?q=pdl+demo says PDL::Demos::BAD_demo

So i says PDL::Demos::Etj_pdl_websocket_awesomeness - watch our big blue marble get zapped by lightning in real time

PDL::Demos::Cartography_Lighting

PDL::Demos::Cartography_Thunderstruck

Reading on Naming Modules Re: RFC: Automatic logger module Re^2: Naming a module that handles SIP2 (library protocol stopwords) Re^3: RFC: nicer subs with GetOptionsFromArray from Getopt::Long ( api design )

The point of my post isn't one demo. The module-names of the existing demos aren't really visible, instead the interface is roughly:

$ perldl
perlDL shell v1.357
[snip]
Type 'help' for online help
Type 'demo' for online demos
Loaded PDL v2.077 (supports bad values)

Note: AutoLoader not enabled ('use PDL::AutoLoader' recommended)

pdl> demo
Use:
   demo pdl         # general demo
   demo 3d          # 3d demo (requires TriD with OpenGL or Mesa)
   demo 3d2         # 3d demo, part 2. (Somewhat memory-intensive)
   demo 3dgal       # the 3D gallery: make cool images with 3-line scr
+ipts
   demo 3dtk        # Tk graphics (requires Tk)
   demo bad         # Bad-value demo (Optional: PGPLOT)
   demo cartography # Cartographic projections (Req.: PGPLOT)
   demo gnuplot     # Gnuplot graphics
   demo pgplot      # PGPLOT graphics output
   demo pgplotOO    # PGPLOT OO interface
   demo transform   # Coordinate transformations (Req.: PGPLOT)

pdl>
[download]

The point of my post was about a new PDL capability of live updating from (in this case) a websocket. The naming of a demo module for that is not something I was asking for help on ;-)

However, while it's not really entirely a Cartography thing (it's as much a 3D, and also live-updating thing - the mash-up/synergy are equally what I want to show off), the name "Thunderstruck" is so good it will definitely be involved - thank you!