topic Re: Alfresco Community 3.0 Dev Edition in Alfresco Archive

Alfresco Community 3.0 Dev Edition

useeliger — Fri, 27 Jun 2008 09:24:07 GMT

Hi,I just downloaded and installed (from nightly builds) the 3.0 Dev edition - but I am disappointed. I thought version 3.0 will get the new user interface which was presented for example in Barcelona some month ago.They also spoke about some nice new features - like multi-select - I can't find them

Re: Alfresco Community 3.0 Dev Edition

francescof — Fri, 27 Jun 2008 12:25:14 GMT

Try connecting to http://localhost:8080/slingshot/.

Re: Alfresco Community 3.0 Dev Edition

useeliger — Tue, 01 Jul 2008 11:41:34 GMT

Thanks for the tip - but seems to be very beta.

Re: Alfresco Community 3.0 Dev Edition

mikeh — Tue, 01 Jul 2008 12:56:59 GMT

I'd say more "alpha" at this stage :wink:

Re: Alfresco Community 3.0 Dev Edition

rscheele — Wed, 02 Jul 2008 08:31:27 GMT

Yes, very ALPHA What i and others users have been asking in different topics, is the 31st of july still the 3.0 community deadline?

Re: Alfresco Community 3.0 Dev Edition

joechavez — Wed, 02 Jul 2008 09:57:59 GMT

Yes, very ALPHA What i and others users have been asking in different topics, is the 31st of july still the 3.0 community deadline?

And that's what we'd like to know as well. Looking at the current stage, this is still very far from being usable. I can't even upload a file. And that's the very basic operation of an ECM system, no? BTW, the upload is hard-coded to "localhost" only.

And we have concerns about Alfresco at this. Since the old web client is pretty much shelved (which is unfortunate, really), and looking at the current Slingshot thingy, which is not even as intuitive as the old web client, we are asking ourselves, what are we going to do with our deployment?

The web client was one of the nicest designs we have used, we do not really understand the move to abandon it.

Re: Alfresco Community 3.0 Dev Edition

mabayona — Wed, 02 Jul 2008 10:21:37 GMT

I do not think that the web client is going to be abandoned and not supported. I think is there and will be kept in the future (with no further development). We use 2.9C_dev and plan to use it beyond 3.0. The idea is to use 3.0 features to extend and complement the web client functionality already available (e.g. as webscript/dashlets) and to migrate slowly to 3.0/webscript.

On the other side, Optaros has announced that will be delivering a web-client "clon" in web scripts that could be used as "migration path".

Re: Alfresco Community 3.0 Dev Edition

rscheele — Wed, 02 Jul 2008 10:30:33 GMT

No, the 2.x web client would continue to exist and to be supported - but plans we're (are?) to present an additional brand new user interface targeted at the knowledge worker - providing a Sharepoint alternative, both in terms of looks and end-user functionality end july. It seems to me that the underlying architecture is more or less finished, but the 3.0 web client isn't far from finished.

Re: Alfresco Community 3.0 Dev Edition

hvyas — Wed, 02 Jul 2008 18:57:21 GMT

What about 2.9C version? When it will be available? Any input would be appreciated.

Re: Alfresco Community 3.0 Dev Edition

klaas — Wed, 02 Jul 2008 19:00:39 GMT

It's a pity when there will be two separated interfaces. Even more if you will use to different stores. This will mean we can' t use the slingshot version. It would be nicer if there is a special space that redirects the user to the slingshot interface and if the documents and other content (like wiki,..) from the slingshot interface will be unavailable in the webclient.

Klaas

Re: Alfresco Community 3.0 Dev Edition

rscheele — Wed, 02 Jul 2008 19:32:27 GMT

As far as i know, the new web client is just one that's built on top of alfresco WCM (actually, http://wiki.alfresco.com/wiki/Web_Framework_3.0). It uses the AVM store and it can communicate with the current alfresco repository using web services (http://wiki.alfresco.com/wiki/Web_Scripts), so it just loosely coupled - not like the current JSP based web client - which by itself is of course a great architectural advantage.

The web framework uses components like a document library through which you can upload, read, update, etc your documents from the java content repository. The whole thing is centered around 'sites' instead of 'spaces', so i don't know if things can be mapped one-on-one.

Again, any input from Alfresco Engineers to these questions would be greatly appreciated - seems like community members have some doubt regarding 3.0 and the current roadmap (like a 2.9c release in june).

Re: Alfresco Community 3.0 Dev Edition

stevereiner — Wed, 02 Jul 2008 20:01:24 GMT

You might want to check out FlexSpaces. This is a rich client for Alfresco developed with Flex (browser and AIR clients) and web scripts. The AIR version has support for drag/drop of desktop files, offlining. Additional coverage of web client features will be added to flexspaces. Its default configuration applications are targeted at power users and administration (of 2.x/3.0 main/avm stores, and will add support for 3.0 site collab stores)

Its components can be used to create simpler UIs (in Flex applications or integrated in html/ajax web applications). Ajax/html webscript components can even be integrated inside the flex applications.

The latest version now has source.
http://forge.alfresco.com/projects/flexspaces/

P.S. slingshot is currently using separate workspace stores not avm stores. Saw a bunch of cool stuff checked in recently (blogs, wikis, configable dashboards) !! (not in the last nightly build from 6/17/08)

Steve Reiner
http://www.integratedsemantics.org
http://www.integratedsemantics.com

Re: Alfresco Community 3.0 Dev Edition

mikeh — Wed, 02 Jul 2008 20:04:23 GMT

It's a pity when there will be two separated interfaces. Even more if you will use to different stores.

Actually, we're currently having a re-think on this exact area. Although there are many advantages to using a new store for v3.0 we recognise that people will still use both clients. With these kind of decisions, there's always a compromise between pushing forward technically and backwards compatibility - it's impossible to please everyone.

This will mean we can' t use the slingshot version.

Is there a specific reason why this would be the case?

Additionally, it's important to realise that we're not covering 100% of the existing web client functionality in v3.0. Obviously this will come with time, but realistically this is just not possible. We also recognise that people are comfortable and experienced in customising the existing web client - and have existing custom installations rolled-out and live. It would be impossible to support all customisations with the Slingshot client, so the v2.x UI will exist for some time yet.

Finally, I should add that it will be much easier to add new functionality to the v3.0 client. Web Scripts have a much shallower learning curve than JSF, and the frameworks (server and client) should be easy to learn for competent Freemarker and JavaScript developers.

Thanks,
Mike

Re: Alfresco Community 3.0 Dev Edition

chen_shaopeng — Thu, 03 Jul 2008 02:02:08 GMT

Although the 2.x web client might be there for some time (but how long before sunsetting?), but the fact that development is frozen is enough of concerns for existing users. That means existing users get themselves into a dead end.

And the fact that the stores are incompatible just make the whole thing even harder to swallow. And "having a rethink in this exact area" means, is the rethink over or just starting? And what is the decision on that?

And as you said, people have probably done a lot of customization and extensions already. Does it mean that, we are either stuck with a shelved product, or take the pain to re-develop again all those customizations in a new environment, with all the cost of development, training, testing, learning curve… ?

Too many questions unanswered after half a day of trying out the new 3.0.

Re: Alfresco Community 3.0 Dev Edition

mikeh — Thu, 03 Jul 2008 07:10:21 GMT

Although the 2.x web client might be there for some time (but how long before sunsetting?), but the fact that development is frozen is enough of concerns for existing users. That means existing users get themselves into a dead end.

Nobody said development was frozen. We have a naming problem at the moment - there will be two web clients: JSF and Slingshot. Obviously they can't both be the "Web Client" but they both exist and are being worked on. More effort is being poured into Slingshot, but there are also people working on the JSF client.

And the fact that the stores are incompatible just make the whole thing even harder to swallow. And "having a rethink in this exact area" means, is the rethink over or just starting? And what is the decision on that?

The stores aren't incompatible at all. You can already create FTP and CIFS interfaces to SiteStore purely through configuration. APIs can access both stores. The only issue is that the current JSF client can't access it, because it was never designed with that in mind. Doesn't mean it's incompatible though.

And as you said, people have probably done a lot of customization and extensions already. Does it mean that, we are either stuck with a shelved product, or take the pain to re-develop again all those customizations in a new environment, with all the cost of development, training, testing, learning curve… ?

No, of course not.

Re: Alfresco Community 3.0 Dev Edition

rscheele — Thu, 03 Jul 2008 07:35:34 GMT

Oke, anyhow, communication is just bad: we would be having early previews of the upcoming 3.0 release (barcelona community meeting) - latest nightly build dates back to 17 june. A 2.9c community versions was communicated - nothing is delivered. As a result of that, i have my doubts regarding 3.0. I think expectations aren't clearly communicated - otherwise we wouldn't be having this conversation.

Re: Alfresco Community 3.0 Dev Edition

mikeh — Thu, 03 Jul 2008 08:30:38 GMT

… 3.0 … latest nightly build dates back to 17 june.

Are you looking in the correct place? http://dev.alfresco.com/downloads/nightly/dist/

A 2.9c community versions was communicated - nothing is delivered.

Yes, that's true - I can only apologise for the delay with 2.9.

Mike

Re: Alfresco Community 3.0 Dev Edition

joechavez — Thu, 03 Jul 2008 14:28:08 GMT

Nobody said development was frozen. We have a naming problem at the moment - there will be two web clients: JSF and Slingshot. Obviously they can't both be the "Web Client" but they both exist and are being worked on. More effort is being poured into Slingshot, but there are also people working on the JSF client.

Well, I have a hard time with that one too. If it's not frozen, why is it called "warehoused"? Doesn't that mean no new development on that anymore, and all efforts will only be on slingshot?

I think I can speak for a lot of people here, because all signs (from the roadmap, from the posts here, from the wiki, from some information on the Alfresco web site…) indicate that the 2.x web client is being abandoned. And I'm pretty sure there will be no new development on the web client. Now, can someone confirm that I'm wrong? I update from HEAD frequently, and I don't see much going in web client.

The stores aren't incompatible at all. …

Come on, by "incompatible", everyone here (especially for me) means that if we have a 2.x rolled out, there's no way we can suddenly switch to slingshot and still access our spaces, with all the rules, workflows, webscripts, etc, just like before, isn't this right? Not with a whole lot of re-coding, I guess.

We have a busy 2.1 server running now, with a lot of in house extensions and modules. We were eager to see 3.0, and when we finally saw what's coming, I have to say, concern is an understatement.

Re: Alfresco Community 3.0 Dev Edition

joechavez — Thu, 03 Jul 2008 14:40:25 GMT

… 3.0 … latest nightly build dates back to 17 june.
Are you looking in the correct place? http://dev.alfresco.com/downloads/nightly/dist/

Haha, rscheele dude, why did you have to post just before another build coming out

Re: Alfresco Community 3.0 Dev Edition

mrintegrity — Fri, 04 Jul 2008 22:41:42 GMT

I'd say more "alpha" at this stage :wink:

This is a bit of a concern for me. We are currently planning for a test of Alfresco, coincidentally, we are planning for the test phase A to start on 31st July.

I already have a test system running with 2.1 but I am finding some of it's limitations a bit too discouraging, particularly in light of a new version coming out on an uncertain but close date that is (by the sounds of things) not easily transitioned to from 2.1, the features planned for 3.0 are much more in line with what we are looking for.

The questions I am asking myself, and that are causing me to feel a fair bit of strain with my colleagues are:

1. Is it worth deploying a 2.1 or 2.9 Alfresco installation, getting everyone used to the system, creating documentation for training, scheduling time from other departments, ordering hardware, creating spaces / rules / permissions /customisations, all with software that is a dead end.

2. Can the 3.0 dev build provide enough stability for a limited test as it currently stands?

3. Will the 3.0 release be ready when we need it to be (Phase B of the test starts 11/8 when we bring in other departments and try real world scenarios)

Basically, if the current 3.0 build is usable without having to have someone babysit the server then I'm all for starting with that, providing there is at least a good chance it will be ready roughly when it's supposed to be. I'm not trying to pressure anyone, just want to know is all so that I can plan properly

Thank you very much for your time,

Alan