MVP made easier.

[vfclists]

Does MVP mean Model-View-Presenter?

Not so minor nitpick - The versioning is easier to understand if you enter the date first before the build version, and the date should be in YMD order, so  10.26.08.2024 should be 2024.08.26_10.

If the ser and ver values are date independent then it may okay for them to precede the date. They must have to be sorted consistently.

These issues make a whole load of difference when you are confused about the versions and their dates.

[cdbc]

Hi

Does MVP mean Model-View-Presenter?

Yes it does, with the dialect leaning towards Martin Fowler's 'Supervising Presenter' philosophy.
Regarding versioning:

Code: Text  [Select][+][-]

1. csuVersion = 10.26.08.2024
2.              |  |  |  +- - : the major version cannot cross year borders
3.              |  |  +- - - -: the major version cannot cross month borders
4.              |  +- - - - - : date committed
5.              +- - - - - - -: MAJOR version, feature change, refactor etc...
6.              !- { - - - - }: bug-fixes can retain major version, until it breaks
7.                              one of the 2 first rules, then it gets bumped +1  
8.  

The rule is, that if I add features to the source, the major version gets bumped +1   
This way I don't have to keep a schema / table with the version <-> date mappings, I can see: oh, it's version ten from 26th of August in year 2024.

If the ser and ver values

Sorry mate, what ?!?
I don't make that many versions or even different programs / utillities / libraries 
Regards Benny

[Hansvb]

Hi,
I can't keep up.  I'm still working on the previous one.  This new addition is going over my head for now. But then I have plenty to do in the fall and winter. So the questions may not come for a while.

[cdbc]

Hi
Don't worry Hans, this last one was just an example of how you can make it, so that you don't have to /hard-code/ the 'Sects' array, but instead let each (new) unit or class that needs it, 'Register' its /section/ with the model, in its initialization code at unit-loading.
I haven't (yet) implemented it in the 'mvp-setup', so its still /cooking/ and waiting for the next nice prime(11) release, who knows - maybe I'll think of something else cool to put in there as well 
Nice, that I too, can put _you_ to work 
Regards Benny

[Hansvb]

Nice, that I too, can put _you_ to work

You indeed do that. But don't get me wrong, that's good.
I'm currently in doubt... I want to get to grips with it better, but I also want to continue working on my own tool in which I already use the mvp setup generated with youre tool. Now do a little of both.

[cdbc]

Hi
That's great, practical 'hands on' experience is the best... Have fun 
The 'Grips' will come with working with it ...or playing 
Regards Benny

[vfclists]

Hi

Does MVP mean Model-View-Presenter?

Yes it does, with the dialect leaning towards Martin Fowler's 'Supervising Presenter' philosophy.
Regarding versioning:

Code: Text  [Select][+][-]

1. csuVersion = 10.26.08.2024
2.              |  |  |  +- - : the major version cannot cross year borders
3.              |  |  +- - - -: the major version cannot cross month borders
4.              |  +- - - - - : date committed
5.              +- - - - - - -: MAJOR version, feature change, refactor etc...
6.              !- { - - - - }: bug-fixes can retain major version, until it breaks
7.                              one of the 2 first rules, then it gets bumped +1  
8.  

The rule is, that if I add features to the source, the major version gets bumped +1   
This way I don't have to keep a schema / table with the version <-> date mappings, I can see: oh, it's version ten from 26th of August in year 2024.

If the ser and ver values

Sorry mate, what ?!?
I don't make that many versions or even different programs / utillities / libraries 
Regards Benny

If the ser and ver values

Sorry mate, what ?!?

These are the prefixes of the directory names in the gitlab repo.

[cdbc]

Hi
I think you'll find, if you look closer, the one is ver_10.26.08.2024 and the other is src_10.26.08.2024.
A binary and a source -release...
Regards Benny