Development libs and packages

build-essential
devscripts
dh-buildinfo
libarchive-dev
libc-dev
libcairo2-dev
libdbus-1-dev
libfixposix-dev
libgconf2-dev
libgdk-pixbuf2.0-dev
libgdu-dev
libgdu-gtk-dev
libgee-dev
libglib2.0-dev
libglibmm-2.4-dev
libgstreamer-plugins-base0.10-dev
libgstreamer0.10-dev
libgtk-3-dev
libgtk-2.0-dev
libice-dev
liboobs-1-dev
libopts25
libpango1.0-dev
libsm-dev
libx11-dev
libxml2-dev

Vala packages

libvala-0.12-0 0.12.1-2
libvala-0.14-0 0.14.0-1
vala-0.12-doc 0.12.1
vala-0.14-doc 0.14.0-1
vala-dbus-binding-tool
valabind 0.6.4-1
valac 0.12.1-2
valac-0.12

Development IDE

anjuta
anjuta-extras
glade
nemiver (debugging)

Suggested Usage

I put the entire Anjuta project into subversion. If you’re developing then here’s what I’d do as there are absolute paths stored in the Anjuta configs.

1. Create a new VALA project in Anjuta
2. Grab the vala files from Subversion along with the .glade and .ui files
3. Add in the references at project level (right click in Anjuta and add:

–pkg gtk+-3.0 –pkg gdk-3.0 –pkg gdu –pkg gee-1.0 –pkg liboobs-1 –pkg libxml-2.0 –pkg pango –pkg pangocairo –pkg posix –pkg gconf-2.0 –pkg gstreamer-0.10 –pkg

4. Add the libs to the EXOGENESIS build (right click and choose NEW LIBRARY).

5. As this is a test config there is a hardcode path in main.vala ( change to your dev location).

6. There is an array of windows in fexomainwin.vala, this is the flow of windows for navigation. Basically the screens are made up from the following:

i. App creates a main gtk3 window and adds in 1 box.
ii. Screens are read from glade (exogenesis.ui) file. Basically, these are boxes added as top level items. The reference to the box is added/removed to the box on the main Gtk window.
iii. Utility functions are loaded globally.
iv. A global reference exists to gInstallData, this holds all install information that will be applied. This includes user and group information, disk partitioning, language and timezone config.

If you have any questions then please get in touch, it’ll be easier to ask rather than try to work it out.

Steve.

During the rework we decided to simplify the installer UI, especially when it came to disk partitioning. This has a couple of simple options:

- Take over complete hard disk – Will delete the existing schema, create a partition schema based on a series of space/RAM calculations. Basically implementing a Root/Home/Swap schema.
- Alongside – Will resize the available space and create a schema as above.
- Advanced – Will allow you to repartition the disk however you see fit.

The core code has or is currently in the processes of rationalisation to make it easier for other developers to pick up.

There is still an option to backup all users and groups complete with Home folders to USB disk if you do choose to take over the entire drive. If this option is chosen then data is copied back from the USB disk into the appropriate home folders at the end of the installation process. It is hoped that this will help those that didn’t have /HOME on a separate partition to move over to Aurora without losing data. The USB disk needs to be at least the size of everything under /HOME. As passwords are not copied, user accounts copied from a previous version have the password reset to “aurora” and the password change flag set. Users will need to change the password at first logon.

If you do fancy lending a code hand then you can grab the latest version from subversion and hack away. Code is in Vala and project managed with Anjuta. There’s a couple of README files that list all the dev libraries you need. If you do pick up some development then please let me know what you’re working on to prevent duplication of effort.

Based on the time spent on this rewrite so far I estimate that there is around 5 weeks of development left before a test release will be available.

I’ve been posting screenshots on Twitter (@preobrazhensky), I’ll post some on this blog as and when things get finished.

Steve.

Paul is still working on the themes and packages required to implement a clean version of systemd and migrate as many sysv init scripts as possible to give the best boot times.

We still need devs (vala or C), we need plymouth designers and package maintainers… Anyone, anyone, anyone? Bueller? Put your hand up if you want to give us a hand…

More updates soon, soaking up the alcohol in Moscow till Jan

Merry christmas to you all!

Steve.

PS: source available here:

http://subversion.inixsys.com/exogenesis

u: exogenesis
p: exogenesis

Please ensure you add your name and address details to the change log when checking stuff in to get the credit when credit is due

Steve.

We know not everyone uses Twitter so this week I’ve added some further features to the blog

1. Auto Post to Facebook – all our likes on Facebook ( http://facebook.com/getaurora ) can now get updates from the blog straight in their feed.

2. Auto Post to Twitter – Auto post of Short link URLs for new updates to our twitter account @getaurora

3. Auto Tweet to Post – Tweets made from the @getaurora account will appear as a mini Blog update for those not using either service.

Next Step is to try integrate the updates here into the Google Plus page I’ve recently setup but no content is on there yet!

Main priorities now are to get an Alpha release out to get the installer tested while we finish working on the DE experience and to make sure you all know about it!

A quick update on some upcoming changes to the website infrastrucure and technology used on the Aurora Web Servers…. We are looking at merging the current forums , Main site and blog into ONE running under WordPress – this is for easier management , site intergration , and future developments I will not yet discuss

To tie into this we will be making some visual changes to the site over the coming weeks. Once the redesign is completed it will relaunch in WordPress with no visible changes ( all the work will be the in backend ) but it will allow us a much better control of future projects and additions to the site.

We will be hoping to either intergrate the existing phpBB build we use for the forums or migrate all user data into the bbPress forum solution – the reasons for this are due to authentication and our Single Sign On plans for the future – we will ensure any migration is completed with minimal risk and that we will only complete if it offers a like-for-like or better User experience to our current forum.

We will also be working on a mailing list functionality including discussions and a monthly newsletter ensuring you are kept in the loop!

With the current changes already we have been able to tigher intergrate the facebook group and twitter profile so the latest news and changes are available. We will be hoping we can engage members of the community who want to help in creating a more regular blog roll aiming at teaching new users how to use Aurora. Screencasts, Tutorials and more!

You may remember a blog post afew months back showing you the current working desktop model we have for Aurora – we have been working on perfecting this even further and getting a UI that really does get out of the way

The challenge with Gnome shell is its default setup – so we have made some fundemental changes to this

Windows lists are a default behaviour so you can see and manage multiple windows from the taskbar ( otherwise its not much of a taskbar)

The messaging tray is gone in favour of notification icons in top corner ( not final solution as we are looking to a single icon option )

glass dock – this is a skinned dock at present but the aim is to develop this into the “drawer” where you can drop any website, application or document you like.

Finally – the wallpaper in this picture is NOT the default – we are testing with a range of wallpapers to ensure the glass works well with all default wallpapers and does not remove focus from the elements.

So I hope this wets your appetite

PS – As I tweeted the other day we’ve managed to get 6-15 second boots now in a VM for the latest systemd builds so close to our 12 second aim

Paul (guitaraholic) has been extremely busy with his new job as a middleware expert for a large, well know media company that rhymes with urgin’.

I’ve been tied up on paying company business and swamped with so much code that I could vomit at the sight of another “if” statement.

Excuses Done

It’s back to the rock and to chip away at the encrustation that has formed on the installer code, kernel mods et al. Pick axe in hand (pneumatic drill required) we’re at it again.

Still based on debian, SID, SystemD and still with our own installer, going with a themed gnome-shell.

The installer code is in subversion, if you fancy lending a vala hand then get in touch, the more the merrier and the faster it’ll be done.

The repo’s are down after a server crash. They were outdated so they’ll be offline for a while whilst we populate with newer packages ready for the ISO release early next year (2012! Before someone coughs ).

Further updates soon, and please, get in touch if you want to help out, package maintainers, vala coders, plymouth designers, shell themers… we do need your help. Paul and I can’t possibly deliver everything we plan to get in the release without YOUR help. Please get in touch and get involved. We had so many ideas and so little resource to deliver.

Thanks,

Steve.

I promised an update this week so here it is

Where we are heading….

Aurora is not aiming to be the “best” Linux distribution , it’s not trying to re-invent the wheel, it’s not trying to do something new. Aurora is here to put the pieces together and make a great product. We have thought long and hard about what that entails and have had SERIOUS version 1.0 feature creep but we think we have finally bolted down our requirements and have the end in our sights!

Gnome 3

We’ve decided that to ensure a stable base with continued development ( and a quicker / easier development lead time ) to focus on using Gnome 3 – aiming for version 3.2 for stable release This decision will mean that these are so many changes to the distribution that it really isn’t feasible to upgrade from ANY old version – the reasons behind this are simple – we are developing a “Semi-Rolling Release” mentality which needs a VERY stable base to build off. We don’t feel those users who attempt an upgrade will benefit and enjoy the stable base and it will cause problems overtime.

So whats a “Semi-Rolling Release”????

I’m sure we could come up with a better title for this but it is as follows….. We will provide the ability to have a Stable code distribution ( which will only receive bug fixes or new versions after heavy testing ) and a testing branch ( newest versions as available , tested then pushed to stable ).

In addition to a stable / testing option for the “core” of Aurora we will also have a stable option for applications ( you won’t get the latest applications straight away but will get the most stable version we deem suitable for our users) or testing applications – getting the latest / greatest applications as they become available for Aurora. We know you don’t want to be stuck on an old version of Firefox or Shotwell just because you want a stable distribution so now you don’t have to be! BSD based distributions have had this idea right all along so its about time Aurora was the same!

Our unique twist on the rolling release idea is that you can pick what you want Aurora to be like for you!

The Aurora DE concept

So you want to know our plans for the Aurora DE? Well we have been working hard on what makes a DE great and came to 3 simple conclusions :

1. It should make you quicker and more productive at what you want to do

2. It should help you and be obvious to use

3. It should get out of your way

That’s the core of the Aurora experience – it should complement what you are doing at all times! By no means will we get this right 100% to start but we will work with users – taking patches , ideas and feedback from the community to make this happen!

So based on the 3 points we have developed what we believe Aurora should be like : here are our mock-ups

I understand that this is a very sketchy mock-up so I will try to explain our ideas ….

1. Launch Control – The Top Left corner launches the search bar , menu and drawer.

2. Search only appears when you need it – lets you search the web, your applications and your documents in one simple place

3. Application Blocks – when an app has a notification tray icon is will appear here : you can select obvious to use features in each app i.e – email can compose a new message.

4.The Drawer – you can drag your favourite documents , websites or applications down here – it hides off-screen and is only in view if you hotspot the top left corner or the bottom of the screen. This is our alternative to the gnome dash ./ favourites in shell.

5.Your Desktop – just as you expect it to be

6.The Menu list – a familiar menu system broken down by category of application – you can click-through the menu’s as you see fit

Some more mockups showing closer detail of our core 6 sections of the desktop.

Showing the Launch Control , Menu system and Search functionality – all of these components are only visible when you need them! The rest of the time they slide out of your way

The Drawer – A easy way of managing your favourite things to do – we don’t discern between a “file” or a “website” or even applications! In our book anything can be a favourite so you can put it in your drawer

Application Blocks – How they behave! we also have ditched the typical “pop-in your face” notifications for a style adapted from Android – Notifications roll down in the panel and only take focus if you click on them Launch control will also show a history of these notifications if you missed them

Teaser time!

We are working very hard to make the above mockups a reality – while they might not be 100% implemented in the first release we will definitely have the outline of our goal in place – the finishing touches to functionality and behaviour will come from your feedback on these…… so as a final treat this is exactly 100% running system of what Aurora currently works like

Firstly I’ll like to start this post with a much deserved apology. Aurora has really slowed down in development over the last 6 months. The reasons behind this are easily explained.

Developer Situation

At present Steve and myself and the key developers on this project – we receive no funding and no commercial support in building Aurora  ( we build Aurora for our own use so we DO use it at all times! ).

Both of us have been very busy this year with new work responsibilities, tougher deadlines and our full-time jobs. Aurora is something very close to our heart so to ensure the quality of development stays high, and to meet our high expectations of release, we took the decision to slow down development on Aurora until the support packages and projects were at al Level were we where happy to continue and pick-up where we left off.

This break has allowed us to re-focus on what we feel Aurora should be in the light of Ubuntu’s new unity interface, the Gnome Shell release and upcoming opensource projects such as Exogenesis and the Cream DE.

The Ball is rolling again…

We can confirm we are started work on Aurora again and are pushing a beta release as soon as the Installer is 100% completed. Once this is done we will be working to move our development to run more in tune with a typical open-source project.

Out kernel development, installer and other additions will be hosted on gitorious.org and we welcome contributions for users and developers alike.

The future

I can confirm we are looking to move to Gnome 3 for our release ( 3.2 for stable release) but with heavy modifications to the gnome-shell environment. We will be posting some updates and some screenshots / mockups later this week of our proposals – the quicker you can help get these in the quicker Aurora can be fully released.

Our Packaging / Release Ethos

The next piece we want to clear up for our user is how Aurora will be released and updated. Due to the amount of changes we don’t feel it will be a stable / feasible change from Eeebuntu 3 or last years Beta 0.5 . The reasons behind this are due to the vast underlining technical changes to the OS and the sheer size of updates would probably be bigger then a new iso.

The next beta we release WILL update fully to the new version

Our new development structure will be a 2 piece release. All ISO’s will automatically be updated every 3 months so when you download Aurora you will be downloading close to the latest versions of all packages. By default the user will be presented with a stable distribution “core” and stable “applications” set. These are deemed stable and only small bug fixes will be made to these versions.
At the users request ( via additional settings ) you will be able to opt in to 2 different pieces of the puzzle.

But I want the latest and greatest applications ALL THE TIME

Well you can! We will have a separate “testing” phase where new applications are added – these will be released and tested by users and reported back if any issues. After a period of testing ( still to be decided ; possibly per app ) they will be pushed to the Stable environment.

But what version are YOU using?

We will also have a “testing” core build – this will include changes to the core system – only advised for users who know their way around the system and can comfortably deal with the odd regression here and there

Keeping it simple for updates

I can pretty much be sure that a large percentage of users don’t care what a lib files contains or does in terms of the application as long as its installed and the application works! Post launch we will be looking at ways to improve the update process by using a simple / advanced view choice – the simple view will simply show you the Application which is being updates or list as a core component. Advanced will give the current description of all packages…

And Finally …

We will be pushing a new post later this week with some mockups so we NEED feedback on users opinions on these …. we also need some budding web developers / gnome users who want to start looking into helping us build the gnome-extensions we need to create a fantastic experience for you.

Thanks Guys – we aren’t Vapour-ware - Aurora WILL come!

After some great work we have Plymouth working with the SystemD-17 builds we are currently working on for the next release ( once the installer is ready ) .

We are looking at having a simple yet suitable plymouth theme for the iso – if you feel your plymouth design or have a good idea / concept for how we could do this please let us know!

Look forward to hearing your ideas / seeing any designs! on the forums too : http://forums.auroraos.org/viewtopic.php?f=64&t=6202

PMcD