1. I installed Glom to see what its about.
2. I launch it.
3. I get a wizard.
4. I choose 'New from example'. It sounds like a good way to find out what its about.
5. I choose example_smallbusiness.glom
6. It asks for a name, I choose: 'test'
7. I choose 'create database in its own folder, to be hosted on this computer'
8. I click 'save'
9. First User wizard runs: I setup a name and password for the database
10. I click 'create'
11. I get a 'proccessing' window: its never done
Now reading this bug-report I understand whats its about. But the fact that I had to go here to find out is a bug.
This is a blocker. Glom will only be used by people who already know it. Others will just uninstall it, or post bug reports. And instead of just making postgre-sql a dependency, you will spent all day marking bug reports duplicate to this one.
On the other hand:
- I don't want to install a full fledged database server
- Well: i dont want it to always run, just when I launch glom
- Why not just default back to the 'old way' mentioned above?
As of 20/2/2007 this bug is still very valid, and something needs to be done. (or at least get the package out of add/remove)
1. I installed Glom to see what its about. smallbusiness. glom
2. I launch it.
3. I get a wizard.
4. I choose 'New from example'. It sounds like a good way to find out what its about.
5. I choose example_
6. It asks for a name, I choose: 'test'
7. I choose 'create database in its own folder, to be hosted on this computer'
8. I click 'save'
9. First User wizard runs: I setup a name and password for the database
10. I click 'create'
11. I get a 'proccessing' window: its never done
Now reading this bug-report I understand whats its about. But the fact that I had to go here to find out is a bug.
This is a blocker. Glom will only be used by people who already know it. Others will just uninstall it, or post bug reports. And instead of just making postgre-sql a dependency, you will spent all day marking bug reports duplicate to this one.
On the other hand:
- I don't want to install a full fledged database server
- Well: i dont want it to always run, just when I launch glom
- Why not just default back to the 'old way' mentioned above?
As of 20/2/2007 this bug is still very valid, and something needs to be done. (or at least get the package out of add/remove)