Sugar Network/Concept: Difference between revisions

Line 394:

The particular technical implementation is tailored by the following decisions:

# Using Web technologies to implement the ~~front end~~;

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

# Keep ~~front end~~ as a local Web application on a client side, it sounds converse regarding the #1 decision but this decision is based on ~~#4 and #5;~~

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

~~# Front end is implemented as a [[Wikipedia~~:~~Flask_(programming)|Falsk]] application using [[Platform_Team/WebSDK|WebSDK]] to accomplish the #4 and #5;~~

# Using Web technologies to implement the default frontend;

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

# 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:

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

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

~~# Implementation should be decentralized to support off-line workflow~~.

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

== Todo ==

@@ Line 394: / Line 394: @@
 The particular technical implementation is tailored by the following decisions:
-# Using Web technologies to implement the front end;
+# Client side functionality is split into DBus service and frontends;
-# Keep front end as a local Web application on a client side, it sounds converse regarding the #1 decision but this decision is based on #4 and #5;
+# Frontends are lightweight to let it possible to implement new frontend in fast manner, or, use DBus service partially in, e.g., Sugar activities;
-# Front end is implemented as a [[Wikipedia:Flask_(programming)|Falsk]] application using [[Platform_Team/WebSDK|WebSDK]] to accomplish the #4 and #5;
+# Using Web technologies to implement the default frontend;
-# Local Web application serve only one user and are much simpler than singular applications that are intended to serve thousands of users simultaneously;
+# 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:
-# Having simple and clean designed (see the previous point), it will be easy for doers to learn, change, reimplement the front end;
+#* Local Web application serve only one user and are much simpler than singular applications that are intended to serve thousands of users simultaneously;
-# Implementation should be decentralized to support off-line workflow.
+#* Having simple and clean designed (see the previous point), it will be easy for doers to learn, change, reimplement the front end.
 == Todo ==