unknown
1970-01-01 00:00:00 UTC
</pre>
<blockquote type="cite">
<pre wrap="">I'd like to help !!!
</pre>
</blockquote>
<pre wrap="">Hurray! Please, jump into the boat ;-)</pre>
</blockquote>
I'll grab a life-vest and a manual bilge pump off of my sailboat.<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">[...]
We need to create a developer's roadmap
</pre>
<pre wrap="">need to merge and sort ideas, will be discussed in Randa
</pre>
<blockquote type="cite">
<pre wrap="">and documentation. This is critical.
</pre>
</blockquote>
<pre wrap="">100% agree: it took me so long to roughly understand what happens where, and
there are still many dark areas.
The problem is that there is an obvious need for code refactoring, almost the
1st thing to do, so if we write a doc now it will be quickly (?) obsolete.</pre>
</blockquote>
I don't think the docs would be quickly obsolete. But, before we
tear off into a refactoring effort, just what are we trying to
accomplish w/ a refactor? Are we just renaming variable, routines,
modules and restructuring the source-tree? If so, developer's
documentation will be important to that task.<br>
<br>
So far, from what I've seen, there's no document that spells out the
goals of a refactoring effort. Creating such a document will then
allow us to formulate a plan of action to accomplish the desired
goals.<br>
<br>
Another thing to consider is that gathering system/developer's
documentation will allow us to come up to speed w/ Kdenlive's
architecture before we start tearing it apart.<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">We also need to dispel the myth that
a video editor is way to complicated 'for me' when somebody approaches this
project for the first time.
</pre>
</blockquote>
<pre wrap="">Hum, it's true that it is not so easy in its globality! But I hope that with
another code organization it would be easier to play with internals...</pre>
</blockquote>
Yes..that's the hope !!!<br>
<blockquote cite="mid:***@hpmini" type="cite">
<blockquote type="cite">
<pre wrap="">The developer's roadmap would be an evolving set of documents w/ provisions
for user comments and contributions etc. I think some of these items in
the roadmap need to be in place before we start altering code. Other items
can be filled in as we go along.
</pre>
</blockquote>
<pre wrap="">Problem: this is boring, and good wills have their limits ;-)</pre>
</blockquote>
I don't think the developer's documentation will need to be updated
frequently. We'll have a significant push at first but then things
will slow down.<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">[...]
there's really no way to brace and indent
code other than GNU style. Yes, it increases the vertical size of code
somewhat but do remember that when K&R style was introduced, we were coding
on VT-102 terminals w/ 80x24 screens. (I have an original edition of K&R's
Learning to Program in 'C' book - a classic - but I digress) So, vertical
size was an issue then. Now - not so much. However, in my mind, K&R
style's legacy of hard to read code and style-induced bugs prevails.
As you might have surmised, Kdenlive uses K&R style. So, that would be the
first code change I'd recommend - and it really would not involve any logic
changes whatsoever. It would be relatively straightforward and easy.
Braces on separate lines and 2 character indent levels. I think that
making these changes would be very important to our ability to attract
other coders. Hard to read code is always a turn-off.
</pre>
</blockquote>
<pre wrap="">Just a run of "indent" away...
But actually the free time I'm giving is mostly in the transportations, on a
small 10" (600px height) display, so size matters (a bit) to me!
I didn't think formatting could be such an important issue...
If only we had the same as "go format"?!</pre>
</blockquote>
If you're writing code on a 600px high display, I feel sorry for
you. <span class="moz-smiley-s1"><span> :-) </span></span><br>
<br>
Coding can be frustrating enough as it is...<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">Refactoring the code so that its easier to understand and modify will be
crucial if we are to have a platform that is conducive to encompassing new
features and capabilities. The refactoring effort would also include a
re-organization of the source code tree. This provides a means of
splitting the code into distinct MVC sections and have source files
organized within separate subdirectories. Thanks For Reading This Far !!!
</pre>
<pre wrap="">How long does the last technical discussion date back on this list? :-)</pre>
</blockquote>
Don't know....<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">That's all I've got for right now. I hope some find this interesting and I
look forward to possibly helping out w/ Kdenlive. If anybody has access to
an Oracle DB (you can download and install one for free for
evaluation/development purposes) I'll set you up w/ my Multimedia
framework. It's all of 1.5Mb in size (I rounded up).
</pre>
</blockquote>
<pre wrap="">"free" here is not the one I like, sorry for being sensitive on the topic :-)</pre>
</blockquote>
No worries. I know that Oracle is not for everyone.<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">If you need help setting up an Oracle DB, I can help w/ that too. It's
easier than it looks....
Sincerely.....Steve Guilford...
</pre>
</blockquote>
<pre wrap="">Thanks again for offering your help.
Don't hesitate to go forward: have a look at how to get involved in KDE in
general; you must have a KDE account for forums, so I gess you also can edit
docs in userbase/community wikis. You will have to ask an upgrade to developer
account to be able to push to git (create your branch :-) )...
You can find some help on this list, but also a lot in the global KDE
community.</pre>
</blockquote>
I'm getting 'linked in'....!!! Time to evolve from a lurker to a
participant...!!!<br>
<br>
<pre class="moz-signature" cols="72">--
Steve Guilford
<a class="moz-txt-link-freetext" href="http://www.dbplugins.com">http://www.dbplugins.com</a></pre>
</body>
</html>
<blockquote type="cite">
<pre wrap="">I'd like to help !!!
</pre>
</blockquote>
<pre wrap="">Hurray! Please, jump into the boat ;-)</pre>
</blockquote>
I'll grab a life-vest and a manual bilge pump off of my sailboat.<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">[...]
We need to create a developer's roadmap
</pre>
<pre wrap="">need to merge and sort ideas, will be discussed in Randa
</pre>
<blockquote type="cite">
<pre wrap="">and documentation. This is critical.
</pre>
</blockquote>
<pre wrap="">100% agree: it took me so long to roughly understand what happens where, and
there are still many dark areas.
The problem is that there is an obvious need for code refactoring, almost the
1st thing to do, so if we write a doc now it will be quickly (?) obsolete.</pre>
</blockquote>
I don't think the docs would be quickly obsolete. But, before we
tear off into a refactoring effort, just what are we trying to
accomplish w/ a refactor? Are we just renaming variable, routines,
modules and restructuring the source-tree? If so, developer's
documentation will be important to that task.<br>
<br>
So far, from what I've seen, there's no document that spells out the
goals of a refactoring effort. Creating such a document will then
allow us to formulate a plan of action to accomplish the desired
goals.<br>
<br>
Another thing to consider is that gathering system/developer's
documentation will allow us to come up to speed w/ Kdenlive's
architecture before we start tearing it apart.<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">We also need to dispel the myth that
a video editor is way to complicated 'for me' when somebody approaches this
project for the first time.
</pre>
</blockquote>
<pre wrap="">Hum, it's true that it is not so easy in its globality! But I hope that with
another code organization it would be easier to play with internals...</pre>
</blockquote>
Yes..that's the hope !!!<br>
<blockquote cite="mid:***@hpmini" type="cite">
<blockquote type="cite">
<pre wrap="">The developer's roadmap would be an evolving set of documents w/ provisions
for user comments and contributions etc. I think some of these items in
the roadmap need to be in place before we start altering code. Other items
can be filled in as we go along.
</pre>
</blockquote>
<pre wrap="">Problem: this is boring, and good wills have their limits ;-)</pre>
</blockquote>
I don't think the developer's documentation will need to be updated
frequently. We'll have a significant push at first but then things
will slow down.<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">[...]
there's really no way to brace and indent
code other than GNU style. Yes, it increases the vertical size of code
somewhat but do remember that when K&R style was introduced, we were coding
on VT-102 terminals w/ 80x24 screens. (I have an original edition of K&R's
Learning to Program in 'C' book - a classic - but I digress) So, vertical
size was an issue then. Now - not so much. However, in my mind, K&R
style's legacy of hard to read code and style-induced bugs prevails.
As you might have surmised, Kdenlive uses K&R style. So, that would be the
first code change I'd recommend - and it really would not involve any logic
changes whatsoever. It would be relatively straightforward and easy.
Braces on separate lines and 2 character indent levels. I think that
making these changes would be very important to our ability to attract
other coders. Hard to read code is always a turn-off.
</pre>
</blockquote>
<pre wrap="">Just a run of "indent" away...
But actually the free time I'm giving is mostly in the transportations, on a
small 10" (600px height) display, so size matters (a bit) to me!
I didn't think formatting could be such an important issue...
If only we had the same as "go format"?!</pre>
</blockquote>
If you're writing code on a 600px high display, I feel sorry for
you. <span class="moz-smiley-s1"><span> :-) </span></span><br>
<br>
Coding can be frustrating enough as it is...<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">Refactoring the code so that its easier to understand and modify will be
crucial if we are to have a platform that is conducive to encompassing new
features and capabilities. The refactoring effort would also include a
re-organization of the source code tree. This provides a means of
splitting the code into distinct MVC sections and have source files
organized within separate subdirectories. Thanks For Reading This Far !!!
</pre>
<pre wrap="">How long does the last technical discussion date back on this list? :-)</pre>
</blockquote>
Don't know....<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">That's all I've got for right now. I hope some find this interesting and I
look forward to possibly helping out w/ Kdenlive. If anybody has access to
an Oracle DB (you can download and install one for free for
evaluation/development purposes) I'll set you up w/ my Multimedia
framework. It's all of 1.5Mb in size (I rounded up).
</pre>
</blockquote>
<pre wrap="">"free" here is not the one I like, sorry for being sensitive on the topic :-)</pre>
</blockquote>
No worries. I know that Oracle is not for everyone.<br>
<blockquote cite="mid:***@hpmini" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">If you need help setting up an Oracle DB, I can help w/ that too. It's
easier than it looks....
Sincerely.....Steve Guilford...
</pre>
</blockquote>
<pre wrap="">Thanks again for offering your help.
Don't hesitate to go forward: have a look at how to get involved in KDE in
general; you must have a KDE account for forums, so I gess you also can edit
docs in userbase/community wikis. You will have to ask an upgrade to developer
account to be able to push to git (create your branch :-) )...
You can find some help on this list, but also a lot in the global KDE
community.</pre>
</blockquote>
I'm getting 'linked in'....!!! Time to evolve from a lurker to a
participant...!!!<br>
<br>
<pre class="moz-signature" cols="72">--
Steve Guilford
<a class="moz-txt-link-freetext" href="http://www.dbplugins.com">http://www.dbplugins.com</a></pre>
</body>
</html>