haefele / mileage Goto Github PK

Should be visible in the popup of the dashboard area.

• Text box where you can enter the search text
• After a delay of a couple hundred milliseconds the search should automatically fire
• Let the user press Enter or click the search button to fire it by hand
• Make 3 different views for the search result
  • Search results
  • Suggestions
  • No search results
• Make the suggestions clickable and automatically change the search text and re-search
• Make everything multilingual
• Loading overlay
• The user should be able to click a search result so we can open a new window with this element preselected or something like that
• Automatically place the cursor in the search text box
• Distinguish the 3 different views with a remarkable icon and show that icon maybe at the bottom of the view
• Activate smooth scrolling for the ListBoxEdits we use in the results and the suggestions.
• Maybe add RavenDB's highlighting feature to the search
• One search result item should be displayed with a nice icon indicating it's type (User, Driver, Vehicle, ...)
• In the nothing found view, display the original search text
• Show the user if we used the single suggestion we found
• Make sure the search result item is stretched inside the ListBoxEdit
• Move it into it's own namespace and rename it, because we want to reuse it in the future (In the dashboard for example)

This way we don't have our developer helper attributes in the actual build.

Maybe we can add social logins with facebook, twitter and co.
That is just way more convenient for the users.

We could even move loading of the license file into the startup-tasks.
Currently we do it with castle windsor IStartable implementations, but with a MileageServer class we have a better approach, because there we can actually control in which order these startup tasks happen.

This way we can reuse the server logic.

For example in creating the admin user we still need to create a user.
Or if we try to retrieve the global settings.

This way we can automatically download the newest version from the web-service.
Maybe even use something like Squirrel.Windows for client updates.

We have several ways to do that:

• If the administrator enters an @ before the domain (@mydomain.com), we don't need to add it ourselves
• If the users enters an @ after his username (test@), we don't need to add it ourselvs.
• Remove everything after the users @ character, and lets just append the admin setting

This way, the user will be able to login, even if he happens to miss click a key

This way we dont need to create them when we create the document store.

So the user is able to search for mercedes and find every mercedes car, or he searches for max and finds every driver named max.

So we can write custom layout panels that we can sell additionally.

With this we can give the user a better experience if he uses tags throughout the application.
So with the DevExpress Tag-ComboBox we can give the user a preview of tags that are already used.
Query for all tags, order them by their count and take the first 50 or 100.

• RavenDB map-reduce index for the tags and their count
• GetTagsCommand to retrieve a specific amount of tags
• HTTP endpoint to actually get the tags (Maybe in the search-controller like /Search/Tags?take=50)
• Client code to call the HTTP endpoint
• Create a basic tag cloud that we can use in the dashboard
• Make the tag cloud multilingual

Maybe something like RavenDB uses:
A weakly typed configuration from the app settings, and a strongly-typed one for the concrete values.

The issue is, if we logout, we don't have the credentials in the web-service client to authenticate the save request.
Saving the layout itself works fine, but the web-service call returns with the status code Unauthorized.

I know, we lose the ability to allow the user part-text searches, but well, then it is like that.
We can still allow him to allow suffix searches like apple*.
But like I wrote in the title, we get the ability for highlighting which is just awesome!

RavenDB had an error there, we need to wait for a new unstable release version.

Maybe we can create a stream of changes from the LocalizationManager (the language changes) and then merge them with our own data (for example a user object).
This way we have automatic updates of the DisplayName property without having to remember anything.

We need one sooner or later.
And now where we have a license http endpoint, why not create it now?

Use the DevExpress Deployment Tool to find out which assemblies we need.

Lets build it like RavenDB Migrations.

So we can reuse it more easy.

The dashboard should be one big DockLayoutManager where the user can add custom areas.
These areas itself are pre-created from us.
We might have areas like a Search or a Calendar or Statistics or something like that.

• Use a DockLayoutManager
• Save and restore the layout of the DockLayoutManager
• Make the areas bindable
• Create an http endpoint Dashboard where we store the dashboard items each use has
• If the user clicks the x close button of an area we remove it from our bound list
• Make a "New area" button into the ribbon
• The "New area" button should show a window where the user can enter a name and a kind of area he wants to add
• Make sure every area name is only used once by every user, he can't create two areas with the same name
• Make everything multilingual

I like the idea and this makes it so easy and simple to use logging.
Lets try it out and see if we should use something else in the future.

Remove the castle.logging package.

Lets change the login from a username to the email address.
This way, we have only one thing that needs to be unique: The email address.

We also can create an admin-setting, where the administrator can define a default email address domain like github.com.

If a user then tries to login with say apple we can extend the email to [email protected].

This way we can still seach for the full text like a firstname or lastname, even if it's longer than our 15 character gram limit.

This is a good tradeoff between searchability and disk-space.
And, more importantly, this way our suggestions will work without any issues, because we can search for the complete suggested text.