Activity for fluxtion
-
fluxtion modified a comment on discussion How to
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...
-
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...
-
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...
-
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...
-
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...
-
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 relational DB 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...
-
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 relational DB 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...
-
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 relational DB 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...
-
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 relational DB 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...
-
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 relational DB 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...
-
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 relational DB 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...
-
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 relational DB 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...
-
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 relational DB 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...
-
We need to be able to add 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 relational DB 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...
-
We need to be able to add long text fields from the table (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 relational DB 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 --...
-
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...
-
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...
-
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...
-
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...
-
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...
-
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; just an archive of the raw project folder will do. Apologies if I'm wrong...
-
Fair enough. I look forward to seeing what you do with NSBase in the future and wish you the best of luck with the renovations, but 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; just an archive of the raw project folder will do. Apologies if I'm wrong...
-
I'm pretty sure the answer is no because the use of QSettings defaults to the registry, but is there any existing way to use Portabase portably across different Windows computers? I just wanted to make sure. If not, I might actually hack the feature in myself. QSettings seems to be a very simple class and I think that getting it working on Windows may be as simple as (though this would potentially break cross platform without a simple OS conditional): QSettings *settings = new QSettings("portabase.ini",...
-
I'm pretty sure the answer is no because the use of QSettings defaults to the registry, but is there any existing way to use Portabase portably across different Windows computers? I just wanted to make sure. If not, I might actually hack the feature in myself. QSettings seems to be a very simple class and I think that getting it working on Windows may be as simple as (though this would potentially break cross platform without a simple OS conditional): QSettings *settings = new QSettings("portabase.ini",...
-
I'm pretty sure the answer is no because the use of QSettings defaults to the registry, but is there any existing way to use Portabase portably across different Windows computers? I just wanted to make sure. If not, I might actually hack the feature in myself. QSettings seems to be a very simple class and I think that getting it working on Windows may be as simple as (though this would potentially break cross platform without a simple OS conditional): QSettings *settings = new QSettings("portabase.ini",...
-
I'm pretty sure the answer is no because the use of QSettings defaults to the registry, but is there any existing way to use Portabase portably across different Windows computers? I just wanted to make sure. If not, I might actually hack the feature in myself. QSettings seems to be a very simple class and I think that getting it working on Windows may be as simple as (though this would potentially break cross platform without a simple OS test): QSettings *settings = new QSettings("portabase.ini",...
-
delete
-
I'm pretty sure the answer is no because the use of QSettings defaults to the registry, but is there any existing way to use Portabase portably across different Windows computers? I just wanted to make sure. If not, I might actually hack the feature in myself. QSettings seems to be a very simple class and I think that getting it working on Windows may be as simple as (though this would potentially break cross platform without a simple OS test): QSettings *settings = new QSettings("portabase.ini",...
-
I'm pretty sure the answer is no because the use of QSettings defaults to the registry, but is there any existing way to use Portabase portably across different Windows computers? I just wanted to make sure. If not, I might actually hack the feature in myself. QSettings seems to be a very simple class and I think that getting it working on Windows may be as simple as (though this would potentially break cross platform without a simple OS test): QSettings *settings = new QSettings("portabase.ini",...
-
I'm pretty sure the answer is no because the use of QSettings defaults to the registry, but is there any existing way to use Portabase portably across different Windows computers? I just wanted to make sure. If not, I might actually hack the feature in myself. QSettings seems to be a very elegant class and I think that getting it working on Windows may be as simple as (though this would potentially break cross platform without a simple OS test): QSettings *settings = new QSettings("portabase.ini",...
-
double post delete
-
double post delete
-
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 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...
-
Delete
-
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.
-
(Actually it's probably UTF-16 by default if the registry is involved!)
-
This appears to be the issue: https://stackoverflow.com/questions/4809298/lazarus-dbgrid-showing-memo-as-the-value-of-string-fields-in-sqlite-3 Idk if anyone else is experiencing this problem though, and if not, why not.
-
I found your PAF portable package myself and figured out how to upgrade it to 1.9.11 so that's all good! Thanks for making it portable!! :)
-
I'm pretty sure the answer is no because the use of QSettings defaults to the registry, but is there any existing way to use Portabase "portably" across different computers? I just wanted to make sure. If not, I might actually hack the feature in myself. QSettings seems to be a very elegant class and I think that getting it working on Windows may be as simple as (though this would potentially break cross platform without a simple OS test): QSettings *settings = new QSettings("portabase.ini", QSettings::IniFormat);...
-
Usage
-
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.
-
Okay, upon further testing, I imported the sample videotheque database and had the same issue while attempting to edit synopses in table view. Hmm.
-
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...
-
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...
-
Source code missing :(
-
Usage
-
Support
-
Installing
-
Development & To-do
1
