Re: how to enable file extensions
 

I downloaded a VM, installed maemo5 SDK and built the package with that change:
http://www.scratchpost.org/software/...0/File_Dialog/

(The Build VM has 3.6 GB, so I'm not hosting it...)

You only need to install the "libhildonfm2_2.28.18+0m5_armel.deb" on the device. Since the version number and stuff is the same, you have to force it with:

dpkg -i libhildonfm2_2.28.18+0m5_armel.deb

Now I really need sleep ;-)

Re: how to enable file extensions
 

Heyup Danny.
wow if this works ok, how can you get a better example of the benefits of the opensource approach to provide by far an exceptional customer facing experience.

This far exceeds anything the closed source community can even dream of achieving.

Certainly gets my thanks.

rgds

Re: how to enable file extensions
 

Has anyone tested this yet?

If not then Dannym any chance you can let me know how to revert once installed and I will try on my phone.

rgds

Re: how to enable file extensions
 

hi,

I rebuilt libhildonfm2 with extensions and rearranged the audio file display to be

filename
artist / song

instead of the current

artist
song

Also renamed the package to libhildonfm2-community, so it won't try to update mp-fremantle-generic-pr. It still breaks ssu, but I made preinst and postrm scripts that take a backup of the original lib file when installing and restores it after removal.

You can't install this from HAM since it pokes at a file belonging to mp-fremantle-generic-pr, but you can dpkg -i it without having to force-overwrite.

I might be putting this in extras-devel later, but here's the file for those brave enough to try it. Demands a reboot, and then you have to wait a while for something to be done, not sure what, because it crashes or reboots the phone if you launch it too soon after the first reboot. After it's done everything seems stable though.

anway, here:
http://www.hedwerks.net/stuff/libhil...emo5_armel.deb

Re: how to enable file extensions
 

I second that.

It is unbelievable how easy it would be for official developers to implement that, but they won't because the official position is that it is better to imitate the default MS Windows (flawed, in my opinion) way of hiding everything from the users. They could at least have left an option buried down some menu to change that default behavior (just like MS Windows does, for example).

Now, what the community has shown is the essence of free software. The freedom to change things and to give it back to the community.

I only wish that Nokia would make even official packages easier to accept patches and deploy them to everybody, without waiting for a full firmware upgrade.

Re: how to enable file extensions
 

The original package is at:
http://repository.maemo.org/pool/fre...h/libhildonfm/

Keep it ready.

Or just reflash the phone if something goes wrong (you have backups, right? :-) )
http://wiki.maemo.org/Updating_the_tablet_firmware

We are changing system parts, so please have backups.

Re: how to enable file extensions
 

Hi Danny

backups?

:-)

Tested this and it does improve things a bit on my version (203uk).

success
filemanager, display extensions ... woot
microb, bookmarks end in .bm ... woot

not there yet
filemanager, rename dialogue, no extensions
microb, save as dialogue, no extensions

note
dpkg -i ... stated downgrading my version.

so really good start, I don't suppose you could point me to what i need to download/compile instructions, I might be tempted to play.

rgds

Re: how to enable file extensions
 

Hi uTMY,

good to know that it works somewhat.

What is it about the microb save dialog? I thought that would work as well. Is it a special (non-standard) save dialog?

Hmm, no idea where the rename dialog code is...

As for setting up the build environment, you should have a Linux system (if you don't, set one up in a VM).

Then, see http://wiki.maemo.org/Documentation/...l_Installation

In short, download
http://repository.maemo.org/stable/5...install_5.0.sh
and chmod +x maemo-scratchbox-install_5.0.sh
and (as root user) ./maemo-scratchbox-install_5.0.sh -u <username>

That will download hundreds of megabytes, so patience... :-)

Note that this will install into directory /scratchbox/, so if you don't have enough space there, create a symbolic link named like that that points to some empty directory on a volume where you do have enough space (or a bind mount or whatever).

Then do /scratchbox/login as a normal user (NOT root).

This should give you an environment where you can build Maemo packages as you would in a regular Debian GNU/Linux distribution.

(Or instead get this VM which has everything preinstalled, INCLUDING Maemo SDK (and I didn't try that out yet): http://maemovmware.garage.maemo.org/2nd_edition/ )

In any case:

Switch to the ARM CPU target using:
sb-conf select FREMANTLE_ARMEL
(or something like that). It will remember that choice.

Edit the file /etc/resolv.conf to list your Domain Name Server.
Check that the package source file /etc/apt/sources.list is correct (i.e. lists fremantle).
Call apt-get update to update the package list.
To fetch a source package, first create an empty directory, cd into it, then call apt-get source <package>. In this case, that would be: apt-get source libhildonfm

That will create another subdirectory (you need that extra directory level since the finished packages will go into ".." usually). cd into it.

There, change whatever you want to change (you don't have to do that from within scratchbox, the same stuff is available in the main system under /scratchbox/users/<user>/home/<user>/).
Note that you are supposed to add a line at the top of debian/changelog with your name and E-Mail address and a (user-readable) description of what you changed and the new version number it's supposed to have.

Then call dpkg-buildpackage -rfakeroot

The first time you do that, it will nag about all the build dependencies it needs. So off you go doing:
fakeroot apt-get install <package-1> <package-2> <package-3>
That will fetch a few more hundreds of MB.
After the dependencies are there, try again.

In ".." you'll find the final .deb files of the package you changed (and other files you can use to automate building on the Maemo build servers).

Feel free to ask me if you have questions.

Re: how to enable file extensions
 

Nope. HildonFileChooserDialog with GTK_FILE_CHOOSER_ACTION_SAVE being passed to it as its GtkFileChooserAction argument.

However, gtk_file_chooser_set_current_name is being called, so it may be MicroB itself setting the name w/out the extension. Dunno, really.

Re: how to enable file extensions
 

heyup
small side effect.
cause file is back revved from maemo pr1.2 ota prompts to update specific file.
rgds