Topics

Anahita Project

Anahita Project's Topics

Rastin Mehr

Rastin Mehr

September 26 2015

What comes after 4.1.5 release

The next major work is #MobileFirst user interfaces in Anahita which pretty much means rebuilding all the UIs and quite likely we are going to introduce new technologies such as #AngularJS and #MaterialDesign that are more suitable that generic #JQuery and #Bootstrap for an application environment. During this process we will be building native administration features in the front-end and completely remove the administration back-end. We may even completely remove Joomla depending on how smoothly things move forward. 

MobileFirst will be a long process and it will take some time to get ready. Before then we will have another small release which introduced #geolocation features in Anahita.

We have already implemented geolocation features in our client projects. It is about time to introduce it in the core framework for all of us who will be developing location services apps using Anahita. The development has been funded by our clients. 2 of them from the Anahita tribes. This is another good example of how financial contributions from our tribe members are helping us innovate and build great #OpenSource technologies for everyone to use.

Rastin Mehr
Rastin Mehr
September 26 2015 Permalink
Development of MobileFirst and geolocation will happen in parallel in separate branches
Scott Crawford
Scott Crawford
September 29 2015 Permalink
With regard to Material Design I'm finding some good resources, Google's entire Guide being one of them: https://www.google.com/design/spec/what-is-material/elevation-shadows.html

It's a very analytical approach to design, seemingly fitting for Google.

I am though hoping Anahita's entire front-end continues to offer the ability to be fully customized altogether. While parts of material design are very interesting it seems to me to be better oriented toward image-rich content rather than information-dense content, and thus might not be applicable to each community's use scenario. As an example of an information-dense implementation I'd offer Google's attempt to re-write Chrome's bookmark manager using material design, which I and apparently a significant portion of Chrome's user base found confusing and generally un-usable.
Rastin Mehr
Rastin Mehr
September 30 2015 Permalink
Material design is focused on user interfaces for apps rather than web design in conventional context. Here are some good examples https://www.materialup.com
Scott Crawford
Scott Crawford
October 02 2015 Permalink
Would you mind giving a hint as to how the geolocation features will work? Based on the nodes table I am assuming geo codes will be assignable to an actor or media node, but how would they be populated, once recorded can relative proximities be accessed, etc?
Rastin Mehr
Rastin Mehr
October 02 2015 Permalink
Similar to hashtags we will have location nodes and graphs. A location node represents a location on the map, a location graph associates a geolocatoable node (actor, medium, ...) with that location.

For actors there will be a place on the settings to associate with locations (existing or new ones)

Geolocation association can also be done by tagging. For example !PradoCafe I'm still unsure about what notation to use for parsing locations in a body of a node.

Powered by Anahita