Well, lets not forget about YAAC (yet another Alfresco client 
), Slingshot that Alfresco is developing.
Well, actually, the more, the merrier.
I don't like Flex, so thats one I'll pass. Daniel and Denis are really kick ass programmers, and from what Daniel has told me about their client, they are closest to my ideal, from UI look to architecture. Just don't know if they'll ever go open source, will check that.
Optaros was proof of concept, don't think it went much further than that.
Will try Docasu, looks good.
Can't figure direction Slingshot is taking Alfresco, except it is not direction I need for now
All in all, after not having usable RIA interface for years, I actually think that several approaches are good in this phase. little competition has never done any harm.
), Slingshot that Alfresco is developing.Well, actually, the more, the merrier.
I don't like Flex, so thats one I'll pass. Daniel and Denis are really kick ass programmers, and from what Daniel has told me about their client, they are closest to my ideal, from UI look to architecture. Just don't know if they'll ever go open source, will check that.
Optaros was proof of concept, don't think it went much further than that.
Will try Docasu, looks good.
Can't figure direction Slingshot is taking Alfresco, except it is not direction I need for now
All in all, after not having usable RIA interface for years, I actually think that several approaches are good in this phase. little competition has never done any harm.
hi,
imo such "large" number of different clients in development is only a proof that Alfresco made a great development platform. It fits equally good for lightweight clients like Opsoro or Docasu and for server side framework like Alfext. However goals of these development efforts are not the same, while Opsoro and Docasu are focusing on improving user experience during repository browsing, the goal of Alfext, I have to say rather ambitious one, is to enable incremental development process while developing complex enterprise applications using Alfresco platform and ExtJs as a view.
Anyone developing anything more than trivial applications which involve fair amount of JavaScript client side development knows that it can be a quite challenging task to manage, especially if you are working in a team. It takes a lot of development discipline and a lot of conventions not to get lost. What we are trying to achieve with AlfExt is to enable development using reusable components which are configured using Alfresco configuration. This is the same concept found in Alfresco JSF application, the difference is that it is not html which gets produced on the server side, but rather JavaScript.
AlfExt itself will be open sourced eventually, but we can not define the date, yet.. There are so many things to do and so little time
Best regards,
Denis
imo such "large" number of different clients in development is only a proof that Alfresco made a great development platform. It fits equally good for lightweight clients like Opsoro or Docasu and for server side framework like Alfext. However goals of these development efforts are not the same, while Opsoro and Docasu are focusing on improving user experience during repository browsing, the goal of Alfext, I have to say rather ambitious one, is to enable incremental development process while developing complex enterprise applications using Alfresco platform and ExtJs as a view.
Anyone developing anything more than trivial applications which involve fair amount of JavaScript client side development knows that it can be a quite challenging task to manage, especially if you are working in a team. It takes a lot of development discipline and a lot of conventions not to get lost. What we are trying to achieve with AlfExt is to enable development using reusable components which are configured using Alfresco configuration. This is the same concept found in Alfresco JSF application, the difference is that it is not html which gets produced on the server side, but rather JavaScript.
AlfExt itself will be open sourced eventually, but we can not define the date, yet.. There are so many things to do and so little time
Best regards,
Denis
fselendic,
Even if you don't want to use Flex for development, FlexSpaces+AIR makes a good CIFS substitute with its support for drag / drop into the repository from the desktop. (Cifs doesn't work for me and others after install of vista sp1. So, for example I use FlexSpaces+AIR to drag multiple webscript files into the Data Dictionary / Web Script Extensions area since it takes less steps than using the web client)
(Personally I find flex to be great, productive platform: mxml to do declarative layout, and actionscript that makes javascript more object oriented, more java like.)
Steve
Fair enough, forgot about that
Hi Denis,
It is hard not to notice (for us that had a chance to see some of your work) that first visible effect of your framework is improving user experience during repository browsing
And, sooner or later, anyone doing anything even slightly serious with Alfresco, will be in need of some kind of framework like AlfExt. So I find your approach a better way of addressing this particular problem.
Also, having in mind ambitious nature of your project, and benefits it could bring, jpfi is right; joining at least some forces would be great. Of course, after you guys find sustainable business model for financing such amount of work
Speaking of AlfExt, any plans for i18n and L10n? Or is that already addressed?
It is hard not to notice (for us that had a chance to see some of your work) that first visible effect of your framework is improving user experience during repository browsing
And, sooner or later, anyone doing anything even slightly serious with Alfresco, will be in need of some kind of framework like AlfExt. So I find your approach a better way of addressing this particular problem.
Also, having in mind ambitious nature of your project, and benefits it could bring, jpfi is right; joining at least some forces would be great. Of course, after you guys find sustainable business model for financing such amount of work
Speaking of AlfExt, any plans for i18n and L10n? Or is that already addressed?
