WordPress.org

Make WordPress Mobile

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Eric 4:58 pm on October 21, 2013 Permalink | Log in to leave a Comment
    Tags: , , firefox os, , , ,   

    Weekly dev chat summary for Oct 21, 2013 

    Chat log

    Agenda:

    • Android Status
    • iOS Status
    • GSoC Projects
    • Handbook
    • This week

    Android Status

    • 2.5: A handful of issues were found during QA and the team has been working on fixes. There are currently two left. Once these are sorted the QA cycle will restart.
    • Development for the next release (2.6) with an improved welcome/signup flow and Native Reader is finished and ready for testing.

    iOS Status

    • Last week was a good bug fixing sprint and 3.8.4 is almost ready and we’ll be starting testing soon.
    • 3.8.3 status – crashes are way down and reviews are improving a bit. Still seeing some login issues that need to be worked on but the majority of the issues still being reported are fixed in 3.8.4.

    GSoC Projects

    • The code for the GSoC BlackBerry and Firefox OS WordPress apps has been added to the WordPress-Mobile github repos. There is more work to do on both apps before they are ready for a v 1.0 release.

    Handbook

    • Missing iOS parts are still a WIP.
    • New release schedule page is just about ready.
    • Versluis expressed his interest in helping out with the handbook.

    This week

    • iOS : finish 3.8.4, testing and submit!
    • Android: fix remaining issues with 2.5 an another round of QA. Go after some quick wins on github tickets and other ui improvements.

    Next Dev Chat

    Join us next week on Monday Oct 28 at 16:00 UTC in #wordpress-mobile on Freenode.

     

    • Jay Versluis 5:19 pm on October 21, 2013 Permalink | Log in to Reply

      Inspired by our chat I’ve just added a couple of additions to the following handbook entries:

      What’s the policy on screenshots in the handbook? I’m happy to provide some to illustrate further points, but currently there’s no media upload button showing for me.

      • Eric 6:55 pm on October 21, 2013 Permalink | Log in to Reply

        Nice additions. :) Its pretty awesome that you dove right in.
        I have two small suggestions:

        • Tools & Requirements: It might be nice to let “Getting the Code” be the main heading and have “Command Line” and “Xcode 5″ be subheadings.
        • Tutorials & Guides: Instead of saying “Replace any spaces in the full path with something else” it would be better to be specific as to what that something else should be.

        Screen shots would be great to have. I’m not sure why you wouldn’t be seeing a media upload button unless it was something related to your user role on the make blog. Are you editing from the wp-admin or from the page itself?

        • Jay Versluis 10:44 pm on October 21, 2013 Permalink | Log in to Reply

          Thanks Eric! I remember those areas were throwing me when I first tried to build WordPress. Totally agree with those changes, I’ve amended the headings and tried my best to re-word the space replacement.

          Re: media uploads – I’ve tried both the inline edit button, as well as wp-admin, both links get me to the admin interface, but no luck on the upload button either way.

    • Jay Versluis 6:02 pm on October 21, 2013 Permalink | Log in to Reply

      I’ve also fleshed out this page about testing and reporting issues:

  • Aaron Douglas 12:59 pm on October 21, 2013 Permalink | Log in to leave a Comment
    Tags:   

    Logging changes in WordPress for iOS 

    One of the things we’ve added to WordPress for iOS in the upcoming 3.8.4 release is a better way to handle feedback from users of the app.  We’ve added CocoaLumberjack to the project to replace our previous method of using FileLogger and three macros throughout the project to log.  There were some limitations with that approach, primarily being no way to easily set the verboseness of the logging.  Turning on “extra debug” involved setting a NSUserDefaults flag that was checked (inconsistently) across the app.  CocoaLumberjack supports multiple (and custom) logging levels to allow for us to turn up and down the amount of logging in the app.

    The three logging macros we defined (WPLog, WPLogMethod, WPLogMethodParam) are still available but they have been moved to WordPress_Prefix.pch.  Instead of using these three methods use one of the pre-defined CocoaLumberjack logging macros:

    DDLogError();
    DDLogWarn();
    DDLogInfo();
    DDLogVerbose();

    In WordPress_Prefix.pch we define the default logging level variable ddLogLevel. In WordPressAppDelegate.m the value is defined as LOG_LEVEL_INFO. What this means is any logging that is under INFO (Verbose) will be excluded from the log file and console. Turning on “extra debug” will flip that logging level to VERBOSE – this is done in both the app delegate and the settings screen during runtime.

    Log files are now kept beyond a single crash as well. CocoaLumberjack will keep up to seven log files, rolling a log file over after the calendar day has passed. Users can explore the contents of the logs through Settings -> Support.

     

  • Jorge Bernal 11:18 am on October 17, 2013 Permalink | Log in to leave a Comment
    Tags:   

    I just went through the latest reviews 1… 

    I just went through the latest reviews (1 to 3 stars) and forum posts and, while the sample is small, here are the top issues detected:

    1. Wrong Credentials/Can’t login
    2. Self hosted issues
    3. HTTP Auth
    4. External keyboard issues
    5. Visual editor
    6. 2 step auth (I think many people don’t know about app specific passwords, some credential issues might actually be 2-step related)
    7. Old posts in app after draft update
    8. Duplicate reader items

    Some of those (specially the 2 first) are usually quite vague and why having a direct contact will be great.

    I haven’t included stuff that it’s already fixed on 3.8.3. I’ve included HTTP Auth even though it’s fixed on develop to highlight that it’s something we need to test better.

    So, highest priority items for 3.8.4:

    • #212 – In-app feedback. @astralbodies let me know if you could use some help in there. I liked @twitkin suggestion on the initial mockups of just adding a ‘Need help?’ link at the bottom of the login screen. Can @twitkin or @hugobaeta review the UI flow from can’t add site to contact us?
    • #268 – Clean up logging. Our logs are a mess and not very helpful most of the times. Since the feedback option should include logs when errors happen, make sure those are actually helpful.

    When those two are ready to go, we’ll freeze .4 with whatever other improvements we have. With feedback from users we should be able to fix everything on the list for 3.8.5 (except the visual editor :( ).

    Other high priority things according to the list.

    I’ve ruthlessly moved everything else to 3.8.5, and added a must-have label to indicate blockers for release

     

    • Aaron Douglas 5:14 pm on October 17, 2013 Permalink | Log in to Reply

      I’m working on both #212 & #268 right now. @twitkin is helping me with reviewing the UX of the feedback screen(s). I’ll keep feedback in its own branch unless you want it merged into develop sooner?

  • Isaac Keyet 4:47 pm on October 14, 2013 Permalink | Log in to leave a Comment
    Tags: , , ,   

    Weekly dev chat summary for Oct 14, 2013 

    Chat log.

    Agenda

    • New release cycles/testing processes
    • Android Status
    • iOS Status
    • This Week
    • Handbook

    New release cycles/testing processes

    When we started talking about the status of the Android project, the new release cycle with a more rigid testing process came up. This is what we’ll be doing for all releases across platforms moving forward:

    • Group decides on dev time needed for a project.
    • Towards the end of the dev cycle the update goes through automatic and manual testing.
    • All developers in the Mobile Group will have to test the app and give their thumbs up.
    • Once approved by the Mobile Group, a RC is put out which marks the start of the Code Freeze. This is the build that will be submitted unless a super critical bug is found. Code Freeze is 1 week minimum.
    • If there’s a critical bug that has to be fixed before submit, the whole testing process is restarted.

    Android Status

    Version 2.5 (Themes, Media, Stats, Pin Lock, etc) is in QA testing this week. This is happening in Master but in the future it’ll be Develop all the way. Reader/NUX is next up but we want to make sure we put aside enough time to have a stable release.

    iOS Status

    To make sure we have stable releases (including bug fix releases) version 3.8.3 of the app is currently in testing. If nothing critical comes up we’ll be able to release the update as-is. This should fix even more issues introduced in version 3.8. Next up is 3.8.4 which goes even further.

    This Week

    • Android: testing v. 2.5
    • iOS: testing v. 3.8.3, planning next releases
    • Update iOS section of Handbook

    Handbook

    There are still some gaps in the handbook that we’re hoping to fill.

    @sendhil promised to take a look at the remaining bits in the iOS section this week, and @isaackeyet will summarize the new release/testing cycle, so let’s follow up on it in the next dev chat.

    Next Dev Chat

    Join us next week on Monday Oct 21 at 16:00 UTC in #wordpress-mobile on Freenode.

     

  • Eric 11:38 am on October 14, 2013 Permalink | Log in to leave a Comment
    Tags:   

    Here is a nice article from a user of the WPiOS app and some suggestions (and wireframes!) based on his experience using the app while traveling. ( Hat tip @karim for the link. ) A lot of his feedback revolves around a better offline experience, especially where media is concerned. Thoughts?

     

    • Eric 2:55 pm on October 14, 2013 Permalink | Log in to Reply

      In another thread @koke mentinoed:

      Making media work offline makes so much sense, but if it’s not uploaded, how is it represented? We’d need to include images in a visual way, then generate the correct HTML after upload. We could start by making quick photo work offline though.

      I can dig it. For the visual editor it wouldn’t be a problem to show a saved image that has not yet been uploaded but I’m not sure what the best way would be to represent it in an HTML view (assuming the visual editor also has an html mode). Maybe its the normal markup but a URL with a custom protocol and we swap it out when the media is actually uploaded. Its definitely something we can play around with.

  • Eric 4:57 pm on October 7, 2013 Permalink | Log in to leave a Comment
    Tags: , ,   

    Weekly dev chat summary for Oct 7, 2013 

    Chat log.

    Agenda

    • WPiOS Status
    • WPAndroid Status
    • This Week
    • Next Dev Chat

    WPiOS Status

    Currently focused on addressing some lingering bugs stemming from earlier changes to support iOS 7. The team will be doing a lot of testing before submitting 3.8.3 to Apple later this week.

    WPAndroid Status

    The team has decided to have another beta round after addressing a bug related to sharing and the new pin lock feature. The beta should last a few days, then we’ll submit the app to the Play store, probably on Wed the 9th.

    For this release we’re trying something new. We’ll take advantage of Google Play’s percentage distribution to release the app to around 10% of our user base, and monitor its reception. If all goes well we’ll open the floodgates and make the app available to everyone.

    This Week

    • iOS : Focus on bug fixes and testing. Submit 3.8.3 to Apple.
    • Android: Monitor the new beta and release 2.5 to Google Play later this week.

    Next Dev Chat

    Join us for the next dev chat on Oct 14, 2013 at 16:00 UTC. Mark your calendar and join us in #wordpress-mobile on Freenode.

     

    • Dan 9:13 pm on October 8, 2013 Permalink | Log in to Reply

      Android update: All release dates are going to be pushed out by approximately one week so that we can do a full code freeze/QA pass to make sure everything is solid.

  • rachel_mccollin 2:55 pm on October 1, 2013 Permalink | Log in to leave a Comment
    Tags:   

    Mobile Handbook – Further Editing update 

    Hi everyone,

    I’ve been into the handbook today and looked at what’s been done over the past couple of weeks.

    The Blackberry section is now complete – thanks Danilo!

    There is still work to do on other sections though. Please see my post http://make.wordpress.org/mobile/2013/09/17/ive-now-worked-through-all-sections-of-the/ for details.

    Thanks :)

     

  • Isaac Keyet 2:00 am on October 1, 2013 Permalink | Log in to leave a Comment
    Tags: , featured images,   

    Weekly dev chat summary for Sep 30, 2013 

    We didn’t follow the usual pattern for the dev chat this week since the majority of the contributors couldn’t make it, and instead opened it up to potential new contributors. — Chat log.

    Featured Images discussion

    @lonchbox (Pancho Perez) joined us to chat about some ideas he’s had for a better iOS app experience, in particular setting Featured Images.

    The discussion was mainly around the placement of the feature and how important it is to editors when using a theme that supports it. We went over the reasons as to why it’s in the Settings tab currently but ultimately agreed that there may be a better home for it somewhere more prominent in the main post editor. Wether this be a button in the tab bar, a graphic overlaying the post, or something exciting like a parallax top header we’re not sure of. Do check out Pancho’s post as it brings up some interesting concepts. @hugobaeta later tweeted and it looks like we’ll be looking at solutions when outlining the visual editor project.

    We’ll circle back to the status of the apps next week. Join us in #wordpress-mobile at 16:00 UTC on Monday, October 7!

     

    • Jay Versluis 4:19 pm on October 5, 2013 Permalink | Log in to Reply

      Isaac,

      I’ve missed the meeting, but I’ll be there on Monday. I’m still interested in fixing this bug: https://github.com/wordpress-mobile/WordPress-iOS/issues/106 – but the project is big, and I have many questions. Is it OK to bring those up in the next meeting, or is there a better place to ask?

      Also, where is the current development version, GitHub or SVN? SVN doesn’t have tags for the current version (3.7+) – just want to make sure I’m not working on an outdated copy.

      • Isaac Keyet 8:45 am on October 6, 2013 Permalink | Log in to Reply

        You want to work in the Develop branch on GitHub, SVN is likely out of date.

        Feel free to ask away here or ping one of the iOS devs in #wordpress-mobile at any time (although most may be out for the weekend).

  • b0unc3 6:52 pm on September 26, 2013 Permalink | Log in to leave a Comment
    Tags: ,   

    GSoC – week 15: All done. 

    Here we are, I’ve completed my project and submitted all the stuff to the GsoC for the final evaluation. Now I don’t want to bother you with more word, let’s go to the serious thing :)

    Here is a short demo of the app running on my BlackBerry Z10 (sorry for the poor quality!):
    http://www.youtube.com/watch?v=89L8kQjCCQo

    The project sources code are on the official SVN repo here :
    http://gsoc.svn.wordpress.org/2013/b0unc3/trunk/

    There is also a GIT repo, here :
    https://github.com/b0unc3/WordPress-bb10

    For whom feel brave enough, but not enough to compile and run the code :) , a .bar beta package is present in all the repos in a “beta/” directory it contains the latest version installable on your devices.
    You can install it with the blackberry-delpoy command line tool, or by sideloading it (google will help you with it ;) )

    svn : http://gsoc.svn.wordpress.org/2013/b0unc3/trunk/beta/wp_bb10-1_0_0_1.bar
    git: https://github.com/b0unc3/WordPress-bb10/blob/master/beta/wp_bb10-1_0_0_1.bar

    That’s all! I hope you find comfortable with it. If you have any suggestions/critics/feedback/whatever, please, feel free to contact me directly.

    I want to give a special big thanks to the WordPress community and GsoC program, I found this experience amazing and I learned a lot!
    Thanks!

    Best Regards,
    Daniele Maio.

     

    • heredia21 2:32 am on September 27, 2013 Permalink | Log in to Reply

      Looks good! Plan on adding any editing buttons? Such as insert more tag, link etc?

    • Zamal974 10:12 am on September 29, 2013 Permalink | Log in to Reply

      Good News !!
      Damage ! It doesn’t work on Q10 and Z30

      • b0unc3 6:19 pm on September 30, 2013 Permalink | Log in to Reply

        I don’t have a Q10 neither a Z30 :(
        Can you please report which OS version are you running and which is the actual outcome.
        Thanks.

        • daniloercoli 11:03 pm on September 30, 2013 Permalink | Log in to Reply

          Did you try to setup the device simulator as a Q10, or Z30?

        • LoganSix 3:09 pm on October 1, 2013 Permalink | Log in to Reply

          In the application or another c++ class, you can do this to get the screen size. Then in the qml, just call these functions to resize.

          int ApplicationUI::screenWidth()
          {
          bb::device::DisplayInfo display;
          return display.pixelSize().width();
          }

          int ApplicationUI::screenHeight()
          {
          bb::device::DisplayInfo display;
          return display.pixelSize().height();
          }

          Q10 is option 2 on the simulator. Z30 is option 3.

    • heredia21 10:26 pm on October 1, 2013 Permalink | Log in to Reply

      Adding the ability to place a post in a certain category, add tags, etc.?

  • Sayak Sarkar 11:17 pm on September 25, 2013 Permalink | Log in to leave a Comment
    Tags:   

    GSoC – Week 15: When everything's complete and done! 

    This is the final week of Google Summer of Code 2013, all the submissions have already been made and the final evaluations are well on their way. So, this is my last GSoC 2013 update and I plan to use this post to display the final result of what I’ve been able to achieve this summer.

    Here are a few screenshots of the app that I’ve taken using the Geeksphone Keon developer device for Firefox OS, which roughly cover the primary features of the app:-

    WordPress for Firefox OS - Login Screen WordPress for Firefox OS - Posts List VIew WordPress for Firefox OS - New Post WordPress for Firefox OS - Successful Post Notification WordPress for Firefox OS - Post Draft View WordPress for Firefox OS - Sliding Menu Drawer WordPress for Firefox OS - Pages List View WordPress for Firefox OS - New Page Screen WordPress for Firefox OS - Page Published Notification WordPress for Firefox OS- View Site Mode

    At the end of the summer, I would like to state that I’m actually quite satisfied and happy with the way the app has turned out to be so far, given the time-limited scope of GSoC. However, I would like to continue work on the app beyond the GSoC timeline and see to it that the app goes forward towards a matured v1.0 release sometime in the near future.

    I would also like to express my heartfelt gratitude and thanks towards @aerych, who has been my mentor for this project. He has been an exceptionally good guide for me throughout the summer and always helped me whenever I’ve faced challenges or felt stuck during the coding period. Also, I would like to express my thanks to the WordPress and Google Summer of Code project coordinators for giving me the opportunity to work on developing the WordPress app for Firefox OS. Thanks a lot to everyone! :-)

     

← Older posts

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel