Talk:KDEEdu: Difference between revisions

(One intermediate revision by the same user not shown)

Line 9:

3. reprogram it to be compatible with sugar - toolbar, rainbow security, autosave, dbus, etc. This is the real work of sugarizing. It is better if you can avoid forking the application - if it provides its interface via widgets which you can rearrange via another layer you put above. You would have to research whether this is possible.

4. document the above so it's easy to do with other kdeedu activities. (It would be cool if you could figure out some strategy to avoid repeatedly downloading 20MB of QT, yet still rely on just .xo packages without real package or dependency management.)

4. document the above so it's easy to do with other kdeedu activities.

5. (optional) It would be cool if you could figure out some strategy to avoid repeatedly downloading 20MB of QT, yet still rely on just .xo packages without real package or dependency management.

Steps 1 and 2 should be relatively simple. I have no good idea how hard step 3 would be.

Line 16:

Line 18:

[[User:Homunq|Homunq]] 18:23, 31 March 2009 (UTC)

== Please be more specific ==

Talk about some of the specific UI choices, and any changes in save behavior, to make your app fit into sugar. Include some of this analysis in your schedule - when would you imagine you'd be working on what?

@@ Line 9: / Line 9: @@
 . reprogram it to be compatible with sugar - toolbar, rainbow security, autosave, dbus, etc. This is the real work of sugarizing. It is better if you can avoid forking the application - if it provides its interface via widgets which you can rearrange via another layer you put above. You would have to research whether this is possible.
-. document the above so it's easy to do with other kdeedu activities. (It would be cool if you could figure out some strategy to avoid repeatedly downloading 20MB of QT, yet still rely on just .xo packages without real package or dependency management.)
+. document the above so it's easy to do with other kdeedu activities.
+. (optional) It would be cool if you could figure out some strategy to avoid repeatedly downloading 20MB of QT, yet still rely on just .xo packages without real package or dependency management.
 Steps 1 and 2 should be relatively simple. I have no good idea how hard step 3 would be.
@@ Line 16: / Line 18: @@
 [[User:Homunq|Homunq]] 18:23, 31 March 2009 (UTC)
+== Please be more specific ==
+Talk about some of the specific UI choices, and any changes in save behavior, to make your app fit into sugar. Include some of this analysis in your schedule - when would you imagine you'd be working on what?