Active Topics
-
Error after installing Leste on sdcard (14)
to Maemo 7 / Leste by t-b - 2 hrs, 28 mins ago -
Maemo 20th Anniversary (4)
to Brainstorm by teroyk - 22 hrs, 39 mins ago -
Nokia Booklet 3G (RX-75) Drivers (64)
to Alternatives by teroyk - 22 hrs, 55 mins ago -
Porting apps to Leste (46)
to Maemo 7 / Leste by teroyk - 3 days, 2 hrs ago -
Maemo repository (8)
to Community by Maemish - 6 days, 20 hrs ago - more...
|
2009-08-03
, 13:14
|
|
Posts: 263 |
Thanked: 679 times |
Joined on Apr 2008
@ Lyon, France
|
#32
|
Many thanks to Tim Samoff and Alan Bruce, who along with myself have proof-read the entirity of the Hildon HIG. I talked to Joaquim at GUADEC, and he had already integrated the changes which were available at that point, I will ping himself and Ivan again to get the more recent changes intgrated and get their feedback on the work that's been done so far.
As an added bonus, we have the entire text of the HIG in the wiki now, so suggestions for improving it, sections that could be added, etc. can be added to Talk pages, please feel free to make suggestions & improvements, and I will make sure that they get rolled upstream once in a while.
The new version of the HIG, complete with our work, will be published soon.
Cheers,
Dave.
As an added bonus, we have the entire text of the HIG in the wiki now, so suggestions for improving it, sections that could be added, etc. can be added to Talk pages, please feel free to make suggestions & improvements, and I will make sure that they get rolled upstream once in a while.
The new version of the HIG, complete with our work, will be published soon.
Cheers,
Dave.
 |
|
2009-08-03
, 15:19
|
|
Posts: 1,605 |
Thanked: 1,601 times |
Joined on Mar 2007
@ Southern California
|
#33
|
Originally Posted by dneary
With screen shots!
...and he had already integrated the changes which were available at that point...
...still needs a little work (I've been busy), but it sure is sweet to see this happen!
Tim
__________________
http://samoff.com
http://samoff.com
Last edited by timsamoff; 2009-08-04 at 03:06.
 |
|
2009-08-04
, 02:05
|
|
Posts: 2,669 |
Thanked: 2,555 times |
Joined on Apr 2007
|
#34
|
Please (Nokia) guys, feel free to bring us more to check/do. A said earlier, we're more than happy to do the work for the community. (Wish I had the time to do what I was going to, but it got done quickly enough anyways.)
| The Following 4 Users Say Thank You to zerojay For This Useful Post: | ||
|
|
2009-08-04
, 08:53
|
|
Posts: 263 |
Thanked: 679 times |
Joined on Apr 2008
@ Lyon, France
|
#35
|
Hi Zerojay,
If there is any document that you're unhappy with, please create a bug, and we will do the same thing again, no problem.
For released docs, this is great, of course. The problem is when we're fixing released documentation which is substantially different from the "private" in-progress documentation, and we don't have an up-to-date version online. That's where I'm working with Nokia to ensure that things are done in a way which allows us to contribute.
Cheers,
Dave.
Originally Posted by zerojay
While this worked well because it was announced, and I did some basic infrastructure for it on the wiki, nothing I did needed special access to anything. I just copied text from a DocBook document over to the wiki, and invited people to contribute, and got the authors to buy into it.
Please (Nokia) guys, feel free to bring us more to check/do. A said earlier, we're more than happy to do the work for the community. (Wish I had the time to do what I was going to, but it got done quickly enough anyways.)
If there is any document that you're unhappy with, please create a bug, and we will do the same thing again, no problem.
For released docs, this is great, of course. The problem is when we're fixing released documentation which is substantially different from the "private" in-progress documentation, and we don't have an up-to-date version online. That's where I'm working with Nokia to ensure that things are done in a way which allows us to contribute.
Cheers,
Dave.
| The Following User Says Thank You to dneary For This Useful Post: | ||
|
|
2009-08-04
, 13:04
|
|
Posts: 2,669 |
Thanked: 2,555 times |
Joined on Apr 2007
|
#36
|
Is there any way we can extend this to the strings used by the default applications as well as localization without needing to wait until a release to file a bug and then hope that maybe the next release a few months down the line will fix it, as has been the case before?
I fully realize that something like Freemantle and the device it runs on will need to stay an internal secret so that you don't give away anything to the competition, but I want to see Freemantle be *everything* it could be. I don't want to notice a thousand little English errors, as small as they might be, all over the operating system. Is there anything we can work out to make this happen?
Last edited by zerojay; 2009-08-04 at 13:12.
I fully realize that something like Freemantle and the device it runs on will need to stay an internal secret so that you don't give away anything to the competition, but I want to see Freemantle be *everything* it could be. I don't want to notice a thousand little English errors, as small as they might be, all over the operating system. Is there anything we can work out to make this happen?
Last edited by zerojay; 2009-08-04 at 13:12.
| The Following 3 Users Say Thank You to zerojay For This Useful Post: | ||
|
|
2009-08-04
, 13:43
|
|
Posts: 263 |
Thanked: 679 times |
Joined on Apr 2008
@ Lyon, France
|
#37
|
Originally Posted by zerojay
The Fremantle betas and alphas were released for that purpose. Most of Fremantle has already been released for review and patches.
Is there any way we can extend this to the strings used by the default applications as well as localization without needing to wait until a release to file a bug and then hope that maybe the next release a few months down the line will fix it, as has been the case before?
I fully realize that something like Freemantle and the device it runs on will need to stay an internal secret so that you don't give away anything to the competition, but I want to see Freemantle be *everything* it could be. I don't want to notice a thousand little English errors, as small as they might be, all over the operating system. Is there anything we can work out to make this happen?
Have you installed a beta image and had a look around, by any chance?
Thanks,
Dave.
|
|
2009-08-04
, 13:47
|
|
Posts: 1,605 |
Thanked: 1,601 times |
Joined on Mar 2007
@ Southern California
|
#38
|
Originally Posted by zerojay
Hey, I was talking to X-Fade about this a while back. We were thinking that the new package management interface would be a good way to do this. Basically, you find an app and leave a comment to what you would like to see changed (description strings, localization notes, etc.). These comments go directly to the package maintainer, so hopefully they'll act on suggestions.
Is there any way we can extend this to the strings used by the default applications as well as localization without needing to wait until a release to file a bug and then hope that maybe the next release a few months down the line will fix it, as has been the case before?
I fully realize that something like Freemantle and the device it runs on will need to stay an internal secret so that you don't give away anything to the competition, but I want to see Freemantle be *everything* it could be. I don't want to notice a thousand little English errors, as small as they might be, all over the operating system. Is there anything we can work out to make this happen?
Initially, I was wondering if Bugzilla would be better for this, but keeping all of the suggestions/notes attached to the packages in the management interface works just as well.
Does that make sense?
Tim
__________________
http://samoff.com
http://samoff.com
|
|
2009-08-04
, 13:55
|
|
Posts: 2,669 |
Thanked: 2,555 times |
Joined on Apr 2007
|
#39
|
Originally Posted by dneary
I don't use Debian but another flavor of Linux (ArchLinux), so installing/running the SDK ends up being *far* from trivial, but I tried. Also from my previous experience, the SDK lacks a *ton* of default apps, so a lot of this checking can't even be done anyways, though I hope that's not the case with the Freemantle SDK.
The Fremantle betas and alphas were released for that purpose. Most of Fremantle has already been released for review and patches.
Have you installed a beta image and had a look around, by any chance?
Thanks,
Dave.
Bugzilla's good for leaving changes we'd like to see since it supports attaching patches and so on... Tim, I guess it depends on whether or not application developers want to have *another* place to check for fixes, bugs, etc...
Last edited by zerojay; 2009-08-04 at 13:58.
| The Following User Says Thank You to zerojay For This Useful Post: | ||
|
|
2009-08-04
, 14:12
|
|
Posts: 1,605 |
Thanked: 1,601 times |
Joined on Mar 2007
@ Southern California
|
#40
|
Originally Posted by zerojay
Except that these things aren't exactly application "bugs," but rather subjective (mostly), human "bugs." So... For now, I say that we should use it and see what happens.
Tim, I guess it depends on whether or not application developers want to have *another* place to check for fixes, bugs, etc...
Tim
__________________
http://samoff.com
http://samoff.com
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!