Raven UI

[Ayende Rahien]

Hi everyone,

Luke, Nick & Kevin came through and we now have 3 separate implemtentation of the basic UI.

That actually put us in the somewhat awkward position of having to choose one.

There is a phrase in Hebrew that comes strongly to mind; That is a rich guy's problem.

I am not used to having these sort of problems. 

You can look at the different implementations on github.

I would like to thank for all three of them for contributing, and even managing to do this in such a short time frame.

I am leaning toward Luke's implementation, but I would like further opinions.

Comments on Luke's implementation

=====================================

  I like the overall look & feel.

  The logo needs to go, we aren't an XML DB, after all :-)

  Documents tab - editing json - can you make the json pretty format?

  

  I really liked Nick's idea of showing statics as well, we should add a tab for that.

  

  I want to drive as much of the actual data in this interface from documents already in, so things like the help on the index

  or the documentation itself, should probably be documents and indexed.

  As a matter of fact, that might be a great sample app, especially since we are using a lot of JS templates already.

  

  Luke mentioned doing something like a view template, so a document can have meta property decsribing the way it will be shown in the UI.

  

  Query UI - we can show a list of the current indexes, but giving the user just a textbox might be too much.

  We can query the index for its list of fields, and for each field, a list of the top terms. That would allow intellisense like behavior.

  Of course, I say that as someone who has no idea what it means from the UI impl.

  

  

[Luke Hertert]

I just did a commit that implements basic querying.  So now you can:

• See basic stats
• List/View/Edit all documents
• Create/View/Edit all indexes
• Query on index -> List/View/Edit results 

The following items are on my todo list

• Delete document/index (delete on index not yet supported)
• A decent JSON viewer/editor
• Handle ajax completion notifications (create/update/delete)
• Documentation (once content is available)
• Index Builder
• Query Builder
• Document Templating

Let me know if you have any questions/comments.  My branch is located here. It's in VS 2010 format because that's all I have on this computer, sorry about that.  In order to run it and view my UI, you'll have to update RDB.Server\Responders\DivanUserInterfaceResponder to point to the path on your machine, and then follow the standard build steps.  You should then be able to browse to http://localhost:8080/ to browse the web ui.

Luke

[Luke Hertert]

Also if you want sample data to play with, there is a utility in there that will populate the db with northwind data.  it's something like this:

>rdbproj\Rhino.DivanDB.Importer\bin\Debug\Rhino.DivanDB.Importer.exe "rdbproj\Rhino.DivanDB.Server\Data" "rdbproj\NorthwindAsDocs"

[Ayende Rahien]

Index delete & index total query count have been implemented.

[Ayende Rahien]

Another thing to handle is showing the compilation errors if the user have a syntax error in the index.

2010/3/1 Ayende Rahien <aye...@ayende.com>