Jonas jonaskahn

INSTALL

Get the latest code of wingpanel: https://github.com/elementary/wingpanel/releases
Extract and open terminal in source folder wingpanel-[version]
Open file Panel.vala, replace line center_menubar.add (indicator_entry); by right_menubar.insert_sorted (indicator_entry);
Open file IndicatorSorter.vala, add line indicator_order[Indicator.DATETIME] = 10; in contruct. Change indicator_order[Indicator.SESSION] = 10; to indicator_order[Indicator.SESSION] = 11;
Run command
```
    meson build --prefix=/usr
```

“Non Postback” requests: The “Non Postback” request refers to a new request to a page. If this case, the Restore View phase creates an empty UI components tree and stores it in the current FacesContext instance. For the “Non Postback” requests, the JSF life cycle directly proceeds to the last phase, which is the “Render Response” phase. In the “Render Response” phase, the empty UI components tree is populated with the JSF components in the page. Also, the UI components tree state is saved in the JSF view state for the next requests.
“Postback” requests: The “Postback” request occurs when the content of the form is submitted to the same page using the HTTP POST method. In this case, the Restore View phase restores the UI components tree from the JSF view state that was generated from the previous page request.

Note The “Apply Request Values” is applied to all the components which have a value attribute. In JSF, the compo

Actually, since JSF 2.0, the faces-config file becomes optional because most of the JSF configuration can be defined using the Java annotations.
JSF Converters don't proceed in the second phase - Apply Request Model except when you set immediate equals true

What is ManagedBean?

Look into current implementation

LifecycleImpl.java

    // Execute the phases up to but not including Render Response
    public void execute(FacesContext context) throws FacesException {

	#! /bin/sh
	sudo curl -o /usr/local/bin/runb https://gist.githubusercontent.com/therealtuyen/320fdafabe1330dac586395e33cf7cd2/raw/863a22c48133d6947168c48bdeec1b50279682e4/run-in-batch.sh
	sudo chmod a+x /usr/local/bin/runb
	source ~/.bashrc >/dev/null 2>&1
	source ~/.zshrc >/dev/null 2>&1

	<!DOCTYPE html>
	<html lang="en">

	<head>
	<meta charset="UTF-8">
	<title>Test Meet</title>
	<!-- change domain to match your Jitsi server -->
	<script src='https://meet.jit.si/external_api.js'></script>
	<style>
	html {

	docker container stop $(docker container ls -aq)
	docker container rm $(docker container ls -aq)
	docker system prune -a