The future of Logseq - Sneak peak at the DB Branch

Summary

この動画は、オープンソースのノートアプリLogseekの今後の開発方向性について解説しています。Logseekチームは、マークダウンファイルではなく新しいデータベース方式を採用する大規模な変更を準備しています。この変更により、ページプロパティやタグ、リレーションなどの高度な機能が実装され、アプリの安定性と速度が向上すると期待されています。また、データのエクスポート機能の改善やユーザーインターフェースの刷新なども見込まれており、Logseekの将来に向けた重要な一歩となりそうです。

Takeaways

• 📝 Logseekのコアは静止状態になっているが、これは大きな変更のための作業が裏で行われているためである。
• 🔧 この変更は、Logseekがデータを保存する方法を書き換えるものであり、マークダウンファイルに依存しないデータベースベースのアプローチに移行する。
• ⚡ この変更により、Logseekのパフォーマンス、安定性、メモリ管理が改善される見込みである。
• 🌐 新しいデータベース設計は、プロパティやタグを使ってデータを構造化し、階層化することを可能にする。
• 📂 これにより、ユーザーは独自のデータ構造を簡単に作成でき、より整理された形でデータを管理できるようになる。
• 🔄 新しいエンジンでは、マークダウン形式のエクスポートに加え、SQLiteデータベースのエクスポートも可能になる。
• ✏️ テンプレートやフォーマットのカスタマイズ機能が強化される予定である。
• 📆 プロパティを活用することで、カレンダービューなどの高度なビューを実現できるようになる可能性がある。
• ⌛ この変更は大規模であり、安定性とスピードの確保が課題となっている。
• 🚀 この変更が完了すれば、Logseekの機能拡張のペースが加速すると期待されている。

Q & A

LogseekのDBブランチの開発に時間がかかっている理由は何ですか?

Logseekのコアエンジンとバックエンドをゼロから書き直す大規模な作業が行われているためです。旧バージョンの制約を解消し、より堅牢で機能的なシステムを構築することが目的とされています。この作業は非常に複雑で大規模なため、長期間を要しています。

新しいDBバージョンではどのようなことができるようになる予定ですか?

新しいバージョンでは、タグやプロパティを使ってカスタムデータ構造を柔軟に構築できるようになります。また、リンクの作成、データのフィルタリング、クエリ機能の強化などが期待されています。さらに、スピードと安定性の改善、データのエクスポート機能の拡張も見込まれています。

新バージョンのデータ構造はどのようなものになるでしょうか?

データはSQLiteデータベースに保存され、1つのテーブルにIDとテキストフィールドを持ちます。テキストフィールドにはEDNデータ形式でデータが格納されます。これにより、メモリを大量に消費することなくデータにアクセスできるようになります。

新しいバージョンではインポート/エクスポートの機能が変更される予定でしょうか?

エクスポート機能はある程度変更される可能性があります。SQLiteデータベースのエクスポートや、より柔軟なマークダウンエクスポートなどの新機能が追加される見込みです。さらに、他のアプリとのデータのやり取りを容易にするためのインポート/エクスポートオプションの追加も期待されています。

タスクの管理方法は変更されますか?

タスク管理は、新しいプロパティベースのシステムに移行される見込みです。つまり、「タスク」もプロパティの1つとして扱われ、カスタマイズが可能になるでしょう。たとえば、優先順位やタスク量などの新しいプロパティを追加できるようになるかもしれません。

新バージョンはマークダウンファイルの扱い方に影響を与えますか?

ある程度影響があると考えられます。データはバックエンドのデータベースに保存されるため、マークダウンファイルの扱い方が変更される可能性があります。ただし、マークダウンのエクスポートオプションは残される見込みです。

現在のLogseekユーザーは、新バージョンに移行する際にデータを移行できますか?

はっきりとした詳細は明らかになっていませんが、データ移行の方法が用意される可能性は高いと考えられます。しかし完全な互換性は難しいかもしれず、ある程度の手作業が必要となる可能性もあります。

ユーザーインターフェースはどのように変更される予定でしょうか?

新しいデータ構造に合わせてユーザーインターフェースも大幅に変更される見込みです。プロパティの設定画面やデータビューアなどが刷新され、より直感的で使いやすいインターフェースになると期待されています。ただし、具体的な変更点については不明な部分が多く残されています。

このアップデートはLogseekの基本的な機能にどのような影響を与えますか?

メモの作成や編集、リンクの追加など、Logseekの基本的な機能は残される見込みです。しかし、それらの機能がどのように実装されるかは変更される可能性があります。全体としては、より堅牢で拡張性の高いプラットフォームへと進化することが期待されています。

新バージョンのリリース時期はわかりますか?

正確な時期は明らかにされていませんが、開発には相当な時間を要しており、まだ先の話になると考えられます。開発者らは新バージョンをしっかりと磨き上げてから公開する方針のようです。

Outlines

00:00

🔍 私のロックシークの将来についてのレビュー

この段落では、ロックシークの開発チームが大きな変更を行っていることを説明し、GitHubのDBブランチを見ることで、将来の変更の方向性を知ることができると述べています。また、この新しいバージョンをプレビューすることについて注意を促し、本番環境で使用しないよう警告しています。

05:02

🤔 ロックシークのバックエンドの課題と変更の必要性

ロックシークのバックエンドにはいくつかの課題があり、変更が必要であると説明しています。マークダウンファイルベースのデータ構造には制限があり、設計上の問題点を指摘しています。また、マークダウンを排除してデータベースバックエンドに移行することで、これらの問題が解決できると述べています。ただし、マークダウンをエクスポートできることが重要であると強調しています。

10:05

🏗️ エンジンの再構築の複雑さ

この段落では、ロックシークのエンジン(コア機能)を書き換えることの複雑さについて説明しています。既存の機能との下位互換性を維持しながら、より堅牢な基盤を構築する必要があります。また、一部のユーザーが新しい方向性に不満を持つかもしれないことを認識していることが述べられています。

15:06

🆕 新しいバージョンのロックシークの機能プレビュー

この段落では、新しいバージョンのロックシークの具体的な機能について説明しています。プロパティの設定、フィルタリング、グラフビューなど、様々な新機能が紹介されています。また、クイックでわかりやすい構造の構築方法を示しており、ロックシークの拡張性と柔軟性が高まることが期待されています。

20:07

✍️ 本の構造を作成するデモ

この段落では、実際に本の構造を作成するデモを通して、新しいロックシークの機能を具体的に示しています。本、著者、発売年などのプロパティを設定し、それらを関連付けていく過程が分かりやすく説明されています。このようにして、ユーザーがカスタマイズした構造を柔軟に構築できることが強調されています。

25:08

🚀 今後の展望と課題

最後の段落では、新しいバージョンのロックシークに対する今後の期待と課題について述べられています。安定性、速度、クエリオプション、テンプレートの改善、タスク管理の改良などが挙げられています。また、ロックシークがこれらの課題を乗り越えることで、大きな進化を遂げることが期待されています。

Keywords

💡データベース分岐

メインのLoglseekコードから分岐したコードベースのことです。ビデオでは、Logseekの将来の大規模な変更を具体化するために、開発者がこのデータベース分岐で作業していることが説明されています。この分岐では、マークダウンファイルではなく、SQLiteデータベースを使用してデータを保存することで、より堅牢でスケーラブルな基盤を構築しようとしています。

💡オープンソース

Logseekがオープンソースのプロジェクトであることが、ユーザーにとって有利な点が強調されています。オープンソースであるため、ソースコードを閲覧でき、開発の進捗状況を把握できます。また、本番環境に影響を与えずに開発版を試用できるというメリットもあります。

💡マークダウン

Logseekの現在のデータ保存形式であるマークダウンファイルには限界があることが指摘されています。マークダウンはテキスト書式用に設計されたものであり、ブロック構造やプロパティ、リンクなどの高度な機能を扱うには適しておらず、パフォーマンスの問題が生じがちです。そのため、新しいデータベース駆動型のアーキテクチャに移行することで、この問題を解決しようとしています。

💡EDN (Extensible Data Notation)

現在の開発版では、SQLiteデータベースにデータを保存する際の形式としてEDNが使用されています。EDNはClojureで使用されるデータ表現形式で、データ構造をテキストで表現できます。ビデオでは、EDNデータを使うことで、メモリ使用量を抑え、パフォーマンスを向上できることが期待されています。

💡プロパティ

新しいLogseekの中核となる概念が「プロパティ」です。各ブロックやページに対して、カスタマイズ可能なプロパティを割り当てることができます。例えば、会議用のプロパティには「出席者」や「議題」などのフィールドが設定できます。このプロパティ機能によって、構造化されたデータ管理が可能になり、フィルタリングやクエリの精度が上がります。

💡グラフデータベース

新しいLogseekでは、データをグラフ構造で表現できるようになります。プロパティを使ってノードやエッジを定義することで、複雑なデータ関係を視覚化できます。ビデオでは、プロジェクト、人物、トピックなどのエンティティ間の関係がグラフで表示される例が紹介されています。

💡スーパータグ

ビデオでは、Logseekの新しいプロパティ機能が、TanaDynamicNotesのスーパータグに似ていると述べられています。スーパータグとは、コンテンツブロックに付与できる構造化された属性のことです。Logseekもこの概念を取り入れることで、より高度な分類とフィルタリングが可能になると期待されています。

💡エクスポート

新しいLogseekでは、さまざまなデータエクスポート機能が提供される予定です。マークダウンファイルや他のアプリケーションとの互換性を確保するためのエクスポート形式のほか、SQLiteデータベースそのものをエクスポートできるようになります。十分なエクスポート機能があれば、ユーザーはデータロックインの心配なく自由にLogseekを利用できます。

💡テンプレート

ビデオでは、新しいLogseekにはテンプレート機能が追加される可能性があると言及されています。テンプレートを使えば、特定の種類のコンテンツに対してプロパティやレイアウトの設定をあらかじめ定義できます。これにより、構造化されたデータ入力が容易になり、ユーザビリティが向上すると期待されています。

💡ユーザーエクスペリエンス (UX)

ビデオでは、新しいLogseekのコアアーキテクチャが完成した後、ユーザーエクスペリエンスに注力する必要があると指摘されています。現在の開発版では、UIやインタラクションの面でまだ課題があり、最終的な製品版に向けて改善が行われる見込みです。優れたUXは、Logseekが広く普及するための重要な要素の一つと考えられています。

Highlights

While there are frequent updates with the chain clock videos I make for example it really feels like the core of Loi is kind of standing still a bit and that's because they are working on a big change in the background.

One of the benefits of a development branch is that you can just toss everything away and start fresh you don't have to think about migrating data, and that's why this warning is all the way in the beginning of the video it's cool stuff but we still have to wait for it.

If you go to GitHub and you go to the loek source code this is like all the code from loek which is awesome and then on the top here it says master and that is the master Branch that's the stuff that gets released to us normal end users but if you click on it you see like all these different names and that doesn't tell you a lot.

Featuring DB is the one that we're going to look at, you can see that you got like the master Branch here and this one says ahead 192 commits that means that 19002 code changes were committed to this Branch, this is way ahead normally it's like like something like this you like the this one 62 that's already a lot usually it's like 10 15 and then you merge it back in 1900 is a lot of work.

To fully grasp this backends are hard and I want to explain a bit how that gets taken away when you're working on normal system so if you're using a web app like Gmail notion something like that uh then it's pretty easy you just talk to your web browser your web browser has a back end as an AB that talks to their dat base or server and they do all the fancy hard stuff on the back end.

The problem with markdown is markdown is based for text formatting it's not based as a database or a structured setup and that means that if you start saving things like a block based system with property and links and all that other stuff in markdown you're kind of making things hard for yourself.

Currently the way loek is running is really stopping loek from performing, Prime examples I have for that are if I open a second window I get into trouble, because Loy doesn't understand that the second window is also making changes so I'm changing a page a totally different page in the other window and then the first window starts screaming because it like hey things gets changed on the disc, I didn't understand that.

This new Branch tries to solve that and it isn't just the back end that's just how it's saves it's the engine so the engine is the stuff between you you're working in loek and it's writing stuff down now if the engine is good and at some point it works and it has a proper back end then a lot of the stability speed problems can be easily resolved.

If you take your house as example if you live somewhere you make small improvements over time say for example I have one of those video doorbells at the door if I'm ever moving moving house and that's basically the same as when you're reiding an engine all these small things come back so the doorbell thing my automated lighting the fact that my oven's installed that my Wi-Fi is configured there's a 100 different things in my house that I fix while I'm going through time and loek having to rewi the engine basically has to make something that is compatible with all the things that they did before and then try and not iterate but like rewrite from scratch make like a more robust base to build on so this is a hard not to crack.

One of the the things that I really like is that if I make a block and I add like a tag to it then you get this like extra properties this is stuff that get added based on this so if I go to meeting it shows me here like hey these are the extra properties that I have like project attending summary.

I also like the fact that the layout like I can give it items, but they look the same as the text, they're a bit brighter but this is like normal you know adding uh text to the bottom to it and then the properties are part of it and not like a separate block, some formatting would be nice but that's something for later and probably a ux thing and if I fold it then it's like fully folded and the properties are no longer showing through.

Tasks are B based on the same thing and I really like seeing this part because that means that it's it's no longer task being like this unique thing now task is just a property and you can also configure it so I added effort for example to like give me up like okay how much effort is this going to be and if I click on it then you can say okay there's a text and I can give it choices so I can also say like hey I make like a low choice and I make like a high choice.

This idea just really Sparks Joy with me, the fact that I could write something down and then say like this is a source and I can link it towards a topic and towards a URL meaning that once I want to talk about a certain topic I can just see all the sources I had with the URL to their original source and probably even use like an export or combination to generate my description from it this is going to save me a lot of time in the future.

Now to give you a feel on how easy it is to build these kind of structures I'm going to go and then make an extra structure in this case I'm just going to add like a book author setup so first of all I'm going to make a page and call it like project Hill marry empty page and go here and I'm going to say like hey this is a book I'm going to go here I'm going to go to Tags I'm going to say it's a book I'm going to hit apply and then the book property gets set and then there are no more properties because book hasn't been configured yet.

I do like the export standard markdown which gives you very clean MD files with like no fluff in it meaning that you can give it to other systems to convert and at some point I would hope that there become like more export things available because if the engines is new that's easier to hook into and then maybe get some conversion into and out of obsidian for example so that people that want to switch tools or people that want to give Loi a try could just import into Loi try it for a couple of weeks and Export it back to obsidian to go back and hopefully stti around but you know that's my buyers opinion as a frequent loek user.

Transcripts

so if you're like me and you use loek a

lot you might be wondering where is it

all going you know what's going to

change and maybe if you've been keeping

your finger on the pulse you heard about

something called the DB branch and what

is that in this one I want to have a

look at the future of Loi and what is to

be expected there's a lot of good

comments I got from the community about

this I had a live stream a couple of

weeks back and that also was like a

really enlightening phase let's dive

into it now while there are frequent

updates with the chain clock videos I

make for example it really feels like

the core of Loi is kind of standing

still a bit and that's because they are

working on a big change in the

background and normally in a company you

couldn't see that but because Lo is open

source we can actually go to the code

and have a look at the branch where

they're working at and get a bit of a

feel where we're heading to and how

we're going to get there now before I

start this is all bleeding edge beta

stuff we're looking into straight source

code and that means that no account is

taken on how your data is stored or how

it's kept if you play around with this

that's fine but don't put any data in

there that you care about it will be

eaten it will be

swallowed and you'll you will lose it I

won't put any production data in there

I'm just messing around with where the

code is at but one of the benefits of a

development branch is that you can just

toss everything away and start fresh you

don't have to think about migrating data

and that's why this warning is all the

way in the beginning of the video it's

cool stuff but we still have to wait for

it now in this video I'm not going to

show you how to build this code that is

not beneficial for a lot of people this

just shows you how it looks like when

you did all the work if you do want to

look into that angle I highly recommend

the live stream I did a couple of weeks

back where I was messing around with the

actual database code now let's have a

quick look at the source code so where

did I find this or where does anybody

find this actually and that is if you go

to to GitHub and you go to the loek

source code this is like all the code

from loek which is awesome and then on

the top here it says master and that is

the master Branch that's the stuff that

gets released to us normal end users but

if you click on it you see like all

these different names and that doesn't

tell you a lot I mean it tells you a bit

about what people are working on but it

doesn't tell you a lot about where are

we in this process now if I scroll all

the way down you see here is view all

branches and if you click on that then

GitHub gives you some crucial

information so first of all featuring DB

is the one that we're going to look at

you can see that you got like the master

Branch here and this one says ahead 192

commits that means that 19002 code

changes were committed to this Branch

this is way ahead normally it's like

like something like this you like the

this one 62 that's already a lot usually

it's like 10 15 and then you merge it

back in 1900 is a lot of work and I know

that it's been constantly worked on

every time I check this one it's updated

at least a couple of hours ago it's

really going well then the other one

there the behind that's zero means that

it's recently been merged with Master

meaning that all the changes that are in

this one are already in this feature DB

effectively making this one-on-one with

the production version but with added

changes one thing that I wanted to show

is that what happens is that basically

there's this change here that happens

for the database uh branch and then

mouse keeps going and they move that

change to here and this is like a

separate change that says like this is

what you should do to combine these two

and they keep doing that over time it

gets very technical if you let me um

let's not but just know that what

they're doing is something that

developers do all the time but on a

larger scale and that's because it's a

big change and speaking of that big

change let's dive into that now I wanted

to answer two questions in this video

first one is what is this work that

they're doing and why does that take so

long which is a more of a technical

explanation on the changes that they're

trying to make and how hard that is and

the other one is of course what does it

look like give you guys a sneak peek on

on the future of loog seek and just like

have a feel for it so let's dive into

the first one and that is like okay

what's this change that they're actually

doing now to fully grasp this backends

are hard and I want to explain a bit how

that gets taken away when you're working

on normal system so if you're using a

web app like Gmail notion something like

that uh then it's pretty easy you just

talk to your web browser your web

browser has a back end as an AB that

talks to their dat base or server and

they do all the fancy hard stuff on the

back end they make the backups make sure

that stuff's there and if they lose your

data then you know it's on them you

actually should be able definely if you

pay them be able to call them and get it

fixed um that doesn't work for loek

because loek stores stuff locally so you

get your actor your loek here and that

stores in markdown files locally and

then if you have sync well then there is

an happy because then that syns the

markdown F somewhere else but this

initial part you don't need loek for

that once you have the app you can do

this forever basically unless you throw

the app away and that does make it a lot

trickier but also there's a limitation

here in the form of

markdown let me explain you see the

problem with markdown is markdown is

based for text formatting it's not based

as a database or a structured setup and

that means that if you start saving

things like a block based system with

property and links and all that other

stuff in markdown you're kind of making

things hard for yourself I also really

don't like the whole discussion about

like markdown not being totally

compliant when it's produced by loek and

stuff like that you have to make a

choice here do you want pristine

markdown files or do you want features

and in my case I want features and what

I want is that the way L seek stores it

in the back end I don't really care

about that too much as long as I'm able

to read it there might be a lot of work

there to get it out of there but as long

as Loi also has like an xort as marked

down with all without all the fluff

around it that's fine by me that just

means that the application that's what

my system can be used to export that but

currently the way loek is running is

really stopping loek from performing

Prime examples I have for that are if I

open a second window I get into trouble

because Loy doesn't understand that the

second window is also making changes so

I'm changing a page a totally different

page in the other window and then the

first window starts screaming because it

like hey things gets changed on the disc

I didn't understand that that are the

kind of trouble that you have on the

back end markdown nothing can tell the

second screen hey this is a different

screen that's working there these

changes are fine you can import them and

then it has to start asking questions

and it all makes for a very bad

experience added to that there's a lot

of metadata that Loy can't save in

between if they would then the markdown

file will be six times as long it will

be unreadable because like when was

every line last updated who did the last

update if we ever get to multi user

that's a lot of problems to have and

this new Branch tries to solve that and

it isn't just the back end that's just

how it's saves it's the engine so the

engine is the stuff between you you're

working in loek and it's writing stuff

down now if the engine is good and at

some point it works and it has a proper

back end then a lot of the stability

speed problems can be easily resolved

and the engine for lookseek of course

was written by someone who was

intentionally starting out for just

himself and then growing from there and

this happens with a lot of software at

some point they outgrow the initial

thought like the initial thing was like

built like this would be cool that would

be cool but then you need like a broader

plan and that means that you need to

rewrite your engine and this is

complicated now I'm going to give you an

example in the form of your house now if

you take your house as example if you

live somewhere you make small

improvements over time say for example I

have one of those video doorbells at the

door if I'm ever moving moving house and

that's basically the same as when you're

reiding an engine all these small things

come back so the doorbell thing my

automated lighting the fact that my

oven's installed that my Wi-Fi is

configured there's a 100 different

things in my house that I fix while I'm

going through time and loek having to

rewi the engine basically has to make

something that is compatible with all

the things that they did before and then

try and not iterate but like rewrite

from scratch make like a more robust

base to build on so this is a hard not

to crack there's a lot of things that

you have to keep in mind it's not just

backwards compatibility it's also that

you need to converted in the future you

are going to piss off a couple of users

cuz I'm pretty sure not everybody's

going to be happy with the direction

they take when they release it there

also one of the reasons why they don't

talk about it too much because until

they're there the conversations won't be

fruitful because a lot of people just be

complaining that it's not marked down

okay fair you know but that's a lot of

things to take this is a big change and

it shows when you're messing around with

the new feature it's cool but it still

needs some work mostly in things like

for example speed because that's

something you do later you start

stability first and then speed second or

maybe functionality first and then

stability and then speed but those

things all come and then ux so the

interface all things that need to be

happening and they all need to be done

and they all need to be polished before

you do this major release that to change

everything and it's something I've been

waiting on for a long time because it's

kind of what edding my channel on on

this way I'm talking Loi because I

believe that once they have this out it

will be a major change in what loic is

and the speed in which it can grow and

develop but even so once they make the

new version conversion stability all

these things need to be perfect because

that means that there will be like a new

Leaf a positive vibe so to say now when

I was live streaming the messing around

with the new version I also could do an

export and it was like an SQL light

export I did the export and then I was

hugely disappointed to find out that it

was a table with ID and one text field

with like edn data in it which is a way

of forting the stuff a large part of

that disappointment comes from me being

someone who's been at DBA for a while so

I used to run databases and seeing that

kind of data structur just makes me die

a little inside it's just how I am given

a night's sleep though it's not all bad

actually it's like a nice quick way of

working because the two most important

things are is that you have the edn the

data that can quickly be read by cler

and Loi as a data structure and then the

idea meaning that if Loi needs a

specific block it can get it from SQL

light this is like I would say uh

minimum valuable product what we say in

agile yes it would be nice if there were

like different fields but that's more an

export thing and not like a copy of the

SQL DB I think if they do manage to work

with this then there will probably be

two versions one is like a full SQL

database export and one would be the SQL

DB export that is used in internally

another big benefit of using this is

that you no longer need to load

everything that's a very important bit

because now you need to have like the

whole graph inside memory it needs to be

in your system and that means that if

you have a lot of notes like me and all

this uncompressed data is floating

around it starts to get bigger and

bigger and bigger and slower as a result

I haven't dove into the code but I

assume that taking with this SQL and you

can fetch elements you can also let go

of things you can say like I don't need

to read all these documents I can just

fetch them as needed and other people

can update it and I can see which one

has been updated and when meaning that

you can keep less memory Less in memory

means that there's like less processing

happening making it lighter on your

system faster to work with so the

database back end has a lot of benefits

and I think that the only person that is

actually really sad about it being edn

are people that wanted to mess with that

data a bit uh if that's you yeah it's

too bad I I know you feel so what

matters more to me is export and that

means that I don't often work with the

backend data of ly I work with what

comes out of Foxy so the exports that I

care about is can I export a block so I

can put it in an email can I export my

data into some type of markdown format

that I can use if I no longer want to

use Loi or use as a base to migrate to

something else that will never be a

oneon-one match there's too many

variables too many features things that

won't be compatible I know that nothing

nothing was ever perfect when I moved

all my stuff to notion it wasn't perfect

when I moved from notion to lock seek it

wasn't perfect it's never going to be

perfect the thing is are you able with

enough elbow grease to get stuff out cuz

that's the stuff that I usually do I

just do like a raw import it's not

perfect you can see like the mistakes

but I can find it with a contr F and I

can fix it over time as I find the data

cuz fixing the format thing I still see

some old obsidian stuff in between when

I'm working with my logi I have the data

I didn't lose anything I just just lose

2 minutes reformatting and making it

nice and proper and then go on with my

day so if export is good then the rest

to me is like fine also uh one of the

things that why I don't worry about the

export M I have to software locally like

I talked about things like you know the

planned and um obsolescence or intific

of cloud apps the problem with Cloud

apps is that if NOA makes a new update I

just have to accept it there won't be an

old version of notion running around and

that means that what happens with a lot

of cloud apps they change over time and

becomes harder and harder to exploit and

eventually you're stuck in this program

and this is much less the case with like

Loi because while Loi could change you

could always just keep using the old

version before the change and then use

that for half a year until you find like

a suitable alternative you're not locked

in like you are with a lot of cloud apps

okay enough dry Fury how does this new

version Look What are you actually going

to see in the future now please keep in

mind yes we're messing but it's a

development version could be that have

these features get removed before it get

released I doubt it but you know things

will change because they're trying to

figure out what would be the best ux how

to make it useful uh in the time that I

messed with this Branch it's already

changed a couple of times and I think in

most cases for the better it became much

more intuitive to use right so if we're

having a look at this then you

immediately will see that it looks a bit

different yes the menu is still there um

but for example here you have like ad NE

graph database version so there's like a

a clear indication that things are

running side by side and you see like

properties look different and we'll dive

into each one of these a lot of this

stuff is just stuff that I quickly build

and because I run an Enterprise

environment I look at it from a work

perspective but I've also seen some

really nice examples from people to do

more of a research set um let's just go

step by step through this and give it a

feel first of all one of the the things

that I really like is that if I make a

block and I add like a tag to it then

you get this like extra properties this

is stuff that get added based on this so

if I go to meeting it shows me here like

hey these are the extra properties that

I have like project attending summary if

you click on those then you get like

this whole bunch of details here so you

give it a name you can give it an an

icon for example in my case construction

is what I always use this scen here and

then I said like hey it should Point

towards a page and then I can say like

multiple pages and I also specify class

and I really like this because that

means that I can start building systems

if I make like a meeting setup here and

I go now back to this overview then this

shows me only one page here that's

because I only had one page that was

marked as project so if I click on this

you see this one it says like type

project this is gamechanging for me

because it means that un like what I

used to do when I had like a meeting and

I had like an attending and I had to

fill in like all the different pages I

could just filter through my whole Loy

graph now if I click on it it just shows

people so if I type one letter I usually

get the person that I would need of

course I don't yet because I can't use

it in production this is the one thing

that I missed the most during my workday

and as you see it looks like really

clean uh you can change it both here

this name for the property is also

Global so if you configure something

like attending with page in person and I

would make like a different type and I

would say that one needs an attending as

well then you'll re like inherent all

these features which is nice I also like

that the layout like I can give it items

but they look the same as the text

they're a bit brighter but this is like

normal you know adding uh text to the

bottom to it and then the properties are

part of it and not like a separate block

some formatting would be nice but that's

something for later and probably a ux

thing and if I fold it then it's like

fully folded and the properties are no

longer showing through another example

here is tasks tasks are B based on the

same thing and I really like seeing this

part because that means that it's it's

no longer task being like this unique

thing now task is just a property and

you can also configure it so I added

effort for example to like give me up

like okay how much effort is this going

to be and if I click on it then you can

say okay there's a text and I can give

it choices so I can also say like hey I

make like a low choice and I make like a

high choice and once you do that and you

go here and I click on effort then I can

say like okay this is low effort uh I

can give it a priority can I like this

is high priority and you give all these

things can get like their own icons

these ones get can get colors so for

example if you say like Hey low should

have like some some kind of green thing

I click on this one I go to Icon uh give

me a second what loads I search on green

said give it an apple do save and you

see this and this is all like setting

through it reminds me very much of super

tags of Tana um I haven't messed with

super tags recently so I don't know how

close this is to it but it's something

that I was really looking forward to

seeing in loek eventually and I'm so

glad that work on that that part is

getting done I also like the fact that

they didn't say like this is how tasks

are supposed to be done will give you

some really nice examples but from there

on you can tweak it you can make your

extra choices we'll just give you a base

and then let you decide how you want to

configure lock seek to fit your needs

this idea just really Sparks Joy with me

the fact that I could write something

down and then say like this is a source

and I can link it towards a topic and

towards a URL meaning that once I want

to talk about a certain topic I can just

see all the sources I had with the URL

to their original source and probably

even use like an export or combination

to generate my description from it this

is going to save me a lot of time in the

future and that's just me messing around

with this for like 10 15 minutes and

there's a lot of options when it comes

to properties so let's take another one

like the source one as you can see here

like you can also make like a base from

it it goes very fast but if you switch

to the configure set it can say like a

parent class so it can basically

inherent stuff from other classes say I

have a a person uh but I could also make

like levels on that by saying like okay

you have a person but you also have like

a work person or something or I don't

know I could have like a person and then

you could have like a customer and an

employee those are both persons and they

could inherit some classes and you can

move down it's a very programmatic

approach but something I really like now

you can give things like extra tags

icons everything is tags like source is

a tag uh you can see that if we look at

the project in a bit and then the

properties are here uh let me quickly go

over the types of properties so let's

say prop example so we get a new one if

I click on that then the options here

currently are text where you can also

decide which type of text you can give

it a number forcing it into a number but

also that one has like available choices

to it where you can give it specific

values it's the same idea but just

limits it to to text uh dates so you

know simple put a date field uh you can

add choices with like specific values to

it but that doesn't really help a lot

here I think I think it's mostly

consistency and might be cleaned out if

they get to a final version checkbox

simple on off very nice to make things

active inactive stuff like that URLs

which are clickable uh yeah love that

because that also means that you can

have like repeating URLs which sometimes

is useful and Pages this is the one I'm

going to use most because here you can

say hey I want a specific type of page

and this is where like the whole ux

comes in a bit like the the sizing

doesn't work it works as expected like

if I person here and I scroll down I

find the apply button then it does what

it does but there's still some ux things

might be my browser might be the layout

might be CSS which is always horror you

can say if you want to hide it by

default which I think is great so then

on a page you don't get like 100

properties if you don't want those and

then we have template and I have no idea

how this works I've been messing with it

a bit and it shows you like hey which

template do you want to use and you get

like a button to say apply template I

think that's the direction but I

couldn't fully get it to to work what

before this video I'm sure that's going

to get better over time and there's

going to be more information about that

and there's also going to be more help

like like these small eye that I see

everywhere another thing that I really

like is once you get this structure

going that means that your graph

suddenly becomes a bit more useful now I

am going to make a video about graphs

because I had some really good

discussions with people about why graphs

are useful and how they help out one of

the things that you see here is that

that all the things that I specified

like persons projects topics cities

these were all taged and configured

stuff are elements and you can see like

okay these are all my person elements

these are all my projects uh one of the

things it doesn't though is that if you

put something in like a property and

Link it this won't show up here so let

me say for example example project here

I'm the owner um but if you look in the

graph there's no direct link between

example project and me uh so I don't

know if that's going to be fixed or if

that's by Design the reason reason why

Bob and me are linked for example here

is because I put like some text in there

saying like hey I make videos about Loi

currently recording from Amish for and

the same thing is in Bob where Bob the

cat links to me and that's how the links

got there but it makes the whole graph

idea a lot more interesting loic itself

here being a like a topic but not

showing here because only DB here has

the topic thing in it uh and loogi is

more of a derivative from it while I was

setting up this t test so now if you

look at this you see like Loi is linked

to loic DB and topic so it has like mult

the colors to me immediately make a bit

more sense I still think there there

should be like more configurability here

but I really like that how you see this

dest structure in the new version kind

of like solves the reason that this

normally always became like such a mess

on my end now to give you a feel on how

easy it is to build these kind of

structures I'm going to go and then make

an extra structure in this case I'm just

going to add like a book author setup so

first of all I'm going to make a page

and call it like project Hill marry

empty page and go here and I'm going to

say like hey this is a book I'm going to

go here I'm going to go to Tags I'm

going to say it's a book I'm going to

hit apply and then the book property

gets set and then there are no more

properties because book hasn't been

configured yet so if I go to book here I

was messing a bit with the template I

can go here and I can click on this go

to properties and say for example well

you know a book should have an

author and next next to an auor maybe uh

good reads link for me it's always very

important good reads and maybe release

year let's give it a year you know for

total of it so I do something like this

I go to author and I say with author

like okay that's cool that's going to be

page and I want to be able to have

multiple cuz some books have multiple

auor I want to say specified class and I

want to link it to a person then scroll

down a bit and find that apply button in

the corner and then do the to the auor

part is configured I can put like an

icon on it then I get to the good reach

one I say that one's a year row and

let's put an icon in there as well let's

see I think link and I'm going to go for

year and then I'm just going to say that

one's like a

number set on there so filling this one

in now if I go back to project Hill Mary

and I say like this is a book I get a

whole bunch of properties and then I can

say like okay the author

is and the rear and as you can see I get

a new Option I can click apply and it

gets created it's automatically marked

as a person and so I can start filling

in data I'm I'm going to put the good

reads uh information in there but then

again like if you get the nyw and this

kind of setup where I'm just clicking on

things and adding and then reusing

elements that I already had that really

like quickly means that it can build

small structures and these things stay

so like if I go to add a property as I

said before like I had the attending if

I use that

one

then you see the same setup I can only

choose persons it's the the setting that

I already had and only if I pick

something it keeps it there because this

is for the page and not for the

book this I really like like I can

quickly build structures and any

structure I build comes back when I'm

building structures meaning that it

stops me from like scatter braining over

my system and making all these new

systems all the time I really hope it it

grows into something that like keeps me

more consistent okay then let's look at

the export options those changed a bit

but not much and there's also not a lot

to see there's the export ssql light DB

which is new I had a look at it it's

just a key value store so it's an ID

with like a long string which has the

data in edn form yeah that just made me

sad but I talked about that before I do

like the export standard markdown which

gives you very clean MD files with like

no fluff in it meaning that you can give

it to other systems to convert and at

some point I would hope that there

become like more export things available

because if the engines is new that's

easier to hook into and then maybe get

some conversion into and out of obsidian

for example so that people that want to

switch tools or people that want to give

Loi a try could just import into Loi try

it for a couple of weeks and Export it

back to obsidian to go back and

hopefully stti around but you know

that's my buyers opinion as a frequent

loek user now that was a very quick skim

over the future of loek and I think

there are still things that I have on my

wish list for this I think first of all

tasks look nice but the way it's set up

right now isn't as clean as the current

setup I'm pretty sure that's a ux thing

though and it's something that they'll

fix like in the end by adding formatting

for different types and classes which

immediate falls into like the other one

is like I would love to be able to

format specific classes to look in a

certain way sometimes you know you want

like the list and that's fine enough to

collect data but for some things you

might want to have like a more condensed

form or like a single line version which

is with tasks for example easy like you

want to have like a easy way of making

this list queries work for that in a way

but it would be nice if there was like a

default so that also my journal makes

like a nice tight bundle of easy to read

text another one is like how will

templates work and I have no idea but

it's a ux thing so I'll probably just

scour the design section of discorde to

see what kind of ideas have been kicking

around they are overhauling it for sure

and that might be good because the

templates as they are now are very

confusing to people with the page

templates and the block templates um

with these super tags kind of

functionality where you just tag a block

and it will become something I think

that's much closer to what the templates

that we were looking for so looking

forward to seeing what's happening there

obvious ones stability and speed it

already feels more stable in the data

wise speed wise I don't know I had like

a test version going that I really tried

to put through his loops and that really

didn't perform that well but as of

course you first build your structure

and then you start optimizing it by

hitting it with low tests and then

figure out where it's slow fixing that

I'm building upon it I will definitely

be running some load tests once it's

ready for prime time which is

unfortunately not now and of course more

options for queries it's nice to have a

table but I really want to have things

like boards and calendars built into the

core definitely with property Fields

like du dates having a calendar view

would be absolutely amazing and make my

day oh that was a quick glimpse into the

future of VX seek if you got any

questions comments leave them down below

in the comments I'll try and read

everything and answer as soon as I get

time or meet me on the Discord where

we're having like discussions on ux and

the database version as it's developing

remember you're awesome keep it

[Music]

up

[Music]

oh look