March 2013 - aerogear-dev - Jboss List Archives

by Daniel Bevenius

Hi all, I'd like to discuss how to handle maintenance branches. Sorry if this has already been discussed, I think Kris posted something about this but I was not able to find it. For example, now that we are about to release 1.0.0 we will tag that release. After that should we create a 1.0.1 branch for patches/bugfixes and then continue with new features in master? Since we are in a waiting state at the moment, which could happen again, should we perhaps create a branch named 1.0.0, which we can use until the release and then tag it and remove that branch. After that any issues would be fixed in the 1.0.1 branch. Does this sound correct? Thanks, /Dan

11 years, 11 months

10
36
0 / 0

Errai javascript aerogear wrappers

by Erik Jan de Wit

Hi guys, I want to create wrappers around aerogear-js to be able to use the Aerogear from Erria. What this task comes down to is to create a java api that calls the aerogear-js api. But then I rembered seeing an example in a presentation that you kept the apis the same on all platforms. So my work is already done I just have to look at the api defined in android. The only problem is there are some differences, for instance DataManager on the js side it can be created by passing some config object, but on the android side there is a need for an IdGenerator and a StoreFactory. So what do you guys think should I stick closer to the js api and really try to create a minimal wrapper that is close to that, or should I stick with the android api and maybe use parts of Errai to implement a bridge? Cheers, Erik Jan

11 years, 11 months

3
4
0 / 0

AeroGear Native Push Server (DRAFT 0.0.2)

by Matthias Wessendorf

Hi, PLEASE review the documents...... Backgrounds on the PUSH server (NATIVE push - NO web push): https://gist.github.com/matzew/69d33a18d4fac9fdedd4 REST APIs: APP registration (requires account/token/rights): https://gist.github.com/matzew/2da6fc349a4aaf629bce Sending messages: https://gist.github.com/matzew/b21c1404cc093825f0fb Thanks! Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

11 years, 11 months

3
4
0 / 0

JS API Doc Updates

by Kris Borchers

Please take a look at http://staging.aerogear.org/docs/specs/aerogear-js/ and let me know if you would like anything else updated, keeping in mind that we are working on https://docs.google.com/document/d/17J-qFm_Fr0rsgusgjcwGhXFOnd2369KZgOYP9... Thanks!

11 years, 11 months

2
6
0 / 0

doc formats

by Matthias Wessendorf

for writing guides, we should use - according to a recent IRC chat - use the asciidoc format -M -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

11 years, 11 months

1
0
0 / 0

Aerogear-Controller-Demo Functional Test

by Apostolos Emmanouilidis

Hi, Just wanted to inform you that I've added a functional test for the Aerogear-Controller-Demo in the GitHub repo [1] I created a parent POM which contains 2 modules, the first module is the aerogear-controller-demo and the second one is the aerogear-controller-demo-ftest. The aerogear-controller-demo version is the latest one until the moment I'm writing this e-mail. The only change which has been done in the aerogear-controller-demo is that the staging repository was added inside the POM xml since I didn't want to modify my maven settings.xml. But we can change it.. The functional test project contains 2 profiles: 1. arq-jbossas-managed-7 2. arq-jbossas-remote By default the first profile is active. Inside the AerogearControllerDemoTestCase there is a TODO task which states: 'TODO: uncomment when https://issues.jboss.org/browse/AEROGEAR-1005 is fixed'. The relevant commented code tests the above JIRA issue. Any comment, enhancement, improvement is highly appreciated :) Thank you, Tolis Emmanouilidis [1] https://github.com/tolis-e/aerogear-controller-demo.git

11 years, 11 months

3
3
0 / 0

Customized JSDoc 3

by Kris Borchers

In the process of updating the JS API docs, I have finally pushed my modified version of JSDoc 3. You can find it here if you ever want to generate docs yourself. https://github.com/kborchers/jsdoc/tree/aerogear-mods

11 years, 11 months

2
1
0 / 0

AeroGear Controller & Security staged for 1.0.0

by Bruno Oliveira

Good morning peeps. For our happiness and amusement PicketLink beta was released today (http://lists.jboss.org/pipermail/security-dev/2013-March/000927.html). I've updated AeroGear Controller demo and Security with the latest release, here comes the staging repository: https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... Enjoy! -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile

11 years, 11 months

2
2
0 / 0

POC: Vert.x based server: (was: Re: AeroGear Native Push Server (DRAFT 0.0.2))

by Matthias Wessendorf

Howdy, here is a POC of the API impl., based on vert.x: https://github.com/matzew/ag-up-poc *** You need (as mentioned in the pom.xml) to build some JARs yourself... *** AUTH etc not in this POC -Matthias On Fri, Mar 22, 2013 at 12:45 PM, Matthias Wessendorf <matzew(a)apache.org>wrote: > Hi, > > PLEASE review the documents...... > > Backgrounds on the PUSH server (NATIVE push - NO web push): > https://gist.github.com/matzew/69d33a18d4fac9fdedd4 > > REST APIs: > > APP registration (requires account/token/rights): > https://gist.github.com/matzew/2da6fc349a4aaf629bce > > Sending messages: > https://gist.github.com/matzew/b21c1404cc093825f0fb > > > Thanks! > Matthias > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

11 years, 11 months

1
0
0 / 0

AeroGear 1.0 and Paging

by Summers Pittman

Y'all, I noticed that some of the method and class names in AeroGear Android around Paging are sub obtimal. I would like to, before 1.0 is cut, make the following changes Methods: PageConfig.setPageHeaderParser -> PageConfig.setParameterProvider Classed: PageResultExtractor -> ParameterProvider ParameterProvider -> gets merged into Parameter Provider All implementations are updated wdyt?

11 years, 11 months

4
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

aerogear-dev March 2013