So the whole app is not made in chatgpt
It started like that 11 months ago though yes
I made the website and 7 pdf operations with chatgpt as a test to investigate chatgpts power and applications
Everything after that has been manual though and basically all the code has been changed by now
No paid backing, just running on donations at the moment.
I am tempted to try add a paid feature for AI integration or something or some high end office features as I have a fair few offices that use this software now.
But to be honest I would always want it free and it's just been a hobby
Yes our v2 version we are working on is this! We plan to completely migrate functionality to be all client with a server side one for API requests as well
I would do exactly what you have done here if I were the dev of the said app. But with the luxury of being an outsider, a user has expressed an inconvenience and it seems to make sense, then if I were to be the dev of the app here, wouldn't I go and create the ticket in whatever system with a link to this post instead of asking the user of the app to follow the red tape? I know there are places where this is not incentivised so this is a question for your org and not for you.
I see what you're saying and for simple features I agree
However Without the OP creating the ticket there can be no feedback look on the feature.
If i wanted it tested for their usecase, there input and confirmation on if its what they wanted and improvements for the workflow etc..
If I base the whole feature on this comment it could end up only doing half a job. Id rather have that communication loop open!
I tend to agree. As an open source dev myself, I avoid asking folks to create issues, as it puts a burden on the user. I’ve see some highly respected open source leads so this, and I’m
not faulting them, as I think they’re coming from a good place; it may be a difference of opinion on what’s best practice.
Not OP. My take is that if the requester can’t be bothered to create a GH issue, it’s likely that this isn’t really a problem for them. An annoyance possibly but has not risen to “pain” levels.
Dev here, totally could, we dismissed it at first as electron is quite bulky containing a whole chromium instance inside the exe. instead we kept it small as possible for the exe version
Truth is its not to hard to port to electron
We have plans for a full UI version in V2. We are releasing V1 (SPDF is currently in beta) sometime this month. But have begun work on a V2 port to different language and framework.
Dev here, totally could, we dismissed it at first as electron is quite bulky containing a whole chromium instance inside the exe. instead we kept it small as possible for the exe version
We have plans for a full UI version in V2. We are releasing V1 (SPDF is currently in beta) sometime this month. But have begun work on a V2 port to different language and framework.
As an alternative you could write some automation scripts to handle all the requirements for self hosted install. If you look at oogaboogas text-generation-webui [0] you can see what I mean. Although ease of install also leads to a larger user base, which can be a double edged sword for something as ubiquitous as a pdf app. It's much easier to get people to submit issues than to help solve them.
