Sugar Network/Concept: Difference between revisions

Line 396:

# Client side functionality is split into DBus service and frontends;

# Frontends are lightweight to let it possible to implement new frontend in fast manner, or, use DBus service partially in, e.g., Sugar activities;

# Using Web technologies to implement the default frontend;

# Using Web technologies to implement the default frontend:

# Keep default frontend as a local Web application on a client side, it sounds converse regarding the #3 ~~decision~~ but this decision is based on:

#* Make it possible to reuse Sugar Network in any Web browser in any Desktop Environment, i.e., not only from Sugar Shell;

#* Local Web ~~application~~ serve only one user and are much simpler than singular applications that are intended to serve thousands of users simultaneously;

#* Using existing Web methods might make frontend developing easier;

#* Involve Web developers to Sugar community;

# Keep default frontend as a local Web application on a client side, it sounds converse regarding the #3, but this decision is based on:

#* Local Web applications serve only one user and are much simpler than singular applications that are intended to serve thousands of users simultaneously;

#* Having simple and clean designed (see the previous point), it will be easy for doers to learn, change, reimplement the front end.

@@ Line 396: / Line 396: @@
 # Client side functionality is split into DBus service and frontends;
 # Frontends are lightweight to let it possible to implement new frontend in fast manner, or, use DBus service partially in, e.g., Sugar activities;
-# Using Web technologies to implement the default frontend;
+# Using Web technologies to implement the default frontend:
-# Keep default frontend as a local Web application on a client side, it sounds converse regarding the #3 decision but this decision is based on:
+#* Make it possible to reuse Sugar Network in any Web browser in any Desktop Environment, i.e., not only from Sugar Shell;
-#* Local Web application serve only one user and are much simpler than singular applications that are intended to serve thousands of users simultaneously;
+#* Using existing Web methods might make frontend developing easier;
+#* Involve Web developers to Sugar community;
+# Keep default frontend as a local Web application on a client side, it sounds converse regarding the #3, but this decision is based on:
+#* Local Web applications serve only one user and are much simpler than singular applications that are intended to serve thousands of users simultaneously;
 #* Having simple and clean designed (see the previous point), it will be easy for doers to learn, change, reimplement the front end.