Re: plasmate status?
On Monday, October 18, 2010, Chani wrote: > to demo plasmate - but when I tried to compile it it wanted qgpgme, and I qgpgme is in kdepimlibs. > are there plasmate packages or anything? binary packages? i don't think so, no. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: plasmate status?
On Mon, Oct 18, 2010 at 11:53 AM, Chani wrote: > On October 18, 2010 17:19:53 Aaron J. Seigo wrote: >> > are there plasmate packages or anything? >> >> binary packages? i don't think so, no. > > darn... eh, I'll probably just do the demo in kate or qt creator then. What distributions are you using? ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: plasmate status?
On Monday, October 18, 2010, Chani wrote: > On October 18, 2010 17:19:53 Aaron J. Seigo wrote: > > On Monday, October 18, 2010, Chani wrote: > > > to demo plasmate - but when I tried to compile it it wanted qgpgme, and > > > I > > > > qgpgme is in kdepimlibs. > > ah, I don't have that and don't intend to. given that things in kdepimlibs are fairly widely used and that it isn't all that big, i'd recommend installing it, tbh. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: plasmate status?
On Monday 18 October 2010 18:57:59 Marco Martin wrote: > On Monday 18 October 2010, Chani wrote: > > On October 18, 2010 18:26:47 Aaron J. Seigo wrote: > > > On Monday, October 18, 2010, Chani wrote: > > > > On October 18, 2010 17:19:53 Aaron J. Seigo wrote: > > > > > On Monday, October 18, 2010, Chani wrote: > > > > > > to demo plasmate - but when I tried to compile it it wanted > > > > > > qgpgme, and I > > > > > > > > > > qgpgme is in kdepimlibs. > > > > > > > > ah, I don't have that and don't intend to. > > > > > > given that things in kdepimlibs are fairly widely used and that it > > > isn't all that big, i'd recommend installing it, tbh. > > > > wouldn't it upset kdepim 4.4? > > given the changes in kdepim 4.5 I'd rather play it safe :) I'm probably > > lucky that kdepim and kdelibs still get along all right (ish). > > i'm using kdepim 4.4 with pimlibs trunk since a while, probably isn't a > wise thing to do, but seems to work decently so far works pretty well here too for ever since I switched to 4.5. It's also what Kubuntu does for example in 10.10: kdepim 4.4 with kdepimlibs 4.5 signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: plasmate status?
On Monday 18 October 2010 16:08:33 Chani wrote: > are there plasmate packages or anything? my system is a bit old, but maybe > the image we'll be using for the workshop will have the dependencies I'm > missing... Version 0.1alpha2 is packaged here, and builds vs trunk still: https://build.opensuse.org/package/show?package=plasmate&project=KDE:Unstable:Playground I can include it on the image if it is still useful. Will ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: plasmate status?
On Monday 18 October 2010 17:57:59 Marco Martin wrote: > On Monday 18 October 2010, Chani wrote: > > wouldn't it upset kdepim 4.4? > > given the changes in kdepim 4.5 I'd rather play it safe :) I'm probably > > lucky that kdepim and kdelibs still get along all right (ish). > > i'm using kdepim 4.4 with pimlibs trunk since a while, probably isn't a > wise thing to do, but seems to work decently so far Nope, should work fine, backwards compatible and all that, kdepim 4.4 continues to use the older parts of kdepimlibs, only kdepim 4.5 uses the new stuff and it's the kdepim side that is problamatic, not kdepimlibs. Cheers! John. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
The following simple change fixes build for me (otherwise the compiler complains about missing gpgme.h): diff --git a/publisher/signingwidget.cpp b/publisher/signingwidget.cpp index c5a8895..744cfc1 100644 --- a/publisher/signingwidget.cpp +++ b/publisher/signingwidget.cpp @@ -37,7 +37,7 @@ #define _FILE_OFFSET_BITS 64 -#include +#include #include #include #include 2011/3/17 Sebastian Kügler : > Hi, > > I've spent a few days working on various aspects of Plasmate, our little Add- > On creator application. Newest screenshots: -- Alexander Potashev ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Thursday, March 17, 2011 17:46:19 Alexander Potashev wrote:
> The following simple change fixes build for me (otherwise the compiler
> complains about missing gpgme.h):
>
> diff --git a/publisher/signingwidget.cpp b/publisher/signingwidget.cpp
> index c5a8895..744cfc1 100644
> --- a/publisher/signingwidget.cpp
> +++ b/publisher/signingwidget.cpp
> -#include
> +#include
I've instead added ${GPGME_INCLUDE} to the include path, can you test if it
build for you now (without your patch)?
Cheers,
--
sebas
http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
2011/3/17 Sebastian Kügler :
> I've instead added ${GPGME_INCLUDE} to the include path, can you test if it
> build for you now (without your patch)?
It builds now, thanks.
--
Alexander Potashev
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate Status
Adding on to that I've since added a new overlay menu to allow the user to select which wallpaper plugin currently installed to use as the previewer background (so having different wallpapers is now possible to degree!). I've also spoken briefly to aseigo about previewing plasmoids without actually installing them and am working on adding support for that at the moment. Next I plan to work on addressing the 'overlay doesn't work nicely when previewer is small' problem, as discussed with Shaan7. By the way I'm committing every bite-size enhancements I'm making, so you could get a pretty good idea what I've been doing by simply browsing the svn logs for plasmate :P On 6/29/09, Shantanu Tushar Jha wrote: > Hi all ! > Last IRC meet we had decided that we'll have a mail about the current > development status of Plasmate every two weeks. It has been two weeks > since. > AFAIK, moofang is working on the previewer on the ideas discussed > earlier and Diego is working on the Git integration using > kdevplatform. > I've not been able to write any code as I've final exams right now. > Will join moofang after my exams end on 10th next month. > Guys, add more info about the things I missed. > Lets make Plasmate rock :) > > -- > Sent from Gmail for mobile | mobile.google.com > > Shantanu Tushar(UTC +0530) > http://www.shantanutushar.com > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > -- Jason "moofang" Lim Yuen Hoe http://yuenhoe.co.cc/ ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate Status
Yep, you're right ! As you saw in the mailing list, there was a problem with managing the git pluging, which was *partially* resolved. In fact the code suggested wasn't totally correct, so I started to talk with apaku, a KDeveloper and Plugin designer, and I discovered that first, I have to subclass the ShellExtension class in order to setup the KDevplatform stuff, then init() that class, after that retrieve a reference to the Core and use it to retrieve the IPluginController by calling pluginController(). Nice, but an other problem arose: when calling pluginForExtension() to recieve a pointer to the git plugin, it returns an invalid pointer all the times =( Talking to apaku, the reason is because i set-up the Core class with the option Core::NoUi, and git sometimes wants to show some gui stuff, like committing with comments. Besides, initalizing the Core with Core::Default creates a full KDevelop gui, which is not our goal ! So, under his suggestion, now I'm using the plugins/git/gitplugin.cpp and I'm modifying the source for our purposes =) I'll commit it as soon as it compiles ( and also works =P ). Good luck with you exams, Cheers !! -- Messaggio inoltrato -- > From: Shantanu Tushar Jha > To: plasma-devel@kde.org > Date: Mon, 29 Jun 2009 17:58:02 +0530 > Subject: Plasmate Status > Hi all ! > Last IRC meet we had decided that we'll have a mail about the current > development status of Plasmate every two weeks. It has been two weeks > since. > AFAIK, moofang is working on the previewer on the ideas discussed > earlier and Diego is working on the Git integration using > kdevplatform. > I've not been able to write any code as I've final exams right now. > Will join moofang after my exams end on 10th next month. > Guys, add more info about the things I missed. > Lets make Plasmate rock :) > > -- > Sent from Gmail for mobile | mobile.google.com > > Shantanu Tushar(UTC +0530) > http://www.shantanutushar.com > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate Status
On Monday 29 June 2009, Diego Casella ([Po]lentino) wrote: > Yep, you're right ! > As you saw in the mailing list, there was a problem with managing the git > pluging, which was *partially* resolved. quite the story... > like committing with comments. Besides, initalizing the Core with > Core::Default creates a full KDevelop gui, which is not our goal ! that sounds like a very serious shortcoming of the kdevplatform. > So, under his suggestion, now I'm using the plugins/git/gitplugin.cpp and > I'm modifying the source for our purposes =) define "using" .. did you just copy it directly into plasmate, or are you using the plugin in a more direct fashion, or ...? -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
Hi guys, On the previewer end we're more or less done function-wise, as far as I can tell :) Since previous update, I've added support for loading plasmoids by path (so you don't need to install them beforehand), as well as modified the tool menus so that it uses a KMenu instead of the current overlay when the previewer is too small. The rest should just be aesthetic improvements... or am I missing something? I'm presently trying to find out why we can't type anything into the textfield that appears when we try to create a new project, but not having much luck since I'm clueless with gui designer ui's =( I agree that a directory tree on the sidebar would be more useful by the way, that's what I always envisioned before :P How bout having the current sidebar items as smaller, overhead buttons instead? I don't think we need that much real-estate for just buttons :P On 7/14/09, Diego Casella ([Po]lentino) wrote: > Hi guys, > other two weeks are gone, so it's time to sinc() with each other about > PlasMate status, IIRC =) > Now the TimeLine loads all the commits within the current branch, and also > all the commits that lead > to that branch ( I'm thinking to make that feature selectable by user, to > decrease the widget length ). > For each item, a tooltip shows the author who made the commit, the date and > the stored message. > In the top of the list is located the current working state of the project, > marked as "Not Saved". > The lower item holds the working branch, and its tooltip shows the other > available branches. > I also modified the GitRunner class, because the previous implementation > caused the app to not close. > Now I'm working on handling properly signals and slots, so we can have an > almost working timeline > within this week ! > By the way, do we *really* need the sidebar ? Each item can be found in the > final release of plasmate > under the menubar, so I was wondering if we can replace it with something > more useful like a directory tree list ... > Let me know about this, and also your ideas; lets make PlasMate rocks =) > > Cheers !! > -- Jason "moofang" Lim Yuen Hoe http://yuenhoe.co.cc/ ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
Hello :) On Monday 13 July 2009, 13:48 Diego Casella ([Po]lentino) wrote: > By the way, do we *really* need the sidebar ? Each item can be found in the > final release of plasmate > under the menubar, so I was wondering if we can replace it with something > more useful like a directory tree list ... Hmmm...remember that we are trying to do this for "non-core-developers"...what means that it can't look too much developer..it must be beautiful and attractiveI really don't know the impact of having menu entries for all the stuff that is in the sidebar. Maybe making the sidebar something smaller, at the top (like a toolbar)let's hear aseigo's opinion about this :) Cheers, -- Artur Duque de Souza openBossa Research Labs INdT - Instituto Nokia de Tecnologia -- Blog: http://blog.morpheuz.cc PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net -- signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Tue, Jul 14, 2009 at 14:09, Artur Souza (MoRpHeUz) wrote: > Hello :) > > On Monday 13 July 2009, 13:48 Diego Casella ([Po]lentino) wrote: >> By the way, do we *really* need the sidebar ? Each item can be found in the >> final release of plasmate >> under the menubar, so I was wondering if we can replace it with something >> more useful like a directory tree list ... > > Hmmm...remember that we are trying to do this for "non-core-developers"...what > means that it can't look too much developer..it must be beautiful and > attractiveI really don't know the impact of having menu entries for all > the > stuff that is in the sidebar. Maybe making the sidebar something smaller, at > the > top (like a toolbar)let's hear aseigo's opinion about this :) > > Cheers, > Hello everyone, are there already any screenshots available? Or is an early look restricted only to those who are willing to compile plasmate? I really enjoyed the specs that Aaron put up on techbase, but after reading about the progress every now and then, I'm wondering if we are on track to meet the goals set forth in said document. I did some mockups, back when Aaron posted the specs and I'd like to update them with what you guys have done so far. Perhaps I can even come up with some ideas for the sidebar. michael ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
There isn't much to look at now I think :P If you want I can grab a bunch of screenshots and post them on a blog or something - unless there is a rule of sorts against previewing unreleased stuff or the like? On 7/14/09, Michael Rudolph wrote: > On Tue, Jul 14, 2009 at 14:09, Artur Souza > (MoRpHeUz) wrote: >> Hello :) >> >> On Monday 13 July 2009, 13:48 Diego Casella ([Po]lentino) wrote: >>> By the way, do we *really* need the sidebar ? Each item can be found in >>> the >>> final release of plasmate >>> under the menubar, so I was wondering if we can replace it with something >>> more useful like a directory tree list ... >> >> Hmmm...remember that we are trying to do this for >> "non-core-developers"...what >> means that it can't look too much developer..it must be beautiful and >> attractiveI really don't know the impact of having menu entries for >> all the >> stuff that is in the sidebar. Maybe making the sidebar something smaller, >> at the >> top (like a toolbar)let's hear aseigo's opinion about this :) >> >> Cheers, >> > > Hello everyone, > > are there already any screenshots available? Or is an early look > restricted only to those who are willing to compile plasmate? > > I really enjoyed the specs that Aaron put up on techbase, but after > reading about the progress every now and then, I'm wondering if we are > on track to meet the goals set forth in said document. > > I did some mockups, back when Aaron posted the specs and I'd like to > update them with what you guys have done so far. Perhaps I can even > come up with some ideas for the sidebar. > > michael > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > -- Jason "moofang" Lim Yuen Hoe http://yuenhoe.co.cc/ ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Tue, Jul 14, 2009 at 16:16, Yuen Hoe Lim wrote: > There isn't much to look at now I think :P If you want I can grab a > bunch of screenshots and post them on a blog or something - unless > there is a rule of sorts against previewing unreleased stuff or the > like? > Hi Yuen, yeah, that's basically the question. Well, if there's no such rule, I'd definitely be interested in some screenshots, when you find the time. Thanks, michael ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Monday 13 July 2009, Diego Casella ([Po]lentino) wrote: > By the way, do we *really* need the sidebar ? which sidebar? the one for the timeline? > Each item can be found in the > final release of plasmate > under the menubar, so I was wondering if we can replace it with something > more useful like a directory tree list ... replace what with a directory tree listing of what? this sentence is really too vague for me to answer -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Mon, Jul 13, 2009 at 10:18 PM, Diego Casella ([Po]lentino) wrote: > > Hi guys, > other two weeks are gone, so it's time to sinc() with each other about > PlasMate status, IIRC =) > Now the TimeLine loads all the commits within the current branch, and also > all the commits that lead > to that branch ( I'm thinking to make that feature selectable by user, to > decrease the widget length ). > For each item, a tooltip shows the author who made the commit, the date and > the stored message. > In the top of the list is located the current working state of the project, > marked as "Not Saved". > The lower item holds the working branch, and its tooltip shows the other > available branches. > I also modified the GitRunner class, because the previous implementation > caused the app to not close. > Now I'm working on handling properly signals and slots, so we can have an > almost working timeline > within this week ! > By the way, do we *really* need the sidebar ? Each item can be found in the > final release of plasmate > under the menubar, so I was wondering if we can replace it with something > more useful like a directory tree list ... If you're talking about a directory tree list of all the files, I think It'll be much like an IDE. There's no need to display it as such. We can just have a list of files. As pointed out, being simple is one of Plasmate's primary goals. IMO lets have the sidebar smaller and maybe positioned just below the menu by default. > > > Let me know about this, and also your ideas; lets make PlasMate rocks =) > > Cheers !! > > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > -- Shantanu Tushar (UTC +0530) http://www.shantanutushar.com ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On 7/14/09, Yuen Hoe Lim wrote: > Hi guys, > > On the previewer end we're more or less done function-wise, as far as > I can tell :) Since previous update, I've added support for loading > plasmoids by path (so you don't need to install them beforehand), as > well as modified the tool menus so that it uses a KMenu instead of the > current overlay when the previewer is too small. The rest should just > be aesthetic improvements... or am I missing something? I still miss the overlay. Wanted to know from others which of the following is better - option 1: Use a KMenu when the previewer is small, and an Overlay when the previewer's size is sufficient. option 2: Always use a KMenu. IMO, having an overlay gives a visual feeling of being 'Plasma'. Opinions? > > I'm presently trying to find out why we can't type anything into the > textfield that appears when we try to create a new project, but not > having much luck since I'm clueless with gui designer ui's =( > > I agree that a directory tree on the sidebar would be more useful by > the way, that's what I always envisioned before :P How bout having the > current sidebar items as smaller, overhead buttons instead? I don't > think we need that much real-estate for just buttons :P > > On 7/14/09, Diego Casella ([Po]lentino) wrote: >> Hi guys, >> other two weeks are gone, so it's time to sinc() with each other about >> PlasMate status, IIRC =) >> Now the TimeLine loads all the commits within the current branch, and also >> all the commits that lead >> to that branch ( I'm thinking to make that feature selectable by user, to >> decrease the widget length ). >> For each item, a tooltip shows the author who made the commit, the date >> and >> the stored message. >> In the top of the list is located the current working state of the >> project, >> marked as "Not Saved". >> The lower item holds the working branch, and its tooltip shows the other >> available branches. >> I also modified the GitRunner class, because the previous implementation >> caused the app to not close. >> Now I'm working on handling properly signals and slots, so we can have an >> almost working timeline >> within this week ! >> By the way, do we *really* need the sidebar ? Each item can be found in >> the >> final release of plasmate >> under the menubar, so I was wondering if we can replace it with something >> more useful like a directory tree list ... >> Let me know about this, and also your ideas; lets make PlasMate rocks =) >> >> Cheers !! >> > > > -- > > Jason "moofang" Lim Yuen Hoe > http://yuenhoe.co.cc/ > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > -- Shantanu Tushar(UTC +0530) http://www.shantanutushar.com ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Wednesday 15 July 2009, 04:11 Shantanu Tushar Jha wrote: > option 1: Use a KMenu when the previewer is small, and an Overlay when > the previewer's size is sufficient. I would go with option 1. We really want to have a Plasma look&feel ;) Cheers, -- Artur Duque de Souza openBossa Research Labs INdT - Instituto Nokia de Tecnologia -- Blog: http://blog.morpheuz.cc PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net -- signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Wednesday 15 July 2009, Diego Casella ([Po]lentino) wrote: > I've attached some screenshots showing the current interface and the > timeline I'm coding; branches ... it's neat to see that in there, but let's be sure to keep them as a detail for more advanced usage. people using plasmate should not need to understand anything about revision control systems to use it. > P.S. : /me thinks that could be a good idea starting a personal blog too =P yes :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
More screenies! http://yuenhoe.co.cc/blog/2009/07/some-early-plasmate-screenies/ I don't know how to work the timeline stuff yet so you'd have to refer to Diego's attachments for those :) As I was saying to Shantanu, I think KMenu's have two main advantages despite the not-so-shiny look: the overlay has visibility issues with certain types of backgrounds (since it's semi-translucent), and KMenu is easily keyboard accessible, while the overlay isn't. Well, I suppose it should be possible to fix up the overlay for the accessibility part... On 7/15/09, Aaron J. Seigo wrote: > On Wednesday 15 July 2009, Diego Casella ([Po]lentino) wrote: >> I've attached some screenshots showing the current interface and the >> timeline I'm coding; > > branches ... it's neat to see that in there, but let's be sure to keep them > as > a detail for more advanced usage. people using plasmate should not need to > understand anything about revision control systems to use it. > >> P.S. : /me thinks that could be a good idea starting a personal blog too >> =P > > yes :) > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE core developer sponsored by Qt Software > -- Jason "moofang" Lim Yuen Hoe http://yuenhoe.co.cc/ ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Wed, Jul 15, 2009 at 1:52 PM, Artur Souza (MoRpHeUz) wrote: > On Wednesday 15 July 2009, 04:11 Shantanu Tushar Jha wrote: >> option 1: Use a KMenu when the previewer is small, and an Overlay when >> the previewer's size is sufficient. > > I would go with option 1. We really want to have a Plasma look&feel ;) That's interesting - I've been wondering what a KDE app with Plasma look&feel would look like recently. Maybe we can use it as a reference example if we need to cut down apps to look good on a netbook? -- Richard ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Wed, Jul 15, 2009 at 16:54, Yuen Hoe Lim wrote: > More screenies! > http://yuenhoe.co.cc/blog/2009/07/some-early-plasmate-screenies/ > I don't know how to work the timeline stuff yet so you'd have to refer > to Diego's attachments for those :) > > As I was saying to Shantanu, I think KMenu's have two main advantages > despite the not-so-shiny look: the overlay has visibility issues with > certain types of backgrounds (since it's semi-translucent), and KMenu > is easily keyboard accessible, while the overlay isn't. > > Well, I suppose it should be possible to fix up the overlay for the > accessibility part... > Hi Yuen, hi Diego, thank you very much for the screenshots. I'll go over my mockups again and post them, when they're ready. Perhaps you will find some ideas useful. michael ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
Yes, the keyboard navigation can probably be added without any difficulty. On 7/15/09, Yuen Hoe Lim wrote: > More screenies! > http://yuenhoe.co.cc/blog/2009/07/some-early-plasmate-screenies/ > I don't know how to work the timeline stuff yet so you'd have to refer > to Diego's attachments for those :) > > As I was saying to Shantanu, I think KMenu's have two main advantages > despite the not-so-shiny look: the overlay has visibility issues with > certain types of backgrounds (since it's semi-translucent), and KMenu > is easily keyboard accessible, while the overlay isn't. > > Well, I suppose it should be possible to fix up the overlay for the > accessibility part... > > On 7/15/09, Aaron J. Seigo wrote: >> On Wednesday 15 July 2009, Diego Casella ([Po]lentino) wrote: >>> I've attached some screenshots showing the current interface and the >>> timeline I'm coding; >> >> branches ... it's neat to see that in there, but let's be sure to keep >> them >> as >> a detail for more advanced usage. people using plasmate should not need to >> understand anything about revision control systems to use it. >> >>> P.S. : /me thinks that could be a good idea starting a personal blog too >>> =P >> >> yes :) >> >> -- >> Aaron J. Seigo >> humru othro a kohnu se >> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 >> >> KDE core developer sponsored by Qt Software >> > > > -- > > Jason "moofang" Lim Yuen Hoe > http://yuenhoe.co.cc/ > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > -- Sent from Gmail for mobile | mobile.google.com Shantanu Tushar(UTC +0530) http://www.shantanutushar.com ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
Hello everyone, I almost feel bad for asking you for the screenshots. You were of course right, there is not much to see yet in terms of workflow and other interactions. I think I understand your concerns with the sidebar now. And I agree with you completely; see my mockups. http://skitch.com/michaelrudolph/ba3j9/plasmate-editor2 http://skitch.com/michaelrudolph/ba3cg/plasmate-editor-timeline If that looks like a viable basis for a plasmate design, I'd gladly answer your questions. I'd also redo the start screen, that's missing right now. My ideas about it have changed a bit since I did my first mockups. Let me hear what you're thinking. michael ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Tue, Jul 14, 2009 at 9:43 AM, Yuen Hoe Lim wrote: > Hi guys, > > On the previewer end we're more or less done function-wise, as far as > I can tell :) Since previous update, I've added support for loading > plasmoids by path (so you don't need to install them beforehand), as > well as modified the tool menus so that it uses a KMenu instead of the > current overlay when the previewer is too small. The rest should just > be aesthetic improvements... or am I missing something? > > I'm presently trying to find out why we can't type anything into the > textfield that appears when we try to create a new project, but not > having much luck since I'm clueless with gui designer ui's =( > As I found out, its a problem with the validChars property in the projectName widget in startpage.ui which is of type KRestrictedLine. It seems it doesn't accept regular expressions ( I tried [a-z] but it only accepted 'a' when I typed). Currently validChars is set to ^[\\w-\\.]+$ . We could put qwertyuiopasdfghjklzxcvbnm there, but I think there should be a better way. Any ideas? (I've also CCed this mail to the author of KRestrictedLine widget). > I agree that a directory tree on the sidebar would be more useful by > the way, that's what I always envisioned before :P How bout having the > current sidebar items as smaller, overhead buttons instead? I don't > think we need that much real-estate for just buttons :P > > On 7/14/09, Diego Casella ([Po]lentino) wrote: > > Hi guys, > > other two weeks are gone, so it's time to sinc() with each other about > > PlasMate status, IIRC =) > > Now the TimeLine loads all the commits within the current branch, and > also > > all the commits that lead > > to that branch ( I'm thinking to make that feature selectable by user, > to > > decrease the widget length ). > > For each item, a tooltip shows the author who made the commit, the date > and > > the stored message. > > In the top of the list is located the current working state of the > project, > > marked as "Not Saved". > > The lower item holds the working branch, and its tooltip shows the other > > available branches. > > I also modified the GitRunner class, because the previous implementation > > caused the app to not close. > > Now I'm working on handling properly signals and slots, so we can have an > > almost working timeline > > within this week ! > > By the way, do we *really* need the sidebar ? Each item can be found in > the > > final release of plasmate > > under the menubar, so I was wondering if we can replace it with something > > more useful like a directory tree list ... > > Let me know about this, and also your ideas; lets make PlasMate rocks =) > > > > Cheers !! > > > > > -- > > Jason "moofang" Lim Yuen Hoe > http://yuenhoe.co.cc/ > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > -- Shantanu Tushar(UTC +0530) http://www.shantanutushar.com ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
Yep, it doesn't seem to accept regular expressions - but a string containing every permitted character.. http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRestrictedLine.html#f30d883fc60f67be39e8ffa039842cd6 I've tried, and it actually does allow me to type every character in the expression (like '[' and '$') =/ It doesn't seem like a pretty thing to do 'qwertyQWERTY012345etcetc' so maybe we could try a regular KLineEdit and do some form of validation? On 7/20/09, Shantanu Tushar Jha wrote: > On Tue, Jul 14, 2009 at 9:43 AM, Yuen Hoe Lim wrote: > >> Hi guys, >> >> On the previewer end we're more or less done function-wise, as far as >> I can tell :) Since previous update, I've added support for loading >> plasmoids by path (so you don't need to install them beforehand), as >> well as modified the tool menus so that it uses a KMenu instead of the >> current overlay when the previewer is too small. The rest should just >> be aesthetic improvements... or am I missing something? >> >> I'm presently trying to find out why we can't type anything into the >> textfield that appears when we try to create a new project, but not >> having much luck since I'm clueless with gui designer ui's =( >> > > As I found out, its a problem with the validChars property in the > projectName widget in startpage.ui which is of type KRestrictedLine. It > seems it doesn't accept regular expressions ( I tried [a-z] but it only > accepted 'a' when I typed). Currently validChars is set to ^[\\w-\\.]+$ . > > We could put qwertyuiopasdfghjklzxcvbnm there, but I think there should be a > better way. Any ideas? > > (I've also CCed this mail to the author of KRestrictedLine widget). > > >> I agree that a directory tree on the sidebar would be more useful by >> the way, that's what I always envisioned before :P How bout having the >> current sidebar items as smaller, overhead buttons instead? I don't >> think we need that much real-estate for just buttons :P >> >> On 7/14/09, Diego Casella ([Po]lentino) wrote: >> > Hi guys, >> > other two weeks are gone, so it's time to sinc() with each other about >> > PlasMate status, IIRC =) >> > Now the TimeLine loads all the commits within the current branch, and >> also >> > all the commits that lead >> > to that branch ( I'm thinking to make that feature selectable by user, >> to >> > decrease the widget length ). >> > For each item, a tooltip shows the author who made the commit, the date >> and >> > the stored message. >> > In the top of the list is located the current working state of the >> project, >> > marked as "Not Saved". >> > The lower item holds the working branch, and its tooltip shows the other >> > available branches. >> > I also modified the GitRunner class, because the previous implementation >> > caused the app to not close. >> > Now I'm working on handling properly signals and slots, so we can have >> > an >> > almost working timeline >> > within this week ! >> > By the way, do we *really* need the sidebar ? Each item can be found in >> the >> > final release of plasmate >> > under the menubar, so I was wondering if we can replace it with >> > something >> > more useful like a directory tree list ... >> > Let me know about this, and also your ideas; lets make PlasMate rocks =) >> > >> > Cheers !! >> > >> >> >> -- >> >> Jason "moofang" Lim Yuen Hoe >> http://yuenhoe.co.cc/ >> ___ >> Plasma-devel mailing list >> Plasma-devel@kde.org >> https://mail.kde.org/mailman/listinfo/plasma-devel >> > > > > -- > Shantanu Tushar(UTC +0530) > http://www.shantanutushar.com > -- Jason "moofang" Lim Yuen Hoe http://yuenhoe.co.cc/ ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Mon, Jul 20, 2009 at 2:59 PM, Yuen Hoe Lim wrote: > thing to do 'qwertyQWERTY012345etcetc' so maybe we could try a regular > KLineEdit and do some form of validation? See QRegExpValidator, that's what I used to validate stuff in the .desktop file editor in plasmate. Cheers Rich. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate status
On Mon, Jul 20, 2009 at 7:29 PM, Yuen Hoe Lim wrote: > Yep, it doesn't seem to accept regular expressions - but a string > containing every permitted character.. > > > http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRestrictedLine.html#f30d883fc60f67be39e8ffa039842cd6 > > I've tried, and it actually does allow me to type every character in > the expression (like '[' and '$') =/ It doesn't seem like a pretty > thing to do 'qwertyQWERTY012345etcetc' so maybe we could try a regular > KLineEdit and do some form of validation? For that we've to find out what characters make a valid project name (if there is a restriction as such, say, on name of a Plasmoid). Help wanted from others. Guys? Also, It'd be very nice If you're logged on #plasma whenever you're online as it helps a lot in discussion. (I have many times tried to catch you online, but in vain ;) > > On 7/20/09, Shantanu Tushar Jha wrote: > > On Tue, Jul 14, 2009 at 9:43 AM, Yuen Hoe Lim > wrote: > > > >> Hi guys, > >> > >> On the previewer end we're more or less done function-wise, as far as > >> I can tell :) Since previous update, I've added support for loading > >> plasmoids by path (so you don't need to install them beforehand), as > >> well as modified the tool menus so that it uses a KMenu instead of the > >> current overlay when the previewer is too small. The rest should just > >> be aesthetic improvements... or am I missing something? > >> > >> I'm presently trying to find out why we can't type anything into the > >> textfield that appears when we try to create a new project, but not > >> having much luck since I'm clueless with gui designer ui's =( > >> > > > > As I found out, its a problem with the validChars property in the > > projectName widget in startpage.ui which is of type KRestrictedLine. It > > seems it doesn't accept regular expressions ( I tried [a-z] but it only > > accepted 'a' when I typed). Currently validChars is set to ^[\\w-\\.]+$ . > > > > We could put qwertyuiopasdfghjklzxcvbnm there, but I think there should > be a > > better way. Any ideas? > > > > (I've also CCed this mail to the author of KRestrictedLine widget). > > > > > >> I agree that a directory tree on the sidebar would be more useful by > >> the way, that's what I always envisioned before :P How bout having the > >> current sidebar items as smaller, overhead buttons instead? I don't > >> think we need that much real-estate for just buttons :P > >> > >> On 7/14/09, Diego Casella ([Po]lentino) wrote: > >> > Hi guys, > >> > other two weeks are gone, so it's time to sinc() with each other > about > >> > PlasMate status, IIRC =) > >> > Now the TimeLine loads all the commits within the current branch, and > >> also > >> > all the commits that lead > >> > to that branch ( I'm thinking to make that feature selectable by > user, > >> to > >> > decrease the widget length ). > >> > For each item, a tooltip shows the author who made the commit, the > date > >> and > >> > the stored message. > >> > In the top of the list is located the current working state of the > >> project, > >> > marked as "Not Saved". > >> > The lower item holds the working branch, and its tooltip shows the > other > >> > available branches. > >> > I also modified the GitRunner class, because the previous > implementation > >> > caused the app to not close. > >> > Now I'm working on handling properly signals and slots, so we can have > >> > an > >> > almost working timeline > >> > within this week ! > >> > By the way, do we *really* need the sidebar ? Each item can be found > in > >> the > >> > final release of plasmate > >> > under the menubar, so I was wondering if we can replace it with > >> > something > >> > more useful like a directory tree list ... > >> > Let me know about this, and also your ideas; lets make PlasMate rocks > =) > >> > > >> > Cheers !! > >> > > >> > >> > >> -- > >> > >> Jason "moofang" Lim Yuen Hoe > >> http://yuenhoe.co.cc/ > >> ___ > >> Plasma-devel mailing list > >> Plasma-devel@kde.org > >> https://mail.kde.org/mailman/listinfo/plasma-devel > >> > > > > > > > > -- > > Shantanu Tushar(UTC +0530) > > http://www.shantanutushar.com > > > > > -- > > Jason "moofang" Lim Yuen Hoe > http://yuenhoe.co.cc/ > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > -- Shantanu Tushar(UTC +0530) http://www.shantanutushar.com ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate Status
Hi Shantanu, The timeline is fully committed, you simply have to right-click on the item to pop-up the menus / trigger the related action =P Note that up to now you have to manually setup the working directory by modifying line 165 in mainwindow.cpp, because that global variable isn't set yet ( actually the projects directories are saved in $HOME/.kde4/share/apps/plasmate which is not a good choice imo, if we want to focus on beginner developers... what about a $HOME/PlasMate_Projects folder instead? ) Now I'm focusing on building a default enviroment based on the project/language selected, so I'll fix also that pending issue =) By the way, I need a DataEngine example written in JavaScript, I searched in TechBase, kde-look.org and in various svn modules without result. As regards runners, I looked for examples in TechBase and in kdebase/workspace/plasma/runners, kdeplasma-addons/runners, kdereview/plasma/runners but I only found c++ sources... So probably scripting support for runners is not ready now, and I hid the corresponding button. However, why I still see the previewer with default wallpaper and without the button showed in Yuen's blog ? I wanna play with them too =D Cheers !! > -- Messaggio inoltrato -- > From: Shantanu Tushar Jha > To: Plasma > Date: Mon, 27 Jul 2009 01:17:10 +0530 > Subject: Plasmate Status > So, another 2 weeks, and here comes the Plasmate status report :) > > As the CHANGELOG says, we have > > 1. Fixed the problem with the project name not taking input. > (KRestrictedLine issue) > 2. Plasmate remembers positioning of the docks, and reloads on startup. > 3. Options to select the scripting language while creating a new project. > 4. Made some UI changes. > > And about the savesystem and Timeline, I believe Deigo is working hard. > ( Btw, I can't see the Timeline menus and see it in action, just a "Not a > savepoint" icon. Diego, Am I missing something, or its not commited yet? ) > > Make it rock !! > -- > Shantanu Tushar(UTC +0530) > http://www.shantanutushar.com > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate Status
On Monday 27 July 2009, 04:31 Diego Casella ([Po]lentino) wrote: > Note that up to now you have to manually setup the working directory by > modifying line 165 in mainwindow.cpp, because > that global variable isn't set yet ( actually the projects directories are > saved in $HOME/.kde4/share/apps/plasmate which is not > a good choice imo, if we want to focus on beginner developers... what about > a $HOME/PlasMate_Projects folder instead? ) > Now I'm focusing on building a default enviroment based on the > project/language selected, so I'll fix also that pending issue =) Usually this config paths are given by you, so you don't have to hardcode them ;) Check this class and method: KStandardDirs::locateLocal (it's also used on startpage.cpp). This way, Plasmate will use whatever path is set for kde applications to store stuff. Cheers! -- Artur Duque de Souza openBossa Research Labs INdT - Instituto Nokia de Tecnologia -- Blog: http://blog.morpheuz.cc PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net -- signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate Status
2009/7/27 Artur Souza (MoRpHeUz) > On Monday 27 July 2009, 04:31 Diego Casella ([Po]lentino) wrote: > > Note that up to now you have to manually setup the working directory by > > modifying line 165 in mainwindow.cpp, because > > that global variable isn't set yet ( actually the projects directories > are > > saved in $HOME/.kde4/share/apps/plasmate which is not > > a good choice imo, if we want to focus on beginner developers... what > about > > a $HOME/PlasMate_Projects folder instead? ) > > Now I'm focusing on building a default enviroment based on the > > project/language selected, so I'll fix also that pending issue =) > > Usually this config paths are given by you, so you don't have to hardcode > them > ;) > Yep I know, I placed that line only for testing purpose XD I told Shantanu how to modify it, so he can test its usage until I'll commit the correct versio ! Cheers !! > Check this class and method: KStandardDirs::locateLocal (it's also used on > startpage.cpp). > > This way, Plasmate will use whatever path is set for kde applications to > store > stuff. > > Cheers! > > -- > Artur Duque de Souza > openBossa Research Labs > INdT - Instituto Nokia de Tecnologia > -- > Blog: http://blog.morpheuz.cc > PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net > -- > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate Status
Diego: you need to sudo make install when building plasmate - the previewer overlay needs to be registered before it shows up :P If you have already done that then most likely the files aren't being copied to the correct folder. At least these are the sorts of problem me and Shantanu encoutered :P I haven't done much extra because I've been travelling around abit. I've been playing around with adding titles to the overlay menus (right now all you see are options). How does one get a Plasma::Label to be rendered with shadowed text? D: On 7/27/09, Diego Casella ([Po]lentino) wrote: > 2009/7/27 Artur Souza (MoRpHeUz) > >> On Monday 27 July 2009, 04:31 Diego Casella ([Po]lentino) wrote: >> > Note that up to now you have to manually setup the working directory by >> > modifying line 165 in mainwindow.cpp, because >> > that global variable isn't set yet ( actually the projects directories >> are >> > saved in $HOME/.kde4/share/apps/plasmate which is not >> > a good choice imo, if we want to focus on beginner developers... what >> about >> > a $HOME/PlasMate_Projects folder instead? ) >> > Now I'm focusing on building a default enviroment based on the >> > project/language selected, so I'll fix also that pending issue =) >> >> Usually this config paths are given by you, so you don't have to hardcode >> them >> ;) >> > > Yep I know, I placed that line only for testing purpose XD > I told Shantanu how to modify it, so he can test its usage until I'll commit > the correct versio ! > > Cheers !! > > >> Check this class and method: KStandardDirs::locateLocal (it's also used >> on >> startpage.cpp). >> >> This way, Plasmate will use whatever path is set for kde applications to >> store >> stuff. >> >> Cheers! >> >> -- >> Artur Duque de Souza >> openBossa Research Labs >> INdT - Instituto Nokia de Tecnologia >> -- >> Blog: http://blog.morpheuz.cc >> PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net >> -- >> > -- Jason "moofang" Lim Yuen Hoe http://yuenhoe.co.cc/ ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasmate Status
On Monday 27 July 2009, Diego Casella ([Po]lentino) wrote: > Note that up to now you have to manually setup the working directory by > modifying line 165 in mainwindow.cpp, because > that global variable isn't set yet what's wrong with m_model->package()? > ( actually the projects directories are > saved in $HOME/.kde4/share/apps/plasmate which is not > a good choice imo, if we want to focus on beginner developers... what about > a $HOME/PlasMate_Projects folder instead? ) the point is that they should never have to worry about where the files are. it's an implementation detail. and polluting the home dir with working data sets is not great form. > By the way, I need a DataEngine example written in JavaScript, I searched > in TechBase, kde-look.org and in various svn > modules without result. i added the first support for those 2 weeks ago, so it's not a mystery why you didn't find anything on it ;) i (or someone) still needs to do some bindings for Service as well so such dataengines can reimplement serviceForSource sanely. > As regards runners, I looked for examples in TechBase and in > kdebase/workspace/plasma/runners, kdeplasma-addons/runners, > kdereview/plasma/runners but I only found c++ sources... So probably > scripting support for runners is not ready now, and I hid > the corresponding button. please don't hide buttons because they don't work. that's what you do for final release only if you don't manage to get them working in the meantime, but hiding them during development is an awesome way to ensure they never get implemented. this is the out of sight, out of mind principle. and yes, it's possible to write runners with ecma script. as soon as it's possible to write something useful with plasmate, i'll do up some examples using it. ;) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Plasmate status
> -- Messaggio inoltrato -- > From: "Aaron J. Seigo" > To: plasma-devel@kde.org > Date: Wed, 15 Jul 2009 08:04:31 -0600 > Subject: Re: Plasma-devel Digest, Vol 13, Issue 33 > On Wednesday 15 July 2009, Diego Casella ([Po]lentino) wrote: > > > -- Messaggio inoltrato -- > > > From: "Aaron J. Seigo" > > > To: plasma-devel@kde.org > > > Date: Wed, 15 Jul 2009 00:10:29 -0600 > > > Subject: Re: Plasmate status > > > > > > On Monday 13 July 2009, Diego Casella ([Po]lentino) wrote: > > > > By the way, do we *really* need the sidebar ? > > > > > > which sidebar? the one for the timeline? > > > > Sorry, I was referring to the "Workflow" sidebar, the one with the "Start > > Page", > > "Edit", "Publish" and "Doc" items .. > > As I previously said, all these commands will be redundant in the final > > release of plasmate, > > in my opinion. So we could replace it with something more useful. > > hm. well ... "start page" is probably unnecessary, as is "edit" (given the > list of package entries) but a few items like publish, save point, refresh > preview, etc would make for nice toolbar entries. > That makes sense ... I'll modify it as soon as possible. > > > > Each item can be found in the > > > > final release of plasmate > > > > under the menubar, so I was wondering if we can replace it with > > > > something more useful like a directory tree list ... > > > > > > replace what with a directory tree listing of what? this sentence is > > > really too vague for me to answer > > > > With a directory tree listing the project files, of course =) > > isn't that already there? or did someone remove it? > I've never seen that dock widget =( > -- Messaggio inoltrato -- > From: "Aaron J. Seigo" > To: plasma-devel@kde.org > Date: Wed, 15 Jul 2009 08:15:18 -0600 > Subject: Re: Plasmate status > On Wednesday 15 July 2009, Diego Casella ([Po]lentino) wrote: > > I've attached some screenshots showing the current interface and the > > timeline I'm coding; > > branches ... it's neat to see that in there, but let's be sure to keep them > as > a detail for more advanced usage. people using plasmate should not need to > understand anything about revision control systems to use it. Ok, so with which synonym should I use instead of "branch" ? I was thinking about something like "sector" or "section" ( "create/switch section" sounds better IMO ), however I'm open to your suggestion ! > > > > P.S. : /me thinks that could be a good idea starting a personal blog too > =P > > yes :) > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE core developer sponsored by Qt Software > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Plasmate status
>> > With a directory tree listing the project files, of course =) >> >> isn't that already there? or did someone remove it? >> > > I've never seen that dock widget =( It's there, though I doubt it's actually doing anything now since we're not saving anything yet afaik. Plus its there when you start out, but it gets replaced with the editor kpart when you select anything. -- Jason "moofang" Lim Yuen Hoe http://yuenhoe.co.cc/ ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
