Re: [dotNetRDF-Develop] Store manager improvements

[Rob V. <rv...@do...>]

Hi Eugen

Thanks for the detailed email, yes there are advantages to a tabbed
interface though I suspect some users (like myself) may prefer to have the
MDI interface still.

What would be ideal from my perspective would be to integrate this such that
users can switch between the modes as desired, so users who prefer the
current interface can continue to use it and those that like the new
interface can use that instead.  Or even to have it such that you can dock
connections into a tabbed interface as and when desired.

The changes all sound useful but I haven't previewed them at all because I'm
afraid I'm not going to run a compiled executable from someone who's
emailing me for the very first time even if it does pass the virus checker.
If you can provide either a link to the git repository, a patch against
latest trunk or ideally a mercurial fork that would be fantastic.  We use
Mercurial for our development with our main repository hosted on BitBucket
at http://bitbucket.org/dotnetrdf/dotnetrdf ­ if you can fork the code on
BitBucket, transfer your changes to there and then open a pull request that
would be the best way for us to see and review your changes.

Btw this is a subscription list, your email was moderated through and you've
been CC'd on this initial reply but if you could subscribe at
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop so you can
participate in this discussion going forward without us having to manually
CC you each time that would be much appreciated.

Thanks,

Rob

From:  Eugen F <feu...@ya...>
Reply-To:  Eugen F <feu...@ya...>, dotNetRDF Developer Discussion and
Feature Request <dot...@li...>
Date:  Saturday, 7 December 2013 11:42
To:  "dot...@li..."
<dot...@li...>
Subject:  [dotNetRDF-Develop] Store manager improvements

> Hi,
> 
> I'm working with store manager and because of the midi interface it's
> difficult to interact with it, meaning each time i create a connection a new
> window is created, then when I run a query another window, rerun a query...new
> window, then close the one of the first query run and so on.
> 
> So i think the approach in sql server management studio or brightstardb
> polaris tool is much better. Both have tabs for each new connection, and when
> i rerun a query only results change (no new window).
> So i made the following changes:
> - when a connection is opened a new tab page is created and I add
> StoreManagerForm as a child to it
> - each tab has a close btn
> The rest of the functionality is the same except for query tab where:
> - i added a splitter control where panel 1 has query window , panel 2 has
> query results (both for graph and resultset)
> - i added a new button for orientation ( --| ) so we can change the
> orientation of the splitter ( vertical mode is v helpful on wide screens with
> few columns on results)
> - i removed "query" word from all buttons to occupy less space (i think it's
> obvious since we are in query window tab)
> - i changed AutoSizeColumnsMode to AllCells (previous was DisplayedCells but i
> had problems with it when large uri's where not in current view)
> 
> I also added a feature (in query tab) to expand a query for some subjects so i
> can see all the properties and values of those subjects. This allows a user to
> see similar results as sql server in case he has entities. For example if a
> user is using Entityframework api from brightstardb he can the select entities
> of rdf:type "Car" and see all car entities with values, in a table.
> - i added a new checkbox "AsEntities" that allows this feature when checked
> (it takes first variable from the current query as entity id/subject)
> It transforms user query to get all properties and the dynamically creates a
> query to get the entities.
> - i also added a numeric control next to the checkbox with default value of 1.
> This was necessary because in may case I have some predicates that are
> entities themselves and i need to filter those out. (a group by is used to
> filter predicates using that default value of 1)
> 
> I've attached the working version so you can play with it. I worked on a local
> git source control using latest 102 source code.
> Let me know what you think of the changes, and if it's ok, how to send/publish
> the source code. I've not really worked on any open source project so i don't
> know the flow.
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a
> single code base. Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk__
> _____________________________________________ dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop