Hello,
I regret that I can't speak French but merci beaucoup pour NSBase. I'm a fellow OSS developer and I've been very impressed with what you've achieved with NSBase on your own, and over such a long period of time. Your commitment is fantastic.
I'm having trouble editing Long Text fields in table view (see attached screenshot), When I attempt to edit the "Mechanism of action" field, which is a 500 character Long Text field, the text "(MEMO)" or "(memo)" appears and there's no way to enter any other text. Short Text fields work fine - I press enter or double click on them and then I get a cursor to enter text, as expected - but I cannot even get a cursor on my Long Text fields. As you can see, I previously managed to enter data into this column, when I first created it, but something has clearly changed and I don't know what.
For clarification, what are the underlying differences, if any, between Short Text and Long Text apart from the 255 character limit? What is the significance of the "(MEMO)" placeholder? Is Long Text implemented differently in the underlying SQLite db?
Any help would be greatly appreciated. I'm trying to use NSBase for work in neuroscience academia and I really hope I can figure this out.
Best wishes,
Elliott
P.S. Is there any current way to make NSBase portable? Never mind. I found your PAF portable package and figured out how to upgrade it to 1.9.11 so that's all good! Thanks for making it portable!! :)
One more thing, I noticed that the taskbar thumbnail captions/titles (see image) are always "NSBase" instead of the actual window titles. I was going to look into the code to see why this was the case (this isn't the default shell API behaviour, which suggests that it's either a FPC/Lazarus quirk or something you've done), but then I realised that I can't find the code anywhere. Where is the source archive or repo?
Btw, I forgot to mention that I'm perfectly happy to fix the problem myself if you upload the source code. It's kinda annoying that the project is labeled as BSD-licensed but there's no actual source release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, friendo, thanks for responding. That's useful to know but it'd be trivial to fix the code so as to make Long Text fields editable in table view too.
My request to @surfvite is please either fix this or upload the code and I'll fix it for you! Both are good. Although please release the source anyway because I want to help improve a few things.
Cheers lads.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
I'm quite busy at the moment with more basic things (house building), I plan to get back to 100% on NSBASE this winter (France)
I saw in this post that "feen" answered correctly, I will see to add a memo field editor, I will also see this display problem in the taskbar. ...
Last edit: neuts-jl 2021-10-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fair enough. I look forward to seeing what you do with NSBase in the future and wish you the best of luck with the home renovations. For the work that I'm doing, I can't just put off finding a database solution for months. Either I fix it myself or use something else -- those are my only options.
I'll make the request very direct: can you please upload a source code archive? It doesn't have to be in a version controlled format or cleaned up in any way; just an archive of the raw project folder will do. Apologies if I'm wrong but it seems like you're deliberately evading my questions about the SC. You can't label a project as open source, claim its under an OS license, create an OS project on Sourceforge, and then not actually share the code. It's morally wrong and I think it's actually against the Sourceforge TOS (but I'm not going to be a snitch about it -- all I will do is implore you to release it). Obviously, I'll share any improvements I make back upstream, and I certainly won't be attempting to fork the project.
Last edit: fluxtion 2021-10-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We need to be able to add/edit long text fields from the table view (because we rely on being able to view many rows at the same time), so basically the same problem as my original post.
Later on, I also need to hook the database layer up directly to a client-server DB backend instead of relying on SQLite files (which will obviously require some significant modifications). When I initially found NSBase and promoted its use for our project, I just assumed that I'd be able to modify it to meet our needs -- it was a BSD-licensed Sourceforge project so I didn't even bother to look for a SC archive before I needed it. I didn't realise it would turn out to be such an issue.
For us, the OS part is intrinsically important. If we end up using NSBase, we're going to be using it for many years and with large and complex datasets. In the future, we'll probably have to modify the code in ways I haven't even foreseen yet to make it work better with our datasets and people. Only a true OS project gives me the guarantee I need that we'll be able to do that, regardless of how far into the future it may be.
If you're not going to share the source, at least change the license on the project page so that it's not such a blatant lie. There's absolutely nothing wrong with writing closed-source freeware if that's what you want to do, but be honest with people about it.
Regardless of what you do, you've still created a great little tool that you can be proud of. If it is closed-source, I'll certainly still use it at home as a personal database for small key-value type stuff. I just couldn't use it in a professional setting. In the professional world, you'd have to be crazy to rely on a freeware tool written by one guy as a hobby -- you either need commercial tools with support contracts backed up by big companies or OS tools that you can reasonably take on in-house.
Last edit: fluxtion 2021-10-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I had put a license at random, knowing that I will put the sources on this site after I have solved the problem of the generated code encryption, the key is somewhere in the code.
I am open to any contribution; nsb code, translation ....
I changed the license, knowing that the use and distribution of runtime is free, as well as the nsb sample applications, lua libraries .....
I will modify nsbase this weekend to be able to directly modify the memo fields
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I regret that I can't speak French but merci beaucoup pour NSBase. I'm a fellow OSS developer and I've been very impressed with what you've achieved with NSBase on your own, and over such a long period of time. Your commitment is fantastic.
I'm having trouble editing Long Text fields in table view (see attached screenshot), When I attempt to edit the "Mechanism of action" field, which is a 500 character Long Text field, the text "(MEMO)" or "(memo)" appears and there's no way to enter any other text. Short Text fields work fine - I press enter or double click on them and then I get a cursor to enter text, as expected - but I cannot even get a cursor on my Long Text fields. As you can see, I previously managed to enter data into this column, when I first created it, but something has clearly changed and I don't know what.
For clarification, what are the underlying differences, if any, between Short Text and Long Text apart from the 255 character limit? What is the significance of the "(MEMO)" placeholder? Is Long Text implemented differently in the underlying SQLite db?
Any help would be greatly appreciated. I'm trying to use NSBase for work in neuroscience academia and I really hope I can figure this out.
Best wishes,
Elliott
P.S. Is there any current way to make NSBase portable?
Never mind. I found your PAF portable package and figured out how to upgrade it to 1.9.11 so that's all good! Thanks for making it portable!! :)
Last edit: fluxtion 2021-10-02
double post delete
Last edit: fluxtion 2021-10-05
Okay, upon further testing, I imported the sample
videothequedatabase and had the same issue while attempting to edit synopses in table view. Hmm.One more thing, I noticed that the taskbar thumbnail captions/titles (see image) are always "NSBase" instead of the actual window titles. I was going to look into the code to see why this was the case (this isn't the default shell API behaviour, which suggests that it's either a FPC/Lazarus quirk or something you've done), but then I realised that I can't find the code anywhere. Where is the source archive or repo?
Thanks.
double post delete
Last edit: fluxtion 2021-10-05
Btw, I forgot to mention that I'm perfectly happy to fix the problem myself if you upload the source code. It's kinda annoying that the project is labeled as BSD-licensed but there's no actual source release.
Hi, can't recall the reasons behind it, but your're able to edit the MEMO field only using that field in a Form.
Hi, friendo, thanks for responding. That's useful to know but it'd be trivial to fix the code so as to make Long Text fields editable in table view too.
My request to @surfvite is please either fix this or upload the code and I'll fix it for you! Both are good. Although please release the source anyway because I want to help improve a few things.
Cheers lads.
Hello
I'm quite busy at the moment with more basic things (house building), I plan to get back to 100% on NSBASE this winter (France)
I saw in this post that "feen" answered correctly, I will see to add a memo field editor, I will also see this display problem in the taskbar. ...
Last edit: neuts-jl 2021-10-17
Fair enough. I look forward to seeing what you do with NSBase in the future and wish you the best of luck with the home renovations. For the work that I'm doing, I can't just put off finding a database solution for months. Either I fix it myself or use something else -- those are my only options.
I'll make the request very direct: can you please upload a source code archive? It doesn't have to be in a version controlled format or cleaned up in any way; just an archive of the raw project folder will do. Apologies if I'm wrong but it seems like you're deliberately evading my questions about the SC. You can't label a project as open source, claim its under an OS license, create an OS project on Sourceforge, and then not actually share the code. It's morally wrong and I think it's actually against the Sourceforge TOS (but I'm not going to be a snitch about it -- all I will do is implore you to release it). Obviously, I'll share any improvements I make back upstream, and I certainly won't be attempting to fork the project.
Last edit: fluxtion 2021-10-18
hello ,
what problem is blocking you for your development ?
you indicated "For the work i do i can't wait months to find a database solution"
We need to be able to add/edit long text fields from the table view (because we rely on being able to view many rows at the same time), so basically the same problem as my original post.
Later on, I also need to hook the database layer up directly to a client-server DB backend instead of relying on SQLite files (which will obviously require some significant modifications). When I initially found NSBase and promoted its use for our project, I just assumed that I'd be able to modify it to meet our needs -- it was a BSD-licensed Sourceforge project so I didn't even bother to look for a SC archive before I needed it. I didn't realise it would turn out to be such an issue.
For us, the OS part is intrinsically important. If we end up using NSBase, we're going to be using it for many years and with large and complex datasets. In the future, we'll probably have to modify the code in ways I haven't even foreseen yet to make it work better with our datasets and people. Only a true OS project gives me the guarantee I need that we'll be able to do that, regardless of how far into the future it may be.
If you're not going to share the source, at least change the license on the project page so that it's not such a blatant lie. There's absolutely nothing wrong with writing closed-source freeware if that's what you want to do, but be honest with people about it.
Regardless of what you do, you've still created a great little tool that you can be proud of. If it is closed-source, I'll certainly still use it at home as a personal database for small key-value type stuff. I just couldn't use it in a professional setting. In the professional world, you'd have to be crazy to rely on a freeware tool written by one guy as a hobby -- you either need commercial tools with support contracts backed up by big companies or OS tools that you can reasonably take on in-house.
Last edit: fluxtion 2021-10-21
Hello,
I had put a license at random, knowing that I will put the sources on this site after I have solved the problem of the generated code encryption, the key is somewhere in the code.
I am open to any contribution; nsb code, translation ....
I changed the license, knowing that the use and distribution of runtime is free, as well as the nsb sample applications, lua libraries .....
I will modify nsbase this weekend to be able to directly modify the memo fields