<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
On 2/22/24 10:58, José Marcio Martins da Cruz wrote:<br>
<blockquote type="cite"
cite="mid:7742673f-be6b-4f78-b83d-52bf077b9457@gmail.com">When I
go to a bookstore, sometimes I need to check if a book I'm
thinking to buy I don't have it already... ;-) So, the web pages
need to be consultable in a smartphone. <br>
<br>
<blockquote type="cite">I also thought to write a script to use
the data saved in Tellico (probably in CSV) to generate a static
website.... <br>
:) <br>
</blockquote>
<br>
A static site is better and easier to do. The only reason to use a
CMS software is to be able to render in a smartphone display. <br>
<br>
The interest of directly use the *.tc file instead of csv dump is
that you don't need to do manual operations like launching
tellico, dumping it and launching an external script to do the
job. If it's ok for you, why not ? <br>
</blockquote>
<br>
I do the same thing regarding checking my collection from stores. I
find a limited CSV export (visible fields only) w/ an app capable of
rendering CSV as a spreadsheet provides a better experience on my
phone. I periodically export my collections and have a sync client
on my phone that copies them to the phone for local viewing.<br>
<br>
It's not ideal, but best I could come up with. The (large) html
exports were slow to load, and searching more clunky than just
searching the CSV for whatever reason.<br>
<br>
Fingers crossed for a Tellico for Android at some point in the
future. :-)<br>
<br>
-- <br>
Jared Breland<br>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:jbreland@legroom.net">jbreland@legroom.net</a><br>
<a class="moz-txt-link-freetext" href="https://www.legroom.net/">https://www.legroom.net/</a><br>
<br>
<br>
</body>
</html>