[Qt-creator] Cross-debugging Win-Linux // project-session issue

[andy fillebrown]

I tend to agree with Patrick.  I rarely launch and app to open a file
from inside it (unless I absolutely have to).  I prefer double
clicking a file in the file explorer.  When I do this with VS, no
problem -- session info loads.  With QtCreator, session info does not
load.  It would be nice if it did.

It's not a big deal either way, imo.  I'd rather have a premade 64 bit
mingw setup that works as well as the the 32 bit one on nokia's ftp
server.

Cheers,
~ andy.f



On Sun, Mar 6, 2011 at 8:42 AM, Patrick Masotta <masottaus at yahoo.com> wrote:
>
>> -0800, Patrick Masotta wrote:
>> > I've been thinking a bit more about the
>> project-session issue and I'd
>> > like to share this with you.
>> >
>> > How about having a project file and a sesion file with
>> the same
>> > project name on the project directory. When I load the
>> project if the
>> > sesion file exists it's automatically loaded if it
>> doesn't it's
>> > created and saved when I save the project. When I
>> share my project I
>> > share myProjectXXX.creator but I do not need to share
>> > myProjectXXX.session
>>
>> That's more or less how sessions work, except that they are
>> stored
>> in your personal settings, not in the project sources.
>
> think about objets please... the session info "belongs" to the project not to the user..., the same user working on several projects load a familiar environment when he/she loads the project...
>
>> That also
>> prevents "accidents" like adding the session to the source
>> repo.
>>
>
> I'm not seeing that as a terrible risk...
>
>
>> There is _also_ a *.pro.user file, that currently contains
>> unfortunately
>> both shared and non-shared data. Refactoring is on the way,
>> but in the
>> end there still will be the concepts of sharable and
>> non-sharable data.
>>
>
> that would be a good place for project-session info
>
>
>> > This way:
>>
>> > 1) We as users do not have to care about sessions
>> "maintenance"
>> > (creation, saving, loading...)
>>
>> Session loading is "as expensive" as project loading.
>
> your approach splits the concept.... project loaded and that's it; no more looking arround for loading things to work with my project as I did yesterday before I closed it....
>
>> Saving is
>> automatic. There is not much complication except the
>> initial
>> "Now, I might want to keep the current setup, so I go to
>> File->
>> SessionManager->Manage->Clone Session".
>
> why you like all of this?? can't you see VS approach on this topic is cleaner, simpler, easier to learn?
>
>> Discoverability might be
>> an issue, but the total effort seems to be neglegible.
>>
>> > 2) Sessions are bounded to projects; loading a project
>> loads the
>> > corresponding last session info.
>>
>> That would be wrong, as a session can cover more then a
>> single projects,
>> and any given project can be part of several sessions.
>>
>
> That is not "wrong"; if a session cover more than one project each individual project brings its own session info, if we always work with several projects we can easily implement the concept of "Solution", a file that only contains the path of the project file that conform the "Solution", and you never have to administer sessions as an independant entity...
> With your aproach if I have a session containing info on several projects and I move one project or delete it what happens with the whole session???...
>
>> > 3) Project session info is esily discarded if needed
>> erasing the
>> > corresponding project's session file.
>>
>> Already there.
>>
>
> no its not there, if I want to get rid of the session info related to project A but no the one related to project B with your approach is all mixed up.
>
>> > Visual Studio & Eclipse AFAIK do not handle
>> sessions independently
>> > from projects.
>>
>> I don't know either.
>>
>> A quick check with google leads to
>>
>>   http://www.wintellect.com/CS/blogs/jrobbins/archive/2008/07/21/debugger-settings-visual-studio-add-in-easily-copy-breakpoints-between-machines.aspx
>>
>> which contains
>>
>>  "[...] breakpoints, along with Watch window variables,
>> window layout, and
>>   other session state items are stored in a hidden
>> file, <Solution
>>   Name>.SUO"
>>
>> That seems to contradict your assumption that VS stores
>> that data in the
>> .vcprof files, and actually looks pretty much exactly like
>> what Creator does.
>>
>
>
> 1) I never said "where" (and I do not care) VS stores the session info, I said VS bounds that info to the Project (or Solution). every project has different session info automatically loaded when we load the project.
>
> 2) conceptually qt-creator creates a new entity, the "session"  VS uses the session concept transparently; the user does not have to care about it. I think VS approach on this should be incorporated on qt-creator.
>
> just my 2-cents contribution to an amazing piece of code wrapped on a lovely 50 Meg install file...
>
> Pat
>
>
>
>
>
>
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at qt.nokia.com
> http://lists.qt.nokia.com/mailman/listinfo/qt-creator
>