Live data from Hacker News

BeeBase, a programmable relational database with graphical user interface

beebase.sourceforge.io

101–110 of 110 posts

Re: BeeBase, a programmable relational database with graphical user interface

#101
post #99
post #98

Earlier quoted context omitted.

they could, but you would have to do pretty much everything from scratch - set up a server, figure out client-server communication, handle state changes, flaky networks, etc. with a webapp you get a lot of that infrastructure "for free" insofar as the entire stack is designed around the multiuser experience, and you are going with the grain of the platform. not to mention all the frameworks and libraries that help yo…

Desktop apps can use HTTP(/grpc/rest/graphql) for communication just fine, that's not really problem.

true, and that saves you having to write the frontend in html/css/js, but you still need to write an api-only web app to act as your backend. the "going with the grain" path for a desktop app is to be running on a local machine, with all data stored locally, and interacting with the user over a keyboard and mouse, not the network.

you can absolutely write a desktop app as a web app client, but it's a lot less well-lit a path than either writing a standalone desktop app, or writing a full-stack web app.

Re: BeeBase, a programmable relational database with graphical user interface

#102
post #100

Earlier quoted context omitted.

The people who use the software of the people who write the software. If the word "customers" is triggering, the argument holds just as well as for "users".

Why are you dodging the question? Who are you talking about, and why? It's not the commenters above that complained about the error message, they aren't users and highly unlikely to ever become users. Instead you've brought in some unspecified other for unspecified reasons.

I answered all of your questions directly.

Re: BeeBase, a programmable relational database with graphical user interface

#103
post #25
post #23

Earlier quoted context omitted.

It's explained on page 8 of the manual, in the tutorial section.

Exactly, it's a bad error message if you need to read 8 pages of tutorial to get that basic feedback.

There is only so much room in one page of a tutorial; not everything can be on page 1.

Re: BeeBase, a programmable relational database with graphical user interface

#104

Ok so first feedback. Launched app. Went to create a new table. Entered name : "users". Got error "Invalid name". Got confused, whats illegal about the name. After some time figured out that name must start with UPPER case latter. This could have been the error message instead of generic "Invalid name".

It's a poor restriction. The table name I want is 収入. Now what?

Re: BeeBase, a programmable relational database with graphical user interface

#106
post #100

Earlier quoted context omitted.

Why are you dodging the question? Who are you talking about, and why? It's not the commenters above that complained about the error message, they aren't users and highly unlikely to ever become users. Instead you've brought in some unspecified other for unspecified reasons.

I answered all of your questions directly.

No, you did not.

Re: BeeBase, a programmable relational database with graphical user interface

#107

Earlier quoted context omitted.

> guess I missed it, im used to scrolling and seeing screenshots and features on splash page. Sigh... A generation conditioned by horrible endless-scroll single-page "applications" (web sites).

Sure buddy. I began using the web in 1996 and I had the same reaction.

> I began using the web in 1996

BTW: So did I. Or if it was '95.

Re: BeeBase, a programmable relational database with graphical user interface

#108

Ok so first feedback. Launched app. Went to create a new table. Entered name : "users". Got error "Invalid name". Got confused, whats illegal about the name. After some time figured out that name must start with UPPER case latter. This could have been the error message instead of generic "Invalid name".

True, this could be improved. Note though that if you hover over the text entry box, there is a tool tip that says this:

Name of the field. Must begin with an uppercase letter followed by further letters, digits or underscore characters. Non-ASCII letters like German umlauts are not allowed.

Re: BeeBase, a programmable relational database with graphical user interface

#109
post #70

From a cursory glance, the Lisp dialect that BeeBase is using is closest to Common Lisp, is that correct? Sorry, I'm not an expert on CL, but it would be great to see a quick comparison of BeeBase Lisp with other popular Lisp dialects, like this: https://clojure.org/reference/lisps

Yes, it is close, although it is completely homebrewn and lacks a lot of functionality of common lisp. Think of it as taking the syntax from lisp, some basic lisp functions, and then adding functionality for programming your database.

Re: BeeBase, a programmable relational database with graphical user interface

#110

Apparently saved project created with BeeBase is basically a sqlite DB, that you can open with any sqlite browser. So i think a lot of value could come from standardised sqlite format, upon which you could build different UI's to manipulate the content of said sqlite DB and then provide a app that would build client UI based on content of same sqlite file.

Yes, BeeBase uses the sqlite3 file format. You can make changes to the sqlite3 file with other SW, but there are some rules to be followed if you want BeeBase to work with those changes. More info is in the manual here: https://beebase.sourceforge.io/index.php?page=documentation&...
Post reply on HN