There are Python and shell scripts and a README.txt in the doc path. These are used to create the prev/next navigation from the main TOC. I applied the scripts and pushed the changes. Btw these are the scripts you initial file name broke.
Anyway find a good place to reference that page, insert the link. I will apply the scripts from time to time. Oliver Am 11.07.2016 um 23:19 schrieb Wolfgang Rosner: > Am Sun, 03 Jul 2016 14:24:24 +0200 > schrieb Oliver Eichler <[email protected]>: > >> That is crisp, informative and just with a minimum of unnecessary >> pathos. +1 from me. > Thanks for the flowers. > This result is mainly due to qualified critics ;-) > > >> I would suggest to insert it under "Working with Projects". But you >> can make it a main topic, too, if yu want. > Do you really ecpext me to screw your TOC and navigation scheme? > > I see that there is some prev/next logic at the top of each manual page. > Is this to be maintained manually? > Or is there any system to maintain navigation consistency? > > Until now, I only used the simple "Markdown" language to produce my > wiki text. To be honest, I'd prefer to stay with that. > I would be glad if someone more competent would perform the > TOC-related operations. > > Wolfgang > >> Oliver >> >> Am Sonntag, 3. Juli 2016, 12:09:57 schrieb Wolfgang Rosner: >>> Hi Oliver >>> >>> pen-pen-ultimate version: >>> https://bitbucket.org/maproom/qmapshack/wiki/DocGisHowToSaveYourWork >>> >>> >>> I worked your database workflow into the workspace chapter. >>> >>> The whole thing is not really perfect - it reads a little bit from >>> back to top. >>> >>> actually, database handling partially would belong to >>> https://bitbucket.org/maproom/qmapshack/wiki/DocGisDatabase >>> >>> But rearranging it would be a major effort. >>> I'd prefer to spend the time on a chapter on route planning instead. >>> >>> So I could live with the version as it is now. >>> Can you, too? >>> >>> >>> Wolfgang Rosner >>> >>> >>> >>> >>> Am Sun, 03 Jul 2016 11:18:15 +0200 >>> >>> schrieb Oliver Eichler <[email protected]>: >>>> If you load an item from the database it's folder is opened as a >>>> project in the workspace with the item attached. If you edit the >>>> item you will see the asterix that it has been changed. If you >>>> save the project, the item will be changed in the database. >>>> >>>> It's really that simple. There is no different between file based >>>> projects or database projects. >>>> >>>> The sync. function is to update your workspace if someone else is >>>> changeing items on another instance of QMapShack. This includes >>>> saving local changes and reloading all items in the workspace. On >>>> a conflict the user is asked which version to keep. >>>> >>>> Am Sonntag, 3. Juli 2016, 11:05:47 schrieb Wolfgang Rosner: >>>>> database and storage.... >>>>> >>>>> referring your remark in my wiki draft: >>>>> >>>>> "kiozen: the usual way to save data to the database is using >>>>> "Save". "Sync. with database" is used when two users access and >>>>> work on the same project in the database." >>>>> >>>>> >>>>> I think syncing databases is big issue beyond the context of >>>>> this wiki page >>>>> >>>>> But I do not find any other way to "save" changes into a >>>>> database. I cannot even edit any item in a database - is this >>>>> correct? >>>>> >>>>> So I assume: >>>>> >>>>> - any item stored into a database is written immediately and as >>>>> a whole >>>>> - I cannot open/edit/store an item into a database, but have to >>>>> copy it to a file based project >>>>> - "sync" means reading the db in case somebody else has made >>>>> changes (may I assume that you can concurrently access a >>>>> database on a file server by several instances of QMS and QMS >>>>> takes care of proper locking and consistency?) >>>>> >>>>> or shall I simply omit the database part from my backup >>>>> chapter / mark it as TODO? >>>>> >>>>> >>>>> Wolfgang Rosner >>>>> >>>>> ------------------------------------------------------------------------ >>>>> ---- -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at >>>>> AT&T Park in San Francisco, CA to explore cutting-edge tech and >>>>> listen to tech luminaries present their vision of the future. >>>>> This family event has something for everyone, including kids. >>>>> Get more information and register today. >>>>> http://sdm.link/attshape >>>>> _______________________________________________ >>>>> Qlandkartegt-users mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users >>>> -------------------------------------------------------------------------- >>>> ---- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T >>>> Park in San Francisco, CA to explore cutting-edge tech and listen >>>> to tech luminaries present their vision of the future. This >>>> family event has something for everyone, including kids. Get more >>>> information and register today. http://sdm.link/attshape >>>> _______________________________________________ >>>> Qlandkartegt-users mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users >> >> ------------------------------------------------------------------------------ >> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in >> San Francisco, CA to explore cutting-edge tech and listen to tech >> luminaries present their vision of the future. This family event has >> something for everyone, including kids. Get more information and >> register today. http://sdm.link/attshape >> _______________________________________________ >> Qlandkartegt-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > > > > > ------------------------------------------------------------------------------ > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > _______________________________________________ > Qlandkartegt-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
