If you use an operating system other than Ubuntu Hardy you will now have to use Envy Legacy. Envy New is dead and will be soon replaced by EnvyNG.

Release highlights of Envy Legacy:

* Fixed: Envy tried to install dkms on Debian.
* Fixed: the GUI didn't show the missing dependencies which can't be installed.
* Added: Nvidia drivers 96.43.05, 71.86.04
* Added: AMD Catalyst driver 8.02

Enjoy

EDIT: there was a problem with the ATI driver which I have just solved. Please download Envy Legacy again

EDIT 2: I have updated the NVIDIA driver to version 169.12

Posted by Alberto Milone | February 26, 2008 3:17 pm
Filed under: Debian, Envy, GNU/Linux, Planet, Python, Ubuntu
Comments (32) |


First of all I would like to thank you all for participating in the contest. I apologise if I didn’t reply to all your emails but I’m receiving so many emails that it’s hard to keep pace with your emails. I’m so busy doing the uploads of your work, coding EnvyNG and living my life (but only in my spare time)… anyway I just wanted to let you know that you ROCK and that I do appreciate all the effort you’re putting into your works.

I have set up a new gallery with all your logos (with thumbnails) so that I don’t have to edit html code every time I receive a new logo. I will only have to upload the new logos and the php scripts which I’m using (LGR Photo) will update the gallery for me.

NOTE: unfortunately the script supports only .jpg.For this reason I had to convert all your works to jpgs therefore the quality of the images in the gallery may be poorer than the one of the originals (which I will use for EnvyNG). If you know a php script with supports pngs and svgs, and which creates albums from folder structure, please let me know.

I would like to make it clear that there’s no rush to create and send me your works since EnvyNG 1.1.x is still under heavy development. EnvyNG 1.0.x won’t include the new GUI and hasn’t been released yet.

Here’s something I managed to do yesterday (despite the fact that I hadn’t slept at all the night before):
EnvyNG Error Dialog QT4

The error dialog (of the QT4 interface) shows what prevented the installation process to end successfully in EnvyNG. You will be able to copy and paste the content of the text browser in dialog (hopefully) without having to send me the full log.

QT4 is great :-)

Of course I’ll do something similar in GTK as well.

Posted by Alberto Milone | February 24, 2008 1:25 pm
Filed under: Debian, Envy, GNU/Linux, Planet, Python, QT, Ubuntu
Comments (1) |


The reactions to the screenshots of the prototypes of EnvyNG 1.1.x were positive however some users (see the comments to my previous posts and this blog post ) led me into thinking that it’s time for me to change EnvyNG’s icon and logo.

I won’t draw a new icon and logo myself though. I wouldn’t define myself as skilled with the GIMP or Inkscape therefore I need your help:

  • If you are a designer (or you can use either the GIMP, Inkscape, etc.) you can send me an icon and logo (you can find my email address on my website) which reflect your idea of what EnvyNG should look like.
  • If you’re not a designer you can post a comment the artwork you think it’s more appropriate.

Requirements for the icons and logos:

  1. They cannot contain trademarked components (e.g. ATI or NVIDIA’s logos).
  2. Their license has to be GPL 2.
  3. The preferred size of the logo is (more or less) 550×133 pixels.
  4. The preferred file formats are “png” or (even better) “svg”.
  5. It would be better if the colours reproduce the look and feel of the old Envy, however you’re free to surprise me in this respect.

For further details you can have a look at the Frequently Asked Questions.

Two Italian users have already sent me their logos. Of course your (polite) feedback on this blog is more than welcome.

Follow this link to participate.

EDIT: the new galley is here

Posted by Alberto Milone | February 22, 2008 1:08 pm
Filed under: Debian, Envy, GNU/Linux, Planet, QT, Ubuntu
Comments (25) |


Features in EnvyNG 1.1.x

  • A new interface in GTK.

      Its code will be cleaner (more readable and sensible). I will use SimpleGladeApp as glatzor (Sebastian Heinlein) suggested a long time ago.
      It won’t waste as much screen space as it used to do (see the screenshot below) as using Envy in 640X480 is not an easy task. It will use tabs and a treeview.
  • A new interface in QT4
      EnvyNG will have an alternative interface written in PyQT4 so that it has a native look on KDE4 and that it doesn’t require GTK dependencies, VTE, etc. It will also use Adept instead of Synaptic.
  • An improved Logger
      The logger of EnvyNG will be improved so that it will be easier for you (and for me) to see what goes wrong in the installation process.
      In GTK I use VTE to show the output of the subprocess which performs the installation, uninstallation, etc. and there’s still room for improvement.
      In QT4 I use a KProcess and insert the output into a QTextEdit widget. I rely only on QT4 (no VTE is required).

  • Save the packages built by EnvyNG to your hard disk
      You will be able to either build, install and save the packages to your hard disk or just build and save without any need to install such packages. For example you might build the packages on a computer which is faster or which has access to a broadband internet connection and install such packages on another computer which lacks these features (in this case you will have to configure your xorg.conf manually).
  • EnvyNG will be split into 3 packages
      envy-core – which contains the program and its textual interface and doesn’t depend on any GUI toolkit so that if, for example, you want to include EnvyNG in your customised distro but don’t have enough space for either the GTK or the QT4 libraries in your livecd, you can include just the textual installer.
      envy-gtk – the GTK interface
      envy-qt – the QT4 interface
      I will set up a PPA repository so that if you do a “sudo apt-get install envy-qt” (or -gtk), envy-core will be installed automatically as a dependency.

    The new GTK interface:

    New GTK interface

    The new QT4 interface:

    QT4 interface

    P.S. In case you’re wondering, I will update the good old Envy soon.

  • Posted by Alberto Milone | February 20, 2008 3:42 pm
    Filed under: Debian, Envy, GNU/Linux, Planet, Python, QT, Ubuntu, Uncategorized
    Comments (9) |


    I have finished writing my thesis (in Latex) and I’ll graduate in March. In the meantime I’m studying PyQT4 and working on Envy.

    I haven’t updated Envy yet as I’ve been working on EnvyNG (”NG” stands for “Next Generation”) i.e. the latest evolution of Envy. EnvyNG will support only Ubuntu Hardy (8.04) or higher while Envy Legacy will still support Ubuntu’s previous releases and Debian (stable).

    The release of EnvyNG which you will see in time for Hardy is 1.0.x. Consider it a transitional release since many new features will be available only in version 1.1.x. Here is a (partial) list of the features in EnvyNG 1.0.x

  • Improved integration with Ubuntu.
      I have worked with a group of Ubuntu developers (to which I’ll give credit when EnvyNG is officially released) in order to prevent Envy from causing troubles when if a user doesn’t do a “envy –uninstall-all” before a dist-upgrade (e.g. from Gutsy to Hardy). Ubuntu’s l-r-m (linux-restricted-modules) and the packages generated by EnvyNG will be able to overwrite each other in a sensible way so that, for example, if Ubuntu’s l-r-m provide the latest NVIDIA driver before EnvyNG does, the former will be perfectly capable of overwriting the packages generated by the latter without causing any problem to the user. Furthermore, thanks to DKMS and also thanks to a patch I wrote for the l-r-m (already applied in Hardy), there will be no need to blacklist Ubuntu’s drivers (in /etc/default/linux-restricted-modules-common). If the packages generated by EnvyNG are installed, they will be automatically loaded at boot.
  • DKMS will automatically build and install the module for your kernel at boot
      In Envy a user had to reinstall the driver every time the kernel was updated. This is no longer the case as DKMS will automatically build and install the module for your kernel at boot (if necessary), provided that your kernel headers are installed.
  • EnvyNG no longer asks you whether you would like to have your xorg.conf configured.

      It does it automatically (during both the installation and the uninstallation processes)
  • The NVIDIA driver *should* work with both realtime kernels (tested) and xen-kernels (untested).

      The same can’t be said about the fglrx driver but I guess this can be fixed later
  • I’ll reveal other details on version 1.0.x soon

    In the meantime you might want to have a look at the list of features in version 1.1.x.

    Posted by Alberto Milone | 3:41 pm
    Filed under: Debian, Envy, GNU/Linux, Planet, Python, QT, Ubuntu
    Comments (14) |