Logbook Konni for OpenCPN

[CeesH]

Hi Konni,

How to check crew In and Out. For example Logbook start in Gibraltar. on Madeira Captain checks Out new Captain checks In. On Tenerife 2 Crew members check Out and 1 new Crew member checks In. Etc...

How to do this.

Regards,
CeesH

[konni]

How to check crew In and Out. For example Logbook start in Gibraltar. on Madeira Captain checks Out new Captain checks In. On Tenerife 2 Crew members check Out and 1 new Crew member checks In. Etc...

Hello CeesH,

the crewlist (ver. 0.915) stores the actuall condition on board only.
the data isn't stored with a from/to date or from/to harbour and it's not planned to add this.

if you change the crew 1:1 overwrite the names and other data.
the changed names appear also in the watchlist-column.

when a crewmember leaves the boat delete the line (rightclick) in crewlist, the
entry in watchlist deletes also.

If a crewmember enters or leaves the boat make a entry in the logbook.


best regards,
konni

[konni]

Hello,

Logbook ver. 0.915 and FindIt ver. 0.7 are compiled with the
new OCPN Beta 1511.

You can download them here

best regards,
konni

[CeesH]

Thanks Konni

CeesH

[Gilletarom]

Hello Konni,

I try the new version V 915 and FindIt-0.7 with the last bêta 260-1511. It seem that all is Ok.

Best regards

Gilletarom

[Gilletarom]

Hello Konni,

It's a long time that nobody write here ...

I have tested your logbook with OpenCPN 260-1524. It seem that it run Ok.

Now, SethDart having updated for plug'in VDR for OpenCPN 260-1524, it was possible to test your plugin Logbook with NMEA data.

I therefore started the timer and I launched VDR that provides NMEA data recorded during a previous navigation.

This seems to work.

But, when you want to stop your plugin, it is not possible. If you click on the red cross, the plug-in closes but opens again automatically because the timer has not been arrested previously.

It took me a while to understand that.

Could you modify your plugin to set the timer stops when closing the plug-in with the red cross.

Thank by advance.

Gilletarom.

[konni]

Hello Gilletarom,

Originally Posted by Gilletarom

Could you modify your plugin to set the timer stops when closing the plug-in with the red cross.

sure i could do that, but my opinion is, it produces a lot of save/load data overhead.

if you start the logbook all data is loaded and kept in the background.
this could take a while if the logbook has e.g. 800 lines.
now you start a timer.
when you hit the close button now, all data must be saved and the timer has to stop (if i follow your idea).
but now you can wait forever for a timer-event.

in fact the window is only hidden, so when a event occurs the plugin
has not always to save/load data and the window shows up immediatly.

i think it's easier to simply stop the timer before closing the window.

best regards,
konni

[cagney]

konni

I can't find the source code for your FindIt module? Is it available?
I would like to est it on Linux.

Thomas

[nohal]

https://github.com/konnibe/FindIt_pi

[konni]

Hello,

logbook ver. 0.916 is ready for download here.

it uses now the routepoints and the active route of the main-prg
(thank's to Dave).

to test it:

1. in logbook options check "If waypoint arrived".
2. create a dummy-route with 3 routepoints and activate the route.
3. set with a right click your boat to the first routepoint
4. open the logbook,the active route name appears in the first column.
5. skip the next routepoint in the rightclick-menu and take a look at the remarks.
6. set boat to the last routepoint and look at the remarks.

best regards,
konni

[fulup]

Finally I sucessed to compile it on Linux (Ubuntu) but it is not as simple as it should. It would be good the README to include basic Linux installation instructions. I also had few errors that should be simple to fix.

• where to find the source code
• where to place the code in OpenCPN source tree
• git and cmake instruction

While it may looks obvious for some people that are cmake expert for the other, the error message is not very helpul

1. get source from https://github.com/konnibe/LogbookKonni/zipball/master
2. unzip in your opencpn/plugins/ directory
3. cd konnibe-LogbookKonni
4. mkdir Built
5. cd Built
6. cmake -D PREFIX_PLUGINS=/usr/local/lib/opencpn ..
7. sudo mv liblogbookkonni_pi.so /usr/local/lib/opencpn

Provide dependencies, as it looks they are more than the one attached to OpenCPN (see final error)

Note:

• I had one errors in cmake

1. INCLUDE(${wxWidgets_USE_FILE})
2. PREFIX_PLUGINS not set

• One error at complilation time

1. gtk/gtk.h not found

Had to change

1. Cmake command line: Add "-D PREFIX_PLUGINS=/usr/local/lib/opencpn" before final ".."
2. File CMakeLists.txt: Line 48 added FIND_PACKAGE(wxWidgets REQUIRED) before NCLUDE(${wxWidgets_USE_FILE})
3. File CMakeLists.txt: Line 23 added

find_package(PkgConfig)
pkg_check_modules(GTK gtk+-2.0)
include_directories(${GTK_INCLUDE_DIRS})

Note: I tried this on Ubuntu LTS 10.04 with the latest git source from OpenCPN and from Konni Logbook.

[nohal]

If you are able to build OpenCPN itself following Compiling - Linux | Official OpenCPN Homepage, building the plugin is trivial and most of the steps described in your post are not needed

cd ~/source/OpenCPN/plugins
git clone https://github.com/konnibe/LogbookKonni.git LogbookKonni_pi
cd ../build
cmake ..
cmake --build . --target logbookkonni_pi

Pavel

The produced library is plugins/LogbookKonni_pi/liblogbookkonni_pi.so in the build directory

[fulup]

You're right your method work, the hack I had to do come from the fact that I compiled the plugin interdependently of OpenCPN source tree.

This being said, I still think that it should be written in the read me. It would avoid people like me to start searching the wrong route.

[nohal]

fulup...
It actually is written there, you just have to read it

https://github.com/nohal/LogbookKonn.../master/README

Pavel

[fulup]

I'm a simple personne, I click on OpenCPN official web site, look for download plugin section which send me to https://github.com/konnibe/LogbookKonni

This is where i would like to find the installation information, don't you think it is the logical place, where it should be ?