Settings and activity

  1. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  LINQPad Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tree Hugger commented  · 

    I've created a Dark Theme that skins the HTML results window - gets us a little closer.

    http://forum.linqpad.net/discussion/1022/dark-theme-for-linqpad

  2. 191 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  LINQPad Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Tree Hugger supported this idea  · 
    An error occurred while saving the comment
    Tree Hugger commented  · 

    I gave it a vote, but add that rather than lock in to GIST API, make management of "My Queries" into a "pluggable" feature.

    LINQPad probes the folder it runs in (or previous versions ran in) for an assembly that implements an interface like IUserQueryManager or similar and then loads that on startup to handle query management features like retrieving the collection to show in the tree and load / save scripts.

    That way, you could use anything as the backing store for your scripts.

  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  LINQPad Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tree Hugger commented  · 

    You could havea text box and a drop down menu with the following items in it: "Default (Instant Share)", "Custom Web API" and "Local Folder". For the first two options, LINQPad can post the script to either the default or specified URL. For the "Local Folder" option, the local path or UNC path entered into the text box is where the file is saved (LINQPad would need to generate the unique filename for any unsaved script, otherwise use the filename of the source script (and effectively create a copy of the script in the local folder).

    Tree Hugger shared this idea  ·