You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(32) |
Aug
(24) |
Sep
(50) |
Oct
(35) |
Nov
(69) |
Dec
(74) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(54) |
Feb
(61) |
Mar
(27) |
Apr
(28) |
May
(57) |
Jun
(44) |
Jul
(35) |
Aug
(13) |
Sep
(30) |
Oct
(67) |
Nov
(11) |
Dec
(10) |
2005 |
Jan
(22) |
Feb
(17) |
Mar
(36) |
Apr
(32) |
May
(47) |
Jun
(24) |
Jul
(17) |
Aug
(29) |
Sep
(17) |
Oct
(20) |
Nov
(40) |
Dec
(48) |
2006 |
Jan
(54) |
Feb
(29) |
Mar
(80) |
Apr
(28) |
May
(49) |
Jun
(30) |
Jul
(61) |
Aug
(50) |
Sep
(54) |
Oct
(67) |
Nov
(65) |
Dec
(18) |
2007 |
Jan
(61) |
Feb
(84) |
Mar
(41) |
Apr
(61) |
May
(21) |
Jun
(10) |
Jul
(35) |
Aug
(38) |
Sep
(18) |
Oct
(26) |
Nov
(30) |
Dec
(18) |
2008 |
Jan
(38) |
Feb
(37) |
Mar
(22) |
Apr
(22) |
May
(44) |
Jun
(59) |
Jul
(45) |
Aug
(23) |
Sep
(18) |
Oct
(16) |
Nov
(34) |
Dec
(38) |
2009 |
Jan
(56) |
Feb
(53) |
Mar
(61) |
Apr
(33) |
May
(15) |
Jun
(22) |
Jul
(23) |
Aug
(12) |
Sep
(12) |
Oct
(4) |
Nov
(16) |
Dec
(33) |
2010 |
Jan
(19) |
Feb
(25) |
Mar
(19) |
Apr
(20) |
May
(11) |
Jun
(10) |
Jul
(6) |
Aug
(19) |
Sep
(5) |
Oct
(7) |
Nov
(12) |
Dec
(7) |
2011 |
Jan
(6) |
Feb
(16) |
Mar
(6) |
Apr
(10) |
May
(9) |
Jun
(10) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(5) |
Nov
(10) |
Dec
(8) |
2012 |
Jan
(13) |
Feb
(14) |
Mar
(2) |
Apr
(10) |
May
(6) |
Jun
(11) |
Jul
(3) |
Aug
(8) |
Sep
(57) |
Oct
(39) |
Nov
(2) |
Dec
(14) |
2013 |
Jan
(11) |
Feb
(3) |
Mar
(44) |
Apr
(2) |
May
(1) |
Jun
(7) |
Jul
(4) |
Aug
(1) |
Sep
(3) |
Oct
(3) |
Nov
(17) |
Dec
(7) |
2014 |
Jan
(7) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
(11) |
Dec
(2) |
2015 |
Jan
(2) |
Feb
(11) |
Mar
(5) |
Apr
(6) |
May
(1) |
Jun
|
Jul
(24) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
(5) |
Apr
(13) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2017 |
Jan
(6) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(3) |
Nov
|
Dec
|
2018 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(10) |
Oct
|
Nov
|
Dec
(1) |
2019 |
Jan
(1) |
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Eugene S. <eug...@gm...> - 2016-04-28 18:23:32
|
> On Квітень 4, 2016, 9:13 після полудня, Michel Ludwig wrote: > > src/kileproject.cpp, line 904 > > <https://git.reviewboard.kde.org/r/127551/diff/2/?file=455096#file455096line904> > > > > This method looks a little complicated. > > > > Wouldn't it be possible to have a "loadVersion2" > > and a "loadVersion3" method for reading project files? > > Eugene Shalygin wrote: > Don't understand you, I'm afraid. This method moves settings to the user file, but not loads them. Do you suggest instead to have two loading methonds and `saveVersion3()`? > > Eugene Shalygin wrote: > Ping? > > Michel Ludwig wrote: > Yes, that's correct (and sorry for the late reply). After some thinking and trying I give up: unable to write a good code for these two functions (loadVersion2()/loadVersion3()). Instead tried to make the migration code cleaner. Please take a look. - Eugene ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/#review94254 ----------------------------------------------------------- On Квітень 28, 2016, 8:20 після полудня, Eugene Shalygin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/127551/ > ----------------------------------------------------------- > > (Updated Квітень 28, 2016, 8:20 після полудня) > > > Review request for Kile and Michel Ludwig. > > > Repository: kile > > > Description > ------- > > If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. > > The following keys get moved into the user file: > "General" group: > kile_livePreviewEnabled > kile_livePreviewStatusUserSpecified > kile_livePreviewTool > lastDocument > > "item:" groups: > column > encoding > line > open > order > > Whole document-settings and view-settings groups. > > Additionally, config version is raised and the version (if < 3) is used to trigger migration. > > > Diffs > ----- > > src/dialogs/projectdialogs.h 0bac169 > src/dialogs/projectdialogs.cpp dec503b > src/kileproject.h 369c124 > src/kileproject.cpp 9d0d9c5 > src/kileversion.h 9ec780d > > Diff: https://git.reviewboard.kde.org/r/127551/diff/ > > > Testing > ------- > > Manual > > > Thanks, > > Eugene Shalygin > > |
From: Eugene S. <eug...@gm...> - 2016-04-28 18:20:55
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/ ----------------------------------------------------------- (Updated Квітень 28, 2016, 8:20 після полудня) Review request for Kile and Michel Ludwig. Changes ------- Refactor migartion code Repository: kile Description ------- If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. The following keys get moved into the user file: "General" group: kile_livePreviewEnabled kile_livePreviewStatusUserSpecified kile_livePreviewTool lastDocument "item:" groups: column encoding line open order Whole document-settings and view-settings groups. Additionally, config version is raised and the version (if < 3) is used to trigger migration. Diffs (updated) ----- src/dialogs/projectdialogs.h 0bac169 src/dialogs/projectdialogs.cpp dec503b src/kileproject.h 369c124 src/kileproject.cpp 9d0d9c5 src/kileversion.h 9ec780d Diff: https://git.reviewboard.kde.org/r/127551/diff/ Testing ------- Manual Thanks, Eugene Shalygin |
From: Michel L. <mic...@gm...> - 2016-04-20 06:13:40
|
> On April 4, 2016, 7:13 p.m., Michel Ludwig wrote: > > src/kileproject.cpp, line 904 > > <https://git.reviewboard.kde.org/r/127551/diff/2/?file=455096#file455096line904> > > > > This method looks a little complicated. > > > > Wouldn't it be possible to have a "loadVersion2" > > and a "loadVersion3" method for reading project files? > > Eugene Shalygin wrote: > Don't understand you, I'm afraid. This method moves settings to the user file, but not loads them. Do you suggest instead to have two loading methonds and `saveVersion3()`? > > Eugene Shalygin wrote: > Ping? Yes, that's correct (and sorry for the late reply). - Michel ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/#review94254 ----------------------------------------------------------- On April 10, 2016, 11:12 a.m., Eugene Shalygin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/127551/ > ----------------------------------------------------------- > > (Updated April 10, 2016, 11:12 a.m.) > > > Review request for Kile and Michel Ludwig. > > > Repository: kile > > > Description > ------- > > If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. > > The following keys get moved into the user file: > "General" group: > kile_livePreviewEnabled > kile_livePreviewStatusUserSpecified > kile_livePreviewTool > lastDocument > > "item:" groups: > column > encoding > line > open > order > > Whole document-settings and view-settings groups. > > Additionally, config version is raised and the version (if < 3) is used to trigger migration. > > > Diffs > ----- > > src/dialogs/projectdialogs.h 0bac169 > src/dialogs/projectdialogs.cpp dec503b > src/kileproject.h 369c124 > src/kileproject.cpp 9d0d9c5 > src/kileversion.h 9ec780d > > Diff: https://git.reviewboard.kde.org/r/127551/diff/ > > > Testing > ------- > > Manual > > > Thanks, > > Eugene Shalygin > > |
From: Eugene S. <eug...@gm...> - 2016-04-17 14:02:34
|
> On Квітень 4, 2016, 9:13 після полудня, Michel Ludwig wrote: > > src/kileproject.cpp, line 904 > > <https://git.reviewboard.kde.org/r/127551/diff/2/?file=455096#file455096line904> > > > > This method looks a little complicated. > > > > Wouldn't it be possible to have a "loadVersion2" > > and a "loadVersion3" method for reading project files? > > Eugene Shalygin wrote: > Don't understand you, I'm afraid. This method moves settings to the user file, but not loads them. Do you suggest instead to have two loading methonds and `saveVersion3()`? Ping? - Eugene ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/#review94254 ----------------------------------------------------------- On Квітень 10, 2016, 1:12 після полудня, Eugene Shalygin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/127551/ > ----------------------------------------------------------- > > (Updated Квітень 10, 2016, 1:12 після полудня) > > > Review request for Kile and Michel Ludwig. > > > Repository: kile > > > Description > ------- > > If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. > > The following keys get moved into the user file: > "General" group: > kile_livePreviewEnabled > kile_livePreviewStatusUserSpecified > kile_livePreviewTool > lastDocument > > "item:" groups: > column > encoding > line > open > order > > Whole document-settings and view-settings groups. > > Additionally, config version is raised and the version (if < 3) is used to trigger migration. > > > Diffs > ----- > > src/dialogs/projectdialogs.h 0bac169 > src/dialogs/projectdialogs.cpp dec503b > src/kileproject.h 369c124 > src/kileproject.cpp 9d0d9c5 > src/kileversion.h 9ec780d > > Diff: https://git.reviewboard.kde.org/r/127551/diff/ > > > Testing > ------- > > Manual > > > Thanks, > > Eugene Shalygin > > |
From: Eugene S. <eug...@gm...> - 2016-04-10 11:18:08
|
> On Квітень 4, 2016, 9:13 після полудня, Michel Ludwig wrote: > > Thanks a lot for the patch! This was an often requested feature. > > > > However, could you leave the "kile_livePreviewTool" and the "encoding" settings in the normal project file? These settings are really tied to the file. > > > > Also, I think we need more checks now when a new project is created (for instance, it has to be checked whether the user config file can be created). > > Eugene Shalygin wrote: > Thank you for the warm welcoming! > > I want to move the "kile_livePreviewEnabled" and "kile_livePreviewTool" settings into the user file because I often find myself in situation when I disable LivePreview for a particular editing phase while my co-author wants it to be enabled or vise-versa. The tool name can be moved to the user file because, for instance, LaTeX distributions can differ, and some of us can use luatex, some prefer xetex. Actually, the "kile_livePreviewStatusUserSpecified" was moved blindly. > > Agree with the rest. Copied checks for project directory and file and applied them to the user settings file and its directory. - Eugene ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/#review94254 ----------------------------------------------------------- On Квітень 10, 2016, 1:12 після полудня, Eugene Shalygin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/127551/ > ----------------------------------------------------------- > > (Updated Квітень 10, 2016, 1:12 після полудня) > > > Review request for Kile and Michel Ludwig. > > > Repository: kile > > > Description > ------- > > If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. > > The following keys get moved into the user file: > "General" group: > kile_livePreviewEnabled > kile_livePreviewStatusUserSpecified > kile_livePreviewTool > lastDocument > > "item:" groups: > column > encoding > line > open > order > > Whole document-settings and view-settings groups. > > Additionally, config version is raised and the version (if < 3) is used to trigger migration. > > > Diffs > ----- > > src/dialogs/projectdialogs.h 0bac169 > src/dialogs/projectdialogs.cpp dec503b > src/kileproject.h 369c124 > src/kileproject.cpp 9d0d9c5 > src/kileversion.h 9ec780d > > Diff: https://git.reviewboard.kde.org/r/127551/diff/ > > > Testing > ------- > > Manual > > > Thanks, > > Eugene Shalygin > > |
From: Eugene S. <eug...@gm...> - 2016-04-10 11:15:59
|
> On Квітень 4, 2016, 9:13 після полудня, Michel Ludwig wrote: > > src/kileproject.h, line 240 > > <https://git.reviewboard.kde.org/r/127551/diff/2/?file=455095#file455095line240> > > > > Can we have two methods here > > > > - projectConfigGroupForItem(KileProjectItem*) > > - userConfigGroupForItem(KileProjectItem*) > > > > (or similar) > > > > I think it will make the code easier to read in the long term. > > Eugene Shalygin wrote: > Maybe we can add an `enum class` and then the call can look like: > > ```C++ > configGroupForItem(item, SettingScope::User) > configGroupForItem(item, SettingScope::Project) > ``` > ? I've replaced the boolean parameter with enum. The calls looks as follows: ```C+ KConfigGroup projectConfigGroup = m_project->configGroupForItem(this, KileProject::ProjectFile); KConfigGroup userConfigGroup = m_project->configGroupForItem(this, KileProject::UserFile); ``` - Eugene ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/#review94254 ----------------------------------------------------------- On Квітень 10, 2016, 1:12 після полудня, Eugene Shalygin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/127551/ > ----------------------------------------------------------- > > (Updated Квітень 10, 2016, 1:12 після полудня) > > > Review request for Kile and Michel Ludwig. > > > Repository: kile > > > Description > ------- > > If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. > > The following keys get moved into the user file: > "General" group: > kile_livePreviewEnabled > kile_livePreviewStatusUserSpecified > kile_livePreviewTool > lastDocument > > "item:" groups: > column > encoding > line > open > order > > Whole document-settings and view-settings groups. > > Additionally, config version is raised and the version (if < 3) is used to trigger migration. > > > Diffs > ----- > > src/dialogs/projectdialogs.h 0bac169 > src/dialogs/projectdialogs.cpp dec503b > src/kileproject.h 369c124 > src/kileproject.cpp 9d0d9c5 > src/kileversion.h 9ec780d > > Diff: https://git.reviewboard.kde.org/r/127551/diff/ > > > Testing > ------- > > Manual > > > Thanks, > > Eugene Shalygin > > |
From: Eugene S. <eug...@gm...> - 2016-04-10 11:12:49
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/ ----------------------------------------------------------- (Updated Квітень 10, 2016, 1:12 після полудня) Review request for Kile and Michel Ludwig. Changes ------- replace boolean parameter with an enum Repository: kile Description ------- If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. The following keys get moved into the user file: "General" group: kile_livePreviewEnabled kile_livePreviewStatusUserSpecified kile_livePreviewTool lastDocument "item:" groups: column encoding line open order Whole document-settings and view-settings groups. Additionally, config version is raised and the version (if < 3) is used to trigger migration. Diffs (updated) ----- src/dialogs/projectdialogs.h 0bac169 src/dialogs/projectdialogs.cpp dec503b src/kileproject.h 369c124 src/kileproject.cpp 9d0d9c5 src/kileversion.h 9ec780d Diff: https://git.reviewboard.kde.org/r/127551/diff/ Testing ------- Manual Thanks, Eugene Shalygin |
From: Eugene S. <eug...@gm...> - 2016-04-09 02:13:48
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127614/ ----------------------------------------------------------- Review request for Kile and Michel Ludwig. Repository: kile Description ------- Fix the typo in the `Manager::getCwlBaseDirs()` which leads to `globalDir == localDir` always, due to comparison `(*it) != localDir` being always true because one of the dirs contain trailing slash while the other one does not. Diffs ----- src/codecompletion.cpp a16fdbb Diff: https://git.reviewboard.kde.org/r/127614/diff/ Testing ------- Completions files are shown in the configuration dialog. Thanks, Eugene Shalygin |
From: Eugene S. <eug...@gm...> - 2016-04-08 16:48:35
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/ ----------------------------------------------------------- (Updated Квітень 8, 2016, 6:48 після полудня) Review request for Kile and Michel Ludwig. Changes ------- Leave "enabled" property in the project file, add checks for ".kile" subdir and .user file when creating a project Repository: kile Description ------- If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. The following keys get moved into the user file: "General" group: kile_livePreviewEnabled kile_livePreviewStatusUserSpecified kile_livePreviewTool lastDocument "item:" groups: column encoding line open order Whole document-settings and view-settings groups. Additionally, config version is raised and the version (if < 3) is used to trigger migration. Diffs (updated) ----- src/dialogs/projectdialogs.h 0bac169 src/dialogs/projectdialogs.cpp dec503b src/kileproject.h 369c124 src/kileproject.cpp 9d0d9c5 src/kileversion.h 9ec780d Diff: https://git.reviewboard.kde.org/r/127551/diff/ Testing ------- Manual Thanks, Eugene Shalygin |
From: Eugene S. <eug...@gm...> - 2016-04-04 20:15:15
|
> On Квітень 4, 2016, 9:13 після полудня, Michel Ludwig wrote: > > Thanks a lot for the patch! This was an often requested feature. > > > > However, could you leave the "kile_livePreviewTool" and the "encoding" settings in the normal project file? These settings are really tied to the file. > > > > Also, I think we need more checks now when a new project is created (for instance, it has to be checked whether the user config file can be created). Thank you for the warm welcoming! I want to move the "kile_livePreviewEnabled" and "kile_livePreviewTool" settings into the user file because I often find myself in situation when I disable LivePreview for a particular editing phase while my co-author wants it to be enabled or vise-versa. The tool name can be moved to the user file because, for instance, LaTeX distributions can differ, and some of us can use luatex, some prefer xetex. Actually, the "kile_livePreviewStatusUserSpecified" was moved blindly. Agree with the rest. > On Квітень 4, 2016, 9:13 після полудня, Michel Ludwig wrote: > > src/kileproject.h, line 240 > > <https://git.reviewboard.kde.org/r/127551/diff/2/?file=455095#file455095line240> > > > > Can we have two methods here > > > > - projectConfigGroupForItem(KileProjectItem*) > > - userConfigGroupForItem(KileProjectItem*) > > > > (or similar) > > > > I think it will make the code easier to read in the long term. Maybe we can add an `enum class` and then the call can look like: ```C++ configGroupForItem(item, SettingScope::User) configGroupForItem(item, SettingScope::Project) ``` ? > On Квітень 4, 2016, 9:13 після полудня, Michel Ludwig wrote: > > src/kileproject.cpp, line 904 > > <https://git.reviewboard.kde.org/r/127551/diff/2/?file=455096#file455096line904> > > > > This method looks a little complicated. > > > > Wouldn't it be possible to have a "loadVersion2" > > and a "loadVersion3" method for reading project files? Don't understand you, I'm afraid. This method moves settings to the user file, but not loads them. Do you suggest instead to have two loading methonds and `saveVersion3()`? - Eugene ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/#review94254 ----------------------------------------------------------- On Квітень 3, 2016, 3:13 після полудня, Eugene Shalygin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/127551/ > ----------------------------------------------------------- > > (Updated Квітень 3, 2016, 3:13 після полудня) > > > Review request for Kile and Michel Ludwig. > > > Repository: kile > > > Description > ------- > > If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. > > The following keys get moved into the user file: > "General" group: > kile_livePreviewEnabled > kile_livePreviewStatusUserSpecified > kile_livePreviewTool > lastDocument > > "item:" groups: > column > encoding > line > open > order > > Whole document-settings and view-settings groups. > > Additionally, config version is raised and the version (if < 3) is used to trigger migration. > > > Diffs > ----- > > src/kileproject.h 369c124 > src/kileproject.cpp 9d0d9c5 > src/kileversion.h 9ec780d > > Diff: https://git.reviewboard.kde.org/r/127551/diff/ > > > Testing > ------- > > Manual > > > Thanks, > > Eugene Shalygin > > |
From: Michel L. <mic...@gm...> - 2016-04-04 19:14:06
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/#review94254 ----------------------------------------------------------- Thanks a lot for the patch! This was an often requested feature. However, could you leave the "kile_livePreviewTool" and the "encoding" settings in the normal project file? These settings are really tied to the file. Also, I think we need more checks now when a new project is created (for instance, it has to be checked whether the user config file can be created). src/kileproject.h (line 240) <https://git.reviewboard.kde.org/r/127551/#comment64112> Can we have two methods here - projectConfigGroupForItem(KileProjectItem*) - userConfigGroupForItem(KileProjectItem*) (or similar) I think it will make the code easier to read in the long term. src/kileproject.cpp (line 903) <https://git.reviewboard.kde.org/r/127551/#comment64113> This method looks a little complicated. Wouldn't it be possible to have a "loadVersion2" and a "loadVersion3" method for reading project files? - Michel Ludwig On April 3, 2016, 1:13 p.m., Eugene Shalygin wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/127551/ > ----------------------------------------------------------- > > (Updated April 3, 2016, 1:13 p.m.) > > > Review request for Kile and Michel Ludwig. > > > Repository: kile > > > Description > ------- > > If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. > > The following keys get moved into the user file: > "General" group: > kile_livePreviewEnabled > kile_livePreviewStatusUserSpecified > kile_livePreviewTool > lastDocument > > "item:" groups: > column > encoding > line > open > order > > Whole document-settings and view-settings groups. > > Additionally, config version is raised and the version (if < 3) is used to trigger migration. > > > Diffs > ----- > > src/kileproject.h 369c124 > src/kileproject.cpp 9d0d9c5 > src/kileversion.h 9ec780d > > Diff: https://git.reviewboard.kde.org/r/127551/diff/ > > > Testing > ------- > > Manual > > > Thanks, > > Eugene Shalygin > > |
From: Eugene S. <eug...@gm...> - 2016-04-02 10:07:58
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/ ----------------------------------------------------------- (Updated Квітень 2, 2016, 12:07 після полудня) Review request for Kile. Changes ------- Silly me made a last minute optimisation which of course broke the code. Here is the fixed one. Repository: kile Description ------- If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. The following keys get moved into the user file: "General" group: kile_livePreviewEnabled kile_livePreviewStatusUserSpecified kile_livePreviewTool lastDocument "item:" groups: column encoding line open order Whole document-settings and view-settings groups. Additionally, config version is raised and the version (if < 3) is used to trigger migration. Diffs (updated) ----- src/kileproject.h 369c124 src/kileproject.cpp 9d0d9c5 src/kileversion.h 9ec780d Diff: https://git.reviewboard.kde.org/r/127551/diff/ Testing ------- Manual Thanks, Eugene Shalygin |
From: Eugene S. <eug...@gm...> - 2016-04-02 02:14:46
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/127551/ ----------------------------------------------------------- Review request for Kile. Repository: kile Description ------- If Kile projects are stored in VCS or several people work on the same project and synchronize their changes, items view settings flood VSC history or interfere with another user settings. To make life of such users simpler, I propose to split the project file onto two parts, as most of the IDEs do. The project file part contains only the static project structure, while user file (stored in $PROJECT_DIR/.kile/$PROJECT_FILENAME.user) contains all the mutable settings. The following keys get moved into the user file: "General" group: kile_livePreviewEnabled kile_livePreviewStatusUserSpecified kile_livePreviewTool lastDocument "item:" groups: column encoding line open order Whole document-settings and view-settings groups. Additionally, config version is raised and the version (if < 3) is used to trigger migration. Diffs ----- src/kileproject.h 369c124 src/kileproject.cpp 9d0d9c5 src/kileversion.h 9ec780d Diff: https://git.reviewboard.kde.org/r/127551/diff/ Testing ------- Manual Thanks, Eugene Shalygin |
From: Michel <mic...@gm...> - 2016-03-31 08:52:03
|
Dear Marciano, On 23.03.2016 20:48, Marciano Siniscalchi wrote: > Hi all, > > I am the co-developer of the LaTeXTools plugin for the Sublime Text and > Atom editors: > > https://github.com/msiniscalchi/atom-latextools > https://github.com/SublimeText/LaTeXTools > > Both plugins are MIT licensed. > > We would like to incorporate support for cwl-based completion. We > already have running code, but the LaTeXTools plugin itself does not > include the cwl files. On Sublime Text (the more mature platform), this > support depends upon an external package that only pulls in the cwl > files. This external package was created by another developer who used > to sell a *competing*, *closed-source* LaTeX plugin; in that case, the > cwl files clearly had to be provided separately. On Atom, we are still > considering what to do. > > Ideally, we would like to include the cwl files with the plugin. > However, we are currently MIT-licensed whereas Kile is GPLv2-licensed. I > am not sure it would be OK for us to just pull in the files, so I wanted > to check with you. I also noticed that the Sourceforge page for Kile > lists it as dual-licensed, GPLv2 and BSD, and I understand from the Atom > devs that that would be compatible with MIT. > > Any thoughts? The bottom line is that, *if* kile (or at least the cwl > files) are BSD-licensed, we should be OK just adding the files (with > attribution, obviously, whether or not that's required). But if not, we > may have to go the separate-package route on Atom as well. By default, Kile is GPLv2+-licensed *only*, which includes the cwl files. However, you may of course ask the authors of the various files whether they would allow you to use them in your project. I'm also not sure whether it's enough to download the cwl files to work around the GPL restrictions as these cwl files would still form an essential part of the resulting program. Best regards, Michel |
From: Marciano S. <mar...@no...> - 2016-03-23 19:48:38
|
Hi all, I am the co-developer of the LaTeXTools plugin for the Sublime Text and Atom editors: https://github.com/msiniscalchi/atom-latextools https://github.com/SublimeText/LaTeXTools Both plugins are MIT licensed. We would like to incorporate support for cwl-based completion. We already have running code, but the LaTeXTools plugin itself does not include the cwl files. On Sublime Text (the more mature platform), this support depends upon an external package that only pulls in the cwl files. This external package was created by another developer who used to sell a *competing*, *closed-source* LaTeX plugin; in that case, the cwl files clearly had to be provided separately. On Atom, we are still considering what to do. Ideally, we would like to include the cwl files with the plugin. However, we are currently MIT-licensed whereas Kile is GPLv2-licensed. I am not sure it would be OK for us to just pull in the files, so I wanted to check with you. I also noticed that the Sourceforge page for Kile lists it as dual-licensed, GPLv2 and BSD, and I understand from the Atom devs that that would be compatible with MIT. Any thoughts? The bottom line is that, *if* kile (or at least the cwl files) are BSD-licensed, we should be OK just adding the files (with attribution, obviously, whether or not that's required). But if not, we may have to go the separate-package route on Atom as well. Thanks! -- Marciano Siniscalchi Economics Department, Northwestern University http://faculty.wcas.northwestern.edu/~msi661 |
From: David H. <dav...@un...> - 2016-03-03 15:18:26
|
Dear Martin, Thank you for your suggestions, unfortunately, the problem stays even after I deleted (renamed) kilerc, or started with a completely fresh user account. Konsole is installed, since I use it almost constantly for my work. There is probably some miscommunication between kile and konsole, but I have no idea where to start looking for the problem. Cheers, David -- Dr. David Holec Dept. of Physical Metallurgy and Materials Testing Montanuniversität Leoben Franz-Josef-Strasse 18 A-8700 Leoben Austria tel. +43-(0)3842-4024211 fax. +43-(0)3842-4024202 On 3 March 2016 at 15:52, Martin Weis <mar...@gm...> wrote: > Hello David! > > On 03.03.2016 13:37, David Holec wrote: >> I am using Kile 2.1.3 in the latest openSuSE Leap 42.1. I made a fresh >> install but imported my old home to get the advantage of using all my >> old settings. >> >> When I open Kile now, the tab with Konsole is shown, but no >> possibility to enter terminal exists any more (it is just a black > > Did you move your old configuration away? ~/.kde* for KDE, I guess, for > kile especially kilerc is relevant. > Or/also try with a fresh user profile, if problem exists there. > > Then you can compare the fresh kilerc to yours. Might also be konsole > related, is it properly installed/configured? > > HTH, > Martin > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Kile-devel mailing list > Kil...@li... > https://lists.sourceforge.net/lists/listinfo/kile-devel > |
From: Martin W. <mar...@gm...> - 2016-03-03 14:52:45
|
Hello David! On 03.03.2016 13:37, David Holec wrote: > I am using Kile 2.1.3 in the latest openSuSE Leap 42.1. I made a fresh > install but imported my old home to get the advantage of using all my > old settings. > > When I open Kile now, the tab with Konsole is shown, but no > possibility to enter terminal exists any more (it is just a black Did you move your old configuration away? ~/.kde* for KDE, I guess, for kile especially kilerc is relevant. Or/also try with a fresh user profile, if problem exists there. Then you can compare the fresh kilerc to yours. Might also be konsole related, is it properly installed/configured? HTH, Martin |
From: David H. <dav...@un...> - 2016-03-03 12:37:41
|
Dear Kile users and developers, I am using Kile 2.1.3 in the latest openSuSE Leap 42.1. I made a fresh install but imported my old home to get the advantage of using all my old settings. When I open Kile now, the tab with Konsole is shown, but no possibility to enter terminal exists any more (it is just a black piece of window). I suspect that this is related to some misconfiguration of my desktop WS, since on my laptop running the same distro and the same updates all is fine. Does anyone have any idea where the problem might be? Thanks a lot in advance, David -- Dr. David Holec Dept. of Physical Metallurgy and Materials Testing Montanuniversität Leoben Franz-Josef-Strasse 18 A-8700 Leoben Austria tel. +43-(0)3842-4024211 fax. +43-(0)3842-4024202 |
From: <kil...@ny...> - 2015-12-07 22:49:37
|
How can I change this? |
From: Aleck M. <myu...@ya...> - 2015-11-04 12:40:53
|
Hi, A user made a project and when he opened it later on he had in The Files and Projects View abracadabra instead of project file names similar to that in lines 16 and 19 of the attached screen snapshot of ~/kde./share/config/kilerc and following clicking on that abracadabra showed empty contents in The Main View. Nevertheless the projects created in Kile earlier in other Linux OS function properly. How can I fix or workaround this problem? Currenty versions used: Kile version 2.1.3 OS: Linux Mint 17.2 Rafaela KDE Edition (Linux 3.16.0-38-generic) I prefer a direct reply. -- Aleck |
From: Jayesh B. <kd...@ja...> - 2015-09-18 20:45:08
|
Hi, The structure view does not show the view of the complete document. Instead, it just shows the view of the current tex file (relevant in multifile documents), which is somewhat limiting. Is this by design? Or is this a bug? If this is a design design, is there a way I can change it? If yes, where do I look? I am already reading structurewidget.h and structurewidget.cpp. -- Cheers Jayesh Badwaik |
From: Michel L. <mic...@gm...> - 2015-08-16 12:22:59
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124538/#review83878 ----------------------------------------------------------- Ship it! I guess we can remove it since no one is working on formulating any tips anyway. - Michel Ludwig On July 30, 2015, 8:36 p.m., Andreas Cord-Landwehr wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/124538/ > ----------------------------------------------------------- > > (Updated July 30, 2015, 8:36 p.m.) > > > Review request for Kile and Michel Ludwig. > > > Repository: kile > > > Description > ------- > > Support for this feature is already removed in most of all KDE applications. > Visual design people strongly decourage using it, mainly for the reason > that the interfaces must be self-explaining enough and let the user > explore for interesting features. More advanced features have to be > explained in the docbook. > > > Diffs > ----- > > src/CMakeLists.txt fc7f7a5e2bd51a86cca82439c19a6f595ea3cf32 > src/kile.h fe6f56a8544c99c86b8443604e97dea5c9d2ee9f > src/kile.cpp abe57fdf1386477ebdbed95ac19d1312a6cf0a44 > src/tips 45e62f4dcca0a2b02447cd27eb22260452428ebd > > Diff: https://git.reviewboard.kde.org/r/124538/diff/ > > > Testing > ------- > > > Thanks, > > Andreas Cord-Landwehr > > |
From: Martin S. <mar...@gm...> - 2015-08-09 20:09:38
|
Hi all, I have been using the live preview feature of Kile for more than 4 years to write mostly scientific papers and I'm very happy with it. To me, live preview seems pretty stable now. Since Kile is currently getting porting to KF5, I wonder if it makes sense to just publish a stable version for KDE4 now (and later, another one for KF5)? All major distributions are still shipping the three year old 2.1.3 version and the live preview feature would definitely deserve being rolled out to a wider audience. Actually, I think the livepreview-kde4 branch might even be more stable than the 2.1.3 release. I really appreciate your work on Kile and that you do not release unstable versions. However, I also love the live preview feature! That's why I have added an Ubuntu PPA years ago [1] to automatically build the live preview branch. This PPA is mostly used by myself and my colleagues, but also by many others [2]. Nevertheless, I'm sure a lot more can benefit from a real Kile live preview release. Thanks, Martin [1] https://launchpad.net/~kile/+archive/ubuntu/livepreview [2] ppastats shows more than 200 downloads of the latest version. |
From: Andreas Cord-L. <cor...@kd...> - 2015-07-30 20:36:46
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124538/ ----------------------------------------------------------- Review request for Kile and Michel Ludwig. Repository: kile Description ------- Support for this feature is already removed in most of all KDE applications. Visual design people strongly decourage using it, mainly for the reason that the interfaces must be self-explaining enough and let the user explore for interesting features. More advanced features have to be explained in the docbook. Diffs ----- src/CMakeLists.txt fc7f7a5e2bd51a86cca82439c19a6f595ea3cf32 src/kile.h fe6f56a8544c99c86b8443604e97dea5c9d2ee9f src/kile.cpp abe57fdf1386477ebdbed95ac19d1312a6cf0a44 src/tips 45e62f4dcca0a2b02447cd27eb22260452428ebd Diff: https://git.reviewboard.kde.org/r/124538/diff/ Testing ------- Thanks, Andreas Cord-Landwehr |
From: Andreas Cord-L. <cor...@kd...> - 2015-07-29 07:33:48
|
----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/124512/ ----------------------------------------------------------- (Updated July 29, 2015, 7:33 a.m.) Status ------ This change has been marked as submitted. Review request for Kile and Michel Ludwig. Changes ------- Submitted with commit a08fa810fab169af187b76d7392f766c297b1eb7 by Andreas Cord-Landwehr to branch master. Repository: kile Description ------- This complies with the design in Kate and KDevelop and follows the design rationale: The user does not have to move the mouse when opening and afterwards closing a sideview. Diffs ----- src/widgets/sidebar.cpp ef242bf5ae30efb209edf31e7dbf9033cdd8a577 Diff: https://git.reviewboard.kde.org/r/124512/diff/ Testing ------- manual testing Thanks, Andreas Cord-Landwehr |