we are further testing your framework and came over two questions recently:
Thanks in advance! Please continue your great work so far.
Hopefully yes, but it will not be based on the toolstrip since the toolstrip system is targeted for the second release – it’s a big beast. The BindingNavigator is essentially simply a toolbar that uses the navigation methods on the BindingSource.
How is work on the Binding Navigator Progressing?
Is it still on target for the release in November?
The BindingNavigator will be available before the release. Don’t know when yet.
We could add a logon setting that references a class but… VWG didn’t have an entry method like Application.Main. The URL was referring to a form so you could redirect to a logon form and then back to the request. Wisej is a lot more flexible, the entry Main method lets you decide what to show and how to authenticate. Gives you access to the browser, cookies, and session. We can’t create a form without creating the Application instance first, since it’s where everything is initialized (browser info, language, theme, settings) and that process calls Main(). We also have wired many events on the Application class that happen before and after every request.
So the issue with having a “logon wall” form is that it would have to happen before Main() is called. But then we’d have to manage also what happens if the authentication fails. Maybe through an event.
Basically it’s quite easy to replicate VWG logon form with few lines of code in Main(). But it would require some more thinking to add a specific workflow to Wisej. I’ll look into this further and keep you posted.