🔒 i'm thinking to make a timeline-like vscode extension

[icy socket]

basically some an extension that acts like vscode's timeline, but with folders, and i'm thinking of how should i design it

[fallen pendant]

@icy socket

Python help channel opened

Remember to:

• Ask your Python question, not if you can ask or if there's an expert who can help.
• Show a code sample as text (rather than a screenshot) and the error message, if you've got one.
• Explain what you expect to happen and what actually happens.

:warning: Do not pip install anything that isn't related to your question, especially if asked to over DMs.

Closes after a period of inactivity, or when you send !close.

[icy socket]

@crude frost

[crude frost]

it should just be a stream of all commits involving files in that folder, no?

[icy socket]

what i have in my mind so far is that all points would be start in the uncategorized folder

yea but like it needs to be easy to use

so then u can change the name of the folder uncategorized to another name

and all those commits inside it will be moved there

should i even have a "new folder" button?

or the ability to move commits from one folder to another

[crude frost]

when you say "with folders", you don't mean source code folders?

[icy socket]

no i mean that there will be folders-like that contain those commits

one sec

uncategorized
-> commit_a
-> commit_b

so uncategorized is a folder that appears in that timeline

like this sort of

[crude frost]

huh
what kind of categories would one have, typically?

[icy socket]

he can then rename the folder uncategorized name to whatever session he had, like "implementing X"

and he'd have all the commits to be under that new folder

and new commits will create the folder uncategorized again and be under it

[crude frost]

isn't this recreating Git branches? 😅

[icy socket]

its like pushing those commits and naming that

but local xD

something like that

and that every save is a commit

all the commits would be in a folder next to the file it made them with

its a bit complicated right

[crude frost]

perhaps... I usually just use Git's branches and stashes for things like this. every save being a commit sounds like too much granularity, but I've never tried doing it like that so I guess I can't be sure.

[icy socket]

i think that it could even be integrated with git 🤔

i dont know how it would be either, with every commit being a save

i guess i need to make a first version of it and see how it is

[fallen pendant]

Python help channel closed for inactivity

This help channel has been closed. Feel free to create a new post in #1035199133436354600. To maximize your chances of getting a response, check out this guide on asking good questions.