Hey guys,
I was hacking on a KCM module and found that there was already a TODO list made up for kcontrol, maybe we can exctract some ideas for that
"this file contain a list of various major changes for KControl(reorganization, broad technical changes etc.) planned for KDE4."
the file is located in tdebase/kcontrol/TODO
Calvin
I was hacking on a KCM module and found that there was already a TODO list made up for kcontrol, maybe we can exctract some ideas for that
"this file contain a list of various major changes for KControl(reorganization, broad technical changes etc.) planned for KDE4."
the file is located in tdebase/kcontrol/TODO
Oh gosh. Some of those ideas are exactly like what I proposed. Scary....
Calvin, do know that recently I did a lot of branding issue work on KControl. I recommend you rebuild everything from the latest GIT before you hack further.
For example KDE Components -> TDE Components, KDE Performance -> TDE Performance, KDE Resources -> TDE Resources, KDE Wallet -> TDE Wallet. Just about any text string that appears in KControl, regardless of the original package source, has been updated from KDE -> TDE.
I have not performed any other renaming because of translation challenges nor did I move anything.
To all: after building from the latest GIT you notice other branding issues, please post a note to the list and I'll try to fix the problem ASAP.
Darrell
On 10 March 2012 13:55, Darrell Anderson humanreadable@yahoo.com wrote:
I was hacking on a KCM module and found that there was already a TODO list made up for kcontrol, maybe we can exctract some ideas for that
"this file contain a list of various major changes for KControl(reorganization, broad technical changes etc.) planned for KDE4."
the file is located in tdebase/kcontrol/TODO
Oh gosh. Some of those ideas are exactly like what I proposed. Scary....
Calvin, do know that recently I did a lot of branding issue work on KControl. I recommend you rebuild everything from the latest GIT before you hack further.
Yes! I am really excited and happy that you've been committing a lot of stuff lately. Not overly complicated stuff, but things like renaming, branding issues, and small fixes. This is awesome! It lets Tim stay focused on major issues, while solving the more minor (but still important) problems. For that I thank you!
Unfortunately, (Embarassingly?) I do not have a running GIT system. Now that David Rankin has finished successfully building arch and TDE I will spend some time getting a git system running on my computer. The problem is that I use TDE for my work - so I don't want to break it :p
Luckily this patch is just implementing a small configuration option related to bug 251. Should be easy enough to use my 3.5.13 sources and not break anything.
To all: after building from the latest GIT you notice other branding issues, please post a note to the list and I'll try to fix the problem ASAP.
have you tried to just grep for all strings related to KDE? I found a regular grep doesn't work well, but doing a pipe helps
grep "i18n" * -r | grep "KDE"
this will show all the KDE's in any string recursively.
Calvin
Unfortunately, (Embarassingly?) I do not have a running GIT system. Now that David Rankin has finished successfully building arch and TDE I will spend some time getting a git system running on my computer. The problem is that I use TDE for my work - so I don't want to break it :p
I understand. I'm fortunate to have a nice desktop machine. I set up virtual machines to test my GIT packaging. That way I don't mess my production desktop. I also have a separate partition on the hard drive that has TDE installed. I have to reboot, of course, but when I am satisfied with my VM testing I then reboot, reinstall the latest packages, and then test. For example, I can't test tuner card issues in my VM (Kaffeine). I have to have a real hardware desktop for that. But overall, the VMs save me gobs of time.
Luckily this patch is just implementing a small configuration option related to bug 251. Should be easy enough to use my 3.5.13 sources and not break anything.
If you resolve bug report 251 then I'll buy you a round of virtual beers. :) Let me know your progress --- I'll be the first in line to test!
To all: after building from the latest GIT you notice
other branding issues, please post a note to the list and I'll try to fix the problem ASAP.
have you tried to just grep for all strings related to KDE? I found a regular grep doesn't work well, but doing a pipe helps
grep "i18n" * -r | grep "KDE"
this will show all the KDE's in any string recursively.
More or less, yes. However, I am not a skilled C++ hacker. Someday, maybe, but not today. :) I also don't know the big picture of how all the various files interrelate. I can't blindly search and replace strings. I tried that a few times and humbled myself by how much things broke. :) Not all strings that SEEM to need replacing should be replaced. I have to be careful because although certain text strings get replaced, I can't replace strings that actually are part of the app name or code base. For example, I can replace user related text strings about "K Menu" -> to "TDE Menu" but kmenu itself remains named the same.
Thus a basic search still requires manually looking at code and context before replacing text.
Further complicating the topic is translations. With many *.desktop files I can replace singular characters like KDE -> TDE and presume I am not doing any serious damage. Yet I can't fix only the English text strings in [Comments] because I can't translate those changes in the other languages. I have to leave those text strings untouched regardless of how much I want to change them.
I have the same challenge with updating the help files. Except for minor entity fixes, I can't touch the tde-i18n versions. I don't know how we'll ever fix those files. At times I am inclined to delete them all. That would cause the system to use the default English versions, but that likely would upset TDE users who do not use English.
So in summary, these branding issues are not all proverbial walks on the beach. My basic approach now is to slow down and only fix what I actually see and not try to guess what could be fixed. :)
Darrell
On 10 March 2012 14:44, Darrell Anderson humanreadable@yahoo.com wrote:
Unfortunately, (Embarassingly?) I do not have a running GIT system. Now that David Rankin has finished successfully building arch and TDE I will spend some time getting a git system running on my computer. The problem is that I use TDE for my work - so I don't want to break it :p
I understand. I'm fortunate to have a nice desktop machine. I set up virtual machines to test my GIT packaging. That way I don't mess my production desktop. I also have a separate partition on the hard drive that has TDE installed. I have to reboot, of course, but when I am satisfied with my VM testing I then reboot, reinstall the latest packages, and then test. For example, I can't test tuner card issues in my VM (Kaffeine). I have to have a real hardware desktop for that. But overall, the VMs save me gobs of time.
Luckily this patch is just implementing a small configuration option related to bug 251. Should be easy enough to use my 3.5.13 sources and not break anything.
If you resolve bug report 251 then I'll buy you a round of virtual beers. :) Let me know your progress --- I'll be the first in line to test!
To all: after building from the latest GIT you notice
other branding issues, please post a note to the list and I'll try to fix the problem ASAP.
have you tried to just grep for all strings related to KDE? I found a regular grep doesn't work well, but doing a pipe helps
grep "i18n" * -r | grep "KDE"
this will show all the KDE's in any string recursively.
More or less, yes. However, I am not a skilled C++ hacker. Someday, maybe, but not today. :) I also don't know the big picture of how all the various files interrelate. I can't blindly search and replace strings. I tried that a few times and humbled myself by how much things broke. :) Not all strings that SEEM to need replacing should be replaced. I have to be careful because although certain text strings get replaced, I can't replace strings that actually are part of the app name or code base. For example, I can replace user related text strings about "K Menu" -> to "TDE Menu" but kmenu itself remains named the same.
Thus a basic search still requires manually looking at code and context before replacing text.
Further complicating the topic is translations. With many *.desktop files I can replace singular characters like KDE -> TDE and presume I am not doing any serious damage. Yet I can't fix only the English text strings in [Comments] because I can't translate those changes in the other languages. I have to leave those text strings untouched regardless of how much I want to change them.
I have the same challenge with updating the help files. Except for minor entity fixes, I can't touch the tde-i18n versions. I don't know how we'll ever fix those files. At times I am inclined to delete them all. That would cause the system to use the default English versions, but that likely would upset TDE users who do not use English.
So in summary, these branding issues are not all proverbial walks on the beach. My basic approach now is to slow down and only fix what I actually see and not try to guess what could be fixed. :)
Darrell
Uploading a patch that fixes the problem :)
Uploading a patch that fixes the problem :)
Ya think? ;) I've been known to make developers scream by the time I am done testing.... :)
Okeydokey. I think I resolved my tdepim bug report problem. I'll test your patch as soon as possible!
Darrell
On 10 March 2012 15:56, Darrell Anderson humanreadable@yahoo.com wrote:
Uploading a patch that fixes the problem :)
Ya think? ;) I've been known to make developers scream by the time I am done testing.... :)
Okeydokey. I think I resolved my tdepim bug report problem. I'll test your patch as soon as possible!
Darrell
Great!
Can you test it from a clean profile to be sure?
Calvin
Great!
Can you test it from a clean profile to be sure?
I'll test both: an existing and fresh profile. Although the latter always drives me batty because the default window sizes for everything is for a 640x480 screen. At least we purged that accursed bouncing mouse pointer! :)
Darrell
-
Calvin Morrison -
Darrell Anderson