The remote control interface still uses the ancient popup confirmation reconnection logic. Change it to automatic and add a clear visual indicator when the connection is down so that the operator knows it.

Schedule next up slide should be unpublished after the last item is reached.

https://github.com/iskcrew/isk/blob/master/inkscape/isk-output.py#L101 is the culprit.

protocol mismatch between components.

It would be really nice to be able to play some videos via the displays. This would be quite nice for ads.

Assembly hasn't used this functionality for a long while and it has apparently been broken.

At Assembly Summer 2017 most of my on-event time was spent on hunting memory leaks. So we need to write some performance testcases to catch the problems and possible performance issues.

This is pretty much needed for issues #8 and #18

Currently when the current event changes the displays retain their (now invalid) presentations and other status information. This can be quite confusing.

It would probably be best to clear the presentations and other state info from the displays on event change.

A slide generator similar to the prizegroup logic for any template slide, with one place to fill fields for multiple slides with same template.

Earlier refactoring missed a create callback: https://github.com/iskcrew/isk/blob/master/app/models/slides/http_slide.rb#L29 and thus broke creating httpslides.

Assembly event currently uses several glue-scripts to import photos and schedules from other systems. Giving the scripts as examples would be nice.

There is multiple buttons with label "(i)Details" in user management page.

The inkscape 0.92 in stretch has once again changed the handling of multiline text.
If there are both sodipodi:role=line and dy=1em attributes on a given tspan the line spacing gets all kinds of wonky.

Will probably need to bite the bullet and just split the html preview svg generation from the inkscape svg generation, or just do Something when converting from simpleslide to inkscape slide.

A hacky and dirty fix is to comment out line https://github.com/iskcrew/isk/blob/master/app/models/slides/simple_slide.rb#L218

Currently displays waiting on a one slide in manual mode trigger the timeout warnings as they don't implement the websocket ping message.

A slide generator similar to the prizegroup logic for countdown slides "foo will start in 13 minutes" would be really nice.

It would be really nice to have a way for letting the displays pick a slide from a group of advertisements and choose a different slide from that group each time it is shown.

The second line of such field goes to top-left corner i.e. the svg coordinate 0,0....

On the current gemset and ruby 2.3.0 and 2.3.3 the puma process leaks memory significantly. Slides#show page appears to be ok, but slides#index and groups#index leak badly.

Need to write performance tests to catch such issues in the future.

They need to be manually baked from console, find out why.

Need to fix it to redirect back to users#index.

Create a system which can be used to hide / publish slides based on timers, either datetime or after a timer has run out.

This depends on refactoring the background jobs process to be more modular

I suspect that even when defining different databases in the 01-redis.rb initializer for testing and other environments something still leaks into tests. As even running tests with the same random seed the results for redis message counts vary.

Need to take a closer look into the test-redis-helper and the redis configuration

It would be nice to have a functionality to code ISK-slides with HTML and CSS, so that you could possibly have some extra opportunities and more interesting slides, for example TG's. It would also be nice, that in a HTML/CSS slide there would be a button to run the slides CSS animations whenever you want.

Current database.yml.example could list more options that user can specify. Right now it's up to Google and right words to get more complex DB configurations in (as in non-ident auth, other server etc...)

I'd propose that at a minimum, database.yml.example should contain these fields (or something similar):

env-keyword:
  <<: *defaults
  database: isk
  # host: localhost
  # username: isk
  # password: changeme

Document the compiling, setup and use of WPE with ISK.

It would be nice to have a functionality to code ISK-slides with HTML and CSS, so that you could possibly have some extra opportunities and more interesting slides, for example TG's. It would also be nice, that in a HTML/CSS slide there would be a button to run the slides CSS animations whenever you want.

It would be nice to have a clean way of opening a connection to each raspberry pi display and monitoring their memory usage and temperature. Also graph this with rrd.

The cashier gem isn't maintained anymore and it blocks migration to rails 5

Current behavior:

• Events are dropped from nextup slide after 15min from their start time.
• Exception for this is the last event of the schedule, which is never cleared, and slide remains public.

Proposed behavior:

• Add "Now playing" event on top of the list with start time dropped. Now playing event is replaced when event end time is reached or next event has started.
• Add customizable message for schedule, to be displayed on nextup slides when all events have ended. Alternatively just unpublish the empty nextup slide automatically.

These can also be added as user selectable alternatives, as the current behavior is actually working for schedule containing multiple locations mixed up. The proposed behavior would be better for schedule with only one location and events never overlap.

At least some conversions (template -> inkscape slide, others?) are broken.

Add functionality so that we can use transparent slides and a background video file for displays to spice things up.

Kelmuille olisi hyvä toteuttaa kommentointimahdollisuudet, ja jos mahdollista pääsy tuohon osioon olisi hyvä olla vapaampi kuin kumpikaan nykyinen tunnus. ehkä jopa pelkällä basicauthilla ja kommenttiin pitäisi jättää nimimerkki...

Kommentit voisi näkyä jonkun pienen ikonin kautta kaikissa kalvonäkymissä (joissa ne napit kalvokuvan alla) ja ikonissa numero kommenttien määrästä..

Currently slide cloning functions need a good looking into them. They work, but the code is ugly and way more complicated it needs to be.

Currently if a large number of slides get accidentally added to a override queue on a display removing them needs a non-ajax operation per slide on the web gui.