In this week's KDE CVS-Digest: New KDE system sounds.
Digikam has a histogram viewer, new camera kioslave, image editor, HSL balance correction plugin.
Kexi adds two run modes; final mode and design mode.
New icons for Juk, Kommander, new splash screen for KDE.
Plus many bug fixes in preparation for the release.
Dot Categories:
Comments
"Kommander is also being developed to be the ultimate tool for in house vertical market software."
Apologies - but what exactly is 'in house vertical market software'?
I've never heard of vertical market software... What's vertical market?
Just curious.
Thanks!
http://en.wikipedia.org/wiki/Vertical_application
http://en.wikipedia.org/wiki/Vertical_Market
'in house vertical market software'
Sounds like a contradiction in terms to me. Software which is 'in house' doesn't get marketed by definition.
A vertical market is a business area such as financial services or GIS or whatever. A horizontal market is something generic like word processing or spreadsheets which all sorts of types of business will use.
"'in house vertical market software'
Sounds like a contradiction in terms to me."
Not to me.
In-house = written by the local IT
Vertical market = Software that fills a certain specific need
In-house vertical market software = Software written in house by the local IT to fill a need for certain specific need inside the company.
And that software DOES get marketed: To the users of the software inside the company! Just because they don't sell it for revenue, does not mean it's not marketed.
"And that software DOES get marketed: To the users of the software inside the company!"
I'm sorry that isn't marketing, that's selling. There is only one buyer and one seller involved.
For a market you need one or more buyers, and two or more sellers who are *competing*.
Semantics. Marketing might as well mean in this case "hey, your workstation has this new whiz-bang app that you can use to accomplish xxxxxxxx". Of course the users could use something else to do the same thing. So even if we follow your definition, there would still be marketing involved.
And, like I said: it's just semantics. You know perfectly well what was meant, you are just arguing whether some word means some specific thing or not. in short: arguing for the sake of arguing.
No, we're not just discussing 'semantics', someone originally asked for clarification of what Eric Laffoon was talking about, otherwise I wouldn't have said anything.
Janne was right. Maybe it was a poor choice of terms or maybe it was just what made sense in my mind combining the phrases. To my mind vertical market software does not have to be developed externally and the idea that it can be done very quickly for specific needs would be very appealing for a company considering using KDE.
It's fun to get in after a long weekend and see something I said is the first thing disputed here. ;-) I met a guy on Saturday at my booth who lives in New York City and works for a company that has something like 1000 KDE desktops. I thought he said he was going to be converting another 1000, and I really wanted to talk with him more on it but we were too busy. I hope he emails me. Anyway he was excited about Quanta and I mentioned using Kommander to quickly develop in house small applications and integration. He was familiar with Kommander and was quite excited it's development and using it. I'm hoping he can give us some good testimonials of KDE and Kommander use in the future.
"Janne was right. Maybe it was a poor choice of terms or maybe it was just what made sense in my mind combining the phrases. To my mind vertical market software does not have to be developed externally and the idea that it can be done very quickly for specific needs would be very appealing for a company considering using KDE."
Well, if it was a poor choice of terms, and all I was doing was pointing that out, I fail to see how I was wrong..
How about calling Kommander 'a killer tool for scripting in house custom applications'?
IMO 'custom application' is a much better name than 'in house vertical market application'
or better:
'a killer tool for visually scripting in house custom applications'
'a killer tool for visually scripting in house custom applications'
Well this illustrates why it is so hard to come up with a descriptive phrase... Maybe "visually building" is better because while you can do scripting you can also rely on internal DCOP functions, which could be called scripting, but is not in the classical sense. Besides, scripting usually implies a script language builds the GUI. To paint the right picture means saying too little or too much.
To me it is an attempt to make small to medium size application building comparable to working with a spreadsheet for ease of use. There are a number of improvements needed to make it really friendly, but it's making good progress. It will also change shortly when we switch to K(exi) Form Designer which means we could remove licensing issues if someone wants to resell Kommander programs. Because they can be compiled to binary it adds an interesting twist. In a few months we will probably have a version with a new editor that natively does KPart creation and loading, MainWindow and wizards (without having to use Designer), menu and action support and more. Then we can discard even more constraints from the description. ;-)
"Kexi adds two run modes; final mode and design mode."
A Small contest: could somebody invent more appropriate term for "final mode"? , i.e. the application mode provided for end-user (without design tools).
Design mode and production mode.
Rich.
We call that sort of thing 'Target Mode' in our area of work, but Production is good, too, and prolly better for the lay person :)
I prefer "user mode", that's the mode the users see!
"production mode"? That's the mode used for production, maybe almost the same like "design mode".
The businesses that I've worked at have all used the term "production environment" to mean "computers the end-users are actually using". I've never really thought about why that is called "production", though.
kexi runtime? runtime mode might sound silly, dunno.
I like it, actually...
(however, "runtime" would be difficult to translate to Polish, nie, Jarku?)
We've one problem with "runtime" term: it's already reserved for Runtime Mode (i.e. the one that allows to use a database app created with Kexi without Kexi environment, i.e. a binary).
And yes, most of these terms are damn hard 1-to-1 translatable to Polish (and other langiages too, I suppose).
Hmm... I thought that "binary" mode was the one you were talking about.
Sounds like what you have is a development/design mode, a binary/runtime/standalone app mode, and what you want a name for would be a "preview" mode?
Oh, I thought that was what was referred to in the original request?
How about design and release mode.
or design and work mode?
Uhm, what about "Preview mode" for example ? I think everyone would get its meaning, fast ;-).
Design and use(r) mode. It is clear and short.
Very hard to live 1 week without KDE-CVS Digest !
Gerard
Agreed. This great for the KDE userbase to keep track of what is going on inside KDE. Keep up the great work and thanks from this KDE user. :)
I enjoyed it :)
A thought occurred to me when reading the lwn report on X.org. I would enjoy reading a commit digest for that project. Is anyone interested in producing one?
Derek
subject
Nope, not at all. It's categorised, so all you have to do (if you find it too long) is scroll down to the relevant section. I'm not interested in EVERY KDE application etc, but it's still good to see the amount of work being done, and interest that is out there.(and seems to be still growing)
My congratulations and thanks to Derek, but I think he should ask next time before he takes a week off!! :o)
Agreed. Now, does anyone know where KDE Traffic has gone?
With more that 128.000 lines written in the last 2 weeks this guy must be exhausted :) I'd recommend sleep;)
Those are translations; they always pick up around this time in the release cycle.
Everytime I look at this list (http://i18n.kde.org/stats/gui/HEAD/toplist.php)
I ask myself what's the criterion for ordering this list?
"translated", "fuzzy" or sum of both?
I do't get it.
It is clearly sorted by "translated".
1. Swedish 99880 translated
2. Portuguese 99859 translated
and so on.
("Fuzzy" is not much different that untranslated.)
Have a nice day!
OK, but what are the green bars good for, which reflect the translated messages?
Obviously the length is computed wrong.
Take a look at the bottom of the page. There is a legend for the graph.
Green = percentage of translated strings
Blue = percentage of fuzzy strings
Red = percentage of untranslated strings
The bars are in percent, not in absolute numbers.
And as a team can have more or less messages than it should have, you can have a total message number that is different. In that case, the green bar does not look sorted anymore (for example currently Hindi at position 27.)
Have a nice day!
German on PLACE 17 ? i thought may developers of KDE are in Germany , so why is the german translation this bad ?
developers!=translators && motivation(coding)!=motivation(translating)
As everywhere in KDE, you need volunteers...
(See http://i18n.kde.org/teams if you want to become a translator.)
Have a nice day!
What is the reason, that column 9 ("total") has different values for
the various languages?
Maybe missing po-files?
Shouldn't be the value in column 9 the same for all languages?
Shouldn't be the percentage related to the maximum amount of messages available in the default language?
In this case the length of the bars would reflect the sorted list.
No, the total should be what it really is, not what it is supposed to be.
Good, for the bars, it would perhaps look better the other way round, but as far as I know, the statistics are mainly for the teams and were not meant for a "hall of fame", like this page.
Have a nice day!
Anyone know if Umbrello CVS supports Ruby yet?
I know someone was working on it, but couldn't contact the Umbrello team/author:
http://www.rubygarden.org/ruby?action=browse&id=RubyAndUML
Has that changed?
I would like to thank the Rosegarden team for their really astonishing piece of software. I tried out version 0.9.7 and found it excellent. I just wanted to communicate this as an encouragement to you. Thanks!
The only two limitations I have found are the midi set up on my notebook and when printing out, I was unable to change the size of the margins. The first one I'll try to solve in the next few weeks, the latter one you might have resolved already in 0.9.9.
Just once again: thank you very much for your great programme!
BTW: great idea with the sample files!
Markus
i second this, creating an application like rosegarden requires the most advanced GUI programming skills (widgets and painting), realtime programming skills, and deep knowledge of one (or no, two, err 3) media layers.
thanks, and keep up the good work !
with those nifty desktop switching sounds, I might be trying to make cool melodies instead of getting work done.
the new sounds are excellent.