Excellent news! 
I really understand, so for me it’s definitely not a problem, but not everyone is enough patient and understanding or they just don’t have a knowledge about possible vacations and other things. Called update because I’m interested, but also to avoid such topics:
Having in mind this net time I believe it would be worth to add just a few words on top of readme like:
I’m rewriting project to version
0.2.0this summer. Therefore below roadmap is outdated.
btw. If you would have a complete guide of how to make hologram app feel free to ping me here. I can’t say how it would be in future, but one thing I’m sure about is that at least I would like to give it a try, search for potential edge cases and give my suggestions.
It would be amazing if client would have 2 states. One accessible only on single page (let’s call it page_state) and other accessible on all pages (let’s call it state). For example changing language or theme could be easily done on client and should be shared on every page unlike counter in example.
defmodule MyPage do
use Hologram.Page
route "/my-page-path"
def init(_params, _conn, state) do
initial_page_state = %{count: 0}
{initial_page_state, state}
end
def template do
# …
end
def action(:change_language, params, page_state, state) do
{page_state, put(state, lang, params.lang))
end
def action(:increment, params, page_state, state) do
{put(page_state, :count, page_state.count + params.by), state)
end
def command(:log_in, params, session) do
# log in
{:logged_in, Map.put(session, :current_user, current_user)}
end
end
I’m not really sure if bundling is needed at all. I would say that you could do one much simpler thing i.e. add a hologram command to cache specific page i.e. the user clicks on some button to make sure data would be available also offline and the app literally do a simple loop calling just one command:
# call hologram command
required_offline_pages = [IndexPage, ShowPage]
Enum.map(required_offline_pages, &send_cache_hologram_command/1)
# call app command
required_offline_data = [Blog,Post]
Enum.map(required_offline_data, &send_fetch_all_command/1)
# this way in let's say IndexPage we could replace such a custom code
data = send_fetch_all_command(Blog.Post)
# to for example
data = send_fetch_all_command(Blog.Post, fallback: &read_from_cache/1)
Since as you said once the page is loaded it works offline, so you already have code to load specific page and call init. If so you can just use said code, but without calling page init. Do you think it’s lots of work this way?
