Submitted by Ident on
User "iceiceice" took the CEGUI library and the Samples using OpenGL3 Core Profile Renderer and ported them to OpenGL ES2. This way he could use them with emscripten, making it possible to run CEGUI in your browser.
More Info here: http://cegui.org.uk/forum/viewtopic.php?f=4&t=7065
This is the link to the result: http://cbeck88.github.io/cegui-emscripten Try it out, it works really well!
Submitted by Ident on
We got a new user contribution from lucebac that just got merged into CEGUI's v0-8 branch yesterday, which will be part of our next CEGUI Release (0.8.5).
He provided what we decided to name "application templates". The currently present application templates (based on GLFW and SDL2) are buildable using CMake for your OS and IDE of choice, just like the rest of CEGUI. The templates are small stand-alone minimal applications that use CEGUI. They serve as a great starting point for creating your own application using CEGUI or might be used as quick guidance to integrate CEGUI into an existing program.
Up to now we only had the SampleBrowser, which in itself is great for showing off samples (Be sure to check out the well-documented code of the samples to learn CEGUI) and for us to quickly test if features still work, but was not a good starting point to setting up your own CEGUI application or for explaining how CEGUI is set up. We suggest beginners to most of all, read the API docs, then to look at all samples in the SampleBrowser that are relevant to them and finally to grab the application template and see how it works.
In the future we would like to add support for more window creation systems for the application template, and maybe also a Ogre and Irrlicht based application template. User contributions are very welcome (https://bitbucket.org/cegui/cegui)
Also I want to remind all our users of our Ticket Issue system on bitbucket: https://bitbucket.org/cegui/cegui/issues
I was made aware recently that there are some issues that do not get reported on our forum or issue tracker by users. It is very important for us that unreported issues get reported on our issue tracker (or at least on our forum). Use the search function to look for reported issues. If the issue was already reported you may also additionally comment on it or add your vote for it, which will raise awareness. We definitely pay more attention to issues (and also suggested features) with more votes, since this shows they are likely to be relevant to more people.
Discuss the news here
Submitted by Ident on
For those who haven't visited it yet, check out CEGUI on Open HUB: https://www.openhub.net/p/CEGUI
It contains interesting information about the CEGUI project, its commits, contributors and a lot of statistics.
Submitted by Ident on
Unfortunately we were not accepted for Google Summer of Code 2015.
We had 3 successful years of participation, with a 100% completion rate and we are very thankful for that.
Ogre3D was neither accepted this year nor last year. Mozilla also apparently didn't make it. It seems that a lot less organisations were accepted this year (2015) compared to 2014.
The accepted organisations can be seen here: http://www.google-melange.com/gsoc/org/list/public/google/gsoc2015
Submitted by Ident on
Timotei has finished moving the issue tracker from our mantis page to bitbucket. All issues have been migrated with their original IDs, attachments, contents and comments.
The CEGUI issue tracker can be found here: https://bitbucket.org/cegui/cegui/issues
and the CEED issue tracker here: https://bitbucket.org/cegui/ceed/issues
Our old mantis page will stay online in read-only mode. Remember that the IDs of mantis tickets are identical to the IDs of the bitbucket if you want to access the new ticket, e.g. :
https://bitbucket.org/cegui/cegui/issue/358 <- migrated from http://cegui.org.uk/mantis/view.php?id=358
You need to select the right project on bitbucket first when you do that (i.e. CEGUI or CEED or SILLY)
Here is our twitter tweet: https://twitter.com/ceguilib/status/570669620908171264
Feel free to create new issues at our new issue trackers (but please only use it only for bugs/features requests etc and not for support requests and stick with the layout ;) )!
Submitted by Ident on
All current mantis tickets have been migrated to bitbucket issue tracker. Therefore, we call all people who care that their past CEGUI mantis ticket submissions are attributed to their bitbucket accounts, to tell us their CEGUI and bitbucket user names: just write to team (at ) cegui . org . uk - We will then correctly link all comments and reports to the supplied account.
We give users 3 days to notify us. Until then our new issue tracker will not go public. Our old issue tracker will remain online for the next months as READ-ONLY, until we decide to remove it entirely. For now, this means you will not be able to post new issues until the 3 days are over: The new issue tracker goes online on Monday 23rd Feb 2015
So again: Everyone who wants their tickets attributed to their bitbucket account (otherwise it will just say "anonymous" and underneath "original author: XXX") should notify us.
Thank you!
Submitted by Ident on
First we had issues with the DNS because of the domain hoster which changed things without notifying us. (great job!). It took us some time to resolve the issue because CrazyEddie's e-mail was not reachable because it was part of this domain (lol!). And this was the only contact we had of him, until we found some other e-mail after days of stalking him on google (and finding no nudes).
Btw., in cases like this it is good to check our twitter for updates:
https://twitter.com/ceguilib
After we had resolved our issues we noticed that our site may still contain backdoors (from the drupal hack-wave in october 2014) and we actually found malicious files there as well as an altered google cache, manipulated php files and finally decided to completely roll back our entire database by months and re-add all news manually. This whole process took us a while. I did the finishing touches today, so everything is up again.
On a completely different note: We are going to remove mantis and move all tickets to the bitbucket issue tracker. In the future users can file tickets there. We believe this will be better for our users.
Submitted by Ident on
Slight headache after waking up, the limbs feeling stiff after a short night's sleep, small patches of cookie dust sparsely spread around the mouth, the sensation in the mouth that grossly reminds of past sparkly wine consumption, ones hair smelling like short-term exposition to ridiculously high amounts of fine dust pollution: This all is clear evidence to me, that the last year has very recently drawn to its end and I have successfully (and alive) managed to enter a new year, again!
Somewhere along these lines, but actually completely unrelated to them, the entire CEGUI team wishes you all a successful, healthy and overall superior year 2015!
About CEGUI in 2015: The plans for this year for us are mainly revolving around the upcoming 1.0 Release (Q3 or Q4) as well as continuing support and bug-fixes for the 0.8 versions. The 1.0 developmental version already offers a lot of new great features, so that we really wish to release this version as soon as possible, of course we have to finish and test all new and planned features before that. See Martin's and my Todo list on the wiki if you are curious about some of the features we still have to add / rework for the Release or check the forum, the last GSoC topics or chat with us on #cegui.
Also we recently enabled file attachment uploads in our Forum. This will make it easier to show screenshots or describing issues in the future!
Submitted by Kulik on
Hi,
our site has been hacked on 13th November 2014. I have restored the site
and updated to Drupal 7.33. We have no way of knowing what was leaked,
so we assume everything was leaked. The passwords in our database are
stored in a secure way and are not simply retrievable using rainbow
tables or similar. Either way we advise you to change your passwords
just to be absolutely safe! We are very sorry for the inconvenience.
As far as I can tell https://www.drupal.org/SA-CORE-2014-005 was the exploit used. It's curious that I can see somebody gaining access on 13th November even though the embargo was lifted on 15th November. I will continue to monitor the situation.
Submitted by timotei on
Hi!
First of all, thanks should go to the CEGUI Team for inviting me as full team member and I humbly accepted it! :)
Now, to the actual article. This summer I worked on a brand new feature for the future CEGUI 1.0 (or, at least, the default branch) called Model View. In short, it's a very nice and good way to decouple the rendering (View) from the actual underlining model (Model), so that they can be replaced as one wishes. For example, we could have a complex (I don't like how it sounds, but for the sake of examples, bear with me) Model that loads some game data from the disk/network/etc. The "Model" is just a term for some class(es) that hold some pieces of data that are necessary for the game. Once you have the model created, you can create multiple views that represent data differently. For example, you can show it via a list view, grid, tree or a custom view you have created. The "View" is represented by a widget/control.
But, in order to provide easier (initial) migration to the new views (yes, we removed the old Listbox/Tree/Itemlistbox - and we'll remove some more, as soon as we have replacements; yes MCL, I'm looking at you!), we have created some convenience widgets that have the view and model in the same package so that they can be used as an in-place replacement from the old ones.
Unfortunately, I don't have any (relevant) screenshots of the new changes, since they are mostly internal, but at least, the TreeView rendering is now much better in respect with the icons.
Another thing that might be of interest, is the performance of the new views. In the following table we can see the improvements, for a benchmark of different usage patterns (total time taken to add ~500 items, clear them, add some more ~1000, edit some, delete some - and with rendering after each step):
| Widget -> View | Widget test running time (seconds) | View test running time (seconds) |
| ItemListBox -> ListView | 3.35 | 1.40 |
| ListBox -> ListView | 1.96 | 1.40 |
| Tree -> TreeView | 1.96 | 3.85 |
The tree unfortunately takes a bit more time, but it's relatively the most basic implementation and no attempts to optimize it have been done :) But once we'll finish them you can expect at least the original speeds, unless even speedier.
That's all for now!
PS: Stay tuned for some news related to CEGUI binaries and simpler/nicer integration of CEGUI with your projects! :D
