Hi all,
I've been looking for a way to do this, and Darrell also mentioned that he was looking for a was to use the Multiple Document Interface with firefox.
I have written a patch that will enable you to only use a single kate window. It is controlled by a kate kconfig option and can be changed under kate's general settings tab.
Tim, Can we push this into the master? is this something we even want to have? I like it personally, I understand if other don't. Remember it is optional so it won't impact anything when disabled, and will be disabled by default.
What do you think? Darrell with this satisfy what you were looking for?
This is using the 3.5.13 resources, prior to the rename. Some things might need to change (kde to tde stuff).
Thanks, Calvin Morrison
I've been looking for a way to do this, and Darrell also mentioned that he was looking for a was to use the Multiple Document Interface with firefox.
I have written a patch that will enable you to only use a single kate window. It is controlled by a kate kconfig option and can be changed under kate's general settings tab.
Looks like the new option is placed in $TDEHOME/share/config/katerc [General] UseInstance=0/1?
I see the check box in your patch, but I haven't yet tried to build.
Tim, Can we push this into the master? is this something we even want to have? I like it personally, I understand if other don't. Remember it is optional so it won't impact anything when disabled, and will be disabled by default.
With the check box I don't see a conflict. The default should be OFF because SDI is the current behavior. Only those who want an MDI would enable the check box.
Bug report 692 addresses this issue. Tim bumped the priority to Blocker, so I am guessing he will be interested in testing the patch. :)
What do you think? Darrell with this satisfy what you were looking for?
We'll have to do some testing. Do you have any kind of test plan? For example, does the new option conflict with the --use parameter? Do users need to disable the --use parameter in all of their *.desktop parameters? I believe the default in all kate related *.desktop files do not have the --use parameter enabled, but I have that changed here because I want an MDI.
We should find people who prefer the SDI to test the patch. When they test with the check box enabled, they will have a different perspective than us MDI users.
I also need to test the patch with Firefox, as I mentioned in previous posts.
This is using the 3.5.13 resources, prior to the rename. Some things might need to change (kde to tde stuff).
I can fix those. :)
Darrell
I've been looking for a way to do this, and Darrell also mentioned that he was looking for a was to use the Multiple Document Interface with firefox.
I have written a patch that will enable you to only use a single kate window. It is controlled by a kate kconfig option and can be changed under kate's general settings tab.
Looks like the new option is placed in $TDEHOME/share/config/katerc [General] UseInstance=0/1?
I see the check box in your patch, but I haven't yet tried to build.
Something else that might be interesting to add is an override flag that, if passed to Kate, launches in the desired instance mode. For example --sdi or --mdi.
Tim
On 26 January 2012 14:31, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
I've been looking for a way to do this, and Darrell also mentioned that he was looking for a was to use the Multiple Document Interface with firefox.
I have written a patch that will enable you to only use a single kate window. It is controlled by a kate kconfig option and can be changed under kate's general settings tab.
Looks like the new option is placed in $TDEHOME/share/config/katerc [General] UseInstance=0/1?
I see the check box in your patch, but I haven't yet tried to build.
Something else that might be interesting to add is an override flag that, if passed to Kate, launches in the desired instance mode. For example --sdi or --mdi.
Tim
That is a very good point. I will add a --sdi flag then.
what happens when a user does -u with this patch? nothing at all.
there is an if statement that states something like this: if MDI enabled or -U option then open in the current instance.
I would like someone to test it as well, but I will make modifications and add it to the bug tracker
On 26 January 2012 14:34, Calvin Morrison mutantturkey@gmail.com wrote:
On 26 January 2012 14:31, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
I've been looking for a way to do this, and Darrell also mentioned that he was looking for a was to use the Multiple Document Interface with firefox.
I have written a patch that will enable you to only use a single kate window. It is controlled by a kate kconfig option and can be changed under kate's general settings tab.
Looks like the new option is placed in $TDEHOME/share/config/katerc [General] UseInstance=0/1?
I see the check box in your patch, but I haven't yet tried to build.
Something else that might be interesting to add is an override flag that, if passed to Kate, launches in the desired instance mode. For example --sdi or --mdi.
Tim
That is a very good point. I will add a --sdi flag then.
what happens when a user does -u with this patch? nothing at all.
there is an if statement that states something like this: if MDI enabled or -U option then open in the current instance.
I would like someone to test it as well, but I will make modifications and add it to the bug tracker
Added a flag -f or --force-sdi which works. if -u or the MDI is enabled via kconfig, they will be overridden by this flag.
I will upload it to the tracker.
Hi all,
I've been looking for a way to do this, and Darrell also mentioned that he was looking for a was to use the Multiple Document Interface with firefox.
I have written a patch that will enable you to only use a single kate window. It is controlled by a kate kconfig option and can be changed under kate's general settings tab.
Tim, Can we push this into the master? is this something we even want to have? I like it personally, I understand if other don't. Remember it is optional so it won't impact anything when disabled, and will be disabled by default.
What do you think? Darrell with this satisfy what you were looking for?
This is using the 3.5.13 resources, prior to the rename. Some things might need to change (kde to tde stuff).
Thanks, Calvin Morrison
As long as the new functionality is user configurable (enabled/disabled), I will push it into GIT. Can you post it to the bug report though? As you mentioned I can't push it directly, so it needs to go in queue for conversion.
Thanks!
Tim
-
Calvin Morrison -
Darrell Anderson -
Timothy Pearson