CEGUI (Crazy Eddie's GUI) Forums

Hi all.

There's alot of uncertainty sorrounding the 0.5.0 release for alot of you I think. Including myself to some extent.
So to get some things straight and to try to take the library development more public, I'm starting this thread.

The original release date we "decided" on IRC was April 1st or 2nd. Whether we will make it or not I am not completely sure of and in a way the release still feels a little premature too..

I've been fairly busy lately and have'nt had as much time as I had hoped I would have for CEGUI, so I pretty much have'nt finished any of the things I said I would. Shame on me

Anyway to let you guys know a little more about whats happening I'm posting the preliminary changelog so you can all see what has been going on:



Yes. It's huge!

OK. Now a question for Paul: I have added a <TextProperty> and <FontProperty> tag to Falagard for the TextComponent. It should be obvious what they do... Should I commit this now or after we release? I'm asking as we did say that the ~26th should be code freeze date back then...

Another one for all of you:
Many of you probably know that I've been working on a listbox replacement for a long time. It does'nt look like it will make it to 0.5.0, but I'm about 95% done and I could really use some feedback on it soon.

If I post a patch will anyone test it?

Amazing work!

I'll be switching over when its released. The combination of lua, layouts and falagard almost completely eliminates the need for C++ glue code, so its a great step forward.

I also think that we will not make that original date. There are still many outstanding issues, ranging from specific things such as XML writing that still needs some things sorting out to much more overall changes, such as those relating to the MIT license change.

Similar to Lindquist, I have been spending my time elsewhere, and so there are a number of things I said I would do which I have not. So, in effect we're pretty much in the same kind of position we were when we first spoke about preparing the release - this means that we still have that work to be done

@lindquist:
Those new Falagard elements sound fine, you can commit those when you like. It would be cool if you could email me some text to add to the reference doc (don't change the wiki version, since that's intended to be in sync with the current release, and I already have a couple of other bits to add / update when 0.5.0 finally arrives).

I'll certainly look at your patch if you post it. Maybe people here would like to offer an opinion on something; would they prefer that we delay 0.5.0 a while longer while the new listbox is integrated and tested, or, have an earlier release of 0.5.0 but without the new listbox (which, depending on implementation details, could mean it would not arrive until 0.6.0).

Wow guys, that list have become very long!

Dalfy and I had a little chat (email) about the editor deadline. We actually targeted for this week too, and the 0.5 compatible layout editor is shaping up nicely, mainly thanks to Dalfy! However, with both a fulltime job it will be tough to complete it for the full 100%, including installers/distributions, wiki updates and such. (Just plain code-wise should still be quite doable.)

Besides, the overhaul to the branching, the re-versioning and the wiki update so far, have taken chunks of my time, but I thought it was/is needed in order to support both 0.4 and 0.5 libraries in the future.

Shall we continue this thread to propose a new deadline then? Or remove some pressure by taken a “when it’s done” approach? I would vote for the first one though, to at least stay in our “momentum”

Well, I just thought I would add my $0.02, as any concerned user might want to do...

Since this list is already so big, and the developers of CEGUI are anticipating the users to have a few problems when upgrading, maybe the Listbox changes can get pushed back to the next minor or major release.

That said, I can understand that you might not want to do many consecutive releases that require code changes when users upgrade. This would be motivation to push the release back, and cram as many "build breakers" into this release as possible.

I'm sure the general public is anxious to try out the new Listbox and give you feedback, but many of us work off releases, and want to sync up. Since I'm ignorant as to exactly how much work it will be to upgrade, I will trust your decisions about when to freeze for the next release.

Good luck in your other projects and thanks for CEGUI. It has been working very well for me. HTML rendering would be a major feature request, and about the last major feature I see CEGUI lacking. Maybe support for that can be on the roadmap as a goal for an upcoming release?

The listbox widget does not introduce breaking change cause it is a completely new widget. I think we should put it in the release in order to get some user feedback until lindquist dive into changing the other similar widget.

Thank you for posting this!
It is evident that 0.5.0 is going to be a great release!
And a perfect opportunity for me to CEGUI-fy my project!

I have made a patch containing the new listbox against the latest SVN trunk code.

http://www.prokop.dk/tomas/itemlistbox.patch

The file has CRLF line endings...
You'll need to add the new files to the project before building too.
Demo8 will be transformed into a small test of the new widget.

Feedback is VERY much appreciated as this will be going into the base library soon.

And please ask away if you have any trouble.

This post is regarding the latest Falagard additions:

the <TextComponent> now allows <TextProperty> and <FontProperty> elements.
Order is Text, TextProperty, FontProperty.
Both new elements are optional.

If a <TextProperty> is given the text that will be rendered for the TextComponent will be fetched from the property given:
<TextProperty name="Text2" />

If a <Text> element with a non-empty string attribute has already been given, and (in this case) the 'Text2' property contains an empty string, the text string from the <Text> element will be used.

This makes it possible to create a default text value.

The <FontProperty> element is very similar to <TextProperty> it just controls the font instead. The same "defaults scheme" apply.

Additionally the <Child> element now supports a 'renderer' attribute. Which is optional like the looknfeel attrib. Can be useful for making layouts in falagard without need to FalagardMap all the looknfeels...

Dalfy convinced me that a branch would be alot easier, so if you'd like to check out the new widget but dont want to apply the patch manually, you can just grab a copy of the 'pre-itemlistbox' branch

hehe
Branch are for this purpose and are cheap why not using them ?

Hi,

I am not a user of CEGUI yet but I have question and I hope it has not been answered or it is simply silly. Will the 5.0 version include Lua 5.1? This might be interesting because of the incremental garbage collector. If not - Did you use an own namespace for lua? Otherwise I am sceptical how to use it in a Project that is using lua 5.1 (linking issues).

Apart from that question: Great work!

Sebastian

lindquist wrote:Dalfy convinced me that a branch would be alot easier, so if you'd like to check out the new widget but dont want to apply the patch manually, you can just grab a copy of the 'pre-itemlistbox' branch

Great thing that. I really was waiting for these. Am I right assuming this means the nice tree control can be ported to the new system and be integrated into the trunk soon? My in game property editor would really profit a lot from fully customizable tree or list elements.

it's definitely possible to implement a treecontrol based on this new listbox, as putting a list inside one of the items is pretty trivial.

but.. right now, I need to get some feedback on this one, before I start making derivatives...

Couple questions...

Is the 0.5.0 release scheduled for "any day now" or "any week now"?

Also, I noted a move to the MIT license in a couple of posts; will that be coming with 0.5.0, or later?

Thanks!