This problem with the install is serious. Can you send more info? We tested a lot with the new firmware and it was ok in our tests.
Can you send us your repository list? and the actions you are taking ( or just clicking on the install button on the website)
We will try to replicate and solve the bug if it's on our side, or help you solve if it's because of other conflicting repositories etc.
Br
Marcelo
Well, I've got everything I had before in the app catalog, the only "new" thing is the RTCOMM beta repository and the new MicroB browser.
Let me try installing it again so I can tell you EXACTLY what the problem is from the log.
@rhouge :
The keyboard was a first experiment by gustavo, to measure how well could we do with a non-full screen keyboard but keeping it usable with fingers. We like the results a lot, and already have a track to improve it even more with some of the apple's trick (autocompletion using some dictionaries / simple error connection with the same dictionary, trying to build the visual paths to fix the typos)
What we know is that the keyboard from maemo now has a nice api that we can actually use, so we can try to provide a alternative keyboard also outside of Canola, for those users who like the keyboard but not the canola itself or simply don't need it.
The good thing is that most of it is a edje (ui) script. So it took just a couple of more days because gustavo was bug fixing the platform first. This shows a lot of potential for a more intelligent keyboard, that is what we need for removing the canola configuration from the web based thing =)
@rhouge :
The keyboard was a first experiment by gustavo, to measure how well could we do with a non-full screen keyboard but keeping it usable with fingers. We like the results a lot, and already have a track to improve it even more with some of the apple's trick (autocompletion using some dictionaries / simple error connection with the same dictionary, trying to build the visual paths to fix the typos)
What we know is that the keyboard from maemo now has a nice api that we can actually use, so we can try to provide a alternative keyboard also outside of Canola, for those users who like the keyboard but not the canola itself or simply don't need it.
The good thing is that most of it is a edje (ui) script. So it took just a couple of more days because gustavo was bug fixing the platform first. This shows a lot of potential for a more intelligent keyboard, that is what we need for removing the canola configuration from the web based thing =)
BR
Marcelo
Fexo, muito bom. If you need any testing done let me know, I would love to get my hands on that. I really have some issues with the stock keyboard, especially with chat clients like skype and gaim.
@rhouge That's nice to hear. I will for sure let you enter the beta test phase then. If you could describe me the problems with the stock keyboard, would be very nice.
Example : I hate the way there's a return and a backspace near with different size and that you have a giant (hide the keyboard).
This problem with the install is serious. Can you send more info? We tested a lot with the new firmware and it was ok in our tests.
Can you send us your repository list? and the actions you are taking ( or just clicking on the install button on the website)
We will try to replicate and solve the bug if it's on our side, or help you solve if it's because of other conflicting repositories etc.
Br
Marcelo
Figured out what the issue was: vpnc installed a version of libgpg that wasn't compatible. Removed it and the libs and Canola installed on the new OS just fine.
@rhouge That's nice to hear. I will for sure let you enter the beta test phase then. If you could describe me the problems with the stock keyboard, would be very nice.
ExaExample : I hate the way there's a return and a backspace near with
different size and that you have a giant (hide the keyboard).
Mainly i don't appreciate the full screen kb taking up all of the screen real estate while in a chat window so you can only see your own post as you're typing and none of the previous posts. This forces the user to keep switching views between kb and chat window.
Actually the contextual interface ( car - home - work) was our goal since the beginning, but was quite hard to convince the managers with what we had at the time, and I was the only in the ui work, taking not only canola but all indt's project. Now with a slightly bigger team we are able to produce a lot more, experiment a lot more and propose!
Contextual interface is definitely an interesting idea.
How about linking automatic switching of contexts to GeoClue? That way Canola could automatically switch to "home" profile when I come home, and to the "work" profile when I'm at work.
I was thinking along similar lines myself. It would be neat IMO to wrap device profiles around network access providers, so that the user could customize the device to his environment(s) and be greeted with that contextual profile automatically when changing environments. I have 2 main areas of use, work and home, and use the device differently in both. The differences could easily be tied to the wifi provider configuration.
