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.

Hardly none is mostly all.

It's not my place to argue with your opinion.

Thank you for taking the time to share it anyway 😉

I mean when you say "hardly no AI" that means it was "mostly all" AI. I don't think that's what you meant to say.

ho ...

😱

English isn’t my first language, but no matter how many times I check my translation, it seems to make sense to me.

But anyway, I’m sure you understand the nuance in that sentence better than I do, so I’ll take it back just to be on the safe side

The original title was : [AIP] besstiolle/Timeline: my own tool for organizing my timeline diagrams with (hardly) no AI-generated content

I don't know why besstiolle is getting downvoted when they are correct.

When people say that there is very little of something the natural way is "hardly any rain" for example. So if you invert the meaning from "any" to "none"/"no" the whole sentence means the opposite.

I guess it could be explained as follows (but I am no ethymologist, just thinking aloud here, may be wrong):

"hardly any rain" means that there is so little of it, it is hard to even say that there is any rain.

If your friend says to you "There is no rain" and you go outside and it pouring, you could say 'Hardly "no rain!" ' As a kind of mocking comment highlighting that it's the complete opposite of no rain. It is very hard to call is "no rain" when it's raining so much.

Hope this helps!

Testing, test plans, and QA is not "mostly all".

Let's also stay on topic please. Its tagged appropriately and the relevant disclosure is present.

If your friend says to you “There is no rain” and you go outside and it pouring, you could say 'Hardly “no rain!” ’ As a kind of mocking comment highlighting that it’s the complete opposite of no rain. It is very hard to call is “no rain” when it’s raining so much.

Hope this helps!

I also thought that was how it worked, but then again, as English isn’t my first language, I’d rather not dwell on that detail

Yes that's my point, they misphrased it

I read the original differently than you, but it seems its been edited in the meantime (and I'm on mobile at the moment)

Either way, I think all is well currently

Wildly ambitious editing timeline in that chart there 😔

Could be a 20s clip! 😀

Just a small point, double negatives can get pretty confusing. Even in English, you often have double negatives becoming a negative rather than a positive, e.g. "I didn't go nowhere" or "You don't know nothing". Changing which part of the phrase you emphasise can also change that, for instance, if you said "I didn't go nowhere" it implies that you did in fact go somewhere (double negative becomes a positive when stressing the second negative). This gets all the more confusing when you bring in other languages, since they all handle double negatives differently!

if you do Gantt charts, please make sure you implement as many dependency types as possible - most of the power of gantt charts lies in how depencies allow for changing one thing and having automatic adjustment of the entire timeline, but almost all of the tools I've used have only implemented "this task starts when that task ends" which is infuriating

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.

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