Page 12 of 14

newer version needs Qt5.

Posted: Thu 30 Jun 2016, 11:54
by Pelo
newer version needs Qt5. I think training with Qt4 version until somebody compiles QT5 is a good idea. Some prefer compiling than adding data in already existing database. That does not make such a progress. :!:
What database do you need ? Your home furniture, your car repairs, Your friends and their phone, Your customers, your pending posts in the forum, everything is already available, but needs some work . Barry Kauler asked some help from everybody about the pets, but our Puppy builders are so occupied to build their own puppies from Woof Ce.
Post scriptum :
If furthermore you run our wonderful Polar Qt005 build with so much care by Pemasu, no Qt SFS had to be added.
Nevertheless, i will feed back when my version 2.1 ready. I hate Dropbox.

To be done with Xenialpup 7.0.2.
Version 2.0
===========

[New Features]
- #11 #12 #16 New fields for web links and email addresses

[Improvements]
- Migration from Qt4 to Qt5 (User interface library)
- Updated Dropbox certificates (Old ones are valid until August 2016)
- Implemented database version checking and upgrading on format change
- Updated about dialog to include github project link
- Compiler warning fixes

You Tube Demo

Posted: Thu 30 Jun 2016, 14:22
by smokey01
I have a version 2.0 in my Fatdog64-700 repo. It does need the qt5-common package as well. http://smokey01.com/fd700/packages/ Are there any difference between 1.2 and 2.0? I didn't notice any.

Pelo did you say you have a version 2.1 of symphytum coming?

BTW thanks for the tip on TreeSize. I like it but it's a bit unstable when clicking on the Reload or skip directories buttons.

Exploring for Symphytum newer version for linuxian colleage

Posted: Thu 30 Jun 2016, 16:26
by Pelo
Exploring for Symphytum newer version for linuxian colleages caring of having on self latest version.
personnaly i have been using version one for three years without trouble. I entered some records for my own usage.
With Xenialpup 7.0.2 the final answer is that a driver is missing. Symphytum 2.0 refuse to restore my backup done with version 1

For people still having Windows beside Puppy Linux, taste Windows version to see what you could miss running version one with Puppy Linux.
I believe i was the only Puppy passenger having run Symphytum in the forum. Perhaps it's no worth loosing time..
Xenialpup still has some trouble with desktop. Everybody is busy.. in the electronic bulk.

i just took a glance at your fatdog 64 repository.

Posted: Thu 30 Jun 2016, 16:43
by Pelo
i just took a glance at your fatdog 64 repository.
With Puppy i decided to run only 32 bits.
Smokey01, i want to thank you here for your works. How often i found happiness in your stores :)
A database manager, again, a new one is born in QT5 PPM Xenialpup... you should not miss databases to fulfill in 2016 !
Screenshot Table created in five minutes importing data from .packages (tahrpup). You can do the same with OSMO (rename columns thru file .mo)

Symphytum is no longer free.

Posted: Sun 05 Mar 2017, 09:03
by Pelo
Symphytum is no longer free. you must pay for it, at least for Windows version (checked yesterday)

Posted: Sun 05 Mar 2017, 11:49
by Colonel Panic
Has everyone else given up on Portabase now? It may be more limited than other databases but I still use it, and perfectly contentedly. (BTW, yes it can import .csv files - that was how I created the data files I use in it now).

ToOpPy Linux, a Precise Puppy 5.7.1. portabase as Database

Posted: Tue 14 Mar 2017, 01:10
by Pelo
Argolance has included POrtabase in its brand new ToOpPy Linux, a Precise Puppy 5.7.1.

Posted: Tue 14 Mar 2017, 01:18
by slavvo67
Has everyone else given up on Portabase now?
Looks like Portabase hasn't been updated in about 4 years. Old isn't necessarily bad but looks like it's no longer being developed....

Posted: Wed 15 Mar 2017, 00:26
by Colonel Panic
Thanks for your replies. Portabase for Debian doesn't look like it's being actively developed either (it's still at version 2.1).

I'm only dimly aware of ToOpPy Linux but I may check it out if I get the time soon.

portabase is one of the worse

Posted: Sat 18 Mar 2017, 00:25
by Pelo
portabase is one of the worse, IMO, CSVpad does better :)

Symphytum topic in Business section

Posted: Mon 22 May 2017, 00:59
by Pelo
Symphytum topic in Business section Take a glance here

Posted: Mon 14 Aug 2017, 10:27
by smokey01
@musher0, some time ago you posted about fields.awk pet.
http://murga-linux.com/puppy/viewtopic. ... 741#874741
I just tried this again in Fatdog64-710 and it failed to add or modify a record. I'm pretty sure the attached is you original pet you provided. I couldn't find it from your post so I have attached it below.

I'm not sure if this is a Fatdog problem or I missed it before. After pressing enter on the last field when adding a record the terminal closes. Have you experienced this?

Cheers

Posted: Mon 14 Aug 2017, 12:18
by musher0
Hi Smokey.

I must confess I haven't used Ian's fileds.awk in a while.

I just tested it again. I changed the word "Duo" to "Duet" in the little CD.txt
database that's included in the pet, without any problem.

But fields.awk refused to edit anything before I selected an editor. I chose
leafpad as editor, and after that I was able to do what I wanted. Ian has
set the default editor to vim, we have to change it, we don't have vim on
Puppy.

Tell me how it goes?

BFN.

Posted: Mon 14 Aug 2017, 13:40
by smokey01
@musher0, found the problem.

I had a directory called tmp in /root that was created by another app. This prevented touch from creating a file called tmp in /root.

It's working again. Better yet my modified version is working.

Posted: Mon 14 Aug 2017, 14:11
by musher0
Excellent ! :)

Modified version ?

Posted: Mon 14 Aug 2017, 21:30
by smokey01
Yeah the original version menu wasn't in a very logical order and the terms used didn't make much sense, not to me anyway, so I changed it.

Posted: Mon 14 Aug 2017, 21:51
by 6502coder
smokey01 wrote:@musher0, found the problem.

I had a directory called tmp in /root that was created by another app. This prevented touch from creating a file called tmp in /root.
I noticed this too when I played with fields.awk. It's one of the first things I changed. Applications writing temporary files in the user's home directory is a BIG NO-NO in my book. That's what /tmp is for!

Posted: Tue 15 Aug 2017, 07:46
by greengeek
6502coder wrote:
smokey01 wrote:@musher0, found the problem.

I had a directory called tmp in /root that was created by another app. This prevented touch from creating a file called tmp in /root.
I noticed this too when I played with fields.awk. It's one of the first things I changed. Applications writing temporary files in the user's home directory is a BIG NO-NO in my book. That's what /tmp is for!
But wouldn't the same problem have occurred if the file already existed in /tmp? The way I read it the problem is the failure to detect if the file already exists (and choose a different file name or location if so...). Doesn't matter where the file already exists - the question is what to do about that.

Posted: Tue 15 Aug 2017, 20:04
by 6502coder
Well, first off, touch simply changes the timestamp on a file -- it doesn't matter whether the file already exists or not -- so there shouldn't have been a permissions problem, unless maybe some of that shady spot/fido business was involved.

Secondly, the shell provides mechanisms for making unique temporary file names, and that's what I always do. The mktemp command is probably the best way, but being old-school I usually use the classic method of including $$ (the process ID) as part of the file name.

Posted: Thu 17 Aug 2017, 20:59
by musher0
Hello everyone.

Have we forgotten that all Puppies have on board THE very powerful
sqlite3 database processor? ;)

Now that we're reminded, the next thing we lazy bones must do is learn
the sqlite language! :lol:

This one-liner will call it as a stand-alone window, like in the attached pic.

Code: Select all

urxvt -bg snow -fg "#432D1E" -g 90x28 +tr -cr orange -bd orange3 -b 20 -e sqlite3
You may fiddle with it as you like.

Please remember that If you use the above line in a script or make it into
a string, the foreground color ( -fg ) will have to be written '\#432D1E'. As
a general rule, in such situations, the # character of any hex color needs
to be escaped.

BFN