>I added renaming rbkdeapi => rbtdeapi, rbkdesh => rbtdesh.
>
>The patch is large, so it is possible that we overlooked
>something.
>However, due to size of the patch, I consider it better first to
>push
>this patch to GIT and then if we find some problems, solve them as
>additional patches.
>
>What is your opinion?
That is what I thought too. There might be some corner cases missed
in a patch this large, but we need to have a starting point. So
push the monster.
Not to sound pedantic, but that is one reason I keep asking for a
simple how-to for guiding users with testing tdebindings. There are
some test files in the sources but I never got them to function.
Darrell
>Small update: Updated date-tag conditions for the new rules.
>Renaming
>tdestyle encapsulated as a separate rule - to separate date-tag
>condition.
Thank you. Pushed to git in commit 75561520.
Darrell
I happened to be browsing and stumbled across this:
http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blo…
In it, the journalist shows how the press kit of openSUSE is an
example for all to follow.
Here is a ling to said press kit:
https://github.com/openSUSE/Press-Kit/zipball/12.3
Note that it is 37 MB.
Since the project was looking for testimonials, I post this so it
might generate some new ideas.
Shalom
--
Bro. Michael Henry
Associate Pastor
Monticello Christian Church
1 Timothy 1:15 "This is a faithful saying, and worthy of all
acceptation, that Messiah Jesus came into the world to save sinners;
of whom I am chief."
>1) Names of java classes are derived from the domain name. I
>watched that
>tde.org domain is owned by The Duke Endowment. Although it seems
>that this
>domain is not used, I think it would be appropriate instead of
>org.tde.* use
>our domain - org.trinitydesktop.* What is your opinion?
Sounds fine to me!
>2) In the patch was typo - slash before 'org' was sometimes
>doubled.
>
>Fixed.
Wow, if that is all you found then I am flabbergasted. I know
nothing about java and much of my patching was pure guessing. I
focused only on renaming kde->tde.
Well, the old adage is true: even blind hogs occasionally find
nuts. :)
>An updated patch is available in my 'rsync' resource tde-patches-
>verify. I tried to build and was successful.
If you are content then push to git. :)
Darrell
Slavek,
I ran into a strange bug on my system. Long story short, part of
the problem I traced to incomplete updates of the ktexteditor_
string.
Attached is another r14-xdg-update patch. Please review.
I modified the test for $PROFILE_DIR/share/apps/tdestyle and kstyle
from -f to -d. On my system there are no files of that name in
$TDEHOME/share/apps, only directories.
I tested the patch here. The update fixed all straggling
ktexteditor_ strings and moved my $TDEHOME/share/apps/kstyle
directory to $TDEHOME/share/apps/tdestyle, which had never been
done with previous versions of r14-xdg-update.
Darrell
>Has anyone approached the endowment and asked if they would
>release tde.org to
>the project? It may well be worth a shot. I for one would much
>prefer tde.org
>over trinitydesktop.org (just from a typing standpoint)
Who types URLs any more? :)
My two cents: I prefer trinitydesktop.org.
Darrell
>Wow, many times I thought that it might be proper to rename some
>parts in
>tdebindings - such as in java org.kde. => org.trinitydesktop. Glad
>to
>hear that you decided to do it! We can find another way to pass
>the
>patch, to I could see patch before will be pushed to git?
Here is the patch (not archived or compressed):
http://humanreadable.nfshost.com/misc/tdebindings-kde-tde-
rename.diff
The patch is about 38 MB.
Feel free to improve any way you want.
Please test. Push to git when you are content.
Darrell
>What makes marketing of opensuse different from trinity is
>that opensuse
>work on a defined release schedule and has always done a number of
>things to
>beat the drum about their release number next.
We have plans to enact a maintenance release schedule after we
release R14.0.0. Tentatively set at every 90 days. As is true with
any software project, we keep pecking away at the "paper cuts," but
a 90 maintenance release schedule also keeps Trinity in the news.
>I see marketing for tde as giving some love and attention to the
>wiki to insure
>that it is a welcoming and informative place for new users and
>distros to check
>out, learn from and get involved. There were good etherpad efforts
>in the past
>that probably still contain a wealth of information that has not
>made its way
>into the wiki. I know we all have nothing but spare time, so the
>wiki gets its
>love as time permits (though candidly, I do think it could use a
>bit, and I've
>always pointed to the Archlinux wiki as a model of how to do a
>distro with a
>code base integrated with it)
Ah yes, spare time. I have no idea how to resolve that. Would be
nice, even if only for a few days, to relive the days when Trinity
patches were being submitted almost hourly and folks like you and I
were testing just as fast the patches were submitted. :)
>When is the next tde meeting scheduled? We could put
>marketing/wiki on the
>agenda and at least firm-up a direction to take in making whatever
>improvements
>make sense. (hell, I might even get my freenode nick to register
>correctly for
>once...) Keep the list posted on the schedule.
We already have etherpads documenting such tasks. We don't need
meetings where typically, after all is said and done, more is said
than ever gets done. Instead we need able-bodied people to step
forward and help. Anybody can create a wiki account and edit,
reorganize, etc. Any Trinity user can review help handbook
documents and post review comments to this list --- I'll update any
such reviews. Somebody out there in Trinity user land has web
skills to create a proposed mockup for web site changes.
As the Nike logo says, "Just do it." :)
Darrell
>In tdebindings source code, there are a few folders called "test".
>They contain simple files written in Java, Python and Ruby that
>should test some of the tdebindings functionality.
>I doubt these are exhaustive tests, but they should serve as a
>good starting point.
A long while back I remember testing those files. They didn't work.
I don't know whether the problem is the files, changes made to
tdebindings, me, or some combination thereof.
If the files do work we still need some notes somewhere how to
properly use the files to test tdebindings.
As a group, we've treated tdebindings as a black sheep way too long.
Darrell
>That's cool but are end users (like me) expected to compile
>LibreOffice in order to use it with Trinity or will binaries be
>offered. If binaries will be offered, the the wiki needs to be on
>a
>developer only wiki. My mother and sister just want to type
>letters
>not compile. Just saying.
Understood, but this is the developer's mail list, not the user's
mail list. The task list is legitimate for this mail list. :)
Yes, users are not concerned with such tasks, but the developers
are. Much of the focus of the wiki is for developers.
Darrell
