path: root/2023/captions/emacsconf-2023-one--oneel-the-static-site-generator-for-emacs-lisp-programmers--tony-aldon--answers.vtt

WEBVTT


00:00:00.459 --> 00:00:05.460
[Speaker 0]: So, will you, when I'm looking at my,

00:00:06.279 --> 00:00:08.480
the other screen, I don't see the chat,

00:00:08.480 --> 00:00:10.380
so maybe someone can tell me.

00:00:11.259 --> 00:00:12.360
[Speaker 1]: It's fine, don't worry about it,

00:00:12.360 --> 00:00:14.320
and we are live. So hi again everyone.

00:00:15.060 --> 00:00:16.140
Hi Tony, how are you doing?

00:00:17.040 --> 00:00:18.420
[Speaker 0]: Really well, and you?

00:00:19.440 --> 00:00:21.040
[Speaker 1]: I am doing fantastically,

00:00:21.380 --> 00:00:23.460
as fantastically as I can be doing,

00:00:24.099 --> 00:00:25.820
having to put out fire in the background

00:00:30.140 --> 00:00:30.640
[Speaker 0]: Cool!

00:00:25.840 --> 00:00:31.520
[Speaker 1]: during MaxConf. But I'm doing great! Alright,

00:00:31.640 --> 00:00:34.900
Let me just try to set up everything so that

00:00:34.960 --> 00:00:37.260
I can show the questions and all this.

00:00:37.260 --> 00:00:38.600
Do you mind if I read you the question?

00:00:38.600 --> 00:00:39.960
It might be a little more interactive and

00:00:39.960 --> 00:00:42.760
this way you can focus on either presenting

00:00:42.800 --> 00:00:43.760
stuff on your end.

00:00:44.059 --> 00:00:48.680
[Speaker 0]: Yes, tell me what are the questions and what

00:00:48.680 --> 00:00:50.940
to do and I will do that.

00:00:53.420 --> 00:00:56.400
[Speaker 1]: Okay great so what I'll do,

00:00:56.400 --> 00:00:58.580
I'll invite people to go to the pad and ask

00:00:58.580 --> 00:01:00.060
questions because it was a very interesting

00:01:00.060 --> 00:01:01.480
talk and I'm sure you have plenty of

00:01:01.480 --> 00:01:03.460
questions but I only see 1 right now.

00:01:03.460 --> 00:01:05.360
Do we have people on BigBlueButton?

00:01:05.640 --> 00:01:08.580
Yes we do have people joining right now.

00:01:11.000 --> 00:01:12.620
So reading the first question then.

00:01:12.620 --> 00:01:14.380
So what's the main motivation for this new

00:01:14.380 --> 00:01:16.100
package? I used to use org.yugo

00:01:16.280 --> 00:01:18.340
and use GitHub Actions to build a blog.

00:01:18.340 --> 00:01:20.600
So can you go in a little bit of details on

00:01:20.600 --> 00:01:21.100
this?

00:01:21.540 --> 00:01:25.780
[Speaker 0]: Yes, OK. So the main goal,

00:01:30.900 --> 00:01:33.570
I didn't want to have,

00:01:33.805 --> 00:01:37.440
to, I will push that here.

00:01:38.040 --> 00:01:44.940
So my goal was to not have to rely on another

00:01:45.060 --> 00:01:49.920
static site generator to produce my website.

00:01:49.920 --> 00:01:54.780
So if you use a Yugo, that means that you

00:01:54.780 --> 00:02:01.060
take, so this is the website that we've seen

00:02:01.960 --> 00:02:07.880
in the talk, this 1. And I didn't want to

00:02:07.880 --> 00:02:13.320
have to use a piece of software in Emacs that

00:02:13.320 --> 00:02:16.960
translate to some other files to be feed to

00:02:16.960 --> 00:02:20.680
another statistic generator because this way

00:02:20.680 --> 00:02:23.680
I have 2 things to understand.

00:02:23.680 --> 00:02:26.620
I have to understand how that software

00:02:26.780 --> 00:02:32.440
translates my files into the other files and

00:02:32.440 --> 00:02:36.960
then I have to understand how Hugo works.

00:02:37.060 --> 00:02:39.480
So if I want to change something I need to

00:02:39.480 --> 00:02:43.660
understand Hugo. So at some point I need to

00:02:43.660 --> 00:02:46.200
work with Hugo. So if I need to work with

00:02:46.200 --> 00:02:49.700
Hugo, maybe I can work with it directly.

00:02:51.800 --> 00:02:56.600
And I wanted also something that was purely

00:02:56.960 --> 00:03:03.080
Emacs-centric and working on it,

00:03:03.700 --> 00:03:05.560
I found out about that solution.

00:03:05.600 --> 00:03:10.740
And I wanted also something that we have only

00:03:11.780 --> 00:03:15.140
1 file that have all the entries.

00:03:15.560 --> 00:03:18.620
And when I thought about that,

00:03:19.140 --> 00:03:22.720
finally I found a way that maybe we can just

00:03:22.720 --> 00:03:30.360
use 1 or 3 to pass it the information of the

00:03:30.360 --> 00:03:33.405
website. And if you look,

00:03:33.405 --> 00:03:37.660
If you just try to work with Gatsby,

00:03:37.920 --> 00:03:40.020
Ugo or all those websites,

00:03:40.940 --> 00:03:45.680
when you start, you download 10,

00:03:46.240 --> 00:03:52.280
20, 30, thousand for hundreds of dependencies

00:03:53.440 --> 00:03:59.620
to do. Just to me, I'm a small guy and I just

00:03:59.620 --> 00:04:02.720
want to have some documentation on the

00:04:02.720 --> 00:04:05.200
website like this 1. It just,

00:04:05.460 --> 00:04:08.980
it shouldn't need that much of a dependency.

00:04:09.160 --> 00:04:11.460
And if you look at the website,

00:04:11.460 --> 00:04:13.180
if you want to hack on something,

00:04:13.540 --> 00:04:17.320
you need a lot of to understand how the

00:04:17.320 --> 00:04:19.459
config files work. So you need to,

00:04:19.459 --> 00:04:21.060
how does it work this config file?

00:04:21.060 --> 00:04:23.320
But I want, it's always happened that you

00:04:23.320 --> 00:04:26.420
want to add 1 thing or to add that things.

00:04:26.420 --> 00:04:27.760
What do you have to do?

00:04:27.780 --> 00:04:30.340
You have to, you can't because it's not

00:04:30.340 --> 00:04:34.040
offered by the configuration file.

00:04:34.380 --> 00:04:37.980
With that solution that I built for me first,

00:04:38.920 --> 00:04:41.580
I don't care if I need something else.

00:04:42.020 --> 00:04:47.600
I just have to go in that file.

00:04:49.840 --> 00:04:52.440
It doesn't need to be that file because as I

00:04:52.440 --> 00:04:55.980
am in Emacs if the render functions are

00:04:56.120 --> 00:04:58.940
already evaluated they exist and I can use it

00:04:58.940 --> 00:05:02.520
but I just have to change that file so if I

00:05:02.520 --> 00:05:07.860
want something more I just I go there let's

00:05:07.860 --> 00:05:10.920
say so does it answer the question or I

00:05:10.920 --> 00:05:12.780
continue to show something?

00:05:14.320 --> 00:05:16.060
[Speaker 1]: It's up to you, I think you are answering the

00:05:16.060 --> 00:05:17.600
question. I think you veered off a little bit

00:05:17.600 --> 00:05:19.940
from just why not you go but then you kind of

00:05:19.940 --> 00:05:21.840
redid part of your presentation to justify

00:05:23.480 --> 00:05:26.360
[Speaker 0]: own system. But stop me if I go because I

00:05:26.360 --> 00:05:29.920
used to want to show more things than what

00:05:29.920 --> 00:05:30.900
there is in the question.

00:05:21.940 --> 00:05:32.080
[Speaker 1]: why you had to roll your Yeah that's fine.

00:05:32.080 --> 00:05:33.340
Just for people who do not know,

00:05:33.340 --> 00:05:35.500
we tend to restrict speakers when they submit

00:05:35.500 --> 00:05:36.620
a presentation. We tell them,

00:05:36.620 --> 00:05:39.000
oh, you can do a flash talk in 10 minutes or

00:05:39.000 --> 00:05:41.100
a bit of a longer talk in 20 minutes or 40

00:05:41.100 --> 00:05:43.180
minutes. And usually, because we have a lot

00:05:43.180 --> 00:05:46.260
of speakers, we have to kind of coerce people

00:05:46.260 --> 00:05:48.340
into going to shorter formats and sometimes

00:05:48.340 --> 00:05:50.260
it's a lot about killing your darlings.

00:05:51.100 --> 00:05:52.360
But just to reassure you,

00:05:52.360 --> 00:05:54.560
we're just about to go on a launch break in

00:05:54.560 --> 00:05:56.840
about 10 minutes, so you've got the full 10

00:05:56.840 --> 00:05:58.320
minutes to use however you want,

00:05:58.320 --> 00:05:59.340
but I'll just tell you,

00:05:59.340 --> 00:06:01.080
you have a lot of questions so you might want

00:06:01.080 --> 00:06:03.400
to perhaps move on to the next 1 as soon as

00:06:03.400 --> 00:06:04.060
you can.

00:06:04.540 --> 00:06:08.240
[Speaker 0]: Yes okay so tell me the next 1 and if people

00:06:08.940 --> 00:06:13.160
want to stay more I can also stay more.

00:06:14.240 --> 00:06:17.220
Right. I understand if people need to go to

00:06:17.220 --> 00:06:19.020
lunch, they can, but people that want to

00:06:19.020 --> 00:06:20.240
stay, if it's possible,

00:06:20.340 --> 00:06:22.860
I'm here to answer any question.

00:06:24.060 --> 00:06:26.240
[Speaker 1]: Splendid. All right, so moving on to the next

00:06:26.240 --> 00:06:29.180
question. Is it possible to include the

00:06:29.180 --> 00:06:31.560
include org tag to add content from other

00:06:31.560 --> 00:06:33.620
files. Do you see what I'm talking about?

00:06:35.200 --> 00:06:39.060
[Speaker 0]: Yes, so it's not included.

00:06:39.380 --> 00:06:45.240
So the idea was really to have only 1 file

00:06:45.720 --> 00:06:49.760
and have no options. So if you look at the,

00:06:49.760 --> 00:06:52.240
let's go into, so the answer is no,

00:06:52.240 --> 00:06:56.320
but if you want, you can write the code that

00:06:56.320 --> 00:07:00.520
do it. But let's just go into one.n,

00:07:02.280 --> 00:07:07.900
so that files. So this is the files where you

00:07:07.900 --> 00:07:11.440
have everything, and there is only 2

00:07:11.440 --> 00:07:13.980
dependencies. Maybe we can see that at the

00:07:13.980 --> 00:07:18.080
top so which are htmlis on the Jack and the

00:07:18.080 --> 00:07:19.840
other are Augment. So for me,

00:07:19.840 --> 00:07:21.760
they're not dependencies because they come

00:07:21.820 --> 00:07:25.440
with Emacs. But the question is,

00:07:25.440 --> 00:07:27.440
can I add other things?

00:07:27.440 --> 00:07:31.640
If you look at that, you don't see the orange

00:07:31.640 --> 00:07:33.220
color which are viable,

00:07:33.600 --> 00:07:38.080
it's because I didn't want any configuration

00:07:38.440 --> 00:07:41.060
nor option. So there is no,

00:07:41.960 --> 00:07:45.660
if you think about, you are used to use org

00:07:45.660 --> 00:07:49.540
export normally and to use all the options

00:07:49.540 --> 00:07:52.000
that are possible on all the things they are

00:07:52.000 --> 00:08:00.600
not included. You can add them because when

00:08:04.900 --> 00:08:06.500
you are in a render function.

00:08:07.060 --> 00:08:08.940
So this is the render function that I showed

00:08:08.940 --> 00:08:11.980
in the theme. You have a page tree so you

00:08:11.980 --> 00:08:18.358
have the information but in the global I

00:08:18.358 --> 00:08:20.440
think, yes in global, you can pass anything

00:08:21.020 --> 00:08:24.720
you want and if you want you can pass the

00:08:24.720 --> 00:08:27.540
parse tree of the whole file.

00:08:28.080 --> 00:08:30.840
So if you pass the parse tree of the whole

00:08:30.840 --> 00:08:34.580
file, what you can do is that you can get it

00:08:35.400 --> 00:08:38.659
there. So I don't have it right now,

00:08:38.659 --> 00:08:43.980
but you might have your include stuff and you

00:08:43.980 --> 00:08:48.040
get it with a node property that target

00:08:48.580 --> 00:08:50.940
something in the global variable.

00:08:50.940 --> 00:08:54.740
So if we look just to be short but those 3

00:08:55.320 --> 00:08:57.180
parts, the first 1 is page tree.

00:08:57.180 --> 00:08:59.160
So it's this page that you are on the right,

00:08:59.160 --> 00:09:02.220
pages are a list of all the pages and global

00:09:02.840 --> 00:09:06.240
is something that you can set and reset once

00:09:06.580 --> 00:09:10.840
and you have the whole part street.

00:09:10.840 --> 00:09:13.400
So anything that you add in your op-files

00:09:15.040 --> 00:09:16.840
could go in global if you want,

00:09:16.840 --> 00:09:18.060
but it's not included.

00:09:20.600 --> 00:09:23.140
[Speaker 1]: All right. I think that's also answering the

00:09:23.140 --> 00:09:24.840
question. Can this generate a single file

00:09:24.840 --> 00:09:26.420
from different sources like blog.org,

00:09:26.880 --> 00:09:28.820
videos.org? I think you've just answered

00:09:30.040 --> 00:09:31.280
[Speaker 0]: Yes, I think yes.

00:09:28.820 --> 00:09:32.660
[Speaker 1]: this, right? Right. Okay.

00:09:32.660 --> 00:09:34.340
So moving on to the other question.

00:09:34.660 --> 00:09:37.200
Do you have pre-made templates already along

00:09:37.200 --> 00:09:38.820
with the 1.el package?

00:09:41.680 --> 00:09:47.940
[Speaker 0]: So, yes and no. So, The answer is if we go to

00:09:49.960 --> 00:09:55.520
1.n, so this file, so the first are blah,

00:09:55.520 --> 00:10:01.780
blah, blah. How it works,

00:10:01.780 --> 00:10:06.480
so, okay, so you have the 1-hocs,

00:10:07.200 --> 00:10:11.980
which is what can translate the org parse

00:10:11.980 --> 00:10:16.180
tree into HTML. So this is for the content of

00:10:16.260 --> 00:10:18.140
each page. So this is very useful.

00:10:18.480 --> 00:10:22.660
Then we have a bunch of functions that help

00:10:22.660 --> 00:10:24.360
to render the function,

00:10:26.040 --> 00:10:30.260
each page. And you have a bunch of...

00:10:31.360 --> 00:10:33.920
Everything that starts with dash default is a

00:10:33.920 --> 00:10:36.140
render function. So there's no template,

00:10:37.480 --> 00:10:40.520
but each page that if you want,

00:10:42.240 --> 00:10:46.400
so that 1, the home, you can use 1 default

00:10:46.400 --> 00:10:48.620
home. So, if you want to list the page,

00:10:48.740 --> 00:10:53.220
you have that 1. For a page with no table of

00:10:53.220 --> 00:10:55.840
content, you use that thing.

00:10:55.840 --> 00:10:58.260
And if you go back to be short,

00:10:58.260 --> 00:11:02.660
if we go there, I put this like that.

00:11:03.900 --> 00:11:09.880
So this that we see here is the first inline

00:11:09.960 --> 00:11:14.440
of 1.org. By the way, it doesn't have to be

00:11:14.440 --> 00:11:17.120
called 1.org. It's just as you want,

00:11:17.160 --> 00:11:19.380
but maybe we can call it.

00:11:20.740 --> 00:11:23.000
So default, what was the other 1?

00:11:23.220 --> 00:11:28.280
Default with sidebar. Or is it default with

00:11:28.280 --> 00:11:30.080
sidebar or default? Yes,

00:11:30.080 --> 00:11:35.380
with sidebar. Sidebar,

00:11:36.400 --> 00:11:37.740
if it's worked correctly.

00:11:39.140 --> 00:11:46.620
Okay, so, okay, so I don't know why the CSS

00:11:46.760 --> 00:11:49.700
is not working correctly.

00:11:50.740 --> 00:11:53.860
[Speaker 1]: It's okay. It wouldn't be a live demo without

00:11:53.860 --> 00:11:55.440
problems occurring at some point.

00:11:55.440 --> 00:11:55.940
Okay.

00:11:56.980 --> 00:12:01.240
[Speaker 0]: But so maybe we can use this 1.

00:12:02.940 --> 00:12:06.980
Or we stuck. So we are going to use this 1,

00:12:06.980 --> 00:12:16.020
we've talked this 1, but maybe better in this

00:12:16.020 --> 00:12:20.240
1 that add something. So we build it again

00:12:20.340 --> 00:12:32.180
and now, oh, come on. We have it and we have

00:12:32.180 --> 00:12:36.140
the, sorry, if we have just default,

00:12:37.820 --> 00:12:41.120
we rebuild and now this is the default layer

00:12:41.120 --> 00:12:44.360
that if we do with table of content,

00:12:46.060 --> 00:12:48.580
you have it, you have the default content.

00:12:48.620 --> 00:12:53.640
So how to change, and they are not template.

00:12:53.940 --> 00:12:57.760
They are render functions that takes your

00:13:00.300 --> 00:13:05.720
page as a tree and render HTML string.

00:13:06.260 --> 00:13:09.200
So you can build any function that you want.

00:13:10.600 --> 00:13:12.280
So yes, I think that answers the question.

00:13:12.280 --> 00:13:16.400
There is no template like in other systems.

00:13:17.780 --> 00:13:18.920
[Speaker 1]: Cool, that makes sense.

00:13:19.020 --> 00:13:21.000
We have 2 more questions and then we'll need

00:13:21.000 --> 00:13:22.200
to go on a lunch break.

00:13:22.200 --> 00:13:23.740
I don't see anyone join the room.

00:13:23.740 --> 00:13:25.640
Remember, Tony has said that he would be

00:13:25.640 --> 00:13:27.500
willing to answer more questions during the

00:13:27.500 --> 00:13:29.120
lunch break, perhaps because it's not lunch

00:13:29.120 --> 00:13:30.980
break for you. Are you in Europe right now?

00:13:32.360 --> 00:13:34.600
So that's why for us, also for me it's very

00:13:34.600 --> 00:13:37.660
dark, but it's not lunch break for us,

00:13:37.660 --> 00:13:39.440
it's going to be dinner break soon actually.

00:13:31.280 --> 00:13:42.840
[Speaker 0]: Yes. Yes, exactly, so I'm just,

00:13:44.020 --> 00:13:44.700
I'm okay.

00:13:45.580 --> 00:13:49.200
[Speaker 1]: Right, Okay, so moving on to 1 of the last 2

00:13:49.200 --> 00:13:51.680
questions. What additional features are there

00:13:51.680 --> 00:13:53.660
that you would like to add to 1.EL

00:13:53.960 --> 00:13:54.780
in the future?

00:13:56.120 --> 00:14:00.440
[Speaker 0]: Yes, there's only 1, which is a full text

00:14:00.560 --> 00:14:05.500
search done in a simple way.

00:14:06.540 --> 00:14:10.020
So I don't meet what simple way means,

00:14:10.320 --> 00:14:12.380
but when I see something complicated,

00:14:12.620 --> 00:14:15.140
it doesn't enter in 1 to me.

00:14:15.400 --> 00:14:18.840
So, but really, if you see that,

00:14:19.120 --> 00:14:22.260
I would like to have some way.

00:14:22.300 --> 00:14:25.080
So, this is the documentation and I would

00:14:25.080 --> 00:14:27.480
like to have some way to just have another

00:14:27.500 --> 00:14:30.740
function because we are not talking about

00:14:31.300 --> 00:14:33.800
those websites on the 1.L.

00:14:34.440 --> 00:14:39.520
It's not made for a big company or of your

00:14:39.520 --> 00:14:42.440
things, it's just for a random guy that have

00:14:42.440 --> 00:14:46.200
a blog or a few blogs and If you are a great

00:14:46.200 --> 00:14:52.280
blogger, maybe you are going to write 100 or

00:14:53.040 --> 00:14:57.240
200 or 300 pages in many years.

00:14:57.240 --> 00:15:00.060
So this enter in that category.

00:15:00.060 --> 00:15:03.580
So it's small. So I think it can,

00:15:04.080 --> 00:15:07.580
we could find a way to make a full text

00:15:07.580 --> 00:15:10.160
search. And that is simple.

00:15:10.240 --> 00:15:12.780
I don't need to, to go with,

00:15:13.520 --> 00:15:16.620
with solution like Algolia that is,

00:15:16.620 --> 00:15:17.900
that works super fine.

00:15:17.900 --> 00:15:21.100
But this is something that I don't control

00:15:21.600 --> 00:15:26.200
and I have to give them the data and I'm not

00:15:26.200 --> 00:15:29.320
against that but it's just that I think with

00:15:29.320 --> 00:15:32.800
a bit of work something can be done with full

00:15:32.800 --> 00:15:35.600
textile. But this is the only thing that I

00:15:35.600 --> 00:15:36.980
would like to add.

00:15:38.720 --> 00:15:41.300
[Speaker 1]: Very clear answer. Next question.

00:15:41.580 --> 00:15:44.380
Can you create navbars on a website and fancy

00:15:44.380 --> 00:15:46.380
things like carousels using 1.EL?

00:15:46.800 --> 00:15:48.220
Now carousels is just,

00:15:48.260 --> 00:15:51.820
I think, a fancy way to display pictures and

00:15:51.820 --> 00:15:53.800
please correct me whoever asked this

00:15:53.800 --> 00:15:55.440
question. Otherwise I see you taking notes

00:15:55.440 --> 00:15:56.820
for the answers, thank you very much.

00:15:56.820 --> 00:15:58.740
But if you could specify maybe carousels so

00:15:58.740 --> 00:16:01.900
that Tony and I may get a better idea.

00:16:01.920 --> 00:16:03.340
But still, first part of the question,

00:16:03.340 --> 00:16:04.940
can you create navbars on a website?

00:16:05.980 --> 00:16:10.860
[Speaker 0]: Yes. So if, for instance,

00:16:10.900 --> 00:16:14.600
you see there, to me, it's not a,

00:16:14.600 --> 00:16:19.040
it's a navbar. So you already have it.

00:16:19.860 --> 00:16:23.080
I didn't show that in the talk,

00:16:23.080 --> 00:16:27.440
but the CSS for the default function that

00:16:27.440 --> 00:16:31.100
works is responsive. So,

00:16:31.720 --> 00:16:34.400
out of the box, if you are using something,

00:16:34.600 --> 00:16:37.540
you will have an app bar done for you with

00:16:37.540 --> 00:16:38.680
all the pages that you have.

00:16:38.680 --> 00:16:40.240
So, if we go to install,

00:16:40.920 --> 00:16:44.900
we have that. And if we no longer have that,

00:16:44.900 --> 00:16:49.960
we have that sidebar there.

00:16:50.220 --> 00:16:51.840
And how it's done. So,

00:16:52.660 --> 00:16:56.380
the same way. I like simple fields that are

00:16:56.380 --> 00:16:58.580
flexible and I didn't want configuration

00:16:58.860 --> 00:17:01.280
because if you want to write the code to

00:17:01.280 --> 00:17:03.480
change something you just have to write code.

00:17:03.480 --> 00:17:05.720
So any function, render function,

00:17:05.859 --> 00:17:08.760
is yours. So you can do whatever you want and

00:17:08.760 --> 00:17:11.520
you enter the html that you want to render.

00:17:11.520 --> 00:17:17.800
So let's see how do we get that navigation

00:17:17.920 --> 00:17:20.920
bar that we have when we do that this is a

00:17:20.920 --> 00:17:23.079
CSS stuff. But when we click,

00:17:23.099 --> 00:17:25.819
this is a JS stuff that,

00:17:27.040 --> 00:17:32.320
so let's go to one.l And maybe this is a

00:17:32.320 --> 00:17:35.660
sidebar. Why that function because,

00:17:36.300 --> 00:17:40.360
okay. So when that function,

00:17:40.680 --> 00:17:45.340
so 1 default sidebar is 1 that is used to do

00:17:45.340 --> 00:17:47.120
some of the things at some point,

00:17:47.120 --> 00:17:52.120
what we return is a JackHTML that take a data

00:17:52.120 --> 00:17:54.340
structure and return a string.

00:17:54.340 --> 00:17:57.280
So this is your HTML. So you can see at the

00:17:57.280 --> 00:18:00.780
top you have the end, then you have the body,

00:18:01.120 --> 00:18:06.080
and if we go at the end we can add a script

00:18:06.080 --> 00:18:08.640
thing. So what we've seen with the sidebar

00:18:08.920 --> 00:18:11.820
it's just that much line of JavaScript.

00:18:11.920 --> 00:18:17.440
So this is the only JavaScript that there is

00:18:17.440 --> 00:18:23.640
to get what we have here when we do that.

00:18:25.360 --> 00:18:29.500
So you can add whatever you want.

00:18:29.500 --> 00:18:33.420
It's code and you're the master of that code.

00:18:35.280 --> 00:18:38.600
[Speaker 1]: Splendid, great. So to specify the carousel

00:18:38.800 --> 00:18:39.860
stuff that we mentioned before,

00:18:39.860 --> 00:18:42.520
it's pictures rolling or sliding from 1 to

00:18:42.520 --> 00:18:44.620
the other. It's kind of like having a

00:18:44.620 --> 00:18:47.540
gallery, imagine a fancy dynamic gallery

00:18:47.540 --> 00:18:48.740
where you can scroll pictures.

00:18:48.740 --> 00:18:50.220
Do you see what I'm talking about?

00:18:50.380 --> 00:18:53.600
[Speaker 0]: Yes, so that things would just be I think

00:18:53.620 --> 00:18:57.620
some javascript added somewhere and I can

00:18:57.620 --> 00:18:59.280
show you another website.

00:18:59.440 --> 00:19:04.200
So for instance if we go because there are

00:19:04.200 --> 00:19:08.160
not all the data of the website are not all

00:19:08.160 --> 00:19:10.140
public, but the website they are.

00:19:10.140 --> 00:19:12.020
So for instance, a mini-buffer,

00:19:14.480 --> 00:19:18.880
it's not a carousel, but at the home page,

00:19:19.140 --> 00:19:20.900
we can do whatever we want.

00:19:22.660 --> 00:19:24.560
Still those pages, still,

00:19:24.560 --> 00:19:28.980
this is only 1 file for each page.

00:19:28.980 --> 00:19:31.580
So if we click, we can get those things.

00:19:31.720 --> 00:19:33.140
It's just that when we,

00:19:33.420 --> 00:19:35.040
for the home page for instance,

00:19:35.860 --> 00:19:38.040
when we go back on that home page,

00:19:38.160 --> 00:19:40.580
we have the list at that point.

00:19:40.580 --> 00:19:45.360
So let's go back to that function that we're,

00:19:45.540 --> 00:19:47.740
so not that 1, maybe the 1,

00:19:47.740 --> 00:19:50.760
1 different, it's better because that 1 is

00:19:50.760 --> 00:19:52.980
simpler. So almost nothing happened.

00:19:53.620 --> 00:19:55.520
We have the list of the pages.

00:19:56.240 --> 00:19:59.680
So I can do whatever I want with that list.

00:20:00.360 --> 00:20:05.400
I can loop over and we can see that 1,

00:20:06.340 --> 00:20:08.600
that default home list of pages,

00:20:08.600 --> 00:20:10.060
so that list of the pages,

00:20:10.260 --> 00:20:12.160
and we see where is the list.

00:20:13.200 --> 00:20:16.160
Okay, so this is a, here we have a function

00:20:17.680 --> 00:20:21.100
that just, we want the pages,

00:20:21.100 --> 00:20:24.100
but I think we, but the home page,

00:20:24.620 --> 00:20:28.120
and we have that list,

00:20:28.300 --> 00:20:33.020
and then here we do that.

00:20:37.740 --> 00:20:40.460
And we get something listed,

00:20:40.680 --> 00:20:44.060
But then as you control everything that you

00:20:44.060 --> 00:20:51.820
do, you can pass any CSS class that you want

00:20:51.820 --> 00:20:53.620
to do those things. So,

00:20:53.620 --> 00:20:55.020
for instance, that div,

00:20:55.260 --> 00:21:00.660
add the class either. Yes,

00:21:00.660 --> 00:21:02.840
you can do. I don't remember the question,

00:21:02.840 --> 00:21:05.660
but I think I was answering the right 1.

00:21:05.860 --> 00:21:07.260
[Speaker 1]: No, no, you were answering it.

00:21:07.260 --> 00:21:09.720
It was about carousels and about having fancy

00:21:09.720 --> 00:21:11.720
display for image galleries.

00:21:11.720 --> 00:21:12.660
And I think you've answered.

00:21:12.660 --> 00:21:14.120
Basically, you just put your JavaScript,

00:21:14.160 --> 00:21:16.100
you embed it inside the code.

00:21:16.620 --> 00:21:17.120
[Speaker 0]: Exactly.

00:21:18.620 --> 00:21:20.220
[Speaker 1]: So, other question. Would there be an

00:21:20.220 --> 00:21:22.860
automated way to convert an existing HTML

00:21:22.860 --> 00:21:24.880
document into a JackHTML form?

00:21:28.180 --> 00:21:32.060
[Speaker 0]: Okay, so that 1, I don't have 1.

00:21:32.200 --> 00:21:35.580
It's another topic, but maybe there are some

00:21:35.660 --> 00:21:37.940
kind of session because some people that

00:21:37.940 --> 00:21:41.620
know, that are used to Lisp,

00:21:43.080 --> 00:21:45.580
common Lisp or Clojure or other,

00:21:46.300 --> 00:21:49.460
Jack-html, that function,

00:21:50.740 --> 00:21:53.680
is something classic, but I didn't find,

00:21:53.680 --> 00:22:00.840
So I wrote it because I didn't find it

00:22:00.840 --> 00:22:04.520
already done the way I want for Emacs.

00:22:06.040 --> 00:22:08.980
And this is something for E-cup closure.

00:22:09.640 --> 00:22:13.260
So really I take, it's not that I take my

00:22:13.260 --> 00:22:15.060
impression, just that when you have something

00:22:15.060 --> 00:22:20.140
that exists and you look at how it's done.

00:22:20.640 --> 00:22:22.720
So you have a eCup for Crusher,

00:22:25.160 --> 00:22:26.640
does the same thing that HTML.

00:22:26.660 --> 00:22:32.140
It's more that I do a Jack HTML do what eCup

00:22:32.440 --> 00:22:37.160
does, but maybe they do it a better way.

00:22:37.800 --> 00:22:41.600
So I think maybe in that community,

00:22:42.320 --> 00:22:46.320
it might already exist something that go from

00:22:46.320 --> 00:22:52.440
HTML to Jack. So you can see,

00:22:53.640 --> 00:22:56.620
is it big enough? I will make it big enough.

00:22:57.626 --> 00:22:59.060
[Speaker 1]: It's good enough, don't worry.

00:22:56.820 --> 00:23:01.420
[Speaker 0]: So if you see- So you have the hash HTML and

00:23:01.420 --> 00:23:04.200
you see those things. There are things that I

00:23:04.200 --> 00:23:05.460
couldn't do, for instance,

00:23:05.460 --> 00:23:09.280
for the ID, I couldn't use the hash in the

00:23:09.280 --> 00:23:14.760
name of, of how do we name that,

00:23:14.760 --> 00:23:18.480
of the keywords, because it's used for

00:23:18.480 --> 00:23:21.180
something else in a Emacs Lisp.

00:23:21.180 --> 00:23:25.020
So, I use... Anyway, so you see that you have

00:23:25.520 --> 00:23:30.260
that things but in Emacs we don't have the

00:23:30.260 --> 00:23:34.960
map with that syntax. We have a hash map but

00:23:34.960 --> 00:23:37.120
they are not with that syntax and I wanted

00:23:37.120 --> 00:23:46.080
that syntax so we use only list and Here we

00:23:46.080 --> 00:23:48.660
have an array with a hash map.

00:23:49.200 --> 00:23:52.120
So let me just say, so the question was,

00:23:52.360 --> 00:23:54.100
does it exist something?

00:23:55.240 --> 00:23:58.680
I think not, but it could be built or maybe

00:23:58.680 --> 00:24:01.600
exist for E-Cups, you are interested.

00:24:03.240 --> 00:24:04.860
[Speaker 1]: Okay, great. I think that answers the

00:24:04.860 --> 00:24:07.840
question perfectly. And our final question,

00:24:08.440 --> 00:24:12.160
does this or you use any other Emacs packages

00:24:12.240 --> 00:24:14.180
for your packages slash website,

00:24:14.840 --> 00:24:16.740
example, or publish? Like,

00:24:17.020 --> 00:24:17.960
rephrasing the question,

00:24:17.960 --> 00:24:20.820
do you use it for your own personal usage or

00:24:20.820 --> 00:24:22.320
do you interact with other packages?

00:24:24.120 --> 00:24:26.180
[Speaker 0]: I'm not sure I understand the question.

00:24:26.640 --> 00:24:28.960
Can you please repeat the question?

00:24:29.820 --> 00:24:32.460
[Speaker 1]: Yes, I will reread it as it is written and I

00:24:32.460 --> 00:24:34.760
will leave you interpret it however you want.

00:24:34.760 --> 00:24:39.220
Thank you. Does this or you use any other

00:24:39.220 --> 00:24:43.060
Emacs packages for your package slash website

00:24:43.840 --> 00:24:45.100
like org-publish?

00:24:46.620 --> 00:24:49.340
[Speaker 0]: No, no, no. I don't use nothing.

00:24:49.660 --> 00:24:54.640
I just accept dependency of 1.n.

00:24:57.660 --> 00:25:01.000
So, we are in 1.n and we go at the top and we

00:25:01.000 --> 00:25:03.980
see that those are the dependencies.

00:25:04.820 --> 00:25:09.520
I use nothing. So what I do is that I

00:25:09.520 --> 00:25:12.420
publish, I just generate the public

00:25:12.620 --> 00:25:15.040
directory. So if we go to public,

00:25:16.500 --> 00:25:18.240
this 1, no, I don't want this 1.

00:25:18.240 --> 00:25:23.240
I want to go to the website of the video.

00:25:23.620 --> 00:25:27.400
If we see here, everything is rendered in the

00:25:27.400 --> 00:25:36.360
public. Any services, if you use your own

00:25:37.380 --> 00:25:39.280
server and you save those files,

00:25:39.280 --> 00:25:40.460
you have your website.

00:25:40.580 --> 00:25:42.580
So I don't use anything else.

00:25:42.580 --> 00:25:49.700
I just git push and I'm using Netlify as a

00:25:49.700 --> 00:25:52.320
service to run to save my files,

00:25:52.580 --> 00:25:54.860
but you can use anything you want.

00:25:55.900 --> 00:25:58.620
Because your website is really what is into a

00:25:58.620 --> 00:26:00.460
public. So, this is another,

00:26:01.360 --> 00:26:03.340
It's not the concern of 1.L

00:26:04.860 --> 00:26:07.180
to answer. I'm not using org.publish.

00:26:08.960 --> 00:26:10.900
[Speaker 1]: Cool, great. Well, thank you.

00:26:10.900 --> 00:26:13.000
I think the question was also about other

00:26:13.000 --> 00:26:16.500
things, but I think If the person wants a

00:26:16.500 --> 00:26:18.340
more clear answer to their question,

00:26:18.820 --> 00:26:21.260
feel free to clarify the question and Tony

00:26:21.260 --> 00:26:22.960
might be able to answer it later on.

00:26:22.960 --> 00:26:24.220
Alright Tony, I think that's all the

00:26:24.220 --> 00:26:25.760
questions we had. Thank you so much for

00:26:25.760 --> 00:26:27.680
taking the time not only to present Adimax

00:26:27.680 --> 00:26:29.240
Kant, but also for answering all the

00:26:29.240 --> 00:26:30.460
questions people had.

00:26:31.220 --> 00:26:34.080
[Speaker 0]: Thank you to everybody participating,

00:26:34.540 --> 00:26:38.000
organizing and thank you for all those

00:26:38.000 --> 00:26:42.180
questions and you can send me any emails if

00:26:42.180 --> 00:26:45.120
you have a question and open the issues if

00:26:45.180 --> 00:26:47.720
it's not working the way it should work for

00:26:47.720 --> 00:26:49.840
you. Please send me those things.

00:26:49.840 --> 00:26:50.900
Thank you, everybody.

00:26:51.940 --> 00:26:54.260
[Speaker 1]: Splendid, thank you. And before,

00:26:54.280 --> 00:26:56.140
so right now we're gonna go on a lunch break.

00:26:56.140 --> 00:26:58.660
We'll be back in about 40 minutes for the

00:26:58.660 --> 00:27:01.240
talk called Emacs Turbocharges My Writing.

00:27:01.300 --> 00:27:02.540
And I will not tell you more.

00:27:02.540 --> 00:27:04.280
You can look at the talk page to see a little

00:27:04.280 --> 00:27:06.340
bit of a synopsis but otherwise keep the

00:27:06.340 --> 00:27:08.900
surprise. So have a good lunch or have a good

00:27:08.900 --> 00:27:11.760
dinner if you are in dinner-friendly times

00:27:11.880 --> 00:27:13.180
and I will see you afterwards.

00:27:13.180 --> 00:27:14.180
Thank you again, Tony.

00:27:14.860 --> 00:27:15.600
[Speaker 0]: See you.

00:27:17.960 --> 00:27:20.320
[Speaker 1]: All right. Let me just close everything.

00:27:29.080 --> 00:27:30.480
All right, got it. OK,

00:27:30.480 --> 00:27:31.400
so thank you so much, Tony.

00:27:31.400 --> 00:27:33.520
I just had to clear everything up on the

00:27:33.520 --> 00:27:35.240
stream. I'm going to need to...

00:27:36.160 --> 00:27:39.000
Sorry. I'm going to stop.