Re: [Flamerobin-devel] FlameRobin roadmap [was: FlameRobin at the Firebird Conference]

[Milan B. <mi...@km...>]

Michael Hieke wrote:
> Ok, I will give you a list, probably not complete though.  See below why 
> I don't think it is purely a matter of on-list discussion or SF tracker.

I didn't say it is "purely a matter of on-list discussion or SF tracker". I 
wrote that we should first discuss ideas here, and then place them in tracker 
(for simple things) or Wiki (for complicated). I agree that Roadmap(tm) should 
go to the Wiki, but we should first discuss it here. We can throw all 1.0 
features on the heap, sort the order of making them, and then write a roadmap. 
Using Wiki for this process is not feasible IMHO, since we shouldn't place 
questions, opinions and doubts there. We should place the definite decisions.

> This list is in *my* personal order of importance:
> 
> 1) User management.  As this one is most important for me, I will/would
> start on it ASA the new DBH is in place.
> 
> 2) Creation, recreation and dropping of databases, while the
> registration info remains intact.
> 
> 3) Database property page (showing page size, buffer count, sweep
> interval, forced writes, ODS, transaction infos, ...)
> 
> 4) Editable grid.
> 
> 5) UI to register for and log events.

Ok, here's my list of features I need a lot. Of course, I will work on some 
others too:

1. DDL generator for each object

2. Generating "recreate view" script that drops all the dependencies (and 
privileges) and the view itself, creates the view, and get it all back. This 
requires that 1) is done

3. "Indices page" for table properties window. I'm not sure, but I think 
someone else also volunteered for this one?

4. Improve Drag&drop stuff for SQL Editor. It will be a very powerful feature, 
but it needs much more polish.

5. Logging changes to in-database table: flamerobin_log

6. Duplicate registration info: When you have the same server, user, pass, 
role, charset, just different database.

> Milan, I'm aware of the situation.  But in any case, I believe we need a 
> roadmap of some sort.  At least a very basic outlook on things to come - 
> even more for our (prospective) users than for ourselves - and we need 
> it in a place that is easy to find and to work with.

Agreed. Here we have your list and mine list. I'd like that Nando send his 
list too. Then, we should discuss if there is something else that also needs 
to go in 1.0, beside these items. After that, we create a Roadmap, and publish 
it in Wiki.

> IMHO there should be something on the homepage, and failing that in the
> wiki

Failing? I didn't get this one. IMHO, wiki is very good for these things since 
anyone of us can easily edit it. We just need a "Roadmap" link on main page 
that leads to Roadmap page in Wiki and we're done.

> - version 0.3, expected mid to end April 2005 (option dialog, execution 
> of selected statements, ...)
> - version 0.5, expected end of May 2005 (integration of new DBH object 
> structure, should facilitate faster development)
> - version 0.6, expected ??? (user management, ...)
> ...
> - version 1.0, expected [date of FB conference 2005]

For now, I'd leave dates out of it. We just need a roadmap: feature X in 
version A, feature Y in version B. We might put a date for 1.0 though.

-- 
Milan Babuskov
http://fbexport.sourceforge.net
http://www.flamerobin.org