Re: repos and kickstarts for pa4
On Mon, May 20, 2013 at 9:20 PM, Hillel Lubman wrote: > May be Plasma Active can set up a donations page so anyone interested > would help key developers to be equipped with important devices (like key > x86 and ARM ones). This can even out the effort since right now, ARM feels > like a lower priority and bugs there are discovered slower. > The problem is not really that, I don't think more devices to current developers could help much. To scale in a manageable fashion, more devices is completely secondary to have more people involved and willing to maintain adaptations. Cheers, Maco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: repos and kickstarts for pa4
May be Plasma Active can set up a donations page so anyone interested would help key developers to be equipped with important devices (like key x86 and ARM ones). This can even out the effort since right now, ARM feels like a lower priority and bugs there are discovered slower. Regards, Hillel. On Mon, May 20, 2013 at 2:55 PM, Thomas Pfeiffer wrote: > On Monday 20 May 2013 14:31:48 Hillel Lubman wrote: > The problem is that Marco, who currently does most of the integration > work, does not have a Nexus 7 so he cannot test on his device. > The champion of PA on Nexus 7 is Ruediger Gad, so maybe he has time to > look into the problems there. > ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: repos and kickstarts for pa4
On Monday 20 May 2013 14:31:48 Hillel Lubman wrote: > I can do it on Nexus 7 (which has current devel image though it doesn't > load the UI anymore after the most recent update %). Great! Any help is greatly appreciated! The problem is that Marco, who currently does most of the integration work, does not have a Nexus 7 so he cannot test on his device. The champion of PA on Nexus 7 is Ruediger Gad, so maybe he has time to look into the problems there. > Is there any list of formal tests, or it's do whatever comes to mind? We do not have a list of formal tests (yet), so for now it's "do whatever comes to mind". Some things I usually check because they often break are - Creating / editing / deleting Activities - Adding files to Activities (via Add Items and via SLC) and removing them again - Starting several applications and switching between them - Files: - Tagging files - Copying files from/to an external storage device - Deleting files - Using the metadata filters (image size or Artist/Album for music) - Browsing the Web - Sending the device to sleep and waking it up again - Browsing though images - Changing screen settings - Downloading Add Ons Others surely have more things to add to this list, but I hope it already helps. Cheers, Thomas ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: repos and kickstarts for pa4
I can do it on Nexus 7 (which has current devel image though it doesn't load the UI anymore after the most recent update %). Is there any list of formal tests, or it's do whatever comes to mind? Thanks, Hillel. On Mon, May 20, 2013 at 10:13 AM, Thomas Pfeiffer wrote: > > Everyone with a device should test hell out of it. > ___ > Active mailing list > Active@kde.org > https://mail.kde.org/mailman/listinfo/active > ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: repos and kickstarts for pa4
On Monday 20 May 2013 19:26:22 Michael Bohlender wrote: > I tried to build one for the nexus 7 but I didn't get it to work. The > tegra3/common and tegra3/nexus7 had no packages so I had to change to the > "devel" repos. > > The last thing I get from systemd is "[OK] Reached target Graphical > Interface." followed by "dhd_rx_frame: net device not registered " but > it never starts a graphical interface. > > I don't have an adapter to attach a keyboard and investigate and I lack too > much knowledge in this field so I will have to wait for someone else to > build an Image (unless there is an obvious fix for this). yeah, unfortunately i can test only on i586 at the moment. would be good having a bit of integration work done on those branches on different device adaptations :) -- Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: repos and kickstarts for pa4
> > we have a new stable option for images creation. > > > > in the plasma-active-kickstart git repo, there is a new yaml for image > > creation. > > > > so, if you do > > > > mer-kickstarter -e . -c releases/plasma-active-4.yaml -o > > plasma-active-latest- ks/ > > > > it will generate kickstarts from kde:stable:* and "fixed" releases for > nemo > > and mer. this will be the basis of pa4. > > > > also, new repositories are enabled in the image: > > * mer-updates: it will contain bugfix updates for the base system if > neede > > (hopefully none) > > * kde:apps : it will contain 3rd party apps and packages based on kde. > being > > enabled on pa4 new packages can land there post release and will be easy > > installable on pa4 systems > > > > hopefully there will be soon images based on this kickstart > I tried to build one for the nexus 7 but I didn't get it to work. The tegra3/common and tegra3/nexus7 had no packages so I had to change to the "devel" repos. The last thing I get from systemd is "[OK] Reached target Graphical Interface." followed by "dhd_rx_frame: net device not registered " but it never starts a graphical interface. I don't have an adapter to attach a keyboard and investigate and I lack too much knowledge in this field so I will have to wait for someone else to build an Image (unless there is an obvious fix for this). > I'd suggest to start a collaborative intense testing phase as soon as the > images are available. Everyone with a device should test hell out of it. > + 1 count me in ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: repos and kickstarts for pa4
On Monday 20 May 2013 14:16:55 Marco Martin wrote: > Hi all, > > we have a new stable option for images creation. > > in the plasma-active-kickstart git repo, there is a new yaml for image > creation. > > so, if you do > > mer-kickstarter -e . -c releases/plasma-active-4.yaml -o > plasma-active-latest- ks/ > > it will generate kickstarts from kde:stable:* and "fixed" releases for nemo > and mer. this will be the basis of pa4. > > also, new repositories are enabled in the image: > * mer-updates: it will contain bugfix updates for the base system if neede > (hopefully none) > * kde:apps : it will contain 3rd party apps and packages based on kde. being > enabled on pa4 new packages can land there post release and will be easy > installable on pa4 systems > > hopefully there will be soon images based on this kickstart I'd suggest to start a collaborative intense testing phase as soon as the images are available. Everyone with a device should test hell out of it. A group of students has been trying out my tablet recently (they will be conducting usability tests with it) and still found quite a few problems, and I did not have the chance to systematically test recently. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
repos and kickstarts for pa4
Hi all, we have a new stable option for images creation. in the plasma-active-kickstart git repo, there is a new yaml for image creation. so, if you do mer-kickstarter -e . -c releases/plasma-active-4.yaml -o plasma-active-latest- ks/ it will generate kickstarts from kde:stable:* and "fixed" releases for nemo and mer. this will be the basis of pa4. also, new repositories are enabled in the image: * mer-updates: it will contain bugfix updates for the base system if neede (hopefully none) * kde:apps : it will contain 3rd party apps and packages based on kde. being enabled on pa4 new packages can land there post release and will be easy installable on pa4 systems hopefully there will be soon images based on this kickstart Cheers, Marco Martin ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 320034] Slowness of the Plasma Active topbar UI after startup on Nexus 7
https://bugs.kde.org/show_bug.cgi?id=320034 --- Comment #3 from Aaron J. Seigo --- I agree with Thomas; a fluid experience is more important than start up time. Some analysis of why these components take so long to load would also be nice, but loading on start would be a good improvement imho. -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 320034] Slowness of the Plasma Active topbar UI after startup on Nexus 7
https://bugs.kde.org/show_bug.cgi?id=320034 Thomas Pfeiffer changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||colo...@autistici.org Ever confirmed|0 |1 --- Comment #2 from Thomas Pfeiffer --- The reason for this is that all the elements in the Peak & Launch area (the ones that are shown when you poll the Top Bar down) are only loaded the first time you pull it down, in order to decrease startup time. Each time I present PA to someone right after booting, though, I get the feeling that maybe this turned out to not have been such a good idea after all: This is often one of the first things people to, and since it feels really really slow, the first impression people get from using PA is "Oh, it's slow!". So I'm starting to think that maybe these elements should be loaded at startup after all, because it's probably less noticeable if the startup takes a few seconds longer than if an interaction feels horribly slow. -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: [Kde-pim] Kontact Touch Mail - Usecases
On Sunday, 2013-05-19, Thomas Pfeiffer wrote: > On Friday 17 May 2013 19:23:11 Michael Bohlender wrote: > > Hello everyone > > > > The discussion about the initial mockups has shown that we need to agree > > on the usecases for Kontact Touch Mail first before we continue. I > > created a wikipage for that: > > http://community.kde.org/Plasma/Active/mail#Usecases > > > > Feel free to post any usecase you want to see enabled and we will > > discuss and classify them. This is not limited to what can be done in a > > single GSoC project. We need to be aware of everything we want to > > support as the general interaction design will likely constrain future > > features. > > > > My goal is to enable a set of core workflows that are likely to appear on > > a mobile/tablet device while keeping the PIM suite concept and "business > > users" in mind. This means that I will not copy over every function of > > the our desktop KMail but it also does not meant that the possible > > usecases are constrained to this core set. Other workflows should be > > possible but they might not be as elegant or prominent in the UI. > > > > Thanks for your participation. > > > > Mike > > Nice approach to the usecase list! > I've added some usecases and moved some around, accordeing to my opinion > (see history for details). > Björn, Kevin, what's your take? Please review the wiki page as well, > thanks! Looks indeed good! One thing I would not count as a major use case though is adding of a signature. At least in desktop KMail this is most often handled implicitly by selecting a different identity and at least for me that almost always happens automatically (configured folder specific identities or when replying based on which of my email addresses was the recepient). So from my personal usage changing signature is a rare, configuration change task. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
