Fruto de la iniciativa del hackathon semi-permanente [1], se inicia aquí el tutorial postzïzëkiano: habitante-oscuro: una interfaz de usuario en JavaScript.
This tutorial is intended to cover the darkinhabitant skeleton JS UI on ten or fifteen sessions. So let's go through over. Good be nice to keep in touch!!
Referencias / links:
[1] https://n-1.cc/discussion/view/2096019/%C2%BFte-apuntas-a-una-hackathon-con-codigo
[English]------------------------
Greetings,
This is to write down Lorea's inhabitant's backup plugin specifications.
By initializing:
1) The plugin should manage private and public documents acording to user privileges. Maybe, user's profile can be used to get an index with current elements. Meaning: user authored documents and related by privileges other's documents.
2) The plugin shoud offer some U.I. to check or uncheck desidered backup elements.
3) All elements of the network should be available for backup.
4) Particular points to be studied: (order from less to maximum complexity):
-- a) Telegrams -- b) Links -- c) Photos -- d) Vídeos -- e) Tasks -- f) Pages -- g) Calendar -- h) Blogs -- i) Wikis -- j) Groups -- -- j.0) Elements above. -- -- j.1) Discussions, assamblies module. -- -- j.2) Mail lists
See suggested approaching methods below...
[Spanish]----------------------
Saludos,
Quisiera proponer un hackaton para el tema del plugin para copias de respaldo de los habitantes de Lorea.
Sé que no hay nadie ahí escuchando, pero supongo que los pasos correctos pasan por abrir este hilo.
Igualmente, también, supongo, que en cuanto plantee la curva de aprendizaje de Lorea me vendré abajo porque veré que la imbrincación con los fósiles y cadáveres que se han amontonado pesa sobremanera. Igualmente, ahora hay energías.
Una primera aproximación:
Tomo como punto de partida el planteamiento que Blinge anotó:
Supongo que un backup de usuarias tendría que distinguir entre los documentos publicos y los escritos en privado.. una forma de seleccionar la información no necesaria y descartarla del backup... ¿Se hace backup de los post de las listas de discusión o de las páginas publicadas en un grupo y no de de los telegramas? ¿Se realiza una busqueda en la base de datos de todo lo relacionado con tal o cual usuario, se copia y comprime todo en un archivo y se envía por email?
Al estar cada usuaria metida en varios grupos y cruzando conversaciones hacer un backup de todo me resulta primero complejo de imaginar de forma ordenada.
¿Y podrías entonces descargar todos los contenidos de otras usuarias si supieras sus contraseñas?
¿Y como sería visualizar el contenido descargado? ¿habría que volverlo a instalar en otro elgg para poder verlo ordenadamente o bastaría con la terminal para el que sepa usarla?
O le dedico tiempo a hacer estas reflexiones o a leer sobre como la gente debe limpiarse el culo. No se por donde seguir inspirándome.
¿Como puedo expresar gratitud por lo que has escrito siempre? Pero las que te hayan leido antes atentamente ya conocían la relación de acontecimientos que has percibido al haberlo explicado otras veces. ¿Para cuando un debate técnico y en inglés sobre problemas concretos? Podemos dinamizar eso mientras cada una se limpia el culo como pueda. O hacer nosotras lo mismo y liarnos a dedicarle a la misma cosa el tiempo que le prestamos atención al grupo lorea de n-1.
Entonces, por sistematizar:
1) El plugin debe distinguir entre documentos públicos y privados y gestionar la descarga acorde con el habitante que la solicita y sus privilegios.
2) Ofrecer una interfaz de usuario para añadir/quitar los documentos que serán incluidos.
3) Los documentos exportables habrán de cubrir todos los módulos de datos de Lorea, desde telegramas hasta las páginas de las wikis, pasando por enlaces, fotos, páginas, etc.
4) Casos concretos a estudiar (ordenados de menor a mayor complejidad):
-- a) Telegramas -- b) Enlaces -- c) Fotos -- d) Vídeos -- e) Tareas -- f) Páginas -- g) Calendario -- h) Blogs -- i) Wikis -- j) Grupos -- -- j.0) Elementos anteriores -- -- j.1) Discusiones, módulo asambleas. -- -- j.2) Lista de correos
LOREA's BACKUP HOLDER - elgg2.0 inhabitant backup plugin - TUTORIAL
NOTA: EL TUTORIAL SE HARÁ EN INGLÉS. SOLICITA LA VERSIÓN EN CASTELLANO O CATALÁN O GALLEGO O EUSKERA O ESPERANTO.
Índice:
Step 3: "Manifesto"
Step 3.1: "Internationalization"
Step 4: "index.html"
Step 5: "The IDE Start-up is over: cronotoping on the repo."
Step 1: "Having a code overview"
As Internet is heavily plenty full of information (it's like a fulfilled utopia to point out that something like this-huge-available-data-on-the-cloud would be desidered for those guys on the 70's phone phreaking times, like Captain Crunch and so on), as for it, this tutorial is intended to be like a knot matrix more than a big data concentration.
To tech the situation, one would mention the Gandhi's spinning wheel and, together, parallel lines, lacanian knot; just as a way of making theory in a way like «a kind of joinning together the polygon edges, rather than keeping on building isolated pyramids for world hegemons demonstrations». That's not precisely a naîf feature. Quite simple, what I have on mind while writting this is: a descentraliced and bitmasked teching paradigma, so the Darkinhabitant APP keeps secure and criptographically protected from the colonizator spying Prism that must be broken, and, that can bring his or her data to every Lorea-Elgg2.0 inhabitant by backing up in a safety way.
So we are here poszîzêkaning, there will be nothing to add, rather than bringing Borromean knot to your attention, while joining together the imaginary-the simbolic-the real, something that would bring to us model-view-controller paradigm as easy and rutinary on code desktop as a broom or a mop should be.
Directly straight from DW repo, take a look to this code jerarchy design:
src/js/ Code Root:
├── BACKEND: Background page specific code (runs on the background)
│ ├── channels Communication channels and transport
│ └── services Backend services
│
├── FRONTEND: User facing code (runs on the tabs, tied to html, uses angular)
│ ├── controllers Angular controllers
│ ├── directives Angular directives
│ ├── filters Angular filters
│ ├── popup Code for the popup area on the topbar
│ └── scripts Content scripts
│
├── MODEL: Storage related core, and generic model functionality.
└── util Generic utils
└── ng Angular utils
Check for further structure hacking on repo info file.
Ok, So it will be on this terms that we will build our skeleton. As the crows flies, in Newsted words: «Don't stop dreamming until the last breath. Until it becomes real.»
Step 2: "Having a tech overview"
In this step of the post-zîzêkian tutorial, we can attach here this famous: "From Platoo to NATO" without further explanations but having drawn a precisely timeline where we can stay ahead, as also, back to the JS skeleton UI, by listing this tech we will use:
RequireJS is a JavaScript file and module loader. It is optimized for in-browser use, but it can be used in other JavaScript environments, like Rhino and Node. Using a modular script loader like RequireJS will improve the speed and quality of your code.
In one word: automation. The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes.
Web sites are made of lots of things — frameworks, libraries, assets, utilities, and rainbows. Bower manages all these things for you.
Bower works by fetching and installing packages from all over, taking care of hunting, finding, downloading, and saving the stuff you’re looking for. Bower keeps track of these packages in a manifest file, bower.json. How you use packages is up to you. Bower provides hooks to facilitate using packages in your tools and workflows.
Bower is optimized for the front-end. Bower uses a flat dependency tree, requiring only one version for each package, reducing page load to a minimum.
Check how can you hack with bower on repo info file.
HTML is great for declaring static documents, but it falters when we try to use it for declaring dynamic views in web-applications. AngularJS lets you extend HTML vocabulary for your application. The resulting environment is extraordinarily expressive, readable, and quick to develop.
Node.js® is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
Check for how to hack NodeJs on Firefox on Mozilla's site.
This little beautifier will reformat and reindent bookmarklets, ugly JavaScript, unpack scripts packed by Dean Edward’s popular packer, as well as deobfuscate scripts processed by javascriptobfuscator.com.
CSS with superpowers. Sass is the most mature, stable, and powerful professional grade CSS extension language in the world. Sass is completely compatible with all versions of CSS. We take this compatibility seriously, so that you can seamlessly use any available CSS libraries. Sass boasts more features and abilities than any other CSS extension language out there.
Check how can you hack on CSS on repo info file.
Step 2.1: "Going deeper on tech overview"
Have you heard about Zîzêk telling the audience that old joke about a man that goes to a bar and ask for a coffee without cream, and then, the waiter replies: «Sorry, we've run out of cream, may I offer you a coffee without milk?». That is, a bit, the point of going deeper on tech overview, one could say that it is the same thing a coffee-without-cream than a coffee-without-milk, but, indeed, they are not. Aren't they? Some naïve coder as me would piss out with this incognita. Netherless, however, I reckon as Goethe wrote and Nietzsche putted on black above white on the prologue of The Use and Abuse of History book: «I hate everything that merely instructs me without increasing or directly quickening my activity»:
Ok, directly straight from DW repo, take a look to this dependencies list managed by Bower, used in 0.8.0 version:
"dependencies": {
"font-awesome": "~4.0.3",
"mnemonic.js": "~1.0.0",
"sjcl": "~1.0.0",
"lorea_gateway": "git://github.com/lorea/lorea-gateway",
"bitcoinjs-lib": "git://github.com/bitcoinjs/bitcoinjs-lib#master",
"angular": "~1.2.13",
"ngprogress": "~1.0.4",
"AngularJS-Toaster": "~0.4.3",
"angular-route": "~1.2.14",
"foundation": "~5.3",
"angular-foundation": "~0.3.1",
"requirejs": "~2.1.11",
"requirejs-domready": "~2.0.1",
"jsqrcode": "https://github.com/LazarSoft/jsqrcode.git#master",
"qrcodejs": "https://github.com/davidshimjs/qrcodejs.git",
"identicon": "https://github.com/stewartlord/identicon.js.git",
"angular-xeditable": "~0.1.8",
"async": "~0.7.0",
"angular-moment": "~0.7.0",
"big.js": "~2.5.0",
"angular-translate": "~2.2.0",
"angular-translate-loader-static-files": "~2.2.0"
}
Please, take note on this subversion of DW gateway on: "lorea_gateway": "git://github.com/lorea/lorea-gateway", while thinking on our Darkinhabitant being a toy that can go through a tor-socks or similar into darkness.
I cannot imagine any mason going to work without a good toolbox and, neither, I can't imagine a mason spreading the word that he is a mason. Take a look also in package.json to devDependencies list. We are not using this list above exactly, but it is good to know that we could take it, isn't it?
So, here, joking as Zîzêk on coffee-without-milk stupidity, we would like to know if a plugin that makes a backup without NSA-vigilance-detection is the same as a plugin that makes a backup without Chinese-Big-Firewall-detection, and, even, if they are the same as a backup without Big-Data-Merchants-interception.
Next, ¡manifesto!
¡Claveles!
Step 3: "Manifesto"
Just going into coding now. I've created three examples so we can talk about it. You know, semantic web needs ontologies over structures. So does anarchism, Hakim Bey would say, O.A.!
Forever and ever, the devil itself is calling for human agreement over artificial intelligence and bots!, this could be a very bad thing for humans to do: making the lacanian Big Other A/a a "tech-potens agent" able to learn by itself.
Here, one would be pretty sure that we are not boomeritis sick people, and that we are poszîzêkians, meaning that we are not going to develop the terms, but going through the burrow. Just simple as orgasmatron's beyond (Sepultura's song here) standing point, here and now, hic et nunc, we can propose that a machine will never have a coño-potens (pornterrorism speaking here), will it?
Ok, so here there are the three examples:
"name": "Lorea 2.0 Backup Holder",
"description": "Your Lorea's back ups.",
"homepage_url": "https://n-1.cc/discussion/view/2095202/lorea-reloaded-spring-summer-autumn-2015-plugin-inhabitant-backups",
"manifest_version": 0,
"icons": {"128": "src/images/icon_128.png"}
We love flowers, and, also, we love petals falling down from above the haulm.
It could be nice you start a seed. But, with this backs up APP, it could be nice you keep some petals of your Lorea.
«... while building fluid and responsive APPcache based client-rendered UI's through JavaScript API; and while managing packages by RequireJS; and "auth-as-a-service" federating with oAuth or OpenID; we will use AngularJS to connect front and backend, by controlling some modules that binds data models between user interfaces and content deploying servers.» Ok, in short: «We are going to play around APP's, or some browser extensions, or some downloadable media pill... to be mobile-device consumed. Doing it in a Elgg2.0-lorea based taste!»
Then, emerging from ex-nihilo, emerging from the void of our artwork and creation process, any robot, any people or any darkinhabitant can get a door to come into our reign. On Newsted heavy metal words: «... underdogs rise, from the flames»; while on Arch Enemy's words it could be: «Watch me closely, I will stand up - now». Just talking on philosophical zombies:
Step 3.1: "Internationalization"
One would be naîf and would be blindly a silly coder while ignoring real terms as torture, or simbolic terms as debt, or imaginary terms as surveillance (We♥Surveillance), and so on.
Netherless, as it is sang on Clapton's Tears from heaven, one always must: «... be strong and carry on, cause I know I don't belong. Here in heaven». I am standing on such a confirmation on being myself a fallen non serviam angel rather than a titan or a prince bringing the god's light to the world.
Poszîzekanially, we can talk on violence towards a violent absolute theology, while asking ourselves what should be a revolutionary today, rather than keeping calm and staying strong on a naîve non-violent satyagraha state of mind against WASP colonizator. And, of course, against other existing colonizators.
A Babel Tower Forum to join in council (Nemesis here) will always be a chance to people, as it is painted on Negri's ontology on empire and multitude; even if we fight each other like drunk people on divine violence of terror.
From whatever, another entry point should be a language selector so APP users can choose their mother-tongue. Take a look to this commit example. Here we bring, directly from DW Repo i18n:
[develop 5dd7260] Hello translators! This is main internalization structure.
We work together with Transifex files, where we hold its key-translation array, see initial commit on this tutorial repo. For official getting started overview check guide on tx web site. Check also hacking indications.
So, as a conclusion, if we do really naîves and really naïfs would need to point out the origins of a violent-imperialist-way-of-living just to stay peacefully or blockupiedly in front of it, now a days, all around the world, I'm pretty sure we should take a branch from this tree, aren't we?:
Step 4: "index.html"
Just another irrelevant and naîve day in my life took place on the 15th of November, 2007. I will explain later on. Could not seem relevant for this tutorial, but for sure it is.
It is very common in application development that main entry point to a rendered UI is named as index. It would be index.html in our HTML context.
So I've uploaded, directly from DW repo, a template where all the magic begins. Take a look:
[develop 9c1e1fd] Hello runtime environments! So this is main rendering entry point.
We should take on consideration some critical blocks on this file. But let me first tell you about this irrelevant and naîf day on 15th November. In short: I just get trapped under the ice of a cold and rationalist speech from spanish-liberal-philosopher, Antonio Escohotado. Do you know what I mean?
The story goes by me taking some acids to Energy Control building on Madrid, in order to make some analytics over them. I was not aware about the book he was introducing to an uncertain audience (who dammit would care about "reality and substance" amoung those guys there?!!), neither, I was not aware of the speech. The event was organized by a self-called Asociación Eleusis; last month, to go beyond, I found some Encuentros Eleusinos going on, again about a Soul map & reality map, where the liberal-philosopher still tries to disturb the people whith his stupidities about, let's put in words: «a case that a gun cannon is threating you to be erased every bit of your personal memory». So does index.html in our APP. It is a kind of unforgettable APP memory loader.
Anyway, we should clearly distinguish some elements on index.html. Mainly, the head block from the body block; and, within heading block, we should appreciate there some meta, title and stylesheet tags. As, on the body, we should distinguish, main body APP controller, plus the area catching backend GUI update events (including the main operations container), and, finally, the notification controllers by identifying the ng-controller AngularJS directives and script tags; by loading RequireJS (which will load our needed modules and backend/frontend main JS loaders). Next, I will mason on this file to darkinhabitanize the tutorial over it, but I thought it would be a good idea to let you some advantage to work on it. You can pull request to server if you want. The idea is nested to this "obelisk" calling through the gateway on line 31; we will have to talk about darkinhabitant obelisk and torsocks invisibility powers to get Elgg2.0-Lorea backup's data. I truly would wish here I wasn't alone, as I am, so we could discuss about it.
Ok, I can't finish this step about darkinhabitant index page without focusing on the same year as above, 2007. In this year, a spanish professional-traitor Verstrynge's book was published, called: «Frente al Imperio: Guerra Asimétrica y Guerra Total', Foca, Madrid». You should notice that this man started his political career on the extreme-right arch section while coming across extreme-left on his olderly years. Aren't this fucking incredible? I must confess I get a bit upset when reading this book. Netherless, just in case you are confused by that in spanish we call: "el enemigo difuso", in a post-zîzêkianinly looking for some text to show your people on this heavy matter of against who you should fight, maybe you can take a look to 2013 spanish-professional-traitor's book: «Contra quiénes luchar, Ediciones Península, Madrid».
Just imagining that we, the people, were fighting with stones while imperialism is killing us with machine-guns. As, for example, Palestinian matter, and so on. Follows Soyos picture, l'H comic illustrator:
It is, indeed, very hard to follow being a naîve. It is not easy to be naîf. One would need big doses of stupidity on his mind. Netherless, you, reader, should always, as it is explained on main info tutorial page, remember that I'm a trashed coder, periferia speaking worthless voice. So keep on your rails, while having some acid trip on a reality-substance bridge to break on through (the other side, The Doors's song here.) where the Empire can't stare at us.
Step 5: "The IDE Start-up is over: cronotoping on the repo."
There is some granaïno's raper-poet called Aitor now on Pangloss Band that wrote and sang on an oldest Hora Zulu granaïnan rap-metal band with Paco Luque on the guitar and so on, song called: «No habrá viento suficiente», what follows: «... ves que hoy lo hacemos increíble y es posible que te parezca asequible; solamente prueba: que te entrara fiebre. Y, yo, me alegro, con mi quiebro estoy fundiendo tus fusibles, ¡estilo libre! que hoy no solo bastará con ser amable y predecible, tu postura me parece respetable, ¡no me hables!: tu puntuarme mientras yo recojo el cobre. Que te sobre. Si se crea otra religion sobre los logros y milagros de este ogro lo llevaré menos negro pa poder salir de pobre; ya verás que un vaso de agua no puede hacer que zozobre una embarcación con esta dimensión de este calibre. Y, ahora, estamos haciendo que el mar se nos abra, ¡abracadabra!: hoy nos hemos metido por donde cubre. Es más de lo que había pedío: pues mi objetivo nunca ha sío ser rey del gremio, no. MÁS BIEN ES EL APREMIO POR ESCAPAR DEL ANDAMIO: si me llevo lo comÍo por lo servÍo según convenio: se que a nadie le he pedío yo nunca nada que no sea miÓ. (...)».
Ok. Index.html is like an Aleph, ain't it?
Like an Aleph with virtual capacity to store infinite cronotopos, can't you see it? Just a backup holder, Soledad based dark storing inside the privacy of some mixed-trusted coin-joined colective, where darkinhabitant, unsystemly, can hold its cryptodata and Elgg2.0 federation on OpenID or so on. Rhyzomatic sowing stars, caedes vision of a d3 big-bang-coded thread of words in such order at such precisely time. Here starts the biography and literature finds the silence while introducing the poiesis based post-internationalized situation of we, the people, in the world, for the past, for the future. Don't naîvely and naîfly take over the last two links over "for the past/future". This is poszîzêkian call for transatlantic peope party far from beyond coorp.'s ones that by demons are driven. What is happening on the real-simbolic-imaginary now on will not be covered but this tutorial.
As spanish cauditian dictatorship derrocator of the Democracy 1.0 on Republican 2.0 spanish res publicanitation always used to say to everyone: «Usted haga como yo y no se meta en política» ¡Je, je! spanish "no se meta en política" is said in english as: don't be naîve, man! what are you doing by your own on real politiks?
See further narrative of the goal on references below [1]... nethertheless, do you know what a chronotope could be in real, simbolic and imaginary terms? It may sound to you, in a taoistic straight ahead line to Godwin on British parlament, like from this line on, on this postzîzêkanian JavaScript UI for a darkinhabitant tutorial, I'm like to work the stones. Less architectural mapa than sweating the spring: she is welcomed. 2015 31th March.
I'm going right now to start chronotoping on the repository. Join the commit's time line or the milestoned issue lists... Chronotoping like this:
https://github.com/aleph1888/darkinhabitant/blob/master/exe/power_on
I will be back, if you are there, just to present the framing of cronotopos on the petal. Self-explained, for sure: darkinhabitant toy will say to the audience: «Hello world!». Keep on your rhythm while keeping safety your gpg keys. Pray to the hipocrenides just while chronotropicanding and chronotypeanding.
Aleph, arcadian mad, a l'H TICmason, lisergian-libido-sintetic transtimed therapist, ¡Vivan las lenguas romance!
Lots of love, drtek, is our band! Lots of love Soyos, no-band-no-cry!
REFERENCES:
[1] "Darkinhabitant, a pervert guide to TIC" - 2015 - eartesania - chapter two: "The goal"
p.d.: Don't forget to resujetokate your ego's as the petals fall.
