• View
• Edit
• History
• Print

back to SeedeaCore

Pages that isn't descriptive but should be interpreted

learn how to write pages from HandlePostRename() of the rename recipe of the official pmwiki cookbook

Cf Architecture, the Roadmap, ...

Tips&tricks should be in the GroupHeader/GroupFooter in order to be displayed directly above the pseudo-code.

Synthesize the new interface as the starting page

	format new layout (cf )
			| create helpers | sandboxes         | OIMP        | lab                        |
			| bubble blower  | tiny bubbles mess | organized   | bubble with preview inside |
		add the new "thelab" visuals
		add the search button
		add the create idea button
		add the trousse for logged in user (?!)
			add a fake picture of it for others
		add the split bucket (note : on multitouch interface it is a natural gesture)
		add the merge bucket (note : on multitouch interface it is a natural gesture)

sh-3.1$ ls | sed "s/\..*//" | sort | uniq : BMI Bugreport CoEvolution CoEvolutionBlog CogniteScafolding Contact Content CT EntryPoint FriendMe Main MetaModuleData MicroservicesIdentity Oimp Pimp PmWiki Profiles Quotes Research Seedea SeedeaCore SeedeaProtected Site SiteAdmin Test UserGeneratedContent Utopiahanalysis WikiBotData Xye

1. Use keywords used in the former entrypoint
2. Move a lot in the "behind the scene" section (research, company, todo, etc) with clean icons (ie: a microscope)
3. prepare for visitors from Mao's page
4. make a "hide-able" menu

Behaviors / use cases

Microservices activity

	add new (:Seedea.microservice-activity:) in Oimp.GroupHeader to allow display of potential activity
		read Oimp-Microservices.X (associated to each Oimp page created by microservices)
			if non existing or empty display sleeping (use visuals inspired by on VirtualAssistant)
				else doing task X with average duration of Z seconds, started at time T

"trousse"

Displayed on the border and to expand on click

	displaying phases zooms (with my filters)
	microservices listing
	input connectors
	notifications preferences (+ others means)	

Create idea

Situations :

	user is logged-in
		normal process (access to his input preferences)
	user is not logged-in
		can input idea content directly (without ANY delay/additional step)
			then can either add it as a gift (anonymously)
			or  then make it its own

New account

normal register procedure but also optionnaly accepting OpenID deternine closest microservices profile for user

	copy microservices configuration (refine periodically)

Delegate abstraction

everything complex and important but not functionnaly making a difference for the first users should be delegated

	* xmlrpc
	* wiki resolution
	all becomes "symbolic" (use fake calls)
		also add a marker to localize and complete them later (cf Roadmap)

What is pseudo-code? What is code? Is it just discussion?

Avoid recursively head spinning abstraction while designing, get simple things going THEN and ONLY THEN abstract/template/etc them!