SimpleKDE Thoughts and Views

[obennett]

On Tuesday 27 September 2005 12:10 pm, Wade Olson wrote:
> Yes, browser-basd applications have an easier time with
> shielding/masking/limiting access to dat basd on roles/privs.
>
> At the level of a desktop and corresponding applications, I could see
> it quickly becoming a huge multi-dimensonal matrix mess.  Possible?
> Yes.  Elegant?  No.  Maintainable?  Not by anyone besides the person
> who created it.
>
> I'd hazard and initial guess and say that KDE's own slick layout is
> its own enemy in this case.
>
> Kparts, library reuse,kioslaves..these all contribute to a massive
> impact analysis that would have to be done and maintained.  Such roles
> are easier with huge monolithic silos of code that don't talk to each
> other.
>
> I don't know much about SimpleKDE, but I wouldn't think about it like
> FireFox and Mozilla, where the fork cleans up code and eventually
> becomes the dominant code base in the end.

Firefox wasn't fork, it was an internal mozilla project to create just a 
browser component instead of a whole suite based on gecko. ;-)

>snip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-quality/attachments/20050927/e7a1c8e7/attachment.pgp