omegat-issues

Feature Requests item #2726068, was opened at 2009-04-02 04:58
Message generated for change (Comment added) made by didierbr
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2726068&group_id=68187
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: OmegaT Application
>Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jean-Christophe Helary (brandelune)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Export last current project in omegat.prefs
Initial Comment:
It looks like the <current_folder> data indicates the folder where the project is located, but there is no indication whatsoever about what the current project name is in the whole file.
I am not sure what the current_folder data is for but as far as the user is concerned (possibility to parse the project name and open it automatically from a script) the <current_project> data is much more valuable.
----------------------------------------------------------------------
>Comment By: Didier Briel (didierbr)
Date: 2009-04-02 12:20
Message:
There's no "active" project, since there can be an unlimited number of
active projects.
What could be possible would be to export the "last current project",
i.e., the current project for the instance that writes omegat.prefs at a
given time.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 10:15
Message:
Ok, I tested a little bit and I see that the value is updated each time a
project is opened, hence, in the case of one instance of OmegaT the value
reflects the directory that includes the currently opened project.
Now, I'd like to know if it is possible (RFE) to have OmegaT declare to
omegat.pref which is the active project ? By active I mean the one that is
being manipulated. That way it is possible to parse omegat.pref for that
value and have scripts that open the project folder or target etc depending
on needs.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 09:50
Message:
<<If <current_folder> is the "last folder opened" then it should be
labeled
<last_folder>, not <current_folder>, or whatever refers to its
function.>>
Tag names (in omegat.prefs) are not there for users to play with them,
it's a persistence mechanism.
<current_folder> is appropriate enough.
<<As for the "current project" that does not exist, do you mean that
OmegaT
does not know which omegat.project is used at any moment in time ?>>
The n (e.g., 50) OmegaT instance*s* in memory at a given time perfectly
know where *they* are.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 09:21
Message:
If <current_folder> is the "last folder opened" then it should be labeled
<last_folder>, not <current_folder>, or whatever refers to its function.
As for the "current project" that does not exist, do you mean that OmegaT
does not know which omegat.project is used at any moment in time ?
I'm fine with renaming this RFE according to what you tell me about the
above 2 points.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 09:06
Message:
<current_folder> indicates the last folder used to open a project, so that
it is used next time a user uses Project/Open. "As far as the user is
concerned", it is extremely useful (otherwise, one would have to start from
an arbitrary location each time).
The concept of "current_project" doesn't exist in OmegaT so far, so there
would be no point in "exporting" it.
Didier
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2726068&group_id=68187

Feature Requests item #2726068, was opened at 2009-04-02 11:58
Message generated for change (Comment added) made by brandelune
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2726068&group_id=68187
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: OmegaT Application
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jean-Christophe Helary (brandelune)
Assigned to: Nobody/Anonymous (nobody)
Summary: Export last current project in omegat.prefs
Initial Comment:
It looks like the <current_folder> data indicates the folder where the project is located, but there is no indication whatsoever about what the current project name is in the whole file.
I am not sure what the current_folder data is for but as far as the user is concerned (possibility to parse the project name and open it automatically from a script) the <current_project> data is much more valuable.
----------------------------------------------------------------------
>Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 20:14
Message:
But when I write a segment, OmegaT knows which instance of itself is doing
it right ?
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 19:20
Message:
There's no "active" project, since there can be an unlimited number of
active projects.
What could be possible would be to export the "last current project",
i.e., the current project for the instance that writes omegat.prefs at a
given time.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 17:15
Message:
Ok, I tested a little bit and I see that the value is updated each time a
project is opened, hence, in the case of one instance of OmegaT the value
reflects the directory that includes the currently opened project.
Now, I'd like to know if it is possible (RFE) to have OmegaT declare to
omegat.pref which is the active project ? By active I mean the one that is
being manipulated. That way it is possible to parse omegat.pref for that
value and have scripts that open the project folder or target etc depending
on needs.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 16:50
Message:
<<If <current_folder> is the "last folder opened" then it should be
labeled
<last_folder>, not <current_folder>, or whatever refers to its
function.>>
Tag names (in omegat.prefs) are not there for users to play with them,
it's a persistence mechanism.
<current_folder> is appropriate enough.
<<As for the "current project" that does not exist, do you mean that
OmegaT
does not know which omegat.project is used at any moment in time ?>>
The n (e.g., 50) OmegaT instance*s* in memory at a given time perfectly
know where *they* are.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 16:21
Message:
If <current_folder> is the "last folder opened" then it should be labeled
<last_folder>, not <current_folder>, or whatever refers to its function.
As for the "current project" that does not exist, do you mean that OmegaT
does not know which omegat.project is used at any moment in time ?
I'm fine with renaming this RFE according to what you tell me about the
above 2 points.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 16:06
Message:
<current_folder> indicates the last folder used to open a project, so that
it is used next time a user uses Project/Open. "As far as the user is
concerned", it is extremely useful (otherwise, one would have to start from
an arbitrary location each time).
The concept of "current_project" doesn't exist in OmegaT so far, so there
would be no point in "exporting" it.
Didier
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2726068&group_id=68187

Feature Requests item #2726068, was opened at 2009-04-02 04:58
Message generated for change (Comment added) made by didierbr
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2726068&group_id=68187
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: OmegaT Application
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jean-Christophe Helary (brandelune)
Assigned to: Nobody/Anonymous (nobody)
Summary: Export last current project in omegat.prefs
Initial Comment:
It looks like the <current_folder> data indicates the folder where the project is located, but there is no indication whatsoever about what the current project name is in the whole file.
I am not sure what the current_folder data is for but as far as the user is concerned (possibility to parse the project name and open it automatically from a script) the <current_project> data is much more valuable.
----------------------------------------------------------------------
>Comment By: Didier Briel (didierbr)
Date: 2009-04-02 14:11
Message:
<<But when I write a segment, OmegaT knows which instance of itself is
doing
it right ?>>
The question doesn't really make sense. Each instance knows that it is
writing a segment, of course. The others have no idea what other instances
are doing. There's not a "big" OmegaT supervising all that. Each OmegaT
instance is totally independent, and has no knowledge of the others.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 13:14
Message:
But when I write a segment, OmegaT knows which instance of itself is doing
it right ?
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 12:20
Message:
There's no "active" project, since there can be an unlimited number of
active projects.
What could be possible would be to export the "last current project",
i.e., the current project for the instance that writes omegat.prefs at a
given time.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 10:15
Message:
Ok, I tested a little bit and I see that the value is updated each time a
project is opened, hence, in the case of one instance of OmegaT the value
reflects the directory that includes the currently opened project.
Now, I'd like to know if it is possible (RFE) to have OmegaT declare to
omegat.pref which is the active project ? By active I mean the one that is
being manipulated. That way it is possible to parse omegat.pref for that
value and have scripts that open the project folder or target etc depending
on needs.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 09:50
Message:
<<If <current_folder> is the "last folder opened" then it should be
labeled
<last_folder>, not <current_folder>, or whatever refers to its
function.>>
Tag names (in omegat.prefs) are not there for users to play with them,
it's a persistence mechanism.
<current_folder> is appropriate enough.
<<As for the "current project" that does not exist, do you mean that
OmegaT
does not know which omegat.project is used at any moment in time ?>>
The n (e.g., 50) OmegaT instance*s* in memory at a given time perfectly
know where *they* are.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 09:21
Message:
If <current_folder> is the "last folder opened" then it should be labeled
<last_folder>, not <current_folder>, or whatever refers to its function.
As for the "current project" that does not exist, do you mean that OmegaT
does not know which omegat.project is used at any moment in time ?
I'm fine with renaming this RFE according to what you tell me about the
above 2 points.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 09:06
Message:
<current_folder> indicates the last folder used to open a project, so that
it is used next time a user uses Project/Open. "As far as the user is
concerned", it is extremely useful (otherwise, one would have to start from
an arbitrary location each time).
The concept of "current_project" doesn't exist in OmegaT so far, so there
would be no point in "exporting" it.
Didier
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2726068&group_id=68187

Feature Requests item #2726068, was opened at 2009-04-02 11:58
Message generated for change (Settings changed) made by brandelune
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2726068&group_id=68187
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: OmegaT Application
>Group: future
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jean-Christophe Helary (brandelune)
Assigned to: Nobody/Anonymous (nobody)
Summary: Export last current project in omegat.prefs
Initial Comment:
It looks like the <current_folder> data indicates the folder where the project is located, but there is no indication whatsoever about what the current project name is in the whole file.
I am not sure what the current_folder data is for but as far as the user is concerned (possibility to parse the project name and open it automatically from a script) the <current_project> data is much more valuable.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 21:11
Message:
<<But when I write a segment, OmegaT knows which instance of itself is
doing
it right ?>>
The question doesn't really make sense. Each instance knows that it is
writing a segment, of course. The others have no idea what other instances
are doing. There's not a "big" OmegaT supervising all that. Each OmegaT
instance is totally independent, and has no knowledge of the others.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 20:14
Message:
But when I write a segment, OmegaT knows which instance of itself is doing
it right ?
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 19:20
Message:
There's no "active" project, since there can be an unlimited number of
active projects.
What could be possible would be to export the "last current project",
i.e., the current project for the instance that writes omegat.prefs at a
given time.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 17:15
Message:
Ok, I tested a little bit and I see that the value is updated each time a
project is opened, hence, in the case of one instance of OmegaT the value
reflects the directory that includes the currently opened project.
Now, I'd like to know if it is possible (RFE) to have OmegaT declare to
omegat.pref which is the active project ? By active I mean the one that is
being manipulated. That way it is possible to parse omegat.pref for that
value and have scripts that open the project folder or target etc depending
on needs.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 16:50
Message:
<<If <current_folder> is the "last folder opened" then it should be
labeled
<last_folder>, not <current_folder>, or whatever refers to its
function.>>
Tag names (in omegat.prefs) are not there for users to play with them,
it's a persistence mechanism.
<current_folder> is appropriate enough.
<<As for the "current project" that does not exist, do you mean that
OmegaT
does not know which omegat.project is used at any moment in time ?>>
The n (e.g., 50) OmegaT instance*s* in memory at a given time perfectly
know where *they* are.
Didier
----------------------------------------------------------------------
Comment By: Jean-Christophe Helary (brandelune)
Date: 2009-04-02 16:21
Message:
If <current_folder> is the "last folder opened" then it should be labeled
<last_folder>, not <current_folder>, or whatever refers to its function.
As for the "current project" that does not exist, do you mean that OmegaT
does not know which omegat.project is used at any moment in time ?
I'm fine with renaming this RFE according to what you tell me about the
above 2 points.
----------------------------------------------------------------------
Comment By: Didier Briel (didierbr)
Date: 2009-04-02 16:06
Message:
<current_folder> indicates the last folder used to open a project, so that
it is used next time a user uses Project/Open. "As far as the user is
concerned", it is extremely useful (otherwise, one would have to start from
an arbitrary location each time).
The concept of "current_project" doesn't exist in OmegaT so far, so there
would be no point in "exporting" it.
Didier
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=520350&aid=2726068&group_id=68187