Hi Ede,
thanks for Dilbert! He is selfexplaining too...
A) I think I explain in a former mail to Michael. Anyhow I agree: "using
Task tags saved to XML is the much more sensible solution". I adopted this
way.
B) Actually OJ ask to save a project only when an user click on "Exit"
plugin ("Do you want to close selected project...?"). Clicking on "X"
button of a Tak frame simply pops up a different warning ("Do you ant to
close a project?"). There are some warnings for modified layers or layers
with no datasource but no control on other project modifciations (chenged
styles and, in this case, changed task properies).
A check that controls all these modifications should be very useful.
I will keep project properties modified but not saved into the project. And
move the question to (automatically) save them on closing task.
C)..
D) It is OK for me
Peppe
2017-05-08 11:38 GMT+02:00 <edgar.sol...@web.de>:
> hey Peppe,
>
> A.
> can you point me to where the tags are currently written/read/managed in
> our Task code?
> i remember us talking about metadata and me opposing to add
> Getters/Setters for each and every field that might come along as handy, so
> i think (re)using Task tags saved to XML is the much more sensible solution.
>
> B.
> wrt. OK/Cancel etc.. - yes the OK button is effectively Cancel if there is
> nothing to change, so you are on the right way.
> you might wanna replace the OK button with Save to make the user aware
> that (the whole incl. all changes?) project is about to be saved when there
> are changes committed.
> generally our workflow has users deciding when to save, so maybe you
> consider just to change the setting, set the project to modified but leave
> saving up to the user?
>
> C.
> wrt. Modification Time - how is this handled within other GIS (Jukka?),
> especial wrt. changed datasets. i can imagine a scenario where only a
> dataset is changed but the project as such is not changed,
> - which date would be more important?
> - would it make sense to show the mod. times of the datasets as well?
>
> D.
> location in menus. the plugin should be available at the end of (instead
> of Customize)
> MAINMENU->Edit
> ...
> Separator
> Project Properties
>
> additionally it can be added in the category popup menu, maybe above the
> 'Open' menu entry.
>
> it's selfexplaining in the UI that users can change values there, so no
> need to add "View/Edit" to the plugin name.
>
> so far.. ede
>
> PS: a little dilbert - http://dilbert.com/strip/2017-05-04 &
> http://dilbert.com/strip/2017-05-05 & http://dilbert.com/strip/2017-05-06
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
