archive-org.com » ORG » M » MERPROJECT.ORG

Total: 820

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Nemo/Glacier - Mer Wiki
    needs polishing locusf UI components Buttons Done Done faenil ButtonRow Done looks wise not yet 100 to specs Design qwazix QML locusf anyone feel free to polish it Header Done Done faenil ListView Done need pull to refresh Nothing Yet Design Morpog Progress Spinner Done Done needs polishing SfietKonstantin ContextRoller It s a broad topic Nothing Yet Brainstorm qwazix Morpog SelectRoller Drafted Pre history Nothing Yet Design qwazix Sliders Done trumpet is there by locusf not yet 100 up to specs sledges locusf SfietKonstantin anyone feel free to polish it Switch Done Done NEMO 710 and animation gradient twitch to be fixed Design Morpog qwazix QML locusf Text Input Done Done locusf Labels Unspecified trivial Mostly done except NEMO 711 QML faenil locusf Dialogs Done Query dialogs are done in git Design sandy locke QML locusf Notifications Blog Row 2 col 4 One more Done Design Hurrian QML locusf Tabs Done Not yet Design qwazix Toolbar Done QML Component provided faenil Tools toolbar with different layouts Done Done faenil Section scroller Done Nothing Yet Design Morpog Sheets Nothing Yet maybe with Text Fields Nothing Yet Page Done Done faenil Progress Bar Done Done sledges Running Indicator Some tests by qwazix nothing in repo Nothing Yet Page Indicators Discuss relevancy see faenil s Page implementation Ratings Nothing Yet Nothing Yet More indicator Need a case by case study Nothing Yet Date Lists tumbler dialog picker Row 3 col 3 vs circular here and here Nothing Yet Design Hurrian Lockscreen Row 1 col 2 Sharpening glass PoC Hurrian Morpog qwazix sledges Notification Screen Row 2 col 1 Nothing Yet Design Hurrian Multi task Screen Row 2 col 3 Nothing Yet Statusbar Done 1 WIP in Glacier homescreen Design Hurrian Spec sandy locke QML locusf Core applications Draft Not started Maliit VKB Needs

    Original URL path: https://wiki.merproject.org/wiki/Nemo/Glacier (2016-02-01)
    Open archived version from archive


  • Nemo/Qt5PortingCoreApps - Mer Wiki
    rpm file file rpm to install the package you just created Start the app by tapping on its icon in the VM you may have problems trying to run it directly from SSH and check that the app is working as expected If you re annoyed by the lack of theme graphics no toolbars etc perform this hack full solution underway zypper in meegotouch theme darko zypper ar http repo merproject org obs home sledge branches nemo devel nemo devel mw latest i486 qt comp zypper dup from qt comp Once you have finished your Qt5 port create a Pull Request on github and wait for a reviewer to review your code This is all thank you very much for contributing Status of Qt5 core apps ports This is the current status of the Qt5 ports of Nemomobile core apps Please come join us Checkout the qmlcalc Repo link to see what a Qt5 port usually consists of Package name Current status Assigned to Repository URL qmlcalc Done faenil https github com nemomobile qmlcalc pull 11 voicecall ui reference Dialer Done faenil https github com nemomobile voicecall ui reference pull 2 qmlnotes Done faenil https github com nemomobile qmlnotes pull 1 qmlcalendar Done sledgeSim https github com nemomobile qmlcalendar pull 6 fingerterm Done also added orientation modes special faenil https github com nemomobile fingerterm pull 4 https github com nemomobile fingerterm pull 5 qmlmessages Done timoha from Nomovok https github com nemomobile qmlmessages pull 7 qmlpackagemanager Done niqt timoha https github com nemomobile qmlpackagemanager git qmlmaps Done locusf Qt location requires API keys https github com nemomobile qmlmaps qmlpinquery Done sledgeSim https github com nemomobile qmlpinquery pull 6 qmlmusicplayer Done locusf https github com nemomobile qmlmusicplayer pull 3 qmlfilemuncher Done locusf https github com nemomobile qmlfilemuncher qmlcontacts Done timoha from

    Original URL path: https://wiki.merproject.org/wiki/Nemo/Qt5PortingCoreApps (2016-02-01)
    Open archived version from archive

  • Nemo/Development - Mer Wiki
    Longer messages Contributes to MER 123 Or if the change actually closes fixes some bug text Longer message Fixes MER 123 Example commit 1efda9cf6a950509b26b69c599fbdc89f70104ae Author Captain Nemo captain nemomobile org Date Fri Apr 26 15 21 34 2013 0300 This is a sample commit message that contains two entries that are picked to the changes file packaging Fixed issues with packaging binary x fix crash when binary x is called with param y Signed off by Captain Nemo captain nemomobile org it is added automatically to the next changelog entry when new version is tagged NOTE Also should be noted that there MUST be at least one commit between each tag that contains a line shown above so that the changelog will be generated properly Here is example how the lines above would correspond in changes file If tag 0 1 would point to commit 1efda9cf6a950509b26b69c599fbdc89f70104ae above Fri Apr 26 2013 Captain Nemo captain nemomobile org 0 1 packaging Fixed issues with packaging binary x fix crash when binary x is called with param y NOTE If you have existing changelog that isn t already in proper format i e git tags and commit messages you need to add the old changes file to the rpm directory This changes file will be is used as a base of the changelog generation and automated changelogs are appended to that Should be noted that this changes file MUST NOT be updated after adding it to the git tree NOTE If you start from scratch with new package and you start following the changelog convention of tar git no changes file should be added to the rpm directory Tagging Tags with tar git should always be version number that was tagged For example 0 1 1 2 4 There is also possibility to add prefix if one wants to sort tags or if you have multiple branches from which packages are build and you want to separate those with names prefix 0 1 When ever you do tag on the branch enabled with the webhook it will automatically launch the tar git service and the new sources will be downloaded and built on the target project Please refer to the tagging format at https wiki merproject org wiki Nemo Development Releasing Logs Process To follow the behaviour of your webhooks you can join to mer boss IRC channel Freenode Here is couple of examples of those messages Merbot Tag s by Developer X in master branch of https github com nemomobile nemo qml plugins git which will trigger build in project nemo devel mw package nemo qml plugins https build merproject org package show package nemo qml plugins project nemo devel mw Merbot 1 commit s pushed by Developer Y to master branch of https github com tswindell telepathy ring git If you tagged a package you can click the link and check that everything is ok Using submodules with tar git When handling upstream packages where one can t use the changlog

    Original URL path: https://wiki.merproject.org/wiki/Nemo/Development (2016-02-01)
    Open archived version from archive

  • Nemo/GettingStartedInFixingBugs - Mer Wiki
    remaining steps and steps in the next section Once the fix works commit your fix to your local branch create patch with git format patch Submit the patch upstream Nemo contains software from a variety of sources so there isn t always a clear guideline for how to do this but generally speaking For anything we maintain generally speaking anything on https github com nemomobile please submit a pull request on github The right people should get a mail notification automatically but feel free to ping us in nemomobile too For software from Maemo or MeeGo or other sources where there may not be an active upstream please ask in nemomobile to get a repository created in the nemomobile project on github For anything else please follow upstream proceedures If you can t find them please ping in nemomobile and we ll try help you out If you re unsure or need help please just ask Building package with the patch in OBS Please note that you don t need to patch packages that we maintain see github Instead we should be making releases of those packages Generally the maintainer s of the packages will take care of this in a reasonable amount of time after your patch is merged but please ping someone on nemomobile if this process takes too long TODO write a page on release guidelines Log into community OBS Search for the package needing the fix Branch the package Go to your computers command line Check out your branched package with osc A https api merproject org co your branched project package name Change into dir that was checked out above Copy the patch to working dir Add the patch to package s source files with osc add patch Add the patch in yaml file in

    Original URL path: https://wiki.merproject.org/wiki/Nemo/GettingStartedInFixingBugs (2016-02-01)
    Open archived version from archive

  • Nemo/Debugging - Mer Wiki
    zypper install contextkit tests context ls Checking value of property in contextkit zypper install contextkit tests su nemo export DISPLAY 0 context listen KEY Restarting connman may help in WLAN issues systemctl restart connman service Restarting user session which includes Xorg home UI maliit and all of the other user space daemons systemctl restart user session 1000 service In addition to these see Mer Debugging guide Debugging Retrieved from https

    Original URL path: https://wiki.merproject.org/wiki/Nemo/Debugging (2016-02-01)
    Open archived version from archive

  • Nemo/ReportingBugs - Mer Wiki
    subcategory to which one can file bugs For Nemo there are at the time of writing this four 4 different bugzilla products Applications Hardware Adaptation Middleware and MTF UX Description of each product is shown after the product which tells you what kind of things belong to this product Also it is not critical to select the absolute one as the bug can be moved later to better place if needed Bugzilla Products Applications All bugs related to applications Exceptions Settings that are launched from the application view Example http sage kapsi fi Nemo mtf ux app launcher png should be filed under this category Hardware Adaptation If bug is related to Hardware adaptation such as N900 N950 i586 etc the bug should be filed here These bugs are usually bugs that do not belong to any other bugzilla product and are only reproducible on certain hardware Usually if you can see something wrong with the UX it belongs to other category than this Middleware Bugs related to some of the middleware components are filed here e g Maliit VKB or resource policy management See list of packages from OBS https build pub meego com project packages project CE 3AMW 3AShared MTF UX Everything related to UI that isn t part of any of the applications is more or less the MTF UX Locscreen http sage kapsi fi Nemo mtf ux lockscreen png systemui http sage kapsi fi Nemo mtf ux systemui png settings home screen etc After selecting Product Lets assume that bug from File Manager application was found and you want to report it You select Applications product and after that from the Components list you select the most suitable component as File Manager application has its own component File Manager component is selected Other fields can be

    Original URL path: https://wiki.merproject.org/wiki/Nemo/ReportingBugs (2016-02-01)
    Open archived version from archive

  • Nemo/USBNetworking - Mer Wiki
    you plug in the usb cable what happens on the host side is that NetworkManager will try to configure the interface using DHCP if the host uses NetworkManager that is There s no DHCP available so the connection will fail You should tell NetworkManager to use manual configuration Open Network Settings Select the right Wired connection the one with Hardware Address of 00 11 22 33 44 55 Go to Options Open the IPv4 Settings tab Change the Method from Automatic DHCP to Manual Click Add on the Addresses section Enter 192 168 2 14 as the address and 255 255 255 0 as the netmask The gateway can be left empty which means that your host machine won t try to route its own internet data through the device Now you can use ssh to connect to the device from the host machine For making life a bit easier you can add this snippet to ssh config Host nemo HostName 192 168 2 15 User nemo This allows you to just run ssh nemo to log in to the device as user nemo If you want to set up a full internet connection from the device through the host machine you ll need to make the host machine a router and set up the name server and routing parameters on the device Connect the device with usb cable to your host pc and run following commands sudo sbin ifconfig usb0 up 192 168 2 14 sudo usr sbin iptables A POSTROUTING t nat s 192 168 2 15 32 j MASQUERADE sudo usr sbin iptables P FORWARD ACCEPT echo 1 sudo tee proc sys net ipv4 ip forward Rest of these are here just to print something that is needed for the device to get routing work NAME SERVER

    Original URL path: https://wiki.merproject.org/wiki/Nemo/USBNetworking (2016-02-01)
    Open archived version from archive

  • Nemo/Creating Releases - Mer Wiki
    in OBS Packages are promoted from devel to testing by maintainer For this there is a script available at https github com nemomobile release tools blob master check project diff py that creates a creq line for you with all the modifications that are currently available between the two repos Example cmdline for promoting mw content check project diff py S nemo devel mw D nemo testing mw c show changelog add without changes While script is executed it shows you the changelog differences and also in the end gives the creq cmdline that can be copy pasted to terminal Example of creq cmd osc A https api merproject org creq m fixes a submit nemo devel mw connman qt nemo testing mw a submit nemo devel mw connman qt5 NOTE this creq cmdline is just a template and should be modified if you want to submit just part of the current changes After the creq has been submitted it goes to BOSS review which can be watched at mer boss IRC channel at Freenode BOSS also informs about status of reviews at nemomobile channel when request is accepted declined or needs review by maintainer After the prechecks are done the request comes to maintainer review where maintainer checks the request osc A https api merproject org review show diff REVIEW ID And if it is ok then accepts or declines the review osc A https api merproject org review accept decline REVIEW ID m COMMENT When this maintainer review is done the request goes to build check where it is checked that no builds are failing after this request is accepted to target project Snapshots Creating the snapshot Before one can do snapshot of repository one should check that the repository is build properly For this there is a tool in https github com nemomobile release tools blob master check build failures sh Example usage check build failures sh nemo testing mw latest armv7hl You can also go to the OBS WebUI and check the status from there After verifying that the repositories are build properly one can do snapshots with the snapshot script This snapshot tool for creating the snapshot is available at https github com nemomobile release tools and is used to create a snapshot and update the links latest links To create for example testing snapshot call nemo snapshot sh testing This new snapshot will be then available at http releases nemomobile org snapshots repos NOTE This script currently assumes that one is on the repository server and have certain permissions to directories Importing the snapshot https github com nemomobile release tools blob master import nemo snapshot dod sh can be used to import a new snapshot Example usage sudo import nemo snapshot dod sh nemo id NEMO ID After this you can see the new static snapshot as nemo NEMO ID projects in the OBS Release Creating the release To create a release one uses the https github com nemomobile release tools blob master nemo

    Original URL path: https://wiki.merproject.org/wiki/Nemo/Creating_Releases (2016-02-01)
    Open archived version from archive