Application talk:X - Revision history

RodWhitby: /* Encoding of Input */

2011-07-21T02:16:24Z

Encoding of Input

DtzWill: shift discussion to input goodness

2011-07-20T18:53:52Z

shift discussion to input goodness

DtzWill: /* Window Managers */

2010-03-17T20:05:41Z

Window Managers

DtzWill: /* Packaging Proposal */ libraries

2010-03-17T20:01:12Z

Packaging Proposal: libraries

DtzWill at 19:59, 17 March 2010

2010-03-17T19:59:57Z

DtzWill at 19:58, 17 March 2010

2010-03-17T19:58:21Z

DtzWill: packaging proposal

2010-03-17T19:56:57Z

packaging proposal

Zonyl: New page: Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly?

2010-03-15T15:07:38Z

New page: Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly?

New page

Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly?

← Older revision		Revision as of 02:16, 21 July 2011
Line 17:		Line 17:
	*...TODO		*...TODO

		+
		+	==Options for Modifier Input==
		+
		+	What options do we have for modifiers on the TouchPad virtual keyboard?
		+
		+	Do we need a "modifier / arrow keys" slice between the keyboard and the X display?

	==Encoding of Input==		==Encoding of Input==

@@ Line 1: / Line 1: @@
-Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc?  Or were you planning on getting X running via sdl directly? ~zonyl
+==Required/desired Input capabilities==
-Zonyl: I had different plans than a sdlvnc+debian chroot+Xvfb.  More integration with webOS (see below), integration into Preware (not reliant on apt-get in the chroot), native apps (potentially faster), and perhaps a more accelerated server (lots of opportunities to make this better, including potentially glx but we'll see :D).  Thanks for offering to write it up though, that is useful and should probably go up somewhere.
+===Mouse===
-I don't know the best place to put this, but I want this to be publicish so throwing it here.
+==Encoding of Input==
-===xlib===
+What should this look like?
-Contains all the X libraries that are used.  Iff the library is listed http://www.x.org/releases/X11R7.5/src/lib/ it's included.
+==Device-specific discussion==

@@ Line 44: / Line 44: @@
 Each window manager would be an application.  One thought is it might not make sense to have a wm-bin package--does that really make sense?
 But maybe it should for consistency's sake.
 ==Meta packages==
 We could introduce meta-packages for commonly installed applications/etc to save people from having to install a large number of applications manually, and just say "give me a good experience and a button to launch it!".

@@ Line 36: / Line 36: @@
 Launcher script for the app "app". Spawns additional X server for each application.
 Depends on xorg-server, and app-bin.
 ==Window Managers==

← Older revision		Revision as of 19:59, 17 March 2010
Line 1:		Line 1:
	Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly? ~zonyl		Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly? ~zonyl

−	Zonyl: I had different plans than a sdlvnc+debian chroot+Xvfb. More integration with ~~webOs~~, integration into Preware, native apps, and perhaps a more accelerated server~~. Well and no requirement~~ to ~~install a big debian chroot even if that~~'~~s easy~~ :). Thanks for ~~the offer~~ though.	+	Zonyl: I had different plans than a sdlvnc+debian chroot+Xvfb. More integration with webOS (see below), integration into Preware (not reliant on apt-get in the chroot), native apps (potentially faster), and perhaps a more accelerated server (lots of opportunities to make this better, including potentially glx but we'll see :D). Thanks for offering to write it up though, that is useful and should probably go up somewhere.

← Older revision		Revision as of 19:58, 17 March 2010
Line 1:		Line 1:
	Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly? ~zonyl		Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly? ~zonyl
−	Zonyl: I had different plans than a sdlvnc+debian chroot+Xvfb. More integration with webOs, integration into Preware, native apps, and perhaps a more accelerated server. Well and no requirement to install a big debian chroot even if that's easy :).	+
		+	Zonyl: I had different plans than a sdlvnc+debian chroot+Xvfb. More integration with webOs, integration into Preware, native apps, and perhaps a more accelerated server. Well and no requirement to install a big debian chroot even if that's easy :). Thanks for the offer though.

← Older revision		Revision as of 19:56, 17 March 2010
Line 1:		Line 1:
−	Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly?	+	Would you like me to list a step-by-step guide here to using X on the pre via debian chroot and sdlvnc? Or were you planning on getting X running via sdl directly? ~zonyl
		+	Zonyl: I had different plans than a sdlvnc+debian chroot+Xvfb. More integration with webOs, integration into Preware, native apps, and perhaps a more accelerated server. Well and no requirement to install a big debian chroot even if that's easy :).
		+
		+
		+	=Packaging Proposal=
		+
		+	I don't know the best place to put this, but I want this to be publicish so throwing it here.
		+
		+	===xlib===
		+
		+	Contains all the X libraries that are used. Iff the library is listed http://www.x.org/releases/X11R7.5/src/lib/ it's included.
		+
		+	==Core==
		+
		+	===xorg-server===
		+	Contains the X server, no front-end.
		+	Depends on xlib
		+
		+	===x11===
		+	Just a launcher script for xorg-server.
		+	Depends on xorg-server
		+
		+	==Applications==
		+	Each application could be separated into two packages.
		+	This allows the user to have the icons they want in the launcher,
		+	but also allows them to install many applications without cluttering the pre's launcher.
		+	A good example here is 'xterm'.
		+
		+	===app-bin===
		+	Contains the binary for the application "app", and app-specific libraries, resources, etc.
		+	No icon/front-end.
		+	Depends on xlib
		+
		+	===app-launcher===
		+	Launcher script for the app "app". Spawns additional X server for each application.
		+	Depends on xorg-server, and app-bin.
		+
		+	==Window Managers==
		+	Each window manager would be an application. One thought is it might not make sense to have a wm-bin package--does that really make sense?
		+	But maybe it should for consistency's sake.
		+
		+	==Meta packages==
		+	We could introduce meta-packages for commonly installed applications/etc to save people from having to install a large number of applications manually, and just say "give me a good experience and a button to launch it!".