I was considering opening an enhancement request to add some missing features to Kate. Specifically, adding a word count feature is what motivated me.
Rather than file an enhancement request for adding a word count feature, I decided to first request a list of Kate scripts that all of you find useful. The key is "find useful" because there probably are hundreds or thousands of scripts floating around the web that could be added to Trinity. A word count script is useful. :)
At this point I don't know whether the scripts should be added as part of tdeaddons or posted someplace at the wiki or web site. We can decide that later. Possibly we can vote and the most popular half-dozen can be added to tdeaddons and the remainder posted to the wiki or web site.
If you use any such scripts, please share the name of the script and a full description. Either attach a copy to your email or post a link to the script.
A full description is important because file names often are cryptic and do not lend well toward understanding the script's purpose.
By the way, I found some word count script candidates:
http://muzso.hu/2007/06/08/word-count-in-kate http://kde-look.org/content/show.php/Kate+script%3A+Word+Count?content=13604... http://old.nabble.com/Re%3A-Kate-external-tools-p3788414.html
I have yet to test. :)
Thanks!
Darrell
There are two "different" types of scripts you can use with Kate.
The ones in the links below which, call kate and operate on the entire file--externally.
The ones that are called using the Kate built in "Filter Text" command that only applies to highlighted text inside Kate--using the keyboard shortcut Ctrl+\ for instance.
Do you want both types or only those that run from external scripts, like the examples you gave?
Keith
On Fri, Feb 24, 2012 at 2:27 PM, Darrell Anderson humanreadable@yahoo.com wrote:
I was considering opening an enhancement request to add some missing features to Kate. Specifically, adding a word count feature is what motivated me.
Rather than file an enhancement request for adding a word count feature, I decided to first request a list of Kate scripts that all of you find useful. The key is "find useful" because there probably are hundreds or thousands of scripts floating around the web that could be added to Trinity. A word count script is useful. :)
At this point I don't know whether the scripts should be added as part of tdeaddons or posted someplace at the wiki or web site. We can decide that later. Possibly we can vote and the most popular half-dozen can be added to tdeaddons and the remainder posted to the wiki or web site.
If you use any such scripts, please share the name of the script and a full description. Either attach a copy to your email or post a link to the script.
A full description is important because file names often are cryptic and do not lend well toward understanding the script's purpose.
By the way, I found some word count script candidates:
http://muzso.hu/2007/06/08/word-count-in-kate http://kde-look.org/content/show.php/Kate+script%3A+Word+Count?content=13604... http://old.nabble.com/Re%3A-Kate-external-tools-p3788414.html
I have yet to test. :)
Thanks!
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
There are two "different" types of scripts you can use with Kate.
The ones in the links below which, call kate and operate on the entire file--externally.
The ones that are called using the Kate built in "Filter Text" command that only applies to highlighted text inside Kate--using the keyboard shortcut Ctrl+\ for instance.
Do you want both types or only those that run from external scripts, like the examples you gave?
I don't want to limit the scope of how kate could be used. Let's embrace both types. :)
I don't know where this discussion will lead. If we obtain a decent collection of scripts we then decide how to make them available to Trinity users. Probably for starters we create a wiki page and host the scripts and descriptions there.
Darrell
On Saturday 25 February 2012 00:26:35 Darrell Anderson wrote:
I don't want to limit the scope of how kate could be used. Let's embrace both types. :)
I don't know where this discussion will lead. If we obtain a decent collection of scripts we then decide how to make them available to Trinity users. Probably for starters we create a wiki page and host the scripts and descriptions there.
this is where a handy kde4 feature comes to mind: GHNS (get hot new stuff). maybe worth checking out/porting to trinity ?
werner
On Saturday 25 February 2012 00:26:35 Darrell Anderson wrote:
I don't want to limit the scope of how kate could be used. Let's embrace both types. :)
I don't know where this discussion will lead. If we obtain a decent collection of scripts we then decide how to make them available to Trinity users. Probably for starters we create a wiki page and host the scripts and descriptions there.
this is where a handy kde4 feature comes to mind: GHNS (get hot new stuff). maybe worth checking out/porting to trinity ?
werner
Hot New Stuff was actually a KDE3 feature that TDE still retains. ;-)
Tim
On Saturday 25 February 2012 08:45:14 Timothy Pearson wrote:
Hot New Stuff was actually a KDE3 feature that TDE still retains. ;-)
ok, then I got it wrong, obviously :) (maybe I tried it first with kde4, so the incorrect recognition..)
werner
On 25 February 2012 02:55, Werner Joss werner@hoernerfranzracing.de wrote:
On Saturday 25 February 2012 08:45:14 Timothy Pearson wrote:
Hot New Stuff was actually a KDE3 feature that TDE still retains. ;-)
ok, then I got it wrong, obviously :) (maybe I tried it first with kde4, so the incorrect recognition..)
werner
GHNS is cool.
I was thinking however, since scripts are small in size, we could just at them as defaults. It doesn't seem to be much overhead.
What do you guys think of that?
GHNS is cool. I was thinking however, since scripts are small in size, we could just at them as defaults. It doesn't seem to be much overhead.
What do you guys think of that?
As I mentioned in a previous post, perhaps we vote and select a half dozen or dozen scripts to include in the default packaging. The default is the scripts are disabled but appear in the Settings configurations for the new user. The remainder of any scripts we want to support could be available at the wiki.
This discussion now raises another point. If Trinity supports a Get Hot New Stuff option, should we check through all of the sources and update the URL to a Trinity location?
Darrell
On Saturday 25 February 2012 18:06:00 Darrell Anderson wrote:
GHNS is cool. I was thinking however, since scripts are small in size, we could just at them as defaults. It doesn't seem to be much overhead.
What do you guys think of that?
As I mentioned in a previous post, perhaps we vote and select a half dozen or dozen scripts to include in the default packaging. The default is the scripts are disabled but appear in the Settings configurations for the new user.
this would be ok, IMHO.
The remainder of any scripts we want to support could be available at the wiki.
well, that was the point where I think GHNS makes much more sense. I don't think normal users would regularly search a wiki for addons for individual applications.
This discussion now raises another point. If Trinity supports a Get Hot New Stuff option, should we check through all of the sources and update the URL to a Trinity location?
agreed - this way would also prevent to point to outdated/inexistent locations, or those which are intended for kde4 only (thus incompatible with trinity).
Werner
On 25 February 2012 12:25, Werner Joss werner@hoernerfranzracing.de wrote:
On Saturday 25 February 2012 18:06:00 Darrell Anderson wrote:
GHNS is cool. I was thinking however, since scripts are small in size, we could just at them as defaults. It doesn't seem to be much overhead.
What do you guys think of that?
As I mentioned in a previous post, perhaps we vote and select a half
dozen
or dozen scripts to include in the default packaging. The default is the scripts are disabled but appear in the Settings configurations for the
new
user.
this would be ok, IMHO.
The remainder of any scripts we want to support could be available at the wiki.
well, that was the point where I think GHNS makes much more sense. I don't think normal users would regularly search a wiki for addons for individual applications.
This discussion now raises another point. If Trinity supports a Get Hot
New
Stuff option, should we check through all of the sources and update the
URL
to a Trinity location?
agreed - this way would also prevent to point to outdated/inexistent locations, or those which are intended for kde4 only (thus incompatible with trinity).
Werner
Many parts of the kde-look website have seperate subsections for kde3.X
series items. For example window manager styles exists for 3 and 4.
I think in those cases it does not nee to be removed, and there is a lot of older themes and utilities out there that could be good.
Calvin
On Saturday 25 February 2012 18:29:10 Calvin Morrison wrote:
Many parts of the kde-look website have seperate subsections for kde3.X series items. For example window manager styles exists for 3 and 4. I think in those cases it does not nee to be removed, and there is a lot of older themes and utilities out there that could be good.
sure - things that work with trinity should not be changed/removed/duplicated elsewhere. my intention was more to ensure that GHNS references in trinity actually work.
Werner
-
Calvin Morrison -
Darrell Anderson -
Keith Daniels -
Timothy Pearson -
Werner Joss