First and foremost, I’d prefer to be honest about my use of AI:

Testing – writing tests, test plans and QA: Pair

That’s it! I think my commit history will speak for itself.

I’ve been a member of this community for a very long time now (ever since the Reddit API crisis and my move to Lemmy) and for several years now, I’ve been thinking about sharing my personal project with you. There is a good reason why I’ve hesitated for so long : I’m happy with what I’ve done, but I haven’t been a professional developer for a long time, and it shows in my UI :D

But nothing ventured, nothing gained, and that’s why I’m taking the plunge today to introduce you to a timeline management tool.

It’s simple, still a bit rough around the edges in some respects (particularly the table-based editing mode), and you’ll certainly find some features missing, but it does the job for me at the moment.

I’m sharing this with you today for two reasons:

  • To showcase my work, and perhaps give you a pleasant surprise
  • To get your feedback on what you see, and any missing features that might make you want to use it

Because if I’m going to spend my evenings working on a project like this for several years, it might as well be of use.

Here are a few ideas for features I’m currently thinking about :

  • Implementing other types of charts (like gantt)
  • New options to customize color
  • Zooming in/out on your charts
  • Implement the option to enable authentication on your instance
  • Implement the option to enable the organisational principle for grouping and sharing creations by different users

The product can be tested online completely free of charge or tested using its Docker image

Thank you in advance for taking the time to consider my project. I look forward to hearing from you soon.

  • besstiolle@lemmy.worldOPEnglish
    2·
    1 day ago

    Thank you so much for your feedback.

    This is indeed a feature that would be interesting to implement—offering three types of links between two tasks:

    • One would be a flexible link that allows the end date to be moved without affecting its downstream tasks
    • The second would be a dynamic link that maintains the gap between upstream and downstream tasks regardless of any changes to the end date of the upstream task
    • The last one would be a semi-dynamic link that simply shifts tasks backward to stay on the critical path of a set of tasks.

    Of course, I need to consider all the constraints this might create in the current user interface. But it’s a very interesting idea that I hadn’t considered before.

    • ogy@fedia.io
      1·
      22 hours ago

      You’re very welcome! Just to be clear, these are the types of dependencies I was thinking:

      • this task can only end a set time after that task ends (the cleaning of the job site can start during the job, but can’t end until the job does)
      • this task can start after that task has started (I can start processing lab data after the first experiments have come in - I don’t have to wait to the end)

      etc.!

      I think it should be possible to define many dependencies / constraints and have the program simply freeze and flag when there are conflicts due to overdefining. I’m sure there’s a way to calculate the degrees of freedom, though the math isn’t something I can be bothered with rn haha