\FOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.
What is opensTeam?
sTeam (structuring information in a team) is an open-source environment for the structuring and maintenance of virtual knowledge spaces. It provides a wealth of different mechanisms to support communicative and cooperative learning and work processes.
Virtual knowledge spaces combine synchronous and asynchronous forms of collaboration with the administration of hypermedia documents. Students and teachers meet in virtual knowledge areas, where they share and modify arrange, annotate and link documents through mutual views. This form of open, collaborative interaction with materials is supported by suitable methods of access permissions and user group management.
The main focus of sTeam is on techniques for distributed knowledge management and establishing of an arena for internet-based methods of cooperation. The concept of self-administration enables the creation of individual knowledge structures for single users as well as for user groups and the development of virtual communities. Mechanisms for social awareness, synchronous whiteboards and cooperative construction of knowledge also form the focus of our research.
sTeam has been developed at the University of Paderborn (Germany) supported by funding of the DFN (Deutsches Forschungs-Netz – german research network).
open-sTeam server
sTeam Server Architecture
Before explaining the server architecture it is important to distinguish between server and web interface. Moreover, there is not just one single webinterface, but possible different clients using the server. This includes our administration interface (sometimes people think of this as the steam system), but also different php interfaces (like BidOWL, openSMT and Sifa – see http://phpsteam.open-steam.org/ for our php interface) and different stylesheet sets (check http://steamware.open-steam.org).
The connection between the server and the steam administration interface is the http protocoll modul of the server and the libxslt module to transformation of steam objects to html code using XSL Stylesheets. The web interface itself is a collection of those Stylesheets and Scripts for execution (this is mostly done through HTML-Formulars, which are send to the server as POST-Requests – these Requests are send to Scripts). For PHP and Java (check http://javasteam.open-steam.org/ ) the COAL-Protocoll handles the connection. For web-applications the PHP/Java-Code is executed within a webserver (usually Apache).
The server itself is the collaboration backend of the application. It can be divided into several parts:
The server is object oriented, with the basic class Object. An Object has many Properties (called Attributes), a unique environment and a list of permissions (ACL).All objects are persistently stored by the server. A database (usually MySQL) is used as the main persistence layer.The server loads different modules, which add functionality to the server (Security, XSLT, LDAP, …). The server starts external services (on the same machine), which are connected by the COAL-Protocol. Those services act independently and if a service fails it is restarted by the server (this behaviour is similar to apache services). Modules and Services interact through Events, which are managed by a global event dispatcher. Groups and Users are special kinds of objects (derived from the Object class). When a request is performed within the server a User become active (user logs in, authorization is checked). Each user can be member of different groups. Each group holds several users and possible other groups (called sub-groups). Permission is usually bound to groups, which are stored inside an objects ACL.
Virtual Knowledge Spaces
The steam server is room-oriented. The unique environment of an object (see above) is usually a room (or a container). A room is a container of objects with connections to other rooms (called Exits or Connections). These connections express semantically related rooms and enable the movement of users from the current environment (room) to the target room. Rooms are also meeting places for users and can be distinguished from containers by this criteria.
Technically, rooms compose a context for users and objects. This is used by events and permissions:
If an action takes place in an object an appropriate event is raised in the objects environment. Therefore, the event can be monitored by subscribing to the environment instead of subscribing to each single object.
If an object is moved to a new environment the permissions of the new environment (room) apply also for the moved object. At the same time, the permissions from the last environment do no longer apply for this object. In both environments the local permissions (bound directly to the moving object) apply.
PHPsTeam
The API is used to interact with the server in php.
For web-applications the PHP/Java-Code is executed within a webserver (usually Apache).
https://github.com/open-steam/phpsteam
(Feel free to explore and contribute.)
JavaSteam
The API “JavaSteam” can be used to interact with a sTeam server using Java.
To communicate with the Server the API uses the COAL Protocol.
1.In order to make all your color values reusable and structural, you can consider to put these color values in res/values/colors.xml file.
2.What you implemented here is already really good. But I still have a little advice here. To avoid repeating your button’s code, you can also define a general Button style and put all general attributes setting in one style definition saved in res/values/styles.xml resource file. And when you want to create button, you can extract it out from this resource file and only write some specific values for each button (for example, android:id, or android:text). By doing so you can make your code cleaner. Try it!
package com.example.ajinkyawavare.myappportfolio; import android.os.Bundle; import android.support.v7.app.AppCompatActivity; import android.support.v7.widget.Toolbar; import android.view.Menu; import android.view.MenuItem; import android.view.View; import android.view.View.OnClickListener; import android.widget.Button; import android.widget.Toast; public class MainActivity extends AppCompatActivity { private Button button; private Button button2; private Button button3; private Button button4; private Button button5; private Button button6; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); Toolbar toolbar = (Toolbar) findViewById(R.id.toolbar); setSupportActionBar(toolbar); /*FloatingActionButton fab = (FloatingActionButton) findViewById(R.id.fab); fab.setOnClickListener(new View.OnClickListener() { @Override public void onClick(View view) { Snackbar.make(view, "Replace with your own action", Snackbar.LENGTH_SHORT) .setAction("Action", null).show(); } }); */ button = (Button)findViewById(R.id.button); button.setOnClickListener(new OnClickListener() { @Override public void onClick(View arg0) { Toast.makeText(getApplicationContext(), "This Button will launch my Spotify Streamer App!", Toast.LENGTH_SHORT).show(); } }); button2 = (Button)findViewById(R.id.button2); button2.setOnClickListener(new OnClickListener() { @Override public void onClick(View arg0) { Toast.makeText(getApplicationContext(), "This Button will launch my Scores App!", Toast.LENGTH_SHORT).show(); } }); button3 = (Button)findViewById(R.id.button3); button3.setOnClickListener(new OnClickListener() { @Override public void onClick(View arg0) { Toast.makeText(getApplicationContext(), "This Button will launch my Library App!", Toast.LENGTH_SHORT).show(); } }); button4 = (Button)findViewById(R.id.button4); button4.setOnClickListener(new OnClickListener() { @Override public void onClick(View arg0) { Toast.makeText(getApplicationContext(), "This Button will launch my Build It Bigger App!", Toast.LENGTH_SHORT).show(); } }); button5 = (Button)findViewById(R.id.button5); button5.setOnClickListener(new OnClickListener() { @Override public void onClick(View arg0) { Toast.makeText(getApplicationContext(), "This Button will launch my XYZ Reader App!", Toast.LENGTH_SHORT).show(); } }); button6 = (Button)findViewById(R.id.button6); button6.setOnClickListener(new OnClickListener() { @Override public void onClick(View arg0) { Toast.makeText(getApplicationContext(), "This Button will launch my Capstone:My Own App!", Toast.LENGTH_SHORT).show(); } }); } @Override public boolean onCreateOptionsMenu(Menu menu) { // Inflate the menu; this adds items to the action bar if it is present. getMenuInflater().inflate(R.menu.menu_main, menu); return true; } @Override public boolean onOptionsItemSelected(MenuItem item) { // Handle action bar item clicks here. The action bar will // automatically handle clicks on the Home/Up button, so long // as you specify a parent activity in AndroidManifest.xml. int id = item.getItemId(); //noinspection SimplifiableIfStatement if (id == R.id.action_settings) { return true; } return super.onOptionsItemSelected(item); } }Suggestion :
Supp:
http://jakewharton.github.io/butterknife/
Also, a video tutorial:
https://www.skillfeed.com/zh/courses/11756-android-butter-knife-the-complete-guide
To learn more, you can also register function for your buttons using XML definition like this sample code:
<Button android:onClick="onClick" />app/build.gradle