Joomla! Discussion Forums

Louis - fair enough. Cheers.

Article link sent by PM to review
(pressure's on you guys now, lol.. )

Thanks, Joe ! Well received and work is underway, just need some sleep first. 

What I want to know is this - is it the serious nature of this thread or some other factor that caused the grinning cat to disappear????
Did Joe feel an article submitted by a crazy looking cat might not get taken seriously?
Was the photo really taken in front of, or behind a prison fence?

Conclusion: who cares? It's just nice to see Joe's face 

Thanks Elpie, guess I'll have to take off those glasses now sometime, right..?
(normally, the ladies fall in love with my eyeZ! )

I felt it was about time, due to the U&A under my nick and other stuff (larger pic available on joomla.fr etc)
About the cat: yeah I miss it, I see you got rid of yours too in favour of Santa!?
Always during the holliday season, lots of abaondonned avatars haunt the internet, looking for a new master..

Still grinning though

Any possible updates/estimates on either 106 or 1.1alpha or anything..? Thanks.

Both are on their way out soon.

Your not speaking on behalf of the community. Nobody restless and is waiting for small changes, nobody is waiting for "a 1.1."
W're waiting for functionalities such as ACL and the JoomFish.

Hey guys,

Just wondering what the scoop is on 1.1... I have a fairly large project that I would like to develop on the 1.1 platform, mainly due to the language features that are being implemented in this release. Since I'm not a very experienced Joomla developer, I'd like to hear what people think about trying to develop something on the alpha release. In this thread I've seen some concerns about changes in the CVS releases causing the developers to have to rework their code. While I understand that this is the case because the software is in development, I also don't want to jump into developing and then up struggling because I'm such a newbie at component development.

Whaddya think?

Thanks,
Andy

I would say you should develop on 1.1, but you should wait for the alpha2. After that, I don't think that there will be many changes in the API.

Thanks Hackwar, that helps. Anyone have word on the release of 1.1 Alpha 2?

I would recommend developing on 1.1 right now.  I am, and it helps with the QA of 1.1.

me, too - I've a problem, to dev or not... but one good thing is waiting, yes. But this occasion is worth for a deeper knowledge of the new 1.1 - me too I'm wating for understanding all news as I have a project to develop, a new comment/review system

Same here... I have a project that would best be built on Joomla with UTF-8 encoding, and involves lots of other things like gallery and shopping cart and stuff. If I had an idea when 1.1 will be released I can tell my client to postpone the project a bit...

I thought about developing it base on the current release but I'm new to Joomla and definitely not an expert in programming, so I'm also worried about messing it up since it will be a production site...

Will it be released in a month? 2 months? It would be great if I could at least have an estimate, so that I can discuss with my client about this...

Thanks in advance ! 

Johan gave a hint that it could be around april/may.

As per roadmap the beta will be out in Q1 of 2006, that gives us to the end of march

O that's GREAT news !!!!!!!!!!!!!!!!!!!!

Thanks sooooooooooo much guys ! Now I can stop worrying about it and just lay back and relax till the release of 1.1 

(And start making a list of components and bridges that will support 1.1 hehehehehe)

THANKSSSSSSSSSSSS !!!!!!!!!!!!!!! 

But it's much more safe to set date of release to May 1st and be nicely surprised when it will be released earlier

I haven't set a date did I, just repeated what is on the roadmap. First beta will be out in Q1. That's all.

... and even in the case of a delivery on april or may... where is it the problem?  For the GREAT work doing on the 1.1 I think worth waiting a while 

Being one of those who is participating in the alpha (which anyone may do in the Q&T forum), what is being done by the developers is phenominal, and worth putting any release back a bit, while bugs are squashed.

Only thing I hope is not too much will want it's place into 1.1, and thus another endless wait with delays after delays like for 4.5.3 starts.
No matter how good the final product, if the public roadmap is not respected, even though it IS subject to change, this will lead to distrust and more and more questions etc. We all remember 4.5.3 days, right?

yes we do..... we all do

Louis

ok, but now we are on march... and I think only "special" 1 delay (1 month?) perhaps isn't so terrific... even if in this case we are talking about the future... and then, if you see what great work doing on 1.1... you're happy to wait for it. The core of the problem is not to delay endlessly, but at the moment we aren't in this case. If so, I hope (4.5.3 memories) a short delay... surely but even for a bit of delay for avoiding any problem there is only 1 solution: communication & communication... and the community will understand that worth waiting for... 

I think I'll try to describe whats the difference between 1.0, 1.1 and later 1.2.

1.0: A big block of code, massive, difficult to use, not really good to manage, restricted function and a pretty static user interface. All in all a restricting framework with a lot of flaws

1.1: Small, easily interchangeable parts, coded along of coding standards, easy to read, easy to manage, enriched by a few functions, but still restricted in many parts and we still have the same user interface. Framework gets better, but to keep backwards compatibility, the problems in the framework from 1.0 are still present.

1.2: Below the surface a lot like 1.1, but with a new, superb user interface, lots of new functions, removal of allmost all restricting aspects of the old framework.

1.0 is like a Tin Lizzy from 1920, while 1.1 is a Ferrari in the shell of a Tin Lizzy and 1.2 is a Ferrari Testarossa, which uses as much as a quarter gallon on a hundred miles. 
All these are exagerations, since there are some tweaks in the user interface in 1.1 and the problems with the framework are much better, but nevertheless 1.1 concentrates more on the engine and the stuff for the 3PD then on the end-user.

Question on backward compatability now and for the future....

I know most 3PD  projects usually break when some function in a core file changes or the file that held that function gets removed altogether...

Wouldn't it be possible to create some sort of legacy.php file that old functions could be moved to and included for backwards compatability?

this would allow old components to work while giving 3PDs some time to upgrade their projects to use the new methods that have been updated....

And end users wouldn't have to sweat what is going to break everytime they performa  core upgrade....

This legacy.php file could be pruned of antique functions after every major release (1.2 would prune all 1.0 legacy functions but keep all 1.1 legacy entries) and that should help alleviate any minor breakage while 3PDs transition to the new core...

It's allready done that way. 1.1 (=1.5) keeps 80-90% backwards compatibility. However, not all functions could be kept, due to the changed framework. Most extensions will still work with 1.1, or just need minor modifications. It is fairly normal, that extensions break when a new version is out. I would compare the step between 1.0 and 1.1 with the change from Win 3.11 to Win95. The bc and the changes are similar.

I understand Hack but you could use the functions in legacy to convert to the new framework no?

I can understand changes to the output not being solved this way but most projects break when the project can't get the input it used to get because something in the retrieval of that data changed...

It's not a big deal really because the best projects are usually right on top of the Joomla Changes just something I thought I would throw out there as a possible solution to legacy apps that users rely on but might not be updated as regularly as they should be...

I'm not a big fan of backwards compatability, it reduces the drive for innovation. That 3PD projects crack means there is not enough motivation to maintain a product. A legacy.php file is an excuse `to be lazy´, there´s no need anymore to be innovative. Backwards compatability requires a lot of attention and effort that better could be used to improve and incorporate `the better`.

I sharpened this statement above, the fact is that there is and always will be a little bit of backwards comaptability needed.

That's my idea also! If you're slave of a total compatibility you don't progress anymore!!!!!!!!!!!!!!!!!