Hello Alexandre,

Thanks for the heads up on this. We'll probably update it when 1.3 beta is available Stay tune to our blogs for more updates

I agree the developer docs are a little out of date, but I have found that anything that I can't figure out from the docs I have been able to ask, and the team here has not yet let me down.

@Mark: ))) i check daily, maybe twice lol
@JTH: i agree that their support is really A1 honestly. I have been digging a lot in the code but, for example, i was looking to their file explorer for group ( and file collection) and their was like 6 redirects or calling to admin method, then view then tmpl then helper etc etc the initial docs were providing a good step A. Looking forward for step B. ex: the javascript namespace and calling (especially for their placeholder) is quite advance (sign of great work) but doesn't make sense for anyone external to develop something advance (was looking to their calendar workarouond with the FullCalendar v1.0). Just feel bad for Mark to answer to 4 of my posts in the same day hehehe

I have been thinking about this all day, and I am wondering if a user supported wiki would be a better way to do the documentation. It would allow the documentation to stay more current.

Hello guys,

I think the documentation is only just a "layer" that gives you an idea of how things are built around EasySocial. We can't write extensive documentation up till the code level that lets you know which apps loads which files. That would be insane :P

I agree that would help so that Mark, Jason and the other devs could work around to have a user feeded developper zone but here is the challenge. I'm currently looking at the ajax call system since my next devs will involve dynamic loading.
However, their foundry framework is commented but no code to work around.
I try to follow the code through Eclipse to look around based on their initial call of
// Listen for ajax calls.
Foundry::ajax()->listen();

Etc. Better the docs for dev better the quality of 3rd party apps and the base subscriber but I don't know to what extend they would come in this.

Hello Alexandre,

That particular code only intercepts when the URL of the request is made with format=ajax . You should also use the javascript framework that's included in EasySocial.

For example, to make a request to a controller,

EasySocial.ajax('site/controllers/filename/methodname', { "a": "b", "c": "d"})

    .done(function(){

        // Do something when it's completed

    })

    .fail(function(){

        // If there's an error, do something here

    });

Hey Mark,

I agree that this shouldn't be too extensive that this would lost track of developing.
I can follow the path on how things are load. However, sample codes and some basic explanation are missing on couple subjects. As mentioned, the way you use javascript is quite advanced in your own apps. Same with how to make use of ajax etc. There are quite a lot of docs on php, mysql and javascript etc. Still several on Joomla but on your own specific framework and libs, really not much hehehehe.

The goal would be to maintain some kind of "know how" as to evolve with you on how we can make ES (and the other apps since it seems they are all based on your Foundry) even better suited for all the subscribers that may have some lower skills or none at all.

Maybe a "developer" section or subscription could do the trick. We could also work on beta testing and debugging too. I don't know but I think there is something we can do there that would also help you to spend less time on some issues since we might be able to fix our own issues among developers.

Obviously, these are my personal 2 cents on the matter

Alex

Thanks Mark for the answer ! It got in before i finished typing

You are most welcome

Hey Mark,

Can you tell me what are the plans to updates the dev documents after release of ES 1.3 or any general documentation in general ???
Would avoid quite few questions.

Thanks

EDIT: Was the update from Oct. 18 is mostly a visual update of the docs ?

Hello Alexandre,

We're actually in the midst of planning something else for the documentation area but this requires quite a bit of man power as we're actually struggling to keep up with the docs and the codes.