Compose Widget about etar-calendar HOT 11 OPEN

@jspricke @Gitsaibot since you both are people who I have seen active in this repo.

Which of you would be better to talk with about architectural problems of this application?

from etar-calendar.

@Doomsdayrs The code is originally from the Google AOSP project and we only try to keep it alive. We welcome fixes for architectural problems as long as they are small logical self contained patches. We neither have the knowledge nor manpower to give you guidance for that.

from etar-calendar.

@Doomsdayrs The code is originally from the Google AOSP project and we only try to keep it alive.

It's like if google was trying to ensure their code was unmaintainable. (sarcasm)

We welcome fixes for architectural problems as long as they are small logical self contained patches.

A long series of small patches, I have experience with that. It's annoying compared to large overhauls, but I can get things done with enough free time. (Don't have currently)

We neither have the knowledge nor manpower to give you guidance for that.

Wait, None of y'all have experience with system analysis and architecture?

from etar-calendar.

We neither have the knowledge nor manpower to give you guidance for that.

Wait, None of y'all have experience with system analysis and architecture?

Not sure how you got to that conclusion but all I said is that we don't have the time help you.

from etar-calendar.

As far as the widget topic in general is concerned, I am "painless" when it comes to changes. I have never used the widget before and can therefore say little about the structure and architecture. That the code is not really great should be clear to anyone who has looked at it ;).

from etar-calendar.

We neither have the knowledge nor manpower to give you guidance for that.

Wait, None of y'all have experience with system analysis and architecture?

Not sure how you got to that conclusion but all I said is that we don't have the time help you.

I arrived at that question, not conclusion, due to the statement "neither have the knowledge nor manpower" which results in: !haveKnowledge && !haveManpower.

Thanks for clarifying that its a lack of time.

from etar-calendar.

As far as the widget topic in general is concerned, I am "painless" when it comes to changes.

Should I just:

1. scrap the code entirely for a compose widget replacement
2. deprecate the original code and write the compose one
3. have the compose one exist alongside the original (original plan)

from etar-calendar.

Since I can't exactly estimate the effort of the individual approaches, I would leave the decision up to you. After all, you have the time and effort ;) But if the compose widget offers the same user experience as the existing widget then I see no reason to keep the old code.

from etar-calendar.

Since I can't exactly estimate the effort of the individual approaches, I would leave the decision up to you. After all, you have the time and effort ;)

I have 10 assignments due, this is my relaxation exercise. 😄

But if the compose widget offers the same user experience as the existing widget then I see no reason to keep the old code.

Alright, will shift priorities to complete replacement of old code.

from etar-calendar.

I will be putting out another release in the next few weeks. Do you have any changes you want to make or is there nothing new regarding the widget yet?

from etar-calendar.

I will be putting out another release in the next few weeks. Do you have any changes you want to make or is there nothing new regarding the widget yet?

Nothing new on my part, Currently been busy this month at parties & raves.

from etar-calendar.