Hi Ivo, New insights may lead to new changes but for now I'd say it is a pretty good start. Some comments/questions I have at this point would be:
1) As Marcel suggested we should keep it pretty flat. This is not flat, but one can say it is pretty flat. I think we should think about level-1 order in terms in software lifecycle. Eg. We would release amdatu-opensocial as a whole and thus it has one version number. For something like the amdatu-examples this might not be so clear? 2) As a next step we should probably specify some release target. Eg. the current release is kind of like a amdatu-full distribution which give you all the goodies, but we will soon need the amdatu-manager and amdatu-launcher as well. 3) Speaking of which. Are amdatu-manager, amdatu-launcher and amdatu-provisioning subprojects or build targets? I think the latter which makes placing generic component such as OBR under them kind of strange? 4) The amdatu-authorization has a funny name as it is only applicable/relevant in an opensocial context? Or should login-gadget actually be part of the opensocial package and is this authorization package only aplpicable in a web context or should it actually be even lower and not depend on any framework package as we need authorization at the lowest at the core and thus does it need to be decoupled or is it something differetn altogether? 5) From a framework perspective I am wondering if some components are generic (enough) to be part of a framework package. Eg. is dashboard-bundle generic enough to be part of an opensocial release or will applications never have to customze it? Anyway, overall I think it is a good first order layout and suggest we move along with it. Regards, Bram On Fri, Oct 22, 2010 at 3:39 PM, Ivo Ladage-van Doorn <Ivo.Ladage-vanDoorn at gxsoftware.com> wrote: > Hi All, > > This thread has become a little quiet but since it's on the roadmap for the > upcoming version, very relevant. Any remarks on the Subversion layout > described on http://amdatu.org/confluence/display/Amdatu/Subversion+layout? > > Regards, Ivo > > > -----Original Message----- > From: amdatu-developers-bounces at amdatu.org > [mailto:amdatu-developers-bounces at amdatu.org] On Behalf Of Martijn van > Berkum > Sent: vrijdag 15 oktober 2010 15:52 > To: amdatu-developers at amdatu.org > Subject: Re: [Amdatu-developers] Repository layout and build > > Ok, my perspective from a higher level: > > One of the original visions of Amdatu is a common platform to bring together > various applications in one environment. Not a technological environment in > the sense of a virtual machine, but a recognizable environment for the > end-user, in the end the most important user of Amdatu, not the developer. > > We can expect all kinds of parties to start building applications on top of > Amdatu. We pay much attention to reuse and easy of development on top of > Amdatu. If we take the end-user in account, we should also pay much attention > to usability and recognizability, the user experience. > > This is something that gets a lot of attention on other platforms, wether it > is Windows, iPhone or facebook. A recognizable user interface really helps a > lot for the end-user, and will greatly help adoption of the platform. Also, > good UI widgets, patterns really helps developers build a solution fast. Of > course, a developer can circumvent the UI guidelines and tools we provide, > but it's really compelling and the end-user expects it, why not use them? > > What UI paradigm and UI strategy helps us achieve that goal? > > > _______________________________________________ > Amdatu-developers mailing list > Amdatu-developers at amdatu.org > http://lists.amdatu.org/mailman/listinfo/amdatu-developers >
