13 Nov
2011
13 Nov
'11
2:48 a.m.
Do we have access to the old KDE web site pages? The Trinity web site provides no package
description pages like the old KDE web site. I think we could use such pages.
I'm no HTML expert but if we have an archive of the old kde web site I am willing to
help massage the old pages into Trinity pages.
Second, I noticed when building the 3.5.13 packages from tarballs that some of the old
/usr/doc files were not part of the binary packages. Fair enough, most of that was stale
and useless. However, there is a readme file in every package and the file says nothing
more than to visit the wiki to learn how to build each package. The wiki is lacking in
specific package information. I can update the wiki but I don't know what is relevant.
That is, I had to heavily patch a few 3.5.13 packages in Slackware, but I don't know
whether that is true for other distros. I had to do some serious head scratching to get
some packages to build and having specific information would have helped.
Perhaps an improved approach is to create a wiki page for each package with instructions
for building. That documentation should be duplicated in the package readme file. Many of
the pages will be repetitive because they require nothing different or unique. Or create
individual pages only for those packages that require different build options. Certainly
any package that requires one or more patches needs that information.
Lastly, long ago I mentioned the idea of a Trinity user's guide. Something that allows
multiple output options, such as HTML, and PDF. Packagers could add a desktop icon to the
generic user profile and first time users would see the icon right away. Several distro
maintainers do this and I always liked the idea. The user's guide would be part of the
Trinity web site too. I am willing to help.
I'm not demanding anything :) --- just trying to start conversations. I welcome that
GIT and bug quashing have priority for 3.5.14. I want that to succeed --- especially the
bug quashing. :) I think documentation is something that can grow and mature on the side.
Do we need a plan?
Darrell
13 Nov
13 Nov
2:50 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
Do we have access to the old KDE web site pages? The
Trinity web site
provides no package description pages like the old KDE web site. I think
we could use such pages.
I'm no HTML expert but if we have an archive of the old kde web site I am
willing to help massage the old pages into Trinity pages.
Second, I noticed when building the 3.5.13 packages from tarballs that
some of the old /usr/doc files were not part of the binary packages. Fair
enough, most of that was stale and useless. However, there is a readme
file in every package and the file says nothing more than to visit the
wiki to learn how to build each package. The wiki is lacking in specific
package information. I can update the wiki but I don't know what is
relevant. That is, I had to heavily patch a few 3.5.13 packages in
Slackware, but I don't know whether that is true for other distros. I had
to do some serious head scratching to get some packages to build and
having specific information would have helped.
Perhaps an improved approach is to create a wiki page for each package
with instructions for building. That documentation should be duplicated in
the package readme file. Many of the pages will be repetitive because they
require nothing different or unique. Or create individual pages only for
those packages that require different build options. Certainly any package
that requires one or more patches needs that information.
Lastly, long ago I mentioned the idea of a Trinity user's guide. Something
that allows multiple output options, such as HTML, and PDF. Packagers
could add a desktop icon to the generic user profile and first time users
would see the icon right away. Several distro maintainers do this and I
always liked the idea. The user's guide would be part of the Trinity web
site too. I am willing to help.
I'm not demanding anything :) --- just trying to start conversations. I
welcome that GIT and bug quashing have priority for 3.5.14. I want that to
succeed --- especially the bug quashing. :) I think documentation is
something that can grow and mature on the side. Do we need a plan?
I tend to agree, and yes we do need a plan. Why don't you add this as a
topic for the Nov. 15 meeting on the Etherpad at
http://trinity.etherpad.trinitydesktop.org/15
Tim
4:11 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
I'm not
demanding anything :) --- just trying to start
conversations. I
welcome that GIT and bug quashing have priority
for
3.5.14. I want that to
succeed --- especially the bug quashing. :) I
think
documentation is
something that can grow and mature on the side.
Do we
need a plan?
I tend to agree, and yes we do need a plan. Why don't
you add this as a
topic for the Nov. 15 meeting on the Etherpad at
http://trinity.etherpad.trinitydesktop.org/15
4:15 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
I'm not demanding anything :) --- just trying to
start
conversations. I
welcome that GIT and bug quashing have priority
for
3.5.14. I want that to
succeed --- especially the bug quashing. :) I
think
documentation is
something that can grow and mature on the side.
Do we
need a plan?
I tend to agree, and yes we do need a plan. Why don't
you add this as a
topic for the Nov. 15 meeting on the Etherpad at
http://trinity.etherpad.trinitydesktop.org/15
10:01 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
It is quite easy to use. The interface is almost
identical to a word
processor; where the power comes in is that you can edit a
document at the
same time as multiple other users. Your changes show
up almost instantly
(i.e. as you are typing them) on connected users'
screens. You can
actually have a slightly delayed discussion with another
user on the
Etherpad while trying to hash out an idea or concept!
Each document is called a "pad". A list of pads is
available once you log
in at http://etherpad.trinitydesktop.org/
. Simply click the pad name to
join the pad and start reading/editing it.
Hope this helps!
Tim
Okay, this is nuts.
I don't remember my account name. Tim or Robert can you find this information?
Darrell
12:26 p.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
On Nov 12, 2011, at 22:02, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
It's the email you're currently using atm :)
It is quite
easy to use. The interface is almost
identical to a word
processor; where the power comes in is that you can edit a
document at the
same time as multiple other users. Your changes show
up almost instantly
(i.e. as you are typing them) on connected users'
screens. You can
actually have a slightly delayed discussion with another
user on the
Etherpad while trying to hash out an idea or concept!
Each document is called a "pad". A list of pads is
available once you log
in at http://etherpad.trinitydesktop.org/
. Simply click the pad name to
join the pad and start reading/editing it.
Hope this helps!
Tim
Okay, this is nuts.
I don't remember my account name. Tim or Robert can you find this information?
14 Nov
14 Nov
7:05 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
On 13 November 2011 00:26, Robert Xu <robxu9(a)gmail.com> wrote:
On Nov 12, 2011, at 22:02, Darrell Anderson
<humanreadable(a)yahoo.com>
wrote:
information?
Hi,
On the note of improving documentation, here looks to be a KWin theme
making guide!
http://kde-look.org/content/show.php?content=6332
Calvin Morrison
It is
quite easy to use. The interface is almost
identical to a word
processor; where the power comes in is that you can edit a
document at the
same time as multiple other users. Your changes show
up almost instantly
(i.e. as you are typing them) on connected users'
screens. You can
actually have a slightly delayed discussion with another
user on the
Etherpad while trying to hash out an idea or concept!
Each document is called a "pad". A list of pads is
available once you log
in at http://etherpad.trinitydesktop.org/
. Simply click the pad name to
join the pad and start reading/editing it.
Hope this helps!
Tim
Okay, this is nuts.
I don't remember my account name. Tim or Robert can you find this
13 Nov
13 Nov
4:15 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
On Sat, Nov 12, 2011 at 16:11, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
First hurdle is I know nothing about etherpad. I am willing to learn, but somebody else
should add the item to the discussion.
Second hurdle is I would like to participate in these meetings, but I know nothing about
etherpad. I have registered an account but I am a proverbial deer in the head lights. What
do I need? What do I do? How do I learn?
Darrell
Etherpad is a real-time, collaborative wiki.
We maintain documents in pads. You can see them by selecting Pads at the top. :)
As you make changes, others will see them in real-time.
Each person has a colour and can use this to contribute their
opinions, thoughts, or ideas.
All changes are saved automatically; to create major revisions, you
can use the save button at the top right to see major revisions or
mark your changes as a major revision.
For instance, if you login right now, you'll see that the November
Meeting has users in it. You can add ideas to it and others will see
them instantly, and have a sort of in-pad discussion. :)
Etherpad is also a great place for checklists. Tim maintains his git
conversion list on here, and we need to put our cmake conversion list
to make stuff easier. We can also raise issues on how bugs should be
solved or what is priority.
--
later daze. :: Robert Xu :: rxu.lincomlinux.org :: protocol.by/rxu
4:23 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
On Saturday 12 November 2011 22:11:20 Darrell Anderson wrote:
First hurdle is I know nothing about etherpad. I am
willing to learn, but
somebody else should add the item to the discussion.
Second hurdle is I would like to participate in these meetings, but I know
nothing about etherpad. I have registered an account but I am a proverbial
deer in the head lights. What do I need? What do I do? How do I learn?
what you need is a browser that can handle javascript well, such as google
chromium, konqueror from TDE will not work :)
the rest is more or less self-explaining.
the document in work can be edited by several persons simultaneously, each
ones contributions are in a specific colour, thus easy to distinguish.
werner
3:21 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
Darrell
I am a HTML expert and would help with any HTML work.
Are you planning on keeping the HTML or converting it to (ugh) wiki format?
I am currently writing the documentation for AutoKey in HTML format
(to be converted to other formats as needed).
Some wikis permit including HTML code. That is what I am doing for
Autokey which is using Google Code hosting.
Keith
3:31 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
Darrell
I am a HTML expert and would help with any HTML work.
Are you planning on keeping the HTML or converting it to (ugh) wiki
format?
I am currently writing the documentation for AutoKey in HTML format
(to be converted to other formats as needed).
Some wikis permit including HTML code. That is what I am doing for
Autokey which is using Google Code hosting.
Keith
We allow HTML formatting tags in our Wiki. My opinion is that the
original documentation pages from Techbase should be left in HTML format,
and simply have the headers and footers replaced with the TDE
headers/footers.
Tim
3:44 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
On Sat, Nov 12, 2011 at 3:31 PM, Timothy Pearson
<kb9vqf(a)pearsoncomputing.net> wrote:
I agree.
I would be glad to help with the alteration, cleanup and replacement
of info in the files selected for insertion into the wiki or any other
similar task that you may require.
Over the years I have written a lot of bash scripts for the conversion
of HTML files on an entire directory basis instead of a file by file
basis. Since a lot of the required changes appear to be identical in
all files I think I can do the conversion fairly rapidly.
Keith
Keith
Darrell
I am a HTML expert and would help with any HTML work.
Are you planning on keeping the HTML or converting it to (ugh) wiki
format?
I am currently writing the documentation for AutoKey in HTML format
(to be converted to other formats as needed).
Some wikis permit including HTML code. That is what I am doing for
Autokey which is using Google Code hosting.
Keith
We allow HTML formatting tags in our Wiki. My opinion is that the
original documentation pages from Techbase should be left in HTML format,
and simply have the headers and footers replaced with the TDE
headers/footers.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
4:22 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
I suggest we create a etherpad page of relevant pages. Ones from all over
the place, not just the tech base.
Calvin
On Nov 12, 2011 3:44 PM, "Keith Daniels" <keithwdaniels(a)gmail.com> wrote:
On Sat, Nov 12, 2011 at 3:31 PM, Timothy Pearson
<kb9vqf(a)pearsoncomputing.net> wrote:
I agree.
I would be glad to help with the alteration, cleanup and replacement
of info in the files selected for insertion into the wiki or any other
similar task that you may require.
Over the years I have written a lot of bash scripts for the conversion
of HTML files on an entire directory basis instead of a file by file
basis. Since a lot of the required changes appear to be identical in
all files I think I can do the conversion fairly rapidly.
Keith
Keith
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Darrell
I am a HTML expert and would help with any HTML work.
Are you planning on keeping the HTML or converting it to (ugh) wiki
format?
I am currently writing the documentation for AutoKey in HTML format
(to be converted to other formats as needed).
Some wikis permit including HTML code. That is what I am doing for
Autokey which is using Google Code hosting.
Keith
We allow HTML formatting tags in our Wiki. My opinion is that the
original documentation pages from Techbase should be left in HTML format,
and simply have the headers and footers replaced with the TDE
headers/footers.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
4:24 a.m.
New subject: [trinity-devel] Improving the Web Site and Adding Documentation
Seems everyone is way ahead of me lol :P
Ill just say a thank you to robert because the Etherpad rocks! Its a really
great tool
On Nov 12, 2011 4:22 PM, "Calvin Morrison" <mutantturkey(a)gmail.com>
wrote:
I suggest we create a etherpad page of relevant pages.
Ones from all over
the place, not just the tech base.
Calvin
On Nov 12, 2011 3:44 PM, "Keith Daniels" <keithwdaniels(a)gmail.com>
wrote:
> On Sat, Nov 12, 2011 at 3:31 PM, Timothy Pearson
> <kb9vqf(a)pearsoncomputing.net> wrote:
> >> Darrell
> >>
> >> I am a HTML expert and would help with any HTML work.
> >>
> >> Are you planning on keeping the HTML or converting it to (ugh) wiki
> >> format?
> >>
> >> I am currently writing the documentation for AutoKey in HTML format
> >> (to be converted to other formats as needed).
> >>
> >> Some wikis permit including HTML code. That is what I am doing for
> >> Autokey which is using Google Code hosting.
> >>
> >> Keith
> >>
> >
> > We allow HTML formatting tags in our Wiki. My opinion is that the
> > original documentation pages from Techbase should be left in HTML
> format,
> > and simply have the headers and footers replaced with the TDE
> > headers/footers.
> >
> > Tim
> >
>
> I agree.
>
> I would be glad to help with the alteration, cleanup and replacement
> of info in the files selected for insertion into the wiki or any other
> similar task that you may require.
>
> Over the years I have written a lot of bash scripts for the conversion
> of HTML files on an entire directory basis instead of a file by file
> basis. Since a lot of the required changes appear to be identical in
> all files I think I can do the conversion fairly rapidly.
>
> Keith
>
> Keith
>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
> > For additional commands, e-mail:
> trinity-devel-help(a)lists.pearsoncomputing.net
> > Read list messsages on the Web archive:
> http://trinity-devel.pearsoncomputing.net/
> > Please remember not to top-post:
> http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
> For additional commands, e-mail:
> trinity-devel-help(a)lists.pearsoncomputing.net
> Read list messsages on the Web archive:
> http://trinity-devel.pearsoncomputing.net/
> Please remember not to top-post:
> http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
>
4827
days inactive
4829
days old
13 comments
6 participants
participants (6)
-
Calvin Morrison -
Darrell Anderson -
Keith Daniels -
Robert Xu -
Timothy Pearson -
Werner Joss