Pluggdapps in a nutshell, that it is today and that it will be
tomorrow.
- Build applications on web-technologies. Build it on pluggdapps.
- Linus took unix to all programmers, and apt-get took Linux to all people.
In pluggdapps, deploy a website by installing a package.
- Not just websites, whether it is an application or web-application, libraries
or plugins or just couple of template files, deploy them by installing an egg
package.
- MVC (Model-View-Controller) is great. Plugin architecture is great. Do them
both in pluggdapps and get the best of both worlds.
- Should client and server run on different machines ? Not with pluggdapps.
- Pluggdapps run on python and javascript and web-browser and uses erlang for
database, hence, it can run on any device supporting them. Why not ?
- Library is a tool. Great libraries are stateless and re-entrant. For
pluggdapps, even applications are stateless and re-entrant.
- A framework is just a library, with callback APIs. A plugin is just a library,
with callback APIs. Hence, plugins are great way to design frameworks.
- To access a library, import them. To access plugins, query for them.
- Pluggdapps is not first to do it right, it merely tracks the footsteps of
its masters - Python, Zope, Pyramid, ...
- Interface will specify attributes, methods, method-signature and its function.
A callback API is nothing but an interface, hence, plugins are nothing but
a bunch of code implementing an interface. That pretty much sums up the
plugin architecture.
- Install applications and access them on the url.
- Configure and customize application along with modules, interfaces and plugins
used by the application. Configure them in .ini file, configure them via web.
- Applications are mounted on the url in three ways - domain, subdomain and
script. While the default is script, choose the one that fits, and
applications can be agnostic to how they are mounted.
- Url-rewriting. Requests are automatically routed to the mounted
application.
- Cross application access. For apps to access each other in the same run-time.
- Scaffolding. From first key-stroke to first application page in less than
30 seconds.
- Authenticate users and authorize them with permissions. Off-the-shelf plugins
available for challenging credentials and interfacing with backend store.
- Your browser has got the best documentation engine ever and wiki makes it
accessible. Use EazyText to create content for your apps.
- EazyText wiki markup. Generate HTML documents with out compromising on its
readability.
- With EazyText highlight your text as bold, italic, underline, subscript,
superscript and more.
- EazyText can hyperlink documents and images.
- Text in EazyText looks natural for reading. All the same it can generate
lists, tables, definitions, blockquotes and paragraphs.
- EazyText macros, create new functions and use them in your documents.
- EazyText extensions, extend the wiki engine.
- Become an expert in EazyText and create interactive documents.
- And EazyText is moving towards HTML5.
- With CSS and javascript, your browser can be way more than just a document
renderer. Use tayra templates to design your front end.
- HTML is verbose. Make it consise with Tayra.
- CSS Selector. That which pulls HTML, Javascript and CSS together.
- Tayra templating language. Bunch of syntax wrapped around a bunch of
specification. Adapt the language to your needs.
- Intendations are only natural to html. Why not enforce them ?
- Tayra templates. Define templates as function.
- Tayra templates. Organise template functions as modules. Import them in other
templates.
- Tayra templates. Templates are modules. Templates are objects. Use template
inheritance to design layouts.
- Tayra templates. Specify template interface. Implement template plugins. Use
them else-where.
- If you like decorators in python, you will like it in Tayra templates.
- NoSQL is cool. CouchDB is radical. Program your database with CouchPy.
- Don't you feel stored procedure in SQL as an after-thought ? After programming
(views,...) in CouchDB, there is a high chance you might.
- CouchDB on HTTP is nothing but CRUD on ReST.
- CouchPy for CouchDB. Model. Transact. Replicate. Program. Query. Eventually
consistent with MVCC.
-
Programmers believe that the value of their system lies in
the whole, in the building: posterity discovers it in the bricks with which
they built and which are often used again for better building.
-
Be it internet apps, be it desktop apps, build them on pluggdapps, whether your
applications live or whither, your plugins will go on to build better apps.
- Start by contributing plugins, grow as you design apps and become a network
geek.