Discussion about : Joomla! 1.1 — Developer Power, User Excitement

[Prasad007]

is this beta ??

Errr, no, I *just* said:

The next release of 1.1 will be alpha2.  Neither alpha1, alpha2, or even beta are recommended on live sites.

Emphasis added

whats alpha then?

[vavroom]

whats alpha then?

Alpha release is really like a proof of concept release.  We have ideas and think things should work a certain way, we release an alpha to have it put through its paces.  Features can be added and/or removed, the code played with extensively.

Beta releases see a feature freeze.  Basically, we're saying: "ok, this is it, we think the code is good", and we do some extensive testing to make sure the product is bug-free (it never really is, but as close as).

Stable release is when we deem the release ready for production environment.

I hope this helps.

[Prasad007]

whats alpha then?

Alpha release is really like a proof of concept release.  We have ideas and think things should work a certain way, we release an alpha to have it put through its paces.  Features can be added and/or removed, the code played with extensively.

Beta releases see a feature freeze.  Basically, we're saying: "ok, this is it, we think the code is good", and we do some extensive testing to make sure the product is bug-free (it never really is, but as close as).

Stable release is when we deem the release ready for production environment.

I hope this helps.

oh okay
Thank you!
p.s. when wud this go stable then?

[vavroom]

p.s. when wud this go stable then?

Whenever it's ready

Hate to give a date, because then if for whatever reason we aren't able to deliver on time, we get jumped on for having promised it by a certain date

[Prasad007]

p.s. when wud this go stable then?

Whenever it's ready

Hate to give a date, because then if for whatever reason we aren't able to deliver on time, we get jumped on for having promised it by a certain date

okay!
Thank you for all your help!

[newart]

Not trying to be negative or anything. But lets recap...

Joomla Versions / Updates Since The Split -    6
Mambo Versions / Updates Since The Split -   1

Just goes to show which one is the most progressive.

I like your ideas   

[benedikt]

p.s. when wud this go stable then?

Whenever it's ready

Hate to give a date, because then if for whatever reason we aren't able to deliver on time, we get jumped on for having promised it by a certain date

Hey Prasad, welcome!
I get the impression that you might not know that there is already a stable version of Joomla that you can use.
This tread is a discussion about the new version. You can find the stable version (=joomla 1.0.5) here.

Sorry if I got this wrong 

P.S.: You also might want to change your signature. Here are the rules for this forum: http://forum.joomla.org/index.php/topic,65.0.html

[Prasad007]

p.s. when wud this go stable then?

Whenever it's ready

Hate to give a date, because then if for whatever reason we aren't able to deliver on time, we get jumped on for having promised it by a certain date

Hey Prasad, welcome!
I get the impression that you might not know that there is already a stable version of Joomla that you can use.
This tread is a discussion about the new version. You can find the stable version (=joomla 1.0.5) here.

Sorry if I got this wrong 

P.S.: You also might want to change your signature. Here are the rules for this forum: http://forum.joomla.org/index.php/topic,65.0.html

done!

[cthree]

I've had a look through SVN and I'm very impressed with the amount of work the team has done in a very short time. One thing that still bothers me is that the components are still hard-coded with html. I was hoping to not have to hack edit the components/com_*/*.html.php files to produce the site layout I desire as I have had to do with 1.0.*.

Can the team offer any idea when we are going to see full separation of layout from code? This is today's holy grail of web development and I'm surprised to see Joolma lag so far behind on this score. I'll hack the files again if I need to but I just hoped that time would cure the problem.

Thanks for all you do!

[rg]

The article sounds very promising. Looking forward to the new release and the developer docs

[Jinx]

Full seperation from layout and code together with the implemenation of WCAG 1.0 is on the roadmap for 1.2. For 1.1 we have decided to refactor the core components in such a way that all output will be made in the html.php files. We will allow to override these files in your templates. This will allow u to more easily adapt the output of the core system in 1.1.

[nengrong]

The incoming new release will be alpha-2 or belta?

The next release of 1.1 will be alpha2.  Neither alpha1, alpha2, or even beta are recommended on live sites.

En, can you estimate when stable version may come out?

I guess I may not wait until stable version to come out, and will begin to set up the site as long as this alpha-2 come out (even though it is not recommended, since I already waited too long).

I will not use too many fancy or crazy mods, just common functions of joomla. So, alpha-2 may be ok to me.

What I am concerning is whether I can smoothly update from alpha-2 when belta or stable version come out .

[cthree]

Thanks for the info!

My needs aren't that complex so as long as there is a way to override the hardcoded stuff that should fit the bill until 1.2 comes out. I hate doing the same work more than once

[Jinx]

I couldn't agree more. We will try to accomodate u there.

[alfredo]

It's been said more than once that Mambo's rigid content structure, which was inherited by Joomla!, was one of the things that, if not a deep shortcoming, did impact negatively to newcomers.
Thus, my question is: Are we going to see a step towards flexible, webmaster-defined hierarchies for content, other than section-category, in 1.1?
Thanks and keep going! You're doing great.

[Tonie]

Unfortunately no, Joomla 1.1 will still have the same content structure. The number of wanted changes is so big that the dev team had to choose a subset for Joomla 1.1. Changing the content to a node based structure is going to require lots of recoding and is almost certainly going to break backward compatibility with previous versions badly.

[feldon27]

Is there a discussion by devs and core devs about how node-based content heirarchy is going to be done?

I would find such a discussion fascinating to say the least. I'm sure there will be an importer that does its absolute best to preserve everything.

Itemids shouldn't have to change, should they?

One of the hardest parts is that any script that depends upon a Sectionid to be set is going to be broken since I would imagine that Sections are going away. Every Category could have any number of parent Categories via a node system.

My impression is that people would have to redo all their menus but when they did, highlighting would now work properly (if you're 3 levels deep, all 3 parent menu items would be highlighted -- I'm having to hack modmainmenu.php to get this functionality right now).

[louis.landry]

Perhaps you should start a new thread for this in the tech zone

Louis

[vavroom]

@nengrong.  don't use an alpha release for your live site.  Why don't you use the current stable release, 1.0.5?

[nengrong]

@nengrong.  don't use an alpha release for your live site.  Why don't you use the current stable release, 1.0.5?

I am going to set up an fresh website, and UTF-8 is critical since the site will accommodate chinese_traditional, chinese_simplified and english simultaneously.

I ever tried Joomla V1.05 stable. I modified some files to UTF coding. Also, I ever tried the UTYF-8 version of Joomla V1.05 provided by Taiwan Joomla Translation Team. However, I always feel some bugs inside those codes.

For example, when I used the taiwan-translated version, I met some strange problems related with non-english characters. I ever wrote a chinese sentence as the title of a content item. The joomla system can not display that item unless I insert a space within the title. Similarly, sometimes I have to insert some spaces into the article to make it displayable by Joomla.

I guess the problem is related with encoding. I am sure my hosting mysql support utf-8. So, finally I gave up set up website before V1.1 is released. I think a Joomla completely based on UTF-8 will not have this problem, since under Joomla V1.1 alpha-1 I never had above problem.

This is why I am anxiously and patiently waiting for Joomla V1.1........

[MystaMax]

Seriously, I just had an epiphany.

The overall picture is alot clearer to me.  The possibilities become endless.  The talk about the developers hangout is just awesome.  Looking forward to the blog (just one more RSS feed to the list )  Bi-Weekly IRC Chats... Another great idea. I began to realized how powerful IRC really is. PHP, CSS, MySQL all have pretty good channels. The higher level of communication between develepers, joomla users, and the core team, makes for a very strong and vibrant community. It'll let everyone be on the same page!

Kudos to the Core. The journey over the next year or so should be very interesting for 3PD's!  I'm excited.

[hans.naphausen]

I notice the multilingual improvements of 1.1 but I am not sure whether or not this improvement will solve my problem.

I'd like to build a multilingual site in three languages :
- Dutch,
- English and
- German.

I'd like to provide the visitor to choose between one of these languages. I do realise that I would need to write every single content item (and polls etc. etc. etc.) in three languages, but that is fine with me. Of course the same question would extend to optional components such as virtuemart (php webshop)...

So will 1.1 provide an answer?
Or does anyone have a suggestion for me?

Thanks!

[Tonie]

Joomfish will also be released soon after 1.1. There are quite a few forum threads about this, it is specifically for multilingual sites.

[CavySpirit]

I'm also in a position with a strong need for multi-site, multi-user group capability. I really, really, really want to stick with Joomla. My timeframe for multi-site can hopefully be put off until towards the end of the year, but that's pushing it. Regarding CMS in general, if multi-site doesn't get here by then, I'll end up doing initial proof-of-concept in Joomla, and biting the bullet with serious development in Typo3. Ugh. I also need a way to easily interact with an Oracle database for some components. Not sure what databases this announcement might be covering, but if it's pure database abstraction, then I have hope?

[andesig]

Just wanted to add my own to the chorus of praise for the development team....

Well done everybody! I'll look forward to 1.1 with interest, and the subsequent move towards tableless presentation.

[Claudek]

Good work!
ACLs are around the corner now?

[Jofel]

Nice work fellows.

Can somebody clear something up for me? (Mr Jinx?) Will this new FTP support open doors for other components as well?

With other words: will for instance Docman use this so we can upload with the FTP protocol (and would be cool if this is possible on the frontend as well)?

[louis.landry]

The FTP support is part of the filesystem class layer.... in other words, anything that uses the JFile or JFolder classes for filesystem operations uses FTP when necessary.  Also, the FTP class JFTP is available for use by any 3rd party component.... its part of the new JFramework API



Louis

[dyrer]

Will 1.1 include in-built gallery, like other CMS?

[louis.landry]

No, it will not.

Louis