import from wallos .json #65

Open
opened 2025-11-25 11:15:43 -05:00 by Silther · 4 comments
Silther commented 2025-11-25 11:15:43 -05:00 (Migrated from github.com)

I currently miss a few features from wallos, but find the interface subtrackr much cleaner.
Would be nice if I could import wallos exports to move over in the future.

I currently miss a few features from wallos, but find the interface `subtrackr` much cleaner. Would be nice if I could import wallos exports to move over in the future.
bscott commented 2025-11-25 14:05:47 -05:00 (Migrated from github.com)

Thanks @Silther -- I will look into this shortly, what other features would you like to see?

Thanks @Silther -- I will look into this shortly, what other features would you like to see?
Silther commented 2025-11-25 16:04:58 -05:00 (Migrated from github.com)

things like having an ics link a calendar can subscribe to instead of an ics file or not bneing able to create a subscription without a category.
But mostly I would need support for custom schedules like 4 weeks not just weekly and monthly.

things like having an ics link a calendar can subscribe to instead of an ics file or not bneing able to create a subscription without a category. But mostly I would need support for custom schedules like 4 weeks not just weekly and monthly.
bscott commented 2025-12-09 01:22:07 -05:00 (Migrated from github.com)

@Silther 👍🏾 on the ical link, Monthly is every 4 weeks, can you elaborate on Custom Schedules?

@Silther 👍🏾 on the ical link, Monthly is every 4 weeks, can you elaborate on Custom Schedules?
bscott commented 2025-12-19 23:00:51 -05:00 (Migrated from github.com)

Hey @Silther — thanks so much for your patience here, and I really appreciate you raising this.

I haven’t forgotten about the request at all. I’m taking a bit of extra time because Wallos is an actively evolving open-source project, and its export format may change over time. I want to make sure that if I do implement this, it’s done in a way that’s respectful of Wallos’s design and sustainable long-term, rather than something brittle that could break quickly.

Wallos has a genuinely great feature set, and that flexibility is part of what makes it such a strong project. The flip side is that matching every possible export variation may not always be feasible on my end, but I’m exploring what a thoughtful, well-scoped integration could look like.

I’ll keep you posted as I learn more — it’ll likely be a few weeks — and I really appreciate your understanding in the meantime.

Hey @Silther — thanks so much for your patience here, and I really appreciate you raising this. I haven’t forgotten about the request at all. I’m taking a bit of extra time because Wallos is an actively evolving open-source project, and its export format may change over time. I want to make sure that if I do implement this, it’s done in a way that’s respectful of Wallos’s design and sustainable long-term, rather than something brittle that could break quickly. Wallos has a genuinely great feature set, and that flexibility is part of what makes it such a strong project. The flip side is that matching every possible export variation may not always be feasible on my end, but I’m exploring what a thoughtful, well-scoped integration could look like. I’ll keep you posted as I learn more — it’ll likely be a few weeks — and I really appreciate your understanding in the meantime.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bscott/subtrackr#65
No description provided.