Hi All
I have a marketing/advertising background. The following suggestion
is primarily aimed at increasing the name recognition of "Trinity
Desktop" but should have other useful side effects as well.
This idea is structurally similar to the concept of "loss leaders"
that commercial stores use to entice people to come to their store, in
the hopes that they will buy something else while they are there
(which they usually do).
Darrel's suggestion of offering Kate scripts to the Trinity Desktop
audience started me thinking about this idea.
If we had something on the Trinity Desktop web site that people need
or want (outside of Trinity itself), and that could be found through a
Google search--they would go there to check it out and while there...
be able to read what Trinity Desktop is, and what it is trying to do.
If they find things they want and that help them (scripts in this
case) they will post about what they found on social networks, blogs
and forums. If they like what they read about Trinity Desktop, they
will post about that as well--whether or not they are interested in
using Trinity Desktop or not.
These postings would increase hits to the Trinity Desktop site, and
cause it to rise in Google ratings. This hopefully would put Trinity's
matches in the first 100 results of a Google search--which would
radically increase the hits on the Trinity Desktop site and name
recognition.
My idea is to start a "Trinity Desktop scripts" webpage or forum
containing user submitted scripts. This should be interactive and
monitored so I think something like a forum would be the best idea.
The site/page would be based around the concept of "Useful scripts
that can help you to learn scripting as well". It would include
scripts that could be used from Konsole or from inside Kate or
Konqueror (which sometimes have to be structured differently than
standard scripts). Information on how to use scripts inside Kate and
Konqueror would also be available.
To have a script accepted, a vote or committee approval would be
needed. Besides being useful (either in actual use or in learning to
script) the script would have to be heavily documented by the writer
so that the "what" and "why" of the script could be understood by
users not familiar with scripting (the majority of them).
What doing this would require:
1 - A web or forum page.
2 - Someone to create & monitor the page.
3 - Someone to manage the submissions, uploads and page entries for the scripts.
4 - Someone(s) to write a Trinity Desktop oriented description of each
script -- the authors are usually terrible at this.
5 - People (or a voting system) to look at and and approve the scripts
and descriptions.
To seed this site/page--all of us could post of its existence on
social network, forum and wiki sites that we are members of.
I will volunteer to create and manage the web page (if it is not a
wiki). Being a retied webmaster I have the skills to do so. Note
that I will be on the road from mid April to late June. I could start
it and set it up--but would not be able to put a lot of time into it
until after June.
I personally have been considering doing something like this for the
last 5 years as a personal project--so it is not a new concept for me.
Because of this my scripts are already heavily documented and ready
to use. I have somewhere between 50 and 100 scripts that I think would
qualify, and that are ready to be posted. I am sure the rest of you
have quite a few scripts as well. This means that an impressive
number of scripts could be put up rapidly, providing the variety
needed to attract viewers.
Thoughts?
Another useful page/site similar in effect to the above would be one
that specialized post and information on how to modify the appearance
and function of menus, toolbars, popups, etc. for Trinity Desktop
programs.
Keith
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-katehttp://kde-look.org/content/show.php/Kate+script%3A+Word+Count?content=1360…http://old.nabble.com/Re%3A-Kate-external-tools-p3788414.html
I have yet to test. :)
Thanks!
Darrell
For those who have Trinity installed from GIT.
From the TDE Menu, select Help.
When KHelpCenter opens, on the left side, top, in the navigator tabs, scroll to the far left to select the Contents tab.
Open/expand Application Manuals.
Open/expand Development.
Do you see individual apps or only categories?
Thanks!
Darrell
In Konqueror (built from GIT), I no longer see the tiny expansion and contraction widgets to the left of a folder. The little plus and minus in a box. Nothing I do makes the widgets appear.
Would somebody confirm this behavior?
Thanks!
Darrell
Guys,
Working with the current tarballs compared with those created from the git
tree I have run into a difference in path information included in the existing
tarballs instead of those created from a local copy of the git tree. The
existing tarballs referenced in the PKGBUILD scripts contain the dependencies
path information i.e.:
dependencies/tqtinterface/
dependencies/tqtinterface/TODO
dependencies/tqtinterface/ConfigureChecks.cmake
dependencies/tqtinterface/COPYING
dependencies/tqtinterface/CMakeLists.txt
dependencies/tqtinterface/configure.in.mid
dependencies/tqtinterface/qtinterface/
dependencies/tqtinterface/qtinterface/tqlcdnum.h
dependencies/tqtinterface/qtinterface/parser2.sh
While those I create from the git tree simply contain e.g.:
tqtinterface/CMakeLists.txt
tqtinterface/configure.in.bot
tqtinterface/AUTHORS
tqtinterface/admin/
tqtinterface/configure.in.mid
Is prefixing the files in the tarball with the entire directory path below
'main/' going to be the standard? In the past, I have always excluded the module
prefix (applications, common, dependencies, libraries, ...).
Either way will work, but from a PKGBUILD standpoint, we need to make sure
there is a standard. What is the consensus?
--
David C. Rankin, J.D.,P.E.
I have completed the list to the best of my knowledge. I listed the two needed updates that I know of. It also contains a list of apps, all that I could glean from the source tarballs for 3.5.13 are listed by package (e.g. base, network, pim, etc.), and each section is alphabetical to make finding the apps in the list a bit easier. The apps list needs adjusting for the name changes in git.
The list is at:
http://trinity.etherpad.trinitydesktop.org/43
Feel free to contribute.
--
Kris Gamrat
Skilled with perl? Here are some nuisance bug reports that need resolving:
719 Koffice: unknown icon types (http://bugs.pearsoncomputing.net/show_bug.cgi?id=719)
804 gwenview: unknown icon type (http://bugs.pearsoncomputing.net/show_bug.cgi?id=804)
805 tdeutils: unknown icon type (http://bugs.pearsoncomputing.net/show_bug.cgi?id=805)
806 kipi-plugins: unknown icon type (http://bugs.pearsoncomputing.net/show_bug.cgi?id=806)
807 tdeaddons: unknown icon type (http://bugs.pearsoncomputing.net/show_bug.cgi?id=807)
All we need to know is how to rename the problematic files and I'll create the patches.
My troubleshooting reveals the build warnings are caused by the way the perl scripts parse the names of the file names. The perl scripts are looking for specific prefixes in the file names. The trick is to figure out the correct file name. That's where the perl skills are needed.
For example, the problematic files in gwenview are imageops.svg and imageops.svgz. I can resolve the problem by renaming those two files to hisc-action-imageops.svg and hisc-action-imageops.svgz. I lack perls skills to resolve the other bug reports.
The specific perl script that parses the file names is named am_edit and is located in the admin directory of each package. Search each am_edit script for the error message reported in the bug report. That will bring you to the section of code that causes the error messages. For example, for gwenview, search for "unknown icon type" in am_edit and the previous lines of code will be how the script parses the file names.
Please let me know whether you need further information.
Thank you!
Darrell
Archers,
Please look at the attached PKGBUILD for libart-lgpl. It pulls the source
either directly from the git tree on the local machine (after updating it), or
it clones directly from scm.trinitydesktop.org. I looked over the existing
pkgbuilds that use git in one form or another in ABS and this is my prototype
for how we could do the remaining build scripts.
Let me know what changes you propose.
--
David C. Rankin, J.D.,P.E.