Re: [dba-dev] resigning as Base project lead (and as Base team member)

2010-03-02 Thread Reizinger Zoltán

Hi Frank,

Effective immediately, I'll be resigning from the position of Base's
project lead. Along with that, I will probably significantly reduce my
contribution to those lists, and definitely to overall Base.

   

Thanks to your work and help.
Best regards,
Zoltan

-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



[dba-dev] And now what?

2010-03-02 Thread Drew Jensen

Hi,

Ok - so 50% of the developer team is now gone.

Anyone want to take a crack at where that leaves us?

Come on now - everyone has had a day to think about it.

Drew


-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



[dba-dev] Re: And now what?

2010-03-02 Thread Andreas Saeger

Drew Jensen wrote:

Hi,

Ok - so 50% of the developer team is now gone.

Anyone want to take a crack at where that leaves us?

Come on now - everyone has had a day to think about it.

Drew


Drop embedded HSQLDB and make the rest working for experienced database 
developers (macros  forms) and for the ordinary mail merger (reliable 
filters, connections and sort orders).


My 2 Cents,
Andreas S.


-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



Re: [dba-dev] Re: And now what?

2010-03-02 Thread Fernand Vanrie

Andreas ,

Your proposal is maybe a bit to drastic,  but OO can, indeed, been a 
ideal frontend for any DB, included a Oracle Base :-), I hope they reed 
this dispared crys and gives us some exctra developer power.


Fernand

Drew Jensen wrote:

Hi,

Ok - so 50% of the developer team is now gone.

Anyone want to take a crack at where that leaves us?

Come on now - everyone has had a day to think about it.

Drew


Drop embedded HSQLDB and make the rest working for experienced 
database developers (macros  forms) and for the ordinary mail merger 
(reliable filters, connections and sort orders).


My 2 Cents,
Andreas S.


-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



[dba-dev] Re: And now what?

2010-03-02 Thread Andreas Saeger

Fernand Vanrie wrote:

Andreas ,

Your proposal is maybe a bit to drastic,  but OO can, indeed, been a 
ideal frontend for any DB, included a Oracle Base :-), I hope they reed 
this dispared crys and gives us some exctra developer power.




Yes, reduce Base to a better frontend.
Drop that embedded caricature of a database backend.
It is slow, unsafe (too many reports about data loss), insecure (no 
permissions) because behaves like an extension. It installs itself 
before you can use it and it gets repackaged when you close the 
document. May be it was the most efficient way to accomplish what the 
crowd shouted for (back in 2005) and certainly it was a nice toy for 
educational purposes but now let it rest in peace.
If all the other pieces would work more consistently (simpler rather 
than easier!) it could be a big improvement with less software to maintain.
Just leave the job to create a relational database up to the 
professionals and power users with their own tools for the respective 
database backend. There is no need for a table designer or relation 
editor in a mere frontend tool.



-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org



Re: [dba-dev] Re: And now what?

2010-03-02 Thread Rony G. Flatscher

On 3/2/2010 8:45 PM, Andreas Saeger wrote:
 Fernand Vanrie wrote:
 Andreas ,

 Your proposal is maybe a bit to drastic,  but OO can, indeed, been a
 ideal frontend for any DB, included a Oracle Base :-), I hope they
 reed this dispared crys and gives us some exctra developer power.


 Yes, reduce Base to a better frontend.
That was Base is already.
 Drop that embedded caricature of a database backend.
It's not a caricature. If it was one, then use MiniSQL or the like instead.

 It is slow, unsafe (too many reports about data loss), insecure (no
 permissions) because behaves like an extension. It installs itself
 before you can use it and it gets repackaged when you close the
 document. May be it was the most efficient way to accomplish what the
 crowd shouted for (back in 2005) and certainly it was a nice toy for
 educational purposes but now let it rest in peace.
For single-user installations it is more than enough. Besides it has
been improving over time.

 If all the other pieces would work more consistently (simpler rather
 than easier!) it could be a big improvement with less software to
 maintain.
 Just leave the job to create a relational database up to the
 professionals and power users with their own tools for the respective
 database backend. There is no need for a table designer or relation
 editor in a mere frontend tool. 
False. As a matter of fact I know of sites which used MS Access for
exactly those purposes (and not using the MSA's JetEngine).

Even if there is some frustration, keep it in proportion (and let those
gazillion single-users still have their database with Base).

In addition, it may be possible that developers from the community step
up/in?

---rony



-
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org