On Thursday, January 31, 2013 13:03:11 Marco Martin wrote: > develop. also, scales in the sense that being an application something > quite isolated that just a couple of developers can work on, is easy to > have, say 1000 developers working to produce software on it, without > significant coordination problems.
i don't think this is a real problem .. apps do not need to have their settings in this theoretical Management/Settings area, but they are nicer if they do and it just means installing a Plasma Active Settings package. apps that are content creators are the minority, and to be included in Create they should only need to include a .desktop file. relative to the rest of the tasks, this seems relatively simple, and could be partly automated with some SDK tools. another example that came to mind is transportation. say i want to take a train to münchen. well, i could just fire up the SBB app (e.g.) which may have none of the fun integration bits and so just appear with the rest of the consumption apps. ooor... i could have a nicely integrated version of the application which adds "travel plan" to Create. so i see it as an optional thing, and one we take full advantage of in our applications and hope others will follow suit. > Also it shouldn't feel like something that gives the impression of forcing > the user to "compile a bureaucratic form" before being allowed to do > something is it more bureaucratic though? the current situation is: * know which app you need to create your $THING. or search for it if you don't. * launch it * create your $THING * save the results somewhere * now do whatever else you need to do with the file starting at step 1 the new situation would be: * state what you want to create (this should be no faster nor slower than launching an app from the launcher now; at most 1 extra press) * create your $THING * say "i'm done!" * have the next steps (if any) automatically started using the results taking that one moment to say "i want to write a letter", which is already in your head, is not particularly bureaucratic, is it? > in the end, is important for me that anything we design is not something > that is heavier (as resources), feels heavier (as user experience) and > feels hostile for 3rd party developers. agreed. > I believe is possible to design something that is nothing o the above, we > just have to constantly keep in mind that yep -- Aaron J. Seigo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Active mailing list [email protected] https://mail.kde.org/mailman/listinfo/active
