When you check this option, the comments are converted from RTF text into plain text. So if you want RTF formated comments you must leave this checkbox unchecked. Or do you mean that the MySQL database doesn't accept the dump file if the comments are RTF formatted? In this case, please send me the dump file and I'll check where the problem could be.I wanted to try RTF conversion, however the mysql dump doesn't work when the convert to RTF is checked in divinglog
phpDivingLog
This is perfect Just send me an e-mail with your preffered passwordNameless wrote: I would like to contribute to this project.
I already did change some things for my own site, but it would be easier, if changes were made at a central repository.
Ofcourse this is password protectedI already configured my SVN client to get the files from your server, but at the moment it seems that one needs a password to update those files.
Jeps mysql didn't accept the dump directly from divinglog. So I'm gonna try the file import so I can see what the error is.divinglog wrote:Or do you mean that the MySQL database doesn't accept the dump file if the comments are RTF formatted? In this case, please send me the dump file and I'll check where the problem could be.I wanted to try RTF conversion, however the mysql dump doesn't work when the convert to RTF is checked in divinglog
Hi guys,
I really like phpdivinglog. I haven't installed the newest update yet, but one thing I did add to the version I'm using is multiple user support so I can show either my husband's dives or my dives. All I did was add an extra field in the logbook table labeled "user id", which is based on the user ids in the Personal table. When I export the SQL from a logbook in Diving Log, I just add on the userid of the person whose dive it is. I then changed the php a little bit to ask on the front page which person's dives you want to see.
I really like phpdivinglog. I haven't installed the newest update yet, but one thing I did add to the version I'm using is multiple user support so I can show either my husband's dives or my dives. All I did was add an extra field in the logbook table labeled "user id", which is based on the user ids in the Personal table. When I export the SQL from a logbook in Diving Log, I just add on the userid of the person whose dive it is. I then changed the php a little bit to ask on the front page which person's dives you want to see.
Would be a nice addition. Maybe it is possible to export a general custom field. Where you could enter a user_idmhedstrom wrote:Hi guys,
I really like phpdivinglog. I haven't installed the newest update yet, but one thing I did add to the version I'm using is multiple user support so I can show either my husband's dives or my dives. All I did was add an extra field in the logbook table labeled "user id", which is based on the user ids in the Personal table. When I export the SQL from a logbook in Diving Log, I just add on the userid of the person whose dive it is. I then changed the php a little bit to ask on the front page which person's dives you want to see.
Overview display
I'm working on the backend of phpdivinglog and I really want to change something on the table view.
So searched for better ways to display the data. Right know I have this version:
http://rob.lensen.nu/divelog_dev/
Just to give you an idea, what do you think?
So searched for better ways to display the data. Right know I have this version:
http://rob.lensen.nu/divelog_dev/
Just to give you an idea, what do you think?
-
- Posts: 228
- Joined: Sun Jun 11, 2006 09:24
- Location: Frankston South, Victoria, Australia
- Contact:
G'day,
The phpDivingLog that this all started from came with some 3rd party code in it for supposedly converting RTF data that had made it into the MySQL database back to HTML on output. But it just didn't work. I tired all sorts of things but no go. It seems that all of the code around to convert RTF to HTML is pay per licence, which doesn't suit phpDivingLog.
So I settled for having my comments in plain text in PC Diving Log, in Pocket PC Diving Log, and in phpDivingLog.
I guess it would be nice if we could have better control over the formatting of comments. Especially being able to put HTML links into them. But I'd only use it if it worked across all three of the "platforms".
Best Regards, Lloyd Borrett.
The phpDivingLog that this all started from came with some 3rd party code in it for supposedly converting RTF data that had made it into the MySQL database back to HTML on output. But it just didn't work. I tired all sorts of things but no go. It seems that all of the code around to convert RTF to HTML is pay per licence, which doesn't suit phpDivingLog.
So I settled for having my comments in plain text in PC Diving Log, in Pocket PC Diving Log, and in phpDivingLog.
I guess it would be nice if we could have better control over the formatting of comments. Especially being able to put HTML links into them. But I'd only use it if it worked across all three of the "platforms".
Best Regards, Lloyd Borrett.
Only an idea, but what about using Ajax? I didn't worked with that so I can't say how difficult it is to implement, but I've seen some great online apps using this technique.I'm working on the backend of phpdivinglog and I really want to change something on the table view.
The table view on http://rob.lensen.nu/divelog_dev/ uses ajax (btw just look with firefox. I need to fix things for IE)divinglog wrote:Only an idea, but what about using Ajax? I didn't worked with that so I can't say how difficult it is to implement, but I've seen some great online apps using this technique.I'm working on the backend of phpdivinglog and I really want to change something on the table view.
(see http://www.gurusistemas.com/indexdatagrid.php for details on how ajax is used in the table view)
If people like this way is display I will continue with this implementation. There are plenty of frameworks available for doing this job, however this is one of the best imo.
Re: Dutch translation for phpDiveLog
I will merge it into the subversion (bedankt Vasco)
Current devopment looks like this:
http://rob.lensen.nu/divelog_dev/
Re: Dutch translation for phpDiveLog
Well, you asked for opinions earlier and quite frankly, I don't like the new datagrid.Inferno wrote: Current devopment looks like this:
http://rob.lensen.nu/divelog_dev/
Not only will it be harder to maintain a single theme throughout the complete site, but it makes one page look bulky and all other pages delicate.
I really liked the original simple layout and adding another framework (you did add Smarty before) makes things difficult for those who would like to contribute to the project (like me) but don't have the time to learn how to use that framework (like me).
I would prefer leaving the layout as simple as possible. That would leave room for the simple and fast development of different themes and it would free time for 'real' improvements like e.g. multiuser support, which I find more important than the look of a single table...
Best regards.